Service continuity during local breakout in a femtocell

A system and methodology that facilitates service continuity when a user equipment (UE), employing local breakout mechanisms at a femto access point (FAP) for a communication session, moves out of the femto coverage area is provided. In particular, a network change detection component can be employed to detect when the UE, attached to the FAP, changes its connection from the femto network to the macro network. Further, an active communication session can exist between the UE and a device/service/application on a local Area network (LAN) connected to a FAP, and/or the Internet, which utilizes local breakout at the FAP. When the UE moves out of the femto network, a context management component can be employed to seamlessly resume the communication session, via the macro network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/117,005, filed on Nov. 21, 2008, and entitled “FEMTO CELL LOCAL BREAKOUT MECHANISMS”. This application is also related to co-pending U.S. patent application Ser. No. 12/623,176, filed on Nov. 20, 2009, entitled “FEMTOCELL LOCAL BREAKOUT MECHANISMS”, co-pending U.S. patent application Ser. No. 12/623,210, filed on Nov. 20, 2009, entitled “HOME SERVICE INTEGRATION AND MANAGEMENT BY EMPLOYING LOCAL BREAKOUT MECHANISMS IN A FEMTOCELL”, and co-pending U.S. patent application Ser. No. 12/623,237, filed on Nov. 20, 2009, entitled “FEMTO CELL LOCAL BREAKOUT MANAGEMENT SERVICES”. The entireties of each of the foregoing applications are incorporated herein by reference.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, more particularly, to providing service continuity during local breakout at a femto access point when a user equipment (UE) moves between the femtocell and macro cell.

BACKGROUND

Femtocells—building-based wireless access points interfaced with a wired broadband network—are traditionally deployed to improve indoor wireless coverage, and to offload a mobility radio access network (RAN) operated by a wireless service provider. Improved indoor coverage includes stronger signal and improved reception (e.g., video, sound, or data), ease of session or call initiation, and session or call retention, as well. Offloading a RAN reduces operational and transport costs for the service provider since a lesser number of end users utilizes over-the-air radio resources (e.g., radio frequency channels), which are typically limited. With the rapid increase in utilization of communications networks and/or devices, mobile data communications have been continually evolving due to increasing requirements of workforce mobility, and, services provided by femtocells can be extended beyond indoor coverage enhancement.

Conventional systems that employ femtocells, transport information (e.g., data and/or voice) from a user equipment (UE) including Internet bound traffic and home network bound traffic, through a landline network to a macro radio access network (RAN). The information is received at the macro RAN and the Internet bound data can be identified and routed to the Internet from the core network, while the home network bound data is directed back to the home network from the core network. This can lead to significant network congestion in the landline network and/or macro RAN. Further, since data sent by the UE is routed to the home network from the wireless core network only after traversing through the landline network, the response time is substantially high. Accordingly, bandwidth utilization in the traditional approach is inefficient and can negatively impact performance and customer satisfaction.

SUMMARY

The systems and methods disclosed herein, in one aspect thereof, can facilitate local breakout mechanisms at a femto access point (FAP) to reduce backhaul and/or macro network congestion. Moreover, a slave Gateway GPRS Support Node (GGSN) can be integrated within the FAP to breakout a packet data protocol (PDP) context connection and directly route the traffic between a user equipment (UE) at the FAP and a local network or Internet. In one example, Local Area Network (LAN) bound traffic can be identified and directly routed to a device and/or application on a LAN connected to the femto AP, for example, a Digital home (DH) LAN. In an aspect a UE DH agent can be employed that performs mapping to provide DH functions to the UE attached to the femto AP. Specifically, the UE DH agent can enable the UE to behave as a DH compliant device in the DH LAN. In addition, Internet bound traffic from the UE can be directly routed to the Internet via the DH LAN.

In accordance with another aspect of the system, a continuity component can be employed to maintain continuity of a communication session between the UE and the Internet, or a device, service and/or application of the DH LAN, when the UE detaches from the FAP. In particular, a network change detection component can be utilized to determine when the UE changes its connection from one network to another, for example, femto network to macro network or vice versa. Further, a context management component can be employed to seamlessly resume communication session on the newly connected network. Specifically, the slave GGSN in the FAP can seamlessly resume a PDP context communication session between the FAP and the core GGSN from a local breakout session, such that a UE can handover to the newly connected network (e.g., macro wireless network). In addition, the network change detection component can also detect when the communication session can be transferred from one UE to another. Moreover, the context management component can seamlessly resume the communication session on the new device by employing a halted session transfer mechanism.

Yet another aspect of the disclosed subject matter relates to a method that can be employed restore a communication session when a UE switches between a macro network and a femto network. Typically, a switch in the UE's network can be determined and accordingly, status information associated with one or more active communication sessions can be stored in a database. As an example, the status information can include a point up to which the communication session has been completed. Further, when the UE switches to the new network, the status information can be utilized to resume the communication sessions over the new network, from a point where they had previously switched.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It may be evident, however, that the various embodiments can be practiced without these specific details, e.g., without applying to any particular networked environment or standard. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the embodiments in additional detail.

Moreover, terms like “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device,” and similar terminology, refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably in the subject specification and related drawings. Likewise, the terms “access point,” “base station,” “Node B,” “evolved Node B,” and the like, are utilized interchangeably in the subject application, and refer to a wireless network component or appliance that serves and receives data, control, voice, video, sound, gaming, or substantially any data-stream or signaling-stream from a set of subscriber stations. Data and signaling streams can be packetized or frame-based flows. Additionally, the terms “femtocell network”, and “femto network” are utilized interchangeably, while “macro cell network” and “macro network” are utilized interchangeably herein. Further, the terms “core network”, “mobility core network”, “mobile core network”, “core mobility network”, “core mobile network” and “mobility network” are utilized interchangeably herein.

Furthermore, the terms “user,” “subscriber,” “customer,” and the like are employed interchangeably throughout the subject specification, 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), which can provide simulated vision, sound recognition and so forth. In addition, the terms “femtocell access point”, “femtocell”, “femto access point,” “home base station,” “home eNode B(HeNB),” “home Node B (HNB),” and the like, are also utilized interchangeably.

Systems and methods disclosed herein employ local breakout mechanisms at a femto access point (FAP) that can reduce network congestion in a macro RAN and/or a backhaul network connected to the femto AP. In one aspect, a user equipment (UE) attached to the femto AP can communicate directly with a home/enterprise LAN (e.g., connected to the femto AP) and/or the Internet, without utilizing core network resources. In addition, service continuity can be maintained when the UE, communicating directly via the femto AP, moves between the femtocell and the macro cell.

Aspects, features, or advantages of the subject innovation can be exploited in substantially any wireless communication technology; e.g., Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), Enhanced General Packet Radio Service (Enhanced GPRS), Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), or Zigbee. Additionally, substantially all aspects of the subject innovation can be exploited in legacy telecommunication technologies.

