Generic access to the iu interface

GENERIC ACCESS TO THE IU INTERFACE

<u>Claims of interest in related applications</u>

This application is filed on July 14, 2006, and is entitled "E-UMA Technology" in US Provisional Application Nos. 60/807,470; U.S. Provisional Application No. 60/823,092, filed August 21, 2006 and entitled "Generic Access to the Iu Interface"; U.S. Provisional Application No. 60/862,564, filed October 23, 2006 and entitled "E-UMA-Generic Access to the Iu Interface"; and U.S. Provisional Application No. 60/949,826, filed July 13, 2007, entitled "Generic Access to the Iu Interface." The contents of each of these four provisional applications are hereby incorporated by reference.

The field of the present invention relates generally to telecommunications. In particular, the present invention relates to a mechanism for extending an Unlicensed Mobile Access (UMA) or Generic Access Network (GAN) to interoperate with a GSM core network using a UMTS (Universal Mobile Telecommunication System) Iu interface.

Licensed wireless systems use wireless transceivers to provide mobile wireless communications to individuals. Licensed wireless system refers to a public cellular telephone system and/or a Personal Communication Services (PCS) telephone system. Radio transceivers include cellular telephones, PCS telephones, wireless personal digital assistants, wireless modems, and the like.

Licensed radio systems use radio signal frequencies licensed by the government. A large fee is paid for access to these frequencies. Expensive base station (BS) equipment is used to support communication on licensed frequencies. Base stations are typically installed approximately one mile apart from each other (eg, cellular towers within a cellular network). The radio transmission mechanisms and frequencies used by typical licensed radio systems limit the data rate and range. As a result, the quality of service (voice quality and data rate) in licensed wireless systems is significantly inferior to that provided by landline (wired) connections. Accordingly, users of licensed wireless systems pay relatively high rates for relatively low quality services.

Landline (wired) connections are widely deployed and generally perform high-quality voice and high-speed data services at low cost. The problem with landline access is that it limits the user's mobility. Traditionally, a physical connection to the landline was required.

Over the past few years, the use of unlicensed wireless communication systems to facilitate mobile access to landline-based networks has grown rapidly. For example, such an unlicensed wireless system may support wireless communication based on the IEEE802.11a, b or g standard (WiFi), or the Bluetooth® standard. The mobility ranges associated with these systems are typically on the order of 100 meters or less. A typical unlicensed wireless communication system includes a base station having a wireless access point (AP) with a physical connection (eg, coaxial, twisted pair, or optical cable) to a landline-based network. The AP has an RF transceiver to facilitate communication with a wireless handset operating within a reasonable distance of the AP, and the data rates supported by the WiFi and Bluetooth® standards are much higher than those supported by the licensed wireless systems described above. . Thus, this option provides high-quality service at low cost, but the service only extends a reasonable distance from the base station.

Currently, technologies are being developed to seamlessly integrate the use of licensed and unlicensed wireless systems, so that users can access unlicensed wireless systems within the range of these systems through a single handset, and the range of unlicensed wireless systems. Access the licensed wireless system when leaving

Some embodiments provide a method for registering a user equipment (UE) in a communication system including a licensed wireless communication system and a general access network (GAN) with a general access network controller (GANC). The method sends a registration request message from the UE to the GANC indicating the GAN mode capability of A/Gb only for the UE. When GANC has GAN mode capability of A/Gb, GANC registers UE with GAN. When the GANC has Iu only GAN mode capability, the GANC rejects the registration request message. When the GANC has GAN mode capability of both A/Gb and Iu, the GANC registers the UE based on a set of GANC mode selection rules that the GANC applies to register UEs with the GAN.

Some embodiments provide a method of activating a packet transport channel (PTC) in a communication system including a first licensed wireless communication system and a second general access network (GAN) having a general access network controller (GANC). The GANC is communicatively connected to a first communication system via a UTRAN (Universal Mobile Telecommunication System (UMTS) terrestrial radio access network) Iu interface. The method involves a GA-PSR activation PTC request message from the GANC to a user equipment (UE). The message contains the terminal endpoint identifier (TEID) that the GANC assigns to the UE.

Some embodiments provide for a communication system comprising a first licensed wireless communication system and a second general access network (GAN) comprising a general access network controller (GANC). The GANC is communicatively connected to the first communication system via a universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN) Iu interface. The communication system also includes user equipment (UE). GANC includes a UDP protocol layer and a GTP-U protocol layer above the UDP protocol layer of GANC. The UE includes a UDP protocol layer and a GTP-U protocol layer above the UDP protocol layer of the UE. The UDP protocol layer of the GANC is communicatively coupled to the UDP protocol layer of the UE. The GTP-U protocol layer of the GANC is communicatively coupled to the GTP-U protocol layer of the UE.

The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, various embodiments of the present invention are set forth in the drawings that follow.

1 illustrates an integrated communications system (ICS) of some embodiments;

2 illustrates several applications of ICS in some embodiments.

3 illustrates the overall A/Gb-mode GAN functional architecture of some embodiments.

4 illustrates the overall Iu-mode GAN functional architecture of some embodiments.

5 illustrates the basic elements of a femtocell system architecture with an asynchronous transfer mode based Iu interface towards a core network in some embodiments.

6 illustrates the basic elements of a femtocell system architecture with an Iu interface towards an IP based core network in some embodiments.

7 illustrates a CS domain control plane architecture of some embodiments.

8 illustrates a CS domain control plane architecture of some embodiments.

9 illustrates a CS domain control plane architecture of some embodiments.

10 illustrates a UE CS domain control plane architecture of some embodiments.

11 illustrates a CS domain user plane protocol architecture of some embodiments.

12 illustrates a CS domain user plane protocol architecture of some embodiments.

13 illustrates a UE CS domain user plane architecture of some embodiments.

14 illustrates a PS domain control plane architecture of some embodiments.

15 illustrates a PS domain control plane architecture of some embodiments.

16 illustrates a UE PS domain control architecture of some embodiments.

17 illustrates a PS domain user plane protocol architecture of some embodiments.

18 illustrates a PS domain user plane protocol architecture of some embodiments.

19 illustrates a PS domain user plane protocol architecture of some embodiments.

20 illustrates a UE PS domain user plane architecture of some embodiments.

21 illustrates a state diagram for general access at a UE in some embodiments.

22 illustrates a GAN security mechanism of some embodiments.

23 illustrates a discovery procedure of some embodiments.

24 illustrates a registration procedure in some embodiments.

25 illustrates UE-initiated de-registration in some embodiments.

26 illustrates a registration minimum initiated by GANC in some embodiments.

27 illustrates a registration update uplink in some embodiments.

28 illustrates a registration update downlink in some embodiments.

29 illustrates a keep-alive procedure of some embodiments.

30 illustrates cell broadcast information in some embodiments.

31 illustrates GA-CSR connection establishment of some embodiments.

32 illustrates a GA-CSR connection release in some embodiments.

33 illustrates secure mode control in some embodiments.

34 illustrates core network-UE NAS signaling in some embodiments.

35 illustrates UE-core network NAS signaling in some embodiments.

36 illustrates a mobile terminal originating CS call in some embodiments;

37 illustrates a mobile terminal originating CS call in some embodiments;

38 illustrates a mobile station terminating CS call in some embodiments.

39 illustrates UE initiated CS call clearing in some embodiments.

40 illustrates CS handover from GERAN to GAN in some embodiments.

41 illustrates an alternative procedure performed during GERAN-GAN in some embodiments.

42 illustrates CS handover from UTRAN to GAN in some embodiments.

43 illustrates an alternative procedure performed during UTRAN-GAN in these embodiments.

44 illustrates CS handover from GAN to GERAN in some embodiments.

45 illustrates CS handover from GAN to UTRAN in some embodiments.

46 illustrates GA-PSR connection establishment in some embodiments.

47 illustrates a GA-PSR connection release of some embodiments.

48 illustrates a message flow for PS security mode control in some embodiments.

49 illustrates core network-user equipment PS NAS signaling in some embodiments.

50 illustrates user equipment-core network NAS signaling in some embodiments.

51 illustrates PTC initial activation in some embodiments.

52 illustrates PTC data transmission in some embodiments.

53 illustrates UE initiated PTC active release in some embodiments.

54 illustrates UE initiated PTC re-activation in some embodiments.

55 illustrates a network initiated PTC activation release in some embodiments.

56 illustrates network initiated PTC re-activation in some embodiments.

57 illustrates an implicit PTC activation release in some embodiments.

58 illustrates PDP context activation in some embodiments.

59 illustrates network requested PDP context activation in some embodiments.

60 illustrates a UTRAN-GAN SRNS relocation preparation step in some embodiments.

61 illustrates a UTRAN-GAN SRNS relocation execution step in some embodiments.

62 illustrates a GAN-UTRAN SRNS relocation preparation step in some embodiments.

63 illustrates a GAN-UTRAN SRNS relocation execution step of some embodiments.

64 illustrates a GAN architecture supporting a CS domain control plane in some embodiments.

65 illustrates a GAN protocol architecture supporting the CS domain user plane in some embodiments.

66 illustrates a GAN architecture supporting a PS domain control plane in some embodiments.

67 illustrates a GAN architecture for the PS domain user plane in some embodiments.

68 illustrates a GA-RC sublayer within a UE in some embodiments.

69 illustrates successful (and unsuccessful) establishment of a GA-RRC connection when initiated by a UE in some embodiments.

70 illustrates successful establishment of a GA-RRC connection when initiated by a network in some embodiments.

71 illustrates the release of a logical GA-RRC connection between a UE and a GANC in some embodiments.

72 illustrates a message flow for secure mode control in some embodiments.

73 illustrates a core network-UE NAS signaling of some embodiments.

74 illustrates UE-core network NAS signaling of some embodiments.

75 is a diagram illustrating a mobile terminal originating CS call procedure in some embodiments.

76 illustrates an alternative procedure performed during a mobile station originating CS call in some embodiments.

77 illustrates a mobile station terminating CS call procedure in some embodiments.

78 illustrates call clearing initiated by a UE in some embodiments.

79 illustrates a CS handover procedure from GERAN to GAN in some embodiments.

80 illustrates an alternative procedure for CS handover from GERAN to GAN in some embodiments.

81 illustrates a CS handover procedure from UTRAN to GAN in some embodiments.

82 illustrates an alternative procedure for CS handover from UTRAN to GAN using RRC protocol in some embodiments.

83 illustrates a CS handover procedure from GAN to GERAN in some embodiments.

84 illustrates a CS handover procedure from GAN to UTRAN in some embodiments.

85 illustrates a packet transport channel initial activation procedure in some embodiments.

86 illustrates transmission of a GPRS user data packet over a GAN packet transport channel in some embodiments.

87 illustrates a scenario when the user equipment de-activates the packet transport channel after the PTC timer expires in some embodiments.

88 illustrates a scenario when user equipment initiates reactivation of a packet transport channel in some embodiments;

89 illustrates a scenario when the network initiates deactivation of a packet transport channel in some embodiments.

FIG. 90 illustrates a scenario when the network initiates reactivation of a packet transport channel in some embodiments.

91 illustrates a successful user equipment initiated PDP context activation procedure in some embodiments.

92 illustrates a successful network-requested PDP context activation procedure in some embodiments.

93 illustrates a successful UE-initiated PDP context activation procedure in some embodiments.

94 illustrates an SRNS relocation procedure from UTRAN to GAN for a UE in PMM connected state in some embodiments.

95 is a conceptual illustration of a computer system embodying some embodiments of the present invention;

96 illustrates an inherent PTC activity release procedure in some embodiments.

In the following detailed description of the invention, many details, examples, and embodiments of the invention are set forth. However, it will be apparent and apparent to those skilled in the art that the present invention is not limited to the described embodiments and that the present invention may be practiced without the specific details and examples described.

Throughout the following description, acronyms commonly used in the field of telecommunications for wireless services are used together with the acronyms specific to the present invention. A table of acronyms used in this application is included in Section IX.

Some embodiments provide a method for registering a user equipment (UE) with a communication system comprising a licensed wireless communication system and a general access network (GAN) having a general access network controller (GANC). The method sends a registration request message from the UE to the GANC indicating the GAN mode capability of A/Gb only for the UE. If GANC has GAN mode capability of A/Gb, GANC registers UE with GAN. If the GANC has only Iu GAN mode capability, the GANC rejects the registration request message. If the GANC has GAN mode capability of A/Gb and Iu, the GANC registers the UE based on a set of GANC mode selection rules that it applies to register the UE with the GAN.

Some embodiments provide a method of activating a packet transport channel (PTC) in a communication system comprising a first licensed wireless communication system and a second general access network (GAN) having a general access network controller (GANC). The GANC is communicatively connected to the first communication system via a universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN) Iu interface. The method sends a GA-PSR activation PTC request message from the GANC to the user equipment (UE). The message includes a terminal endpoint identifier (TEID) assigned to the UE by the GANC.

Some embodiments provide a communication system that includes a first licensed wireless communication system, a second general access network (GAN) that includes a general access network controller (GANC). The GANC is communicatively connected to the first communication system via a universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN) Iu interface. The communication system also includes user equipment (UE). GANC includes a UDP protocol layer and a GTP-U protocol layer on top of the UDP protocol layer of GANC. The UE includes a UDP protocol layer and a GTP-U protocol layer above the UDP protocol layer of the UE. The UDP protocol layer of the GANC is communicatively coupled to the UDP protocol layer of the UE. The GTP-U protocol layer of the GANC is communicatively coupled to the GTP-U protocol layer of the UE.

Several more detailed embodiments of the present invention are described in the following sections. Specifically, Section I describes the entire integrated communication system in which several embodiments are included. Description in Section I Following the description in Section II, functional entities of some embodiments are described. Next, Section III describes the control and user plane architecture of some embodiments. Section IV next describes the general access network (GAN) security mechanism of some embodiments.

Next, Section V describes high-level procedures such as discovery, registration, authentication, handover, etc. of some embodiments. Section VI next describes configuration information of some embodiments. Next, the identifiers used in the GAN are provided in Section VII. An alternative embodiment using the same protocol for voice and data services is disclosed in Section VIII. Section IX of a computer system implementing some embodiments of the invention is described. Finally, Section X lists the abbreviations used.

I. Whole system

A. Integrated Communications Systems (ICS)

1 illustrates an integrated communications system (ICS) architecture 100 in accordance with some embodiments of the present invention. ICS architecture 100 allows user equipment (UE) 102 to perform voice and make it possible to access the data network 165 . In some embodiments, the communication session includes a voice service, a data service, or both.

The mobile core network 165 includes one or more Home Location Registers (HLRs) 150 and a database 145 for subscriber authentication and authorization. Once authorized, UE 102 can access voice and data services of mobile core network 165 . To provide these services, the mobile core network 165 includes a mobile switching center (MSC) 160 for providing access to voice services. Data services are provided through a Serving General Packet Radio Service (SGPR) Support Node (SGSN) 155 along with a gateway such as a Gateway GPRS Support Node (GGSN) 157 .

SGSN 155 typically functions to forward data packets to GGSN 157 and user equipment within the geographic service area of SGSN 155 . Additionally, the SGSN 155 may perform functions such as mobility management, user profile storage, and location information storage. However, the actual interface from the mobile core network 165 to various external data packet service networks (eg, the public Internet) is facilitated by the GGSN 157 . The role of the GGSN 157 is to function as a gateway within this packet service network as data packets from user equipment are typically not in a format that accesses external data networks. In this manner, GGSN 157 provides addressing for data packets that are forwarded to UE 102 and an external packet service network (not shown). Also, as the user equipment of the licensed wireless network traverses multiple service areas, and thus multiple SGSNs, the role of the GGSN 157 is to provide a static gateway to the external data network.

In the illustrated embodiment, components common to a UMTS Terrestrial Radio Access Nentwork (UTRAN) based cellular network 185 are shown, which components each licensed radio link 106 (eg, a radio frequency within the licensed bandwidth). It includes a number of base stations, referred to as Node Bs 180 (only one is shown for simplicity) that facilitate wireless communication services to various user equipment 102 over the radio links used). However, those skilled in the art will appreciate that in some embodiments the licensed wireless network may include other licensed wireless networks such as GSM/EDGE Radio Access Network (GERAN). An example of a system using the A and Gb interfaces to access the GERAN is shown in FIG. 3 below.

The licensed radio channel 106 may include licensed radio services with UTRAN or GERAN interface protocols defined for voice/data networks (eg, Iu-cs and Iu-ps interfaces for UTRAN or Gb interfaces for GERAN). can The UTRAN 185 typically includes at least one Node B 180 and a radio network controller (RNC) 175 for managing the set of Node Bs 180 . Typically, multiple Node Bs 180 are configured in a cellular configuration (one for each cell) that covers a large service area.

Each RNC 175 communicates with the components of the core network 165 via standard radio network controller interfaces, such as the Iu-cs and Iu-ps interfaces shown in FIG. 1 . For example, the RNC 175 communicates with the MSC 160 via the UTRAN Iu-cs interface for circuit switched voice services. Additionally, the RNC 175 communicates with the SGSN 155 over the UTRAN Iu-ps interface for packet data service over the GGSN 157 . Also, those skilled in the art will recognize that other networks with other standard interfaces may be applied in some embodiments. For example, the RNC 175 in the GERAN network is replaced by a base station controller (BSC) that delivers voice to the MSC 160 via the A interface, and the BSC delivers the data to the SGSN via the Gb interface of the GERAN network.

In some embodiments of the ICS architecture, the user equipment 102 is connected via an ICS access interface 110 and a second communication network facilitated by a generic access network controller (GANC) 120 (also referred to as a universal network controller or UNC). It uses the services of the Mobile Core Network (CN) 165 .

In some embodiments, voice and data services on the ICS access interface 110 are facilitated via an access point 114 communicatively coupled to a broadband IP network 116 . In some embodiments, the access point 114 is a generic wireless access point that connects the user equipment 102 to the ICS network via the unlicensed wireless network 118 created by the access point 114 .

Signaling from UE 102 is communicated to GANC 120 via ICS access interface 110 . After performing subscriber authentication and authorization, the GANC 120 communicates with the components of the mobile core network 165 using a radio network controller interface that is the same or similar to the radio network controller interface of UTRAN described above, and provides circuit switched voice services. a UTRAN Iu-cs interface for use and a UTRAN Iu-ps interface for packet data services (eg, GPRS). In this manner, the GANC 120 uses an interface to the same or similar mobile core network as the UTRAN radio network subsystem (eg, Node B 180 and RNC 175 ).

In some embodiments, the GANC 120 is configured with multiple numbers that are (1) "Up", (2) "Wm", (3) "DVGr'", (4) "Gn'", and (5) "Sl". It communicates with other system components of the ICS system via one or more of the other interfaces. The "Up" interface is the interface between the UE 102 and the GANC 120 . The "Wm" interface is a standardized interface between the GANC 120 and the Authorization, Authentication, and Accounting (AAA) server 170 for authentication and authorization of the UE 102 in the ICS. The "D/Gr'" interface is a standard interface between the AAA server 170 and the HLR 160 . Optionally, some embodiments use a "Gn'" interface, which is a modified interface for direct communication with a data services gateway (eg, GGSN) of the core grant network. Some embodiments optionally include an "Sl" interface. In these embodiments, the "Sl" interface provides an authorization and authentication interface from the GANC 120 to the AAA 140 server. In some embodiments, the AAA server 140 supporting the Sl interface and the AAA server 170 supporting the Wm interface may be the same. Further details of the Sl interface can be found in U.S. Patent Application 11/, filed February 6, 2006 and entitled "Service Access Control Interface for an Unlicensed Wireless Communication System" 349,025.

In some embodiments, UE 102 must register with GANC 120 before accessing the ICS service. Registration information in some embodiments includes the subscriber's International Mobile Subscriber Identity (IMSI), Media Access Control (MAC) address, and serving access as well as the cell identity from the GSM or UTRAN cell in which the UE 102 is already camped. Contains the SSID (Service Set Identifier) of the point. In some embodiments, the GANC 120 passes this information to the AAA server 140 to authenticate the subscriber and determine the services (eg, voice and data) available to the subscriber. If access is granted by the AAA 140 , the GANC 120 will allow the UE 102 to access the voice and data services of the ICS system.

These voice and data services are seamlessly provided by the ICS to the UE 102 via the various interfaces described above. In some embodiments, when data service is requested by UE 102 , ICS uses the optional Gn interface to communicate directly with GGSN 157 . The Gn' interface avoids the overhead and latency associated with communicating with the SGSN 155 over the Iu-ps interface of the UTRAN or the Gb interface of the GSM core network before the GANC 120 reaches the GGSN 157. make it possible

In some other embodiments, the access point 114 is a femtocell access point (FAP). The FAP facilitates a short range licensed wireless communication session 118 that operates independently of the licensed communication session 106 . In the case of a femtocell, the user equipment 102 connects to the ICS network via the short range licensed wireless network 118 created by the FAP 114 . The signal from the FAP is then transmitted over the broadband IP network 116 .

B. Applications of ICS

ICS provides a scalable security interface to the core service network of mobile communication systems. 2 illustrates several applications of ICS in some embodiments. As shown, homes, offices, hotspots, hotels, and other public and private venues 205 are connected via the Internet 215 to one or more network controllers 210 (eg, GANC 120 shown in FIG. 1 ). connected The network controller is also connected to the mobile core network 220 (eg, the core network 165 shown in FIG. 1 ).

2 also shows several user equipment. These user equipment are merely examples of user equipment that may be used for each application. Although only one of each type of user equipment is shown in most examples, one of ordinary skill in the art will recognize that other types of user equipment may be used in these examples without departing from the invention. Also, although only each type of access point, user equipment, or network controller is shown, many such access points, user equipment, or network controllers may be used in FIG. 2 . For example, an access point may be connected to several user equipment, a network controller may be connected to several access points, and several network controllers may be connected to the core network. The following subsections provide examples of several services that may be provided by ICS.

One. Wi-Fi

Wi-Fi access point 230 enables dual-mode cellular/Wi-Fi UEs 260-265 to receive high-performance, low-cost mobile services when within range of a home, office, or public Wi-Fi network. . Using a dual-mode UE, subscribers can roam and handover between licensed wireless communication systems and Wi-Fi access, and receive a consistent set of services when transitioning between networks.

2. femtocell

The femtocell enables user equipment, such as the illustrated standard mobile station 270 and wireless computer 275 , to receive low cost services using a short range licensed wireless communication session via the FAP 235 .

3. terminal adapter

Terminal adapter 240 makes it possible to include fixed terminal devices such as telephone 245, facsimile 250, and other equipment not wirelessly enabled within the IC. As far as subscribers are concerned, the service behaves as a standard analog fixed phone line. The service is delivered in a manner similar to other fixed line VoIP services, where the UE is connected to the subscriber's existing broadband (eg, Internet) service.

4. WiMAX

Some licensed wireless communication system operators are studying the deployment of WiMAX networks in parallel with existing cellular networks. The dual mode cellular/WiMAX UE 290 enables subscribers to seamlessly transition between cellular networks and such WiMAX networks.

5. soft mobile

Connecting a laptop 280 to broadband access in hotels and Wi-Fi hotspots is widely used, especially for international business travelers. In addition, many travelers are starting to use laptops and broadband connections for voice communication. Instead of using a mobile phone to make calls and pay significant roaming fees, softmobile (or softphone) and VoIP services are used to make long-distance calls.

To use the softmobile service, the subscriber installs a USB memory stick 285 with a SIM embedded in the USB port of the laptop 280 . The softmobile client automatically initiates and connects to the mobile service provider via IP. From this point on, the subscriber can make and receive mobile calls as if they were in their home call area.

Several examples of integrated communications systems (ICS) are provided in the following subsections. Those skilled in the art will appreciate that these examples can be readily combined. For example, an ICS may be an IP based system and may have an A/Gb interface towards the core network, while another ICS may have an IP based system similar to an Iu interface towards the core network.

C. Integrated system with A/Gb and/or Iu interfaces towards the core network

3 illustrates an A/Gb-mode General Access Network (GAN) functional architecture of some embodiments. The GAN includes one or more generic access network controllers (GANCs) 310 and one or more generic IP access networks 315 . One or more UEs 305 (one is shown for simplicity) may be connected to the GANC 310 via a generic IP access network 315 . The GANC 310 has the ability to appear as a GSM/EDGE Radio Access Network (GERAN) base station controller (BSC) to the core network 325 . GANC 310 includes a secure gateway (SEGW) 320 terminating a secure remote access tunnel from UE 305 , providing mutual authentication, encryption and data integrity for signaling, voice and data traffic.

Generic IP access network 315 provides connectivity between UE 305 and GANC 310 . The IP transport connection extends from the GANC 310 to the UE 305 . A single interface, Up interface, is defined between the GANC 310 and the UE 305 .

The GAN coexists with GERAN and maintains interconnection with the core network (CN) 325 through a standardized interface defined for GERAN. These standardized interfaces are an interface to a mobile switching center (MSC) 330 for circuit switched services, a Gb interface to a serving GPRS support node (SGSN) 335 for packet switched services, and a serving mobile location to support location services. an Lb interface to a center (SMLC) 350 , and an interface to a cell broadcast center (CBC) 355 supporting cell broadcast services. Transaction control (eg, connection management CC, and session management SM) and user services are provided by the core network (eg, MSC/VLR and SGSN/GGSN).

As shown, the SEGW 320 is connected to the AAA server 340 via a Wm interface. The AAA server 340 is used to authenticate the UE 305 when setting up the secure tunnel. Some embodiments only require a subset of Wm functionality for GAN applications. In these embodiments, at least the GANC-SEGW will support the Wm authentication procedure.

4 illustrates an Iu-mode general access network (GAN) functional architecture of some embodiments. The GAN includes one or more generic access network controllers (GANCs) 410 and one or more generic IP access networks 415 . One or more UEs 405 (one is shown for simplicity) may be connected to the GANC 410 via a generic IP access network 415 . Compared to the GANC 310 , the GANC 410 has the ability to appear as a UMTS TERRESTRIAL RADIO ACCESS NETWORK (UTRAN) radio network controller (RNC) to the core network 425 . In some embodiments, the GANC has extended capabilities to support Iu and A/Gb interfaces to simultaneously support Iu-mode and A/Gb-mode UEs. Similar to GANC 310 , GANC 410 includes a secure gateway (SEGW) 420 that terminates a secure remote access tunnel from UE 405 , including mutual authentication, encryption, and encryption for signaling, voice and data traffic. Provides data integrity.

Generic IP access network 415 provides connectivity between UE 405 and GANC 410 . The IP transport connection extends from the GANC 410 to the UE 405 . A single interface, Up interface, is defined between the GANC 410 and the UE 405 . A function is added to this interface through the Up interface shown in FIG. 3 to support the Iu-mode GAN service.

The GAN coexists with the UTRAN and maintains interconnection with the core network (CN) 425 via a standardized interface defined for the UTRAN. These standardized interfaces include an Iu-cs interface to a mobile switching center (MSC) 430 for circuit switched services, an Iu-ps interface to a Serving GPRS Support Node (SGSN) 435 for packet switched services, and location services. an Iu-pc interface to a serving mobile location center (SMLC) 450 to support Transaction control (eg, connection management CC and session management SM) and user services are provided by the core network (eg, MSC/VLR and SGSN/GGSN).

As shown, the SEGW 420 is connected to the AAA server 440 via a Wm interface. The AAA server 440 is used to authenticate the UE 405 when setting up the secure tunnel. Some embodiments only require a subset of Wm functionality for Iu mode GAN applications. In these embodiments, at least the GANC-SEGW will support the Wm authentication procedure.

D. ATM and IP-Based Architectures

In some embodiments, the system uses an Asynchronous Transfer Mode (ATM) based Iu (Iu-cs, Iu-ps) interface towards the CN. In some embodiments, the system architecture may also support an IP-based Iu (Iu-cs, Iu-ps) interface towards the CN. The next two subsections describe examples of these architectures for femtocells.

