Virtual neighbor objects for managing idle mode mobility in a wireless network

PRIORITY CLAIM

This patent application is a divisional application of U.S. patent application Ser. No. 14/709,172, filed on May 11, 2015 (now U.S. Pat. No. 9,686,727), and entitled “VIRTUAL NEIGHBOR OBJECTS FOR MANAGING IDLE MODE MOBILITY IN A WIRELESS NETWORK”, which is a continuation of, and claims priority to, each of U.S. patent application Ser. No. 13/886,616, filed on May 3, 2013 (now U.S. Pat. No. 9,060,319), and entitled “VIRTUAL NEIGHBOR OBJECTS FOR MANAGING IDLE MODE MOBILITY IN A WIRELESS NETWORK”, which is a continuation of U.S. patent application Ser. No. 12/614,033, filed on Nov. 6, 2009 (now U.S. Pat. No. 8,451,784), and entitled “VIRTUAL NEIGHBOR OBJECTS FOR MANAGING IDLE MODE RESELECTION.” The entireties of the aforementioned applications are incorporated by reference herein.

BACKGROUND

Wireless devices, e.g., cellular based devices, are ubiquitous. Moreover, there is increased demand for cellular services in areas where such services may be limited, e.g., residential or small business environments. Accordingly, a small cellular base station, e.g., femtocell, coupled to a wireless service provider's network via a broadband connection, can be located in such environments to improve wireless service capacity and/or coverage.

In a cellular based system, a mobile wireless device can communicate with a base station within a wireless coverage area, or sector, of the base station. During a voice and/or data session, e.g., phone call, the mobile wireless device operates in an active mode while communicating with the base station. When the mobile wireless device is powered on between calls, the mobile wireless device operates in an idle mode. During the idle mode, the mobile wireless device can perform a reselection procedure to transition between base stations and/or wireless access points, e.g., based on base station/wireless access point signal quality. For example, the mobile wireless device can monitor one or more control and/or broadcast channels of proximate base stations to obtain information for selecting a base station for servicing an incoming/outgoing call in the active mode. Such information can include a neighbor list, which identifies channels of proximate base stations the mobile wireless device can monitor during the idle mode. As the mobile wireless device moves within a sector served by a base station, the mobile wireless device can monitor the channels of base stations and/or access points utilizing the neighbor list and determine a best channel for active mode operation.

As increased amounts of femtocells are integrated into a broader cellular network to improve wireless service capacity and/or coverage, conventional techniques cannot adequately account for tens, hundreds, thousands, etc. of femtocells included within a base station's sector using a neighbor list. Each item included in a neighbor list transmitted by a base station corresponds to only one base station and/or one access point within a sector of the base station. Further, conventional techniques limit a number of neighbors included in a base station neighbor list to 32. Consequently, if more than 32 femtocells are within a sector of a base station, then a mobile wireless device cannot use a neighbor list to monitor and/or select each femtocell within the sector during idle mode.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a wireless network that includes a virtual neighbor component for facilitating optimal idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a wireless environment that includes a virtual neighbor component for facilitating effective idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates another wireless environment that facilitates effective idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a GSM wireless environment that facilitates effective idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a UMTS wireless environment that facilitates optimal idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a system that provides for effective idle mode reselection in a wireless-based communication infrastructure, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates a virtual neighbor object referencing multiple femtocells of a wireless network, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 8</figref> illustrates a virtual neighbor object, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 9</figref> illustrates a wireless environment utilizing different virtual neighbor objects, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates a reselection component including an access restriction component, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 11</figref> illustrates a wireless environment that includes two femtocells referenced by a virtual neighbor object, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 12</figref> illustrates a virtual neighbor component including a neighbor list component and a provisioning component, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 13</figref> illustrates a neighbor list including virtual neighbor objects, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 14</figref> illustrates a wireless environment associating six virtual neighbor objects to femtocells, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 15</figref> illustrates a system that includes an access component for facilitating effective idle mode reselection, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 16</figref> illustrates a wireless environment associating multiple femtocells to a virtual neighbor object, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 17</figref> illustrates a system that includes a femto neighbor list component and a transition component, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 18</figref> illustrates another wireless environment associating multiple femtocells to a virtual neighbor object, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 19</figref> illustrates a process that provides for effective idle mode reselection in a wireless environment, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 20</figref> illustrates another process that provides for effective idle mode reselection in a wireless environment, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 21</figref> illustrates yet another process that provides for effective idle mode reselection in a wireless environment, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 22</figref> illustrates a process associated with a mobile wireless device, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 23</figref> illustrates another process associated with a mobile wireless device, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 24</figref> illustrates a block diagram of a mobile wireless device, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 25</figref> illustrates a block diagram of a femto access point, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 26</figref> illustrates a block diagram of a wireless network environment, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 27</figref> illustrates a block diagram of a computer operable to execute the disclosed methods and apparatus, in accordance with an embodiment.

<figref idref="DRAWINGS">FIG. 28</figref> illustrates a schematic block diagram of an exemplary computing environment, in accordance with an embodiment.

DETAILED DESCRIPTION

Various non-limiting embodiments of systems, methods, and apparatus are provided for facilitating effective management of idle mode mobility in a wireless-based communication infrastructure. Such an infrastructure can include femtocells, which are wireless access points that can interface with a wired or wireless broadband network. Femtocells usually use a licensed radio spectrum operated and controlled by a wireless service provider, and are generally deployed to improve indoor wireless coverage. Moreover, femtocells can reduce loading of over-the-air radio resources, e.g., radio frequency channels, operated by the wireless service provider. User equipment (UE), e.g., a mobile wireless device, cell phone, wireless communications device, etc. can be operated by a subscriber of the wireless service provider within a femto coverage area, or femto network including one or more femtocells.

The UE can communicate with a core network, e.g., wired broadband network, via a femto access point (AP), or femtocell, utilizing a femto based wireless protocol. The femto AP employs a backhaul network, e.g., broadband wired network backbone, to route packet communication, e.g., voice traffic, data traffic, data, etc., to the core network. Typically, the UE can register with the femto AP, and communication, such as voice and/or data traffic, can be routed to the subscriber via the femto AP utilizing the femto based wireless protocol. As used herein, the phrases “femto based wireless protocol,” “femto wireless protocol,” or “femto based communication,” refer generally to a wireless protocol used to route data between a femto AP and UE, e.g., utilizing the licensed radio spectrum described above.

Further, the UE can communicate with the core network via a macro network that includes at least one base station generally intended to serve mobile wireless devices in outdoor locations. Each base station can employ a backhaul network, e.g., broadband wired or wireless network backbone, to route packet communication, e.g., voice traffic, data traffic, data, etc. to the core network. As the UE moves within the macro and/or femto networks between phone calls during idle mode, the UE can receive neighbor lists from proximate base stations and/or femto access points (APs). Each neighbor list received from a base station identifies a limited number of neighboring base stations and/or femto APs within a coverage area of the base station. The UE can select a base station and/or femto AP, e.g., associated with highest signal quality, from those identified via the neighbor list for servicing an incoming/outgoing call in active mode.

As increased amounts of femtocells are integrated into a broader cellular network to improve wireless service capacity and/or coverage, conventional techniques cannot adequately account for tens, hundreds, thousands, etc. of femtocells included within a base station's coverage area using a neighbor list. Each item included in a neighbor list transmitted by a base station corresponds to only one base station and/or access point within a coverage area, or sector, of the base station. Further, conventional techniques can limit a number of neighbors included in a base station neighbor list to 32. Consequently, if more than 32 femtocells are within a sector of a base station, then a mobile wireless device cannot use a neighbor list to monitor and/or select each femtocell within the sector during idle mode.

Compared to such techniques, various systems, methods, and apparatus described herein improve wireless customer experience(s) by effectively managing idle mode reselection between a cellular based macro network and a femto network.

Aspects, features, or advantages of the disclosed subject matter can be exploited in substantially any wireless telecommunication or radio technology, e.g., wireless fidelity (Wi-Fi™); Worldwide Interoperability for Microwave Access (WiMAX™); Enhanced General Packet Radio Service (Enhanced GPRS); 3GPP Long Term Evolution (LTE™); Third Generation Partnership Project 2 (3GPP2); Ultra Mobile Broadband (UMB); Third Generation Partnership Project (3GPP) Universal Mobile Telecommunication System (UMTS); High Speed Packet Access (HSPA); High Speed Downlink Packet Access (HSDPA); High Speed Uplink Packet Access (HSUPA); LTE™ Advanced (LTE-A), Global System for Mobile Communication (GSM), etc.

Additionally, one or more embodiments described herein can include legacy telecommunication technologies, e.g., plain old telephone service (POTS). It is also noted that selections of radio technology include second generation (2G), third generation (3G), and fourth generation (4G) evolution of the radio technology; however, such selections are not intended as a limitation of the disclosed subject matter and related aspects thereof. In addition, the aspects, features, or advantages of the disclosed subject matter can be exploited in disparate electromagnetic frequency bands. Moreover, one or more embodiments described herein can be executed in one or more network elements, such as a mobile wireless device, e.g., user equipment, and/or within one or more elements of a network infrastructure, e.g., radio network controller.

In the following description, numerous specific details are set forth to provide a thorough understanding of the embodiments. One skilled in the relevant art will recognize, however, that the techniques described herein can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