Referring initially toFIG. 1, there illustrated is an example system100that facilitates seamless communication with a user equipment (UE)102when switching between a femtocell and macro cell, during local breakout at the femto access point (FAP)104, according to an aspect of the subject disclosure. In one embodiment, the UE102, can be located within a coverage area of the FAP104and can attach to the FAP104by employing most any attachment procedure. Typically, the UE102as disclosed herein can include most any communication device employed by a subscriber, such as, but not limited to, a cellular phone, a personal digital assistant (PDA), a laptop, a personal computer, a media player, a gaming console, and the like. Moreover, the UE102can access a mobile core network109through the femto network via FAP104and/or a macro network via base station106. It can be appreciated that the macro network can include most any radio environment, such as, but not limited to, Universal Mobile Telecommunications System (UMTS), Global System for Mobile communications (GSM), LTE, CDMA, etc. The signaling and bearer technologies, for example circuit switched (CS), and/or packet switched (PS), in a femtocell and macro cell can be the same or different, depending on the radio technologies involved.

Typically, traffic flows between the FAP104and mobile core network109and between the base station106and mobile core network109through a broadband backhaul110(e.g., optical fiber based technologies (e.g., Ethernet, DS3, etc.), twisted-pair line based technologies (e.g., DSL, T1/E1 phone line, etc.), or coaxial cable based technologies (e.g., DOCSIS, etc.)). The FAP104generally can rely on the broadband backhaul110for signaling, routing and paging, and for packet communication. According to an embodiment, the FAP104can include a routing component108that can be utilized to facilitate efficient routing of traffic to via the FAP104.

In one example, the routing component108can include a slave Gateway GPRS Support Node (GGSN). Typically, the slave GGSN can implement functionality substantially similar to the functionality implemented by a GGSN in the mobile core network109. For example, slave the GGSN can be employed to break the PDP context between a UE and core GGSN and a routing functionality can be implemented by the slave GGSN to perform local breakout at the FAP104. In addition, the slave GGSN can enable anchoring of a communication session at the routing component108rather than the core network GGSN. In the local breakout status, the slave GGSN can set up a (0,0) PDP context, e.g., a (zero uplink data bandwidth, zero downlink data bandwidth) connection between slave GGSN and core GGSN while route (x,y), e.g., (x uplink data bandwidth, y downlink data bandwidth) with a local network or Internet. The (0,0) PDP context link can be utilized to switch local breakout session to core network so UE's handover to new network can accomplished. In one aspect, the routing component108can receive traffic (e.g., voice, data, media, etc.) from the UE102and/or from the mobile core network109(e.g., via the broadband backhaul110), analyze the received information and determine a route for the received traffic. According to one embodiment, the routing component108can selectively route UE traffic away from an Iuh Virtual Private network (VPN) tunnel and send the traffic to a residential/enterprise local IP network destination, for example, via a home/enterprise network, Local Area Network (LAN), and/or a broadband access network (e.g., Internet) (not shown).

For example, the routing component108can receive communication packets sent by UE102connected to the FAP104and can determine information associated with the received packet that can facilitate routing of the packet from the FAP104via the slave GGSN. As an example, the routing component108can check a header associated with the received packet and determine a destination address. Based in part on the determined destination address, the routing component108can compute an optimal route to transfer the received packet, such that, network bandwidth is efficiently utilized. Moreover, the routing component108can facilitate route determination based in part on a destination address, source address, type of packet, type of protocol, one or more user and/or service provider defined rules or policies and/or user preferences. Additionally, the routing component108can utilize load balancing mechanisms, machine learning techniques, and/or a cost benefit analysis to generate a route for the received packets.

Typically, a femto gateway (not shown) can aggregate regional traffic received from the multiple FAPs and tunnel the traffic to the mobile core network109. The conventional circuit switched (CS) traffic can be routed to a Mobile Switching Center (MSC) and the packet switched (PS) traffic can be routed to a Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN). According to an aspect, the routing component108can facilitate communication between UE102and a device on a local area network (LAN) (not shown), such as but not limited to, a Digital Home (DH) LAN, by directly routing information between the UE102and the LAN (e.g., without routing the traffic through the mobile core network109). Accordingly, the UE102can directly communicate with a device, service and/or application of the LAN, when UE102is attached to the FAP104. Similarly, routing component108can route Internet bound traffic, received from the UE102, directly to the Internet, for example, via the LAN. In one example, the routing component108can examine traffic sourced in the UE102to separate home/enterprise bound, broadband access network bound and/or Internet bound traffic from the rest.

It can be appreciated that when UE102detaches from the FAP104, the mobile core network109can maintain a connection to the UE102via the mobility network (e.g., through base station106). Moreover, the continuity component112(e.g., which can be a part of a slave GGSN) can be utilized to facilitate seamless service continuity for the UE102, when the UE102detaches from the femto AP104. As an example, the continuity component112can determine when the UE102changes its connection from the femto cell to the macro cell and/or vice versa. In particular, the continuity component112can be employed to seamlessly resume communication with the UE102on the newly connected network. In one example scenario, when the UE102is attached to the femto AP104, the UE can communicate with a device, service and/or application on the LAN and/or the Internet, by employing local breakout. During communication, the continuity component112can determine when the UE102, is going to move to out of the femtocell, for example, based on user indication, UE location, UE behavior, historical patterns, etc. Accordingly, the continuity component112can ensure a seamless handoff to the macro network, such that the communication is performed via the macro network. Similarly, in another example scenario, the UE102can be roaming in the macro network (not shown) and can communicate for example, with a device, service and/or application on the LAN and/or the Internet via base station106. According to an aspect, the continuity component112, can maintain service continuity when detected that the UE102has attached to the femto AP104. The routing component108can then be utilized to facilitate communication of the UE102with the device, service and/or application on the LAN and/or the Internet, by employing local breakout at the femto AP104.

FIG. 2illustrates an example system200that can be employed to facilitate service continuity during local breakout mechanisms at a femto access point (AP), in accordance with an aspect of the disclosure. It can be appreciated that the continuity component112can include functionality, as more fully described herein, for example, with regard to system100.

System200can include a network change detection component202that can determine when the UE changes its connection from one network to another, for example, femto network to macro network or vice versa. In one example, the network change detection component202can determine when the UE, attached to the femtocell, leaves the femtocell, based in part on various factors, such as, but not limited to, UE registration data, UE location, UE behavior, historical patterns, user preferences, etc. Further, a context management component204can be employed to seamlessly resume content delivery on the newly connected network.

As an example, when the UE connects to a macro network, the UE can indicate a change in connection by updating its registration, which can be detected by the network change detection component202. According to an aspect, the network change detection component202can indicate the change in user network to the context management component204. The context management component204can be employed to determine a context state associated with the communication of the UE, for example, with a device, application, and/or service of the LAN or the Internet. As an example, the context management component204can determine a point up to which content has been delivered to the UE, such as, but not limited to, “15 files delivered”, “20% of video streamed” etc.

Further, the context management component204can store the current context state to a database206. The database206can store the context state, which can include, for example, data associated with the content at a point in time (e.g., video frames up to 30.25 minutes) that has been delivered to the user. It can be appreciated that the context state can include most any data associated with the state of the communication session when the UE moves from one network to another. In one aspect, the context state can be obtained from the device, application and/or service of the LAN and/or the Internet, with which the UE is communicating. Additionally, the database206can also store a session-id and/or a user-id associated with the context state that can be employed to facilitate a lookup at a later time. It can be appreciated that although the database206is illustrated to reside within the continuity component, for example, in the femto AP, the database206can be local or remote to the femto AP, and can also reside within the macro network. According to an aspect, the database206can be accessed by and/or the saved context state can be utilized by a component (not shown) in the newly connected network that can be employed to facilitate communication over the new network, such that, the communication session can begin from where it left off. Further, in one aspect, the context management component204can also save context state associated with a communication session to the database206, when determined that the communication session has to be transferred from one device to another.