Those skilled in the art will recognize that the same example can be readily applied to other types of ICS. For example, these examples show that when the ICS access interface 110 (shown in FIG. 1 ) uses an unlicensed frequency (instead of a femtocell's licensed frequency) and the access point 114 is a generic WiFi access point (instead of a FAP), etc., can be used Also, those skilled in the art will appreciate that the same example can be easily implemented using the A/Gb interface (described above) instead of the Iu interface.

5 illustrates the basic elements of a femtocell system architecture with an Asynchronous Transfer Mode (ATM) based Iu (Iu-cs, Iu-ps) interface towards the CN in some embodiments. These elements include user equipment (UE) 505 , FAP 510 , and general access network controller (GANC) 515 , and access point management system (AMS) 570 .

For simplicity, only one UE and one FAP are shown. However, each GANC may support multiple FAPs, and each FAP may support multiple UEs. As shown, the GANC 515 includes an IP network controller (INC; 525), a GANC secure gateway (SeGW; 530), a GANC signaling gateway 535, a GANC media gateway (MGW; 540), and an ATM gateway 545. include Elements of the femtocell are further described below.

6 illustrates basic elements of a femtocell system architecture with an IP-based Iu (Iu-cs, Iu-ps) interface towards the CN in some embodiments. For simplicity, only one UE and one FAP are shown. However, each GANC may support multiple FAPs, and each FAP may also support multiple UEs. This option eliminates the need for a GANC signaling gateway 535 and also an ATM gateway 545 . Optionally, for the IP-based Iu interface, the GANC media gateway 540 also allows the R4 MGW 605 in the CN to terminate voice data, i.e. "IETF RFC 3267-AMR (Adaptive Multi-Rate) and AMR-WB (Adaptive Multi-Rate Wideband) RTP (Real-Time Transport Protocol) Payload Format and File Storage Format for Audio Codec", "RFC 3267" may be removed if it can support the end of the RTP frame.

Also, the components of a licensed wireless communication system are shown in FIGS. 5 and 6 . These components are 3G MSC 550 , 3G SGSN 555 , and another core network system (shown together) 565 . The 3G MSC 550 provides a standard Iu-cs interface towards the GANC. Another alternative to MSC is shown in FIG. 6 . As shown, the MSC 650 is divided into an MS (MSC server) 675 for Iu-cs based signaling and an MGW 680 for a bearer path. R4 MSC 650 is a 4 version of 3G MSC with different architecture. That is, the R4 MSC is divided into an MSS for control traffic and an MGW for handling bearers. A similar MSC may be used in the ATM architecture of FIG. 5 . Also, the two architectures shown in Figures 5 and 6 are adaptable to use any future version of MSC.

The 3G SGSN 555 provides packet services (PS) over a standard Iu-ps interface. The SGSN is connected to the INC 525 for signaling and to the SeGW 530 for PS data. The AAA server 560 communicates with the SeGW 530, supports the EAP-AKA and EAP-SIM procedures used for IKEv2 through the Wm interface, and includes a MAP interface for HLR/AuC. In some embodiments, the system also supports enhanced service access control functionality via the Sl interface.

II. functional entity

A. User Equipment

The UE 405 includes the necessary functionality to access the Iu-mode GAN. In some embodiments, the UE additionally includes the necessary functionality to access the A/Gb-mode GAN. In some embodiments, user equipment (UE) 305 is a dual mode (eg, GSM and unlicensed radios) handset device with the ability to switch between the two modes. User equipment may support Bluetooth® or IEEE 802.11 protocols. In some embodiments, the UE supports an IP interface to the access point. In these embodiments, the IP connection from the GANC extends widely to the UE. In some other embodiments, user equipment (UE) 305 is a standard 3G handset device operating on the provider's licensed spectrum.

In some embodiments, the user equipment comprises a cellular phone, a smart phone, a personal cellular communication, or a computer equipped with a subscriber identity mobile (SIM) card for communicating over a licensed or unlicensed wireless network. Also, in some embodiments a computer with a SIM card communicates over a wired communication network.

Alternatively, in some embodiments the user equipment provides a fixed set of terminal adapter functions to connect an Integrated Services Digital Network (ISDN), Session Initiation Protocol (SIP), or Plain Old Telephone Service (POTS) terminal to the IC. included wireless devices. Applying the present invention to this type of device, the wireless service provider can provide users with so-called landline replacement services, even for user locations not sufficiently covered by licensed wireless networks. In addition, some embodiments of terminal adapters may connect ISDN, SIP, or POTS terminals to other communication networks (eg, IP networks), although alternative embodiments of terminal adapters provide wireless equivalent functionality to connect over unlicensed or licensed wireless networks. It is a fixed wired device that connects to

B. Generic Access Network Controller (GANC)

The core network 425 interacts with the GANC 410 as if it were an RNC. Generic IP access network 415 provides connectivity between GANC 410 and UE 405 . The GANC 410 entity interacts between the Iu interface and the generic IP access network using control plane and user plane functions. The control plane function is used for call control signaling, and the user plane function is used for information transmission (eg, voice or data). In some embodiments, the GANC has extended capabilities to work with the GERAN A/Gb interface.

Some embodiments of the aforementioned apparatus, such as user equipment, FAP, or GANC, implement a wireless protocol for managing voice and data services on a machine-readable or computer-readable medium, as further described below in the section entitled "Computer Systems". and electronic components such as a microprocessor (not shown) and a memory that stores computer program instructions for execution. Examples of machine-readable media or computer-readable media include magnetic media such as hard disks, memory modules, magnetic tapes, optical media such as CD-ROMS and holographic devices, magneto-optical media such as optical disks, and application specific integrated circuits), programmable logic devices (PLDs), ROM, and hardware devices specifically configured to store and execute program code such as RAM devices. An example of a computer program or computer code is a file containing, for example, machine code generated by a compiler, and high-level code executed by a computer, electronic component, or microprocessor using an interpreter.

III. Control and user plane architecture

In some embodiments, the Iu interface includes support for Asynchronous Transfer Mode (ATM) and IP-based signaling and user data transfer mechanisms. The following sections describe the control and user plane architecture for the circuit switched (CS) domain and packet switched (PS) domain.

A. Circuit switched (CS) domain

One. CS domain-control plane

7 illustrates a GAN architecture supporting a CS domain control plane in some embodiments. 7 shows different protocol layers for UE 705 , generic IP network 710 , GANC 715 , and MSC 720 . 7 also shows two interfaces Up 725 and Iu-c 730 . The main features of the GAN CS domain control plane architecture are as follows. The underlying access layer 735 and transport IP layer 740 provide generic IP connectivity between the UE 705 and the GANC 715 . IPSec layer 745 provides encryption and data integrity between UE 705 and GANC 715 . Remote IP layer 750 is the 'inner' IP layer for IPSec tunnel mode and is used by UE 705 to be handled by GANC 715 . The remote IP layer 750 is configured during IPSec connection establishment.

In some embodiments, a single TCP connection is used to provide reliable transmission for GA-RC and GA-CSR signaling between UE 705 and GANC 715 . TCP connections are managed by GA-RC and transmitted using the remote IP layer. A Non-Access Stratum (NAS) protocol such as the MM 760 is transparently carried between the UE 705 and the MSC 720 . The General Access Resource Control (GA-RC) protocol manages Up sessions, including GAN discovery and registration procedures. The GA-RC protocol (described in section 8.1.4 of "General access to A/Gb interfaces; Phase 2" of the 3GPP TS 43.318 standard) is extended to include support for selection of A/Gb mode or Iu mode GANs do.

The Generic Access Circuit Switched Resources (GA-CSR) protocol supports UMTS-specific as well as GERAN-specific requirements. The GANC 715 terminates the GA-CSR protocol and interworks with the RANAP 755 protocol through the Iu-c 730 interface. In some embodiments, the Iu-cs signaling transport layer 765 conforms to the "UTRAN Iu Interface Signaling Transport" of the 3GPP TS 25.412 standard (hereinafter "3GPP TS 25.412").

a) Alternative architecture-control plane for CS domain

The embodiment shown in FIG. 7 is for implementing a CS domain control plane architecture in which a UE 705 and a generic IP network 710 are used to connect a subscriber using the UE to the MSC 720 via the GANC 715. It's just one alternative. Those skilled in the art will appreciate that the present invention is applicable for other user equipment and access points (eg, those shown in FIG. 2 ).

For example, FIG. 8 illustrates a CS domain control plane architecture of some embodiments. As shown, the GANC and MSC in FIG. 8 are similar to the GANC and MSC shown in FIG. 7 . In Fig. 8, the local node where the subscriber is located is represented by a black box (referred to as the local node 805). Other embodiments use other equipment to connect subscribers located at local node 805 with MSC 720 via GANC 715 . For example, in the embodiment shown in FIG. 7 , a UE 705 and a generic IP network 710 are used. 9 shows another embodiment in which a UE 905, a femtocell access point (FAP) 910, and a generic IP network 915 are used to connect the local node 805 with the MSC 720 via the GANC 715. to exemplify

As shown, the protocol layers of the GANCs 880-885 are communicatively coupled with corresponding layers in the generic IP network 915 (shown by arrows 845-850, respectively). Similarly, GANC layers 855-875 are communicatively coupled with corresponding layers in FAP 910 (shown by arrows 820-840, respectively). Also, the MM layer 890 and CC/CS/SMS layer 895 of the MSC 720 are transparently connected to the corresponding layer 905 within the UE (shown by arrows 810-815, respectively). Using this technique, a FAP similar to the FAP 235 shown in FIG. 2 may be used to connect a UE (eg, UEs 270 - 275 ) to the radio core network 220 via the network controller 210 . . Those of ordinary skill in the art will know that user equipment, access points, terminal adapters, softmobiles, etc. (eg, those shown in FIG. 2 ) can be integrated into an integrated communication system (ICS) using a multi-layer CS domain control architecture as shown in FIG. 7 . The techniques shown in FIGS. 8 and 9 can be applied to communicatively connect to the .

b) <u>CS domain-control plane-</u><u>UE</u><u> architecture</u>

10 illustrates a control plane for a UE architecture CS domain. As shown, the architecture includes support for GERAN, UTRAN, and A/Gb mode GAN and Iu mode GAN. The main features of the UE CS domain control plane architecture shown in FIG. 10 are as follows. The GERAN RR-SAP interface 1015 to the GSM-MM layer 1005 is reserved equally for GERAN and A/Gb-mode GAN access. Likewise, the UTRAN RR-SAP interface 1020 to the GSM-MM layer 1005 is equally reserved for UTRAN and Iu-mode GAN access. The access mode switch 1010 is provided to switch between the GERAN/UTRAN, A/GB-mode GAN and Iu-mode GAN modes. The GA-CSR/GA-RC 1025 peers directly with the UTRAN RRC 1030 and GERAN RRC 1035 layers to provide coordination for roving and handover. As shown in FIG. 10 , a GA-CSR/GA-RC 1025 , a UTRAN RRC 1030 , and a GERAN RRC 1035 interface through a set of service access interfaces (SAPs) 1040 .

2. CS domain-user plane

11 illustrates a GAN protocol architecture supporting the CS domain user plane in some embodiments. 11 shows different protocol layers for UE 1105 , generic IP network 1110 , GANC 1115 , and MSC 1120 . 11 also shows two interfaces Up 1125 and Iu-c 1130. The main features of the GAN CS domain user plane architecture are as follows. The underlying access layer 1135 and transport IP layer 1140 provide general connectivity between the UE 1105 and the GANC 1115 . The IPSec layer 114 5 provides encryption and data integrity. The CS user plane data transfer over the Up interface 1125 is the same as the CS user plane for A/Gb-mode GAN (ie, using real-time protocol (RTP) according to IETF RFC 3267). GANC 1115 interworks with the CS domain user plane between RTP/UDP and Iu user plane (Iu-UP) protocols on Iu-cs interface 1130 . In some embodiments, the Iu-cs data transport layer 1165 conforms to the 3GPP TS 25.414 standard.

Those skilled in the art will recognize that other user equipment, access points, terminal adapters, softmobiles, etc. may be connected to the core network via GANC. For example, FIG. 12 illustrates a CS domain, a user plane protocol architecture of a UE 1205 , a femtocell access point (FAP) 1210 , and a generic IP network 1215 . Using the techniques described with reference to FIGS. 8 and 9 , those skilled in the art will connect the UE 1205 and the generic IP network 1110 shown in FIG. 11 to the UE 1205 to connect the femtocell UE 1205 to the core network via GANC. 1205 , FAP 1210 , and general IP network 1215 . Similarly, other types of UEs, access points, terminal adapters, softmobiles, etc. may be connected to the core network via GANC.

b) <u>CS domain-user plane-</u><u>UE</u><u> architecture</u>

13 illustrates a UE architecture for a CS domain user plane in some embodiments. As shown, the architecture includes support for A/Gb mode and Iu mode GAN 1305 , as well as GERAN 1310 , and UTRAN 1315 . RFC 3267 AMR processing layer (1320) is the CS user plane data selected access network; That is, it is used to connect the GAN RTP/UDP/IP layer 1325 to the AMR audio processing layer 1330 via the CS user plane routing service layer 1335 routing for GERAN, UTRAN, or GAN. RFC 3267 AMR processing layer 1320 is not used when connecting to CS data processing layer 1340, ie for circuit switched data as opposed to circuit switched voice.

B. Packet Switched (PS) Domain

One. PS domain-control plane

14 illustrates a GAN architecture supporting the PS domain control plane. 14 shows UE 1405 , generic IP network 1410 , GANC 1415 , SGSN 1420 different protocol layers. 14 also shows two interfaces Up 1425 and Iu-p 1430. The main features of the GAN PS domain control plane architecture shown in FIG. 14 are as follows. The underlying access layer 1435 and transport IP layer 1440 provide general connectivity between the UE 1405 and the GANC 1415 . IPSec layer 1445 provides encryption and data integrity. TCP 1450 provides reliable transport for GA-PSR between UE 1405 and GANC 1415 . GA-RC manages IP access including GAN registration process. The Generic Access Packet Switched Resource (GA-PSR) protocol supports UMTS-specific requirements.

The GANC 1415 terminates the GA-PSR protocol and interworks with the RANAP protocol 1455 through the Iu-ps interface 1430 . NAS protocols 1460 such as GMM, SM and SM are carried transparently between UE 1405 and SGSN 1420 . In some embodiments, the Iu-ps signaling transport layer 1465 conforms to 3GPP TS 25.412.

Those skilled in the art will recognize that other user equipment, access points, terminal adapters, softmobiles, etc. may be connected to the core network via GANC. For example, FIG. 15 shows a PS domain, a control plane protocol architecture of a UE 1505 , a femtocell access point (FAP) 1510 , and a generic IP network 1515 . Using the techniques described in conjunction with Figures 8 and 9, one of ordinary skill in the art would connect the UE 1405 and the generic IP network 1410 to the UE shown in Figure 11 in order to connect the femtocell UE 1505 to the core network via GANC. 1505 ), FAP 1510 , and general IP network 1515 . Similarly, other types of UEs, access points, terminal adapters, softmobiles, etc. may be connected to the core network via GANC.

c) <u>PS domain-control plane-</u><u>UE</u><u> architecture</u>

16 illustrates a UE architecture for the PS domain control plane in some embodiments. As shown, the architecture includes support for A/Gb mode and Iu mode GAN as well as GERAN and UTRAN. The main features of the UE PS domain control plane architecture shown in FIG. 16 are as follows. The GERAN GRR-SAP interface 1615 and the GERAN GMMRR-SAP interface 1617 to the GMM layer 1605 are equally reserved for GERAN and A/Gb-mode GAN access. Likewise, the UTRAN RABMAS-SAP interface 1620 and the UTRAN GMMAS-SAP interface 1622 to the GMM layer 1605 are equally reserved for UTRAN and Iu-mode GAN access. An access mode switch 1610 is provided to switch between GERAN/UTRAN, A/GB-mode GAN and Iu-mode GAN modes. GA-PSR/GA-RC 1625 to provide coordination for roving and handover. It peers directly with the UTRAN RRC (1630) and GERAN RRC (1635) layers. As shown in FIG. 16 , a GA-PSR/GA-RC 1625 , a UTRAN RRC 1630 , and a GERAN RRC 1635 are interfaced through a set of service access interfaces (SAPs) 1640 .

2. PS domain-user plane

17 illustrates a GAN architecture for the PS domain user plane in some embodiments. 17 shows another protocol layer for UE 1705 , generic IP network 1710 , GANC 1715 , and SGSN 1720 . 17 also shows two interfaces Up 1725 and Iu-p 1730. The main features of the GAN PS domain user plane architecture shown in FIG. 17 are as follows. The underlying access layer 1735 and transport IP layer 1740 provide general connectivity between the UE 1705 and the GANC 1715 . The IPSec layer 1745 provides encryption and data integrity.

GA-PSR is extended to include support for the GTP-U G-PDU message format to transport PS user data (eg IP packets) rather than LLC PDUs as in A/Gb mode GAN. As shown in FIG. 17 , user data in the GTP-U G-PDU message may be transmitted to the GGSN through the SGSN transparently between the UE 1705 and the core network. In some embodiments, the Iu-ps data transport lower layer 1765 conforms to the 3GPP TS 25.414 standard.

18 illustrates an alternative GAN PS domain user plane configuration supported by the Up interface procedure of some embodiments. In this configuration, GANC 1815 terminates the Up interface GTP-U tunnel with UE 1805 and also terminates a separate Iu-ps GTP-U tunnel to SGSN 1820 . The GANC 1815 relays PS user data between the Up interface GTP-U tunnel and the Iu-ps interface GTP-U tunnel associated with it so that the PS user data flows between the UE and the SGSN.

This configuration minimizes the number of active GTP-U "paths" provided to the core network. That is, the SGSN may be limited to the number of RNCs that may simultaneously exchange PS user data (eg, today, there may be only 4096 RNCs in a given PLMN). Without a software upgrade, for example, it may not be able to support simultaneous communication with the countless UEs required when a GTP-U tunnel is formed from the UE to the SGSN. This potential SGSN limitation is circumvented by terminating the Iu-ps GTP-U tunnel over the GANC. In some embodiments, the Iu-ps data transport lower layer 1865 conforms to the 3GPP TS 25.414 standard.

Those skilled in the art will recognize that other user equipment, access points, terminal adapters, SoftMobiles, etc. may be connected to the core network via GANC. For example, FIG. 19 illustrates a PS domain, a user plane protocol architecture of a UE 1905 , a femtocell access point (FAP) 1910 , and a generic IP network 1915 . Using the techniques described with reference to FIGS. 8 and 9 , one of ordinary skill in the art would connect the UE 1805 and the generic IP network 1810 shown in FIG. 11 to the UE to connect the femtocell UE 1905 to the core network via GANC. (1905), FAP (1910), and general IP network (1915). Similarly, other types of UEs, access points, terminal adapters, softmobiles, etc. may be connected to the core network via GANC.

a) <u>PS domain-user plane-</u><u>UE</u><u> architecture</u>

20 illustrates a UE architecture for a PS domain user plane in some embodiments. As shown, the architecture includes support for A/Gb mode and Iu mode GAN (2005) as well as GERAN (2010), and UTRAN (2015). The access mode switch 2020 is used to switch between GERAN/UTRAN, A/GB-mode GAN and Iu-mode GAN modes.

C. GA-RC (General Access resource control)

The GA-RC protocol provides a resource management layer with the following functions: discovery and registration using GANC, registration update using GANC, application level keep alive using GANC; and support of identification of APs used for GAN access.

One. State of the GA-RC sub-layer

21 illustrates a state diagram for general access at a UE in some embodiments. As shown, the GA-RC sub-layer within the UE can be in one of two states: GA-RC-deregistration 2105 or GA-RC-registration 2110 . When switching the Serving RR to Iu-mode GAN (indicated by arrow 2112) the following results are possible: (1) Transition to GA-CSR-Idle 2115 and GA-PSR-Idle 2120 (i.e. UE is idle during the transition), (2) transition to GA-CSR-connection 2125 and GA-PSR-idle 2130 (ie due to CS handover or relocation), (3) GA-CSR-idle (2115) and GA-PSR-connection (transition to 2130 (ie due to PS handover or relocation); (4) GA-CSR-connection 2125 and transition to GA-PSR-connection 2130 (i.e. due to PS handover or relocation) , due to dual transmission mode handover or CS+PS relocation). The transition of the serving RR from GAN to GERAN/UTRAN RRC (indicated by arrow 2135) may occur when the UE is in any combination of GA-CSR and GA-PSR states.

In the GA-RC-deregistration state 2105 , the UE may be in the GAN coverage area, but is not successfully registered with the GANC. The UE may initiate the GAN registration procedure when in the GA-RC-deregistration state 2105 . The UE reverts to the GA-RC-deregistration state 2105 upon loss of the TCP or IPSec connection or upon execution of the GAN deregistration procedure.

In the GA-RC-registration state 2110 , the UE is registered with the serving GANC. The UE has a TCP connection and IPSec tunnel established to the serving GANC that the UE can use to exchange GA-RC, GA-CSR, and GA-PSR signaling messages with the GANC.

The UE performs GANC and application level keep alive while maintaining the GA-RC-registration state 2110 . In the GA-RC-registration state 2110 , the UE may be in UTRAN/GERAN mode or GAN mode. The UE is either (1) camped on GERAN or UTRAN and idle, (2) active in GERAN or UTRAN (eg, a GSM RR or UTRAN RRC connection may be established), or (3) "roved" into GAN mode )", or (4) recently "roving" from GAN mode (eg, due to handover from GAN).

D. GA-CSR (Generic Access Circuit Switched Resources)

The GA-CSR protocol has the following functions: (1) setup of a transport channel for CS traffic between UE and GANC, (2) CS handover support between UTRAN/GERAN and GAN, (3) NAS between UE and core network Provides a circuit-switched service resource management layer that supports other functions such as direct transmission of messages, (4) CS paging, and security configuration.

One. State of the GA-CSR sub-layer

The GA-CSR sub-layer of the UE may be in two states as illustrated in FIG. 21 , namely GA-CSR-idle or GA-CSR-connected. The UE enters the GA-CSR-idle state 2115 when the UE switches the serving RR entity to GAN. This transition can only occur when the GA-RC is in the GA-RC-registered state 2110 .

The UE moves from the GA-CSR-idle state 2115 to the GA-CSR-connected state 2125 when the GA-CSR connection is established, and the GA-CSR-idle state 2115 when the GA-CSR connection is released. return to Upon release of the GA-CSR connection, an indication that a dedicated CS resource does not exist is transmitted to the upper layer. The UE may also enter the GA-CSR-connected state 2125 from the GA-RC-registration state 2110 of the GERAN/UTRAN mode when handover to GAN is being performed. In the same way, the UE enters the GA-RC-registration state 2110 of the GERAN/UTRAN mode from the GA-CSR-connected state 2125 when the handover from the GAN is successfully executed.

E. GA-PSR (Generic Access Packet Switched Resources)

The GA-PSR protocol has the following functions: (1) setup of transport channels for PS traffic between UE and network, (2) support for PS relocation/handover between UTRAN/GERAN and GAN, (3) UE and PS core It provides a packet switched service resource management layer that supports direct transmission of NAS messages between networks, (4) transmission of GPRS user plane data, and (5) PS paging and other functions such as security configuration.

One. Status of the GA-PSR sub-layer

The GA-PSR sub-layer within the UE can be in two states: GA-PSR-idle or GA-PSR-connected as illustrated in FIG. 21 . The UE enters the GA-PSR-idle state 2120 when the UE switches the serving RR entity to GAN. This transition can only occur when the GA-RC is in the GA-RC-registered state 2110 . The UE moves from the GA-PSR-idle state 2120 to the GA-PSR-connected state 2130 when the GA-PSR connection is established, and the GA-PSR-idle state 2120 when the GA-PSR connection is released. return to Upon release of the GA-PSR connection, an indication indicating that there is no dedicated resource is transmitted to the upper layer.

The UE may also enter the GA-PSR-connected state 2130 from the GA-RC-registration state 2110 of the GERAN/UTRAN mode when handover to GAN is being performed. In the same way, the UE enters the GA-RC-registration state 2110 in the GERAN/UTRAN mode from the GA-PSR-connected state 2130 when the handover from the GAN is successfully executed. The GA-PSR packet transmission channel (GA-PSR PTC) provides an association between the UE and the GANC through an Up interface for transmission of GPRS user data. This is described in the PS NAS signaling procedure of the V subsection below.

IV. GAN Security Mechanism

GAN supports security mechanisms at different levels and interfaces as shown in FIG. 22 . A security mechanism 2205 on the Up interface protects the control plane, and user plane traffic flows between the UE 2210 and the GANC 2215 from unauthorized use, data processing and eavesdropping, i.e. authentication, encryption and data integrity. mechanism is supported.

Network access security 2220 includes mechanisms defined in "3G Security; Security Architecture" of the 3GPP T33.102 standard. Mutual authentication of subscriber and core network (CN) 2225 takes place between the MSC/VLR or SGSN and the UE, and is transparent to the GANC. However, cryptographic binding exists between UE-CN authentication and UE-GANC authentication to prevent man-in-the-middle attacks.

An additional application level security mechanism 2230 may be used in the PS domain to secure end-to-end communication between the UE 2210 and the application server 2235 . For example, in some embodiments UE 2210 may operate the HTTP protocol over an SSL session for secure web access.

All control plane and user plane traffic transmitted between UE 2210 and GANC 2215 over the Up interface is the same as specified in "3G Security; Wireless Local Area Network (WLAN) Interworking Security" of 3GPP T33.234. It is protected by an IPSec tunnel between the UE 2210 and the GANC-SEGW using a mechanism to provide mutual authentication (using USIM certificates), encryption and data integrity.

As described above (with reference to FIGS. 9 , 12 , 15 and 19 ), some embodiments provide a Femtocell Access Point (FAP) for communicatively connecting a user equipment UE to a GANC via a generic IP network. use the As shown in FIG. 9 , the FAP architecture for the CS control plane has an IPSec layer 920 . Similarly, the FAP architecture for the CS user plane, the PS control plane, and the PS user plane architecture also include an IPSec (or IPSec ESP) layer (1220, 1520, and 1920, respectively). As shown in Figures 9, 12, 15 and 19, these IPSec layers are above the transport IP layer and the remote IP layer of the GANC, and are communicatively coupled to the corresponding GANC IPSec layer, and thus between the GANC and the FAP. A secure link is provided at

V. HIGH-LEVEL PROCEDURES

A. Mode selection in multi-mode terminal

Generic accessible UEs may support IP access technologies in addition to UTRAN and possibly GERAN air interfaces. The UE may be in GERAN/UTRAN mode or GAN mode of operation. A UE may be configured to operate in one of two modes (ie, GERAN/UTRAN or GAN) at any given time. There may be preferred modes of operation that may be configured by the subscriber or service provider through various mechanisms, eg, device management.

On power up, the UE always starts in GERAN/UTRAN mode and runs the normal power-up sequence. The UE, in some embodiments, executes a power-up sequence, as specified in the "Non-Access-Stratum (NAS) function related to a mobile station (MS) in idle mode" of the 3GPP TS23.122 standard. Thereafter, the UE may switch to the GAN mode based on the user preference or the mode selection preference determined by the operator configuration.

The various preferences for possible UEs are: GERAN/UTRAN only, GERAN/UTRAN-preferred, GAN-preferred, and GAN only. In GERAN/UTRAN only, the UE RR entity maintains GERAN/UTRAN mode and does not switch to GAN mode. GERAN/UTRAN -preferably, the UE RR entity is in GERAN/UTRAN mode as long as there is a PLMN available and not prohibited via GERAN/UTRAN. If an acceptable PLMN is not available via GERAN/UTRAN, and the UE is successfully registered with GAN via generic IP access network, the UE switches to GAN mode. When the PLMN becomes available via GERAN/UTRAN and the PLMN is not barred, or when the UE is deregistered or loses connection with the GAN via the generic IP access network, the UE returns to the GERAN/UTRAN mode.

In GAN-preferred, when the UE successfully registers with GAN via the generic IP access network, the UE switches to GAN mode and maintains this mode as long as the GAN is available. When the UE is deregistered, or otherwise loses connection with the GAN via the generic IP access network, the UE switches to the GERAN/UTRAN mode.

In GAN-only, the UE switches to GAN mode (after the initial power-up sequence in GERAN/UTRAN mode to obtain cellular network information, but except for MM and GMM procedures with GERAN/UTRAN core network) and does not switch to GERAN/UTRAN mode does not During the initial power-up sequence in GERAN/UTRAN mode, the UE will ignore all paging messages received via the GERAN/UTRAN network.

B. PLMN Selection

In some embodiments, there is no change from the PLMN selection procedure in the NAS layer (the MM) in the UE except that "in VPLMN background scan" in GAN mode is disabled. A GANC can only be connected to one PLMN. PLMN selection in the NAS layer does not result in a mode change between the GERAN/UTRAN mode and the GAN mode. For a specific example of PLMN selection, only PLMNs available via GAN or PLMNs available via GERAN/UTRAN are provided to the NAS layer (ie, there is no combination of PLMNs available via GERAN/UTRAN and GAN).

