The present invention relates generally to telecommunications and, more particularly, to a system and method for providing mobility to circuit-switched (CS) user equipment (UE) using IP Multimedia Subsystem (IMS)-based services.
In telecommunications, a femtocell—originally known as an Access Point Base Station—is a small cellular base station, typically designed for use in residential or small business environments. It connects to the service provider's network via broadband (such as DSL or cable). A femtocell allows service providers to extend service coverage indoors, especially where access would otherwise be limited or unavailable. The femtocell incorporates the functionality of a typical base station, but extends it to allow a simpler, self-contained deployment.
A Node B is an element of a 3G macro Radio Access Network (RAN), and a 3G Home Node B (3G HNB) is the 3GPP's term for a 3G femtocell. Within a 3G HNB Access Network there are two network elements: a 3G HNB (or femtocell) and a 3G Home Node B Gateway (3G HNB GW). The 3G HNB is connected to an existing residential broadband service and provides 3G radio coverage for 3G handsets within a home. The 3G HNB GW is installed within an operator's network and aggregates traffic from a large number of 3G HNBs back into an existing core service network.
The 3G network, as well as the next generation standard, referred to as Long Term Evolution (LTE), is an Internet Protocol (IP)-based network architecture. As the telecommunications network has evolved, mobile devices have also evolved to act as IP devices. IP devices typically implement IP Multimedia Subsystem (IMS) sessions that utilize packet-switched (PS) communications instead of CS communications. Legacy CS devices, however, are unable to communicate with the PS network, and hence, the legacy CS devices are unable to utilize services or take advantage of the capabilities offered by IMS systems or other PS networks. Furthermore, multi-mode (e.g., 2G/3G multi-mode devices) devices may initially connect via PS communications, but roam to an area that is not serviced by PS communications. In these situations, there is a need for a method and system that allow the legacy CS devices to utilize IMS services when communicating via a femtocell, as well as allow multi-mode devices to roam between PS networks and CS networks.
These and other problems are generally solved or circumvented, and technical advantages are generally achieved, by preferred embodiments of the present invention which provide for access to IP Multimedia Subsystem (IMS) sessions using a circuit-switched (CS) device.
Embodiments of the present invention provide a system and a method for allowing legacy circuit-switched user equipment (CS UE) to operate via a packet-switched (PS) system, such as an IP Multimedia Subsystem (IMS) system. An embodiment utilizes an Interworking Function (IWF) with an agent that interfaces between the CS system and a PS system.
In an embodiment, a communications session is established between UE and a 3G Home Node B (3G HNB) via a CS connection, such that the bearer path extends through a Media Gateway (MGW) and signaling path extends through an Interworking Function (IWF). The communications session is handed over from the 3G HNB to a Base Station System (BSS). After handover is completed, the bearer path extends through the MGW and the signaling path extends through the IWF. The MGW translates between a bearer channel between the CS network and the PS network, and the IWF translates between PS signaling and CS signaling.
In another embodiment, a communications session is initially established between a UE and a 3G HNB via a PS connection. In this embodiment, handover is performed such that the bearer path extends through the MGW and the signaling path extends through the IWF. The MGW translates a bearer path between the CS network and the PS network, and the IWF translates between PS signaling and CS signaling.
In yet another embodiment, a communications session is initially established between a UE and an Enhanced Node B (eNodeB) via a PS communications path. A handover to a 3G HNB via a CS communications path is performed. After handover, the bearer path extends through the MGW, wherein the MGW translates the bearer path between the CS network and the PS network toward the remote end. The signaling path extends through the IWF, wherein the IWF translates between PS signaling and CS signaling.
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
The making and using of the presently preferred embodiments are discussed in detail below. It should be appreciated, however, that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.
Embodiments of the present invention allow user equipment (UE) configured to only provide circuit-switched (CS) communications to access the packet-switched (PS) network, and hence, IP Multimedia Subsystem (IMS) services, as well as allowing mobility between access points of different networks, such as mobility between a packet-switched (PS) network and a circuit-switched (CS) network. Embodiments of the present invention will be described with respect to embodiments in specific contexts, namely a system and method for the provision and mobility of IMS-based services accessed via a 3G Home Node B (3G HNB) using PS or CS communications, a Base Station System (BSS) using CS communications, and/or a Long Term Evolution (LTE) Access using PS communications. Other embodiments of the present invention, however, may be applied to ad hoc networks, cellular networks, wireline networks, and the like, as well as other architectural configurations.
As discussed in greater detail below, an embodiment of the present invention provides a Session Initiation Protocol (SIP) agent collocated with an Interworking Function (IWF) for interworking CS session control procedures with SIP session control procedures to provide active mode mobility between macro CS and macro PS networks. It should be noted, however, that the following embodiments are provided for illustrative purposes only and are not intended to limit the scope of the present invention to only those embodiments described herein. Furthermore, it should be noted that the messages and the message parameters are provided for illustrative purposes only and that other messages and parameters may be used, as well as any suitable protocol, such as session description protocol (SDP), session initiation protocol (SIP), or the like. Additional information regarding the various network elements, interfaces, and message flows may be found in 3GPP TS 23.228, v9.0.0, 3GPP TS 23.237, v9.1.0, 3GPP TS 23.009, v8.1.0, 3GPP TS 23.216, v9.0.0, 3GPP TS 23.228, v9.0.0, and 3GPP TS 23.292, 9.2.0, all of which are incorporated herein by reference.
Referring now to
In an IMS system, a 3G HNB 116 acts as an access point, typically within a user's home, for the UE 110 to provide a PS connection to the 3G PS core 118 via a 3G HNB Gateway (GW) 120. An IMS session is created between the UE 110 and a remote end (not shown), thereby enabling the UE 110 to access media flows. The session control signaling flow extends between the UE 110 and a Call Session Control Function (CSCF), and possibly a Service Centralization Continuity Application Server (SCC AS) or other telephony application servers (TAS), collectively shown in
Generally, the CSCF processes SIP signaling packets in the IMS system, and the telephony application servers host and execute a variety of services. In one embodiment, the SCC AS operates in a Back-to-Back User Agent (B2BUA) mode wherein it acts as an SIP element to mediate SIP signaling between the UE and the remote end. The telephony application servers may be executed on the remote leg as part of standard service execution logic at the CSCF.
An IWF 132, which provides functionality similar to a mobile switching center (MSC) in the macro CS network, is responsible for interfacing with the femtocell system to provide handover capability between the CS network of the macro CS core network (e.g., the BSS/RNS 112 and MSC 114) and the PS network (e.g., the 3G HNB 116). The IWF 132 also connects to a media gateway (MGW) 134, which provides translation services between the IMS network and the macro CS network for media flows over the CS network, and a home subscriber server (HSS) 124, which provides a subscriber database and contains user-related subscription data, such as location information, security information, user profile information, and the like, required to handle IMS sessions.
Also shown in
It should be noted that other network elements, such as routers, gateways, switches, and/or the like, may be present within the networks. The configurations and the communications between network elements are provided for illustrative purposes only, and as such, the communications between the specified elements may be between different elements and/or through additional elements, as well as different signaling/commands may be used.
One of ordinary skill in the art will realize that the above architecture provides various types of access to different types of networks. The description in the following paragraphs provides examples of performing handovers between these different types of networks in accordance with embodiments of the present invention. In particular,
Referring now to
In step 212, the UE 110 initiates a CS attach procedure by transmitting a CS ATTACH message to the 3G HNB 116, which transmits the CS ATTACH message to the 3G HNB GW 120, which in turn forwards the CS ATTACH message to the IWF 132. Upon receiving the CS ATTACH message, the CS location of the UE 110 is updated between the IWF 132 and the HSS 124, which may include the appropriate HLR and VLR, in step 214. An authentication procedure is also performed to authenticate the UE 110 and to obtain subscriber data as indicated. The subscriber identity may be provided by the IWF 132 as part of radio access network application part (RANAP) common ID procedures, whereas the UE 110 identity may be provided by the UE as part of a check in an international mobile equipment identify (IMEI) procedure. Additional information regarding the CS location update and UE registration to the 3G HNB GW 120 may be found in 3GPP TS 25.467, v8.2.0, which is incorporated herein by reference.
After the CS attach procedure is completed, a CS ATTACH ACCEPT message is transmitted from the IWF 132 to the UE 110 via the 3G HNB 116 to signify that the CS attach was successful in step 216. This completes the CS attachment procedure for mobility within the CS domain.
Upon successful completion of the CS attach procedure, the IWF 132 initiates an IMS registration procedure by transmitting, e.g., an IMS REGISTER message, to the CSCF 122 in step 218. Thereafter, in step 220, an IMS registration procedure is performed using, for example, a procedure similar to an early IMS registration, thereby completing the session control attach procedure in the IMS domain.
It should be noted that the above message flow diagram is a high level description of a process in accordance with an embodiment of the present invention. Other embodiments may utilize different messages and/or additional messages. Furthermore, additional procedures, such as authorization procedures, may also be performed. Each message may include various parameters.
In step 314, the IWF 132 transmits the INVITE message to the SCC AS via the CSCF, and in step 316, the SCC AS transmits the INVITE message to the designated third party, e.g., UE-B in this case. Thereafter, the IMS session between the 3G HNB 116 and UE-B is completed using, for example, techniques as defined in 3GPP TS 23.228, v9.0.0 and 3GPP TS 23.292, v9.2.0, which are incorporated herein by reference, as illustrated in step 318, and the CS session between UE 110 and the 3G HNB 116 using, for example, techniques defined in 3GPP TS 24.008, v8.6.0, which is incorporated herein by reference, as illustrated in step 320. As a result, a CS bearer channel is established between the UE 110 and the MGW 134, and an IMS bearer channel is established between the MGW 134 and UE-B, wherein the MGW 134 interfaces between the CS domain and the IMS domain.
Referring now to
After handover, the UE 110 is attached to the BSS/RNS 112, which provides connectivity to the MSC 114. The MSC 114 forwards the CS bearer channel to the MGW 134, which communicates with the remote end via an IP bearer channel. The MSC 114 forwards the CS signaling channel to the IWF 132, which acts as a SIP agent to convert the CS signaling messages to SIP messages before forwarding the signaling messages to the CSCF 122.
Thereafter, in step 512, the 3G HNB 116 signals to the IWF 132 that a handover is required by, for example, a HANDOVER REQUIRED message. In response, the IWF 132 signals to the appropriate CS network element, e.g., the MSC 114, to prepare for a handover, providing it with the necessary information in step 514. The handover may be completed per the procedure defined within 3GPP TS 23.009, v8.1.0, which is incorporated herein by reference, as indicated in step 516. Upon completion of the handover procedure, the access leg with the 3G HNB 116 may be released.
One of ordinary skill in the art will realize that at this point the bearer channel extends from the UE 110 to the MSC 114 (via the BSS/RNS 112) to the MGW 134 to the remote end (e.g., UE-B in this case).
Referring now to
After handover, the UE 110 is attached to the BSS/RNS 112, which provides connectivity to the MSC 114. The MSC 114 forwards the CS bearer channel to the MGW 134, which communicates with the remote end via the IP bearer channel. The MSC 114 forwards the CS signaling channel to the IWF 132, which acts as a SIP agent to convert the CS signaling messages to SIP messages.
Thereafter, in step 712, the 3G HNB 116 signals that a handover is required by, for example, a RELOCATION REQUIRED message to the 3G PS Core 118, which forwards the message to the IWF 132. In step 714, the IWF 132 transmits an INVITE message to the SCC AS via the CSCF. The active session with the UE-B may be transferred using procedures defined in 3GPP TS 23.216, v9.0.0 and/or 3GPP TS 23.237, v9.1.0, both of which are incorporated herein by reference, as indicated in step 716.
The handover may be completed per the procedure defined within 3GPP TS 23.009, v8.1.0, which is incorporated herein by reference, as indicated in step 718. Upon completion of the handover procedure, the access leg with the 3G HNB 116 may be released.
One of ordinary skill in the art will realize that at this point the bearer channel comprises a CS bearer channel extending from the UE 110 to the MSC 114 (via the BSS/RNS 112) to the MGW 134 and an IMS bearer channel between the MGW 134 and the remote end (e.g., the UE-B in this case).
Referring now to
After handover, the UE 110 is attached to the 3G HNB 116, which provides connectivity to the IMS network. The 3G HNB 116 forwards the CS bearer channel to the MGW 134, which communicates with the remote end via the IP bearer channel. The 3G HNB 116 forwards the CS signaling channel to the IWF 132, which acts as a SIP agent to convert the CS signaling messages to SIP messages.
Thereafter, in step 912, the eNodeB 126 signals that a handover is required by transmitting, for example, a RELOCATION REQUIRED message to the SAE Core 128, which forwards the message to the IWF 132. In step 914, the IWF 132 transmits an INVITE message to the SCC AS via the CSCF. The active session with the UE-B may be transferred using procedures defined in 3GPP TS 23.216, v9.0.0 and/or 3GPP TS 23.237, v9.1.0, both of which are incorporated herein by reference, as indicated in step 916.
The handover may be completed per the procedure defined within 3GPP TS 23.009, v8.1.0, which is incorporated herein by reference, as indicated in step 918. Upon completion of the handover procedure, the access leg with the eNodeB 126 may be released.
One of ordinary skill in the art will realize that at this point the bearer channel comprises a CS bearer channel extending from the UE 110 to the MGW 134 (via the 3G HNB 116 and the 3G PS Core 118) and an IMS bearer channel between the MGW 134 and the remote end (e.g., the UE-B in this case).
Referring now to
The network element 1000 also includes a Network Adapter 1018, which may be a wired link, such as an Ethernet cable or the like, and/or a wireless/cellular link for communications with a network 1020. In an embodiment, the network interface 1018 comprises a switching fabric for switching bearer and signaling channels. The network interface 1018 may also comprise a suitable receiver and transmitter for wireless communications. It should be noted that the network element 1000 may include other components. For example, the network element 1000 may include power supplies, cables, a motherboard, removable storage media, cases, and the like. These other components, although not shown, are considered part of the network element 1000.
As one of ordinary skill in the art will appreciate, various embodiments of the invention provide a multitude of advantages. For example, the preferred embodiment completely offloads the CS Core network of the session control signaling. It also provides service continuity with CS, as well as PS macro cellular. As discussed above, embodiments of the present invention offload the CS Core network of the session control signaling by placing the translation of CS signaling to SIP signaling in the IWF, placing mobility functions in the transport layer, as opposed to some other approaches that place these functions in the application layer requiring tunneling of transport layer information in application layer signaling.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. For example, many of the features and functions discussed above can be implemented in software, hardware, or firmware, or a combination thereof. As another example, it will be readily understood by those skilled in the art that different network elements, messaging, protocols, and/or the like may be varied while remaining within the scope of the present invention.
Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
This application claims the benefit of U.S. Provisional Application No. 61/098,152, filed on Sep. 18, 2008, entitled “System and Method for Provision of IMS Based Services for Legacy CS UE with Home Node B Access,” which application is hereby incorporated herein by reference. This application relates to the following co-pending and commonly assigned patent applications: Ser. No. 12/486,645, filed Jun. 17, 2009, entitled “System and Method for Provision of IMS Based Services for Legacy CS UE with Home Node B Access,” Ser. No. 12/561,825, filed Sep. 17, 2009, entitled “Attach and Handover for IMS Systems for Legacy CS UE with Home Node B Access,” Ser. No. 12/561,850, filed Sept. 17, 2009, entitled “Attach and Handover for IMS Systems for Legacy CS UE with Home Node B Access,” and Ser. No. 12/561,877, filed Sep. 17, 2009, entitled “Attach and Handover for IMS Systems for Legacy CS UE with Home Node B Access,” which applications are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
7366514 | Ejzak | Apr 2008 | B2 |
7522585 | Liu et al. | Apr 2009 | B2 |
7975037 | Tai et al. | Jul 2011 | B2 |
8103267 | Lee et al. | Jan 2012 | B2 |
20040162077 | Kauranen et al. | Aug 2004 | A1 |
20060098598 | Gallagher | May 2006 | A1 |
20060256752 | Svensson et al. | Nov 2006 | A1 |
20060268849 | Larsson et al. | Nov 2006 | A1 |
20060281459 | Marinescu et al. | Dec 2006 | A1 |
20070058788 | Mahdi et al. | Mar 2007 | A1 |
20070061397 | Gregorat et al. | Mar 2007 | A1 |
20070121608 | Gu et al. | May 2007 | A1 |
20070213078 | Shaheen | Sep 2007 | A1 |
20070281717 | Bharadwaj | Dec 2007 | A1 |
20080009287 | Donovan et al. | Jan 2008 | A1 |
20080032695 | Zhu et al. | Feb 2008 | A1 |
20080090570 | Deshpande et al. | Apr 2008 | A1 |
20080117878 | Kim et al. | May 2008 | A1 |
20080181205 | Azada et al. | Jul 2008 | A1 |
20080291874 | Bae et al. | Nov 2008 | A1 |
20080316998 | Procopio et al. | Dec 2008 | A1 |
20090086719 | Mutikainen et al. | Apr 2009 | A1 |
20090104905 | DiGirolamo et al. | Apr 2009 | A1 |
20090147754 | Long et al. | Jun 2009 | A1 |
20090156213 | Spinelli et al. | Jun 2009 | A1 |
20090257418 | Allen et al. | Oct 2009 | A1 |
20090265543 | Khetawat et al. | Oct 2009 | A1 |
20100041405 | Gallagher et al. | Feb 2010 | A1 |
20100048216 | Sundarraman et al. | Feb 2010 | A1 |
20100069101 | Mahdi et al. | Mar 2010 | A1 |
20100074223 | Mahdi | Mar 2010 | A1 |
20100074224 | Mahdi et al. | Mar 2010 | A1 |
20100077459 | Mahdi et al. | Mar 2010 | A1 |
20100238920 | Salkintzis et al. | Sep 2010 | A1 |
20100293265 | Lindholm et al. | Nov 2010 | A1 |
20100309822 | Witzel et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
1756242 | Apr 2006 | CN |
1870553 | Nov 2006 | CN |
101061729 | Oct 2007 | CN |
101166133 | Apr 2008 | CN |
101212386 | Jul 2008 | CN |
101262656 | Sep 2008 | CN |
1 909 438 | Apr 2008 | EP |
WO 0189251 | Nov 2001 | WO |
WO 2007009298 | Jan 2007 | WO |
WO 2008081310 | Jul 2008 | WO |
WO 2010031349 | Mar 2010 | WO |
Entry |
---|
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Handover procedures,” Release 7, 3GPP TS 23.009 V7.0.0, Mar. 2007, pp. 1-287. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Handover procedures,” Release 8, 3GPP TS 23.009 V8.1.0, Mar. 2009, pp. 1-289. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access,” Stage 2, Release 8, 3GPP TS 23.204 V8.2.0, Jun. 2008, pp. 1-37. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access,” Stage 2, Release 8, 3GPP TS 23.204 V8.4.0, Mar. 2009, pp. 1-37. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Single Radio Voice Call Continuity (SRVCC),” Stage 2, Release 8, 3GPP TS 23.216 V8.0.0, Jun. 2008, pp. 1-20. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Single Radio Voice Call Continuity (SRVCC),” Stage 2, Release 9, 3GPP TS 23.216 V9.0.0, Jun. 2009, pp. 1-39. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS),” Stage 2, Release 8, 3GPP TS 23.228 V8.5.0, Jun. 2008, pp. 1-240. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS),” Stage 2, Release 9, 3GPP TS 23.228 V9.0.0, Jun. 2009, pp. 1-250. |
3rd Generation Partnership Project, Technical Specification Group Services and Architecture, “IP Multimedia Subsystem (IMS) Service Continuity,” Stage 2, Release 8, 3GPP TS 23.237 V8.0.0, Jun. 2008, pp. 1-40. |
3rd Generation Partnership Project, Technical Specification Group Services and Architecture, “IP Multimedia Subsystem (IMS) Service Continuity,” Stage 2, Release 9, 3GPP TS 23.237 V9.1.0, Jun. 2009, pp. 1-88. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS) Centralized Services,” Stage 2, Release 8, 3GPP TS 23.292 V8.0.0, Jun. 2008, pp. 1-89. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS) centralized services,” Stage 2, Release 9, 3GPP TS 23.292 V9.2.0, Jun. 2009, pp. 1-105. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IMS Aspects of Architecture for Home NodeB,” Stage 2, Release 9, 3GPP TR 23.832 V0.4.0, May 2009, pp. 1-61. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS) service continuity enhancements; Service, policy and interaction,” Stage 2, Release 9, 3GPP TR 23.838 V9.0.0, Jun. 2009, pp. 1-51. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Mobile radio interface Layer 3 specification; Core network protocols,” Stage 3, Release 8, 3GPP TS 24.008 V8.2.0, Jun. 2008, pp. 1-553. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Mobile radio interface Layer 3 specification; Core network protocols,” Stage 3, Release 8, 3GPP TS 24.008 V8.6.0, Jun. 2009, pp. 1-582. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP),” Stage 3, Release 9, 3GPP TS 24.229 V9.0.0, Jun. 2009, pp. 1-623. |
3rd Generation Partnership Project, Technical Specification Group Radio Access Network, “UTRAN lu interface RANAP signalling,” Release 7, 3GPP TS 25.413 V7.9.0, Jun. 2008, pp. 1-359. |
3rd Generation Partnership Project, Technical Specification Group Radio Access Network, “UTRAN lu interface Radio Access Network Application Part (RANAP) signalling,” Release 8, 3GPP TS 25.413 V8.3.0, Jun. 2009, pp. 1-398. |
3rd Generation Partnership Project, Technical Specification Group Radio Access Network, “UTRAN architecture for 3G Home Node B (HNB),” Stage 2, Release 8, 3GPP TS 25.467 V8.2.0, Jun. 2009, pp. 1-26. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Evolved Packet System; 3GPP EPS Sv interface (MME to MSC) for SRVCC,” Release 8, 3GPP TS 29.280 V1.0.1, Sep. 2008, pp. 1-10. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC,” Release 8, 3GPP TS 29.280 V8.1.0, Mar. 2009, pp. 1-13. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Security aspects of early IP Multimedia Subsystem (IMS),” Release 8, 3GPP TS 33.178 V1.0.0, Mar. 2008, pp. 1-26. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “3GPP System Architecture Evolution (SAE); Security architecture,” Release 8, 3GPP TS 33.401 V8.0.0, Jun. 2008, pp. 1-45. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “3GPP System Architecture Evolution (SAE); Security architecture,” Release 9, 3GPP TS 33.401 V9.0.0, Jun. 2009, pp. 1-99. |
“International Search Report,” International Application No. PCT/CN2009/074020, Applicant: Huawei Technologies Co., Ltd., et al., Dec. 31, 2009, 4 pages. |
“Written Opinion of the International Searching Authority,” International Application No. PCT/CN2009/074020, Applicant: Huawei Technologies Co., Ltd., et al., Dec. 31, 2009, 5 pages. |
3rd Generation Partnership Project, Technical Specification Group Radio Access Network, “UTRAN lu interface RANAP signalling,” Release 8, 3GPP TS 25.413 V8.0.0, Sep. 2008, pp. 1-374. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “Single Radio Voice Call Continuity (SRVCC),” Stage 2, Release 8, 3GPP TS 23.216 V8.1.0, Sep. 2008, pp. 1-29. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS),” Stage 2, Release 8, 3GPP TS 23.228 V8.6.0, Sep. 2008, pp. 1-241. |
3rd Generation Partnership Project, Technical Specification Group Services and Architecture, “IP Multimedia Subsystem (IMS) Service Continuity,” Stage 2, Release 8, 3GPP TS 23.237 V8.1.0, Sep. 2008, pp. 1-41. |
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, “IP Multimedia Subsystem (IMS) Centralized Services,” Stage 2, Release 8, 3GPP TS 23.292 V8.1.0, Sep. 2008, pp. 1-90. |
3rd Generation Partnership Project, Technical Specification Group Core Network and Terminals, “Mobile radio interface Layer 3 specification; Core network protocols,” Stage 3, Release 8, 3GPP TS 24.008 V8.3.0, Sep. 2008, pp. 1-556. |
PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, International Application No. PCT/CN2009/074027, Huawei Technologies Co. Ltd., et al., Dec. 24, 2009, 10 pages. |
International Search Report and the Written Opinion of the Patent Cooperation Treaty, received in International Application No. PCT/CN2009/074028, Huawei Technologies Co. Ltd., et al., mailed Dec. 31, 2009, 10 pages. |
Zho, X., et al, “Solution to Fixed Mobile Network Convergence: Femtocell,” Mobile Communications, May 2008, No. 6, pp. 59-65. |
Number | Date | Country | |
---|---|---|---|
20100067493 A1 | Mar 2010 | US |
Number | Date | Country | |
---|---|---|---|
61098152 | Sep 2008 | US |