Referring now toFIG. 3, there illustrated is an example system300that can be employed to facilitate efficient routing of traffic within a femtocell, according to an aspect of the subject disclosure. It can be appreciated that the UE102, femto AP104, routing component108and continuity component112can include respective functionality, as more fully described herein, for example, with regard to systems100and200. Moreover, system300includes a femto AP104that can be integrated with an integrated residential gateway (RG). AlthoughFIG. 3illustrates an RG that is integrated within the femto AP104, it can be appreciated that the RG can be externally connected to the femto AP104. Further, Femto AP104can be connected to a LAN, for example digital home (DH) LAN310, by a wireless and/or wired connection. It can be appreciated that the DH LAN310disclosed herein, can be most any LAN and can be deployed in most any area, such as but not limited to, a house, an office, a building, a warehouse, a store, a restaurant, a hotel, a factory, etc.

Typically, the femto AP104can receive communications from a UE102. The UE102can be most any communication device employed by a user, for example, a cellular phone, a gaming module, a laptop, a television, a projector, personal computer, a personal digital assistant (PDA) etc. Moreover, the UE102can utilize various technologies for terrestrial wireless communication, for example, an advanced second generation (2.5G) telecommunication technology such as Enhanced Data Rate for Global System for Mobile Communications (GSM) Evolution (EDGE); a third generation technology (3G) like Third Generation Partnership Project (3GPP) Universal Mobile Telecommunication System (UMTS), 3GPP Long Term Evolution (LTE), a 3GPP2 Evolution Data Only (EVDO) system, or Ultra-broadband Mobility (UMB); advanced 3G such as Worldwide Interoperability for Microwave Access (WiMax); or a fourth generation (4G) technology such as for example Long Term Evolution (LTE) Advanced. Additionally, a UE102can consume satellite-based traffic such as data originated from GPS, GLONNAS, or Galileo systems, conveyed through a deepspace link (not shown).

In one aspect, the Home Node B (HNB)302can receive communication from the UE102and can perform Node-B radio functions such as, but not limited to scheduling. Further, a partial Radio network control (RNC)304can be employed to perform Radio Resource Control (RRC), radio bearer (RB)/radio access bearers (RABs), radio access network (RAN) quality of service (QoS), call admission control (CAC)/Power/Congestion control, and the like. In accordance with an aspect, a routing component108can locally break out Internet and/or home/enterprise network bound traffic. In one aspect, the routing component108can include a slave GGSN. Moreover, information packets received from the UE102can be analyzed by the routing component108and a route to transfer the packets can be determined. In one example, the routing can be based in part on a destination address, source address, type of packet, type of protocol, one or more user and/or service provider defined rules or policies and/or user preferences.

According to an embodiment, a Policy Decision/Policy Enforcement Function (PDF/PEF)306can be employed to drive the selection of the route. The PDF/PEF306can include multiple policies that can be specified, for example, by a service provider through a management component308. The management component308can be employed to facilitate FAP management (FAP white list, policy rule updates, Ethernet port management, FAP firmware updates, GSN routing function management, performance and alarm status update, etc.). Additionally, the management component308can employ Technical Report 069 (TR-69) protocol to communicate with a femto provisioning/management platform in the mobility network. According to an aspect, when a customer installs the femto AP104, during setup (or at any other time), the management component308can facilitate authentication of the femto AP104with the mobility network, such that, the service provider can recognizes the femto AP104and can ensure that the customer and/or femto AP104is legitimate. Further, once the customer and/or femto AP104are authenticated, the management component308can download configuration information (e.g., service provider policies, rules, definitions) and parameters that can facilitate connection with the core network elements (e.g., GGSN).

In one embodiment, the management component308can provide an interface that enables a mobility network operator/service provider/mobility network element to control the local breakout mechanism, for example, by specifying policies in the PDF/PEF. In one example, the management component308can also provide mobility network operator/service provider/mobility network element with an override functionality. Moreover, the mobility network operator/service provider/mobility network element can utilize the override functionality to stop local breakout at most any time and/or for a specified time period. Specifically, the override functionality can be employed by a service provide upon legal request and/or for security purposes. For example, a legal/security request can be made (e.g., by a government agency) to monitor communication through a particular FAP and the service provider can utilize the management component308to override the breakout mechanisms employed at the FAP, such that all communication at the FAP can be transferred via the mobility network. Moreover, the management component308, in response to the override command, can disable breakout functionality at the routing component108and/or create a policy, which ensures that local breakout is not performed at the FAP104.

The routing component108, based in part on factors, such as but not limited to, the analysis, the PDF/PEF, etc., identifies an optimal route for traffic received at the femto AP104. In one example, when traffic is received from the UE102, the routing component108can identify whether the traffic should be routed to the macro network, via the Iu tunnel, to the Internet via the DH LAN310, a device/application/service on the DH LAN310and/or a disparate UE (not shown) attached to the femto AP104. Based on the determination, the routing component108can deliver the traffic via the identified route. In another example, the routing component108can receive traffic from the device on the DH LAN310and can determine an optimal route (e.g., to UE102, or macro network, etc.) for the traffic, for example, by employing one or more policies in the PDF/PEF306, and route the traffic via the optimal route.

Additionally or alternately, a Network address translation (NAT)/Firewall component312(e.g., IPv4) can be employed to map network address information in packet headers that can be routed via the backhaul network and/or the home/enterprise network. Typically, the RG can provision the femtocell with an IP address when the femtocell attaches to the home network, for example DH LAN310. When the routing component108determines that the traffic (e.g., from UE102) can be routed to the DH LAN310, the NAT/Firewall component312can employ a NAT function to proxy the IP address of UE102in a packet header, with a home network domain IP address associated with the DH LAN310. Similarly, when the routing component108determines that the traffic (e.g., from DH LAN310) can be routed to the UE102, the NAT/Firewall component312can utilize a NAT function to proxy the home domain IP address with the IP address of the UE102.

Further, the NAT/Firewall component312can employ a firewall for intrusion detection and/or prevention for UE102to home network traffic and vice versa. Furthermore, the firewall can allow or prevent a device on the DH LAN310to access the mobility network through the Iu tunnel. In one aspect, the NAT/firewall component312can utilize one or more policies from the PDF/PEF306to control access of the mobility network by the device on the DH LAN310. For example, the firewall can protect the digital home network and prohibit bridging the DH LAN310with the Internet through the mobility core network. It can be appreciated that the firewall can be hardware, software, or a combination thereof. In one example, a modem314(DSL or most any broadband modem) can be employed for transmission of packets through the backhaul network to the macro RAN. Furthermore, the femto AP104can include a security component316that can utilize most any encryption technique for secure channel set up and/or tear down and/or encryption of outbound traffic. For example, the security component316can perform encryption for establishing the Iu tunnel.