In the case of a GAN capable UE, some embodiments require a GANC selection process as part of the process of establishing a connection between the UE and the GANC. This allows, during GAN registration, the GAN-capable UE to choose from two or more GANC-PLMN pairs indicated by the default GANC (ie, within the GA-RC registration redirect message). The GANC selection process takes place while the UE is still in GERAN/UTRAN mode and before the UE roving to GAN mode. The currently selected PLMN may be selected if available through the GAN. Otherwise, the choice of GANC is implementation specific.

If the UE does not have stored information related to the serving GANC for the cell or AP to which it is currently connected, the UE attempts to register with the default GANC stored in the UE (always located in the HPLMN). The UE includes an indication identifying the GANC as the default GANC in the GA-RC registration request message.

When a UE attempts to register with the default GANC containing an indication indicating that it is in automatic PLMN selection mode, one of the following happens: If the default GANC decides to serve the UE, the default GANC responds with a GA-RC registration accept message. When the default GANC decides to redirect the UE to another GANC in the HPLMN, the default GANC responds with a GA-RC registration redirect message that does not contain a list of PLMN identities.

If the default GANC decides to redirect the UE to a non-HPLMN PLMN, the default GANC responds with a GA-RC registration redirect message and includes a list of PLMNs capable of providing GAN service to the UE at its current location. The list contains one or more PLMN identities along with the identities of the associated GANC and SEGW nodes (in IP address or FQDN format). After the GANC selection process, the GA-RC entity in the UE attempts to register with the associated GANC.

Regardless of whether the UE is in manual PLMN selection mode or automatic PLMN selection mode, if the user wants to perform manual PLMN selection or "user reselection", the UE sends a GA-RC registration request message including an indication indicating that it is in manual PLMN selection mode is sent to the default GANC. The default GANC cannot accept registration and responds with a GA-RC registration redirect message and contains a list of PLMNs that can provide GAN services to the UE at its current location.

If the UE includes the identity of the current serving GSM network in the GA-RC registration request message, the default GANC uses this identity to identify the list of PLMNs to send to the UE in the response message.

After successful registration with the serving GANC, the UE does not store the PLMN list. The UE does not use the PLMN list provided to the UE during the registration procedure for background scanning. The UE cannot use the GA in the VPLMN unless the HPLMN supports and permits GA.

C. Reselection between GERAN/UTRAN and GAN mode

One. Roving (from GERAN/UTRAN mode to GAN mode)

This procedure is applicable only when GAN service is available, the UE is not in NC2 mode (applicable if the UE is in GERAN mode as defined in "Radio Subsystem Link Control" of 3GPP T45.008 standard), only GAN , GAN-preferred, or if an acceptable PLMN is not available via GERAN/UTRAN, have UE preference for GERAN/UTRAN-preferred.

After successful GAN registration, the access mode at the UE is switched to GAN mode. The GA-CSR entity in the UE provides the NAS layer with the received NAS-related system information received in the GAN registration procedure. The NAS considers the GANC-allocated cell identity to be the current serving cell.

In GAN mode, the GERAN-RR and UTRAN RRC entities are separated from the RR-SAP in the UE. As a result, the entity: (1) does not inform the NAS of GERAN/UTRAN cell reselection and/or change of system information of the current camping cell, (2) does not inform the NAS of the PLMN newly discovered in GERAN or UTRAN, (3) ) does not act on paging request messages received via GERAN or UTRAN.

2. Lob-out (from GAN mode to GERAN/UTRAN mode)

This procedure is applicable when the UE is separated from the general IP access network, and its mode selection is GAN-preferred or GERAN/UTRAN-preferred. When the UE is disconnected from the general IP access network, depending on the progress, the UE may first deregister with the GANC.

In case of GAN-preferred and GERAN/UTRAN-preferred mode selection, the UE detaches the GA-CSR entity from the RR-SAP and reattachs the GERAN-RR or UTRAN RRC entity to the RR-SAP, normal GERAN-RR or UTRAN RRC restore function. For GAN-only mode selection, the GA-CSR remains attached to the NAS and the UE remains in the GAN mode (ie, "no service" state).

D. Procedures for GAN Registration

One. Discover and Register for General Access

The discovery and registration procedure is applicable as long as the UE preference operates in GAN-only, GAN-preferred, or GERAN/UTRAN-preferred mode when no acceptable PLMN is available via GERAN/UTRAN.

Once the UE establishes a connection to the generic IP access network, the UE determines the appropriate GANC-SEGW to connect to by completing the discovery procedure for the provisioning GANC in the UE's HPLMN. The providing GANC provides the address of the default GANC in the UE's HPLMN with which the UE can register.

The UE attempts to register with the default GANC provided by the provisioning GANC during the discovery procedure by completing the registration procedure. The default GANC may accept registration, redirect the UE to another GANC, or decline registration.

a) <u>Secure gateway identification</u>

The USIM of the UE includes the providing GANC and the FQDN (or IP address) of the associated SEGW, or the UE derives this information based on information in the USIM. If the UE does not have information about other GANCs and associated SEGWs stored, the UE completes the discovery procedure towards the providing GANC. As part of the registration procedure, the default GANC may indicate whether this GANC and SEGW address or the address of the GANC to which the UE is being redirected can be stored by the UE.

The UE may also store serving GANC information for the serving GANC it used to complete the successful registration procedure. Default GANC controls whether the UE can store serving GANC information. When the AP location does not have GERAN/UTRAN coverage, the stored serving GANC information is associated with the AP-ID. When the AP location has GERAN/UTRAN coverage, the stored serving GANC information is associated with GSM CGI or LAI or UTRAN CI. The stored Serving GANC information includes: (1) Serving SEGW FQDN or IP address after successful registration, (2) Serving GANC FQDN or IP address after successful registration, and (3) optionally, Serving GANC TCP after successful registration and if provided from the network. it's a port Other embodiments store different numbers of such entries in the UE, and are implementation specific. When the default GANC indicates that the UE can store these allowed addresses, the last successfully registered GANC association is saved. The UE may first subscribe to a generic IP access network point of attachment whose association with the serving GANC is stored in memory.

Upon connection to the generic IP access network, the UE attempts to register with the associated Serving GANC in its memory when it has a stored Serving GANC for the AP-ID or GERAN/UTRAN cell. The GANC may still reject the UE for some reason, even if it has served the UE before. The UE deletes the address of the Serving GANC from its stored list upon receipt of a registration rejection or if registration fails for some other reason (eg, no response is received).

If the UE does not receive a response to the registration request sent to the serving GANC (not the default GANC), it will retry to register with the default GANC. If the UE does not receive a response to the registration request sent to the default GANC, it attempts a discovery procedure with the provision GANC to obtain a new default GANC.

If the UE is attempting to register or discover a GANC after failing to register with the GANC, in the registration or discovery procedure, an indication that the UE attempted to register with another GANC, the reason for the failure, and the GANC and SEGW of the failed registration address is provided. When the UE connects to the generic IP access network, it attempts to register with the default GANC because it does not have a serving GANC stored in its memory.

b) <u>GANC ability</u>

Upon successful registration, GANC specific information is sent to the UE.

c) <u>UE capabilities</u>

The UE's GAN specific capabilities are sent to the GANC during registration.

d) <u>Required GAN service</u>

The UE may request the requested GAN service from the GANC as part of the registration procedure.

e) <u>GAN mode selection</u>

The UE (ie, Iu-mode GAN support) sends its GAN mode support information to the GANC during the discovery and registration procedure, ie in the GAN classmark IE. GAN mode support options are A/Gb mode support, Iu mode support, or both mode support. If GAN mode support information is not received, GANC assumes that the UE supports only A/Gb mode operation.

The provision GANC provides the UE with a suitable default GANC (eg, if separate A/Gb mode and Iu-mode GANCs are deployed in the network) or a default GANC (eg separate TCP ports with A/Gb mode and Iu-mode GAN service). The received GAN mode support information can be used to assign to the appropriate TCP port on The Iu-mode capable GANC also indicates to use the GAN mode for the current session in the GAN mode indicator IE, so that the UE can determine the Iu-mode capability of the home PLMN.

Table 1 lists the discovery process for various combinations of UE and home PLMN GAN mode capabilities.

Table 1: GAN Mode Selection Procedures Associated with GAN Discovery

<table><tgroup xmlns="http://www.oasis-open.org/tables/exchange/1.0" cols="4"><colspec colnum="1" align="center" colname="col1" colwidth="2660" /><colspec colnum="2" align="center" colname="col2" colwidth="2660" /><colspec colnum="3" align="center" colname="col3" colwidth="2660" /><colspec colnum="4" align="center" colname="col4" colwidth="2660" /><tbody><row><entry align="center" colname="col1"></entry><entry align="center" namest="col2" nameend="col4">Home PLMN GAN Mode Capabilities</entry></row><row><entry align="center" colname="col1">UE GAN Mode Capabilities</entry><entry align="center" colname="col2">A/Gb only</entry><entry align="center" colname="col3">only Iu</entry><entry align="center" colname="col4">both</entry></row><row><entry align="center" colname="col1">A/Gb only</entry><entry align="justify" colname="col2">GANC: Process with normal A/Gb mode discovery UE: Proceed with A/Gb mode registration </entry><entry align="justify" colname="col3">GANC: Rejected (not specified) because GAN mode support information is not provided or A/Gb mode (only) is indicated by the UE. UE: Retry at next power-on </entry><entry align="justify" colname="col4">GANC: GAN mode support information is not provided or A/Gb mode (only) is indicated by the UE, treated as normal A/Gb mode discovery. Assign UE to A/Gb capable GANC UE: Proceed to A/Gb mode registration</entry></row><row><entry align="center" colname="col1">only Iu</entry><entry align="justify" colname="col2">GANC: Treated as normal A/Gb mode discovery UE: No GAN mode selection provided by GANC, abort GAN operation and retry at next power-on</entry><entry align="justify" colname="col3">GANC: Iu mode support (only) is indicated by the UE, accept and transmit GAN mode indication = Iu UE: Proceed to Iu mode registration</entry><entry align="justify" colname="col4">GANC: Iu mode support (only) is indicated by the UE, accept and send GAN mode indication = Iu. Assign UE to Iu capable GANC UE: Proceed to Iu mode registration</entry></row><row><entry align="center" colname="col1">both</entry><entry align="justify" colname="col2">GANC: Process with normal A/Gb mode discovery UE: No GAN mode selection provided by GANC, proceed to Iu mode registration (Note 1)</entry><entry align="justify" colname="col3">GANC: Support for both modes is indicated by the UE, accept and transmit GAN mode indication = Iu UE: Proceed to Iu mode registration</entry><entry align="justify" colname="col4">GANC: Support for both modes is indicated by the UE, accept and send GAN mode indication = Iu. Assign UE to Iu capable GANC UE: Proceed to Iu mode registration</entry></row></tbody></tgroup></table>

Note: As described in Table 2 below, the result of Iu mode registration of an A/Gb-capable UE on an A/Gb-capable GANC is that the UE goes into A/Gb mode.

In some embodiments, the default or serving GANC uses the received GANmode support information to redirect the UE to another GANC or other TCP port on the current GANC. Iu-mode capable GANC also instructs to use GAN mode for the current session in the GAN mode indicator IE.

Table 2 lists the registration process for various combinations of UE and home PLMN GAN mode capabilities.

Table 2: GAN Mode Selection Procedures Associated with GAN Registration

<table><tgroup xmlns="http://www.oasis-open.org/tables/exchange/1.0" cols="4"><colspec colnum="1" align="center" colname="col1" colwidth="2660" /><colspec colnum="2" align="center" colname="col2" colwidth="2660" /><colspec colnum="3" align="center" colname="col3" colwidth="2660" /><colspec colnum="4" align="center" colname="col4" colwidth="2660" /><tbody><row><entry align="center" colname="col1"></entry><entry align="center" namest="col2" nameend="col4">Default/Serving GANC GAN mode capability</entry></row><row><entry align="center" colname="col1">UE GAN Mode Capabilities</entry><entry align="center" colname="col2">A/Gb only</entry><entry align="center" colname="col3">only Iu</entry><entry align="center" colname="col4">both</entry></row><row><entry align="center" colname="col1">A/Gb only</entry><entry align="justify" colname="col2">GANC: Processed with normal A/Gb mode registration UE: Proceed according to A/Gb mode GAN procedure</entry><entry align="justify" colname="col3">GANC: Rejected (invalid GANC) because GAN mode support information is not provided or A/Gb mode (only) is indicated by UE </entry><entry align="justify" colname="col4">GANC: GAN mode support information is not provided or A/Gb mode (only) is indicated by the UE, treated as normal A/Gb mode registration. Redirect UE to A/Gb capable GANC, if necessary UE: Follow A/Gb mode GAN procedure</entry></row><row><entry align="center" colname="col1">only Iu</entry><entry align="justify" colname="col2">GANC: Treated as normal A/Gb mode registration UE: No GAN mode selection provided by GANC, deregistration and regarded as registration rejection (void GANC)</entry><entry align="justify" colname="col3">GANC: Iu mode support (only) is indicated by the UE, accept and transmit GAN mode indication = Iu UE: proceed according to Iu mode GAN procedure</entry><entry align="justify" colname="col4">GANC: Iu mode support (only) is indicated by the UE, accept and send GAN mode indication = Iu. UE: Proceed according to Iu mode GAN procedure</entry></row><row><entry align="center" colname="col1">both</entry><entry align="justify" colname="col2">GANC: Treated with normal A/Gb registration UE: No GAN mode selection provided by GANC, proceed according to A/Gb mode GAN procedure</entry><entry align="justify" colname="col3">GANC: support for both modes is indicated by the UE, accept and transmit GAN mode indication = Iu UE: proceed according to Iu mode GAN procedure</entry><entry align="justify" colname="col4">GANC: Support for both modes is indicated by the UE, accept and transmit GAN mode indication = Iu (see note 1 below). Redirect UE to Iu or A/Gb capable GANC if necessary UE: Follow Iu or A/Gb mode GAn procedure</entry></row></tbody></tgroup></table>

Note 1: The selection of the GANC in Iu-mode versus A/Gb-mode may be based on other information received in the GAN registration message from the UE, information stored in the GANC, and operator (ie service provider) policy. For example, if the GSM RR/UTRAN RRC status IE indicates that the UE is in GERAN-only mode, the UE location is an area without UTRAN coverage, and the operator wants to minimize inter-RAT handover, GANC allows the UE to use A/Gb mode can direct

f) <u>discovery process</u>

When the UE supported GAN first attempts to connect to the GAN, the UE needs to identify the default GANC. Each GAN capable UE may be configured with the providing GANC and the FQDN (or IP address) of the associated SEGW, or the UE may be configured with this FQDN can be derived. The UE first connects to the provisioning GANC-SEGW and GANC in the UE's HPLMN by establishing a secure IPSec tunnel and TCP connection using the provided or derived address. The UE obtains the FQDN or IP address of the default GANC from the HPLMN and the associated SEGW through the discovery procedure.

If GERAN/UTRAN coverage is not available when the UE connects to the GANC for the GAN service, the GANC determines the location of the UE for the purpose of allocating the UE to the correct serving GANC (eg to enable handover and location-based services). does not necessarily have to be determined. GANC enables the operator to determine the service policy in this case, eg the operator can provide the service to the user with restrictions (if possible, with user interface instructions on the UE). If the UE initiates the discovery/registration procedure and GERAN/UTRAN coverage is not available, the GANC may have insufficient information to correctly route the subsequent emergency call.

23 illustrates a discovery procedure of some embodiments. 23 shows other messages between UE 2305, DN 2310, Provisioning GANC 2315, Security Gateway SEGW 2320 associated with Provisioning GANC 2315, and DNS Server 2325 associated with Provisioning GANC 2315. is shown to be exchanged in In the following description, it is assumed that the UE 2305 has a mode selection of GAN-only or GAN-preferred or GERAN/UTRAN-preferred and that the UE is already connected to a general IP access network. Another embodiment considers that different signal levels are sufficient to trigger the GAN discovery and registration procedure. The following steps are taken during the discovery procedure.

As shown in Figure 23, if the UE 2305 has the provisioned or derived FQDN of the provisioning SEGW, the UE uses DNS (via the generic IP access network interface) to resolve the FQDN into an IP address (in step 1). Execute the query. When the UE has the provisioning IP address of the provisioning SEGW, the DNS step is omitted. Next, DNS server 2310 provides a response containing the IP address of the providing SEGW 2320 (in step 2).

As shown, the UE 2305 establishes a secure tunnel to the provisioning SEGW 2320 (in step 3). If the UE 2305 has the provided or derived FQDN of the provided GANC 2315, the UE 2305 (in step 4) with the provided GANC 2315 (via a secure tunnel) to resolve the FQDN to an IP address. Performs a DNS query to the associated DNS server 2325 . If the UE 2305 has the provisioning IP address of the provisioning GANC, the DNS step will be omitted. The DNS server 2325 returns a response containing the IP address of the providing GANC 2315 (in step 5).

The UE 2305 sets up a TCP connection to a well-defined port on the provisioning GANC 2315 . Next, the UE 2305 queries the providing GANC 2315 for the default GANC using the GA-RC discovery request (in step 6). The message is: (1) Cell Info: the current camping UTRAN/GERAN cell ID with an indicator indicating the presence or the last LAI the UE was successfully registered with, (2) the generic IP defined in the identifier in the GAN of subclause VII below. Access network attachment point information includes: AP-ID, (3) UE identity: IMSI, (4) GAN class mark including indication of supported A/Gb mode and supported Iu mode.

Next, the providing GANC 2315 uses the information (eg, cell ID) provided by the UE to provide the FQDN or IP address of the default GANC and the associated default SEGW (in step 7) in a GA-RC discovery accept message provides This is done to direct the UE to the "local" default GANC in HPLMN to optimize network performance. A GANC port that the UE must use for registration may be included. The GAN mode indicator may be included as described in the sub-clause, the GAN mode section.

When the providing GANC 2315 cannot accept the GA-RC discovery request message, it provides a GA-RC discovery rejection message indicating the cause of rejection (in step 8). The secure IPSec tunnel to the provisioning SEGW 2320 is released (in step 9). It is possible to reuse the same IPSec tunnel for the GAN registration procedure. In this case, the IPSec tunnel is not released.

g) <u>Registration process - normal case</u>

After the discovery procedure, the UE establishes a secure tunnel with the security gateway of the default GANC provided by the providing GANC in the discovery procedure, and attempts to register with the default GANC. The default GANC may become the serving GANC for that connection by accepting registration, or the default GANC may redirect the UE performing registration to another serving GANC.

GANC redirection may be based on information provided by the UE during the registration procedure, operator selection policy or network load balancing. The GAN registration procedure has the following functions: (1) the ability to ensure that the UE is registered with the appropriate GANC entity using a redirection process, and (2) the UE is now connected via a generic IP access network and available at a special IP address It serves the function of informing the GANC of (GANC (eg) maintaining a registration context for mobile station calls), (3) providing the UE with operating parameters associated with the GAN service. The "System Information" message content applicable to the GAN cell is conveyed to the UE during the GAN registration process. Accordingly, the UE may switch to the GAN mode and trigger a NAS procedure (eg, location/routing area update, mobile terminal outgoing call, mobile station incoming call, etc.) with the core network after the registration procedure. It also serves (4) a function that allows the UE to request which GAN service is required.

24 illustrates a registration procedure in some embodiments. 24 shows each other between UE 2405 , DN 2410 , provisioning GANC 2415 , security gateway SEGW 2420 associated with provisioning GANC 2415 , and DNS server 2425 associated with provisioning GANC 2415 . Another message exchange is shown. The following steps are taken during the registration process.

24 , when the UE 2405 is provided with the FQDN of the default or serving SEGW, the UE performs a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address (in step 1). carry out When the UE has a provision IP address for the SEGW, the DNS step is omitted. DNS server 2410 provides the response (in step 2).

As shown, the UE 2405 sets up a secure IPSec tunnel to the SEGW 2420 (in step 3). This step can be omitted if the IPSec tunnel is being reused from a previously done discovery or registration. If the UE 2405 is provided with the FQDN of the default or serving GANC, the UE performs a DNS query (via secure tunnel) to resolve the FQDN to an IP address (in step 4). If the UE has an IP address for GANC, the DNS step is skipped. Next, DNS server 2425 provides a response (in step 5).

The UE 2405 then sets up a TCP connection to the TCP port on the GANC. The TCP port may be a well-known port or it may have been previously received from the network during discovery or registration. The UE 2405 attempts to register with the GANC by sending a GA-RC registration request (in step 6). The message includes: (1) Cell Info: Current camping UTRAN/GERAN cell ID with indicator indicating presence, or last LAI the UE was successfully registered with, (2) General IP access network attachment point information: the following section AP-ID defined in the identifier of GAN of VII, (3) UE identity: IMSI, (4) UE capability information, (5) GAN service request, (6) A/Gb mode support, including indication of Iu mode support GAN class mark is included.

If GANC 2415 accepts the registration attempt, GANC 2415 responds (in step 7) with a GA-RC Registration Accept message. In this case, the TCP connection and secure IPSec tunnel are not released, but remain as long as the UE is registered with this GANC.

The GA-RC registration accept message includes (1) GAN capability information (2) GAN-specific system information, and the GAN-specific system information includes: (a) GAN mode indicator: A/Gb mode GAN or Iu mode GAN, (b ) cell description of the GAN cell, (c) a location-area identification comprising a mobile country code, a mobile network code, and a location area code corresponding to the GAN cell, (d) a cell identity within the location area corresponding to the cell GAN cell, and (e) an applicable system timer value (eg, for an application-level keep-alive message transmission interval, see the Keep Alive subsection below).

Alternatively, GANC 2415 may deny the request. In this case, the GANC 2415 responds (in step 8) with a GA-RC Registration Reject message indicating the cause of the rejection. The TCP connection and secure IPSec tunnel are then released.

Alternatively, if the GANC 2415 decides to redirect the UE to the (other) serving GANC, then the GANC 2415 (in step 9) the FQDN or IP address of the target serving GANC and that the GANC has a special mode with the serving GANC. When requesting to be used together (eg, when the GANC knows that the serving GANC only supports A/Gb mode GAN), it responds with a SEGW GA-RC registration redirecting message providing a GAN mode indicator. In this case, the TCP connection is released and the secure IPSec tunnel is optionally released (in step 10) depending on whether the network indicates that the same IPSec tunnel can be reused for the next registration. The GA-RC registration redirect message may include (1) a single serving SEGW and GANC address or (2) a PLMN identity list and associated serving SEGW and GANC address. The message may also include an indication of whether the GANC address(es) may be stored in the UE for future use.

a) registration process - in case of abnormal

If the serving GANC rejects the registration request and does not provide a redirect to the other serving GANC, the UE will retry registration with the default GANC, including the failed registration attempt and cause the registration request indicates the failed serving GANC and SEGW. The UE also deletes all stored information about this serving GANC.

When the default GANC rejects the registration request and cannot provide a redirect to a suitable serving GANC, the UE may retry the discovery procedure to the serving GANC (cause indicating the failed registration attempt and default GANC provided in the final discovery procedure) including). The UE also deletes all stored information about the default GANC.

2. Cancel registration

25 illustrates deregistration initiated by UE 2505 in some embodiments. The GA-RC deregistration procedure allows the UE 2505 to exit the GAN mode (eg, when disconnected from the general IP access network) by sending a GA-RC deregistration message to the GANC 2510 (in step 1). Allows for unambiguous notification to GANC 2510 , thereby allowing GANC 2510 to free up resources allocated to UE 2505 . GANC 2510 also supports "intrinsic GAN deregistration" when the TCP connection to the UE is suddenly disconnected.

26 illustrates deregistration initiated by GANC 2610 in some embodiments. As shown, the GANC 2610 may autonomously release the UE registration context and send (in step 1) a GA-RC deregistration message to the UE 2605 . Alternatively, the GANC 2610 may unconditionally deregister the UE 2605 by closing the TCP connection with the UE. Upon power down, the GA-RC sublayer of the UE ensures that the UE is clearly disconnected from the network before completing the GA-RC deregistration procedure, if possible.

3. Registration update

27 illustrates registration update in some embodiments. The GA-RC registration update procedure allows the UE 2705 to update information in the GANC 2710 regarding changes to the identity of overlapping GERAN cells or changes to the generic IP access network point of attachment. As shown, the UE 2705 sends (in step 1) a GA-RC Registration Update Uplink message to the GANC 2710 carrying the updated information. Accordingly, the UE 2705 may be redirected to another serving GANC, or service may be denied due to, for example, operator policy.

If the UE 2705 detects UTRAN/GERAN coverage after reporting no coverage during GAN registration, the UE sends a GA-RC registration update uplink to the GANC with the updated information. If the generic IP access network point of attachment changes, the UE sends a GA-RC registration update uplink message to the GANC with the updated generic IP access network point of attachment information. When the UE needs to update the GANC with the new list of GAN service requests, the UE sends a GA-RC registration update uplink message including the new GAN service request list to the GANC.

The GANC 2710 may optionally send a GA-RC registration redirect message when it decides to redirect the UE based on the updated information (in step 2). The GANC 2710 may also selectively deregister the UE 2705 upon receiving the update by sending a GA-RC deregistration message to the UE (in step 3).

28 illustrates a registration update downlink procedure in some embodiments. The GAN registration update procedure also allows the GANC 2810 to update the GAN system information in the UE 2805 by sending a GA-RC registration update downlink message carrying the updated information to the UE, if necessary (in step 1). make it possible to update

4. keep alive

29 illustrates a keep alive process of some embodiments. The keep-alive process is a mechanism between peer GA-RC entities to indicate that the UE is still registered with the GANC. Using periodic transmission of a GA-RC keep alive message (step 1), the UE 2805 also determines that the GANC 2810 is still available using the currently established lower layer connection.

5. Cell Broadcast Information

30 illustrates a cell broadcast information mechanism of some embodiments. Cell broadcast information is a mechanism between peer GA-RC entities that enables GANC to convey UE information about cell broadcast services. The UE 3005 includes the GAN service request information indicating that the UE requests the cell broadcast service in the GA-RC registration request message and the GA-RC registration update uplink message transmitted to the GANC. The GANC 3010 then forwards the requested information (in step 1) to the UE 1105 via a GA-RC cell broadcast INFO message.

E. Certification

The Up interface supports the ability to authenticate the UE with the GANC (to establish a secure tunnel) using either GSM or UMTS credentials. Authentication between UE and GANC is performed using EAP-SIM or EAP-AKA in IKEv2.

F. Encryption and Integrity Protection

All control and user plane traffic over the Up interface is carried over a pair of IPSec ESP tunnel mode security associations (one for each direction) that are established during establishment of the IKEv2 security association. Encryption and integrity protection are achieved through a negotiated cryptographic algorithm based on the core network policy enforced by the GANC-SEGW.

G. GA-CSR connection processing

The Iu-mode GAN GA-CSR connection is a logical connection between the UE and the GANC for the CS domain. A GA-CSR connection is established when an upper layer within the UE requests establishment of a CS domain signaling connection and the UE is in GA-CSR-idle state, that is, there is no GA-CSR connection. When a successful response is received from the network, the GA-CSR responds to the upper layer with the CS domain signaling connection established and the UE entering the RRC connected mode (ie, GA-CSR-connected state).

One. GA-CSR connection setting

31 illustrates successful and unsuccessful establishment of a GA-CSR connection in some embodiments. As shown, the UE 3105 initiates the GA-CSR connection establishment by sending a GA-CSR request message to the GANC 3110 (in step 1). This message contains an establishment cause indicating the reason for establishing a GA-CSR connection.

When the GANC determines that the connection request can be accepted, the GANC 3110 informs the UE 3105 of the acceptance of the connection request by sending a GA-CSR request accept message (in step 2), and the UE sends a GA-CSR- become connected. On the other hand, when the GANC determines that the GA-CSR connection request is rejected, the GANC 3110 sends a GA-CSR request rejection message indicating the cause of rejection to the UE 3105 (in step 3), and ends the procedure. .

2. GA-CSR disconnection

32 illustrates the release of a logical GA-CSR connection between a UE and a GANC in some embodiments. As shown, the MSC 3215 instructs the GANC 3210 to release the CS resource allocated to the UE by sending a RANAP Iu Release Command message to the GANC 3210 (in step 1).