As utilized herein, terms “component,” “system,” “platform,” “node,” “layer,” “selector,” “interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a process running on a processor, a processor, an object, an executable, a program, a storage device, and/or a computer. By way of illustration, an application running on a server and the server can be a component. One or more components can reside within a process and a component can be localized on one computer and/or distributed between two or more computers.

Further, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as the Internet, with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry which is operated by a software application or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components.

The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.

Artificial intelligence based systems, e.g., utilizing explicitly and/or implicitly trained classifiers, can be employed in connection with performing inference and/or probabilistic determinations and/or statistical-based determinations as in accordance with one or more aspects of the disclosed subject matter as described herein. For example, an artificial intelligence system can be used, via provisioning component <b>1220</b> (described below) to automatically transmit a neighbor list from a wireless access point to a mobile wireless device; and automatically facilitate idle mode reselection between the wireless access point and another wireless access point via the mobile wireless device, based on, at least in part, the neighbor list.

In another example, the artificial intelligence system can be used, via reselection component <b>1000</b> (described below) to automatically facilitate idle mode reselection between a wireless access point and another wireless access point based on, at least in part, a channel number, a scrambling code, and at least one control parameter.

As used herein, the term “infer” or “inference” refers generally to the process of reasoning about or inferring states of the system, environment, user, and/or intent from a set of observations as captured via events and/or data. Captured data and events can include user data, device data, environment data, data from sensors, sensor data, application data, implicit data, explicit data, etc. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states of interest based on a consideration of data and events, for example. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification schemes and/or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, and data fusion engines) can be employed in connection with performing automatic and/or inferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, computer-readable carrier, or computer-readable media. For example, computer-readable media can include, but are not limited to, magnetic storage devices, e.g., hard disk; floppy disk; magnetic strip(s); optical disk (e.g., compact disk (CD), digital video disc (DVD), Blu-ray Disc™ (BD)); smart card(s), and flash memory device(s) (e.g., card, stick, key drive).

Moreover, terms like “user equipment” (UE), “mobile station (MS),” “mobile subscriber station,” “access terminal,” “terminal,” “handset,” “appliance,” “machine,” and similar terminology refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive and/or convey data associated with voice, video, sound, and/or substantially any data-stream or signaling-stream. Further, the foregoing terms are utilized interchangeably in the subject specification and related drawings. Likewise, the terms “local wireless communications cite,” “access point” (AP), “base station,” “Node B,” “evolved Node B,” “home Node B” (HNB), “home access point” (HAP), and the like are utilized interchangeably in the subject specification and drawings and refer to a wireless network component or apparatus that sends and/or receives data associated with voice, video, sound, and/or substantially any data-stream or signaling-stream between a set of subscriber stations—unless context warrants particular distinction(s) among the terms. Further, the data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” “agent,” “owner,” and the like are employed interchangeably throughout the subject specification and related drawings, unless context warrants particular distinction(s) among the terms. It should be appreciated that such terms can refer to human entities, or automated components supported through artificial intelligence, e.g., a capacity to make inference based on complex mathematical formalisms, that can provide simulated vision, sound recognition, decision making, etc. Also, the terms “local wireless communications cite,” “access point,” “base station,” and the like are utilized interchangeably throughout the subject specification, and refer to devices that can receive and transmit signal(s) from and to wireless devices through one or more antennas. In addition, the terms “wireless network” and “network” are used interchangeable in the subject application, unless context warrants particular distinction(s) among the terms.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a wireless network <b>100</b> that includes a virtual neighbor component <b>130</b> for facilitating optimal idle mode reselection, in accordance with an embodiment. Wireless network <b>100</b> can further include macro network <b>110</b> and femto network <b>120</b>. Macro network <b>110</b> can include at least one base station (not shown) that serves mobile wireless devices (not shown) in outdoor locations via a macro cell. The term “macro cell” generally refers to a coverage area, or geographical area, having a radius of at least one kilometer. The terms “microcell,” “picocell,” and “femtocell” generally refer to progressively smaller sized coverage areas.

While aspects and/or features of the subject disclosure are illustrated in relation to macro cells, femtocells, and femtocell access points, such aspects and/or features are also applicable to, and can be implemented in: a microcell, or microcell access point; a picocell, or picocell access point; a Wi-Fi™ access point; a WiMAX™ access point, a Bluetooth™ access point, other wireless-based access points; or the like. Further, macro network <b>110</b> can include a core network (not shown) comprising one or more cellular technologies, e.g., 3GPP UMTS, GSM, etc. Each base station, or access point, of macro network <b>110</b> can communicate with the core network via a wired backbone link (not shown), e.g., optical fiber, twisted-pair, coaxial cable, etc.

Femto network <b>120</b> can include femtocells (not shown), which are wireless access points that can interface with macro network <b>110</b>. It should be appreciated that although femto network <b>120</b> is illustrated in <figref idref="DRAWINGS">FIG. 1</figref> as an entity distinct from macro network <b>110</b>, femto network <b>120</b> can be located/included within and/or across one or more locations, components, e.g., hardware, software, etc., of macro network <b>110</b>. For example, one or more femtocells of femto network <b>120</b> can be located within a macro cell served by a base station of macro network <b>110</b>.

A mobile wireless device served by macro network <b>110</b>, and operated by a subscriber within a femto coverage area of femto network <b>120</b>, can communicate with the core network of macro network <b>110</b> via one or more femto access points (APs) (not shown). Typically, the mobile wireless device can register with a femto AP and communication, e.g., voice or data traffic, can be routed to the subscriber through the femto AP utilizing a femto based wireless protocol, e.g., based on a licensed or unlicensed radio spectrum. The femto AP can employ a backhaul network (not shown), e.g., broadband wired or wireless network backbone, to route packet communication, e.g., voice traffic, data traffic, data, etc. to the core network of macro network <b>110</b>.

As the mobile wireless device moves within and/or between macro network <b>110</b> and femto network <b>120</b> during idle mode, e.g., between phone calls, it can receive a neighbor list transmitted from a proximate base station and/or access point. The mobile wireless device can select a base station or femto AP from the neighbor list to service incoming/outgoing calls during active mode. Conventional neighbor lists contain a small number of broadcast channels from which the mobile wireless device can select from in order to service incoming/outgoing calls during active mode. Moreover, each broadcast channel, or reference to a base station/femto AP, corresponds to only one access point within a coverage area, or sector, of the proximate base station and/or access point. Consequently, if more femtocells are within a sector of a base station than can be identified in a neighbor list, a mobile wireless device cannot use the neighbor list to select from each femtocell within the sector during idle mode. For example, if a residential area within a base station sector contains over 50 femtocells, and a neighbor list transmitted from the base station to a mobile wireless device only identifies 32 neighbors, the mobile wireless device cannot reselect to each femtocell in the base station sector using the neighbor list.

Compared to conventional techniques, virtual neighbor component <b>130</b> can enable effective idle mode reselection between macro and femto networks, e.g., between femto network <b>110</b> and macro network <b>120</b>, by utilizing virtual femto neighbor objects in neighbor lists (not shown). Accordingly, with respect to the example above, virtual neighbor component <b>130</b> can enable the base station to account for the over 50 femtocells via the neighbor list by assigning more than one femtocell to a virtual neighbor object. As such, each virtual neighbor object included in the neighbor list can identify multiple femtocells within the base station sector. In addition, because a virtual neighbor object can identify multiple access points, less than 32 entries in a neighbor list can be used to identify all base stations and/or femto APs within a coverage area during idle mode.

It should be appreciated that although virtual neighbor component <b>130</b> is illustrated in <figref idref="DRAWINGS">FIG. 1</figref> as an entity distinct from macro network <b>110</b> and femto network <b>120</b>, virtual neighbor component <b>130</b> can be located/included within and/or across one or more components, e.g., hardware, software, etc., of wireless network <b>100</b>, e.g., within or among hardware and/or software of components of macro network <b>110</b> and/or femto network <b>120</b>.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a wireless environment <b>200</b> that includes a virtual neighbor component <b>260</b> for facilitating effective idle mode reselection, in accordance with an embodiment. Each macro cell <b>205</b> represents a “macro” cell coverage area, or sector, served by a base station <b>210</b>. It should be appreciated that although macro cells <b>205</b> are illustrated as hexagons, macro cells <b>205</b> can adopt other geometries generally dictated by a deployment or topography of the macro cell coverage area, or covered geographic area, e.g., metropolitan statistical area (MSA), rural statistical area (RSA), etc. Macro cell coverage is generally intended to serve mobile wireless devices, e.g., mobile wireless device <b>220</b>_A, mobile wireless device <b>220</b>_B, in outdoor locations. An over-the-air wireless link <b>215</b> provides the macro coverage, and wireless link <b>215</b> comprises a downlink (DL) and an uplink (UL) (both not shown) that can utilize a predetermined band of radio frequency (RF) spectrum associated with, e.g., GSM, 3GPP UMTS. Accordingly, mobile wireless device <b>220</b>_Acan be a GSM or 3GPP UMTS mobile phone, while <b>220</b>_Bcan be a remote computing device with GSM or 3GPP UMTS capabilities.