According to an aspect, a continuity component112can be utilized to detect when UE102is detaching from the femto AP104. The continuity component112can further identify if the UE102has an active communication session with a device/application/service on the DH LAN310and/or the Internet, for example, facilitated by the routing component108. If one or more communication sessions exist, the continuity component can determine a current context state associated with the sessions and save the context state, such that the context state can be utilized by an element in the macro network to continue the communication session with the UE102, when the UE102moves into the macro cell. Additionally, in another aspect, the continuity component112can detect attachment of UE102to the femto AP104and determine whether the UE102has an ongoing communication session(s) with a device/application/service on the DH LAN310and/or the Internet via a macro network. Further, the continuity component112can determine a current context state associated with the ongoing communication session(s), for example, stored by an element of the macro network, and can facilitate seamless continuity of the session when the UE102attaches to the femto AP104from the macro cell. In one aspect, the routing component108can facilitate delivery of the remaining communication session, when the UE102attaches to the femto AP104.

Additionally or alternately, the femto AP104can include a synchronization component318that can be employed to facilitate dynamic synchronization when the UE102attaches to the femto AP104(and/or on demand). In particular, the synchronization component318can manage synchronization of data between a device, application and/or service on the DH LAN310, and/or a website from the Internet, with an authorized UE, for example, UE102. In one aspect, an authorized UE, femtocell owner and/or network provider can specify data that can be synchronized when a specific UE102attaches to the femto AP104. In one example, the synchronization component318can utilize data from an access control list (ACL) to determine synchronization parameters. In another example, the synchronization component318can perform synchronization based on one or more policies. In particular, the synchronization data can be directly routed between the UE102and the device, application and/or service on the DH LAN310, and/or the Internet, by employing the routing component108.

Referring toFIG. 4, there illustrated is an example system400that facilitates communication session continuity for a UE associated with a femtocell, according to an aspect of the subject specification. It can be appreciated that the continuity component112can include functionality, as more fully described herein, for example, with regard to system100,200and300. As discussed previously, the continuity component112can be employed to maintain seamless communications between a UE and a device/service/application on a DH LAN, or the Internet, when the UE moves between the femto and macro networks.

Typically, the continuity component112can include a data session management component402that can facilitate maintaining a data communication session associated with the UE, when the UE moves from the femtocell to the macro cell and/or vice versa. In one example a UE attached to a femto AP can directly communicate (e.g., by employing the routing component) with a device, service and/or application of a DH LAN, connected to the femto AP. Additionally or alternately, the UE can directly communicate with the Internet for example, via the DH LAN. The data session management component402can monitor the status of a data session associated with the UE when determined that the UE is leaving the femto network. In one example, the determination can be made automatically, for example, by employing a machine learning technique, and/or can be indicated by the UE and/or the user. The data session management component402can store the session status information in a database, for example, residing in the femtocell and/or in the macro cell. When the UE moves into the macro cell, the macro network can identify the stored session status and resume the session where it left off.

In another example, when a UE, communicating with the Internet or a device, service and/or application of a DH LAN, connected to a femto AP, moves from the macro cell to the femtocell, the data session management component402can determine a current status of the data session, for example, from a local or remote database. In one example, the status of the data session can be stored by various entities, such as but not limited to, the device, service, application and/or a web server, etc. Moreover, the data session management component402can utilize the stored status to resume the data session through the femto AP, by employing a local breakout mechanism. For example, a data session between a UE and the Internet can be facilitated in the macro network, and when the UE enters the femtocell, the data session management component402can continue the session between the UE and the Internet through the femtocell, by employing local breakout to the Internet at the femto AP.

According to an aspect, a streaming session management component404can be utilized to facilitate session continuity for steaming data, such as but not limited to, video, audio, real time data, etc. Further, the streaming session management component404can be employed to transfer a streaming session from one device in the femto network to another. For example, a user who is viewing television in his home, for example, connected to the DH LAN can utilize the streaming session management component404to transfer the viewing session to his mobile device, for example attached to the femto AP in preparation to leave the house. In one aspect, the streaming session management component404can facilitate transferring the streaming session to the UE and ensuring session continuity when the UE moves out of the femto network. The reverse scenario can also be handled by the streaming session management component404. Accordingly, the streaming session management component404can facilitate continuity of a streaming session, between devices and/or networks. It can be appreciated that the transferring of a streaming session can be based in part on various factors, such as, but not limited to, user input, UE location, historical patterns, cost benefit analysis, etc.

In one aspect, an interactive session management component406can be utilized to facilitate interactive session continuity between devices and/or networks. As an example, the interactive session management component406can transfer an interactive session between one or more UE attached to the femto AP, and a device/application/service of a DH LAN, connected to the femto AP, etc. Moreover, the transfer can be driven, based on a user input, and/or a user preference, service provider policy, UE location, time or date, etc. In addition, when the UE moves outside the femtocell, the interactive session management component406can ensure seamless session continuity over the macro network. As an example, the interactive session management component406can transfer an interactive session from a gaming module, connected to the DH LAN, to a UE attached to the femto AP, for example, when a user, playing a game prepares to leave the femtocell coverage area. Further, the interactive session management component406ensures that the interactive session is continued even when the UE moves into the macro network, for example, by employing macro network resources. It can be appreciated that the interactive session management component406can also facilitate communication continuity in a reverse scenario. Similarly, a messaging session management component408can be included, which can facilitate seamlessly transferring a messaging session from one device to another (e.g., by employing local breakout at the femto AP) and/or ensuring messaging session continuity, when the devices associated with the messaging session move between the femtocell and macro cell.

Further, an application management component410can be employed to ensure continuity during application (e.g., management traffic) transfer. For example, an operation support system (OS) can communicate with a UE, when the UE is attached to the femto AP, for configuring the UE, loading a new version of a server to the UE, etc. During the communication, if the UE moves out of the femto coverage area, the application management component410can ensure that the OS can complete the configuration, update and/or download, via the macro network. Accordingly, the continuity component112can facilitate continuity during communication with most any source application, for example, sourced in the UE, the DH LAN, the macro network, etc. As an example, the source application can exchange files, messages, and/or most any content. Further, the communication traffic can be session-based (e.g., Voice over Internet Protocol) or transactional (e.g., messaging and/or file transfer).

Referring toFIG. 5, there illustrated is an example system500that facilitates UE-to-UE CS media breakout and continuity within a femtocell in accordance with an aspect of the subject disclosure. It can be appreciated that the routing component108, management component308, continuity component112, synchronization component318, and femto AP104can include functionality, as more fully described herein, for example, with regard to system100,200,300and400.

One or more UEs (502,504) can attach to the femto AP104when the UEs (502,504) are within the coverage area of the femto AP104, for example, by employing most any attachment procedure. It can be appreciated that the femto AP104can utilize an authentication and/or authorization technique to prevent unauthorized attachments. For example, the femto AP104can manage access to femtocell services through access control list(s)508, e.g., white list(s) or black list(s). Such access control list(s)508can be configured through various apparatuses and in various modes, e.g., interactively or automatically, which facilitates access management of access to femtocell coverage. As an example, white list(s) includes a set of UE(s) identifier numbers, codes or tokens, and can also include additional fields that can contain information respectively associated with communication devices to facilitate femtocell access management based at least in part on desired complexity; for example, an additional field in a white list can be a logic parameter that determines whether an associated identifier is available for dissemination across disparate white lists. Values of attribute fields that determine white list(s), black list(s), or white list profile(s) can be generated through various sources. The management component308can facilitate generation and maintenance of white list(s), black list(s), or white list profile(s).