Next, the GANC 3210 confirms the resource release to the MSC 3215 using the Iu release complete message (in step 2). Next, GANC 3210 instructs UE 3205 to release resources using a GA-CSR Release message (in step 3). Finally, the UE 3205 confirms the resource release for the GANC using the GA-CSR release complete message (in step 4), and the GA-CSR state of the UE is changed to GA-CSR-idle (IDLE).

H. CS Security Mode Control

33 illustrates a message flow for secure mode control in some embodiments. As shown, the MSC 3315 sends (at step 1) a RANAP Secure Mode Command message to the GANC 3310 . This message contains an integrity key (IK) and an allowed algorithm, and optionally an encryption key (CK) and an allowed algorithm.

Next, GANC 3310 sends (in step 2) a GA-CSR Secure Mode Command message to UE 3305 . This message indicates the integrity protection and encryption settings (ie, applicable after relocation to UTRAN), and a random number. The UE stores the information for possible future use after relocation to the UTRAN.

Next, the UE 3305 calculates a MAC based on the random number calculated by the UE, the UE IMSI and the integrity key. The MAC or "message authentication code" enables the GANC to verify that the UE was able to compute the same integrity key value as the GANC received from the MSC, thereby preventing any "man in the middle" security attack. The UE 3305 then sends a GA-CSR Secure Mode Complete message to the GANC 3310 to inform the selected algorithm and computed MAC (in step 3).

The GANC 3310 then verifies the MAC using the random number provided by the MSC in step 1, the UE IMSI and the integrity key. If the GANC confirms that the MAC is correct (ie, the GANC-computed MAC is the same as the UE-computed MAC), it sends (in step 4) a secure mode complete message to the MSC 3315 . The MAC proves that the identity authenticated to the GANC is the same as the identity authenticated to the core network.

I. CS NAS Signaling Procedure

After GA-CSR connection establishment, NAS signaling may be sent from MSC to UE and from UE to MSC.

One. MSC-UE NAS signaling

34 illustrates MSC-UE NAS signaling in some embodiments. As shown, in the case of MSC-UE NAS signaling, MSC 3415 transmits the NAS PDU through the RANAP direct transmission message (in step 1) to the GANC. The GANC 3410 wraps the NAS PDU in a GA-CSR DL direct transport message (in step 2) and sends the message to the UE 3405 over the existing TCP connection.

2. UE-MSC NAS signaling

35 illustrates UE-MSC NAS signaling in some embodiments. As shown, the UE 3505 receives a request to transmit an uplink NAS PDU from the NAS layer. Assuming that the required signaling connection already exists, the UE 3505 wraps the NAS PDU in a GA-CSR UL direct transport message, and sends the message to the GANC 3510 (in step 1). The GANC 3510 relays the received message (in step 2) to the MSC 3515 via a RANAP direct transport message.

J. Mobile terminal outgoing CS call

One. GANC terminates the Iu UP protocol.

36 illustrates a step performed during a mobile station originating CS call in some embodiments. The procedure assumes that the UE is in GAN mode, that is, it is successfully registered with GANC and the GA-CSR is the serving RR entity for CS service in the UE. It is also assumed that no GA-CSR signaling connection exists between the UE and GANC (ie, GA-CSR-idle state). As shown, the GA-CSR connection establishment procedure (in step 1) is performed. In some embodiments, this procedure is performed as described in the GA-CSR Connection Establishment subsection above. Next, the UE 3605 sends a CM service request message to the GANC 3610 via a GA-CSR UL direct transmission message.

Next, the GANC 3610 establishes an SCCP connection to the MSC 3615 and (in step 3) sends a NAS PDU (ie, a CM service request message) to the MSC 3615 using the RANAP initial UE message. . The message contains a domain indicator set to the value 'CS domain'. Subsequent NAS messages between UE and MSC will be sent between GANC and MSC using RANAP direct transport messages.

The MSC 3615 may optionally authenticate (in step 4) using the UE standard UTRAN authentication procedure. The MSC 3615 may optionally initiate the security mode control procedure described in the CS security mode control subsection above (in step 5). The UE 3605 sends (in step 6) a setup message providing details about the call to the MSC and its bearer capabilities and supported codecs. This message is included in the GA-CSR UL Direct Transmission message between the UE and the GANC. The GANC sends a setup message to the MSC.

The MSC 3615 then (in step 7) indicates to the GANC with a call proceed message that it has received the call setup and will not accept additional call-setup information. The GANC sends this message (in step 7) to the UE via a GA-CSR DL direct transport message.

The MSC 3615 requests the GANC 3610 to allocate call resources using the RANAP RAB allocation request message (in step 8). MSC 3615 includes, among other parameters, RAB-ID, CN transport layer address and CN Iu transport association for user data, and an indication indicating that an Iu UP support mode is required.

GANC 3610 then (in step 9) (1) channel mode, (2) multi-rate codec configuration, (3) UDP port and IP address for uplink RTP stream, (4) bearer such as voice sample size A GA-CSR activation channel message including path setup information is sent to the UE 3605 .

Next, the UE 3605 sends (at step 10) a GA-CSR activation channel ACK indicating the UDP port for the downlink RTP stream to the GANC 3610 . Since the Iu UP support mode is indicated by the MSC in step 8, the GANC 3610 sends an Iu UP initialization packet to the MSC (in step 11).

In response, the MSC responds (in step 12) with an Iu UP initialization ACK packet. The GANC 3610 notifies the UE 3605 of completion of RAB setup (in step 13) with a GA-CSR activation channel complete message. Alternatively, steps 11 and 12 may occur prior to step 9 .

The GANC 3610 informs the MSC 3615 that the RAB has been established by sending a RANAP RAB Assignment Response message (in step 14). The MSC 3615 informs the UE 3505 that a warning message, the callee is ringing. The message is sent (at step 15) to the GANC 3610, which sends (at step 15) the message to the UE 3605 via a GA-CSR DL direct send message. If the UE has not connected an audio path to the user, a ring back is issued to the caller. Otherwise, a network-generated ring back will be provided to the caller.

Next, the MSC 3615 informs that the callee responded via a connect message. The message is sent (at step 16) to the GANC 3610 and the GANC sends (at step 16) the message to the UE via a GA-CSR DL direct send message. The UE connects the user to the audio path. If the UE is generating a ring back, it stops and connects the user to the audio path.

The UE 3605 then sends a Connect Ack message in response (in step 17), and the two means are connected for the voice call. This message is included in the GA-CSR UL Direct Transmission message between the UE and the GANC. The GANC sends a Connect Ack message to the MSC. At this point, two-way voice traffic flows between the UE 3605 and the MSC 3615 via the GANC 3610 (in step 18).

2. The UE terminates the Iu UP protocol.

Some embodiments use an alternative procedure for a mobile station originating CS call. 37 illustrates the steps performed during a mobile station originating CS call in these embodiments. The procedure assumes that the UE is in GAN mode, that is, the UE is successfully registered with GANC and the GA-CSR is the serving RR entity for CS service in the UE. It is also assumed that no GA-CSR signaling connection exists between the UE and GANC (ie, GA-CSR-idle state). Steps 1 to 8 are performed in the same manner as described for steps 1 to 8 shown in FIG. 36 above, and are not repeated for simplicity.

Since the Iu UP support mode is indicated by the MSC in step 8 (as described with reference to FIG. 36), the GANC indicates (in step 9) that the Iu UP support mode is required in the GA-CSR activation channel message, and the UE 3705 sends an Iu UP initialization packet to MSC 3715 (at step 10). In response, the MSC 3715 responds (in step 11) with an Iu UP initialization ACK packet. Next, the UE 3705 sends a GA-CSR activation channel ACK to the GANC 3710 (at step 12 ).

The GANC 3710 informs the MSC 3715 that the RAB has been established by sending a RANAP RAB Assignment Response message (in step 13). GANC 3710 also sends (at step 14) a GA-CSR Activate Channel Complete message to UE 3705 . Steps 15 to 18 are performed as described above for steps 15 to 18 shown in FIG. 36 and are not repeated for simplicity.

K. Mobile station incoming CS call

38 illustrates a step performed during a mobile station terminating CS call in some embodiments. The description of the procedure assumes that the UE is in GAN mode, that is, the UE is successfully registered with GANC and the GA-CSR is the serving RR entity for CS service in the UE. It is also assumed that no GA-CSR signaling connection exists between the UE and the GANC (ie, the UE is in the GA-CSR-idle state). When the mobile station incoming call arrives at the MSC 3815, as shown in FIG. 38, the MSC 3815 sends (in step 1) a RANAP paging message to the GANC 3810 identified via the last location update it received. and, if available, include the TMSI. The IMSI of the mobile station being paged is always included in the request.

The GANC 3810 then uses the IMSI provided by the MSC 3815 to identify the UE registration context. Next (in step 2) the UE 3805 is paged using a GA-CSR paging request message. The message contains the TMSI if available in the request from the MSC, otherwise only the IMSI of the UE.

The UE 3805 responds with a GA-CSR paging response. The UE transitions to the GA-CSR connected state. GANC 3810 establishes an SCCP connection to MSC 3815 . The GANC 3810 then sends a paging response to the MSC 3815 using a RANAP initial UE message (in step 4). Subsequent NAS messages between the UE and the core network will be sent between the GANC and the MSC using RANAP direct transport messages.

The MSC 3815 may optionally authenticate the UE 3805 using a standard UTRAN authentication procedure (in step 5). The MSC may optionally update the security configuration in the UE via GANC as described in the CS Security Mode Control subsection above (in step 6).

The MSC 3815 then initiates call setup using a setup message sent to the UE via GANC (in step 7). The GANC sends this message (in step 7) to the UE 3805 via a GA-CSR DL direct transport message.

Next, the UE 3805 checks its compatibility with the requested bearer service in setup and, after modifying the bearer service if necessary, responds with a call acknowledgment using a GA-CSR UL direct transmission message. If the setup includes a signal information element, the UE warns the user using the indicated signal, otherwise the UE warns the user after successful configuration of the user plane. GANC 3810 sends (at step 8) a call acknowledgment message to MSC 3815.

Next, the MSC 3815 triggers the setup (voice bearer channel) of the RTP stream between the GANC and the UE as in steps 8 to 14 of the mobile terminal originating CS call scenario described above (in step 9). (3810) and the allocation procedure is initiated.

Next, the UE 3805 informs (in step 10) that it is to warn the user through a warning message included in the GA-CSR UL direct transmission message. The GANC sends a warning message (at step 10) to the MSC. The MSC sends a corresponding warning message to the caller.

The UE 3805 then informs (in step 11) that the protector has responded via the attach message included in the GA-CSR UL direct transmission message. GANC 3810 sends (at step 11) a connect message to MSC 3815. The MSC sends a corresponding connect message to the caller and connects the audio. The UE connects the user to the audio path.

The MSC 3815 then acknowledges the GANC 3810 with a Connect Ack message (at step 12). The GANC sends this message (in step 12) to the UE 3805 via a GA-CSR DL Direct Send message. The two means on the call are connected on the audio path. At this time, the two-way voice traffic flows between the UE and the MSC via the GANC (in step 13).

L. CS call clearing

39 illustrates call clearing initiated by a UE in some embodiments. As shown, UE 3905 sends (in step 1) a detach message to MSC 3915 to release the call. This message is included in the GA-CSR UL Direct Transmission message between the UE 3905 and the GANC 3910 . The GANC 3910 sends (in step 1) a detach message to the MSC (ie, using a RANAP direct send message).

The MSC 3915 then responds to the GANC with a release message (in step 2). The GANC sends this message (in step 2) to the UE 3905 using a GA-CSR DL direct transport message. UE 3905 responds (in step 3) with a Release Complete message. This message is included in the GA-CSR UL Direct Transmission message between the UE and the GANC. The GANC (in step 3) sends a detach message to the MSC. The MSC triggers the release of the connection (in step 4) as described in the GA-CSR Connection Release subsection below.

M. CS Handover

One. CS handover from GERAN to GAN

a) <u>GANC terminates Iu UP protocol</u>

40 illustrates CS handover from GERAN to GAN. The description of the GERAN-GAN handover procedure assumes the following: (1) the UE is on an active call in GERAN, (2) the UE mode selection is GAN-preferred, or GERAN/UTRAN-preferred, if the current Assume that the RxLev from the serving cell falls below a defined threshold. In some embodiments, this threshold may be specified as a fixed value or may be provided to the UE by the GERAN BSS in dedicated mode. (3) the UE is successfully registered with the GANC, so that the UE can obtain the GAN system information, and (4) the GERAN provides information about the adjacent 3G cell as provided in the AS-related element of the system information obtained from the GANC Therefore, it is assumed that one of the cells in the 3G neighbor cell list can match 3G cell information associated with GANC. As shown, the UE 4005 starts including the GAN cell information in the measurement report message for the GERAN BSC 4015 . The UE 4005 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but rather an artificial value (eg RxLev = 63) that allows the UE to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the GERAN BSC 4015 decides to handover to the GAN cell. The BSC 4015 initiates handover preparation by sending a handover request message identifying the target 3G RNC (GANC) to the MSC 4020 (in step 2).

The MSC 4020 requests the target GANC 4010 to allocate resources for handover (in step 3) using a relocation request message. The UE is identified by the included IMSI parameter.

Since the Iu UP support mode is indicated, the GANC 4010 sends an Iu UP initialization packet to the MSC (in step 4). The MSC responds (in step 5) with an Iu UP initialization ACK packet.

The GANC 4010 constructs a handover command message to the UTRAN and transmits it to the MSC 4020 through a relocation request acknowledgment message (in step 6). The MSC sends a handover command message to the UTRAN (in step 7) to the GERAN BSC 4015 through a BSSMAP handover command message to complete the handover preparation.

Next, the GERAN BSC 4015 sends an intersystem-UTRAN handover command message including a handover command message to the UTRAN to the UE 4005 to initiate the handover to the GAN (in step 8). The UE does not switch the audio path from the GERAN to the GAN until the handover is complete (ie, until sending a GA-CSR handover complete message) to keep the audio dropout short.

The UE 4005 accesses the GANC 4010 using the GA-CSR handover access message (in step 9) and provides it to the full intersystem-UTRAN handover command message received from the GERAN. GANC 4010 (in step 10) (1) channel mode, (2) multi-rate codec configuration, (3) UDP port and IP address for uplink RTP stream, (4) bearer path setup such as voice sample size A GA-CSR activation channel message including information is sent to the UE 4005 .

Next, the UE 4005 sends (at step 11) a GA-CSR Activation Channel ACK indicating the UDP port for the downlink RTP stream to the GANC 4010 . The GANC 4010 informs the UE 4005 of completion of RAB setup (in step 11) with a GA-CSR activation channel complete message.

The UE 4005 sends a GA-CSR handover complete message to indicate completion of the handover procedure at the end (in step 13). The UE 4005 switches the user from the GERAN user plane to the GAN user plane. The GANC 4010 indicates to the MSC 4020 that it has detected the UE using the relocation detection message (in step 14). The CN can now selectively switch the user plane from the source GERAN to the target GAN.

Bidirectional voice traffic now flows (in step 15) between the UE 4005 and the MSC 4020 via the GANC 4010. The target GANC 4010 indicates that the handover is completed using the relocation complete message (in step 16). If it has not done so before, the CN now switches the user plane from the source GERAN to the target GAN.

The CN uses a clear command message (in step 17) to disconnect the connection to the source GERAN. Finally, the source GERAN 4015 confirms the release of the GERAN resources allocated for this call using the clear complete message (in step 18).

b) <u>UE terminates Iu UP protocol</u>.

Some embodiments use an alternative procedure for CS handover from GERAN to GAN. 41 illustrates the steps performed during GERAN-GAN in these embodiments. The description of the GERAN-GAN handover procedure assumes that: (1) the UE is on an active call in GERAN, and (2) the UE mode selection is GAN-preferred, or GERAN/UTRAN-preferred. , it is assumed that RxLev from the current serving cell falls below the defined threshold. In some embodiments, this threshold may be specified as a fixed value or provided to the UE by GERAN BSS in dedicated mode, (3) the UE is successfully registered with GANC, so that the UE can obtain GAN system information; , (4) assume that GERAN provides information about neighboring 3G cells as provided in the AS-related element of system information obtained from GANC so that one of the cells in the 3G neighbor cell list matches the 3G cell information associated with GANC do. Steps 1 to 3 are performed as described for steps 1 to 3 shown in FIG. 40 above, and are not repeated for the sake of simplicity.

GANC 4110 (in step 4) supports (1) channel mode, (2) multi-rate codec configuration, (3) UDP port and IP address for uplink RTP stream, (4) voice sample size, and Iu UP A GA-CSR activation channel message including bearer path setup information such as an indication indicating that the mode is required is sent to the UE 4105 . In some embodiments, the GANC 4110 includes a radio access bearer (RAB) parameter, and an Iu UP parameter (eg, an Iu UP mode when the assisted mode is used for an AMR voice call).

Since the Iu UP support mode is indicated, the UE 4110 transmits the Iu UP initialization packet indicated in the GA-CSR activation channel message (in step 5) to the IP address and the UDP port.

The MSC 4115 responds (in step 6) with an Iu UP initialization ACK packet. The MSC 4115 sends a message with the source IP address and UDP port number of the received initialization packet. The UE 4105 sends (at step 7) a GA-CSR activation channel ACK to the GANC 4110 . The GANC 4110 constructs a handover command message to the UTRAN and sends it to the CN 4115 via a relocation request acknowledgment message (in step 8).

The GANC 4110 informs the UE 4105 of the completion of RAB setup (in step 9) via a GA-CSR Activate Channel Complete message. An end-to-end audio path now exists between the UE 4105 and the MSC 4115 . The MSC 4115 transmits a handover command message to the UTRAN to the GERAN BSC 4120 through a BSSMAP handover command message (in step 10), and completes handover preparation.

The GERAN BSC 4120 sends (in step 11) an intersystem-UTRAN handover command message including a handover command message to the UTRAN to the UE to initiate a handover to the GAN. The UE does not switch to the audio path from GERAN to GAN until handover is complete (ie, until sending a GA-CSR handover complete message), in order to keep the audio dropout short.

The UE accesses the GANC 4110 using the GA-CSR handover access message (in step 12) and provides the full intersystem-UTRAN handover command message received from the GERAN. The GANC 4110 indicates to the MSC 4115 that it has detected the UE using the relocation detection message (in step 13). The MSC 4115 may now selectively switch the user plane from the source GERAN to the target GAN. Bidirectional voice traffic now flows (in step 14) between the UE and MSC 4115 via GANC 4110.

The UE sends a GA-CSR handover complete message to indicate completion of the handover procedure at the end (in step 15). The UE switches the user from the GERAN user plane to the GAN user plane.

The target GANC 4110 indicates that the handover is completed using the relocation complete message (in step 16). If this has not been done before, the MSC 4115 now switches the user plane from the source GERAN to the target GAN.

Finally, the MSC 4115 uses a clear command message (at step 17) to disconnect the connection to the source GERAN. The source GERAN confirms the release of the GERAN resources allocated for this call using the clear complete message (in step 18).

2. CS handover from UTRAN to GAN

a) <u>GANC ends the Iu UP packet</u>

42 illustrates CS handover from UTRAN to GAN in some embodiments. The description of the UTRAN-GAN handover procedure assumes the following. That is, (1) the UE is on an active call in the UTRAN, (2) the UE is instructed by the RNC to make inter-frequency measurements (i.e., the GAN cell is assigned a frequency value different from the frequency used in the UTRAN) (a) if the UE is in the GAN preferred mode configured for Event 2A, the UE processes the parameters associated with Event 2A in a GAN-specific manner for reporting of EGAN ("Radio Resource Control (RRC)" of the 3GPP TS 25.331 standard) Protocol Specification" (hereinafter "3GPP TS 25.331")), (b) when the UE is in GERAN/UTRAN preferred mode and event 2A is configured for the GAN cell, this event is triggered and from the UE's neighbor cell list If the UTRAN cells of UTRAN do not satisfy the trigger condition of this event (as described in 3GPP TS 25.331), the UE may only transmit measurements on the GAN cell. (3) It is assumed that the UTRAN causes one of the cells in the neighbor cell list to match the cell associated with the GANC by providing information about the neighbor cell as provided in the AS-related element of the system information obtained from the GANC.

As shown in FIG. 42 , the UE 4205 starts to include information about the GAN cell in the measurement report message sent to the RNC 4215 (in step 1). The UE 4205 reports the highest signal level for the GAN cell. This is not an actual measured signal level on the GAN, but rather an artificial value that allows the UE 4205 to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the RNC 4215 decides to initiate a handover to the GAN cell. The RNC 4215 starts the preparation phase of the relocation procedure by sending (in step 2) a relocation request message to the MSC identifying the target (GAN) cell.

Next, steps 3 to 5 shown in FIG. 42 are performed as described for steps 3 to 5 of the GERAN-GAN handover subsection above. The target GANC 4210 (in step 6) requests a handover using a relocation request acknowledgment message indicating that it can support the requested handover and includes a physical channel reconfiguration message indicating the radio channel to which the UE should be directed. Acknowledge the message.

Next, the MSC 4220 sends a relocation command message to the RNC 4215 (in step 7) to complete the relocation preparation. RNC 4215 sends (in step 8) a physical channel reconfiguration message to UE 4205 to initiate handover to GAN. The UE does not switch its audio path from the UTRAN to the GAN until the handover is complete (ie, until sending a GA-CSR handover complete message) to keep the audio dropout short.

Next, steps 9 to 16 shown in FIG. 42 are performed similarly to steps 9 to 16 for the GERAN-GAN handover described above. The MSC 4220 then disconnects the connection to the source RNC using the Iu release command (at step 17). Finally, the source RNC 4215 confirms the release of the UTRAN resource allocated for this call using Iu Release Complete (in step 18).

b) <u>UE terminates the Iu UP packet</u>.

Some embodiments use an alternative procedure for CS handover from UTRAN to GAN. 43 illustrates the step performed during UTRAN-GAN in these embodiments. As shown, the UE starts to include information about the GAN cell (in step 1) in the measurement report message sent to the RNC 4320 . The UE reports the highest signal level for the GAN cell. This is not an actual measured signal level on the GAN, but rather an artificial value that allows the UE to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the RNC 4320 decides to initiate a handover to the GAN cell. The RNC 4320 starts the preparation phase of the relocation procedure by sending (in step 2) a relocation request message indicating the target GAN cell to the MSC 4315 .

The MSC 4315 requests (in step 3) to allocate resources for handover to the target GANC 4310 using a relocation request message. The UE 4305 is identified by an included IMSI parameter.