Base station <b>210</b>—including associated electronics, circuitry and/or components—and wireless link <b>215</b> form a radio network, e.g., base station subsystem (BSS) associated with a GSM wireless network, or radio access network (RAN) associated with a UMTS wireless network. In addition, base station <b>210</b> communicates with macro network platform <b>208</b> via backhaul link(s) <b>251</b>. Macro network platform <b>208</b> represents a core network comprising one or more cellular wireless technologies, e.g., 3GPP UMTS or GSM. In one aspect, macro network platform <b>208</b> controls a set of base stations <b>210</b> that serve either respective cells or a number of sectors within such cells. Macro network platform <b>208</b> can also communicate with other base stations (not shown) that serve other cells (not shown). Backhaul link(s) <b>251</b> can include a wired backbone link, e.g., optical fiber backbone, twisted-pair line, T1/E1 phone line, synchronous or asynchronous digital subscriber line (DSL), asymmetric DSL (ADSL), coaxial cable, etc. Moreover, backhaul links(s) <b>251</b> can link disparate base stations <b>210</b> based on macro network platform <b>208</b>.

Packet communication, e.g., voice traffic, data traffic, is typically routed through a broadband wired network backbone (or backhaul network) utilizing, e.g., optical fiber backbone, twisted-pair line, T1/E1 phone line, synchronous or asynchronous digital subscriber line (DSL), asymmetric DSL (ADSL), coaxial cable, etc. To this end, base station <b>210</b> is typically connected to the backhaul network, e.g., service provider network <b>255</b>, via a broadband modem (not shown) and backhaul link(s) <b>251</b>. Through backhaul link(s) <b>251</b>, base station <b>210</b> can handle substantially any quality of service (QoS) for heterogeneous packetized traffic, e.g., various multiple packet flows.

Base station <b>210</b> can integrate into an existing network, e.g., GSM or 3GPP network, via various interfaces, for example: via an A-bis interface (not shown) between a base transceiver station (BTS) and a base station controller (BSC); via an Iub interface (not shown) between a radio network controller (RNC) and base station <b>210</b>; via an interface (not shown) between an RNC and a Circuit Switched Core Network (CS-CN); via an interface (not shown) between an RNC and an Iu-CS interface; via an interface (not shown) between an RNC and a Packet Switched Core Network (or Iu-PS interface); via an interface (not shown) between a BSC and a mobile switching center (MSC) and/or Network Switching Subsystem (NNS); via an interface (not shown) between a Serving General Packet Radio Service Support Node (SGSN) and a public data network (PDN) (or Gi interface); via an interface (not shown) between an SGSN and other SGSNs (or Gn interface).

A group of femtocells <b>225</b> served by respective femto access points (APs) <b>230</b> can be deployed within each macro cell <b>205</b>. While three femtocells <b>225</b> are deployed per macro cell <b>205</b> as shown in <figref idref="DRAWINGS">FIG. 2</figref>, aspects of the subject disclosure can be directed to femtocell deployments with substantive femto AP <b>230</b> density, e.g., 10⁴-10⁸femto APs <b>230</b> per base station <b>210</b>. As such, femtocell group <b>227</b> as illustrated in <figref idref="DRAWINGS">FIG. 2</figref> includes more than 10⁴femto APs <b>230</b> (not shown). Femtocell <b>225</b> typically covers an area (or coverage area) that includes confined area <b>245</b>, which is determined, at least in part, by transmission power allocated to femto AP <b>230</b>, path loss, shadowing, etc. While the confined area <b>245</b> and coverage area typically coincide, it should be appreciated that in certain deployment scenarios, the coverage area can include an outdoor portion, e.g., parking lot, patio deck, recreation area; while confined area <b>245</b> can be enclosed by a building, e.g., home, retail store, business. The coverage area typically is spanned by a coverage radius ranging from 20 to 100 meters. Confined area <b>245</b> is generally associated with an indoor space and/or building, such as a residential space, e.g., house, condominium, apartment complex, etc.; business space, e.g., retail store, mall, etc.; or public space, e.g., library, hospital, etc. Such spaces can span about 5000 sq. ft.

Femto AP <b>230</b> typically serves a few (e.g., 2-5) wireless devices, e.g., UE <b>220</b>_Aand subscriber station <b>220</b>_B, within the coverage area associated with respective femtocells <b>225</b>—each wireless device coupled to femto AP <b>230</b> via a wireless link <b>235</b> that comprises a downlink and an uplink (depicted as arrows in <figref idref="DRAWINGS">FIG. 2</figref>). A femto network platform <b>209</b> can control such service(s), in addition to registering femto APs, provisioning femto APs, managing macro-to-femto handover, and managing femto-to-macro handover. Control or management is facilitated by access point backhaul link(s) <b>253</b> that connect deployed femto APs <b>230</b> with femto network platform <b>209</b>. Access point backhaul link(s) <b>253</b> are substantially similar to backhaul link(s) <b>251</b>.

Femto network platform <b>209</b> also includes components, e.g., nodes, gateways, interfaces, that facilitate packet-switched (PS), e.g., internet protocol (IP), traffic and signal generation for networked telecommunication. It should be appreciated that femto network platform <b>209</b> can integrate seamlessly with substantially any PS-based and/or circuit switched (CS)-based network (such as macro network platform <b>208</b>). Thus, operation with a wireless device such as <b>220</b>_Ais substantially seamless when handover from femto-to-macro, or vice versa, occurs.

As an example, femto AP <b>230</b> can integrate into an existing network, e.g., GSM or 3GPP network, via various interfaces, for example: via an A-bis interface (not shown) between a base transceiver station (BTS) and a base station controller (BSC); via an Iub interface (not shown) between a radio network controller (RNC) and base station <b>210</b>; via an interface (not shown) between an RNC and a Circuit Switched Core Network (CS-CN); via an interface (not shown) between an RNC and an Iu-CS interface; via an interface (not shown) between an RNC and a Packet Switched Core Network (or Iu-PS interface); via an interface (not shown) between a BSC and a mobile switching center (MSC) and/or Network Switching Subsystem (NNS); via an interface (not shown) between a Serving General Packet Radio Service Support Node (SGSN) and a public data network (PDN) (or Gi interface); via an interface (not shown) between an SGSN and other SGSNs (or Gn interface).

Substantially all voice or data active sessions associated with subscribers within femtocell coverage, e.g., coverage area associated with femtocell <b>225</b>, are terminated once the femto AP <b>230</b> is shut down; however, for data sessions, data can be recovered at least in part through a buffer, e.g., memory, associated with a femto gateway at femto network platform <b>209</b>. Coverage of a suspended (or hotlined) subscriber station, or an associated account, can be blocked, e.g., over an associated air-interface. If a suspended or hotlined customer who owns a femto AP <b>230</b> is in Hotline/Suspend status, there is no substantive impact to customers covered through the subject femto AP <b>230</b>. In another aspect, femto AP <b>230</b> can exploit high-speed downlink packet access via an interface with macro network platform <b>208</b>, or through femto network platform <b>209</b>, in order to accomplish substantive bitrates.

As described above, conventional idle mode reselection techniques cannot adequately account for tens, hundreds, thousands, etc. of femtocells included within a sector of a base station since (1) each reference included in a conventional neighbor list corresponds to only one base station/femto AP within the sector and (2) such techniques limit neighbor lists to contain a small amount of references, e.g., 32. Accordingly, virtual neighbor component <b>260</b> can facilitate optimal idle mode reselection within wireless network <b>200</b> by enabling reuse of virtual neighbor object references in neighbor lists—the virtual neighbor object references identifying multiple base stations/femtocells, e.g., base stations <b>210</b>/femto APs <b>230</b>, within wireless network <b>200</b>.

It should be appreciated that although virtual neighbor component <b>260</b> is illustrated in <figref idref="DRAWINGS">FIG. 2</figref> as an entity distinct from, e.g., base stations <b>210</b>, femto APs <b>230</b>, mobile wireless devices <b>220</b>_Aand <b>220</b>_B, service provider network <b>225</b>, etc., aspects and/or features of virtual neighbor component <b>260</b> can be located/included within and/or across one or more components, e.g., hardware, software, etc., of wireless network <b>200</b>. For example, in one embodiment, virtual neighbor component <b>260</b> can be located within any component(s) of a GSM and/or UMTS core network e.g. service provider network <b>255</b>. In another embodiment, virtual neighbor component <b>260</b> can be located in hardware and/or software of base stations <b>210</b>, femto APs <b>230</b>, and/or mobile wireless devices <b>220</b>_Aand <b>220</b>_B. Moreover, it should be appreciated that features and advantages of the subject innovation can be implemented in microcells, picocells, or the like, wherein base station <b>210</b> can be embodied in an access point.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates another wireless environment (<b>300</b>) that facilitates effective idle mode reselection, in accordance with an embodiment. Wireless environment <b>300</b> can comprise one or more base stations <b>210</b>, for example: coupled to a BSC forming a base station system (BSS) (see, e.g., <figref idref="DRAWINGS">FIG. 4</figref>); coupled to an RNC forming a UMTS Terrestrial Radio Access Network (UTRAN) (see, e.g., <figref idref="DRAWINGS">FIG. 5</figref>). Radio network <b>320</b> can couple to a core network, e.g., service provider network <b>255</b>, via one or more backhaul links <b>251</b> (see above) to facilitate wireless communication and data transfer to one or more wireless devices, e.g., mobile wireless device <b>220</b>_A/mobile wireless device <b>220</b>_B, in accordance with the disclosed subject matter. Radio network <b>320</b> can comprise any wireless technology, e.g., GSM, UMTS. Wireless environment <b>300</b> includes virtual neighbor component <b>310</b> that can facilitate optimal idle mode reselection, e.g., between and/or among macro network <b>110</b> and femto network <b>120</b> (see above), within any wireless technology supporting idle mode reselection, e.g., GSM, 3GPP UMTS.