In addition, the management component308can be employed to create, update and/or delete information that facilitates routing and/or authentication, which can be stored in database506. Although database506is shown to reside within the femto AP104, it can be appreciated that database506can be a local, a remote, and/or a distributed database. In one example, the database506can be substantially similar to and/or the same as database206(FIG. 2). The database506can be employed to store information such as, but not limited to, access control list508, user preferences510, attached UE parameters512, service provider policies514and/or session context data516. The service provider policies514can typically include one or more policies associated with routing and/or breakout at the femto AP104. In addition, the service provider policies514can include the PDF/PEF that can drive the selection of an optimal route, for example, by the routing component108. Further, the attached UE parameters512can provide a list of currently attached UEs (502,504) and can typically include information (e.g., device ID, SIM, USIM, a mobile number, etc.) associated with the UEs (502,504) that are currently attached to the femto AP104.

In one example, when UE502initiates a call, the routing component108can analyze the CS traffic from the UE502and determine an optimal path to route the call. As an example, the routing component108can analyze information stored in the database506, such as, but not limited to user preferences510, attached UE parameters512and/or service provider policies514, to determine the optimal path. In one aspect, the routing component108can verify whether the destination device for the CS call is attached to the femto AP104, for example, by employing information from the attached UE parameters512. When the routing component108determines that the destination entity is not attached to the femto AP104, the routing component108can direct the call to the macro network via the backhaul network. Alternately, when the routing component108determines that the destination entity is attached to the femto AP104, for example, if the destination entity is UE504, the routing component108can facilitate CS media breakout at the femto AP104and facilitate communication between the UE502and UE504without routing the call through the macro network. It can be appreciated that when one of or both the UEs move out of the femtocell coverage area, service continuity can be established, by the continuity component112, and the call can be routed via the macro network. Further, it can be appreciated that the routing component can transmit data indicating the CS media breakout to the core mobility network (e.g., that can be utilized for billing and/or records, etc.)

Traditionally, when the UE (502,504) attaches to the femtocell, an active CS call continue via base audio unit (BAU) except for the transport path of the traffic, which is routed through a home broadband service. According to an embodiment, the femto AP104can further include a CS to VoIP management component518that facilitates converting the active CS call to a VoIP call, without customer interaction, to release CS resources in the network. Moreover, the VoIP call can be routed by employing breakout mechanisms at the femto AP104. For example, a CS call from a UE (502,504) can be converted to a VoIP call and routed to the Internet via DH LAN (310,FIG. 3), without utilizing core mobile network resources.

FIG. 6illustrates an example system600that provides service continuity during home services integration with a femtocell, according to an aspect of the subject disclosure. Typically, system600can include a femto AP104that can comprise an integrated and/or external RG. It can be appreciated that the routing component108, NAT/Firewall component312, modem314, security component316, continuity component112, synchronization component318and femto AP104can include functionality, as more fully described herein, for example, with regard to system100,200,300,400and500. Additionally, it can be appreciated that femto AP104can include components (e.g., HNB, partial RNC, management component, PDF/PEF, etc.) as illustrated inFIG. 3and described herein with respect to system300.

According to an embodiment, the routing component108can facilitate communication between a UE (602,604) and one or more devices606on the DH LAN310. Typically, device606can be most any device on the DH LAN310, such as, but not limited to, a telephone, a printer, a laptop, an appliance, a television, a projector, a gaming module, music player, etc. Thus, the UE (602,604) can join the LAN (e.g., home network), without supporting a dual mode wireless/Wi-Fi functionality. In addition, the routing component108can directly route Internet bound packets to the Internet, without transferring the packets to the core network. Further, the routing component108can identify communication directed to a device on the LAN and route the communication directly to the destination via the DH LAN310. In one aspect, the continuity component112can maintain communication session(s) via the macro network when the UE (602,604) detach from the femto AP104.

According to an embodiment, the femto AP104can include a UE DH agent608that can facilitate communication between UE602and a device606on the DH LAN310. In one aspect, the UE DH agent608can identify when a UE602attaches to the femto AP104and can communicate the presence of the UE602to the DH functions. Similarly, the UE DH agent608can identify when the UE602leaves the femtocell and accordingly communicate the absence of the UE602to the DH functions. Moreover, the UE DH agent608can perform mapping to provide DH functions to the UE602. Specifically, the UE DH agent608can make the UE602appear as a DH compliant device in the DH LAN310. In accordance with an aspect, the UE DH agent608can provide an authorized UE with DH services610, such as, but not limited to, Digital Rights management (DRM), Remote User Interface (RUI), Dynamic Host Configuration Protocol (DHCP), session management (SM), Universal Plug and Play (UPnP), Analog Terminal Adapter (ATA).

Moreover, the UE DH Agent608can offload traffic to the broadband access network. For example, UE traffic to/from the Internet can be routed directly to the Internet service provider (ISP) and the DH LAN310, and can bypass the GSN. Accordingly, the UE DH agent608can route signaling and/or media to and/or from the DH LAN310in an efficient manner, avoiding hairpinning (e.g., tromboning). In an additional aspect, the UE DH agent608can utilize the continuity component112to facilitate session continuity for traffic between the UE602and select DH LAN services610and/or devices606, when the UE602moves from the femtocell to the macro cell and vise versa.

It can be appreciated that the UE DH agent608can be located within the femtocell and/or can be located within a UE, for example the DH client612in UE604. In particular, the DH client612can include functionality substantially similar to that of the UE DH agent608. Moreover, the DH Client612can be a device-specific Digital Home compliant client, residing in the UE, for delivering DH services to the UE. It can be appreciated that although only one DH client612is illustrated in UE614, one or more DH clients may reside in UE604, each with the same or different functionality. In one aspect, the DH Client612can enhance user experience beyond that which can be provided with the UE DH Agent608, for example, based on UE specifications and/or user preferences.

Further, the femto AP104can include a femto DH Agent614that can be employed to authenticate the femto AP104with the home network. For example, the femto DH Agent614can facilitate attaching, detaching and establishing its presence in the DH LAN310. In addition, the femto DH Agent614can facilitate wireline and/or wireless convergence by inter-working between the DH functions610and mobility applications616. For example, the femto DH Agent614can facilitate location assisted cellular services by obtaining location of the femto AP104from a function, application, database, and/or device attached to the DH LAN310and providing it to the mobility location servers. In one aspect, the data (e.g., location data, registration data, authorization data, etc.) obtained by the femto DH agent614can be utilized by the continuity component112to determine when the UE (602,604) will change networks. Additionally or alternately, the femto DH Agent614can assist a mobile core charging function for measuring Internet traffic breakout at the femto AP104. Further, the femto DH Agent614can provide traffic breakout information to a service provider billing system (not shown).