GANC 4310 (in step 4) (1) UDP port and IP address for uplink RTP stream, (2) radio access bearer (RAB) parameter, (3) Iu UP parameter (eg, support mode is AMR voice When used for a call, a GA-CSR activation channel message including bearer path setup information received in a relocation request message (such as Iu UP mode) is transmitted to the UE 4305 .

Since the Iu UP support mode is indicated, the UE 4305 sends (in step 5) an Iu UP initialization packet to the IP address and UDP port indicated in the GA-CSR activation channel message. This message is routed to the core network 4315 (eg, R4 media gateway).

The MSC 4315 responds (in step 6) with an Iu UP initialization ACK packet. MSC 4315 sends the message to the source IP address and UDP port number of the received initialization packet. The UE 4305 sends (in step 7) a GA-CSR activation channel ACK to the GANC 4310 .

The target GANC 4310 uses (in step 8) a relocation request acknowledgment message indicating that it can support the requested handover and includes a physical channel reconfiguration message indicating the radio channel to which the UE 4305 should be directed. Acknowledge the handover request message.

The GANC 4310 informs the UE 4305 of completion of RAB setup with a GA-CSR activation channel complete message (in step 9). An end-to-end audio path now exists between the UE 4305 and the MSC 4315 . The MSC 4315 sends a relocation command message to the RNC 4320 (at step 10) to complete the relocation preparation.

The RNC 4320 sends (at step 11) a physical channel reconfiguration message to the UE to initiate handover to the GAN. The UE does not switch its audio path from the UTRAN to the GAN until the handover is complete (ie, until sending a GA-CSR handover complete message) to keep the audio dropout short. The UE accesses the GANC 4310 using the GA-CSR handover access message (in step 12) and provides the full physical channel reconfiguration message received from the RNC 4320.

The GANC 4310 indicates to the MSC 4315 that it has detected the UE using the relocation detection message (in step 13). The MSC 4315 can now selectively switch the user plane from the source RNC 4320 to the target GANC 4310 . Bidirectional voice traffic now flows (in step 14) between the UE and MSC 4315 via GANC 4310.

At this point (in step 15), the UE sends a GA-CSR handover complete message to indicate the completion of the handover procedure. The UE switches the user from the UTRAN user plane to the GAN user plane. The target GANC 4310 indicates that the handover is complete using the relocation complete message (in step 16). If this has not been done before, the CN 4315 now switches the user plane from the source RNC 4320 to the target GANC 4310 .

Finally, the MSC 4315 disconnects the connection to the source RNC 4320 using the Iu release command (at step 17). The source RNC 4320 confirms (in step 18) the release of the UTRAN resource allocated for this call using Iu Release Complete.

3. CS handover from GAN to GERAN

44 illustrates a GAN to GERAN handover procedure in some embodiments. The procedure description in this subclause assumes that: (1) the UE is on an active call in GAN Iu-mode, (2) GERAN becomes available, and (a) UE mode selection is GERAN/UTRAN -preferred, or (b) the UE mode selection is GAN-preferred and the UE starts out of GAN coverage based on its local measurements and received RTCP reports as well as uplink quality indications received from GANC. The handover procedure from GAN to GERAN is always triggered by the UE. As shown in FIG. 44 , the following steps are performed during handover from GAN to GERAN.

The GANC 4410 may send a GA-CSR uplink quality indication when there is a problem with the uplink quality for an ongoing call (in step 1). The uplink quality indication is information sent by the GANC to the UE, indicating the crossing of the uplink quality threshold in the uplink direction. Whenever the UE receives an indication of poor quality, it must initiate a handover procedure as described in the next step. Alternatively, the UE may use its local measurement or received RTCP report to determine whether to initiate a handover procedure.

As shown, the UE 4405 (in step 2) selects the channel mode and list of target GERAN cells identified by the CGI, in order of preference (eg, ranked by the Cl pathloss parameter) for handover. It sends a GA-CSR handover information message indicating the GANC 4410 and includes the received signal strength for each identified GERAN cell. This list is the most recent information available from the GSM RR subsystem. In addition, the GA-CSR handover information message may include a list of target UTRAN cells ranked in order of preference for handover, and received signal strength for each identified UTRAN cell.

When the serving GANC selects the target GERAN cell, a handover procedure to the GERAN is performed. The serving GANC 4410 uses the relocation request (in step 3) to inform the MSC 4420 that a handover is required and starts the handover preparation by including the GERAN cell list provided by the UE. The GANC may only contain a subset of the cell list provided by the UE.

Next, the MSC 4420 selects a target GERAN cell and requests to allocate a necessary resource using a handover request message (in step 4). The target GERAN BSC 4415 constructs a handover command message providing information on the allocated channel and transmits it to the MSC 4420 through a handover request acknowledgment message (in step 5).

The MSC 4420 informs the GANC 4410 to handover the UE 4405 to GERAN using a relocation command message (in step 6), and ends the handover preparation phase. The GANC sends (in step 7) a GA-CSR handover command to the UE containing details about the target resource allocation sent by the GERAN.

Next, the UE 4405 (at step 8) sees the handover, so that the target GERAN BSC 4415 can correlate this handover access with the handover command message previously sent to the MSC in response to the handover request. Sends a "Um: Handover Access" message containing the element. The target GERAN BSC 4415 confirms the detection of the handover to the MSC 4420 using the handover detection message (in step 9).

At this point, the MSC 4420 switches the user plane to the target BS (at step 10). The GERAN BSC 4415 provides physical information to the UE (ie, timing progress) so that the UE synchronizes with the GERAN (in step 11). The UE 4405 informs that the GERAN BSC 4415 handover is complete using the handover complete (in step 12).

The GERAN BSC 4415 confirms the completion of the handover to the MSC 4420 through a handover complete message (in step 13). The MSC 4420 may use the target CGI used in the handover procedure for charging purposes.

Bidirectional voice traffic now flows (in step 14) between UE 4405 and MSC 4420 via GERAN BSC 4415. Upon receipt of confirmation of the completion of the handover, the MSC 4420 instructs the GANC to release the resources allocated to the UE via the Iu Release command (in step 15).

Next, the GANC 4415 instructs the UE 4405 to release resources using a GA-CSR Release message (in step 16). The GANC 4410 confirms the resource release to the MSC 4420 using the Iu release complete message (in step 17).

The UE 4405 confirms the resource release to the GANC 4410 using the GA-CSR Release Complete message (in step 18). The UE 4405 may finally deregister from the GANC using a GA-RC deregistration message (in step 19).

4. CS handover from GAN to UTRAN

45 illustrates a handover procedure from GAN to UTRAN in some embodiments. The procedure description assumes that: (1) the UE is on an active call in GAN, (2) the UE can operate in all GAN, GERAN and UTRAN modes, (3) the UTRAN becomes available, (a) the UE is in GERAN/UTRAN-preferred mode, or (b) UE mode selection is GAN preferred, leaving GAN coverage based on its local measurements and received RTCP reports as well as uplink quality indications received from GANC Assume to start The handover procedure from the GAN is always triggered by the UE. As shown in FIG. 45 , the following steps are performed during handover from GAN to UTRAN.

The GANC 4510 may send a GA-CSR uplink quality indication if there is a problem with the uplink quality for the on-going call (in step 1). The uplink quality indication is information sent by the GANC 4510 to the UE 4505 indicating the crossing of the uplink quality threshold in the uplink direction. Whenever the UE 4505 receives an indication of poor quality, it must initiate a handover procedure as described in the next step. Alternatively, the UE may use its local measurement or received RTCP report to determine whether to initiate a handover procedure.

Next, the UE 4505 sends (in step 2) a GA-CSR handover information message indicating the channel mode and the list of candidate target UTRAN and GERAN cells to the serving GANC in order of preference for handover, and identifies each Include the received signal strength for the specified cell. A UTRAN cell is identified by a PLMN ID, LAC and 3G cell identity (as defined in 3GPP T (25.331)).

If the serving GANC 4510 selects the UTRAN as the target RAT, a handover procedure to the UTRAN is performed. Serving GANC 4510 initiates handover preparation by informing MSC 4520 that handover is required by including the UTRAN cell list provided by UE 4505 using a relocation request (in step 3). The GANC 4510 may include a subset of the cell list provided by the UE 4505 .

The MSC 4520 initiates the handover procedure towards the target RNC 4515 identified by the serving GANC. The MSC 4520 requests (at step 4) to allocate the necessary resources using a relocation request from the target RNC 4515 . The target RNC 4515 forms a physical channel reconfiguration message providing information about the allocated UTRAN resources and sends it to the MSC 4520 through a relocation request acknowledgment message (in step 5).

Next, the MSC 4520 informs the serving GANC 4510 to handover the UE to the UTRAN using a relocation command message (including a physical channel reconfiguration message) (in step 6), and initiates the handover preparation step. quit

The serving GANC 4510 sends (in step 7) a GA-CSR handover command to the UE that includes details about the target resource allocation sent by the UTRAN. The target RNS 4515 achieves uplink synchronization on the Uu interface (in step 8).

The target RNC 4515 confirms the detection of the handover to the MSC using a relocation detection message (in step 9). At this point the MSC 4520 switches the user plane to the target RNS 4515 (at step 10).

Next, the UE 4505 informs the UTRAN RNC 4515 that the handover is complete using a handover to UTRAN complete message (in step 11). The UTRAN RNC 4515 confirms the completion of the handover to the MSC 4520 through a relocation complete message (in step 12). If the user plane was not switched in step 10, the MSC 4520 switches the user plane to the target RNS.

Bidirectional voice traffic now flows (in step 13) between the UE 4505 and the MSC 4520 via the UTRAN RNC 4515. Upon receipt of confirmation of completion of the handover, the MSC 4520 instructs the serving GANC 4510 to release the resources allocated to the UE via an Iu release command (in step 14).

The serving GANC 4510 then instructs the UE 4505 to release the resource using a GA-CSR release message (in step 15). The serving GANC 4510 confirms the resource release to the MSC 4520 using the Iu release complete message (in step 16).

The UE 4505 confirms the resource release to the serving GANC 4510 (in step 17) using the GA-CSR release complete message. The UE 4505 may finally deregister from the serving GANC 4510 using a GA-RC deregistration message (in step 18).

N. GA-PSR connection processing

The Iu-mode GA-PSR connection is a logical connection between the UE and the GANC for the PS domain. The GA-PSR connection is established when an upper layer within the UE requests establishment of a requested PS domain signaling connection and the UE is in GA-PSR-idle state, that is, when there is no GA-PSR connection. When a successful response is received from the network, the GA-PSR responds to the upper layer that the PS domain signaling connection has been established and the UE has entered the RRC connected mode (ie, the GA-PSR-connected state).

One. GA-PSR connection setting

46 illustrates successful and unsuccessful establishment of a GA-PSR connection in some embodiments. As shown, the UE 4605 initiates the GA-PSR connection establishment by sending a GA-PSR request message to the GANC 4610 (in step 1). This message contains an establishment cause indicating the reason for establishing a GA-PSR connection. If the GANC 4610 determines that the GA-PSR connection request can be accepted, the GANC 4610 informs the UE 4605 of the acceptance of the connection request by sending a GA-PSR request accept (in step 2), which Enter the GA-PSR-connected state. Alternatively, if the GANC 4610 determines that the GA-PSR connection request should be rejected, the GANC 4610 sends (in step 3) a GA-PSR request rejection indicating the reason for the rejection to the UE ZC05, and completes the procedure. .

2. Disconnect GA-PSR

47 illustrates the release of a logical GA-PSR connection between a UE and a GANC in some embodiments. During release, the following steps are performed. As shown, the SGSN 4715 instructs the GANC 4710 to release the PS resources allocated to the UE by sending a RANAP Iu Release Command message to the GANC 4710 (in step 1).

Next, the GANC 4710 confirms the resource release to the SGSN 4715 using the Iu release complete message (in step 2). Next, the GANC 4710 instructs the UE 4705 to release the resource using the GA-PSR Release message (in step 3). Finally, the UE 4705 confirms the resource release for the GANC 4710 using the GA-PSR release complete message (in step 4), and the GA-PSR state of the UE changes to GA-PSR-idle.

O. PS Security Mode Control

48 illustrates a message flow for PS security mode control in some embodiments. As shown, SGSN 4815 sends (in step 1) a RANAP Secure Mode Command message to GANC 4810 . This message contains an integrity key (IK) and an allowed algorithm, and optionally an encryption key (CK) and an allowed algorithm.

The GANC 4810 then sends a GA-PSR secure mode command message to the UE 4805 (in step 2). This message indicates the integrity protection and encryption settings (ie, applicable after relocation to UTRAN), and a random number. The UE stores the information for possible future use after relocation to the UTRAN.

Next, the UE 4805 calculates a message authentication code (MAC) based on the random number calculated by the UE, the UE IMSI and the integrity key. The UE 4805 then sends a GA-PSR Secure Mode Complete message to the GANC 4810 to inform (in step 3) its selected algorithm and computed MAC.

The GANC 4810 then verifies the MAC using the random number provided by the SGSN in step 1, the UE IMSI and the integrity key. If the GANC verifies that the MAC is correct, it sends (at step 4) a secure mode complete message to the SGSN 4815. The MAC proves that the identity authenticated to the GANC is the same as the identity authenticated to the core network.

P. PS NAS Signaling Procedure

After GA-PSR connection establishment, NAS signaling is sent from SGSN to UE and from UE to SGSN.

One. SGSN-UE NAS signaling

49 illustrates SGSN-UE PS NAS signaling in some embodiments. As shown, for SGSN-UE NAS signaling, SGSN 4915 sends (in step 1) a NAS PDU to GANC via a RANAP direct transmission message. The GANC 4910 wraps the NAS PDU in a GA-PSR DL direct transport message and sends the message (in step 2) to the UE 4905 over the existing TCP connection.

2. UE-SGSN NAS signaling

50 illustrates UE-SGSN NAS signaling in some embodiments. As shown, the UE 5005 receives a request from the NAS layer to transmit an uplink NAS PDU. Assuming that the required signaling connection already exists, the UE 5005 wraps the NAS PDU in a GA-PSR UL direct transport message and sends the message to the GANC 5010 (in step 1). The GANC 5010 relays the received message (in step 2) to the SGSN 5015 currently serving the UE via a RANAP direct transport message.

Q. GA-PSR packet transmission channel management procedure

The GA-PSR Packet Transport Channel (GA-PSR PTC) provides an association between the UE and the network for the transmission of GPRS user data over the Up interface (ie over GAN in Iu-mode). PTC uses the GTP-U protocol running over UDP transport. The endpoint address of the PTC is identified by the IP address and UDP port assigned to the PTC in the UE and network during the PTC activation procedure. The UDP port number for GTP-U is as defined in "UTRAN Iu Interface Data Transmission and Transmission Signaling" (hereinafter "3GPP TS 25.414") of the 3GPP TS 25.414 standard.

Multiple PTC instances between the UE and the network can be activated simultaneously using the same endpoint address. Each PTC instance is assigned a unique GTP-U tunnel endpoint ID (one on the UE and one on the network) during the activation procedure. The UE and GANC manage the activation and deactivation of PTC instances based on data transfer requests and configurable PTC timers.

One. Status of GA-PSR packet transmission channel

A UE in the GA-PSR-connected state may be in one of two PTC states: PTC-Standby or PTC-Active. The PTC-standby state is an initial/default PTC state of the UE when it is in the GA-PSR-connected state of the GAN mode. The UE cannot transmit GPRS user data to or receive from the network. The UE needs to activate the PTC by sending GPRS user data. If the UE successfully establishes the PTC, the UE transitions to the PTC-active state.

In the PTC-active state, the UE is in the GA-PSR-connected state, the PTC is active between the UE and the network, and the UE can send and receive GPRS user data to and from the network. Several events can activate the GA-PSR PTC on the UE side. These events include either the UE initiates uplink user data transmission or the GANC initiates PTC activation, ie the UE receives a GA-PSR-ACTIVATE-PTC-Request message from the GANC.

Upon successful PTC activation and in parallel with the transition to the PTC-active state, the UE starts the PTC timer. When the PTC timer expires, the UE sends a message to the GANC to initiate PTC activation release. Upon successful PTC activation release, the UE transitions to the PTC-standby state.

At any time in the GA-PSR-connected state and the PTC-active state, the UE may receive the GA-PSR release message. In addition to requesting release of the GA-PSR session, this is interpreted as an implicit PTC deactivation command by the UE.

At any time in GAN mode, when the serving RR entity switches to GSM-RR/UTRAN-RRC, the GA-PSR is separated from the GPRS SAPs, and the UE enters the GERAN/UTRAN mode. At the same time, the UE will release the associated PTC regardless of the PTC timer state.

The UE GA-PSR entity maintains one PTC for each active PDP context. The PTC timer is restarted in association with the PDP context whenever an uplink user data packet is transmitted or a downlink user data packet is received. The PTC timer value is provided to the UE as part of the GAN registration procedure (ie, via the GA-RC registration accept message).

2. PTC Initial Activation

51 illustrates a packet transport channel initial activation procedure assuming that the UE is in the GA-PSR-idle state. As shown, the following steps are performed. The GA-PSR connection establishment procedure (in step 1) is performed as described in the GA-PSR connection establishment subsection above. The UE 5105 transitions to a GA-PSR-connected state and a PTC-standby state. Next, an additional PS signaling procedure is performed (in step 2). Examples of these signaling procedures are illustrated in the following subsections PDP Context Activation and Network Request PDP Context Activation.

Next, SGSN 5115 initiates the RAB assignment procedure (in step 3), RAB-ID for user data, CN transport layer address (IP address) and CN Iu transport association (GTP-U terminal endpoint identifier, TEID). The GANC 5110 sends a GA-PSR activation PTC request message to the UE to request activation of the packet transport channel (in step 4). The message contains the RAB-ID, the TEID assigned to the UE by the GANC, and the GANC IP address and GANC TEID. If the GANC is configured so that the UE can send the PTC packet (i.e. GTP-U message) directly to the SGSN (i.e. the configuration illustrated in Fig. 17), the GANC sets the GANC IP address to the CN IP address and sets the GANC TEID to the CN TEID, otherwise GANC assigns the local address as the GANC IP address and the GANC-assigned TEID as the GANC TEID, and sends this information to the UE (ie the configuration illustrated in FIG. 18 ). The UE 5105 acknowledges the PTC activation (in step 5).

GANC 5110 sends a RAB assignment response message to SGSN 5115 to complete the RAB assignment procedure (in step 6). If the GANC is configured such that the SGSN 5115 can send the GTP-U message directly to the UE 5105 (ie, the configuration illustrated in FIG. 17 ), the GANC 5110 sets the RAN IP address to the UE's IP address and the RAN TEID to the TEID assigned to the UE by the GANC; otherwise, the GANC assigns the local address as the RAN IP address and the GANC-assigned TEID as the RAN TEID, and assigns this information to the SGSN (i.e., as illustrated in FIG. 18 ). config) to

Next, the GANC 5110 informs the UE 5105 of the completion of RAB setup with a GA-PSR activation PTC complete message (in step 7). Upon receipt of the message, the UE transitions to the PTC-active state and starts the PTC timer. Next, an additional PS signaling procedure is performed (step 8). Examples of these PS signaling are illustrated in the following subsections PDP Context Activation and Network Request PDP Context Activation. The UE 5105 initiates uplink user data transmission via the established PTC (in step 9) and the SGSN 5115 may use the same transport channel to transmit the downlink user data packet.

3. PTC data transfer

52 illustrates the transmission of a GPRS user data packet over a GAN packet transport channel. This scenario assumes that user data is transported transparently between the UE and the core network (ie the configuration illustrated in FIG. 17 ). As shown, the following steps are performed.

If necessary, the GAN PTC is established (in step 1) as specified in the sub-clause PCT Initial Activation above. Upon establishing the GA-PSR PTC, the UE 5205 enters the PTC-active state to start the PTC timer. Next, the UE 5205 (in step 2) implements the standard GTP-U protocol as specified in "GPRS Tunneling Protocol (GTP) over Gn and Gp Interfaces" (hereinafter "3GPP TS 29.060") of the 3GPP TS 29.060 standard. to initiate transmission of the uplink user data packet and restart the PTC timer.

SGSN 5215 then transmits the downlink user data packet using the same PTC associated with the particular PDP context (in step 3). Downlink user data packets are transmitted using the standard GTP-U protocol specified in 3GPP TS 29.060. Upon receiving the downlink data packet, the UE restarts the associated PTC timer. Additional uplink and downlink user data packets are sent (in step 4) over the same PTC described in steps 2 and 3, respectively. After each transmit/receive, restart the UE PTC timer. When the configuration illustrated in FIG. 18 is used, an uplink GTP-U packet is sent from the UE to the GANC and then relayed from the GANC to the SGSN. Likewise, downlink GTP-U packets are relayed from SGSN to GANC and then from GANC to UE.

4. MS-initiated PTC activation off

53 shows a scenario when the UE deactivates the packet transport channel after the PTC timer expires. The UE is in a GA-PSR-connected state and a PTC-active state. As shown, the following steps are performed.

The PTC timer associated with one of the active packet transport channels expires (in step 1). The UE 5305 sends (in step 2) a GA-PSR Deactivation PTC Request message including a RAB-ID identifying the PTC and indicating denormalization as the cause of deactivation to the GANC 5310 . Alternatively, the UE may indicate PTC timer expiration as the cause of deactivation.

Next, the GANC 5310 sends a RAB Release Request message to the SGSN 5315 to request the release of the associated RAB (in step 3). SGSN 5315 responds (in step 4) with a RAB Assignment Request message indicating release.

GANC 5310 responds to UE 5305 with a GA-PSR Deactivate PTC ACK message to acknowledge successful deactivation (in step 5). The UE 5305 transitions to the PTC-standby state. GANC 5310 sends a RAB Assignment Response message to notify SGSN 5315 that the RAB release procedure is complete (in step 6).

5. MS initiated PTC re-activation

54 shows that in some embodiments the UE is in a GA-PSR-connected state and a PMM-connected state, e.g., a PS signaling connection and an active PDP context exist between the UE and the CN, but the PTC is activated by the UE due to PTC timer expiration; A scenario is shown when initiating reactivation of a packet transport channel in a previously deactivated state. As shown, the following steps are performed. The UE is in a GA-PSR-connected state and a PTC-standby state. The UE is in a PMM-connected state (ie there is a PS signaling connection and an active PDP context).

If the UE 5405 has a PDU to transmit, the UE 5405 sends (in step 1) a service request message (with service type value "data") to the GANC 5410 via a GA-PSR UL direct transmission message. do. Next, GANC 5410 sends (in step 2) a service request message to SGSN 5415 using a RANAP direct transport message over the existing signaling connection.

The SGSN 5415 may optionally initiate the security mode control procedure described in the subclause security mode control above (in step 3). SGSN 5415 sends (in step 4) a service accept message to GANC 5410 . The GANC 5410 sends a message to the UE (in step 5).

Next, UE 5405, GANC 5410 and SGSN 5415 (in step 6) establish a GA-PSR Packet Transport Channel (PTC) as described in steps 3 to 7 of the sub-clause PTC Initial Activation above. set The UE transitions to the PTC-active state and starts the PTC timer. Finally, the UE 5405 transmits the uplink PDU (in step 7). Additional data transfers may also occur.

6. Disable Network Initiated PTC Active

55 depicts a scenario when the network initiates deactivation of a packet transport channel in some embodiments. The UE is in a GA-PSR-connected state and a PTC-active state. As shown, the following steps are performed.

Optionally, GANC 5510 may initiate a PTC deactivation procedure, eg, as a result of an error handling procedure. If so, GANC 5510 sends (in step 1) a RAB Release Request message to SGSN 5515.

SGSN 5515 sends a RAB assignment request to request release of the associated RAB (in step 2). A release request may include one or more RABs. Next, the GANC 5510 requests deactivation of the associated GA-PSR PTC by sending a GA-PSR deactivation PTC request message to the UE 5505 (in step 3).

The UE 5505 transitions to the PTC-standby state, stops the PTC timer, and sends an acknowledgment back to the GANC (in step 4). Steps 3 and 4 are repeated for each additional RAB/PTC that needs to be released. Finally, the GANC 5510 notifies the SGSN 5515 that the release was successful (at step 5).

7. Network Initiated PTC Re-Activation

56 illustrates in some embodiments while the UE is in a GA-PSR-connected state and a PMM-connected state, e.g., while a PS signaling connection and an active PDP context exist between the UE and the CN but the PTC has been previously deactivated; A scenario is shown when the network initiates reactivation of a packet transport channel. The UE is in a GA-PSR-connected state and a PTC-standby state. The UE is in a PMM-connected state (ie there is a PS signaling connection and an active PDP context). As shown, the following steps are performed.

When the SGSN 5615 has a PDU to send to the UE 5605, the SGSN 5615 may optionally initiate the security mode control procedure described in the subclause Security Mode Control above (in step 1). The UE 5605, GANC 5610 and SGSN 5615 establish (in Step 2) a GA-PSR Packet Transport Channel (PTC) as described in Steps 3 to 7 of the sub-clause PTC Initial Activation above. The UE transitions to the PTC-active state and starts the PTC timer. SGSN 5615 then sends a downlink PDU (in step 3). Additional data transfers may also occur.

8. Inherent PTC deactivation due to UE deregistration

As part of the GAN deregistration procedure, the GANC must release all resources allocated to the UE. GAN deregistration may be initiated either explicitly by the UE or unconditionally by the GANC upon detection of loss of the signaling connection (as described in the sub-clause deregistration above). 57 illustrates an inherent PTC activity release procedure in some embodiments. Initially, one or more GA-PSR PTCs associated with the UE are in a PTC-active state. As shown, the following steps are performed.

A GAN deregistration procedure is initiated by the UE 5705 or the GANC 5710 for the UE 5705 (in step 1 ). Optionally, (in step 2) the good resources associated with the CS domain are released.

GANC 5710 initiates the Iu release procedure to release the corresponding RAB (in step 3). SGSN 5715 responds (in step 4) with an Iu release command.

Upon receipt of the Iu Release command, the GANC 5710 locally deactivates all associated PTCs (in Step 6) and responds to the SGSN 5715 with an Iu Release Complete message (in Step 6).

R. Activate PDP Context

58 illustrates a successful UE-initiated PDP context activation procedure assuming the UE into a GA-PSR-idle state in some embodiments. As shown, the following steps are performed.

The GA-PSR connection establishment procedure (in step 1) is performed as described in the sub-clause GA-PSR connection establishment above. The GANC 5810 establishes an SCCP connection to the SGSN and sends (in step 2) a service request message (with the service type value "Signaling") to the SGSN 5815 using a RANAP initial UE message. Subsequent NAS messages between the UE and the core network will be sent between GANC and SGSN using RANAP direct transport messages.

The SGSN 5815 may optionally authenticate the UE (in step 3) using a standard UTRAN authentication procedure. The SGSN 5815 may optionally initiate the security mode control procedure described in the sub-clause security mode control above (in step 4). SGSN 5815 responds (in step 5) with a service accept message. GANC 5810 sends a message to UE 5805 (in step 5).

The UE 5805 then sends (in step 6) an Activate PDP Context Request message to the SGSN 5815 providing details regarding the PDP context. This message is included in the GA-PSR UL Direct Transmission message between the UE 5805 and the GANC 5810 . GANC 5810 sends (in step 6) an Activate PDP Context Request message to SGSN 5815.

Next, the UE 5805, GANC 5810, and SGSN 5815 (in step 7) establish a GA-PSR packet transport channel (PTC) as described in steps 3 to 7 of the section PTC Initial Activation above. set SGSN 5815 indicates to GANC that PDP context setup has been completed using the Activate PDP Context Accept message (in step 8). The GANC sends this message to the UE via a GA-PSR DL direct transport message. Finally, the UE 5805 and the CN 5815 exchange user data transmission via the established PTC (in step 9).

S. Enable Network Request PDP Context

59 illustrates a successful network-requested PDP context activation procedure assuming the UE into GA-PSR-idle state in some embodiments. Initially, the SGSN receives downlink user data to send to the UE, and the associated RAB is not established. The UE is in the PMM-idle state. As shown, the SGSN 5915 sends a RANAP paging message to the UE 5905 via the GANC 5910 to find the user (in step 1). The paging request indicates paging for PS domain signaling.

The GANC 5910 sends (in step 2) paging information to the UE 5905 via a GA-PSR Paging Request message. The GA-PSR connection establishment procedure (in step 3) is performed as described in the GA-PSR connection establishment subsection above. Alternatively, rather than using the GA-PSR connection establishment procedure, the UE 5905 may transmit a GA-PSR paging response message (in step 3) and then transition to the GA-PSR connection state.

The GANC 5910 establishes an SCCP connection to the SGSN and sends a service request message (with the service type value "paging response") to the SGSN 5915 using a RANAP initial UE message (in step 4). Subsequent NAS messages between the UE 5905 and the core network 5915 will be sent between the GANC 5910 and the SGSN 5915 using a RANAP direct transport message.

The SGSN 5915 may optionally authenticate the UE 5905 using a standard UTRAN authentication procedure (in step 5). The SGSN 59 15 may optionally initiate the security mode control procedure described in the sub-clause security mode control above (in step 6).

Next, SGSN 5915 sends (at step 7) a Request PDP Context Activate message to GANC 5910 . GANC 5910 sends this message (in step 7) to UE 5905 via a GA-PSR DL Direct Send message. The UE 5905 sends (in step 8) an Activate PDP Context Request message to the SGSN 5915 providing details regarding the PDP context. This message is included in the GA-PSR UL Direct Transmission message between the UE and the GANC. GANC 5910 sends (in step 8) an Activate PDP Context Request message to SGSN 5915.

UE 5905, GANC 5910, and SGSN 5915 establish (in step 9) a GA-PSR Packet Transport Channel (PTC) as described in steps 3 to 7 of the sub-clause PTC Initial Activation above. . The SGSN 5915 indicates to the GANC that the PDP context setup has been completed using the Activate PDP Context Accept message (in step 10). The GANC sends this message to the UE via a GA-PSR DL direct transport message. Finally, the UE 5905 and the SGSN 5915 exchange user data transmission via the established PTC (in step 11).

T. SRNS Relocation Between UTRAN and GAN

An SRNS relocation procedure is performed to move one or more PS sessions between Iu mode GAN and UTRAN. This procedure reassigns Iu-ps access points in GAN/UTRAN (in all cases) and SGSN (only in case of inter-SGSN relocation).

Support for the Iur interface between UTRAN and GAN is not described in this document. Therefore, only combined hard handover and SRNS relocation is applicable for GAN-UTRAN SRNS relocation. Therefore, only the "Related UE" relocation type is supported.

One. Relocating SRNS from UTRAN to GAN

a) <u>preparatory stage </u>

60 illustrates a UTRAN-GAN SRNS relocation preparation step in some embodiments. As shown, the following steps are performed.

The UE 6005 has one or more active PDP contexts with an active RAB in the UTRAN. Next, the UE 6005 detects the GAN 6015 , performs a registration procedure (in step 2), and enters the GA-RC-registration state with valid GAN cell identity information.

The measurement control message (in step 3) from the RNC 6010 to the UE 6005 contains the cell identity of this GAN. The UE starts including the GAN cell information in the measurement report sent to the RNC (in step 3a). In the message, the US sets the signal strength indicator of the GAN cell to the highest possible value.

Next, the RNC 6010 decides to initiate a combined hard handover and SRNS relocation procedure. This determination is made based on measurement reports and vendor/operator specific criteria. Upon deciding to initiate the relocation, the RNC 6010 sends (at step 4) a relocation request message to the SGSN.

The SGSN 6020 determines that the target cell is a GANC based on the content of the relocation request message. SGSN 6020 then sends a relocation request to GANC 6015 (in step 5).

Upon receipt of the Relocation Request message, the GANC 6015 (at step 6) sends the packet transport channel ( ) will be set up. The GANC 6015 will then send a relocation request acknowledgment to the SGSN (in step 6a).

b) <u>Execution step </u>

61 illustrates a step of executing UTRAN-GAN SRNS relocation in some embodiments. As shown, the following steps are performed.

Upon receipt of an affirmative acknowledgment from the GANC 6115 to serve the UE 6105 , the SGSN 6120 initiates the execution phase by sending (in step 1) a relocation command to the RNC 6110 . The RNC 6110 instructs the UE 6105 to initiate a physical layer switch to move to the GAN by sending a physical channel reconfiguration message (in step 2a).

If the QoS attribute of the active RAB requires lossless sequential SDU delivery (lossless PDCP), the RNC 6110 sends the GTP PDU to the GANC (in step 2b) while still sending the GTP PDU to the UE 6105 in the downlink direction. 6115) to start sending. This transmission is routed through the Iu PS interface. The GANC may buffer these transmitted GTP PDUs, transmit them downlink, and discard them according to the QoS profile, network conditions, and whether lossless relocation is supported. Particular implementations are vendor and/or operator specific. In addition, the GANC delays the start of the downlink transmission until the next step 5 to synchronize the GTP-U sequence number.

The RNC sends a Forward SRNS context message to the GAN via the SGSN (in steps 2c and 3a). In this message, the next-expected sequence numbers of the uplink and downlink GTP-U packets are indicated to the GANC by the previous SRNC. If QoS attributes require lossless relocation and the GANC supports lossless relocation, these sequence numbers are used to ensure sequential delivery of GTP PDUs.

Immediately after receiving the physical channel reconfiguration message, the UE 6105 sends a GA-PSR-Handover-Complete message to the GANC 6115 (in step 3b). Upon receipt of this message and the forward SRNS context message sent from SGSN 6120 (in step 3a), GANC 6115 becomes the serving RNC.

Upon receiving the GA-PSR-Handover-Complete message from the UE, the GANC 6115 sends (at step 4) a Relocation Detect message to the SGSN 6120 . If the UE supports lossless relocation and one or more RABs QoS attributes require the relocation, the UE initiates a GTP-U sequence number exchange procedure with the GANC on the newly established PTC (in step 5). When the GANC 6115 supports lossless relocation and one or more RABs QoS attributes require the relocation, it initiates a GTP-U sequence number exchange procedure if the GTP-U sequence number exchange procedure has not already been initiated by the UE.

Upon completion of the GTP-U sequence number exchange procedure, the GANC 6115 sends (at step 6) a Relocation Complete message to the SGSN. If the GTP-U sequence number exchange is skipped (due to lack of support at the UE and/or as GAN or QoS attributes do not require that exchange), a Relocation Complete message is sent immediately after the Relocation Detect message. Active RAB and PDP contexts are now moved between UE and GANC and SGSN. The SGSN 6120 then releases the Iu PS connection with the previous RNC 6110 (in step 7). If the routing area of the GANC cell (indicated by the GANC to the UE) is different from the routing area under the previous RNC, the UE 6105 performs a routing area update procedure (in step 8).