It should be appreciated that although virtual neighbor component <b>310</b> is illustrated in <figref idref="DRAWINGS">FIG. 3</figref> as an entity distinct from radio network <b>320</b> and service provider network <b>255</b>, virtual neighbor component <b>310</b> can be located/included within and/or across one or more components, e.g., hardware, software, etc., of wireless environment <b>300</b>, e.g., within or among hardware and/or software of components of radio network <b>320</b> and/or service provider network <b>255</b>.

Further, one or more aspects of wireless environment <b>300</b>, and the wireless environments, networks, systems, apparatus, and processes explained herein, may constitute machine-executable instructions embodied within a machine, e.g., computer, readable medium, which when executed by a machine will cause the machine to perform the operations described. Additionally, the systems and processes may be embodied within hardware, such as an application specific integrated circuit (ASIC) or the like. The order in which some or all of the process blocks appear in each process should not be deemed limiting. Rather, it should be understood by a person of ordinary skill in the art having the benefit of the instant disclosure that some of the process blocks may be executed in a variety of orders not illustrated.

Conventional idle mode reselection techniques utilizing neighbor lists cannot adequately account for integration of femtocells within a cellular based macro network because such neighbor lists contain a small number of references, and each reference corresponds to only one access point within a sector of a base station/femto AP. Compared to such techniques, various systems, methods, and apparatus described herein facilitate effective idle mode reselection between a macro network and a femto network by utilizing virtual neighbor objects. For example, virtual neighbor component <b>310</b> can facilitate referencing multiple base stations, and/or femto APs, within wireless environment <b>300</b> with one virtual neighbor object.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a GSM wireless environment <b>400</b> that facilitates effective idle mode reselection, in accordance with an embodiment. GSM wireless environment <b>400</b> can include at least one base transceiver station (BTS) <b>440</b> coupled to base station controller (BSC) <b>430</b> to form a base station subsystem (BSS) <b>420</b> of a GSM network. BSS <b>420</b> can be coupled to a core network, e.g., service provider network <b>455</b>, via one or more backhaul links <b>451</b> (see above) to facilitate wireless communication and data transfer to one or more wireless devices, e.g., mobile station <b>450</b>_A/mobile station <b>450</b>_B, in accordance with the disclosed subject matter. GSM wireless environment <b>400</b> includes virtual neighbor component <b>410</b>, which can facilitate optimal idle mode reselection between and/or among BTS <b>440</b> and a femto AP (not shown) within the GSM network utilizing virtual neighbor objects (see above). It should be appreciated that although virtual neighbor component <b>410</b> is illustrated in <figref idref="DRAWINGS">FIG. 4</figref> as an entity distinct from other entities and/or components of GSM wireless environment <b>400</b>, one or more aspects of virtual neighbor component <b>410</b> can be located/included within one or more components, e.g., hardware, software, etc. (e.g., BSS <b>420</b>, femto AP (not shown)), of GSM wireless environment <b>400</b>.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a UMTS wireless environment <b>500</b> that facilitates optimal idle mode reselection, in accordance with an embodiment. UMTS wireless environment <b>500</b> can include at least one node B <b>540</b> coupled to a radio network controller <b>530</b> to form a UMTS Terrestrial Radio Access Network (UTRAN) <b>520</b> of a UMTS network. UTRAN <b>520</b> can couple to a core network, e.g., service provider network <b>555</b>, via one or more backhaul links <b>551</b> (see above) to facilitate wireless communication and data transfer to one or more wireless devices, e.g., user equipment <b>550</b>_A/user equipment <b>550</b>_B, in accordance with the disclosed subject matter. UMTS wireless environment <b>500</b> includes virtual neighbor component <b>510</b> that can facilitate optimal idle mode reselection between and/or among node B <b>540</b> and a femto AP (not shown) within the UMTS network, e.g., a 3GPP network, utilizing virtual neighbor objects (see above). It should be appreciated that although virtual neighbor component <b>510</b> is illustrated in <figref idref="DRAWINGS">FIG. 5</figref> as an entity distinct from other entities and/or components of UMTS wireless environment <b>500</b>, one or more aspects of virtual neighbor component <b>510</b> can be located/included within one or more components, e.g., hardware, software, etc. (e.g., UTRAN <b>520</b>, femto AP (not shown)), of UMTS wireless environment <b>500</b>, e.g., a 3GPP network.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a system <b>600</b> that provides for effective idle mode reselection in a wireless-based communication infrastructure, in accordance with an embodiment. System <b>600</b> can include a virtual neighbor component <b>610</b> and a reselection component <b>620</b>. Virtual neighbor component <b>610</b> can be configured to create at least one virtual neighbor object and associate the at least one virtual neighbor object with at least two wireless access points. For example, virtual neighbor component can create six virtual neighbor objects and associate more than one access point, e.g., base station, femto AP, etc. of a wireless network, e.g., a 3GPP network or GSM network, with one of the six virtual neighbor objects.

In an aspect, the at least two wireless access points can include at least one of: a microcell; a microcell access point; a picocell; a picocell access point; a Wi-Fi™ access point; a WiMAX™ access point; a Bluetooth™ access point; an Enhanced GPRS access point; a 3GPP access point; an LTE™ access point; a 3GPP2 access point; a UMB access point; a 3GPP UMTS access point; a HSPA access point; a HSDPA access point; a HSUPA access point; an LTE-A access point; or a GSM access point.

In another aspect, illustrated by <figref idref="DRAWINGS">FIG. 7</figref>, virtual neighbor component <b>610</b> can create a virtual neighbor object <b>710</b> and associate virtual neighbor object <b>710</b>, e.g., as a reference, with five femtocells <b>225</b> of wireless network <b>700</b>. As described below, one or more mobile wireless devices (not shown) can select one of the five femtocells <b>225</b> for active mode servicing based on virtual neighbor object <b>710</b> and one or more access restrictions. Further, it should be appreciated that although virtual neighbor component <b>610</b> can reference, or associate, five femtocells <b>225</b> with virtual neighbor object <b>710</b>, virtual neighbor component <b>610</b> can associate virtual neighbor object <b>710</b> with many more femtocells <b>225</b>, e.g., 10⁸femto APs <b>230</b> per base stations <b>210</b>, throughout wireless network <b>700</b>.

Now returning to <figref idref="DRAWINGS">FIG. 6</figref>, reselection component <b>620</b> of system <b>600</b> can be configured to facilitate idle mode reselection between a wireless access point of the at least two wireless access points and an other wireless access point based on, at least in part, the at least one virtual neighbor object. In one embodiment, the other wireless access point can include: a microcell; a microcell access point; a picocell; a picocell access point; a Wi-Fi™ access point; a WiMAX™ access point; a Bluetooth™ access point; an Enhanced GPRS access point; a 3GPP access point; an LTE™ access point; a 3GPP2 access point; a UMB access point; a 3GPP UMTS access point; a HSPA access point; a HSDPA access point; a HSUPA access point; an LTE-A access point; or a GSM access point.

As described above, a mobile wireless device can perform a reselection procedure between phone calls, e.g., during idle mode, to transition between base stations and/or femtocells, e.g., based on received signal quality. The mobile wireless device can receive information via control/broadcast channels of the base stations and/or femtocells in the form of a neighbor list, which can identify base stations and/or femtocells within a coverage area and/or sector of an associated base station and/or femtocell. Unfortunately, conventional techniques cannot adequately account for tens, hundreds, thousands, etc. of femtocells included within the coverage area and/or sector using the neighbor list because each item, or reference, included in the neighbor list only corresponds to one base station and/or access point.

In contrast, reselection component <b>620</b> can facilitate idle mode reselection based on at least one neighbor list entry, e.g., virtual neighbor object, which can refer to multiple base stations and/or femto APs. Referring to the example above, and referencing <figref idref="DRAWINGS">FIG. 7</figref>, reselection component <b>620</b> can facilitate idle mode reselection between a base station (not shown) and one of the femtocells <b>225</b> based on, at least in part, virtual neighbor object <b>710</b>. Further, as described below, reselection component <b>620</b> can facilitate such reselection, at least in part, based on one or more access restrictions.

<figref idref="DRAWINGS">FIG. 8</figref> illustrates a virtual neighbor object <b>800</b>, in accordance with an embodiment. Virtual neighbor object <b>800</b> can include a channel number <b>810</b> and/or a scrambling code <b>820</b> (as illustrated, scrambling code <b>820</b> is included). Channel number <b>810</b> can be associated with a control channel and/or a broadcast channel of an access point, e.g., base station, femtocell, etc., and used by a mobile wireless device to monitor and/or communicate with the access point, e.g., for servicing an incoming/outgoing call in the active mode. Scrambling code <b>820</b> can be used for scrambling transmissions from the access point, e.g., for scrambling Primary Common Control Physical Channel (P-CCPCH) transmissions from node B <b>540</b> of UMTS wireless environment <b>500</b>. In one embodiment, reselection component <b>620</b> of system <b>600</b> can be configured to facilitate idle mode reselection between wireless access points, e.g., between a base station and a femto AP, based on, at least in part, channel number <b>810</b> and/or scrambling code <b>820</b>.