Further, in one example, a DSL network can be employed, by the femto AP104, as the transport media to connect to the femto gateway (FGW)618located at the edge of the mobility core network. The conventional Iu traffic consisting of the Circuit Switched (Iu-cs) voice traffic and Packet Switched (Iu-ps) data traffic together with Femto signaling can be transported between the Femtocell and Femto Gateway in a secure channel. Moreover, the Iu over IP protocol can be referred to as Iu+. In order to facilitate a fast radio link layer control, functions of conventional RNC can be split between and integrated into femto AP104and femto gateway618. Functions such as radio bearer management and radio QoS management can be included in the femto AP104(e.g., by employing partial RNC304); and functions of GPRS Tunneling Protocol (GTP) tunnel management, femtocell authentication, mobility management and/or handover control can be integrated into the FGW618. In one example, the FGW618can aggregate regional femtocells' traffic and tunnel the traffic to the core network. The conventional circuit switched (CS) traffic is routed to a Mobile Switching Center (MSC) and the packet switched (PS) traffic is routed to a Serving GPRS Support Node (SGSN)620and Gateway GPRS Support Node (GGSN)622.

FIG. 7illustrates an example system700that employs an artificial intelligence (AI) component702, which facilitates automating one or more features in accordance with the subject innovation. It can be appreciated that the continuity component112, synchronization component318, CS to VoIP management component518, and femto AP104can include respective functionality, as more fully described herein, for example, with regard to systems100-600.

The subject innovation (e.g., in connection with routing, providing service continuity, detecting change in network, etc.) can employ various AI-based schemes for carrying out various aspects thereof. For example, a process for network and/or device transfer determination by the continuity component112can be facilitated via an automatic classifier system and process. Moreover, where the continuity component112can ensure communication session continuity, the classifier can be employed to determine when a UE can move between networks, and/or devices.

A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to a class, that is, f(x)=confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. In the case of communication systems, for example, attributes can be information within the packet headers or other data-specific attributes derived from the information within the packet headers, and the classes can be categories or areas of interest (e.g., levels of priorities).

As will be readily appreciated from the subject specification, the subject innovation can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing user behavior, receiving extrinsic information). For example, SVM's are configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to a predetermined criteria whether the UE is moving from a femtocell to a macro cell, whether the UE is moving from the macro cell to the femto cell, whether a communication session can be transferred from one UE to another, etc. The criteria can include, but is not limited to, UE location, session context data, the type of active session, the importance (e.g., priority) of the active session, historical patterns, UE behavior, user preferences, service provider preferences and/or policies, femto AP parameters, etc.

Referring now toFIG. 8, illustrated is an example methodology800that can restore a communication session when a UE switches to a macro network from a femto network in accordance with an aspect of the subject disclosure. Typically, the communication session can include, but is not limited to, a data communication session, an interactive communication session, a streaming communication session, a messaging communication session, etc. Moreover, the communication session can be delivered in various delivery types (e.g. real-time, near real time, progressive download or download) and/or utilizing various delivery methods. In one aspect, a source application associated with the session can reside in the UE attached to a femto AP, a device on a LAN attached to the femto AP and/or the internet.

At802, it can be determined that the UE is detaching from the femto AP. In one example, various factors, such as, but not limited to, user input, registration information, UE location, UE motion, UE behavior, user preferences, service provider policies, day, date, time, historical patterns, machine learning techniques, etc. can be utilized for the determination. At804, communication session(s) associated with the UE can be determined. In one aspect, the UE can communicate, by employing local breakout at the femto AP, with a device, application and/or service of the LAN, and/or the Internet. If the UE is part of one or more active communication sessions, then at806, status information associated with the communication session(s) can be stored. As an example, the status information can include a point up to which the communication session has been completed. In one aspect, the status information can be stored on a local or remote database (e.g., within the femto or macro network).

At808, seamless continuation of the communication session(s) can be facilitated by providing the stored status information, for example, to an element on the macro network. Accordingly, the communication session(s) can be resumed from a point where they had previously stopped, over the macro network. Thus, re-delivery of the previously communicated information can be avoided and the remaining information can be exchanged efficiently on the macro network.

FIG. 9illustrates an example methodology900that can be employed to resume a communication session when a UE switches to a femto network from a macro network, according to an aspect of the subject disclosure. In one aspect, an authorized UE that enters a coverage area of a femto access point (FAP), from a macro network, can attach to the FAP by employing most any attachment procedure. Typically, the UE can include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a laptop, a personal computer, a media player, a gaming console, and the like.

At902, it can be determined that an authorized UE is attaching to the femto AP. In one example, various factors, such as, but not limited to, user input, registration information, UE location, UE motion, UE behavior, user preferences, service provider policies, day, date, time, historical patterns, machine learning techniques, etc. can be utilized for the determination. At904, active communication session(s) associated with the UE can be determined. According to an example, the active communication sessions can include most any communication session between the UE and a disparate UE connected to the femto AP, a device/service/application of a LAN connected to the femto AP, or the Internet. At906, status information associated with the communication session(s) can be determined. For example, the status information can be retrieved from a remote and/or local database. In one aspect, the status information can be stored in the remote and/or local database, when determined that the UE is moving from the macro network to the femto network. As an example, the status information can include data that indicates a point at which a communication session can resume.

At908, it can be determined that an entity associated with the communication session is connected to the femto AP. For example, the entity can be a disparate UE attached to the femto AP, a device, application or service of a DH LAN connected to the femto AP, and/or the Internet (e.g., connected to the femto AP via the DH LAN). At910, seamless continuation of the communication session(s) can be facilitated based on the status information and by employing local breakout at the femto AP. In one aspect, the local breakout can directly exchange information between the UE and the entity, without employing macro network resources.

FIG. 10illustrates an example methodology1000that facilitates CS continuity to and/or from VoIP, according to an aspect of the subject disclosure. At1002, a UE attachment to a femto AP is identified. At1004, an active CS call can be received to and/or from the UE. At1006, the active CS call can be converted to a VoIP call to release CS resources in the communication network. As an example, the conversion can be performed automatically, without user interaction and/or user input. In one aspect, the conversion can be performed by employing one or more machine learning techniques.

Referring toFIG. 11, there illustrated is an example methodology1100that facilitates streaming communication session continuity between devices and networks in accordance with an aspect of the subject specification. At1102, viewing of a streaming session can be enabled on a UE1. In one aspect, the UE1can be most any UE attached to the femto AP, or a device on a DH LAN connected to the femto AP. For example, streaming video from a camera connected to the DH LAN can be viewed on a television connected to the DH LAN. In another example, the streaming video can be transferred to a mobile device attached to the femto AP, by employing a local breakout mechanism. At1102, the streaming communication session can be transferred to a UE2, for example, connected to the femto AP, by employing a local breakout mechanism at the femto AP. In one example, the camera output viewed on the television, for example, connected to the DH LAN, can be transferred to a mobile device, for example attached to the femto AP in preparation of a user to leave the house. It can be appreciated that the transferring of a streaming session can be based in part on various factors, such as, but not limited to, user input, UE location, historical patterns, cost benefit analysis, etc. In one aspect, the streaming session can be transferred seamlessly from one device to another without disrupting continuity.

According to an embodiment, at1106it can be determined whether the UE2is moving to a macro network. At1108, context data associated with the streaming communication session can be stored at a database, which can be utilized to facilitate session continuity over the macro network, when determined that the UE2is moving to the macro network. Alternately, at1110, the streaming session can be transferred to the UE2, via the femto network, if determined that the UE2is not moving into the macro network.