2. SRNS relocation from GAN to UTRAN

a) <u>preparatory stage </u>

62 illustrates a GAN-UTRAN SRNS relocation preparation step in some embodiments. As shown, the following steps are performed.

The UE 6205 is (in step 1) in an active packet flow exchange state with the PTC and active PDP context(s) in the GAN. The GANC 6215 may send a GA-PSR uplink quality indication message if there is a problem with the uplink quality for the ongoing session (in step 2). The uplink quality indication is information sent by the GANC 6215 to the UE 6205 indicating the crossing of the uplink quality threshold in the uplink direction. Whenever the UE receives an indication of poor quality, it must initiate the relocation procedure as described in the next step. Alternatively, the UE may use its local measurement to determine whether to initiate a handover procedure.

Next, the UE decides to initiate the SRNS relocation from the GAN to the UTRAN by sending a GA-PSR-Handover-Information message to the GANC 6215 (in step 3). Specific criteria for this decision include when the UE is out of GAN coverage (eg, based on degraded WLAN signal quality).

The GANC 6215 selects a target RNC based on the content of the GA-PSR-Handover-Information message (eg, the RNC serves the cell identified as having the best signal quality by the UE). The GANC 6215 sends a relocation request message containing the selected RNC information to the SGSN 6220 (in step 4).

SGSN 6220 sends (at step 5) a relocation request to target RNC 6210 . The RNC 6210 performs the necessary allocation of radio and Iu transmission resources (in step 6) and provides a relocation request acknowledgment message to the SGSN (in step 7). This message contains the channelization information needed by the UE to access the UTRAN.

<u>b) Execution step </u>

63 illustrates a GAN-UTRAN SRNS relocation execution step in some embodiments. As shown, the following steps are performed.

SGSN 6320 begins the execution phase by providing a relocate command to GANC 6315 (in step 1). The message contains channel access information to the target UTRAN cell. GANC 6315 sends (in step 2a) a GA-PSR-Handover-Command to UE 6305 . This message contains information from the relocation command received earlier in step 1. GANC stops sending downlink GTP PDUs at this point. If the GANC supports lossless SRNS relocation and the existing RAB's QoS requires the relocation, then the GANC may initiate transmission of the PDU to the target RNC 6310 via the SGSN 6320 (in step 2c).

The GANC 6315 also sends the forward SRNS context to the target RNC via the SGSN (in steps 2b and 3). As shown, the GANC sends a forward SRNS context message to the SGSN (in step 2b), and the SGSN relays the forward SRNS context to the target RNC (in step 3).

Upon receiving the GA-PSR-Handover-Command, the UE immediately stops transmitting uplink GTP PDUs. The UE immediately initiates the UTRAN access using the channel access parameter indicated in the message. The UE's access attempt is detected by the Node B and the RNC 6310 and reported to the SGSN 6320 via a relocation detection message (in step 4).

The UE completes the lower layer setup and configuration, and sends an RRC physical channel reconfiguration complete message to the target RNC 6310 (in step 5a). This triggers the RNC 6310 to send a relocation complete message to the SGSN 6320 (in step 5b). In this step, the target RNC assumes the role of the SRNC for the UE.

Packet data flow is now activated (in step 6) via UTRAN. Next, the SGSN releases the Iu_PS connection by sending (in step 7a) an Iu release command message to the GANC to which the GANC responds with an Iu release complete message (in step 7b). If the routing area of the cell under the target RNC is different from the routing area of the cell under the previous GANC cell, the UE 6305 performs a routing area update procedure (in step 8).

U. Short Message Service

GAN provides support for circuit switched and packet switched SMS services. A GAN-attached UE will be able to send and receive SMS messages via the GAN.

One. CS-based SMS

CS-based SMS support in GAN is based on the same mechanism used for CS mobility management and call control. On the UE side, the SMS layer (including supporting CM sublayer functions) uses the services of the MM layer to send SMS messages through the standard circuit switched UMTS implementation.

The SM-CP protocol effectively tunnels between the UE and the CN using the GA-CSR uplink direct transport message and the GA-CSR downlink direct transport message between the UE and the GANC, where the GANC performs transmission over the Iu-cs interface. For this purpose, SM-CP message is relayed through RANAP message. As in the case of mobility management and call control procedures, secure IPSec tunnels and TCP sessions are used to provide secure and reliable SMS delivery over IP networks.

2. PS-based SMS

PS-based SMS message transmission is based on the same mechanism as PS mobility management and session management signaling messages transmission. On the UE side, the SMS layer (including supporting CM sublayer functions) uses the services of the GA-PSR layer to send SMS messages through the standard packet switched UMTS implementation. As in the case of mobility management and session management signaling, secure IPSec tunnels and TCP sessions are used to provide secure and reliable PS-based SMS delivery over IP networks.

VI. configuration information

A. GAN UARFCN and main scrambling code for handover to GAN

In some embodiments, the selection of a UMTS Absolute Radio Frequency Channel Number (UARFCN) uses the following guidelines:

One. The UARFCN shall be assigned from the operator's assigned UARFCN value.

2. The UARFCN may be required to be the same unique number throughout the entire operator network to minimize RNC configuration effort.

3. The primary scrambling code (possible values from 0 to 511) shall not be assigned from the operator's use value, ie the code used by the macro cell.

4. The primary scrambling code may be required to be the same unique number throughout the entire operator network to minimize RNC configuration effort.

Several options will be described later in more detail.

One. Option 1

Some embodiments allocate the GAN UARFCN from the DCS band being used for GSM. Accordingly, the DL UARFCN is in the range of 1162 to 1513. In this technique, there is no limit to the selection of a specific primary scrambling code (PSC) for the GAN - any of the 512 values can be used in the selected particular UARFCN.

If the initial UMTS deployment is within the 1900 MHz band, a similar approach can be used - ie the use of UARFCN from the 850 MHz band. This gives a GAN UARFCN range of 4357 to 4458. Alternatively, the UARFCN from the PCS sub-band carrying the non-UMTS technique may also be specified. Also, there is no restriction on the selection of PSCs in a given GAN UARFCN.

2. Option 2

The strategy here is to use the TDD unpaired spectrum and its UARFCN range for GAN purposes. As part of a UMTS auction, many operators acquire TDD single-sided 5 MHz spectrum in addition to one or more FDD pairs. The TDD spectrum remains unused and is likely to remain that way for the foreseeable future.

Even if a given operator does not own the TDD spectrum in a given market, unused TDD spectrum from any operator in the market can be used, since it is a completely harmless, interference-free procedure for the UE to do cell discovery. Even if a given TDD cross-section 5MHz is used in the UTRAN-TDD mode, there is a possibility that the FDD-only handset will fail initial synchronization at the PHY layer. Many handsets planned for the near future are FDD only.

If the handset semantically accepts these values, these UARFCNs are indeed defined in 3GPP, and the infrastructure vendor allows the provision of these UARFCN ranges in the system, this approach is possible. The UARFCN ranges, in this case, are 9504 to 9596 and 10054 to 10121. As in the case of option 1, there are no restrictions on the PSC selection of the GAN.

3. Option 3

This plan requires the use of UARFCN in the idle FDD spectrum for GAN purposes. The "idle" spectrum may or may not belong to a particular operator. In many parts of Europe and Asia, the FDD spectrum is still unused, as bidders at auctions go out of business or owners choose not to deploy services due to the cost and unavailability of the equipment.

VII. Identifier of GAN

A. Identifier of UE and Generic IP Access Network

The key UE and generic IP access network addressing parameters are the IMSI associated with the (U)SIM in the terminal, the public IP address of the UE, and the generic IP access network point (AP-ID) of the attachment address. The IMSI associated with the (U)SIM is provided by the UE to the GANC during the registration procedure. GANC maintains a record for each registered UE. For example, the IMSI is used by the GANC to index the appropriate UE records when the GANC receives a RANAP paging message.

The public IP address of the UE is the source IP present in the outermost IP header of the packet received from the UE by the GANC-SEGW. When available, this identifier may be used by GANC to support assisted location services and fraud detection, or may be used by service providers to advertise IP flows to managed IP networks that require special QoS treatment.

The generic IP access network point (AP-ID) of the attach address is provided to the GANC by the UE upon registration. The AP-ID may be used by the GANC to support location services or by the service provider to restrict GAN access to authorized APs.

B. Service Area Identifier for GAN

One. GAN service area for location services and billing

A service area identifier (SAI) in UMTS is an emergency service; Operator; It can be used to perform location-based routing of calls for services such as guidance and toll-free numbers. The SAI may also be used by the core network to identify where a call is initiated/terminated for charging purposes. The GANC provides the SAI representing the Iu-mode GAN service area to the core network.

a) <u>Based on UTRAN/GERAN location </u><u>GAN</u><u></u><u>SAI</u><u> Assignment</u>

In the Iu-mode GAN architecture, the UE has a direct IP-based connection to the GANC. The GAN coverage area may cover the UTRAN/GERAN coverage area. Logical mapping of GAN cells to SAI can be done at various resolutions. For example, but not limited to: (1) GAN SAI for each UTRAN/GERAN cell, (2) GAN SAI for each UTRAN/GERAN routing area; or (3) GAN SAI for each UTRAN/GERAN location area. A single GANC may represent more than one SAI in more than one location area (LAI).

VIII. Alternative embodiments

In some embodiments, instead of using separate CSR and PSR protocols, a single protocol, Generic Access Radio Resource Control (GA-RRC) is used, as described in the previous section. The following sections describe the architecture and messaging features of this protocol layer. Only features different from the previous embodiment will be described.

A. Control and user plane architecture

The Iu interface standard includes support for ATM and IP-based signaling and user data transport mechanisms.

One. circuit switched (CS) domain

a) <u>CS domain-control plane</u>

64 illustrates a GAN architecture supporting the CS domain control plane in some embodiments. 64 shows different protocol layers for UE 6405 , generic IP network 6410 , GANC 6415 , and MSC 6420 . 64 also shows two interfaces Up 6425 and Iu-cs 6430. The main features of the GAN CS domain control plane architecture are as follows. The underlying access layers 6435 and transport IP layer 6440 provide a general connection between the UE 6405 and the GANC 6415 . IPSec layer 6445 provides encryption and data integrity between UE 6405 and GANC 6415 . The remote IP layer 6450 is the 'inner' IP layer for the IPSec tunnel mode and is used by the UE 6405 to be processed by the GANC 6415 . The remote IP layer 6450 is configured during IPSec connection establishment.

In some embodiments, a single TCP connection 6455 is used to provide reliable transport for GA-RC 6460 and GA-RRC 6465 signaling between UE 6405 and GANC 6415 . TCP connection 6455 is managed by GA-RC 6460 and transmitted using remote IP layer 6450 .

The Generic Access Resource Control (GA-RC) protocol 6460 manages Up sessions, including GAN discovery and registration procedures. The Generic Access Radio Resource Control (GA-RRC) protocol 6465 performs the equivalent of the UMTS-RRC protocol using the underlying connectivity managed by the GA-RC sublayer 6460 . Note that GA-RRC 6465 includes CS service and PS service-related signaling messages. The GANC 6415 terminates the GA-RRC protocol 6465 and interworks with the RANAP protocol 6470 through the Iu-cs 6430 interface. NAS protocols such as MM 6475 are transparently carried between UE 6405 and MSC 6420 . In some embodiments, the Iu-cs signaling transport layer 6495 conforms to 3GPP TS 25.412.

b) <u>CS domain-user plane</u>

65 illustrates a GAN protocol architecture supporting the CS domain user plane in some embodiments. 65 shows different protocol layers for UE 6505 , generic IP network 6510 , GANC 6515 , and MSC 6520 . 65 also shows two interfaces Up 6525 and Iu-cs 6530 . The main features of the GAN CS domain user plane architecture are as follows. The underlying access layer 6535 and transport IP layer 6540 provide a general connection between the UE 6505 and the GANC 6515 .

IPSec layer 6545 provides encryption and data integrity. CS domain user plane data is transmitted between UE 6505 and MSC 6520 using an Iu user plane (Iu UP) protocol 6550 running over RTP/UDP 6555, 6560. Each Iu UP protocol 6550 instance may operate in either transparent or supported mode as described in "UTRAN Iu Interface User Plane Protocol" of the 3GPP TS 25.415 standard. Mode selection is indicated to the GANC by the MSC using RANAP and to the UE by the GANC using GA-RRC. As specified in "AMR voice codec; general technology" of 3GPP TS 26.071 standard, support for AMR FR codec is mandatory when operating in GAN mode, and support for other codecs is optional. In some embodiments, the Iu-cs data transport layer 6595 conforms to 3GPP TS 25.414.

Some embodiments using the GA-RRC protocol implement a protocol stack for GANC that is different from the protocol stack shown for GANC 6515 . In these embodiments, the GANC protocol stack is similar to the GANC 1115 protocol stack illustrated in FIG. 11 . In these embodiments, the GANC has additional protocol layers above the IPSec layer 6545: Remote IP, UDP, and RTP. GANC also has an additional Iu UP protocol layer above the data transport layer 6595 . Similar to the GANC 1115 shown in FIG. 11 , the GANC interoperates with the CS domain user plane between RTP/UDP and Iu user plane protocols in these embodiments.

2. Packet-Switched (PS) Domains

a) PS domain-control plane

66 illustrates a GAN architecture supporting the PS domain control plane in some embodiments. 66 shows other protocol layers for UE 6605 , Generic IP Network 6610 , GANC 6615 , and SGSN 6620 . 66 also shows two interfaces Up 6625 and Iu-ps 6630. The main features of the GAN PS domain control plane architecture are: The function of the GA-RRC 6635 and the underlying layer is as described in subclause VIII.AI a: "CS domain-control plane" above. The GA-RRC protocol 6635 performs an equivalent function to the UTRAN RRC protocol using an underlying Up session managed by the GA-RC 6640 . GA-RRC 6635 includes CS service and PS service-related signaling messages.

The GANC 6615 terminates the GA-RRC protocol 6635 and interworks with the RANAP protocol 6645 through the Iu-ps interface 6630 . NAS protocols such as GMM, SM and SMS 6650 are carried transparently between UE 6605 and SGSN 6620 . In some embodiments, the Iu-ps signaling transport layer 6695 conforms to 3GPP TS 25.412.

b) <u>PS domain-user plane</u>

67 illustrates a GAN architecture for the PS domain user plane in some embodiments. 67 shows different protocol layers of UE 6705 , generic IP network 6710 , GANC 6715 , and SGSN 6720 . 67 also shows two interfaces Up 6725 and Iu-ps 6730. The main features of the GAN PS domain user plane architecture are as follows. The underlying access layer 6735 and transport IP 6740 layers provide general connectivity between the UE 6705 and the GANC 6715 . IPSec layer 6745 provides encryption and data integrity. The GTP-U 6750 protocol operates between the UE 6705 and the SGSN 6720 to transfer the upper layer payload (i.e., PS domain user plane data 6755) to the Up interface 6725 and the Iu-ps interface ( 6730). User data is carried transparently between the UE 6705 and the core network. In some embodiments, the Iu-ps data transport lower layer 6795 conforms to 3GPP TS 25.414.

Some embodiments using the GA-RRC protocol implement a protocol stack for GANC that is different from the protocol stack shown for GANC 6715 . In these embodiments, the GANC protocol stack is similar to the GANC 1815 protocol stack illustrated in FIG. 18 . In these embodiments, the GANC has additional protocol layers above the IPSec layer 6745: Remote IP, UDP, and GTP-U. In these embodiments, the GTP-U in the UE and the GTP-U layer above the UDP layer in the GANC are part of the GA-RRC protocol. GANC also has additional IP, UDP, and GTP-U layers above the data transport lower layer 6795 .

3. Generic Access Resource Control (GA-RC)

The GA-RC protocol provides a resource management layer with the following functions: Support for discovery and registration using GANC, update registration using GANC, application level keepalive using GANC, and identification of APs used for GAN access.

b) <u>State of the GA-RC sub-layer</u>

68 illustrates a GA-RC sublayer within a UE in some embodiments. As shown, the GA-RC sub-layer within the UE may be in one of two states: GA-RC-de-registration 6805 or GA-RC-registration 6810 . In the GA-RC-deregistration state 6805, the UE may be in the GAN coverage area, but the UE is not successfully registered with the GANC. The UE may initiate the GAN registration procedure when in the GA-RC-deregistration state 6805 . The UE reverts to the GA-RC-deregistration state 6805 upon loss of TCP or IPSec connection or upon execution of a GAN deregistration procedure.

In the GA-RC-registration state 6810 , the UE is registered with the serving GANC. The UE has a TCP connection and IPSec tunnel established to the serving GANC that the UE uses to exchange GA-RC or GA-RRC signaling messages with the GANC. The UE performs GANC and application level keep alive while maintaining the GA-RC-register state 6805 .

In the GA-RC-registration state, the UE may be in UTRAN/GERAN mode 6815 or GAN mode 6820 . UE (1) may be camped on GERAN or UTRAN and may be idle, (2) may be active in GERAN or UTRAN (eg GSM RR or UTRAN RRC connection may be established), (3) GAN mode, or (4) may have recently "roved" from GAN mode (eg, due to a handover from GAN).

4. Generic Access Radio Resource Control (GA-RRC)

The GA-RRC protocol provides an alternative resource management layer to UTRAN-RRC and provides the following functions: (1) setup of transport channels for CS and PS traffic between UE and GANC, (2) flow control of PS traffic, (3) CS and PS handover support between UTRAN/GERAN and GAN, (4) UE and core network Direct transfer of NAS messages between, and (5) other functions such as paging and security configuration.

b) the status of the GA-RRC sub-layer

The GA-RRC sub-layer within the UE may be two states, GA-RRC-idle 6825 or GA-RRC-connected 6830 as shown in FIG. 68 . The UE enters the GA-RRC-idle 6825 state when transitioning the serving RR entity to GA-RRC, and the SAP between NAS and GA-RRC is activated. This transition can only occur when the GA-RC is in the GA-RC-registered state. The UE moves from the GA-RRC-idle state 6825 to the GA-RRC-connected state 6830 when the GA-RRC connection is established, and returns to the GA-RRC-idle state when the GA-RRC connection is released. . Upon release of the GA-RRC connection, an indication indicating that there is no dedicated resource is transmitted to the upper layer. The UE also enters the GA-RRC-connected state from the GA-RC-REGISTERED state of the GERAN/UTRAN mode when handover to the GAN is being performed. In the same way, the UE enters the GA-RC-registration state of the GERAN/UTRAN mode from the GA-RRC-connected state when the handover from the GAN is successfully executed.

B. High-Level Procedures

One. GA-RRC connection processing

A GA-RRC connection is a logical connection between the UE and the GANC for the CS or PS domain. This connection is established when upper layers in the UE request the GA-RRC to establish a signaling connection and the UE is in idle mode (no RRC connection). When a successful response is received from the network, the GA-RRC responds to the upper layer as having entered the RRC connected mode. At this time, there is a possibility that upper layers may request transmission of a NAS message to the network.

a) <u>GA-RRC connection setting</u>

i) UE-initiated GA-RRC connection establishment

69 illustrates successful (and unsuccessful) establishment of a GA-RRC connection when initiated by a UE in one embodiment. The UE 6905 initiates the GA-RRC connection establishment by sending a GA-RRC request message to the GANC 6910 (in step 1). This message contains an establishment cause indicating the reason for establishing a GA-RRC connection. The message also includes a domain indicator (CS or PS). The GANC 6910 informs the UE 6905 of a successful response by sending a GA-RRC request accept (in step 2), and the UE 6905 enters the GA-RRC connected mode. Alternatively, the GANC 6910 may provide a GA-RRC Request Reject message indicating the reason for the rejection (in step 3).

ii) Network-initiated GA-RRC connection establishment

70 illustrates successful establishment of a GA-RRC connection when initiated by the network in some embodiments. The CN 7015 sends (in step 1) a RANAP paging message to the identified GANC 7010 via the last location update received and includes the TMSI if available. The IMSI of the UE being paged is always included in the request, which is the domain indicator (CS or PS). Paging causes may be included.

The GANC 7010 then uses the IMSI provided by the CN 7015 to identify the UE registration context. The GANC 7010 then pages the UE 7005 using a GA-RRC paging request message (in step 2). The UE 7005 responds (in step 3) with a GA-RRC Initial Direct Send message containing the appropriate NAS message and cause for the domain indicator (CS or PS). Alternatively, the UE 7005 responds (in step 3) with a GA-RRC Paging Response message including a NAS message, a domain indicator (ie, CS or PS) and a cause. The UE 7005 enters the GA-RRC connected mode. GANC 7010 establishes an SCCP connection to CN 70015 . The GANC 7010 then sends a NAS message to the CN 7015 using the RANAP initial UE message (in step 4). Subsequent NAS messages between the UE and the core network will be sent between GANC and CN using RANAP direct transport messages.

b) <u>Disconnect GA-RRC</u>

71 illustrates the release of a logical GA-RRC connection between a UE and a GANC in some embodiments. The CN 7115 instructs the GANC 7110 to release the user plane connection assigned to the UE 7115 using the RANAP Iu Release Command message (in step 1). GANC 7110 confirms resource release to CN 7115 using Iu release complete message 7125 (in step 2).

Next, the GANC 7110 instructs the UE 7105 to release the resource using a GA-RRC Connection Release message (in step 3). The UE 7105 confirms the resource release to the GANC 7110 using the GA-RRC connection release complete message (in step 4), and the GA-RRC state at the UE changes to idle.

3. Security Mode Control

72 illustrates a message flow for secure mode control in some embodiments. CN 7215 sends (in step 1) a RANAP secure mode command message to GANC 7210 . This message contains an integrity key (IK) and an allowed algorithm, and optionally an encryption key (CK) and an allowed algorithm. GANC 7210 sends (in step 2) a GA-RRC Secure Mode Command message to UE 7205 . This message indicates the integrity protection and encryption settings (ie, applicable after relocation to UTRAN), and a random number. The UE 7205 stores the information for possible future use after handover to the UTRAN.

Next, the UE 7205 calculates a MAC based on the random number calculated by the UE, the UE IMSI and the integrity key. The UE 7205 then sends a GA-RRC Security Mode Complete message to inform (in step 3) its selected algorithm and computed MAC. Next, the GANC 7210 verifies the MAC using the random number provided by the CN 7215 in step 1, the UE IMSI and the integrity key. If the GANC verifies that the MAC is correct, it sends a secure mode complete message to the CN 7215 (in step 4). The MAC proves that the identity authenticated to the GANC is the same as the identity authenticated to the core network.

4. GA-RRC NAS signaling procedure

After GA-RRC connection establishment, NAS signaling may be sent from CN to UE and from UE to CN.

a) <u>CN-UE </u><u>NAS</u><u></u><u>signaling</u>

73 illustrates core network-UE NAS signaling of some embodiments. For CN-UE NAS signaling, the core network 7315 sends the NAS PDU to the GANC via a RANAP direct transmission message (in step 1). The GANC 7310 wraps the NAS PDU (in step 2) into a GA-RRC DL direct transport message and sends the message to the UE 7305 over the existing TCP connection.

b) <u>UE</u><u>-</u><u>CN</u><u></u><u>NAS</u><u></u><u>signaling</u>

74 illustrates UE-core network NAS signaling of some embodiments. The UE 7405 GA-RRC layer receives a request from the NAS layer to send an uplink NAS PDU. Since the MM connection (and thus the RR signaling connection) already exists, the UE GA-RRC wraps the NAS PDU into a GA-RRC UL direct transport message (in step 1) and sends the message to the GANC 7410 . GANC 7410 relays the received message to core network 7415 via RANAP direct send message 7420 (in step 2).

5. Mobile terminal outgoing CS call

a) <u>UE terminates the Iu UP packet</u>

75 illustrates a mobile terminal originating CS call procedure in some embodiments. In the description of the above procedure, it is assumed that the UE 7505 is in GAN mode. That is, it is assumed that it is successfully registered with the GANC 7510 and that the GA-RRC is the serving RR entity in the UE 7505 . It is also assumed that no GA-RRC connection exists between the UE 7505 and the GANC 7510 (ie, the GA-RRC-idle state). The GA-RRC connection establishment procedure is performed (in step 1) as described above in subclause VIII.Blai: UE-initiated GA-RRC connection establishment. Upon request from the upper layer, the UE 7505 sends a CM service request (in step 2) to the GANC 7510 via a GA-RRC Initial Direct Send message.

GANC 7510 sends an SCCP connection to CN 7515 and (in step 3) sends a CM service request to CN 7515 using a RANAP initial UE message. Subsequent NAS messages between the UE 7505 and the core network 7515 will be transmitted between the GANC 7510 and the CN 7515 using a RANAP direct transport message.

The CN 7515 may optionally authenticate the UE 7505 using a standard UTRAN authentication procedure (in step 4). CN 7515 may optionally initiate a security mode control procedure as described in subclause VIII.B.3: "Security Mode Control" above (in step 5).

The UE 7505 sends (in step 6) a setup message providing the CN 7515 with details about the call, its bearer capabilities and supported codecs. This message is included in the GA-RRC UL Direct Transmission message between the UE 7505 and the GANC 7510 . GANC 7510 sends a setup message to CN 7515 (in step 6).

The CN 7515 has received the call setup (in step 7) and indicates to the GANC 7510 that it will not accept additional call-setup information using a call progress message. The GANC 7510 sends this message (in step 7) to the UE 7505 via a GA-RRC DL Direct Send message.

The CN 7515 requests (in step 8) the GANC 7510 to allocate call resources using a RANAP RAB allocation request message. CN 7515 contains the RAB-ID for user data, CN transport layer address (IP address) and CN Iu transport association (UDP port number). GANC 7510 (in step 9) (1) radio access bearer (RAB) parameters; For example, RAB-ID, UDP port and IP address for uplink RTP stream (2) received via RAB assignment request message such as Iu UP parameter (eg, Iu UP mode if support mode is used for AMR voice call) Sends a GA-RRC activation channel message including the bearer path setup information to the UE (7505).

Since the Iu UP support mode is indicated, the UE 7505 sends (in step 10) an Iu UP initialization packet to the IP address and UDP port indicated in the GA-RRC activation channel message. This message is routed to the core network 7515 (eg, R4 media gateway). The core network 7515 responds (in step 11) with an Iu UP initialization ACK packet. The core network 7515 sends the message to the source IP address and UDP port number of the received initialization packet.

The UE 7505 sends (at step 12) a GA-RRC activation channel ACK to the GANC 7510 . The GANC informs the CN 7515 that the RAB has been established by sending (in step 13) a RANAP RAB Assignment Response message. The GANC 7510 informs the UE 7505 of the completion of RAB setup (in step 14) with a GA-RRC Activate Channel Complete message.

An end-to-end audio path now exists between the UE 7505 and the CN 7515 . The UE 7505 can now connect the user to the audio path. The CN 7515 informs the UE 7505 that the callee is ringing with a warning message. The message is sent (at step 15) to the GANC 7510, which sends (at step 15) the message to the UE 7505 via a GA-RRC DL direct send message.

The UE 7505 issues a ring back to the caller if it has not connected an audio path to the user. Otherwise, a network-generated ring back will be provided to the caller. The CN 7515 informs that the responder has responded through a connection message. The message is sent (at step 16) to the GANC 7510, and the GANC sends (at step 16) the message to the UE 7505 via a GA-RRC DL direct send message 7595. The UE 7505 connects the user to the audio path. The UE 7505 stops if it is generating a ring back and connects the user to the audio path.

The UE 7505 sends (at step 17) a Connect Ack message in response, and the two means are connected for the voice call. This message is included in the GA-RRC UL Direct Transmission message between the UE 7505 and the GANC 7510 . GANC sends (at step 17) a Connect Ack message to CN 7515. Bidirectional voice traffic flows (in step 18) between UE 7505 and CN 7515 via GANC 7510.

b) <u>GANC ends the Iu UP packet</u>

Some embodiments use an alternative procedure for mobile station originating CS calls using the RRC protocol. 76 illustrates the step performed during a mobile station originating CS call in these embodiments. The procedure assumes that the UE is in GAN mode. That is, it is assumed that it is successfully registered with the GANC and that the GA-RRC is the serving RR entity for the CS service in the UE. It is also assumed that there is no GA-RRC signaling connection between the UE and the GANC (ie, the GA-RRC-idle state). As shown, the GA-RRC connection establishment procedure (in step 1) is performed. In some embodiments, this procedure is performed. Next, the UE 7605 sends a CM service request message to the GANC 7610 via a GA-RRC UL direct transmission message.