For example, in an example wireless environment <b>900</b> illustrated by <figref idref="DRAWINGS">FIG. 9</figref>, different virtual neighbor objects (<b>905</b>, <b>910</b>, <b>915</b>, <b>920</b>) comprising different combinations of channel numbers <b>810</b> and scrambling codes <b>820</b> can be associated with different femtocells (<b>907</b>, <b>912</b>, <b>917</b>, <b>922</b>). Reselection component <b>620</b> can be configured to facilitate idle mode reselection from base station <b>210</b> to femtocell <b>917</b> based on, at least in part, a channel number <b>810</b> and a scrambling code <b>820</b> associated with virtual neighbor object <b>915</b>.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates a reselection component <b>1000</b> that includes an access restriction component <b>1010</b>, in accordance with an embodiment. Access restriction component <b>1010</b> can be configured to define at least one access restriction associated with at least one wireless access point of the at least two wireless access points discussed in relation to system <b>600</b> above. For example, the at least one access restriction can comprise an identification (ID) associated with a mobile wireless device affected by the idle mode reselection, e.g., a user ID associated with the mobile wireless device. In another aspect, the at least one access restriction can be associated with an ACL (see above). In yet another aspect, the at least one access restriction can relate to one or more signals associated with communication between a mobile wireless device and one or more femtocells. For example, the at least one access restriction can relate to signal quality of the one or more signals.

In an aspect, the at least one access restriction can prevent access to the wireless access point of the at least two wireless access points if the user ID is not validated. In another aspect, reselection component <b>1000</b> can be configured to facilitate idle mode reselection between the wireless access point and the other wireless access point based on, at least in part, the channel number, the scrambling code, and the at least one access restriction.

For example, in an example wireless environment <b>1100</b> illustrated by <figref idref="DRAWINGS">FIG. 11</figref>, two femtocells (<b>1112</b> and <b>1117</b>) are associated with, or referenced by, virtual neighbor object <b>1115</b>, which includes a channel number and a scrambling code. Further, femtocell <b>1112</b> can be associated with at least one access restriction defined by access restriction component <b>1010</b>. Reselection component <b>620</b> can be configured to facilitate idle mode reselection from base station <b>210</b> to femtocell <b>1112</b> based on, at least in part, the channel number and scrambling code of virtual neighbor object <b>1115</b>, and the at least one access restriction associated with femtocell <b>1112</b>.

<figref idref="DRAWINGS">FIG. 12</figref> illustrates a virtual neighbor component <b>1200</b> including a neighbor list component <b>1210</b> and a provisioning component <b>1220</b>, in accordance with an embodiment. In relation to the discussion regarding <figref idref="DRAWINGS">FIG. 6</figref> above, neighbor list component <b>1210</b> can be configured to construct a neighbor list (see <figref idref="DRAWINGS">FIG. 13</figref>) comprising the at least one virtual neighbor object. As illustrated by <figref idref="DRAWINGS">FIG. 13</figref>, in one embodiment, neighbor list <b>1300</b> can include six distinct virtual neighbor objects (<b>1310</b>, <b>1320</b>, <b>1330</b>, <b>1340</b>, <b>1350</b>, and <b>1360</b>). Further, the at least one virtual neighbor object can include a channel number and a scrambling code (not shown). Moreover, provisioning component <b>1220</b> can be configured to transmit the neighbor list from the other wireless access point to a mobile wireless device, e.g., mobile wireless device <b>220</b>_A, mobile wireless device <b>220</b>_B. Reselection component <b>1210</b> can be configured to facilitate idle mode reselection between the wireless access point and the other wireless access point, via the mobile wireless device, based on, at least in part, the neighbor list, e.g., based on the channel number and the scrambling code associated with a virtual neighbor object included in the neighbor list.

For example, in an example wireless environment <b>1400</b> illustrated by <figref idref="DRAWINGS">FIG. 14</figref>, six different virtual neighbor objects (<b>1405</b>, <b>1410</b>, <b>1415</b>, <b>1420</b>, <b>1425</b>, <b>1430</b>) comprising different combinations of channel numbers <b>810</b> and scrambling codes <b>820</b> can be associated with different femtocells (<b>1407</b>, <b>1412</b>, <b>1417</b>, <b>1422</b>, <b>1427</b>, <b>1432</b>). Neighbor list component <b>1210</b> can be configured to construct a neighbor list (not shown) that includes the six different virtual neighbor objects (<b>1405</b>, <b>1410</b>, <b>1415</b>, <b>1420</b>, <b>1425</b>, and <b>1430</b>). Provisioning component <b>1220</b> can be configured to transmit the neighbor list from base station <b>210</b> to mobile wireless device <b>220</b>_A, via wireless link <b>215</b>. Further, reselection component <b>1210</b> can be configured to facilitate idle mode reselection between femtocell <b>1417</b> and base station <b>210</b>, via mobile wireless device <b>220</b>_A, based on, at least in part, virtual neighbor object <b>1415</b> included in the neighbor list. It should be appreciated that neighbor list component can be configured to construct a neighbor list that includes more/less virtual neighbor objects. Moreover, as described below, it should be appreciated that at least one virtual neighbor object included in the neighbor list can reference more than one femtocell.

<figref idref="DRAWINGS">FIG. 15</figref> illustrates a system <b>1500</b> that includes virtual neighbor component <b>1200</b> and an access component <b>1510</b>, in accordance with an embodiment. In relation to the discussion regarding <figref idref="DRAWINGS">FIGS. 6 and 12</figref> above, access component <b>1510</b> can be configured to assign at least one access control parameter to at least one access point of the at least two wireless access points. In one aspect, the at least one access control parameter can relate to an ID associated with mobile wireless device <b>220</b>_A, e.g., the at least one access control parameter can relate to an account associated with a wireless service provider. In another aspect, the at least one access control parameter can be associated with an ACL (see above). In yet another aspect, the at least one access control parameter can relate to one or more signals associated with communication between mobile wireless device <b>220</b>_Aand one or more femtocells, e.g., the at least one access control parameter can relate to signal quality of the one or more signals.

Further, reselection component <b>1520</b> can be configured to facilitate idle mode reselection between the wireless access point and the other wireless access point based on, at least in part, the channel number, the scrambling code, and the at least one access control parameter. For example, in an example wireless environment <b>1600</b> illustrated by <figref idref="DRAWINGS">FIG. 16</figref>, six distinct virtual neighbor objects (<b>1605</b>, <b>1610</b>, <b>1615</b>, <b>1620</b>, <b>1625</b>, <b>1630</b>) comprising different combinations of channel numbers <b>810</b> and scrambling codes <b>820</b> can be associated with different femtocells, e.g., <b>1607</b>, <b>1612</b>, etc. Neighbor list component <b>1210</b> can be configured to construct a neighbor list (not shown) that includes the six distinct virtual neighbor objects. Provisioning component <b>1220</b> can be configured to transmit the neighbor list from base station <b>210</b> to mobile wireless device <b>220</b>_A, via wireless link <b>215</b>.

As illustrated by <figref idref="DRAWINGS">FIG. 16</figref>, virtual neighbor object <b>1610</b> is associated with two femtocells (<b>1612</b> and <b>1613</b>). Moreover, virtual neighbor object <b>1615</b> is associated with two femtocells (<b>1617</b> and <b>1618</b>). Accordingly, reselection component <b>1520</b> can be configured to facilitate idle mode reselection between base station <b>210</b> and femtocell <b>1617</b>, via mobile wireless device <b>220</b>_A, based on, at least in part, channel number <b>810</b>, scrambling code <b>820</b>, and at least one access control parameter assigned to one or more femtocells within wireless environment <b>1600</b> via access component <b>1510</b>, e.g., at least one access control parameter assigned to femtocell <b>1617</b>.

<figref idref="DRAWINGS">FIG. 17</figref> illustrates a system <b>1700</b> that includes a femto neighbor list component <b>1710</b> and a transition component <b>1720</b>, in accordance with an embodiment. Femto neighbor list component <b>1710</b> can be configured to reference at least two femtocells associated with macro cells using a virtual neighbor object of a plurality of virtual neighbor objects. Further, femto neighbor list component <b>1710</b> can be configured to build a femtocell neighbor list comprising the plurality of virtual neighbor objects. Transition component <b>1720</b> can be configured to transmit the femtocell neighbor list from base stations associated with the macro cells to mobile wireless devices. Moreover, transition component <b>1720</b> can be configured to facilitate selection of a femtocell of the at least two femtocells via at least one of the mobile wireless devices based on, at least in part, the femtocell neighbor list.

In an example wireless environment <b>1800</b> illustrated by <figref idref="DRAWINGS">FIG. 18</figref>, femto neighbor list component <b>1710</b> references femtocells <b>1810</b> and <b>1840</b> via virtual neighbor object <b>1805</b>; references femtocells <b>1820</b>, <b>1850</b>, and <b>1860</b> via virtual neighbor object <b>1815</b>; and references femtocell <b>1830</b> via virtual neighbor object <b>1825</b>. Femto neighbor list component <b>1710</b> can include virtual neighbor objects <b>1805</b>, <b>1815</b>, and <b>1825</b> in a femto neighbor list (not shown). Transition component <b>1720</b> can transmit the femtocell neighbor list from base stations <b>210</b> to mobile wireless devices <b>220</b>_Aand <b>220</b>_B, which can facilitate reselection to femtocells <b>1820</b> and <b>1850</b> from base stations <b>210</b> via mobile wireless devices <b>220</b>_Aand <b>220</b>_B, respectively.