FIG. 12illustrates a schematic wireless environment1200(e.g., a network) in which a femtocell can exploit various aspects of the subject innovation in accordance with the disclosed subject matter. In wireless environment1200, area1205can represent a coverage macro cell, which can be served by base station1210. Macro coverage is generally intended for outdoors locations for servicing mobile wireless devices, like UE1220A, and such coverage is achieved via a wireless link1215. In an aspect, UE1220can be a 3GPP Universal Mobile Telecommunication System (UMTS) mobile phone.

Within macro coverage cell1205, a femtocell1245, served by a femto access point1230, can be deployed. A femtocell typically can cover an area1225that is determined, at least in part, by transmission power allocated to femto AP1230, path loss, shadowing, and so forth. Coverage area typically can be spanned by a coverage radius that ranges from 20 to 50 meters. Confined coverage area1245is generally associated with an indoors area, or a building, which can span about 5000 sq. ft. Generally, femto AP1230typically can service a number (e.g., a few or more) wireless devices (e.g., subscriber station1220B) within confined coverage area1245. In an aspect, femto AP1230can integrate seamlessly with substantially any PS-based and CS-based network; for instance, femto AP1230can integrate into an existing 3GPP Core via conventional interfaces like Iu-CS, Iu-PS, Gi, Gn. In another aspect, femto AP1230can exploit high-speed downlink packet access in order to accomplish substantive bitrates. In yet another aspect, femto AP1230has a LAC (location area code) and RAC (routing area code) that can be different from the underlying macro network. These LAC and RAC are used to identify subscriber station location for a variety of reasons, most notably to direct incoming voice and data traffic to appropriate paging transmitters.

As a subscriber station, e.g., UE1220A, leaves macro coverage (e.g., cell1205) and enters femto coverage (e.g., area1215), as illustrated in environment1200, UE1220Acan attempt to attach to the femto AP1230through transmission and reception of attachment signaling, effected via a FL/RL1235; in an aspect, the attachment signaling can include a Location Area Update (LAU) and/or Routing Area Update (RAU). Attachment attempts are a part of procedures to ensure mobility, so voice calls and sessions can continue even after a macro-to-femto transition or vice versa. It is to be noted that UE1220can be employed seamlessly after either of the foregoing transitions. Femto networks are also designed to serve stationary or slow-moving traffic with reduced signaling loads compared to macro networks. A femto service provider (e.g., an entity that commercializes, deploys, and/or utilizes femto AP1230) therefore can be inclined to minimize unnecessary LAU/RAU signaling activity at substantially any opportunity to do so, and through substantially any available means. It is to be noted that substantially any mitigation of unnecessary attachment signaling/control can be advantageous for femtocell operation. Conversely, if not successful, UE1220generally can be commanded (through a variety of communication means) to select another LAC/RAC or enter “emergency calls only” mode. It is to be appreciated that this attempt and handling process can occupy significant UE battery, and femto AP capacity and signaling resources as well.

When an attachment attempt is successful, UE1220can be allowed on femtocell1225and incoming voice and data traffic can be paged and routed to the subscriber station through the femto AP1230. It is to be noted also that data traffic is typically routed through a backhaul broadband wired network backbone1240(e.g., optical fiber backbone, twisted-pair line, T1/E1 phone line, DSL, or coaxial cable). It is to be noted that as a femto AP1230generally can rely on a backhaul network backbone1240for routing, signaling and paging. Namely, packet flows established for wireless communication devices (e.g., terminals1220Aand1220B) served by femto AP1230, and for devices served through the backhaul network pipe1240. It is to be noted that to ensure a positive subscriber experience, or perception, it is desirable for femto AP1230to maintain a high level of throughput for traffic (e.g., voice and data) utilized on a mobile device for one or more subscribers while in the presence of external, additional packetized, or broadband, traffic associated with applications (e.g., web browsing, data transfer (e.g., content upload), and the like) executed in devices within the femto coverage area (e.g., area1225or area1245).

It can be appreciated that the femto AP1230can be substantially similar to femto AP104and include functionality, more fully described herein, for example, with respect to systems100-700. In particular, femto AP1230can include a continuity component112(not shown), which can facilitate session continuity when UE (1220Aand1220B), move between macro coverage area1205and femto coverage area1225.

To provide further context for various aspects of the subject specification,FIGS. 13 and 14illustrate, respectively, an example wireless communication environment1300, with associated components for operation of a femtocell, and a block diagram of an example embodiment1400of a femto access point, which can facilitate communication session continuity at a femtocell in accordance with aspects described herein.

Wireless communication environment1300includes two wireless network platforms: (i) A macro network platform1310that serves, or facilitates communication with user equipment1375via a macro radio access network (RAN)1370. It should be appreciated that in cellular wireless technologies (e.g., 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB), macro network platform1310is embodied in a Core Network. (ii) A femto network platform1380, which can provide communication with UE1375through a femto RAN1390linked to the femto network platform1380via backhaul pipe(s)1385, wherein backhaul pipe(s) are substantially the same a backhaul link1240. It should be appreciated that femto network platform1380typically offloads UE1375from macro network, once UE1375attaches (e.g., through macro-to-femto handover, or via a scan of channel resources in idle mode) to femto RAN. According to an aspect, the continuity component112can facilitate efficient communication of traffic between the DH LAN310and the UE1375, when the UE1375moves between the macro RAN1370and the femto RAN1390. Further, it can be appreciated that the continuity component112can include functionality, more fully described herein, for example, with respect to systems100-700.

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 RAN1370can comprise various coverage cells like cell1205, while femto RAN1390can comprise multiple femtocell access points. As mentioned above, it is to be appreciated that deployment density in femto RAN1390is substantially higher than in macro RAN1370.

Generally, both macro and femto network platforms1310and1380can include components, e.g., nodes, gateways, interfaces, servers, or platforms, that facilitate both packet-switched (PS) and circuit-switched (CS) traffic (e.g., voice and data) and control generation for networked wireless communication. For example, macro network platform1310includes CS gateway node(s)1312which can interface CS traffic received from legacy networks like telephony network(s)1340(e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a SS7 network1360. Moreover, CS gateway node(s)1312interfaces CS-based traffic and signaling and gateway node(s)1318.

In addition to receiving and processing CS-switched traffic and signaling, gateway node(s)1318can 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 platform1310, like wide area network(s) (WANs)1350; it should be appreciated that local area network(s) (LANs) can also be interfaced with macro network platform1310through gateway node(s)1318. Gateway node(s)1318generates packet data contexts when a data session is established. It should be further appreciated that the packetized communication can include multiple flows that can be generated through server(s)1314. Macro network platform1310also includes serving node(s)1316that convey the various packetized flows of information, or data streams, received through gateway node(s)1318. It is to be noted that server(s)1314can include one or more processor configured to confer at least in part the functionality of macro network platform1310. To that end, the one or more processor can execute code instructions stored in memory1330, for example.

In example wireless environment1300, memory1330stores information related to operation of macro network platform1310. 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. Memory1330can also store information from at least one of telephony network(s)1340, WAN(s)1350, or SS7 network1360.

Femto gateway node(s)1384have substantially the same functionality as PS gateway node(s)1318. Additionally, femto gateway node(s)1384can also include substantially all functionality of serving node(s)1316. In an aspect, femto gateway node(s)1384facilitates handover resolution, e.g., assessment and execution. Server(s)1382have substantially the same functionality as described in connection with server(s)1314and can include one or more processor configured to confer at least in part the functionality of macro network platform1310. To that end, the one or more processor can execute code instructions stored in memory1386, for example.

Memory1386can include information relevant to operation of the various components of femto network platform1380. For example operational information that can be stored in memory1386can comprise, but is not limited to, subscriber information; contracted services; maintenance and service records; femtocell configuration (e.g., devices served through femto RAN1390; access control lists, or white lists); service policies and specifications; privacy policies; add-on features; and so forth

With respect toFIG. 14, in example embodiment1400, femtocell AP1410can receive and transmit signal(s) (e.g., traffic and control signals) from and to wireless devices, access terminals, wireless ports and routers, etc., through a set of antennas14691-1469N. It should be appreciated that while antennas14691-1469Nare a part of communication platform1425, which comprises electronic components and associated circuitry that provides for processing and manipulating of received signal(s) (e.g., a packet flow) and signal(s) (e.g., a broadcast control channel) to be transmitted. In an aspect, communication platform1425includes a transmitter/receiver (e.g., a transceiver)1466that can convert signal(s) from analog format to digital format upon reception, and from digital format to analog format upon transmission. In addition, receiver/transmitter1466can divide a single data stream into multiple, parallel data streams, or perform the reciprocal operation. Coupled to transceiver1466is a multiplexer/demultiplexer1467that facilitates manipulation of signal in time and frequency space. Electronic component1467can 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 component1467can 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, and so on. A modulator/demodulator1468is also a part of operational group1425, 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), and the like.