Next, the GANC 7610 establishes an SCCP connection to the core network CN 7615 (in step 3) and sends the NAS PDU (ie, a CM service request message) to the core network CN 7615 using the RANAP initial UE message. send to The message contains a domain indicator set to the value 'CS domain'. Subsequent NAS messages between the UE and the core network CN will be transmitted between the GANC and the core network CN using RANAP direct transport messages.

The core network CN 7615 may optionally authenticate the UE (in step 4) using a standard UTRAN authentication procedure. The core network CN 7615 may optionally initiate a secure mode control procedure (in step 5). The UE 7605 sends (in step 6) a setup message providing the core network CN with details about the call, and its bearer capabilities and supported codecs. This message is included in the GA-RRC UL Direct Transmission message between the UE and the GANC. The GANC sends a setup message to the core network CN.

Next, the core network CN 7615 indicates to the GANC that it has received the call setup (in step 7) and will not accept additional call-setup information using a call progress message. The GANC sends this message (in step 7) to the UE via a GA-RRC DL direct transport message.

The core network CN 7615 requests the GANC 7610 to allocate call resources using the RANAP RAB allocation request message (in step 8). Core network CN 7615 includes, among other parameters, RAB-ID, CN transport layer address for user data and CN Iu transport association, and an indication indicating that Iu UP support mode is required.

Next, GANC 7610 (in step 9) (1) channel mode, (2) multi-rate codec configuration, (3) UDP port and IP address for uplink RTP stream, (4) voice sample size A GA-RRC activation channel message including bearer path setup information is sent to the UE 7605 .

The UE 7605 then sends (at step 10) a GA-RRC activation channel ACK indicating the UDP port for the downlink RTP stream to the GANC 7610 . Since the Iu UP support mode is indicated by the core network CN in step 8, the GANC 7610 sends an Iu UP initialization packet to the core network CN (in step 11).

In response, the core network CN responds (in step 12) with an Iu UP initialization ACK packet. GANC 7610 notifies UE 7605 of completion of RAB setup (in step 13) with a GA-RRC Activate Channel Complete message. Alternatively, steps 11 and 12 may occur prior to step 9 .

The GANC 7610 informs the core network CN 7615 that the RAB has been established by sending a RANAP RAB assignment response message (in step 14). The core network CN 7615 informs the UE 3505 that the callee is ringing with a warning message. The message is sent (at step 15) to the GANC 7610, which sends (at step 15) the message to the UE 7605 via a GA-RRC DL direct send message. The UE issues a ring back to the caller when it has not connected the audio path to the user. Otherwise, a network-generated ring back will be provided to the caller.

Next, the core network CN 7615 informs through a connection message that the protectee has responded. The message is sent to the GANC 7610 (in step 16) and the GANC sends the message to the UE (in step 16) via a GA-RRC DL direct send message. The UE connects the user to the audio path. If the UE is generating a ring back, it stops and connects the user to the audio path.

The UE 7605 then sends a Connect Ack message in response (in step 17), and the two means are connected for the voice call. This message is included in the GA-RRC UL Direct Transmission message between the UE and the GANC. GANC sends a connection Ack message to the core network CN. At this time, the two-way voice traffic flows through the GANC 7610 between the UE 7605 and the core network CN 7615 (in step 18).

6. Mobile station incoming CS call

77 illustrates a mobile station terminating CS call procedure in some embodiments. The description of the procedure assumes that the UE 7705 is in GAN mode. That is, it is assumed that it is successfully registered with the GANC 7710 and that the GA-RRC is the serving RR entity within the UE 7705 . Also, it is assumed that there is no GA-RRC connection between the UE 7705 and the GANC 7710 (ie, the GA-RRC-idle state).

The mobile station's incoming call arrives at CN (7715). The CN 7715 sends (in step 1) a RANAP paging message to the identified GANC 7710 via the last location update received and includes the TMSI if available. The IMSI of the mobile station being paged is always included in the request. GANC 7710 uses the IMSI provided by CN 7715 to identify the UE registration context. The GANC then pages the UE 7705 using a GA-RRC paging request message (in step 2). The message contains the TMSI when available in a request from CN 7715 . Otherwise, the message contains only the IMSI of the UE 7705 .

The UE 7705 responds (in step 3) with a GA-RRC Initial Direct Send message including a paging response. The UE 7705 enters the GA-RRC connected mode. GANC 7710 establishes an SCCP connection to CN 7715 . The GANC 7710 then sends a paging response to the CN 7715 using a RANAP initial UE message (in step 4). Subsequent NAS messages between the UE 7705 and the core network 7715 will be sent between the GANC 7710 and the CN 7715 using a RANAP direct transport message.

The CN 7715 may optionally authenticate the UE 7705 using a standard UTRAN authentication procedure (in step 5). The CN 7715 may optionally update the security configuration within the UE 7705 via the GANC 7710 as described in subclause VIII.B.3: "Security Mode Control" above (in step 6). CN 7715 initiates call setup using a setup message sent to UE 7705 via GANC 7710 (in step 7). The GANC sends this message (in step 7) to the UE 7705 via a GA-RRC DL direct transport message.

The UE 7705 (in step 8) checks its compatibility with the bearer service requested for setup and, if necessary, modifies the bearer service, and then responds with a call acknowledgment message using a GA-RRC UL direct transmission message. If the setup includes a signal information element, the UE 7705 alerts the user using the indicated signal, otherwise the UE 7705 warns the user after successful configuration of the user plane. GANC 7710 sends (at step 8) a call acknowledgment message to CN 7715. The CN 7715 initiates the allocation procedure with the GANC 7710 (in step 9), triggering the setup of an RTP stream (voice bearer channel) between the GANC 7710 and the UE 7705 .

The UE 7705 informs the user that it is warning the user through a warning message included in the GA-RRC UL direct transmission message (in step 10). GANC 7710 sends a warning message to CN 7715 (at step 10). CN 7715 sends a corresponding warning message to the caller. The UE 7705 informs (in step 11) that the protector has responded via a connect message included in the GA-RRC UL direct transmission message. GANC 7710 sends (at step 11) a connect message to CN 7715. CN 7715 sends a corresponding connect message to the caller and connects the audio. The UE 7705 connects the user to the audio path.

CN 7715 acknowledges GANC 7710 via a Connect Ack message (in step 12). GANC 7710 sends this message (in step 12) to UE 7705 via a GA-RRC DL Direct Send message. The two means on the call are connected on the audio path. Bidirectional voice traffic flows (in step 13) between UE 7705 and CN 7715 via GANC 7710.

7. CS arc clearing

78 illustrates call clearing initiated by a UE in some embodiments. As shown, the UE 7805 sends (in step 1) a detach message to the CN 7815 to release the call. This message is included in the GA-RRC UL direct transmission message between the UE 7805 and the GANC 7810 . GANC 7810 sends (in step 1) a detach message to CN 7815 (ie, using a RANAP direct send message).

CN 7815 responds to GANC 7810 with a release message (in step 2). The GANC 7810 sends this message (in step 2) to the UE 7805 using a GA-RRC DL Direct Send message.

The UE 7805 responds (in step 3) with a Release Complete message. This message is included in the GA-RRC UL Direct Transmission message between the UE 7805 and the GANC 7810 . GANC 7810 sends (in step 3) a detach message to CN 7815. CN 7815 triggers the release of the connection as described in subclause VIII.Blb: "GA-CSR Connection Release" (in step 4).

8. CS handover

a) CS handover from GERAN to GAN

i) UE terminates the Iu UP packet

79 illustrates a CS handover procedure from GERAN to GAN in one embodiment. The description of the GERAN-GAN handover procedure assumes the following. That is, (1) the UE is on an active call in GERAN; (2) if the UE mode selection is GAN-preferred, or GERAN/UTRAN-preferred, then RxLev from the current serving cell falls below a defined threshold, which in some embodiments may be specified as a fixed value and , or provided by the UE by GERAN BSS in dedicated mode; (3) the UE is successfully registered with the GANC, so that the UE can obtain GAN system information; (4) GERAN provides information about neighboring 3G cells as provided in the AS-related element of system information obtained from GANC, so that one of the cells in the 3G neighboring cell list can be matched with 3G cell information associated with GANC do.

The UE starts (in step 1) to include the GAN cell information in the measurement report message for GERAN. The UE reports the highest signal level for the GAN cell. This is not an actual measured signal level on the GAN, but rather an artificial value that allows the UE to indicate a preference for the GAN (ie, RxLev = 63).

Based on the UE measurement report and other internal algorithms, the GERAN BSC decides to handover to the GAN cell. The BSC 7920 initiates handover preparation by sending a handover request message to the CN 7915 identifying the target 3G RNC (GANC) 7910 (in step 2). The CN 7915 requests (in step 3) to allocate resources for handover to the target GANC 7910 using a relocation request message. The UE 7905 is identified by the included IMSI parameter.

GANC 7910 (in step 4) (1) UDP port and IP address for uplink RTP stream, (2) radio access bearer (RAB) parameter, (3) Iu UP parameter (eg, support mode is AMR voice Sends a GA-RRC Activate Channel message to the UE 7905 including the bearer path setup information received in the relocation request message, such as Iu UP mode when used for a call).

Since the Iu UP support mode is indicated, the UE 7905 sends (in step 5) an Iu UP initialization packet to the IP address and UDP port indicated in the GA-RRC activation channel message. This message is routed to the core network 7915 (eg, R4 media gateway).

The core network 7915 responds (in step 6) with an Iu UP initialization ACK packet. The core network 7915 sends the message to the source IP address and UDP port number of the received initialization packet. The UE 7905 sends (at step 7) a GA-RRC activation channel ACK to the GANC 7910 . The GANC 7910 constructs a handover command message to the UTRAN and sends it to the CN 7915 via a relocation request acknowledgment message (in step 8).

The GANC 7910 informs the UE 7905 of completion of RAB setup (in step 9) through a GA-RRC activation channel complete message. An end-to-end audio path now exists between the UE 7905 and the CN 7915 . The CN 7915 transmits a handover command message to the UTRAN to the GERAN BSC 7920 through a BSSMAP handover command message (in step 10) to complete the handover preparation.

The GERAN BSC 7920 sends (in step 11) an intersystem-UTRAN handover command message including a handover command message to the UTRAN to the UE to initiate a handover to the GAN. The UE does not switch the audio path from the GERAN to the GAN until the handover is complete (ie, until sending a GA-RRC handover complete message) in order to keep the audio dropout short.

The UE accesses the GANC 7910 using the GA-RRC handover access message (in step 12), and provides it to the full intersystem-UTRAN handover command message received from the GERAN. The GANC 7910 indicates to the CN 7915 that it has detected the UE using the relocation detection message (in step 13). The CN 7915 can now selectively switch the user plane from the source GERAN to the target GAN. Bidirectional voice traffic now flows (in step 14) between the UE and CN 7915 via GANC 7910.

The UE sends a GA-RRC handover complete message to indicate completion of the handover procedure at the end (in step 15). The UE switches the user from the GERAN user plane to the GAN user plane.

The target GANC 7910 indicates that the handover is complete using the relocation complete message (in step 16). If this has not been done before, the CN 7915 now switches the user plane from the source GERAN to the target GAN.

Finally, the CN 7915 uses a clear command message (at step 17) to disconnect the connection to the source GERAN. The source GERAN confirms the release of the GERAN resources allocated for this call using the clear complete message (in step 18).

ii) GANC ends the Iu UP packet

80 illustrates an alternative procedure for CS handover from GERAN to GAN in some embodiments. The description of the GERAN-GAN handover procedure assumes the following. That is, if (1) the UE is on an active call in GERAN, (2) UE mode selection is GAN-preferred, or GERAN/UTRAN-preferred, it is assumed that RxLev from the current serving cell falls below the defined threshold. In some embodiments, this threshold may be fixed to a fixed value, or may be provided to the UE by the GERAN BSS in dedicated mode. (3) the UE is successfully registered with the GANC, so that the UE can obtain the GAN system information, and (4) the GERAN provides information about the adjacent 3G cell as provided in the AS-related element of the system information obtained from the GANC Thus, it is assumed that one of the cells in the 3G neighbor cell list can match 3G cell information associated with GANC. As shown, the UE 8005 starts including the GAN cell information for the GERAN BSC 8015 in the measurement report message. The UE 8005 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but rather an artificial value (eg RxLev = 63) that allows the UE to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the GERAN BSC 8015 decides to handover to the GAN cell. The BSC 8015 starts the handover preparation by sending a handover request message identifying the target 3G RNC (GANC) to the core network CN 8020 (in step 2).

The core network CN 8020 requests the target GANC 8010 to allocate resources for handover by using the relocation request message (in step 3). The UE is identified by the included IMSI parameter.

Since the Iu UP support mode is indicated, the GANC 8010 sends an Iu UP initialization packet to the core network CN (in step 4). The core network CN responds (in step 5) with an Iu UP initialization ACK packet.

The GANC 8010 forms a handover command message to the UTRAN and sends it to the core network CN 8020 via a relocation request acknowledgment message (in step 6). The core network CN transmits a handover command message to the UTRAN (in step 7) to the GERAN BSC 8015 through a BSSMAP handover command message to complete the handover preparation.

Next, the GERAN BSC 8015 sends an intersystem-UTRAN handover command message including a handover command message to the UTRAN to the UE 8005 to initiate the handover to the GAN (in step 8). . The UE does not switch the audio path from the GERAN to the GAN until the handover is complete (ie, until sending a GA-RRC handover complete message) in order to keep the audio dropout short.

The UE 8005 accesses the GANC 8010 using the GA-RRC handover access message (in step 9) and provides the full intersystem-UTRAN handover command message received from GERAN. GANC 8010 (in step 10) (1) channel mode, (2) multi-rate codec configuration, (3) UDP port and IP address for uplink RTP stream, (4) bearer path setup such as voice sample size A GA-RRC activation channel message including information is sent to the UE 8005 .

Next, the UE 8005 sends (at step 11) a GA-RRC activation channel ACK indicating the UDP port for the downlink RTP stream to the GANC 8010 . The GANC 8010 informs the UE 8005 of completion of RAB setup (in step 11) with a GA-RRC activation channel complete message.

The UE 8005 transmits a GA-RRC handover complete message to indicate completion of the handover procedure at the end (in step 13). The UE 8005 switches the user from the GERAN user plane to the GAN user plane. The GANC 8010 indicates to the core network CN 8020 that it has detected the UE using the relocation detection message (in step 14). The CN can now selectively switch the user plane from the source GERAN to the target GAN.

Bidirectional voice traffic now flows (in step 15) between the UE 8005 and the core network CN 8020 via the GANC 8010. The target GANC 8010 indicates that the handover is completed using the relocation complete message (in step 16). If this has not been done before, the CN now switches the user plane from the source GERAN to the target GAN.

The CN uses the clear command message (in step 17) to disconnect the connection to the source GERAN. Finally, the source GERAN 8015 confirms the release of the GERAN resources allocated for this call using the clear complete message (in step 18).

b) <u>from UTRAN </u><u>GAN</u><u>to </u><u>CS</u><u></u><u>handover</u>

i) The UE terminates the Iu UP packet.

The description of the UTRAN-GAN handover procedure assumes the following. That is, (1) the UE is on an active call in UTRAN; (2) It is assumed that the UE has received an instruction from the RNC to perform inter-frequency measurement . When the UE is in the GAN preferred mode configured for Event 2A, the UE processes the parameters associated with Event 2A in a GAN-specific manner (described in 3GPP TS 25.331) for reporting of the GAN. When the UE is in GERAN/UTRAN preferred mode and event 2A is configured for a GAN cell, this event is triggered and the UTRAN cells from the UE's neighbor cell list do not satisfy the trigger condition of this event (described in 3GPP TS 25.331). If not, the UE can only send a measurement about the GAN cell, and (3) the UTRAN provides information about the neighbor cell as provided in the AS-related element of the system information obtained from the GANC so that one of the cells in the neighbor list is Assume that it is possible to match the cell associated with the GANC.

81 illustrates a CS handover procedure from UTRAN to GAN in some embodiments. The UE starts (in step 1) to include information about the GAN cell in the measurement report message sent to the RNC 8120 . The UE reports the highest signal level for the GAN cell. This is not an actual measured signal level on the GAN, but rather an artificial value that allows the UE to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the RNC 8120 decides to initiate a handover to the GAN cell. The RNC 8120 starts the preparation phase of the relocation procedure by sending a relocation request message to the CN 8115 identifying the target (EGAN) cell (in step 2).

The CN 8115 requests (in step 3) to allocate resources for handover to the target GANC 8110 using a relocation request message. The UE 8105 is identified by an included IMSI parameter.

GANC 8110 (in step 4) (1) UDP port and IP address for uplink RTP stream, (2) radio access bearer (RAB) parameter, (3) Iu UP parameter (eg, support mode is AMR voice Sends to UE 8105 a GA-RRC Activate Channel message containing the bearer path setup information received in the relocation request message, such as Iu UP mode when used for a call).

Since the Iu UP support mode is indicated, the UE 8105 sends (in step 5) an Iu UP initialization packet to the IP address and UDP port indicated in the GA-RRC activation channel message. This message is routed to the core network 8115 (eg, R4 media gateway).

The core network 8115 responds (in step 6) with an Iu UP initialization ACK packet. The core network 8115 sends a message to the source IP address and UDP port number of the received initialization packet. The UE 8105 sends a GA-RRC activation channel ACK to the GANC 8110 (in step 7).

The target GANC 8110 uses a relocation request acknowledgment message indicating that it can support the requested handover (in step 8) and includes a physical channel reconfiguration message indicating the radio channel to which the UE 8105 should be directed. Thus, it acknowledges the handover request message.

The GANC 8110 informs the UE 8105 of the completion of RAB setup (in step 9) with a GA-RRC activation channel complete message. There is now an end-to-end audio path between the UE 8105 and the CN 8115 . The CN 8115 sends a relocation command message to the RNC 8120 (in step 10) to complete the relocation preparation.

The RNC 8120 sends (at step 11) a physical channel reconfiguration message to the UE to initiate handover to the GAN. The UE does not switch its audio path from the UTRAN to the GAN until the handover is complete (ie, until sending a GA-RRC handover complete message) to keep the audio dropout short. The UE accesses the GANC 8110 using the GA-RRC handover access message (in step 12) and provides the full physical channel reconfiguration message received from the RNC 8120.

The GANC 8110 indicates to the CN 8115 that it has detected the UE using the relocation detection message (in step 13). The CN 8115 can now selectively switch the user plane from the source RNC 8120 to the target GANC 8110 . Bidirectional voice traffic now flows (in step 14) between the UE and CN 8115 via GANC 8110.

The UE transmits a GA-RRC handover complete message to indicate completion of the handover procedure at this point (in step 15). The UE switches the user from the UTRAN user plane to the GAN user plane. The target GANC 8110 indicates that the handover is complete using the relocation complete message (in step 16). If this has not been done before, the CN 8115 now switches the user plane from the source RNC 8120 to the target GANC 8110 .

Finally, the CN 8115 disconnects the connection to the source RNC 8120 using the Iu release command (in step 17). The source RNC 8120 (in step 18) uses Iu Release Complete to confirm the release of the UTRAN resource allocated for this call.

ii) GANC ends the Iu UP packet

82 illustrates an alternative procedure for CS handover from UTRAN to GAN using RRC protocol in some embodiments. The description of the UTRAN-GAN handover procedure assumes the following. That is, (1) the UE is on an active call in the UTRAN, (2) the UE has been instructed by the RNC to make an inter-frequency measurement (i.e. the GAN cell is assigned a frequency value different from the frequency used in the UTRAN) ), (a) if the UE is in GAN preferred mode configured for event 2A, then the UE processes the parameters associated with event 2A in a GAN specific manner for reporting of EGAN, (b) if the UE is in GERAN/UTRAN preferred mode and event When 2A is configured for a GAN cell, if this event is triggered and the UTRAN cells from the UE's neighbor cell list do not satisfy the trigger condition of this event (as described in 3GPP TS 25.331), the UE is connected to the GAN cell and (3) the UTRAN provides information about the neighbor cell as provided in the AS-related element of the system information obtained from the GANC so that one of the cells in the neighbor cell list will match the cell associated with the GANC. Assume that it is possible

As shown in FIG. 82 , the UE 8205 starts to include (in step 1) information about the GAN cell in the measurement report message sent to the RNC 8215 . The UE 8205 reports the highest signal level for the GAN cell. This is not an actual measured signal level on the GAN, but rather an artificial value that allows the UE 8205 to indicate a preference for the GAN.

Based on the UE measurement report and other internal algorithms, the RNC 8215 decides to initiate a handover to the GAN cell. The RNC 8215 starts the preparation phase of the relocation procedure by sending (in step 2) a relocation request message identifying the target (GAN) cell to the core network CN.

Next, steps 3 to 5 shown in Fig. 82 are CSR GERAN-GAN in the sub-clause "GANC ends Iu UP packet" described above, except that the messages are RRC messages (instead of CSR). Steps 3 to 5 for handover are performed similarly. The target GANC 8210 uses a relocation request acknowledgment message that includes (in step 6) a physical channel reconfiguration message indicating that it can support the requested handover and indicates the radio channel to which the UE should be directed. Acknowledge the request message.

Next, the core network CN 8220 sends a relocation command message to the RNC 8215 (in step 7) to complete the relocation preparation. The RNC 8215 sends a physical channel reconfiguration message to the UE 8205 to initiate the handover to the GAN (in step 8). The UE does not switch its audio path from the UTRAN to the GAN until the handover is complete (ie, until sending a GA-RRC handover complete message) to keep the audio dropout short.

Next, steps 9 to 16 shown in FIG. 82 are "GANC terminates the Iu UP packet" as described above except that steps 9 to 16 in FIG. 82 use the RRC protocol instead of the CSR protocol. Steps 9 to 16 for the CSR GERAN-GAN handover in the subclause , are performed similarly. Next, the core network CN 8220 disconnects the connection to the source RNC using the Iu release command (in step 17). Finally, the source RNC 8215 (in step 18) uses the Iu Release Complete message to confirm the release of the UTRAN resources allocated for this call.

c) <u>from GAN </u><u>GERAN</u><u>to </u><u>CS</u><u></u><u>handover</u>

The procedure descriptions in this subclause assume the following. That is, (1) the UE is on an active call in EGAN; (2) GERAN becomes available, (i) UE mode selection is GERAN/UTRAN-preferred, or (ii) UE mode selection is GAN-preferred, and the UE performs GANC as well as its local measurements and received RTCP reports. Based on the uplink quality indication received from , it is assumed that the GAN starts out of coverage.

The handover procedure from GAN to GERAN is always triggered by the UE.

83 illustrates a CS handover procedure from GAN to GERAN in some embodiments. The GANC 8310 may send a GA-RRC uplink quality indication if there is a problem with the uplink quality for the on-going call (in step 1). The uplink quality indication is information sent by the GANC 8310 to the UE 8305 indicating the crossing of the uplink quality threshold in the uplink direction. Whenever the UE 8305 receives a bad quality indication, it should initiate a handover procedure as described in the next step. Alternatively, the UE 8305 may use its local measurement or received RTCP report to determine whether to initiate a handover procedure.

UE 8305 (in step 2) in order of preference for handover (eg, ranked by Cl pathloss parameter), GA-RRC hand indicating a list of target GERAN cells identified by channel mode and CGI An over information message is sent to the GANC 8310 and includes the received signal strength for each identified GERAN cell. This list is the most recent information available from the GSM RR subsystem. In addition, the GA-RRC handover information message may include a list of target UTRAN cells ranked in order of preference for handover, and received signal strength for each identified UTRAN cell.

When the serving GANC 8310 selects a target GERAN cell, a handover procedure to GERAN is performed. The serving GANC 8310 informs the CN 8315 that a handover is required using a relocation request message (in step 3) and starts the handover preparation by including the GERAN cell list provided by the UE 8305 . The GANC 8310 may include only one subset of the cell list provided by the UE 8305 .

The CN 8315 selects a target GERAN cell and requests to allocate the necessary resources using a handover request message (in step 4). The target GERAN constructs a handover command message providing information about the assigned channel and provides it to the CN 8315 through a handover request acknowledgment message (in step 5).

The CN 8315 informs the GANC 8310 to handover the UE 8305 to GERAN using the relocation command message (in step 6), and ends the handover preparation phase. The GANC 8310 sends (in step 7) a GA-RRC handover command to the UE 8305 containing details about the target resource allocation sent by the GERAN. The UE 8305 (in step 8) includes a handover reference element, so that the target GERAN can correlate this handover access with the handover command message previously sent to the CN 8315 in response to the handover request message. Um: Transmits a handover access message.

The target GERAN confirms the detection of the handover to the CN 8315 using the handover detection message (in step 9). CN 8315 may at this point (at step 10) switch the user plane to the target BS. The GERAN provides physical information to the UE 8305 (ie, timing progress) so that the UE 8305 synchronizes with the GERAN (in step 11). The UE 8305 informs the GERAN that the handover is complete using the handover complete (in step 12).

The GERAN confirms the completion of the handover to the CN 8315 through the handover completion message (in step 13). The CN 8315 may use the target CGI used in the handover procedure for charging purposes. Bidirectional voice traffic now flows (in step 14) between UE 8305 and CN 8315 via GERAN.

Upon receiving confirmation of the completion of the handover, the CN 8315 instructs the GANC 8310 to release the resource allocated to the UE 8305 (in step 15) via the Iu release command. The GANC 8310 instructs (at step 16) to release the UE 8305 resource using a GA-RRC Release message. The GANC 8310 confirms the resource release to the CN 8315 using the Iu release complete message (in step 17).

The UE 8305 confirms the resource release to the GANC 8310 using the GA-RRC Release Complete message (in step 18). The UE 8305 may finally deregister from the GANC 8310 using a GA-RC deregistration message (at step 19 ).

d) CS handover from GAN to UTRAN

The procedure description in this subclause assumes that: (1) the UE is on an active call in the GAN; (2) UE can operate in all GAN, GERAN and UTRAN modes; (3) UTRAN becomes available, (i) UE is in GERAN/UTRAN-preferred mode, or (ii) UE mode selection is GAN Preferred, and its local measurement and received as well as uplink quality indications received from GANC Assume that it starts out of GAN coverage based on the RTCP report.

84 illustrates a CS handover procedure from GAN to UTRAN in some embodiments. The handover procedure from the GAN is always triggered by the UE 8405 . The GANC 8410 may send a GA-RRC uplink quality indication if there is a problem with the uplink quality for the on-going call (in step 1). The uplink quality indication is information that is transmitted by the GANC 8410 to the UE 8405 and indicates the crossing of the uplink quality threshold in the uplink direction. Whenever the UE 8405 receives a bad quality indication, it should initiate a handover procedure as described in the next step. Alternatively, the UE 8405 may use its local measurement or received RTCP report to determine whether to initiate a handover procedure.

The UE 8405 sends (in step 2) a GA-RRC handover information message indicating a list of channel modes and candidate target UTRAN and GERAN cells in order of preference for handover to the serving GANC 8410, and identifies each Contains the received signal strength for the selected cell. A UTRAN cell is identified by a PLMN ID, LAC and 3G cell identity (defined in 3GPP TS 25.331).

If the serving GANC 8410 selects the UTRAN as the target RAT, a handover procedure to the UTRAN is performed. The serving GANC 8410 informs the CN 8415 that a handover is required using a relocation request message (in step 3) and starts the handover preparation by including the UTRAN cell list provided by the UE 8405 . The GANC 8410 may only include a subset of the cell list provided by the UE 8405 .

The CN 8415 initiates the handover procedure towards the target RNC 8420 identified by the serving GANC 8410 . The CN 8415 makes a request from the target RNC 8420 to allocate the necessary resources using a relocation request message (in step 4). The target RNC 8420 constructs a physical channel reconfiguration message providing information about the allocated UTRAN resources and sends it to the CN 8415 through a relocation request acknowledgment message (in step 5).

The CN 8415 informs the serving GANC 8410 to handover the UE 8405 to the UTRAN using a relocation command message (including a physical channel reconfiguration message) (in step 6), and indicates the handover preparation step. quit The serving GANC 8410 sends (in step 7) a GA-RRC handover command to the UE 8405 that includes details about the target resource allocation sent by the UTRAN.