As described above, a mobile wireless device, e.g., mobile wireless device <b>220</b>_A/<b>220</b>_B, can monitor one or more control and/or broadcast channels of base stations for selecting one of the base stations to service an incoming/outgoing call in active mode. Accordingly, in one aspect, transition component <b>1720</b> can transmit the femtocell neighbor list from base stations <b>210</b> to mobile wireless devices <b>220</b>_Aand <b>220</b>_Bvia at least one of a System Information Block (SIB) message or a quater message.

A SIB message, or measurement control message, can be transmitted from a base station, e.g., node B <b>540</b>, associated with a UTRAN, e.g., UTRAN <b>520</b>. A quater message can contain measurement control information transmitted from a base station, e.g., BTS <b>440</b>, associated with a BSS, e.g., BSS <b>420</b>. The SIB and/or quater message can describe parameters of an associated base station, which a mobile wireless device can use for monitoring the base station, e.g., to determine base station signal quality. Mobile wireless devices <b>220</b>_Aand <b>220</b>_Bcan receive the SIB and/or quater message and extract the femtocell neighbor list from the SIB and/or quater message. Each mobile wireless device <b>220</b>_A/<b>220</b>_Bcan attempt to monitor, or scan, femtocells associated with virtual neighbor object entries included in the femtocell neighbor list, e.g., via channel numbers and scrambling codes associated with each virtual neighbor object entry.

As illustrated by <figref idref="DRAWINGS">FIG. 18</figref>, one or more virtual neighbor objects included in a femtocell neighbor list can reference at least two femtocells, e.g., VNO <b>1815</b> included in a femtocell neighbor list transmitted to mobile wireless device <b>220</b>_B—VNO referencing femtocells <b>1850</b> and <b>1860</b>. Accordingly, in an aspect, one or more access control lists can be associated with one or more of the at least two femtocells described above regarding <figref idref="DRAWINGS">FIG. 17</figref>. Moreover, and referring to the discussion above regarding <figref idref="DRAWINGS">FIG. 17</figref>, transition component <b>1720</b> can be configured to facilitate selection of a femtocell of the at least two femtocells via at least one of the mobile wireless devices based on, at least in part, the femtocell neighbor list and one or more access control lists, the one or more access control lists associated with one or more of the at least two femtocells.

For example, an access control list can be associated with femtocells <b>1850</b> and <b>1860</b>, and transition component <b>1720</b> can be configured to facilitate selection of femtocell <b>1850</b> via mobile wireless device <b>220</b>_Bbased on an access control list related to femtocell <b>1850</b>, e.g., the access control list granting access based on one or more parameters associated with mobile wireless device <b>220</b>_B, such as account information, mobile wireless device identification, etc.

It should be appreciated that although virtual neighbor object <b>1805</b> references two femtocells (<b>1810</b> and <b>1840</b>) associated with different macro cells <b>205</b>, a femtocell neighbor list transmitted to mobile wireless device <b>220</b>_Adoes not include a virtual neighbor object that references at least two femtocells located within macro cell <b>205</b> associated with mobile wireless device <b>220</b>_A. Accordingly, transition component <b>1720</b> can facilitate reselection to femtocell <b>1810</b> from base station <b>210</b> via mobile wireless device <b>220</b>_Awithout considering access control list restrictions.

<figref idref="DRAWINGS">FIGS. 19-23</figref> illustrate methodologies in accordance with the disclosed subject matter. For simplicity of explanation, the methodologies are depicted and described as a series of acts. It is to be understood and appreciated that the subject innovation is not limited by the acts illustrated and/or by the order of acts. For example, acts can occur in various orders and/or concurrently, and with other acts not presented or described herein. Furthermore, not all illustrated acts may be required to implement the methodologies in accordance with the disclosed subject matter. In addition, those skilled in the art will understand and appreciate that the methodologies could alternatively be represented as a series of interrelated states via a state diagram or events. Additionally, it should be further appreciated that the methodologies disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methodologies to computers. The term article of manufacture, as used herein, is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.

Referring now to <figref idref="DRAWINGS">FIGS. 19 and 20</figref>, processes <b>1900</b> and <b>2000</b> that provide for effective idle mode reselection in a wireless environment are illustrated, in accordance with an embodiment. At <b>1910</b>, at least one virtual neighbor object comprising a channel number and a scrambling code can be built/created. In an aspect, the channel number and the scrambling code can be associated with one or more femtocells located within a coverage area, or macro cell, of a base station. At <b>1920</b>, the at least one virtual neighbor object can reference at least two femtocells, e.g., within the macro cell and/or across different macro cells. A message including the at least one virtual neighbor object, e.g., comprising neighbor list, can be transmitted from a base station to a mobile wireless device at <b>1930</b>. In an aspect, the message can include a System Information Block (SIB) message or a quater message (see above). Further, an idle mode reselection can be facilitated between the base station and one of the at least two femtocells via the mobile wireless device, based on, at least in part, the channel number and the scrambling code associated with the femtocell.

Regarding example process <b>2000</b> illustrated by <figref idref="DRAWINGS">FIG. 20</figref>, one or more access restrictions can be assigned to one or more femtocells at <b>2010</b>. For example, the one or more access restrictions can comprise an ID associated with a mobile wireless device that is enabled access to a femtocell, e.g., based on the ID matching the one or more access restrictions. In an aspect, the ID can include a user ID associated with the mobile wireless device, or an account number affiliated with a wireless service provider. At <b>2020</b>, reselection component can facilitate idle mode reselection between the base station and one of the at least two femtocells via the mobile wireless device, based on, at least in part, the channel number, the scrambling code, and the one or more access restrictions. Returning now to the example above, the one or more access restrictions can prevent access/prevent reselection to the femtocell if the user ID and/or account number associated with the mobile wireless device is not validated.

<figref idref="DRAWINGS">FIG. 21</figref> illustrates a process <b>2100</b> that provides for effective idle mode reselection in a wireless environment, in accordance with an embodiment. At <b>2110</b>, at least two femtocells of different macro cells—the macro cells associated with a UMTS network and/or a GSM network—can be referenced by a virtual neighbor object of a plurality of virtual neighbor objects. A femtocell neighbor list can be constructed to include the plurality of virtual neighbor objects at <b>2120</b>. At <b>2130</b>, the femtocell neighbor list can be transmitted from base stations of the different macro cells to mobile wireless devices. Further, reselection from one of the base stations to a femtocell of the at least two femtocells can be performed via one of the mobile wireless devices at <b>2130</b>.

Referring now to <figref idref="DRAWINGS">FIG. 22</figref>, a process <b>2200</b> associated with a mobile device is illustrated, in accordance with an embodiment. At <b>2210</b>, a mobile wireless device can receive a femtocell neighbor list transmitted from a base station of a macro cell sector. The mobile wireless device can scan femtocell channels at <b>2220</b>—each channel associated with a channel number and a scrambling code related to a virtual neighbor object included in the femtocell neighbor list. At <b>2230</b>, the mobile wireless device can reselect to a femtocell associated with the scanned femtocell channels based on, at least in part, a channel number, a scrambling code, and an access control list related to the femtocell. The access control list can grant access to the femtocell based on one or more parameters associated with the mobile wireless device, such as account information, mobile wireless device identification, etc.

<figref idref="DRAWINGS">FIG. 23</figref> illustrates another process (<b>2300</b>) associated with a mobile device, in accordance with an embodiment. A mobile wireless device, e.g., UE, can receive a femtocell neighbor list including virtual neighbor objects transmitted from a base station at <b>2310</b>. At <b>2320</b>, the mobile wireless device can determine, for each virtual neighbor object included in the femtocell neighbor list, whether the virtual neighbor object references two or more femtocells—the two or more femtocells communicating with/sending information to the mobile wireless device. If it is determined that the virtual neighbor object does not reference two or more femtocells, flow continues to <b>2340</b>, at which the mobile wireless device can scan a femtocell associated with a channel number and scrambling code included in the virtual neighbor object, e.g., to evaluate whether to select the femtocell to service an active communication.

If it is determined at <b>2320</b> that the virtual neighbor object references two or more femtocells communicating with/sending information to the mobile wireless device, then it can be determined at <b>2330</b>, e.g., via a femtocell associated with the virtual neighbor object, whether one or more access parameters related to the femtocell correlate with the mobile wireless device. If it is determined that the one or more access parameters correlate with the mobile wireless device, then flow continues to <b>2340</b> (see above); however, if it is determined that the one or more access parameters do not correlate with the mobile wireless device, then flow returns to <b>2320</b>, at which the mobile wireless device can determine whether another virtual neighbor object included in the femtocell neighbor list references two or more femtocells.

<figref idref="DRAWINGS">FIG. 24</figref> illustrates a block diagram of a mobile wireless device <b>2400</b>, in accordance with an embodiment. Mobile wireless device <b>2400</b> can perform the acts described above related to, e.g., mobile wireless devices <b>220</b>_Aand <b>220</b>_B; mobile stations <b>450</b>_Aand <b>450</b>_B; user equipment <b>550</b>_Aand <b>550</b>_B. For example, mobile wireless device <b>2400</b> can perform acts described with respect to <figref idref="DRAWINGS">FIGS. 22 and 23</figref> via processor(s) <b>2410</b>. Processors(s) <b>2410</b> can perform such acts within the mobile wireless device utilizing, e.g., memory device(s) <b>2420</b>.

