WO2013025554A1 - System to simplify ganc deployments by using voip services - Google Patents

Abstract

An apparatus and method for wireless communications over a generic access network, for example, as recommended by the 3GPP GAN Specifications (e.g., TS 43.318 and TS 44.318) and a VoIP protocol (e.g., SIP RFC 3261), while avoiding access to an MSC and SGSN of HPLMNs are provided.

Description

SYSTEM TO SIMPLIFY GANC DEPLOYMENTS BY USING VOIP SERVICES

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority under 35 U.S. C.

§ 119(e) to U.S. Provisional Application No. 61/523,456, filed August 15, 2011, titled "System to simplify GANC deployments by using VoIP services" and which is incorporated herein by reference.

FIELD

[0002] This disclosure generally relates to apparatus and methods for wireless communications using a Generic Access Network (GAN) and voice over internet protocol (VoIP) protocols. More particularly, the disclosure relates to a method to integrate GAN and VoIP technologies to provide SIP based services to GAN enabled mobile devices.

BACKGROUND

[0003] The 3rd Generation Partnership Project (3GPP) GAN Specification describes a method and apparatus that enables a GAN enabled mobile device such as a smart phone to access mobile circuit switched services via a generic IP based access network, namely the Internet. The Specification describes a network element known as a GAN Controller (GANC). The GANC connects into the Home Public Land Mobile Network (HPLMN 400) via traditional circuit based services interfaces (A and Gb interfaces for a second generation (2G) architecture and Iu-CS and Iu-PS interfaces for third generation (3G) architecture).

[0004] In current systems, voice channels are carried on Tl, El or ATM circuits, which are difficult and expensive to deploy. The current architecture in not conducive to providing a hosted GAN service operated by an independent third party that is not directly affiliated with the Mobile Network Operator (MNO). Specifically, the current architecture is not suitable for third party Mobile Virtual Network Operators (MVNOs) desiring to deploy GAN based services because MVNOs do not have deployed prerequisite mobile switching centers (MSCs 410) and Serving General Packet Radio Service Support Nodes (SGSNs 420), which HPLMNs 400 have in their networks.

[0005] Therefore, what is needed is an architecture for use by an MVNO that limits its connection to the HPLMN 400 only for Authentication and Subscriber management and connects to hardware outside the HPLMN 400 for voice services.

SUMMARY OF THE DISCLOSURE

[0006] Disclosed are apparatus and methods for wireless communications using the 3 GPP GAN Specifications (e.g., TS 43.318 and TS 44.318) and a VoIP protocol (e.g., SIP RFC 3261) and avoiding interfaces to the MSCs and SGSNs of HPLMNs.

[0007] Disclosed are an apparatus and method for implementing a GANC so that it no longer interconnects with the HPLMN 400 at the standard reference interface points (A and Gb interfaces for 2G networks, or Iu-CS and Iu-PS interfaces for 3G networks) but instead incorporates the additional functions of an MSC 410, VLR, SIP Registrar and SIP Server. The only required interconnect to the HPLMN 400 is a MAP-D interface to the Home Location Register (HLR 430) in order to retrieve: (1) the Subscriber profile; (2) Authorization/Ciphering keying data; and (3) Mobile Subscriber Roaming Number (MSRN) for mobile terminated call scenarios. The modified GANC, hereinafter called a Generic Access Network exchange (GANX 500), becomes a peer network to the HPLMN 400 instead of an access network. The disclosure herein is not limited to GAN-enabled mobile devices but can be adopted for other access

mechanisms as well. Hereinafter, any device or system that accesses the GANX 500 for mobile services is referred to as a GAN device (GD 130) (e.g., a GAN-enabled mobile devices, a GAN-enabled user device, a GAN-enabled device, or GD entity). Examples of a GD 130 include: (1) a 2G MS 100 with an embedded GAN Client; (2) 3G UE 120 in combination with a Femtocell or Home Node-B (HnB 110); and (3) a PC running GAN Client software. [0008] According to some aspects, disclosed is a generic access network exchange (GANX) comprising: a D interface to an HL (Home Location Register); a VoIP (voice-over-IP) interface to PSTN (public switched telephone network) via a VoIP gateway; a GAN (generic access network) interface to a GAN-enabled user device (GD); a processor coupled to communicate with the D interface, the VoIP interface and the GAN interface; and memory coupled to the processor, the memory comprising code, when executed by the processor, to control the GANX to perform mobile services.