The target RNS achieves uplink synchronization on the Uu interface (in step 8). The target RNC 8420 confirms the detection of the handover to the CN 8415 using the relocation detection message (in step 9). At this point CN 8415 switches the user plane to the target RNS (at step 10). The UE 8405 informs that the UTRAN handover is complete using the handover to UTRAN complete (in step 11).

The UTRAN confirms the completion of the handover to the CN 8415 through a relocation complete message (in step 12). If the user plane was not switched in step 10, the CN 8415 switches the user plane to the target RNS. Bidirectional voice traffic now flows (in step 13) between the UE 8405 and the CN 8415 via the UTRAN.

Upon receipt of confirmation of the completion of the handover, the CN 8415 instructs the serving GANC 8410 to release the resources allocated to the UE 8405 via an Iu release command (in step 14). The serving GANC 8410 instructs the UE 8405 to release resources using a GA-RRC release message (in step 15).

The serving GANC 8410 confirms the resource release to the CN 8415 using the Iu release complete message (in step 16). The UE 8405 confirms the resource release to the serving GANC 8410 using a GA-RRC Release Complete message (in step 17). The UE 8405 may finally deregister from the serving GANC 8410 using a GA-RC deregistration message (in step 18).

9. GA-RRC packet transmission channel management procedure

The GA-RRC Packet Transport Channel (GA-RRC PTC) provides the association between the UE and the network for transmission of GPRS user data via the Up interface (ie, via GAN in Iu-mode). PTC uses the UDP transport GTP-U protocol. The endpoint address of the PTC is identified by the IP address and UDP port assigned to the PTC in the UE and network during the PTC activation procedure. The UDP port number for GTP-U is as defined in 3GPP TS 25.414. Multiple PTC instances between the UE and the network may be active simultaneously using the same endpoint address. Each PTC instance is assigned a unique GTP-U tunnel endpoint ID (one on the UE and one on the network) during the activation procedure. The UE and GANC manage the activation and deactivation of PTC instances based on data transfer requests and configurable PTC timers.

a) <u>Status of GA-RRC packet transmission channel</u>

A UE in the GA-RRC-connected state may be in one of two PTC states: PTC-Standby or PTC-Active. PTC-Standby: This is the initial/default PTC state of the UE when in GA-RRC-connected state in GAN mode. The UE cannot transmit or receive GPRS user data to or from the network. The UE does not need to activate PTC before sending GPRS user data. When the UE successfully establishes the PTC, the UE transitions to the PTC-active state. The PTC-active UE is in the GA-RRC-connected state and the PTC is active between the UE and the network, and the UE can send and receive GPRS user data to and from the network. The following are possible triggers for GA-RRC PTC activation on UE side: (1) UE initiates uplink user data transmission, (2) GANC initiates PTC activation. That is, the UE receives a GA-RRC-ACTIVATE-PTC-request message from the GANC.

Upon successful PTC activation and in parallel with the transition to the PTC-active state, the UE starts the PTC timer. When the PTC timer expires, the UE sends a message to the GANC to initiate PTC deactivation. Upon successful PTC activation release, the UE transitions to the PTC-standby state. At any time in the GA-RRC-connected state and the PTC-active state, the UE may receive a GA-RRC release message. In addition to requesting release of the RRC session, this is interpreted as an implicit PTC deactivation command by the UE. At any time in GAN mode, when the serving RR entity switches to GSM-RRAJTRAN-RRC, the GA-RRC is separated from the GPRS SAP, and the UE enters the GERAN/UTRAN mode. At the same time, the UE will release the associated PTC regardless of the PTC timer state. The UE GA-RRC entity maintains one PTC for each active PDP context. The PTC timer is restarted whenever an uplink user data packet is transmitted or a downlink user data packet is received in relation to the PDP context. The PTC timer value is provided to the UE as part of the GAN registration procedure (ie, via the GA-RC registration accept message).

b) <u>PTC Initial Activation</u>

85 illustrates a packet transport channel initial activation procedure in some embodiments. The following description assumes that the UE 8505 is in a GA-RRC-idle state in some embodiments. The GA-RRC connection establishment procedure is performed (in step 1) as described in the section UE-initiated GA-RRC connection establishment above. The UE 8505 transitions to a GA-RRC-connected state and a PTC-standby state. Additional PS signaling procedures are performed (in step 2).

CN SGSN 8510 initiates the RAB assignment procedure (in step 3), RAB-ID for user data, CN transport layer address (IP address) and CN Iu transport association (GTP-U terminal endpoint identifier, TEID) include The GANC 8515 sends a GA-RRC activation PTC request message to the UE 8505 to request activation of the packet transport channel (in step 4). The message includes a RAB-ID, and a CN IP address and TEID to enable the UE 8505 to send a PTC packet (ie, a GTP-U message) directly to the SGSN.

The UE 8505 acknowledges the PTC activation (in step 5) and provides an Iu transport association (GTP-U TEID) and transport layer address (IP address) identifying the UE end of the PTC. The UE 8505 transitions to the PTC-active state and starts the PTC timer.

Upon receiving the acknowledgment, the GANC 8515 sends a RAB assignment response message to the CN SGSN 8510 to complete the RAB assignment procedure (in step 6), including the UE IP address and GTP-U TEID. Additional PS signaling procedures are performed (in step 7). That is, examples are illustrated in the PDP Context Activation and Network Request PDP Context Activation subsections below. The UE 8505 initiates uplink user data transmission via the established PTC (in step 8), and the CN SGSN 8510 may use the same transport channel to transmit the downlink user data packet.

c) <u>PTC data transfer</u>

86 illustrates transmission of a GPRS user data packet over a GAN packet transport channel in some embodiments. If necessary, the GAN PTC is established (in step 1) as specified in subclause VIII.B.9.b: "Initial activation of PTC" above. Upon establishing the GA-RRC PTC, the UE 8605 enters the PTC-active state to start the PTC timer. The UE 8605 initiates the transmission of the uplink user data packet using the standard GTP-U protocol specified in 3GPP TS 29.060 (in step 2) and restarts the PTC timer.

CN 8615 (SGSN) sends the downlink user data packet using the same PTC associated with the particular PDP context (in step 3). Downlink user data packets are transmitted using the standard GTP-U protocol specified in 3GPP TS 29.060. Upon receipt of the downlink data packet, the UE restarts the associated PTC timer. Additional uplink and downlink user data packets are sent (in step 4) over the same PTC as described in steps 2 and 3. After each transmit/receive, the UE 8605 restarts the PTC timer.

d) <u>UE Initiation </u><u>PTC</u><u> active off</u>

87 illustrates a scenario when the UE deactivates the packet transport channel after the PTC timer expires in some embodiments. The UE 8705 is in a GA-RRC-connected state and a PTC-active state (in step 1). The PTC timer associated with one of the active packet transport channels expires.

The UE 8705 sends (in step 2) a GA-RRC Deactivate PTC Request message to the GANC 8710 that includes the RAB-ID to identify the PTC and indicates denormalization as the cause of deactivation. The GANC 8710 sends a RAB Release Request message to the CN(SGSN) 8715 to request the release of the associated RAB (in step 3). CN(SGSN) 8715 responds with a RAB Assignment Request message indicating release (in step 4).

GANC 8710 responds to UE 8705 with a GA-RRC Deactivate PTC ACK message to acknowledge successful deactivation (in step 5). The UE 8705 transitions to the PTC-Standby state. The GANC 8710 sends (in step 6) a RAB assignment response message to notify the SGSN 8715 that the RAB release procedure is complete.

e) <u>UE Initiation </u><u>PTC</u><u> re-activation</u>

88 illustrates a scenario when the UE initiates reactivation of a packet transport channel in some embodiments. The UE is in a GA-RRC-connected state and a PMM-connected state. For example, a PS signaling connection and an active PDP context exist between the UE 8805 and the CN 8815 , but the PTC has been previously deactivated by the UE 8805 due to PTC timer expiration in some embodiments. The UE 8805 is in a GA-RRC-connected state and a PTC-standby state. The UE 8805 is in a PMM-connected state (ie, a PS signaling connection and an active PDP context exist).

The UE 8805 has a PDU to transmit. The UE 8805 sends a service request message (with a service type value "data") to the GANC 8810 via a GA-RRC UL direct transmit message (in step 1). The GANC 8810 sends a service request message to the CN 8815 via the existing signaling connection using the RANAP direct transport message (in step 2).

CN 8815 may optionally initiate the security mode control procedure described in subclause VIII.B.3: "Security Mode Control" (in step 3). CN 8815 responds (in step 4) with a service accept message. GANC 8810 sends a message to UE 8805 (in step 5).

UE 8805, GANC 8810 and CN 8815 (at step 6) send GA-RRC packets as described in steps 3 to 6 of section VIII.B.9.b: "PTC Initial Activation" above (at step 6). Set the transmission channel (PTC). The UE 8805 transitions to the PTC-active state and starts the PTC timer. The UE 8805 sends (in step 7) an uplink PDU. Additional data transfers may occur.

f) <u>Disable Network Initiated PTC Active</u>

89 illustrates a scenario when the network initiates deactivation of a packet transport channel in some embodiments. The UE 8905 is in a GA-RRC-connected state and a PTC-active state.

Optionally, GANC 8910 may initiate a PTC deactivation procedure, such as as a result of an error handling procedure. If so, GANC 8910 sends (in step 1) a RAB Release Request message to CN 8915. The CN(SGSN) 8915 sends (in step 2) a RAB assignment request message to request release of the associated RAB. A release request may include one or more RABs.

The GANC 8910 requests deactivation of the associated GA-RRC PTC by sending a GA-RRC deactivation PTC request message to the UE 8905 (in step 3). The UE 8905 transitions to the PTC-Standby state, stops the PTC timer and sends an acknowledgment back to the GANC 8910 (in step 4). Steps 3 and 4 are repeated for each additional RAB/PTC that must be released. The GANC 8910 notifies the CN(SGSN) 8915 (in step 5) that the release was successful.

g) Network initiated PTC re-activation

90 illustrates a scenario when the network initiates reactivation of a packet transport channel in some embodiments. The UE 9005 is in a GA-RRC-connected state and a PMM-connected state. For example, a PS signaling connection and an active PDP context exist between the UE and the CN, but the PTC has been deactivated in some embodiments. The UE 9005 is in a GA-RRC-connected state and a PTC-standby state. The UE 9005 is in a PMM-connected state (ie, a PS signaling connection and an active PDP context are present).

CN 9015 has a PDU to send to UE 9005 . The CN 9015 may optionally initiate the security mode control procedure described in subclause VIII.B.3: "Security mode control" above (in step 1). UE 9005, GANC 9010 and CN 9015 (in step 2) GA-RRC as described in steps 3 to 6 of subclause VIII.B.9.b: "PTC Initial Activation" above (in step 2). Set the packet transmission channel (PTC). The UE 9005 transitions to the PTC-active state and starts the PTC timer. CN 9015 sends a downlink PDU (in step 3). Additional data transfers may occur.

h) <u>Implicit due to UE deregistration </u><u>PTC</u><u> active off</u>

96 illustrates an inherent PTC activity release procedure in some embodiments. As part of the GAN deregistration procedure, the GANC needs to release all resources allocated to that UE 9605 . GAN deregistration may be initiated either explicitly by the UE 9605 or unconditionally by the GANC 9610 if loss of signaling connection is detected. Initially, one or more GA-RRC PTCs associated with the UE 9605 are in a PTC-active state.

GAN deregistration procedure is initiated by UE 9605 or GANC 9610 for UE 9605 (in step 1). Optionally, the good resources associated with the CS domain are released (in step 2). Optionally, if there is a good resource associated with the PS domain, the GANC 9610 initiates the Iu release procedure to release the corresponding RAB (in step 3). CN(SGSN) 9615 responds (in step 4) with an Iu release command. Upon receipt of the Iu Release command, the GANC 9610 locally deactivates all associated PTCs (in Step 5) and responds to the Core Network (SGSN) 9615 with an Iu Release Complete message (in Step 6).

10. Activate PDP Context

91 illustrates a successful UE-initiated PDP context activation procedure assuming the UE in GA-RRC-idle mode in some embodiments. The GA-RRC connection establishment procedure (in step 1) is performed as described in the sub-clause UE-initiated GA-RRC connection establishment above. If a GA-RRC connection already exists (eg, there is an existing CS call in progress), this step is skipped.

Upon request from the upper layer, the UE 9105 sends (in step 2) a service request message (with the service type value "Signaling") to the GANC 9110 via a GA-RRC Initial Direct Send message. The GANC 9110 establishes an SCCP connection to the CN 9115 and sends a service request to the CN 9115 using a RANAP initial UE message (in step 3). Subsequent NAS messages between the UE 9105 and the core network 9115 will be transmitted between the GANC 9110 and the CN 9115 using a RANAP direct transport message.

The CN 9115 may optionally authenticate the UE 9105 using a standard UTRAN authentication procedure (in step 4). The CN 9115 may optionally initiate the security mode control procedure described in subclause VIII.B.3: "Security Mode Control" (in step 5).

The CN(SGSN) 9115 responds (in step 6) with a service accept message. GANC 9110 sends a message to UE 9105 (in step 6). The UE 9105 sends (in step 7) an Activate PDP Context Request message to the CN 9115 providing details regarding the PDP context. This message is included in the GA-RRC UL Direct Transmission message between the UE 9105 and the GANC 9110 . GANC 9110 sends (in step 7) an Activate PDP Context Request message to CN 9115 .

UE 9105, GANC 9110 and CN 9115 (at step 8) GA-RRC as described in steps 3 to 6 of subclause VIII.B.9.b: "PTC Initial Activation" above (at step 8). Set the packet transmission channel (PTC). The CN 9115 uses the Activate PDP Context Accept message (in step 9) to instruct the GANC 9110 that the PDP context setup is complete. The GANC sends this message (in step 9) to the UE 9105 via a GA-RRC DL direct transfer message. UE 9105 and CN 9115 exchange user data transmission via the established PTC (in step 10).

11. Enable Network Request PDP Context

92 illustrates a successful network-requested PDP context activation procedure assuming the UE in GA-RRC-idle mode in some embodiments. Initially, the CN (SGSN) 9215 receives downlink user data for transmission to the UE, and the associated RAB is not established. The UE is in the PMM-idle state.

The CN(SGSN) 9215 sends a RANAP paging message to the UE 9205 via the GANC 9210 to find the user (in step 1). The paging request indicates paging for PS domain signaling. The GANC 9210 sends paging information to the UE 9205 via a GA-RRC paging request message (in step 2).

UE 9205 responds to SGSN 9215 with a service request message (with service type value "paging response") via GANC 9210 (in step 3). The message is wrapped in a GA-RRC initial direct transfer message. The GANC 9210 sends (at step 4) a service request message wrapped in a RANAP initial UE message to the SGSN 9215 .

The CN 9215 may optionally authenticate the UE 9205 using a standard UTRAN authentication procedure (in step 5). The CN 9215 may optionally initiate the security mode control procedure described in subclause VIII.B.3: "Security Mode Control" above (in step 6).

CN 9215 sends (at step 7) a Request PDP Context Activate message to GANC 9210 . GANC 9210 sends this message (in step 7) to UE 9205 via a GA-RRC DL Direct Send message.

The UE 9205 sends (in step 8) an Activate PDP Context Request message to the CN 9215 providing details regarding the PDP context. This message is included in the GA-RRC UL Direct Transmission message between the UE 9205 and the GANC 9210 . The GANC sends (in step 8) an Activate PDP Context Request message to the CN 9215. UE 9205, GANC 9210, and CN 9215 (in step 9) refer to subclause VIII. B.9.b: Set up the GA-RRC packet transmission channel (PTC) in steps 3 to 6 of "PTC Initial Activation".

The CN 9215 instructs the GANC 9210 that the PDP context setup is complete, using the Activate PDP Context Accept message (at step 10). The GANC sends this message (in step 10) to the UE 9205 via a GA-RRC DL direct transmission message. UE 9205 and CN 9215 exchange user data transmission via the established PTC (in step 11).

12. Activate PDP Context Using Active CS Session

93 illustrates a successful UE-initiated PDP context activation procedure assuming the UE 9305 in a GA-RRC-connected mode (eg, an existing CS session) in some embodiments. The GA-RRC connection establishment procedure is performed as described in the sub-clause UE-initiated GA-RRC connection establishment above. If a GA-RRC connection already exists (eg, there is an existing CS call in progress), this step is skipped.

Upon receipt of the request from the upper layer, the UE 9305 sends (in step 1) a service request message (with the service type value "Signaling") to the GANC 9310 via a GA-RRC Initial Direct Send message. The GANC 9310 establishes an SCCP connection to the CN 9315 (in step 2) and sends a service request message to the CN using the RANAP initial UE message. Subsequent NAS messages between the UE 9305 and the core network 9315 will be sent between the GANC 9310 and the CN 9315 using a RANAP direct transport message.

The CN 9315 may optionally authenticate the UE 9305 using a standard UTRAN authentication procedure (in step 3). The CN 9315 may optionally initiate the security mode control procedure described in subclause VIII.B.3: "Security Mode Control" above (in step 4).

CN(SGSN) 9315 responds (in step 5) with a service accept message. GANC 9310 sends a message to UE 9305 (in step 5). The UE 9305 sends (in step 6) an Activate PDP Context Request message to the CN 9315 providing details regarding the PDP context. This message is included in the GA-RRC UL Direct Transmission message between the UE 9305 and the GANC 9310 . GANC sends (in step 6) an Activate PDP Context Request message to CN 9315.

UE 9305, GANC 9310 and CN 9315 (at step 7) send GA-RRC packets as described in steps 3 to 6 of subclause VIII.B.9.b: "PTC Initial Activation". Set the transmission channel (PTC). The CN 9315 instructs the GANC 9310 using the Activate PDP Context Accept message that the PDP context setup is complete (in step 8). The GANC sends this message to the UE 9305 (in step 8) via a GA-RRC DL Direct Send message. UE 9305 and CN 9315 exchange user data transmission via the established PTC (in step 9).

13. SRNS Relocation

A serving RNS relocation procedure is performed for the UE in PMM-connected state to move the RAN access point from the old RNC to the new RNC. Two scenarios will be considered: (1) SRNS relocation from RNC to GANC, ie UTRAN to GAN, and (2) SRNS relocation from GANC to RNC, ie GAN to UTRAN. These procedures include several options based on support for Iur interfaces and lossless SRNS relocation. In this version of the GAN specification, it is assumed that the Iur interface is not supported. Additionally, lossless SRNS relocation is also not supported unless the PDCP protocol is included in the GAN solution to minimize data transmission.

a) <u>From UTRAN to GAN </u><u>SRNS</u><u> relocation</u>

94 illustrates an SRNS relocation procedure from UTRAN to GAN for a UE in PMM connected state in some embodiments. Assume that the Iur interface and lossless SRNS relocation procedure are not supported. Initially, the UE 9405 is registered for GAN service and with a PMM connected state. At least one PDP context is active with a maximum bitrate greater than zero.

After detecting the GAN coverage and successfully registering for the GAN service, the UE 9405 sends (in step 1) a measurement report indicating the highest signal level for the GAN cell to the RNC 9410 . The RNC 9410 sends (in step 2) a relocation request message to the core network (SGSN) 9420 to initiate the SRNS relocation procedure. The message indicates the GANC 9415 as the target RNC 9410 and contains information necessary for relocation coordination.

The core network (SGSN) 9420 sends (at step 3) a request to the GANC 9415 . The message contains a list of RABs to be set up and associated information. Based on the relocation request message, CN 9420 and GANC 9415 establish the requested RAB and associated PS transport channel, as specified in the GA-RRC packet transport channel management procedure subclause (in step 4). .

The GANC 9415 responds to the core network 9420 (in step 5) with an acknowledgment containing the target RNC 9410-source RNC transport container. The core network (SGSN) 9420 proceeds with the relocation by sending (in step 6) a relocation command including the target RNC-source RNC transport container to the previous RNC.

The RNC 9410 starts to transmit data for the transmitted RAB to the UE 9405 (in step 7). Transmission is performed for downlink user data only, and is based on the transport layer address and Iu transport association received from GANC 9415 .

The RNC 9410 sends (in step 8) a physical channel reconfiguration message to the UE 9405 to initiate the relocation to the GAN. RNC 9410 continues the relocation by sending (at step 9) SRNS context information to GANC 9415 via core network (SGSN) 9420 . The core network (SGNS) 9420 sends (at step 10) the SRNS context to the GANC 9415 . GANC 9415 responds (at step 11) with a Relocation Detect message.

The UE 9405 sends (at step 12) a GA-RRC Relocation Complete message to the GANC 9415 to indicate successful relocation. The GANC 9415 sends (at step 13) a relocation complete message to the core network (SGSN) 9420 to complete the procedure.

Upon receiving the relocation complete message, the core network (SGSN) 9420 switches the user plane from the RNC 9410 to the GANC(UE), and (in step 14) initiates the Iu release procedure towards the RNC 9410 . After the data transfer timer expires and after releasing the associated resource, the RNC 9410 responds (at step 15) to the core network (SGSN) 9420 with an Iu Release Complete message.

14. short message service

GAN provides support for circuit switched and packet switched SMS services. GAN-attached UEs and GPRS-enabled UEs will send and receive SMS messages via GAN.

a) <u>CS-based SMS</u>

CS-based SMS support in GAN is based on the same mechanism used for CS mobility management and call control. On the UE side, the SMS layer (including supporting CM sublayer functions) uses the services of the MM layer to send SMS messages according to the standard circuit switched UMTS implementation. The SM-CP protocol is effectively tunneled between the UE and the CN using GA-RRC from the message UE to the GANC, where the GANC relays the SM-CP-RANAP message for transmission over the Iu-cs interface. As in the case of mobility management and call control procedures, secure IPSec tunnels and TCP sessions are used to provide secure and reliable SMS delivery over IP networks.

b) <u>PS-based SMS</u>

PS-based SMS message transmission is based on the same mechanism as the transmission of PS mobility management and session management signaling messages. On the UE side, the SMS layer (including supporting CM sublayer functions) uses the services of the RRC (ie, GA-RRC) layer to send SMS messages according to the standard packet switched UMTS implementation. As in the case of mobility management and session management signaling, secure IPsec tunnels and TCP sessions are used to provide secure and reliable PS-based SMS delivery over IP networks.

IX. computer system

95 conceptually illustrates a computer system implementing some embodiments of the present invention. Computer system 9500 includes bus 9505 , processor 9510 , system memory 9515 , read-only memory 9520 , persistent storage 9525 , input device 9530 , and output device 9535 . do.

Bus 9505 collectively represents all system buses, peripheral buses, and chipset buses that support communication between the internal devices of computer system 9500 . For example, bus 9505 communicatively couples processor 9510 to read-only memory 9520 , system memory 9515 , and permanent storage 9525 .

From these various memory units, the processor 9510 receives instructions to be executed and data to be processed in order to execute the process of the present invention. In some embodiments the processor includes a Field Programmable Gate Array (FPGA), ASIC, or various other electronic components for executing instructions. Read-only memory (ROM) 9520 stores static data and instruction names needed by the processor 9510 and other modules of the computer system. On the other hand, the permanent memory device 9525 is a read-write memory device. This device is a non-volatile memory device that stores instructions and data even when the computer system 9500 is off. Some embodiments of the present invention use mass storage devices (eg, magnetic or optical disks and corresponding disk drives) as permanent storage 9525 . Some embodiments use one or more removable storage devices (flash memory cards or memory sticks) as permanent storage devices.

Like permanent storage 9525, system memory 9515 is a read-and-write memory device. However, unlike the storage device 9525, the system memory is a volatile read-write memory, such as a random access memory. System memory stores some of the instructions and data that the processor needs at run time.

Instructions and/or data necessary to perform the processes of some embodiments are stored in system memory 9515 , permanent storage 9525 , read-only memory 9520 , or a combination thereof. For example, various memory units contain instructions for processing multimedia items in accordance with some embodiments. From these various memory units, the processor 9510 retrieves instructions to execute and data to process in order to execute the processes of some embodiments.

Bus 9505 is also connected to input and output devices 9530 and 9535. Input devices enable a user to communicate information and select commands to a computer system. Input device 9530 includes an alphanumeric keyboard and cursor-controller. The output device 9535 displays the image generated by the computer system. The output device includes a printer and a display device such as a cathode ray tube (CRT) or liquid crystal display (LCD). Finally, as shown in FIG. 95 , bus 9505 also connects computer 9500 to network 9565 via a network adapter (not shown). In this manner, a computer may be part of a network of computers (eg, a local area network (LAN), a wide area network (WAN), or an intranet) or a network of networks (eg, the Internet).

Those skilled in the art should recognize that some or all of the components of computer system 9500 may be used with the present invention. For example, some or all components of the computer system described with respect to FIG. 95 include some embodiments of UEs, FAPs, GANCs, and other equipment described above. In addition, those skilled in the art will understand that other system configurations may be used with the present invention or components of the present invention.

X. Definitions and Abbreviations

The following is a list of definitions and abbreviations used.

AAA Authentication, Authorization and Accounting

AKA Authentication and Key Agreement

AP Access Point

AS Access Stratum

BSC Base Station Controller

BSS Base Station Subsystem

BSSGP Base Station System GPRS Protocol

BSSMAP Base Station System Management Application Part

CC Call Control

CGI Cell Global Identification

CM Connection Management

CN Core Network

CS Circuit Switched

CTM Cellular Text Telephone Modem

DNS Domain Name System

DTM Dual Transfer Mode

EAP Extensible Authentication Protocol

GA-CSR Generic Access - Circuit Switched Resources

GA-PSR Generic Access - Packet Switched Resources

GA-RC Generic Access - Resource Control

GAN Generic Access Network

GANC Generic Access Network Controller

ETSI European Telecommunications Standards Institute

FCC US Federal Communications Commission

FQDN Fully Qualified Domain Name

GAD Geographical Area Description

GERAN GSM EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GMM/SM GPRS Mobility Management and Session Management

GPRS General Packet Radio Service

GSM Global System for Mobile communications

GSN GPRS Support Node

HLR Home Location Register

HPLMN Home PLMN

IETF Internet Engineering Task Force

IKE Internet Key Exchange

IKEv2 IKE Version 2

IMEISV International Mobile station Equipment Identity and Software Version number

IMSI International Mobile Subscriber Identity

IP Internet Protocol

LA Location Area

LAI Location Area Identity

LLC Logical Link Control

MAC Medium Access Control

MAC Message Authentication Code

MM Mobility Management

MS Mobile Station

MSC Mobile Switching Center

MTPl Message Transfer Part layer 1

MTP2 Message Transfer Part layer 2

MTP3 Message Transfer Part layer 3

NAS Non-Access Stratum

PDP Packet Data Protocol

PDU Protocol Data Unit

PLMN Public Land Mobile Network

PSAP Public Safety Answering Point - A PSAP is an emergency services network element that is responsible for answering emergency calls

PSTN Public Switched Telephone Network

P-TMSI Packet - TMSI

QoS Quality of Service

RA Routing Area

RAC Routing Area Codes

RAI Routing Area Identity

RAT Radio Access Technology

RLC Radio Link Control

RNC Radio Network Controller

RNS Radio Network Subsystem

RTCP Real Time Control Protocol

RTP Real Time Protocol

SCCP Signaling Connection Control Part

SEGW Security Gate Way

SGSN Serving GPRS Support Node

SIM Subscriber Identity Module

SMLC Serving Mobile Location Center

SMS Short Message Service

SNDCP Sub-Network Dependent Convergence Protocol

TBF Temporary Block Flow

TC Transport Channel

TCP Transmission Control Protocol

TFO Tandem Free Operation

TMSI Temporary Mobile Subscriber Identity

TrFO Transcoder Free Operation

TTY Text Telephone or TeletYpewriter

UE User Equipment

UDP User Datagram Protocol

UMTS Universal Mobile Telecommunication System

UTPvAN UMTS terrestrial Radio Access Network

Up Up is the Interface between UE and GANC

VLR Visited Location Register

VPLMN Visited Public Land Mobile Network

While the present invention has been described with reference to many specific details, those skilled in the art will recognize that the present invention may be embodied in other specific forms without departing from the spirit of the invention. For example, certain sequencing and associated attributes of the described procedures may be modified. Accordingly, it will be understood by those skilled in the art that the present invention is not limited by the details set forth above, but rather is defined by the appended claims.

The present invention provides a mechanism for extending a UMA or GAN to interoperate with a GSM core network using a UMTS Iu interface. Specifically, a method for registering a user equipment (UE) in a communication system comprising a licensed wireless communication system and a general access network (GAN) having a general access network controller (GANC) is provided.