To provide further context for various aspects of the disclosed subject matter, <figref idref="DRAWINGS">FIGS. 25 and 26</figref> illustrate, respectively, a block diagram of an embodiment <b>2500</b> of a femtocell access point <b>2505</b> that can enable or exploit features and/or aspects of the disclosed subject matter; and a wireless network environment <b>2600</b> that includes femto and macro network platforms, which can enable aspects or feature of a mobile network platform as described herein, and utilize femto APs that exploit aspects of the subject innovation in accordance with various aspects of the subject specification. In embodiment <b>2500</b>, femto AP <b>2505</b> can receive and transmit signal(s) from and to wireless devices, e.g., femto access points, access terminals, wireless ports and routers, or the like, through a set of antennas <b>2520</b>₁-<b>2520</b>_N(N is a positive integer). Antennas <b>2520</b>₁-<b>2520</b>_Nare a part of communication platform <b>2515</b>, which comprises electronic components and associated circuitry that provides for processing and manipulation of received signal(s) and signal(s) to be transmitted.

In an aspect, communication platform <b>2515</b> includes a receiver/transmitter <b>2516</b> that can convert analog signals to digital signals upon reception of the analog signals, and convert digital signals to analog signals upon transmission. In addition, receiver/transmitter <b>2516</b> can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation. Coupled to receiver/transmitter <b>2516</b> is a multiplexer/demultiplexer <b>2517</b> that facilitates manipulation of signal in time and frequency space. Electronic component <b>2517</b> can multiplex information (data/traffic and control/signaling) according to various multiplexing schemes such as time division multiplexing (TDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), code division multiplexing (CDM), space division multiplexing (SDM). In addition, mux/demux component <b>2517</b> can scramble and spread information (e.g., codes) according to substantially any code known in the art, e.g., Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, etc. A modulator/demodulator <b>2518</b> is also a part of communication platform <b>2515</b>, and can modulate information according to multiple modulation techniques, such as frequency modulation, amplitude modulation, e.g., M-ary quadrature amplitude modulation (QAM), with M a positive integer), phase-shift keying (PSK), etc.

Femto access point <b>2505</b> also includes a processor <b>2535</b> configured to confer, at least in part, functionality to substantially any electronic component in femto AP <b>2505</b>. In particular, processor <b>2535</b> can facilitate configuration of femto AP <b>2505</b> via system <b>600</b>, and one or more component therein. Additionally, femto AP <b>2505</b> includes display interface <b>2512</b>, which can display functions that control functionality of femto AP <b>2505</b>, or reveal operation conditions thereof. In addition, display interface <b>2512</b> can include a screen to convey information to an end user. In an aspect, display interface <b>2512</b> can be a liquid crystal display (LCD), a plasma panel, a monolithic thin-film based electrochromic display, and so on. Moreover, display interface can also include a component, e.g., speaker that facilitates communication of aural indicia, which can also be employed in connection with messages that convey operational instructions to an end user. Display interface <b>2512</b> also facilitates data entry e.g., through a linked keypad or via touch gestures, which can facilitated femto AP <b>2505</b> to receive external commands, e.g., restart operation.

Broadband network interface facilitates connection of femto AP <b>2505</b> to femto network via access point backhaul link(s) <b>253</b> (not shown in <figref idref="DRAWINGS">FIG. 25</figref>), which enable incoming and outgoing data flow. Broadband network interface <b>2514</b> can be internal or external to femto AP <b>2505</b>, and it can utilize display interface <b>2512</b> for end-user interaction and status information delivery.

Processor <b>2535</b> also is functionally connected to communication platform <b>2515</b> and can facilitate operations on data, e.g., symbols, bits, or chips, for multiplexing/demultiplexing, such as effecting direct and inverse fast Fourier transforms, selection of modulation rates, selection of data packet formats, inter-packet times, etc. Moreover, processor <b>2535</b> is functionally connected, via data, system, or address bus <b>2511</b>, to display interface <b>2512</b> and broadband network interface <b>2514</b> to confer, at least in part functionality to each of such components.

In femto AP <b>2505</b>, memory <b>2545</b> can retain location and/or home macro sector identifier(s); access list(s) that authorize access to wireless coverage through femto <b>2505</b>; sector intelligence that includes ranking of macro sectors in the macro wireless environment of femto AP <b>2505</b>, radio link quality and strength associated therewith, or the like. Memory <b>2545</b> also can store data structures, code instructions and program modules, system or device information, code sequences for scrambling, spreading and pilot transmission, femto AP floor plan configuration, and so on. Processor <b>2535</b> is coupled, e.g., via a memory bus, to memory <b>2545</b> in order to store and retrieve information necessary to operate and/or confer functionality to the components, platform, and interfaces that reside within femto access point <b>2505</b>.

Now referring to <figref idref="DRAWINGS">FIG. 26</figref>, wireless communication environment <b>2600</b> includes two wireless network platforms: (1) macro network platform <b>2610</b> that serves, or facilitates communication with, user equipment (UE) <b>2675</b>, e.g., mobile wireless device <b>2400</b>, via a macro radio access network (RAN) <b>2670</b>; and (2) femto network platform <b>2680</b>, which can provide communication with UE <b>2675</b> through a femto RAN <b>2690</b>, which is linked to femto network platform <b>2680</b> via backhaul pipe(s) <b>2685</b>, e.g., access point backhaul link(s) <b>253</b>. Moreover, wireless communication environment <b>2600</b> includes virtual neighbor component <b>260</b>. It should be appreciated that wireless communication environment <b>2600</b> can include aspects and/or components of the subject innovation discussed above regarding, e.g., system <b>600</b>, virtual neighbor component <b>1200</b>, system <b>1500</b>, system <b>1700</b>, etc. Moreover, such aspects and/or components can be located/included within one or more components/elements, e.g., hardware, software, etc., of wireless communication environment <b>2600</b>, e.g., macro network platform <b>2610</b>, radio network <b>2690</b>, and/or mobile device <b>2695</b>.

It should also be appreciated that in cellular wireless technologies, e.g., 3GPP UMTS, HSPA, 3GPP LTE™, 3GPP2 UMB, GSM, etc., macro network platform <b>2610</b> is embodied in a core network. It should also be appreciated that macro network platform <b>2610</b> typically hands off UE <b>2675</b> to femto network platform <b>2610</b> once UE <b>2675</b> attaches, e.g., through macro-to-femto handover, to femto RAN <b>2690</b>, which includes a set of deployed femto APs, e.g., femto AP <b>230</b>, which can operate in accordance with aspects described herein.

It is noted that RAN includes base station(s), or access point(s), and its associated electronic circuitry and deployment site(s), in addition to a wireless radio link operated in accordance with the base station(s). Accordingly, macro RAN <b>2670</b> can comprise various coverage cells like macro cell <b>205</b>, while femto RAN <b>2690</b> can comprise multiple femtocell access points such as femto AP <b>230</b>. Deployment density in femto RAN <b>2690</b> is substantially higher than in macro RAN <b>2670</b>.

Generally, both macro and femto network platforms <b>2610</b> and <b>2680</b> include components, e.g., nodes, gateways, interfaces, servers, or platforms, that facilitate both packet-switched (PS), e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM), and circuit-switched (CS) traffic, e.g., voice and data, and control generation for networked wireless communication. In an aspect of the subject innovation, macro network platform <b>2610</b> includes CS gateway node(s) <b>2612</b> which can interface CS traffic received from legacy networks like telephony network(s) <b>2640</b>, e.g., public switched telephone network (PSTN), or public land mobile network (PLMN), or a SS7 network <b>2660</b>. Circuit switched gateway <b>2612</b> can authorize and authenticate traffic, e.g., voice, arising from such networks. Additionally, CS gateway <b>2612</b> can access mobility, or roaming, data generated through SS7 network <b>2660</b>; for instance, mobility data stored in a VLR, which can reside in memory <b>2630</b>. Moreover, CS gateway node(s) <b>2612</b> interfaces CS-based traffic and signaling and gateway node(s) <b>2618</b>. As an example, in a 3GPP UMTS network, PS gateway node(s) <b>2618</b> can be embodied in gateway GPRS support node(s) (GGSN).

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) <b>2618</b> can authorize and authenticate PS-based data sessions with served, e.g., through macro RAN, wireless devices. Data sessions can include traffic exchange with networks external to the macro network platform <b>2610</b>, like wide area network(s) (WANs) <b>2650</b>; enterprise networks (NWs) <b>2670</b>, e.g., enhanced 911, or service NW(s) <b>2680</b> like IP multimedia subsystem (IMS). It should be appreciated that local area network(s) (LANs), which may be a part of enterprise NW(s), can also be interfaced with macro network platform <b>2610</b> through PS gateway node(s) <b>2618</b>. Packet-switched gateway node(s) <b>2618</b> generates packet data contexts when a data session is established. To that end, in an aspect, PS gateway node(s) <b>2618</b> can include a tunnel interface, e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown), which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks. It should be further appreciated that the packetized communication can include multiple flows that can be generated through server(s) <b>2614</b>. It is to be noted that in 3GPP UMTS network(s), PS gateway node(s) <b>2618</b> (e.g., GGSN) and tunnel interface (e.g., TTG) comprise a packet data gateway (PDG).

Macro network platform <b>2610</b> also includes serving node(s) <b>2616</b> that convey the various packetized flows of information, or data streams, received through PS gateway node(s) <b>2618</b>. As an example, in a 3GPP UMTS network, serving node(s) can be embodied in serving GPRS support node(s) (SGSN).