[0009] According to some aspects, disclosed is a method performed in a generic access network exchange (GANX) for performing mobile services, the method comprising: interfacing to a D interface to an HLR (Home Location Register);

interfacing to a VoIP (voice-over-IP) interface to PSTN (public switched telephone network) via a VoIP gateway; interfacing to a GAN (generic access network) interface to a GAN-enabled user device (GD); performing call control (CC) and mobility management (MM) within the GANX, thereby avoiding an interface to a mobile switching center (MSC); and performing packet services (PS) and GPRS mobility management (GMM) within the GANX, thereby avoiding an interface to an SGSN.

[0010] It is understood that other aspects will become readily apparent to those skilled in the art from the following detailed description, wherein it is shown and described various aspects by way of illustration. The drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1A shows a typical 2G GAN network architecture.

[0012] FIG. IB shows a typical 3G GAN network architecture.

[0013] FIG. 2 shows network architecture including a GANX, in accordance with some embodiments of the present invention.

[0014] FIG. 3 shows internal stack architecture of a GANX, in accordance with some embodiments of the present invention. [0015] FIG. 4 illustrates a simplified location update message flow, in accordance with some embodiments of the present invention.

[0016] FIG. 5 illustrates a simplified mobile originated call setup message flow, in accordance with some embodiments of the present invention.

[0017] FIG. 6 illustrates a simplified mobile terminated call setup procedure, in accordance with some embodiments of the present invention.

[0018] FIG. 7 shows a GANX, in accordance with some embodiments of the present invention.

[0019] FIG. 8 illustrates a method in a GANX for performing mobile services, in accordance with some embodiments of the present invention.

DETAILED DESCRIPTION

[0020] The detailed description set forth below in connection with the appended drawings is intended as a description of various aspects of the present disclosure and is not intended to represent the only aspects in which the present disclosure may be practiced. Each aspect described in this disclosure is provided merely as an example or illustration of the present disclosure, and should not necessarily be construed as preferred or advantageous over other aspects. The detailed description includes specific details for the purpose of providing a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the present disclosure. Acronyms and other descriptive terminology may be used merely for convenience and clarity and are not intended to limit the scope of the disclosure.

[0021] This disclosure uses the following acronyms:

3G 3rd Generation

3 GPP 3rd Generation Partnership Project

AAA Authentication, Authorization & Accounting

ATM Asynchronous Transfer Mode

CC Call Control

DTAP Direct Transfer Application Process

GAN Generic Access Network

GANC GAN Controller

GANX GAN eXchange

GD GAN-enabled user Device

GPRS General Packet Radio Service

GSM Global System for Mobile communications

HLR Home Location Register

HnB Home Node-B

HPLMN Home PLMN

ISDN Integrated Services Digital Network

ISUP ISDN User Port

LU Location Update

MAP Mobile Application Part

MM Mobility Management

MNO Mobile Network Operator

MS Mobile Station

MSC Mobile Switching Center

MSRN Mobile Subscriber Roaming Number

MVNO Mobile Virtual Network Operator

PBX Private Branch Exchange

PLMN Public Land Mobile Network

PRI Primary Rate Interface

PSTN Public Switched Telephone Network

SecGW Security Gateway

SGSN Serving GPRS Support Node

SIP Session Initiation Protocol

SS7 Signaling System 7

TS Technical Specification UE User Equipment

VLR Visitor Location Register

VoIP Voice-over-Internet Protocol

] Reference is also made to the following interfaces:

Interface Description

A Interface between a 2G GAN Controller and an

MSC (see also, 3G Iu-CS interface)

D MAP-D Interface between a GANX and an

HLR

D' MAP-D Interface between a AAA Server and an HLR

Gb Interface between a 2G GAN Controller and a

SGSN (see also, 3G Iu-PS interface)

IPsec Internet Protocol Security

ISDN Interface using Integrated Services Digital