Femto access point1410also includes a processor1445configured to confer functionality, at least partially, to substantially any electronic component in the femto access point1410, in accordance with aspects of the subject innovation. In particular, processor1445can facilitate femto AP1410to implement configuration instructions received through communication platform1425, which can include storing data in memory1455. In addition, processor1445facilitates femto AP1410to process 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, processor1445can manipulate antennas14691-1469Nto facilitate beamforming or selective radiation pattern formation, which can benefit specific locations (e.g., basement, home office . . . ), covered by femto AP; and exploit substantially any other advantages associated with smart-antenna technology. Memory1455can store data structures, code instructions, system or device information like device identification codes (e.g., IMEI, MSISDN, serial number . . . ) and specification such as multimode capabilities; code sequences for scrambling; spreading and pilot transmission, floor plan configuration, access point deployment and frequency plans; and so on. Moreover, memory1455can store configuration information such as schedules and policies; femto AP address(es) or geographical indicator(s); access lists (e.g., white lists); license(s) for utilization of add-features for femto AP1410, and so forth.

In embodiment1400, processor1445is coupled to the memory1455in order to store and retrieve information necessary to operate and/or confer functionality to communication platform1425, broadband network interface1335(e.g., a broadband modem), and other operational components (e.g., multimode chipset(s), power supply sources . . . ; not shown) that support femto access point1410. The femto AP1410can further include a routing component108, continuity component112, synchronization component318, CS to VoIP component518, which can include functionality, as more fully described herein, for example, with regard to systems100-700. In addition, it is to be noted that the various aspects disclosed in the subject specification can also be implemented through (i) program modules stored in a computer-readable storage medium or memory (e.g., memory1386or memory1455) and executed by a processor (e.g., processor1445), or (ii) other combination(s) of hardware and software, or hardware and firmware.

Referring now toFIG. 15, there is illustrated a block diagram of a UE1500suitable for communication with a DH LAN via a femto network in accordance with the innovation. The UE1500can include a processor1502for controlling all onboard operations and processes. A memory1504can interface to the processor1502for storage of data and one or more applications1506being executed by the processor1502. A communications component1508can interface to the processor1502to facilitate wired/wireless communication with external systems (e.g., femtocell and macro cell). The communications component1508interfaces to a location component1509(e.g., GPS transceiver) that can facilitate location detection of the UE1500. Note that the location component1509can also be included as part of the communications component1508.

The UE1500can include a display1510for displaying content downloaded and/or for displaying text information related to operating and using the device features. A serial I/O interface1512is provided in communication with the processor1502to facilitate serial communication (e.g., USB, and/or IEEE 1394) via a hardwire connection. Audio capabilities are provided with an audio I/O component1514, which can include a speaker for the output of audio signals related to, for example, recorded data or telephony voice data, and a microphone for inputting voice signals for recording and/or telephone conversations.

The device1500can include a slot interface1516for accommodating a subscriber identity module (SIM)1518. Firmware1520is also provided to store and provide to the processor1502startup and operational data. The UE1500can also include an image capture component1522such as a camera and/or a video decoder1524for decoding encoded multimedia content. The UE1500can also include a power source1526in the form of batteries, which power source1526interfaces to an external power system or charging equipment via a power I/O component1528. In addition, the UE1500can include a DH client612that facilitates communication between UE1500and home network via a femto AP. The DH client612can include functionality, as more fully described herein, for example, with regard to system600.

The illustrated aspects of the specification can also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

With reference again toFIG. 16, the example environment1600for implementing various aspects of the specification includes a computer1602, the computer1602including a processing unit1604, a system memory1606and a system bus1608. The system bus1608couples system components including, but not limited to, the system memory1606to the processing unit1604. The processing unit1604can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit1604.

The system bus1608can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory1606includes read-only memory (ROM)1610and random access memory (RAM)1612. A basic input/output system (BIOS) is stored in a non-volatile memory1610such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer1602, such as during start-up. The RAM1612can also include a high-speed RAM such as static RAM for caching data.

The computer1602further includes an internal hard disk drive (HDD)1614(e.g., EIDE, SATA), which internal hard disk drive1614can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)1616, (e.g., to read from or write to a removable diskette1618) and an optical disk drive1620, (e.g., reading a CD-ROM disk1622or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive1614, magnetic disk drive1616and optical disk drive1620can be connected to the system bus1608by a hard disk drive interface1624, a magnetic disk drive interface1626and an optical drive interface1628, respectively. The interface1624for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Other external drive connection technologies are within contemplation of the subject specification.

A number of program modules can be stored in the drives and RAM1612, including an operating system1630, one or more application programs1632, other program modules1634and program data1636. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM1612. It is appreciated that the specification can be implemented with various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer1602through one or more wired/wireless input devices, e.g., a keyboard1638and a pointing device, such as a mouse1640. Other input devices (not shown) can include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit1604through an input device interface1642that is coupled to the system bus1608, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

A monitor1644or other type of display device is also connected to the system bus1608via an interface, such as a video adapter1646. In addition to the monitor1644, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

When used in a LAN networking environment, the computer1602is connected to the local network1652through a wired and/or wireless communication network interface or adapter1656. The adapter1656can facilitate wired or wireless communication to the LAN1652, which can also include a wireless access point disposed thereon for communicating with the wireless adapter1656.

When used in a WAN networking environment, the computer1602can include a modem1658, or is connected to a communications server on the WAN1654, or has other means for establishing communications over the WAN1654, such as by way of the Internet. The modem1658, which can be internal or external and a wired or wireless device, is connected to the system bus1608via the serial port interface1642. In a networked environment, program modules depicted relative to the computer1602, or portions thereof, can be stored in the remote memory/storage device1650. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

In the subject specification, terms such as “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, or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.