As indicated above, server(s) <b>2614</b> in macro network platform <b>2610</b> can execute numerous applications, e.g., location services, online gaming, wireless banking, wireless device management, etc. that generate multiple disparate packetized data streams or flows, and manage such flows, e.g., schedule, queue, format. Such application(s), for example can include add-on features to standard services provided by macro network platform <b>2610</b>. Data streams can be conveyed to PS gateway node(s) <b>2618</b> for authorization/authentication and initiation of a data session, and to serving node(s) <b>2616</b> for communication thereafter. Server(s) <b>2614</b> can also effect security, e.g., implement one or more firewalls, of macro network platform <b>2610</b> to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) <b>2612</b> and PS gateway node(s) <b>2618</b> can enact. Moreover, server(s) <b>2614</b> can provision services from external network(s), e.g., WAN <b>2650</b>, or Global Positioning System (GPS) network(s), which can be a part of enterprise NW(s) <b>2680</b>. It is to be noted that server(s) <b>2614</b> can include one or more processors configured to confer at least in part the functionality of macro network platform <b>2610</b>. To that end, the one or more processors can execute code instructions stored in memory <b>2630</b>, for example.

In example wireless environment <b>2600</b>, memory <b>2630</b> stores information related to operation of macro network platform <b>2610</b>. Information can include business data associated with subscribers; market plans and strategies, e.g., promotional campaigns, business partnerships; operational data for mobile devices served through macro network platform; service and privacy policies; end-user service logs for law enforcement; and so forth. Memory <b>2630</b> can also store information from at least one of telephony network(s) <b>2640</b>, WAN <b>2650</b>, SS7 network <b>2660</b>, enterprise NW(s) <b>2670</b>, or service NW(s) <b>2680</b>.

Regarding femto network platform <b>2680</b>, it can include femto gateway node(s) <b>2684</b>, which have substantially the same functionality as PS gateway node(s) <b>2618</b>. Additionally, femto gateway node(s) <b>2684</b> can also include substantially all functionality of serving node(s) <b>2616</b>. Disparate gateway node(s) <b>2684</b> can control or operate disparate sets of deployed femto APs, which can be a part of femto RAN <b>2690</b>. In an aspect of the subject innovation, femto gateway node(s) <b>2684</b> can aggregate operational data received from deployed femto APs.

Memory <b>2686</b> can retain additional information relevant to operation of the various components of femto network platform <b>2680</b>. For example, operational information that can be stored in memory <b>2686</b> can comprise, but is not limited to, subscriber intelligence; contracted services; maintenance and service records; femtocell configuration, e.g., devices served through femto RAN <b>2690</b>, authorized subscribers associated with one or more deployed femto APs; service policies and specifications; privacy policies; add-on features; so forth.

Server(s) <b>2682</b> have substantially the same functionality as described in connection with server(s) <b>2614</b>. In an aspect, server(s) <b>2682</b> can execute multiple application(s) that provide service, e.g., voice and data, to wireless devices served through femto RAN <b>2690</b>. Server(s) <b>2682</b> can also provide security features to femto network platform. In addition, server(s) <b>2682</b> can manage, e.g., schedule, queue, format, substantially all packetized flows, e.g., IP-based, frame relay-based, ATM-based, it generates in addition to data received from macro network platform <b>2610</b>. Furthermore, server(s) <b>2682</b> can effect provisioning of femtocell service, and effect operations and maintenance. It is to be noted that server(s) <b>2682</b> can include one or more processors configured to provide at least in part the functionality of femto network platform <b>2680</b>. To that end, the one or more processors can execute code instructions stored in memory <b>2686</b>, for example.

As it employed in the subject specification, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile wireless devices. A processor may also be implemented as a combination of computing processing units.

In the subject specification, terms such as “store,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory,” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, for example, which can be included in memory devices <b>2420</b>, memory <b>2545</b>, memory <b>2630</b>, and memory <b>2686</b>, can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

In order to provide a context for the various aspects of the disclosed subject matter, <figref idref="DRAWINGS">FIGS. 27 and 28</figref>, as well as the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter may be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the subject innovation also may be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Moreover, those skilled in the art will appreciate that the inventive systems may be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, watch), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

With reference to <figref idref="DRAWINGS">FIG. 27</figref>, a block diagram of a computer <b>2700</b> operable to execute the disclosed systems and methods, in accordance with an embodiment, includes a computer <b>2712</b>. The computer <b>2712</b> includes a processing unit <b>2714</b>, a system memory <b>2716</b>, and a system bus <b>2718</b>. The system bus <b>2718</b> couples system components including, but not limited to, the system memory <b>2716</b> to the processing unit <b>2714</b>. The processing unit <b>2714</b> can be any of various available processors. Dual microprocessors and other multiprocessor architectures also can be employed as the processing unit <b>2714</b>.

The system bus <b>2718</b> can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MSA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), Firewire (IEEE 1194), and Small Computer Systems Interface (SCSI).

The system memory <b>2716</b> includes volatile memory <b>2720</b> and nonvolatile memory <b>2722</b>. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer <b>2712</b>, such as during start-up, is stored in nonvolatile memory <b>2722</b>. By way of illustration, and not limitation, nonvolatile memory <b>2722</b> can include ROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory <b>2720</b> includes RAM, which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as SRAM, dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM).

Computer <b>2712</b> also includes removable/non-removable, volatile/nonvolatile computer storage media. <figref idref="DRAWINGS">FIG. 27</figref> illustrates, for example, disk storage <b>2724</b>. Disk storage <b>2724</b> includes, but is not limited to, devices like a magnetic disk drive, floppy disk drive, tape drive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memory stick. In addition, disk storage <b>2724</b> can include storage media separately or in combination with other storage media including, but not limited to, an optical disk drive such as a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive (DVD-ROM). To facilitate connection of the disk storage devices <b>2724</b> to the system bus <b>2718</b>, a removable or non-removable interface is typically used, such as interface <b>2726</b>.

It is to be appreciated that <figref idref="DRAWINGS">FIG. 27</figref> describes software that acts as an intermediary between users and the basic computer resources described in the suitable operating environment <b>2700</b>. Such software includes an operating system <b>2728</b>. Operating system <b>2728</b>, which can be stored on disk storage <b>2724</b>, acts to control and allocate resources of the computer system <b>2712</b>. System applications <b>2730</b> take advantage of the management of resources by operating system <b>2728</b> through program modules <b>2732</b> and program data <b>2734</b> stored either in system memory <b>2716</b> or on disk storage <b>2724</b>. It is to be appreciated that the disclosed subject matter can be implemented with various operating systems or combinations of operating systems.

A user enters commands or information into the computer <b>2711</b> through input device(s) <b>2736</b>. Input devices <b>2736</b> include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processing unit <b>2714</b> through the system bus <b>2718</b> via interface port(s) <b>2738</b>. Interface port(s) <b>2738</b> include, for example, a serial port, a parallel port, a game port, and a universal serial bus (USB). Output device(s) <b>2740</b> use some of the same type of ports as input device(s) <b>2736</b>.

Thus, for example, a USB port may be used to provide input to computer <b>2712</b> and to output information from computer <b>2712</b> to an output device <b>2740</b>. Output adapter <b>2742</b> is provided to illustrate that there are some output devices <b>2740</b> like monitors, speakers, and printers, among other output devices <b>2740</b>, which use special adapters. The output adapters <b>2742</b> include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device <b>2740</b> and the system bus <b>2718</b>. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s) <b>2744</b>.

Computer <b>2712</b> can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s) <b>2744</b>. The remote computer(s) <b>2744</b> can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer <b>2712</b>.

For purposes of brevity, only a memory storage device <b>2746</b> is illustrated with remote computer(s) <b>2744</b>. Remote computer(s) <b>2744</b> is logically connected to computer <b>2712</b> through a network interface <b>2748</b> and then physically connected via communication connection <b>2750</b>. Network interface <b>2748</b> encompasses wire and/or wireless communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ring and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).

Communication connection(s) <b>2750</b> refer(s) to the hardware/software employed to connect the network interface <b>2748</b> to the bus <b>2718</b>. While communication connection <b>2750</b> is shown for illustrative clarity inside computer <b>2712</b>, it can also be external to computer <b>2712</b>. The hardware/software for connection to the network interface <b>2748</b> can include, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.

<figref idref="DRAWINGS">FIG. 28</figref> illustrates a schematic block diagram of an exemplary computing environment <b>2830</b>, in accordance with an embodiment. The system <b>2800</b> includes one or more client(s) <b>2810</b>. The client(s) <b>2810</b> can be hardware and/or software (e.g., threads, processes, computing devices). The system <b>2800</b> also includes one or more server(s) <b>2820</b>. Thus, system <b>2800</b> can correspond to a two-tier client server model or a multi-tier model (e.g., client, middle tier server, data server), amongst other models. The server(s) <b>2820</b> can also be hardware and/or software (e.g., threads, processes, computing devices). The servers <b>2820</b> can house threads to perform transformations by employing the subject innovation, for example. One possible communication between a client <b>2810</b> and a server <b>2820</b> may be in the form of a data packet transmitted between two or more computer processes.

The system <b>2800</b> includes a communication framework <b>2830</b> that can be employed to facilitate communications between the client(s) <b>2810</b> and the server(s) <b>2820</b>. The client(s) <b>2810</b> are operatively connected to one or more client data store(s) <b>2840</b> that can be employed to store information local to the client(s) <b>2810</b>. Similarly, the server(s) <b>2820</b> are operatively connected to one or more server data store(s) <b>2850</b> that can be employed to store information local to the servers <b>2820</b>.

The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiments for performing the same, similar, alternative or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.