Network

ISUP Interface using SS7 ISDN User Part

Iu-CS Interface between a 3G GAN Controller and an

MSC (see also, 2G A interface)

IuH Encrypted interface between the Security

Gateway and a Generic IP Access Network (e.g., the Internet) (see also 2G Up interface)

IuH' Unencrypted internal interface between a

Security Gateway and a 3G GAN Controller (see also, 2G Up' interface)

Iu-PS Interface between a 3G GAN Controller and a

SGSN (see also, 2G Gb interface)

SIP Interface carrying Session Initiation Protocol

SIP-S Interface carrying SIP security

Up Encrypted interface between a Security

Gateway and a Generic IP Access Network (e.g., the Internet) (see also, 3G IuH interface)

Up^* Unencrypted internal interface between a 2G

GAN Controller and the Security Gateway (see also, 3G IuH' interface)

Wm Interface between the AAA Server and the

Security Gateway [0023] A GANX 500 may interface with wireless communications equipment using the 3 GPP GAN Specifications (e.g., TS 43.318 and TS 44.318) and voice equipment using a VoIP protocol (e.g., SIP RFC 3261). This disclosure describes how to integrate the technologies to provide SIP based services to GAN enabled mobile devices. With the architecture described, an independent third party may offer a hosted GAN service and subscribers would effectively roam onto the GAN network. A GAN service may implement a VoIP protocol, such as SIP, which is better suited for a hosted environment and allows for less expense mobile originate and mobile terminated calls.

[0024] FIG. 1 A shows a typical 2G GAN network architecture. The 2G GAN network architecture includes GAN 300 and a HPLMN 400. The GAN 300 includes a 2G GANC 320, an Authentication, Authorization & Accounting server (AAA server 330), and security gateway (SecGW 310). The architecture also includes a generic IP access network (e.g., the Internet) to one or more 2G MSs 100.

[0025] The HPLMN 400 includes an MSC 410, an SGSN 420 and an HLR 430.

The MSC 410 is the primary service delivery node for circuit based voice services in a GSM network. The MSC 410 uses traditional voice circuits. The SGSN 420 is the primary service delivery node for packet based data services in a GSM network. The HLR 430 is the subscriber database in a GSM network. It contains details of each mobile phone subscriber that is authorized to use the GSM network.

[0026] The 2G GAN network architecture uses several interfaces. An A interface couples the MSC 410 of the HPLMN 400 and the 2G GANC 320. The A interface comprises of multiple Tl or El circuits carrying dedicated 64 Kbit voice channels plus one or more SS7 signaling channels. A Gb interface couples the SGSN 420 of the HPLMN 400 and the 2G GANC 320. The Gb interface consists of El channels carrying Frame Relay packets. Internally to the GAN 300, an Up' interface couples the SecGW 310 and the 2G GANC 320. An Up interface couples the SecGW 310 and a generic IP access network 200 (e.g., the Internet). Also internally to the GAN 300, a Wm interface couples the AAA server and the SecGW 310. A D' interface couples the HLR 430 of the HPLMN 400 and the AAA server 330. A D' interface differs from a D interface in that the D' interface carries a subset of commands found on a D interface. [0027] On the access side, a 2G MS 100 includes an embedded GAN client and communicates with the 2G GANC 320 via a SecGW 310. Typically, the 2G MS 100 accesses the network over a WiFi Access Point connected to the Internet. The 2G MS 100 communicates with the SecGW 310 via the Up interface. The SecGW 310 translates between the encrypted Up interface (to the 2G MS 100) and the unencrypted Up' interface (to the 2G GANC 320). The SecGW 310 includes a radius based Wm interface to the AAA server 330. The AAA server 330 provides a bridge between the SecGW 310 and the HLR 430. It forwards the keying material provided by the HLR 430 to the SecGW 310. Keying material is used by the SecGW 310 to encrypt the Up Interface.

[0028] FIG. IB shows a typical 3G GAN network architecture. The typical 3G

GAN network architecture is similar to the typical 2G GAN network architecture discussed above but with different interfaces. The 3G GAN network architecture includes GAN 300 and a HPLMN 400. The GAN 300 includes a 3G GANC 340, an AAA server 330, and SecGW 310. The architecture also includes a generic IP access network (e.g., the Internet) to one or more UEs 120 via an HnB 110.

[0029] The 3G GAN network architecture includes interfaces replacing those used in the 2G GAN network architecture. An Iu-CS interface (rather that an A interface) couples the MSC 410 of the HPLMN 400 and the 2G GANC 320. An Iu-PS interface (rather that a Gb interface) couples the SGSN 420 of the HPLMN 400 and the 3G GANC 340. The Iu-CS interface allows for circuit switched voice services and the Iu-PS interface allows for packet switched data services. Both the Iu-CS and Iu-PS interfaces comprise ATM circuits that terminate on the MSC 410 and SGSN 420, respectively. Internally to the GAN 300, an IuH' interface (rather that an Up' interface) couples the SecGW 310 and the 3G GANC 340. An IuH interface (rather that an Up interface) couples the SecGW 310 and a generic IP access network 200 (e.g., the Internet). As before, a Wm interface couples the AAA server and the SecGW 310, and a D' interface couples the HLR 430 of the HPLMN 400 and the AAA server 330.

[0030] On the access side, a 3G UE 120 communicates over the UMTS air interface to an HnB 110, which in turn communicates with the 3G GANC 340 through a generic IP Access Network 200 over the IuH interface to the SecGW 310. The SecGW 310 translates data between the encrypted IuH interface and the unencrypted IuH' interface.

[0031] FIG. 2 shows network architecture including a GANX 500, in

accordance with some embodiments of the present invention. The GANX network architecture includes a GANX 500, a HPLMN 400, a SIP GW 600 (or a VoIP GW 602), a PSTN 610 and one or more GD 130 coupled via a generic IP access network (e.g., the Internet).

[0032] The GANX 500 provides the same functionality as the 2G GANC 320 in

FIG. 1A and the 3G GANC 340 in FIG. IB. In addition, the GANX 500 also provides the functionality of the MSC 410 and SGSN 420. Therefore, interfaces to an external MSC 410 and SGSN 420 of an HPLMN 400 are no longer required. In addition, instead of using traditional voice circuits on an MSC 410, the GANX 500 uses VoIP with a gateway. For example, a SIP interface may be used to communicate voice traffic with a SIP gateway (SIP GW 600). Generally, a VoIP gateway (VoIP GW 602) is used to communicate voice traffic, however, SIP GW 600 is used as a specific example below.

[0033] The GANX 500 includes a VoIP interface, a GAN interface and a D interface. The VoIP interface may be a SIP interface or a SIP-S interface (e.g., using TLS public key encryption). The GAN interface may support an Up interface, an IuH interface or both. The D interface couples the GANX 500 to an HL 430 of the

HPLMN 400. As explained above, the GANX 500 does not need an interface to an MSC 410 or an SGSN 420.

[0034] The GANX 500 modifies the standard GANC specified in 3 GPP by incorporating functions of the MSC 410 and SGSN 420 so that it is no longer an Access Node in the PLMN; instead it becomes a combined Access and Core Network Node.

[0035] In addition, instead of converting the IP based voice into circuit based voice as in the 3GPP standard GANC, the GANX 500 keeps the voice IP based and converts it to a standard VoIP service such as SIP. As a result the GANX can be deployed on standard computer server equipment and unlike the 3 GPP standard GANC does not require expensive dedicated hardware and expensive dedicated voice circuits. [0036] Multiple GANX 500 systems may be installed in a network that shares a central VL , which is accessed via a MAP-GW function 510. The GANX 500 provides call routing functionality and switches calls locally either between two registered GDs 130 or between a GD 130 and a POTS telephone via the SIP GW 600. That is, POTS telephone calls are routed via the SIP GW 600. The SIP GW 600 routes calls via one or more private/enterprise gateways to a private branch exchange (PBX) (not shown) or via public SIP gateways to a PSTN 610. The SIP GW 600 may be external or internal to a GANX operator. That is, the GANX operator may contract with one or more third- party SIP providers to route calls through their SIP GWs 600. Alternatively or in addition to, the GANX operator may implement its own SIP GW 600, thereby providing a direct route to mobiles registered in the macro PLMN and optimizing call routing.

[0037] FIG. 3 shows internal stack architecture of a GANX 500, in accordance with some embodiments of the present invention. As with the standard GAN protocols, the GD 130 sets up a secure IP (IPsec) tunnel with a security gateway function (shown as "Sec GW"). The GANX 500 also sets up a SIP interface between a SIP server function (shown as "SIP Server") and an external SIP GW 600. Keying material for the IPsec tunnel is generated by the HLR 430 using MAP-D over SS7, which is accessed via a MAP-GW function 510. The MAP-GW function 510 communicates to an VLR function using MAP-D over TCP and also communicates to the Sec GW function through the radius gateway function (shown as "Radius GW) using MAP-D over TCP.

[0038] Once the IPsec tunnel is setup, one of a number of low level handlers handles messaging between the GANX 500 and the GD 130. A GAN Handler function, which operates over TCP/IP, handles traffic with any 2G MS 100. An IuH Handler function, which operates over SCTP, handles traffic with any 3G UE 120. These low level handlers pass a higher layer message onto a common message handler function (shown as "Msg Handler") which in turn invokes specific handlers for call control functions (shown as "CC Handler") or mobility management functions (shown as "MM Handler"). A mobile originator handler function (shown as "MO Handler") provides state machine logic to handle mobile originated calls from the GD 130. The mobile terminated handler function (shown as "MT Handler") provides state machine logic to handle mobile terminated calls to the GD 130. The SIP Registrar function provides a database of all currently registered GDs 130. The VLR function is a database of subscriber profiles provided by the HLR 430 during location update procedures.

[0039] FIGS. 4, 5 and 6 show various message flows. Numerous messages have been omitted from these message flows to focus on the functionality of the GANX 500.

[0040] FIG. 4 illustrates a simplified location update (LU) message flow, in accordance with some embodiments of the present invention. The simplified Location Update Procedure is further described in 3GPP TS 24.008, which also includes identity, authentication and ciphering procedures.

[0041 ] The GD 130 initiates ( 1 ) an LU procedure with a GANX 500 over a generic IP access network 200. On receipt of the LU Request, the GANX 500 performs a standard LU operation. In addition, the GANX 500 also performs (2) a SIP

registration procedure and a SIP publication procedure with the internal SIP Registrar function. In some embodiments, the SIP Registrar function co-exists with the VLR function. The GANX 500 then sends (3) a MAP Update Location message to the HLR 430 within the HPLMN 400 so that the appropriate HLR 430 record is updated for MT calls. The HLR 430 sends (4) a MAP Insert Subscriber Data message to the GANX 500, which informs the GANX 500 about the subscriber's profile (including for example, MS ISDN, Call forward settings, Call barring settings, etc.). Finally, the GANX 500 sends (5) a LU Accept message to the GD 130 to complete the procedure. The SIP publication procedure is optional but provides Presence Information. This Presence Information may be used in a smart contact list on a Smart Phone. In some

embodiments, the Caller will know if the Callee is available to take calls before he/she dials a phone number.

[0042] FIG. 5 illustrates a simplified mobile originated (MO) call setup message flow, in accordance with some embodiments of the present invention. The interface between the SIP Gateway and the PSTN could be one of a number of possible protocols (e.g PRI-ISDN or ISUP). In this embodiment, the PRI-ISDN has been selected as an example. [0043] Initially, the GANX 500 receives (1) a DTAP-Setup message from the

GD 130 containing the dialed digits. The GANX 500 (2) extracts the dialed digits from the message and compares the digits with a pre-configured routing table. That is, the GANX 500 examines the dial plan and selects a route.

[0044] At this point the call may be switched locally within the GANX 500 or forwarded to an external SIP Gateway 600. Assuming a SIP Gateway 600 has been selected, the DTAP-SETUP message is mapped to a SIP-INVITE message. The GANX 500 sends (3) the SIP-INVITE message to the SIP Gateway 600. The SIP Gateway 600 will translate the SIP-INVITE to a PSTN based protocol to continue the call setup. The SIP Gateway 600 sends (4) a SETUP message to and receives (5) an ALERT message from the PSTN 610. At this point during the call setup, the SIP Gateway 600 is notified that the Called Party's phone is ringing. In turn, the SIP Gateway 600 sends (6) a SIP- Ringing message to the GANX 500 to notify the Called Party is ringing. The GANX 500 translates the SIP-Ringing message to (7) a DTAP -Alert message and forwards to the Calling GD 130. The SIP Gateway 600 is then notified that the Called Party has answered the call. The SIP Gateway 600 then sends (9) a SIP-200 OK message to the GANX 500 to indicate that the call setup is complete. The GANX 500 translates the SIP-200 OK message to (10) a DTAP-Connect and forwards the message to the GD 130.

[0045] FIG. 6 illustrates a simplified mobile terminated (MT) call setup message flow, in accordance with some embodiments of the present invention. Most of the message flow in this procedure follows routine GSM procedures, however, the flow does not involve the GANX 500. The procedure shown is only provided for clarity and context. After a PSTN 610 provides (1) SETUP message to an MSC 410 and the MSC 410 provides (2) a Send Routing Information (SendRtlnfo) message to an HLR 430, the GANX 500 receives (3) a MAP-Provide-Roaming-Number (ProvideRoamNum) message for a registered GD 130 from the HLR 430. The GANX 500 selects an unallocated MSRN number from its configured pool of MSRNs, allocates this MSRN number to the GD 130 and sends (4) a MAP-Provide-Roaming-Number Result

(ProvideRoamNum Results) message back to the HLR 430 containing the allocated MSRN number. [0046] Next, the HLR 430 sends (5) a MAP-Send-Routing-Info-Result

(SndRtlnfoRes) message to the MSC 410, which sends (6) a SETUP message to the SIP Gateway 600. A short interval later, the GANX 500 receives (7) a SIP-INVITE message from the SIP Gateway 600 with the "To" field set to the allocated MSRN. The GANX 500 sends (8) a Page message to the GD 130 with the allocated MSRN number and the MSRN is returned to the MSRN pool. A number of messages have been omitted from the flow but eventually the GD 130 will start ringing and send (9) a DTAP -ALERT message to the GANX 500. The GANX 500 translates the DTAP- ALERT message to a SIP-Ringing message and forwards (10) the SIP-Ringing message to the SIP Gateway 600. The SIP Gateway 600 sends (11) an ALERT message to the MSC 410, which forwards (12) an ALERT message to the PSTN 610. When the Subscriber answers the ringing, the GD 130 sends a (13) DTAP-CONNECT message to the GANX 500. The GANX 500 translates the DTAP-CONNECT message to a SIP-200 OK message and forwards (14) the SIP-200 OK message to the SIP Gateway 600. In turn, the SIP Gateway 600 sends (15) a Connect message to the MSC 410 which forwards (16) a Connect message to the PSTN 610.

[0047] FIG. 7 shows a GANX 500, in accordance with some embodiments of the present invention. The GANX 500 comprises a D interface 520 to an HLR 430, a VoIP interface 530 to PSTN 610 via a VoIP gateway 602, a GAN interface 540 to a GD 130, a processor 550 coupled to communicate with the D interface 520, the VoIP interface 530 and the GAN interface 540, and a memory 560 coupled to the processor. The memory 560 comprising code 570, when executed by the processor, to control the GANX 500 to perform mobile services.

[0048] The VoIP gateway 602 may comprise a SIP gateway 600 and the VoIP interface may comprise a SIP interface to the SIP gateway 600. The GAN interface 540 may comprise a TCP/IP interface, wherein the TCP/IP interface may comprise an Up interface. Alternatively, the GAN interface 540 may comprise a SCTP/IP interface, wherein the SCTP/IP interface may comprise an IuH interface. Alternatively, the GAN interface 540 may comprise both a TCP/IP interface and a SCTP/IP interface. The GD 130 may belong to an HPLMN. [0049] The mobile services may comprise call control (CC) and mobility management (MM) within the GANX, thereby avoiding an interface to an MSC. The code may comprise code for packet services (PS) and GPRS mobility management (GMM) within the GANX, thereby avoiding an interface to an SGSN.

[0050] The mobile services may comprise a Location Update (LU) procedure.

The code to perform mobile services may comprise code to perform location update, which may comprise: (1) code to receive a location update (LU) message from the GD 130; (2) code to send an Update Location message, to support mobile terminated (MT) calls, to an HLR within the HPLMN, in response to receiving the LU message from the GD 130; (3) code to receive from the HLR an insert subscriber data message comprising a subscriber's profile; and (4) code to send an LU accept message to the GD 130, in response to receiving the insert subscriber data message.

[0051] The mobile services may comprise a mobile originated call, which may include: (1) code to receive a SETUP message, comprising dialed digits, from the GD; (2) code to send an INVITE message to the PSTN via the gateway, in response to receiving the SETUP message from the GD 130; (3) code to receive from the PSTN via the gateway a RINGING message; (4) code to send an ALERT message to the GD, in response to receiving the RINGING message; code to receive from the PSTN via the gateway an OK message; and (5) code to send a CONNECT message to the GD, in response to receiving the OK message.

[0052] The mobile services may comprise a mobile terminated call, which may include: (1) code to receive a PROVIDE-ROAM-NUM message, comprising a roaming number, from an HLR; (2) code to send a PROVIDE-ROAM-NUM RESULT message to the HLR; (3) code to receive from a gateway an INVITE message; (4) code to send a PAGE message to the GD, in response to receiving the INVITE message; (5) code to receive from the GD an ALERT message; (6) code to send to an MSC, via the gateway, a RINGING message; (7) code to receive a CONNECT message from the GD; and (8) code to send to the MSC, via the gateway, an OK message.

[0053] FIG. 8 illustrates a method 700 in a GANX for performing mobile services, in accordance with some embodiments of the present invention. At 710, the GANX 500 interfaces to a D interface to an HLR (Home Location Register). At 720, the GANX 500 interfaces to a VoIP (voice-over-IP) interface to PSTN (public switched telephone network) via a VoIP gateway. At 730, the GANX 500 interfaces to a GAN (generic access network) interface to a GAN-enabled user device (GD). At 740, the GANX 500 performs call control (CC) and mobility management (MM) within the GANX, thereby avoiding an interface to a mobile switching center (MSC). At 750, the GANX 500 performs packet services (PS) and GPRS mobility management (GMM) within the GANX, thereby avoiding an interface to an SGSN.

[0054] The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various

modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure.

Claims

1. A generic access network exchange (GANX) comprising: a D interface to an HL (Home Location Register); a VoIP (voice-over-IP) interface to PSTN (public switched telephone network) via a VoIP gateway; a GAN (generic access network) interface to a GAN-enabled user device (GD); a processor coupled to communicate with the D interface, the VoIP interface and the GAN interface; and memory coupled to the processor, the memory comprising code, when executed by the processor, to control the GANX to perform mobile services.

2. The GANX of claim 1, wherein the VoIP gateway comprising a SIP gateway and the VoIP interface comprises a SIP interface to the SIP gateway.

3. The GANX of claim 1, wherein the GAN interface comprises a TCP/IP interface.

4. The GANX of claim 3, wherein the TCP/IP interface comprises an Up interface.

5. The GANX of claim 1, wherein the GAN interface comprises a SCTP/IP interface.

6. The GANX of claim 5, wherein the SCTP/IP interface comprises an IuH interface.

7. The GANX of claim 1, wherein the GAN interface comprises both a TCP/IP interface and a SCTP/IP interface.

8. The GANX of claim 1 , wherein the GD belonging to an HPLMN

(Home Public Land Mobile Network).

9. The GANX of claim 1 , wherein the code to control the GANX further comprises code for call control (CC) and mobility management (MM) within the GANX, thereby avoiding an interface to a mobile switching center (MSC).

10. The GANX of claim 1, wherein the code to control the GANX further comprises code for packet services (PS) and GPRS mobility management (GMM) within the GANX, thereby avoiding an interface to an SGSN.

11. The GANX of claim 1 , wherein the mobile services comprises a Location Update (LU) procedure.

12. The GANX of claim 11, wherein the code to perform the

Location Update (LU) procedure comprises: code to receive a location update (LU) message from the GD; code to send a location update (LU) message, to support mobile terminated (MT) calls, to an HLR within the HPLMN, in response to receiving the LU message from the GD; code to receive from the HLR an insert subscriber data message comprising a subscriber's profile; and code to send an LU accept message to the GD, in response to receiving the insert subscriber data message.

13. The GANX of claim 1, wherein the memory further comprises code, when executed by the processor, to control the GANX to perform a mobile originated call.

14. The GANX of claim 13, wherein the code to perform the mobile originated call comprise: code to receive a SETUP message, comprising dialed digits, from the GD; code to send an INVITE message to the PSTN via the VoIP gateway, in response to receiving the SETUP message from the GD; code to receive from the PSTN via the VoIP gateway a RINGING message; code to send an ALERT message to the GD, in response to receiving the RINGING message; code to receive from the PSTN via the VoIP gateway an OK message; and code to send a CONNECT message to the GD, in response to receiving the OK message.

15. The GANX of claim 1, wherein the memory further comprises code, when executed by the processor, to control the GANX to perform a mobile terminated call.

16. The GANX of claim 15, wherein the code to perform the mobile terminated call comprise: code to receive a PROVIDE-ROAM-NUM message, comprising a roaming number, from an HLR; code to send a PROVIDE-ROAM-NUM RESULT message to the HLR; code to receive from a VoIP gateway an INVITE message; code to send a PAGE message to the GD, in response to receiving the INVITE message; code to receive from the GD an ALERT message; code to send to an MSC, via the VoIP gateway, a RINGING message; code to receive a CONNECT message from the GD; and code to send to the MSC, via the VoIP gateway, an OK message.

17. A method performed in a generic access network exchange (GANX) for performing mobile services, the method comprising: interfacing to a D interface to an HLR (Home Location Register); interfacing to a VoIP (voice-over-IP) interface to PSTN (public switched telephone network) via a VoIP gateway; interfacing to a GAN (generic access network) interface to a GAN-enabled user device (GD); performing call control (CC) and mobility management (MM) within the GANX, thereby avoiding an interface to a mobile switching center (MSC); and performing packet services (PS) and GPRS mobility management (GMM) within the GANX, thereby avoiding an interface to an SGSN.

18. The method of claim 17, further comprising performing a location update.

19. The method of claim 18, wherein performing the location update comprises: receiving a location update (LU) message from the GD; sending a location update (LU) message, to support mobile terminated (MT) calls, to an HLR within the HPLMN, in response to receiving the LU message from the GD; receiving from the HLR an insert subscriber data message comprising a subscriber's profile; and sending an LU accept message to the GD, in response to receiving the insert subscriber data message.

20. The method of claim 17, further comprising performing a mobile originated call.

21. The method of claim 20, wherein performing the mobile originated call comprises: receiving a SETUP message, comprising dialed digits, from the GD; sending an INVITE message to the PSTN via the VoIP gateway, in response to receiving the SETUP message from the GD; receiving from the PSTN via the VoIP gateway a RINGING message; sending an ALERT message to the GD, in response to receiving the RINGING message; receiving from the PSTN via the VoIP gateway an OK message; and sending a CONNECT message to the GD, in response to receiving the OK message.

22. The method of claim 17, further comprising performing a mobile terminated call.

23. The method of claim 22, wherein performing the mobile terminated call comprises: receiving a PROVIDE-ROAM-NUM message, comprising a roaming number, from an HLR; sending a PROVIDE-ROAM-NUM RESULT message to the HLR; receiving from a VoIP gateway an INVITE message; sending a PAGE message to the GD, in response to receiving the INVITE message; receiving from the GD an ALERT message; sending to an MSC, via the VoIP gateway, a RINGING message; receiving a CONNECT message from the GD; and sending to the MSC, via the VoIP gateway, an OK message.

24. The method of claim 17, wherein the VoIP gateway comprising a SIP gateway and the VoIP interface comprises a SIP interface to the SIP gateway.

25. The method of claim 17, wherein the GAN interface comprises both a TCP/IP interface and a SCTP/IP interface.