Generic access to IU interface

Universal access to ιυ interface

[0001] Rights and Interests Requirements for Related Applications

[0002] This application requires the submission of the title on August 7, 2007^uGeneric Access to the Iulnterfaces-Stage 2 Specification US provisional application 60/954, 549 rights. The application was also submitted on July 14, 2007 with the title^uGeneric Access to the Iu Interface's US non-provisional patent application 11/778,040 (current publication number is No. US 2008-0039086A1) is a partial continuous case. Application 11/778,040 requires the rights of the following applications: U.S. Provisional Application 60/807, 470, filed on July 14, 2006, entitled "E-UMATechnology", and filed on August 21, 2006, entitled "GenericAccess to the Iu" Interface" U.S. Provisional Application 60/823, 092, U.S. Provisional Application entitled "E-UMA-Generic Access to the Iu Interface" filed on October 23, 2006 60/862, 564> and July 13, 2007 U.S. Provisional Application No. 60/949, 826, entitled "Generic Access to the Iu Interface" filed on_OAll of the above applications---namely

The contents of 60/954, 549, 11/77 & 040, 60/807, 470, 60/823, 092, 60/862, 564 and 60/949, 826--- are incorporated herein by reference.

Technical field

[0003] The field of the invention relates generally to telecommunications. More specifically, the present invention relates to improving unlicensed mobile access (UMA) or universal access network (GAN) handover and session establishment.

Background technique

[0004] Authorized wireless systems use wireless transceivers to provide individuals with mobile wireless communications. An authorized wireless system refers to a public cellular telephone system and/or a personal communication service (PCS) telephone system. Wireless transceivers include cellular phones, PCS phones, wireless personal digital assistants, and wireless modems.

[0005] The wireless system is authorized to use the wireless signal frequency authorized by the government. A lot of fees are paid for the access of these frequencies. Expensive base station (BS) facilities are used to support communications on licensed frequencies. Base stations are usually installed about a mile away from each other (for example, a cell tower in a cellular network). The wireless transmission mechanism and frequency adopted by a typical authorized wireless system both limit the data transmission speed and limit the range. As a result, the quality of service (voice quality and data transfer speed) in an authorized wireless system is significantly lower than that provided through a ground line (wired) connection. In this way, users of authorized wireless systems pay relatively high fees for relatively low-quality services.

[0006] Ground line (wired) connections are widely deployed, and higher-quality voice services and higher-speed data services are generally performed at a lower cost. The problem with ground line connections is that they limit the mobility of users. Traditionally, a physical connection to the ground line is required.

[0007] In the past few years, the use of unlicensed wireless communication systems to assist mobile access to terrestrial line-based networks has been rapidly developed. For example, such an unlicensed wireless system can support wireless communication based on the IEEE 802.11a, IEEE 802.11a, or IEEE 802.11g standard (WiFi) or the Bluetooth® standard. The range of movement associated with such systems is usually on the order of 100 meters or less. A typical unlicensed wireless communication system includes a base station that includes a wireless access point (AP) with a physical connection (for example, coaxial cable, twisted pair, or fiber optic cable) to a ground line-based network. The AP has an RF transceiver to assist in communicating with wireless mobile phones that are operable within a moderate distance from the AP.

The data transfer rate supported by the WiFi and Bluetooth® standards is much higher than the data transfer rate supported by the above-mentioned authorized wireless system. Therefore, this option provides a higher quality service at a lower cost, but the service only extends a moderate distance from the base station.

[0008] At present, technology has been developed to integrate the use of authorized and unauthorized wireless systems in a seamless manner, thereby enabling users to access unauthorized wireless systems through a single mobile phone when they are within the range of such systems, while Access an authorized wireless system when it is outside the range of the wireless system.

Summary of the invention

[0009] Some embodiments provide a method and technique for explicitly indicating the initiation of a communication session within an unlicensed mobile access (UMA) network or a universal access network (GAN). In order to help explicitly indicate the start of a communication session, some embodiments use a new message (ie, GA-RRC INITIAL DIRECT TRANSFER (GA-RRC initial direct transfer) message) to replace the user equipment (UE) and UMA network or The first DIRECT TRANSFER message exchanged between GAN's network controllers. In some embodiments, the GA-RRC INITIAL DIRECT TRANSFER message includes an intra-domain NAS node selector (IDNNS), which is to be used by the UMA network or GAN network controller to establish and route the signaling connection to the indicated core network domain Core network node.

[0010] Some embodiments provide a method and technique to activate a communication channel before performing a handover from a first authorized wireless communication network to a UMA network or GAN. In this way, while minimizing the delay caused by the handover by performing the channel activation process before the handover, some embodiments perform a more efficient and seamless handover from the authorized wireless network.

[0011] In some such embodiments, the network controller of the UMA network or GAN performs early communication channel establishment when receiving a relocation request message from the core network. Specifically, the relocation request message contains the identification parameters (for example, IMSI) of the UE, and the UE triggers the channel activation process between the UE and the network controller before the session is switched to the UMA network or GAN. In some embodiments, the channel activation process includes passing an activation channel message from the network controller to the UE. The UE responds with the activation channel confirmation message, and the network controller responds with the activation channel completion message when receiving the activation channel confirmation message. At this stage, the channel between the UE and the network controller is activated. After the channel activation process, the UE submits a relocation complete message to the network controller, and the call is switched to the UMA network or GAN.

[0012] In some embodiments, the channel activation process includes passing a relocation request message from the network to the UE. The UE responds to the network controller with a relocation request confirmation message. At this time, the channel between the UE and the network controller is activated.

Description of the drawings

[0013] The novel features of the invention are set forth in the appended claims. However, for the purpose of explanation, several embodiments of the present invention are set forth in the following drawings.

[0014] FIG. 1 shows an integrated communication system (ICS) of some embodiments.

[0015] FIG. 2 shows several applications of ICS in some embodiments.

[0016] FIG. 3 shows the overall A/Gb mode GAN functional architecture of some embodiments.

[0017] FIG. 4 shows the GAN functional architecture of the overall Iu mode of some embodiments.

[0018] FIG. 5 shows the basic elements of a Femtocell system architecture with a core network-oriented Iu interface based on an asynchronous transfer mode in some embodiments.

[0019] FIG. 6 shows the basic elements of a femtocell system architecture with a core network-oriented Iu interface based on IP in some embodiments.

[0020] FIG. 7 shows a CS domain control plane architecture of some embodiments.

[0021] FIG. 8 shows a CS domain control plane architecture of some embodiments.

[0022] FIG. 9 shows a CS domain control plane architecture of some embodiments.

[0023] FIG. 10 shows a UE CS domain control plane architecture of some embodiments.

[0024] FIG. 11 shows a CS domain user plane protocol architecture of some embodiments.

[0025] FIG. 12 shows a CS domain user plane protocol architecture of some embodiments.

[0026] FIG. 13 shows a UE CS domain user plane architecture of some embodiments.

[0027] FIG. 14 shows the PS domain control plane architecture of some embodiments.

[0028] FIG. 15 shows the PS domain control plane architecture of some embodiments.

[0029] FIG. 16 shows a UE PS domain control architecture of some embodiments.

[0030] FIG. 17 shows the PS domain user plane protocol architecture of some embodiments.

[0031] FIG. 18 shows the PS domain user plane protocol architecture of some embodiments.

[0032] FIG. 19 shows the PS domain user plane protocol architecture of some embodiments.

[0033] FIG. 20 shows a UE PS domain user plane architecture of some embodiments.

[0034] FIG. 21 shows a state diagram of universal access in a UE of some embodiments.

[0035] FIG. 22 shows a GAN security mechanism of some embodiments.

[0036] FIG. 23 illustrates the discovery process of some embodiments.

[0037] FIG. 24 illustrates the registration process of some embodiments.

[0038] FIG. 25 illustrates deregistration initiated by the UE in some embodiments.

[0039] FIG. 26 illustrates deregistration initiated by GANC in some embodiments.

[0040] FIG. 27 shows a registration update uplink of some embodiments.

[0041] FIG. 28 shows the registration update downlink of some embodiments.

[0042] FIG. 29 shows a keep-alive process of some embodiments.

[0043] FIG. 30 shows cell broadcast information in some embodiments.

[0044] FIG. 31 shows the GA-CSR connection establishment of some embodiments.

[0045] FIG. 32 shows the GA-CSR connection release of some embodiments.

[0046] FIG. 33 shows safe mode control in some embodiments.

[0047] FIG. 34 shows the signaling from the core network to the UE NAS in some embodiments.

[0048] FIG. 35 shows signaling from the UE to the core network NAS in some embodiments.

[0049] FIG. 36 shows a CS call originating from a mobile device in some embodiments.

[0050] FIG. 37 shows a CS call originating from a mobile device in some embodiments.

[0051] FIG. 38 shows a CS call terminated at a mobile device in some embodiments.

[0052] FIG. 39 shows UE-initiated CS call clearing in some embodiments.

[0053] FIG. 40 shows a CS handover from GERAN to GAN in some embodiments.

[0054] FIG. 41 shows an alternative process performed during GERAN to GAN in some embodiments.

[0055] FIG. 42 shows a CS handover from UTRAN to GAN in some embodiments.

[0056] FIG. 43 shows an alternative process performed during UTRAN to GAN in these embodiments.

[0057] FIG. 44 shows a CS handover from GAN to GERAN in some embodiments.

[0058] FIG. 45 shows a CS handover from GAN to UTRAN in some embodiments.

[0059] FIG. 46 shows the GA-PSR connection establishment of some embodiments.

[0060] FIG. 47 shows the GA-PSR connection release in some embodiments.

[0061] FIG. 48 shows a message flow for PS security mode in some embodiments.

[0062] FIG. 49 shows PS NAS signaling from the core network to the user equipment in some embodiments.

[0063] FIG. 50 shows NAS signaling from the user equipment to the core network in some embodiments.

[0064] FIG. 51 shows the initial activation of the PTC in some embodiments.

[0065] FIG. 52 shows PTC data transfer in some embodiments.

[0066] FIG. 53 shows UE-initiated PTC disabling in some embodiments.

[0067] FIG. 54 shows UE initiated PTC reactivation in some embodiments.

[0068] FIG. 55 shows network initiated PTC disabling in some embodiments.

[0069] FIG. 56 illustrates network-initiated PTC reactivation in some embodiments.

[0070] FIG. 57 shows implicit PTC disabling in some embodiments.

[0071] FIG. 58 shows PDP context activation in some embodiments.

[0072] FIG. 59 shows a network-requested PDP context activation in some embodiments.

[0073] FIG. 60 shows the UTRAN to GAN SRNS relocation preparation phase in some embodiments.

[0074] FIG. 61 shows the UTRAN to GAN SRNS relocation execution phase in some embodiments.

[0075] FIG. 62 shows a GAN to UTRAN SRNS relocation preparation phase in some embodiments.

[0076] FIG. 63 shows the execution phase of GAN to UTRAN SRNS relocation in some embodiments.

[0077] FIG. 64 shows a GAN architecture supporting a CS domain control plane in some embodiments.

[0078] FIG. 65 shows the GAN protocol architecture supporting the CS domain user plane in some embodiments.

[0079] FIG. 66 shows a GAN architecture supporting PS domain control plane in some embodiments.

[0080] FIG. 67 shows a GAN architecture for the PS domain user plane in some embodiments.

[0081] FIG. 68 shows the GA-RC sublayer in the UE in some embodiments.

[0082] FIG. 69 illustrates the successful (and unsuccessful) establishment of a GA-RRC connection when initiated by the UE according to some embodiments.

[0083] FIG. 70 shows the successful establishment of a GA-RRC connection when initiated through the network in some embodiments.

[0084] FIG. 71 shows the release of the logical GA-RRC connection between the UE and the GANC in some embodiments.

[0085] FIG. 72 illustrates the release of the logical GA-RRC connection between the UE and the GANC when initiated by MS or GANC (ie due to abnormal conditions) according to some embodiments.

[0086] FIG. 73 shows a message flow for security mode control in some embodiments.

[0087] FIG. 74 shows signaling from the core network to the UE NAS of some embodiments.

[0088] FIG. 75 shows UE signaling to the core network NAS of some embodiments.

[0089] FIG. 76 shows an alternative embodiment for initial UE signaling to the core network NAS.

[0090] FIG. 77 shows initial UE to core network NAS signaling in the context of a femtocell/home base station system according to some embodiments.

[0091] FIG. 78 shows a CS call process starting from a mobile device in some embodiments.

[0092] FIG. 79 shows an alternative procedure performed during a CS call originating from a mobile device in some embodiments.

[0093] FIG. 80 shows a CS call originating from a mobile device using the above-mentioned explicit start session indication with reference to FIG. 76

Alternative embodiment of the call process.

[0094] FIG. 81 shows a CS call process terminated at a mobile device in some embodiments.

[0095] FIG. 82 illustrates call clearing initiated by the UE in some embodiments.

[0096] FIG. 83 shows CS channel release of some embodiments.

[0097] FIG. 84 shows a CS channel modification process of some embodiments.

[0098] FIG. 85 shows a CS handover process from GERAN to GAN in some embodiments.

[0099] FIG. 86 shows an alternative procedure for CS handover from GERAN to GAN in some embodiments.

[0100] FIG. 87 presents a process for performing channel activation in anticipatory handover to assist in a more seamless handover.

[0101] FIG. 88 shows the CS handover procedure from GERAN to GAN according to the early channel activation procedure described above with reference to FIG. 87.

[0102] FIG. 89 shows an alternative embodiment for CS handover from GERAN to GAN.

[0103] FIG. 90 shows the CS handover process from UTRAN to GAN in some embodiments.

[0104] FIG. 91 shows an alternative procedure for CS handover from UTRAN to GAN using the RRC protocol in some embodiments.

[0105] FIG. 92 shows an alternative embodiment for performing CS handover from UTRAN to GAN using early channel activation.

[0106] FIG. 93 shows a second alternative embodiment for performing CS handover from UTRAN to GAN using early channel activation.

[0107] FIG. 94 shows a CS handover process from GAN to GERAN in some embodiments.

[0108] FIG. 95 shows the CS handover process from GAN to UTRAN in some embodiments.

[0109] FIG. 96 shows an initial activation process of a packet transport channel of some embodiments.

[0110] FIG. 97 shows an alternative embodiment for performing an initial activation process of a packet transport channel.

[0111] FIG. 98 shows the forwarding of GPRS user data packets through the GAN packet transmission channel in some embodiments.

[0112] FIG. 99 shows a situation when the user equipment disables the packet transmission channel after the PTC timer expires in some embodiments.

[0113] FIG. 100 shows an alternative embodiment for a situation when the UE disables the packet transmission channel after the PTC timer expires.

[0114] FIG. 101 shows a situation when a user equipment initiates reactivation of a packet transmission channel in some embodiments.

[0115] FIG. 102 shows a situation when the UE initiates the reactivation of the packet transmission channel in some alternative embodiments.

[0116] FIG. 103 shows a situation when the network initiates the disabling of the packet transmission channel in some embodiments.

[0117] FIG. 104 shows a situation when the network initiates the reactivation of the packet transmission channel in some embodiments.

[0118] FIG. 105 shows the situation of some alternative embodiments when the network initiates the reactivation of the packet transfer channel.

[0119] FIG. 106 shows a process for implicit PTC disabling in some embodiments.

[0120] FIG. 107 shows a successful PDP context activation process initiated by the user equipment in some embodiments.

[0121] FIG. 108 shows the PDP context activation process of a successful network request in some embodiments.

[0122] FIG. 109 shows a successful UE initiated PDP context activation process in some embodiments.

[0123] FIG. 110 shows the preparation phase of PS relocation from UTRAN to GAN according to some embodiments.

[0124] FIG. 111 shows the execution phase of PS relocation.

[0125] FIG. 112 shows the preparation phase of PS relocation from GAN to UTRAN according to some embodiments.

[0126] FIG. 113 shows the execution phase of PS relocation from GAN to UTRAN according to some embodiments.

[0127] FIG. 114 shows the SRNS relocation process from UTRAN to GAN for the UE in the PMM connected state in some embodiments.

[0128] FIG. 115 conceptually illustrates a computer system, and some embodiments of the present invention are implemented by using the computer system.

Detailed ways

[0129] In the following detailed description of the present invention, many details, examples and embodiments of the present invention are set forth and described. However, it is clear and obvious to those skilled in the art that the present invention is not limited to the illustrated embodiments, and the present invention can be practiced without some specific details and examples discussed.

[0130] Throughout the following description, abbreviations commonly used in the telecommunications industry for wireless services are used together with abbreviations specific to the present invention. A list of abbreviations used in this application is included in Part V.

[0131] Some embodiments provide a method and technique for explicitly indicating the start of a communication session in an unlicensed mobile access (UMA) network or a universal access network (GAN). In order to facilitate the explicit indication of the initiation of the communication session, some embodiments use a new message, namely GA-RRC INITIAL DIRECTTRANSFER, to replace the direct transmission message exchanged between the user equipment (UE) and the UMA network or the network controller of the GAN. In some embodiments, the GA-RRC INITIAL DIRECT TRANSFER message includes the intra-domain NAS node selector (IDNNS), which is to be used by the network controller of the UMA network or GAN to access the core network nodes in the indicated core network domain. The signaling connection is established for routing.

[0132] Some embodiments provide a method and technique to activate a communication channel before performing a handover from a first authorized wireless communication network to a UMA network or GAN. In this way, while minimizing the delay caused by the handover by performing the channel activation process before the handover, some embodiments perform a more active and seamless handover from the authorized wireless network.

[0133] In some such embodiments, the network controller of the UMA network or GAN performs early communication channel establishment when receiving a relocation request from the core network. Specifically, the relocation request includes the identification parameters (for example, IMSI) of the UE, and the UE triggers the channel activation process between the UE and the network controller before the session is switched to the UMA network or GAN. In some embodiments, the channel activation process includes passing an activation channel message from the network controller to the UE. The UE responds with an activation channel confirmation message, and the network controller responds with an activation channel completion message when receiving the activation channel confirmation message. At this stage, the channel between the UE and the network controller is activated. After the channel activation process, the UE submits a relocation complete message to the network controller, and the call is switched to the UMA network or GANo

[0134] In some embodiments, the channel activation process includes passing a relocation request message from the network to the UE. The UE responds to the network controller with a relocation request confirmation message. At this time, the channel between the UE and the network controller is activated.

[0135] Several more detailed embodiments of the present invention will be described in sections below. Specifically, Part I describes an overall integrated communication system including some embodiments. After the discussion of Part I, the functional entities of some embodiments in Part II are discussed. Next, Part III describes the control plane architecture and user plane architecture of some embodiments. Part IV then describes the general access network (GAN) security mechanisms of some embodiments.

[0136] Next, Part V describes the high-level processes of some embodiments, such as discovery, registration, authentication, handover, etc. Then, Part VI describes configuration information for some embodiments. Next, the identifier used in GAN is proposed in Part VII. An alternative implementation using the same protocol for both voice and data services is disclosed in Part VIII

example. Following this discussion, a computer system is described in Section IX, and some embodiments of the invention are implemented using the computer system. Finally, Part X lists the abbreviations used.

[0137] I. Overall System

[0138] A. Integrated Communication System (ICS)

[0139] FIG. 1 shows an integrated communication system (ICS) architecture 100 according to some embodiments of the present invention. The ICS architecture 100 enables the user equipment (UE) 102 to access the voice and data network through the authorized air interface 106 or the ICS interface 110 165. The authorized air interface 106 or the ICS interface 110 can alternatively access the components of the mobile core network 165. In some embodiments, the communication session includes voice services, data services, or both.

[0140] The mobile core network 165 includes one or more home location registers (HLR) 150 and a database 145 for user authentication and authorization. Once authorized, the UE 102 can access the voice and data services of the mobile core network 165. In order to provide such services, the mobile core network 165 includes a mobile switching center (MSC) 160 for providing access to voice services. Data services are provided through the Serving GPRS (General Packet Radio Service) Support Node (SGSN) 155 and the gateway (such as the Gateway GPRS Support Node (GGSN) 157).

[0141] The SGSN 155 is generally responsible for transmitting data packets from the GGSN 157 and the user equipment in the geographic service area of the SGSN 155, and transmits the data packets to the GGSN 157 and the user equipment in the geographic service area of the SGSN 155. In addition, the SGSN 155 can perform the following functions: such as mobility management, storage of user profiles, and storage of location information. However, the GGSN 157 facilitates the actual interface from the mobile core network 165 to various external data packet service networks (for example, the public Internet). Since the data packet starting from the user equipment is usually not formed in the format of accessing an external data network, the task of the GGSN 157 is to act as a gateway in such a packet service network. In this way, the GGSN 157 provides for addressing data packets delivered to and from the UE 102 and an external packet service network (not shown). In addition, because the user equipment of the authorized wireless network spans multiple service areas and further multiple SGSNs, the task of the GGSN 157 is to provide a static gateway in the external data network.

[0142] In the described embodiment, the common components for the cellular network 185 based on the UMTS Terrestrial Radio Access Network (UTRAN) are described as including a plurality of base stations called base stations 180 (for simplicity, only one of them is shown) ), these base stations facilitate wireless communication services for each user equipment 102 through each authorized radio link 106 (for example, a wireless link using a radio frequency in the authorized bandwidth). However, those skilled in the art can understand that, in some embodiments, the authorized wireless network may include other authorized wireless networks, such as GSM/EDGE Radio Access Network (GERAN). An example of a system that uses A interface and Gb interface to access GERAN is shown in Figure 3 below.

[0143] The authorized wireless channel 106 may include any UTRAN or GERAN interface protocol that has been defined for voice/data networks (for example, Iu-cs and Iu-ps interfaces for UTRAN or A and Gb interfaces for GERAN). ) Authorized wireless service. The UTRAN 185 generally includes at least one base station 180 and a radio network controller (RNC) 175 for managing a group of base stations 180. Generally, multiple base stations 180 are configured in a cellular configuration (one for each cell) covering a wide service area.

[0144] Each RNC 175 communicates with the components of the core network 165 through a standard radio network controller interface (Iu-cs and Iu-ps interfaces as described in FIG. 1). For example, the RNC 175 communicates with the MSC 160 through the UTRAN Iu-cs interface for circuit-switched voice services. In addition, the RNC 175 communicates with the SGSN 155 via the UTRAN Iu-ps interface for packet data service through the GGSN 157. In addition, those skilled in the art can understand that, in some embodiments, other networks with other standard interfaces may be applied. For example, the base station controller (BSC) is used to replace the RNC 175 in the GERAN network. The base station controller (BSC) transmits voice to the MSC 160 through the A interface, and the BSC uses the Gb interface of the GERAN network.

Transfer data to SGSNo

[0145] In some embodiments of the ICS architecture, the user equipment 102 passes through a second communication network facilitated by the ICS access interface 110 and the universal access network controller (GANC) 120 (also known as the universal network controller or UNC). To use the services of the mobile core network (CN) 165.

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

[0147] The signaling from the UE 102 is transferred to the GANC 120 via the ICS access interface 110. After the GANC120 performs user authentication and authorization, the GANC 120 uses the radio network controller interface to communicate with the components of the mobile core network 165, where the radio network controller interface is the same as or similar to the above-mentioned UTRAN radio network controller interface, and includes UTRAN Iu-cs interface for circuit-switched voice services and UTRAN Iu-ps interface for packet data services (eg (GPRS)). In this way, GANC 120 uses the same or similar interface to the mobile core network as the UTRAN radio network subsystem (for example, base station 180 and RNC 175).

[0148] In some embodiments, one or more of several other interfaces are used to communicate with other system components of the ICS system, where several other interfaces are (1) "Up", (2) "Wm", and (3) "D' / Gr'", "Gn'" and (5) "SI". The "Up" interface is the interface between UE 102 and GANC 120. The "Wm" interface is a standardized interface between the GANC 120 and the authorization, authentication and accounting (AAA) server 170, and the AAA server 170 is used to authenticate and authorize 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 service gateway (eg, GGSN) of the core authorization network. Some embodiments optionally include an "S1" interface. In these embodiments, the "S1" interface provides authorization and authentication from the GANC 120 to the AAA 140 server. In some embodiments, the AAA server 140 supporting the S1 interface and the AAA server 170 supporting the Wm interface may be the same.

[0149] In some embodiments, the UE 102 must register with the GANC 120 before accessing the ICS service. The registration information of some embodiments includes the users international mobile subscriber identity (IMSI), medium access control (MAC) address, and service set identifier (SSID) of the service access point, as well as information from the GSM or UTRAN cell where the UE 102 is located. Cell ID. In some embodiments, the GANC 120 may pass this information to the AAA server 140 to authenticate the user and determine that these services (such as voice and data) are available to the user. If the AAA 140 approves the access, the GANC 120 allows the UE 102 to access the voice and data services of the ICS system.

[0150] The ICS provides these voice and data services to the UE 102 in a seamless manner through the various interfaces described above. In some embodiments, when the UE 102 requests data services, the ICS uses an optional Gn' interface to directly communicate with the GGSN. 157 communication. The Gn' interface enables the GANC 120 to avoid the overhead and delay time associated with communicating with the SGSN 155 through the Iu-ps interface of UTRAN or the Gb interface of the GSM core network before reaching the GGSN 157.

[0151] In some other embodiments, the access point 114 is a femtocell access point (FAP). The FAP provides a short-range authorized wireless communication session 118 that operates independently of the authorized communication session 106. In the case of a femtocell, the user equipment 102 connects to the ICS network through the short-range authorized wireless network 118 created by the FAP 114. Then, the signal from the FAP is transmitted on the broadband IP network 116.

[0152] B. Application of ICS

[0153] ICS provides a scalable and secure interface in the core service network of the mobile communication system. Figure 2 shows some

Several applications of ICS in the embodiment. As shown in the figure, homes, offices, hotspots, hotels, and other public and private places 205 are connected to one or more network controllers 210 via the Internet 215 (GANC 120 as shown in FIG. 1). The network controller is in turn connected to the mobile core network 220 (core network 165 as shown in FIG. 1).

[0154] Figure 2 also shows several user equipment. These user equipment are only examples of user equipment that can be used for each application. Although only one of each type of user equipment is shown in most of the examples, those skilled in the art can understand that other types of user equipment can be used in these examples without departing from the teachings of the present invention. Moreover, although only one of each type of access point, user equipment, or network controller is shown, many such access points, user equipment, or network controllers may be employed in FIG. 2. For example, an access point can be connected to several user equipments, a network controller can be connected to several access points, and several network controllers can be connected to a core network. The following subsections provide several examples of services that can be provided through ICS.

[0155] 1. Wi-Fi

[0156] The Wi-Fi access point 230 enables dual-mode cellular/Wi-Fi UEs 260-265 to receive high-performance and low-cost mobile services within the range of a home, office, or public Wi-Fi network. With dual-mode UEs, users can roam and switch between authorized wireless communication systems and Wi-Fi access, and can receive a consistent set of services as they transition between networks. In some embodiments, each access point establishes a UMA network or GAN service area, where the UMA network or GAN network controller serves one or more such service areas.

[0157] 2. Femtocell

[0158] Femtocells enable user equipment (such as the standard mobile station 270 and wireless computer 275 shown) to receive low-cost services through the FAP 235 using a short-range authorized wireless communication session. In some embodiments, each FAP establishes a GAN's service area, where the GAN's network controller serves one or more such service areas. It is obvious to those skilled in the art that the home base station provides similar functions for the nodes of the FAP 235. Specifically, a home base station (HNB) provides a standard radio interface for user equipment connectivity, where the radio interface operates independently of authorized communication sessions. The HNB creates a short-range wireless service area to facilitate wireless communication sessions with one or more UEs. The signal from HNB is then transmitted on the broadband IP network. The HNB supports functions similar to the RNC and works on the Iu-h interface, which supports the relay of RANAP signaling between the core network and the home base station access network. In some embodiments, each FAP/HNB establishes a GAN service area, where the GAN's network controller serves one or more such service areas.

[0159] 3. Terminal Adapter

[0160] The terminal adapter 240 allows to join fixed terminal devices, such as telephone 245, fax 250, and other ICS devices that do not implement wireless. As long as the user is connected, the service behaves as a standard analog fixed telephone line. This service is delivered in a similar way to other fixed line VoIP services, where the UE is connected to the user's existing broadband (eg Internet) service.

[0161] 4. WiMAX

[0162] Some authorized wireless communication system operators are studying the deployment of WiMAX networks in parallel with their existing cellular networks. Dual-mode cellular/WiMAX UE 290 enables users to seamlessly transition between cellular networks and such WiMAX networks. [0163] 5. Soft Mobility (SoftMob Subscriptions)

[0164] Broadband access and Wi-Fi hotspots that connect laptop computers 280 to hotels have become popular, especially for international business travelers. In addition, many tourists started to use their laptop computers and broadband connections for voice communication purposes. Instead of using mobile phones to make calls and pay considerable roaming charges, they use soft mobile (or soft phones) and VoIP services when making long-distance calls.

[0165] In order to use the soft mobile service, users need to embed a USB memory stick 285 with an embedded SIM into the USB port of their laptop 280. Soft mobile customers will automatically start and connect to the mobile service provider via IP. From then on, the user will be able to make and receive mobile calls as if she were in her home calling area.

[0166] Several examples of integrated communication systems (ICS) are given in the following subsections. Those of ordinary skill in the art will understand that the teachings in these examples can be easily combined. For example, an ICS may be an IP-based system with an A/Gb interface facing the core network, while another ICS may have a similar IP-based system with an Iu interface facing the core network.

[0167] C. Integrated system with core network-oriented A/Gb interface and/or Iu interface

[0168] FIG. 3 shows a functional architecture of a general access network (GAN) in A/Gb mode of some embodiments. The GAN includes one or more general access network controllers (GANC) 310 and one or more general IP access networks 315. One or more UEs 305 (one UE is shown for simplicity) may be connected to the GANC 310 through a general IP access network 315. The GANC 310 has the ability to appear to the core network 325 as a GSM/EDGE radio access network (GERAN) base station controller (BSC). The GANC 310 includes a security gateway (SEGW) 320 that terminates the secure remote access tunnel from the UE 305, and provides mutual authentication, encryption, and data integrity for signaling, voice, and data services.

[0169] The universal IP access network 315 provides connectivity between the UE 305 and the GANC 310. The IP transport connection extends from the GANC 310 to the UE 305. A separate interface, namely the Up interface, is defined between the GANC 310 and the UE 305.

[0170] GAN and GERAN coexist and maintain the interconnection with the core network (CN) 325 through standardized interfaces defined for GERAN. These standardized interfaces include: the A interface to the Mobile Switching Center (MSC) 330 for circuit-switched services, the Gb interface to the Serving GPRS Support Node (SGSN) 335 for the packet-switched services, and the service to support location services. The Lb interface of the Mobile Positioning Center (SMLC) 350 and the interface to the Cell Broadcast Center (CBC) 355 for supporting cell broadcast services. Provide transaction control (for example, connection management CC and session management SM) and user services through the core network (for example, MSC/VLR and SGSN/GGSN).

[0171] As shown in the figure, the SEGW 320 is connected to the AAA server 340 through the Wm interface. The AAA server 340 is used to authenticate the UE 305 when it sets up a secure tunnel. Some embodiments only require a subset of Wm functionality for GAN applications. In these embodiments, the GANC-SEGW should at least support the Wm authentication process.

[0172] FIG. 4 shows the functional architecture of a general access network (GAN) in Iu mode of some embodiments. The GAN includes one or more general access network controllers (GANC) 410 and one or more general IP access networks 415. One or more UEs 405 (one UE is shown for simplicity) may be connected to the GANC 410 through a general IP access network 415. Compared with the GANC 310, the GANC 410 has the ability to appear to the core network 425 as a UMTS Terrestrial Radio Access Network (UTRAN) Radio Network Controller (RNC). In some embodiments, GANC has extended performance: supports Iu and A/Gb interfaces to support both Iu mode and A/Gb mode UEo. Similar to GANC 310, GANC 410 includes termination of secure remote from UE 405 The security gateway (SEGW) 420 of the access tunnel provides mutual authentication, encryption and data integrity for signaling, voice and data services.

[0173] The universal IP access network 415 provides connectivity between the UE 405 and the GANC 410. The IP transport connection extends from the GANC 410 to the UE 405. A separate interface is defined between the GANC 410 and the UE 405, that is, the Up interface. This interface increases the functionality below T, and supports the Iu mode GAN service through the Up interface shown in Figure 3.

[0174] GAN and UTRAN coexist, and maintain the interconnection with the core network (CN) 425 through standardized interfaces defined for UTRAN. These standardized interfaces include: Iu-cs interface to Mobile Switching Center (MSC) 430 for circuit-switched services, Iu-ps interface to Serving GPRS Support Node (SGSN) 435 for packet-switched services, to Iu-ps interface to support positioning service

Service Mobile Positioning Center (Iu-pc interface of SMLO450, and Iu-bs interface to Cell Broadcast Center (CBC) 455 used to support cell broadcast services. Provided via core network (for example, MSC/VLR and SGSN/GGSN) Transaction control (for example, connection management CC and session management SM) and user services.

[0175] As shown in the figure, the SEGW 420 is connected to the AAA server 440 through the Wm interface. The AAA server 440 is used to authenticate the UE 405 when it sets up a secure tunnel. Some embodiments only require a subset of Wm functionality for GAN applications in Iu mode. In these embodiments, the GANC-SEGW should at least support the Wm authentication process.

[0176] D. ATM and IP-based architecture

[0177] In some embodiments, the system uses an asynchronous transfer mode (ATM)-based Iu (Iu-cs and Iu-ps) interface for CN. In some embodiments, the system architecture may also support CN-oriented Iu (Iu-cs and Iu-ps) interfaces based on IP. The following two subsections describe examples of these architectures for femtocells.

[0178] Those of ordinary skill in the art will understand that the same example can be easily applied to other types of ICS_OFor example, these instances can be used when the ICS access interface 110 (shown in Figure 1) uses an unlicensed frequency (rather than the licensed frequency of femtocells), and the access point 114 is a general WiFi access point (rather than FAP). )Wait. Moreover, those of ordinary skill in the art will understand that the same example can be easily implemented using the A/Gb interface (described above) instead of the Iu interface.

[0179] FIG. 5 shows the basic elements of a Femtocell system architecture with a CN-oriented Iu (Iu-cs and Iu-ps) interface based on Asynchronous Transfer Mode (ATM) 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.

[0180] For simplicity, only one UE and one FAP are shown. However, each GANC can support multiple FAPs, and each FAP in turn can support multiple UEs. As shown in the figure, the GANC 515 includes an IP network controller (INC) 525, a GANC security gateway (SeGW) 530, a GANC signaling gateway 535, and a GANC media gateway (MGW) 540>ATM gateway (545). The components of the femtocell are further described below.

[0181] FIG. 6 shows the basic elements of a femtocell system architecture with a CN-oriented IP-based Iu (Iu-cs and Iu-ps) interface in some embodiments. For simplicity, only one UE and one FAP are shown. However, each GANC can support multiple FAPs, and each FAP in turn can support multiple UEs. This selection does not require the GANC signaling gateway 535 and the ATM gateway 545. Optionally, for the IP-based Iu interface, if the R4MGW 605 in the CN can support voice data (that is, in IETF RFC3267-Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", "RFC 3267" defined in the RTP frame) termination, the GANC media gateway 540 can also be omitted.

[0182] FIGS. 5 and 6 also show the components of the authorized wireless communication system. These components are 3G MSC 550, 3G SGSN 555, and (shown together) other core network systems 565. 3G MSC 550 provides a standard Iu-cs interface for GANC. Another alternative to MSC is shown in FIG. 6. As shown in the figure, MSC 650 is divided into MSS (MSC server) 675 for Iu-cs based signaling and MGW 680 for bearer path. R4MSC 650 is a release 4 version of 3G MSC, with different architectures, that is, R4MSC is divided into MSS used to control traffic and MGW used to handle bearers. A similar MSC can be used in the ATM architecture of Figure 5. The two architectures shown in Figure 5 and Figure 6 are also suitable for using any future version of MSCo

[0183] The 3G SGSN 555 provides packet service (PS) through a standard Iu-ps interface. The SGSN is connected to INC 525 for signaling and SeGW 530 for PS data. The AAA server 560 communicates with the SeGW 530 and supports the Wm connection

EAP-AKA and EAP-SIM procedures used in IKEv2 on the mouth, and include the MAP interface to HLR/AuC. In some embodiments, the system also supports an enhanced service access control function on the S1 interface.

[0184] II. Functional entity

[0185] A. User Equipment

[0186] The user equipment (UE) 405 includes functions required to access the GAN in the Iu mode. In some embodiments, the UE additionally includes functions required to access the A/Gb mode GAN. In some embodiments, the UE 305 is a dual-mode (for example, GSM and unlicensed radio equipment) mobile phone device, which has the ability to switch between the two modes. The user equipment can 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 along the way to the UE. In some other embodiments, the UE 305 is a standard 3G mobile phone device that operates on the provider's licensed spectrum.

[0187] In some embodiments, the user equipment includes a cell phone, a smart phone, a personal digital assistant, or a computer equipped with a subscriber identity mobile (SIM) card for communicating on authorized or unauthorized wireless networks. In addition, in some embodiments, a computer equipped with a SIM card communicates through a wired communication network.

[0188] Alternatively, in some embodiments, the user equipment includes a fixed wireless device, providing a set of integrated services digital network (ISDN) terminals, session initiation protocol (SIP) terminals or plain old telephone service (POTS) ) The terminal is connected to the terminal adapter function of ICS. Even for user locations that are not fully covered by an authorized wireless network, the application of this type of device of the present invention enables wireless service providers to provide users with so-called land line replacement services. In addition, although alternative embodiments of the terminal adapter provide wireless equivalent functionality for connection through an unauthorized or authorized wireless network, some embodiments of the terminal adapter are fixed wired devices for connecting ISDN.SIP or POTS terminals are connected to different communication networks (for example, IP networks).

[0189] B. General Access Network Controller (GANC)

[0190] The core network 425 interacts with the GANC 410 as if it is an RNC. The universal IP access network 415 provides connectivity between the GANC 410 and the UE 405. The GANC 410 entity uses the functionality of the control plane and the user plane to interact between the Iu interface and the general IP access network. The functionality of the control plane is used for call control signaling, and the functionality of the user plane is used for information transmission (such as voice or data). In some embodiments, GANC has the ability to expand to also interact with the GERANA/Gb interface.

[0191] Some embodiments of the above-mentioned devices (such as user equipment, FAP or GANC) include electronic components such as a microprocessor and a memory (not shown) that will be used for execution to manage voice and The computer program instructions of the wireless protocol for data services are stored in a machine-readable or computer-readable medium, as further described in the section labeled "computer system" below. Examples of machine-readable media or computer-readable media include, but are not limited to: magnetic media, such as hard disks, memory modules, and magnetic tapes; optical media, such as CD-ROMS and holographic devices; magneto-optical media, such as optical disks; and specially configured to store And hardware devices that execute program codes, such as application-specific integrated circuits (ASIC), programmable logic devices (PLD), ROM, and RAM devices. Examples of computer programs or computer codes include, for example, machine codes generated by a compiler, and files containing high-level codes executed by computers, electronic components, or microprocessors using an interpreter.

[0192] III. Control Plane and User Plane Architecture

[0193] 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 some embodiments of the control plane and user plane architectures for the circuit switched (CS) domain and the packet switched (PS) domain.

[0194] A. Circuit Switched (CS) Domain

[0195] 1. CS Domain-Control Plane

[0196] FIG. 7 shows a GAN architecture supporting a CS domain control plane according to some embodiments. The figure shows different protocol layers for UE 705, general IP network 710, GANC 715 and MSC 720. Figure 7 also shows two interfaces Up 725 and Iu-cs 730. The main features of GAN's CS domain control plane architecture are as follows: The following access layer 735 and transport IP layer 740 provide general IP connectivity between UE 705 and GANC 715. The IPSec layer 745 provides encryption and data integrity between UE 705 and GANC 715. The remote IP layer 750 is the "internal" IP layer for the IPSec tunnel mode, and the UE 705 uses this layer to be addressed by the GANC715. The remote IP layer 750 is configured during the establishment of the IPSec connection.

[0197] In some embodiments, a separate TCP connection is used to reliably transmit GA-RC and GA-CSR signaling between the UE 705 and the GANC 715. The TCP connection is managed through GA-RC and transmitted using the remote IP layer. Non-Access Stratum (NAS) protocols (such as MM 760 and above) are transparently transmitted between UE 705 and MSC 720. The General Access Resource Control (GA-RC) protocol manages the Up session, including the GAN discovery and registration process. The GA-RC protocol (described in Generic access to the A/Gb interface; Stage 2", 3GPP TS 43. 318 standard & 1.4 item) was expanded to include GANO that supports the selection of A/Gb mode or Iu mode

[0198] The General Access Circuit Switched Resource (GA-CSR) protocol supports UMTS dedicated requirements and GERAN dedicated requirements. GANC 715 terminates the GA-CSR protocol and interacts with the RANAP 755 protocol on the Iu-cs 730 interface. In some embodiments, the Iu-cs signaling transport layer 765 is based on the UTRAN Iu interface signaling transport" 3GPP TS 25.412 standard, hereinafter referred to as "3GPPTS 25.412".

[0199] a) Alternative architecture for CS domain-control plane

[0200] The embodiment shown in FIG. 7 is only an alternative solution for implementing the CS domain control plane architecture. In the CS domain control plane architecture, the UE 705 and the general IP network 710 are used to use the GANC 715 The user of the UE is connected to the MSC 720. Those of ordinary skill in the art will understand that the teachings of the present invention can be applied to other user equipment and access points (such as the user equipment and access points described in FIG. 2).

[0201] For example, FIG. 8 shows the CS domain control plane architecture of some embodiments. As shown in the figure, the GANC and MSC in Figure 8 are similar to the GANC and MSC in Figure 7. In Figure 8, the local node where the user is located is represented as an unknown box (referred to as the local node 805). Different embodiments use different devices to connect the user located in the local node 805 and the MSC 720 through the GANC 715. For example, in the embodiment shown in FIG. 7, the UE 705 and the general IP network 710 are used. FIG. 9 shows another embodiment in which a UE 905, a Femtocell Access Point (FAP) 910, and a general IP network 915 are used to connect the local node 805 and the MSC 720 through the GANC 715.

[0202] As shown in the figure, the protocol layers of the GANC 880-885 are communicatively coupled with their corresponding layers in the general IP network 915 (respectively shown by arrows 845-850). Likewise, GANC layers 855-875 are communicatively coupled with their corresponding layers in FAP 910 (shown by arrows 820-840, respectively). Moreover, the MM layer 890 and the CC/CS/SMS layer 895 of the MSC 720 are transparently connected to their corresponding layers in the UE 905 (shown by arrows 810-815, respectively). Using this technology, a FAP similar to the FAP 235 shown in FIG. 2 can be used to connect a UE (such as the UE 270-UE 275) to the wireless core network 220 through the network controller 210. Those of ordinary skill in the art will be able to apply the techniques shown in Figures 8 and 9 to communicatively couple any user equipment, access points, terminal adapters, soft mobiles, etc. (those devices shown in Figure 2) to use The integrated communication system (ICS) of the multi-layer CS domain control architecture shown in Figure 7.

[0203] b) CS domain-control plane-UE architecture

[0204] FIG. 10 shows the UE architecture for the CS domain control plane. As shown in the figure, the architecture includes GAN supporting GERAN, UTRAN, and A/Gb mode and GAN in Iu mode. The main structure of the UE CS domain control plane architecture shown in Figure 10

The main features are as follows: The GERANRR-SAP interface 1015 to the GSM-MM layer 1005 remains the same for GERAN and A/Gb mode GAN access. Likewise, the UTRAN SAP interface 1020 to the GSM-MM layer 1005 remains the same for GAN access in UTRAN and Iu modes. The access mode converter 1010 is set to switch between the GAN mode of the GERAN/UTRAN.A/GB mode and the GAN mode of the Iu mode. GA-CSR/GA-RC 1025 is directly peered with UTRAN RRC 1030 and GERAN RRC 1035 layers to provide coordination for roaming and handover. As shown in Figure 10, GA-CSR/GA-RC 1025, UTRAN RRC 1030, and GERAN RRC 1035 interface through a set of service access interfaces (SAP) 1040.

[0205] 2. CS Domain-User Plane

[0206] FIG. 11 shows a GAN protocol architecture supporting a CS domain user plane in some embodiments. The figure shows different protocol layers for UE 1105, general IP network 1110, GANC 1115 and MSC 1120. Figure 11 also shows the main features of the CS domain user plane architecture of the two interfaces Up 1125 and Iu-cs 1130o GAN as follows: The following access layer 1135 and transport IP layer 1140 provide common IP between UE 1105 and GANC 1115 Connectivity. The IPSec layer 1145 provides encryption and data integrity. The CS user plane data transmission of the Up interface 1125± is the same as the CS user plane used for A/Gb mode GAN (ie, using real-time protocol, RTP, according to IETF RFC 3267). GANC 1115 enables the CS domain user plane to interact between RTP/UDP and the Iu user plane (Iu-UP) protocol of the Iu-cs interface 1130±. In some embodiments, the Iu-cs data transport layer 1165 is based on the 3GPP TS 25.414 standard.

[0207] Those of ordinary skill in the art will understand that other user equipment, access points, terminal adapters, soft mobiles, etc. can be connected to the core network through the GANC. For example, FIG. 12 shows the CS domain and user plane protocol architecture of UE 1205, femtocell access point (FAP) 1210, and general IP network 1215. Using the technology described in conjunction with FIG. 8 and FIG. 9, those of ordinary skill in the art can use UE 1205, FAP1210 and general IP network 1215 to replace UE 1105 and general IP network 1110 shown in FIG. The cellular UE 1205 is connected to the core network. Similarly, other types of UEs, access points, terminal adapters, soft mobility, etc. can be connected to the core network through GANC.

[0208] a) CS domain-user plane-UE architecture

[0209] FIG. 13 shows a UE architecture for the CS domain user plane in some embodiments. As shown in the figure, the architecture includes GAN 1305 supporting A/Gb mode and Iu mode, as well as GERAN 1310 and UTRAN 1315. The RFC 3267 AMR processing layer 1320 is used to connect the GAN RTP/UDP/IP layer 1323 to the AMR audio processing layer 1330 through the CS user plane routing service layer 1335, where the CS user plane routing service layer 1335 routes the CS user plane data to the selected The access network may be routed from the selected access network, where the access network is GERAN, UTRAN or GAN. The RFC 3267 AMR processing layer 1320 is not used when it is connected to the CS data processing layer 1340, that is, in the case of circuit-switched data that is the opposite of circuit-switched voice.

[0210] B. Packet Switching (PS) Domain

[0211] 1. PS Domain-Control Plane

[0212] FIG. 14 shows the GAN architecture supporting the PS domain control plane. The figure shows the different protocol layers used for UE 1405, general IP network 1410, GANC 1415 and SGSN 1420. Figure 14 also shows two interfaces Up 1425 and Iu-ps 1430. The main features of the PS domain control plane architecture of the GAN shown in Figure 14 are as follows: The following access layer 1435 and transport IP layer 1440 provide UE 1405 and GANC Universal connectivity between 1415. The IPSec layer 1445 provides encryption and data integrity. TCP 1450 provides reliable transmission of GA-PSR between UE1405 and GANC 1415. GA-RC manages the IP connection, including the GAN registration process. The General Access Packet Switching Resource (GA-PSR) protocol supports UMTS specific requirements. GANC 1415 terminates the GA-PSR protocol, and interacts with the RANAP protocol 1455 on the Iu-ps interface 1430. For example, the NAS protocol 1460 used for GMM, SM, and SMS is transparently transmitted between UE 1405 and SGSN 1420.

Fortunately, the Iu-ps signaling transport layer 1465 is based on 3GPP TS 25.412.

[0213] Those of ordinary skill in the art will understand that other user equipment, access points, terminal adapters, soft mobility, etc. can be connected to the core network through the GANC. For example, FIG. 15 shows the PS domain control plane protocol architecture of UE 1505, femtocell access point (FAP) 1510, and general IP network 1515. Using the technology described in conjunction with FIG. 8 and FIG. 9, a person of ordinary skill in the art can use UE 1505, FAP 1510, and general IP network 1515 to replace the UE 1405 and general IP network 1410 shown in FIG. The UE 1505 of the pico cell is connected to the core network. Similarly, other types of UEs, access points, terminal adapters, soft mobility, etc. can be connected to the core network through GANC.

[0214] a) PS domain-control plane-UE architecture

[0215] FIG. 16 shows a UE architecture for the PS domain control plane of some embodiments. As shown in the figure, the architecture includes GAN supporting A/Gb mode and Iu mode, as well as GERAN and UTRAN. The main features of the UE PS domain control plane architecture shown in Figure 16 are as follows: The GERANGRR-SAP interface 1615 and GERAN GMMRR-SAP interface 1617 to the GMM layer 1605 remain the same for GERAN and A/Gb mode GAN access. Similarly, the UTRAN RABMAS-SAP interface 1620 and the UTRAN GMMAS-SAP interface 1622 to the GMM layer 1605 remain the same for GAN access in UTRAN and Iu modes. The access mode converter 1610 is set to switch between GERAN/UTRAN, A/GB mode GAN and Iu mode GAN mode. GA-PSR/GA-RC 1625 is directly peered with UTRAN RRC1630 and GERAN RRC 1635 layers to provide coordination for roaming and handover. As shown in Figure 16, GA-PSR/GA-RC 1625> UTRAN RRC 1630 and GERAN RRC 1635 interface through a set of service access interfaces (SAP) 1640.

[0216] 2. PS Domain-User Plane

[0217] FIG. 17 shows a GAN architecture for the PS domain user plane in some embodiments. The figure shows the different protocol layers used for UE 1705, general IP network 1710, GANC 1715 and SGSN 1720. Figure 17 also shows two interfaces Up 1725 and Iu-ps 1730. The main features of the PS domain user plane architecture of the GAN shown in Figure 17 are as follows: The following access layer 1735 and transport IP layer 1740 provide UE 1705 and GANC Universal connectivity between 1715. The IPSec layer 1745 provides encryption and data integrity.

[0218] GA-PSR is extended to include supporting GTP-U G-PDU message format instead of LLC PDU in GAN as in A/Gb mode to transmit PS user data (for example, IP packets). As shown in Figure 17, the user data in the GTP-U G-PDU message can be transparently transferred between the UE 1705 and the core network through the SGSN to the GGSN. In some embodiments, the Iu-ps data transmission lower layer 1765 is based on the 3GPP TS25.414 standard.

[0219] FIG. 18 shows an alternative GAN PS domain user plane configuration supported by the Up interface procedure of some embodiments. In this configuration, the GANC 1815 terminates the GTP-U tunnel with the Up interface of the UE 1805, and also terminates the independent Iu-ps GTP-U tunnel to the SGSN 1820. GANC 1815 relays the PS user data between the GTP-U tunnel of the Up interface and the GTP-U tunnel of the related Iu-ps interface, so that the PS user data can flow between the UE and the SGSN.

[0220] This configuration minimizes the number of active GTP-U "paths" that exist in the core network, that is, the SGSN can be limited to the number of RNCs with which the SGSN can exchange PS user data at the same time (for example, today, There can be no more than 4096 RNCs in a given PLMN). For example, if there is no software upgrade, if the GTP-U tunnel is from the UE to the SGSN, it may not be able to support simultaneous communication with hundreds of thousands of UEs on demand. Terminating the Iu-ps GTP-U tunnel on the GANC avoids this potential SGSN restriction. In some embodiments, the Iu-ps data transmission lower layer 1865 is based on the 3GPP TS 25.414 standard.

[0221] Those of ordinary skill in the art will understand that other user equipment, access points, terminal adapters, soft mobility, etc.

It can be connected to the core network through GANC. For example, FIG. 19 shows the PS domain and user plane protocol architecture of UE 1905, femtocell access point (FAP) 1910, and general IP network 1915. Using the technology described in conjunction with FIG. 8 and FIG. 9, those of ordinary skill in the art can use UE 1905.FAP1910 and general IP network 1915 to replace UE 1805 and general IP network 1810 shown in FIG. The cellular UE 1905 is connected to the core network. Similarly, other types of UEs, access points, terminal adapters, soft mobility, etc. can be connected to the core network through GANC.

[0222] a) PS domain-user plane-UE architecture

[0223] FIG. 20 shows a UE architecture for the PS domain user plane in some embodiments. As shown in the figure, the architecture includes GAN 2005 that supports A/Gb mode and Iu mode, as well as GERAN 2010 and UTRAN 2015. The access mode converter 2020 is set to switch between GERAN/UTRAN, A/GB mode GAN and Iu mode GAN mode.

[0224] C. GA-RC (General Access Resource Control)

[0225] The GA-RC protocol provides a resource management layer, which has the following functions: discovering and registering with the GANC, updating the GANC registration, keeping the GANC active at the application layer, and supporting the identification of APs used for GAN access.

[0226] 1. GA-RC sublayer status

[0227] FIG. 21 shows a state diagram of universal access in the UE in some embodiments. As shown in the figure, the GA-RC sublayer in the UE can be in one of two states: GA-RC-DEREGISTERED (GA-RC has been deregistered) 2105 or GA-RC-REGISTERED (GA-RC has been registered) 2110. When the service RR is switched to GAN in Iu mode (shown by arrow 2112), the following results are possible: Transition to GA-CSR-IDLE (GA-CSR idle) 2115 and GA-PSR-IDLE (GA-PSR idle) ) 2120 (ie, if the UE is idle during the transition period); (2) Transition to GA-CSR-CONNECTED (GA-CSR connected) 2125 and GA-PSR-IDLE (GA-PSR idle) 2130 (ie, due to CS switching (Or relocation); (3) Transition to GA-CSR-IDLE (GA-CSR idle) 2115 and GA-PSR-CONNECTED (GA-PSR connected) 2130 (ie, due to PS switching or relocation); (4) Transition to GA-CSR-CONNECTED (GA-CSR is connected) 2125 and GA-PSR-CONNECTED (GA-PSR-CONNECTED) 2130 (That is, due to dual transfer mode switching or CS+PS relocation). The transition of the serving RR from GAN to GERAN/UTRAN RRC (shown by arrow 2135) can occur when the UE is in any combination of GA-CSR and GA-PSR states.

[0228] In the GA-RC-DEREGISTERED state 2105, the UE may be located in the area covered by the GAN; but the UE has not successfully registered with the GANC. When in the GA-RC-DEREGISTERED state 2105, the UE can initiate GAN registration. When the TCP or IPSec connection is lost or when the GAN deregistration process is performed, the UE returns to the GA-RC-DEREGISTERED status 2105ο

[0229] In the GA-RC-REGISTERED state 2110, the UE registers with the serving GANC. The UE has an IPSec tunnel and a TCP connection established to the serving GANC. Through the IPSec tunnel and TCP connection, the UE can exchange GA-RC, GA-CSR, and GA-PSR signaling messages with the GANC.

[0230] When the UE remains in the GA-RC-REGISTERED state 2110, the UE executes the application layer to remain active for the GANC. In the GA-RC-REGISTERED state 2110, the UE can be in UTRAN/GERAN mode or GAN mode. The UE can be (1) located in GERAN or UTRAN and idle; (2) activated in GERAN or UTRAN (for example, a GSM RR or UTRAN RRC connection can be established); (3) has "roamed" into GAN mode; or recently "roamed" Out" GAN mode (for example, due to switching from GAN).

[0231] D. GA-CSR (Common Access Circuit Switching Resource)

[0232] The GA-CSR protocol provides a circuit-switched service resource management layer, which supports the following functions: (1) Establish a CS service transmission channel between UE and GANC; (2) CS handover support between UTRAN/GERAN and GAN; (3) UE and core

NAS is directly transmitted between networks; and (4) other functions such as CS paging and security configuration.

[0233] 1. GA-CSR sublayer status

[0234] The GA-CSR sublayer in the UE can be in two states, GA-CSRTDLE or GA-CSR-CONNECTED, as shown in FIG. 21. When the UE switches the serving RR entity to GAN, the UE enters the GA-CSR-IDLE state 2115. This switching occurs only when the GA-RC is in the GA-RC-REGISTERED state 2110.

[0235] When the GA-CSR connection is established, the UE transitions from the GA-CSR-IDLE state 2115 to the GA-CSR-CONNECTED state 2125, and when the GA-CSR connection is released, the UE returns to the GA-CSR-IDLE state 2115. After the GA-CSR connection is released, an indication that no dedicated CS resource exists is passed to the upper layer. When the handover to the GAN is being performed, the UE can also enter the GA-CSR-CONNECTED state 2125 when it is in the GA-RC-REGISTERED state 2110 in the GERAN/UTRAN mode. Similarly, when the handover from the GAN is successfully performed, the UE enters the GA-RC-REGISTERED state 2110 in the GERAN/UTRAN mode from the GA-CSR-CONNECTED state 2125.

[0236] E. GA-PSR (General Access Packet Switching Resource)

[0237] The GA-PSR protocol provides a packet-switched service resource management layer that supports the following functions: (1) Set up a PS service transmission channel between the UE and the network; (2) Support PS relocation/switching between UTRAN/GERAN and GAN directly transmit NAS messages between UE and PS core network; (4) transmit GPRS user plane data; and (5) other functions, such as PS paging and security configuration.

[0238] 1. The status of the GA-PSR sublayer

[0239] The GA-PSR sublayer in the UE can be in two states: GA-PSR-IDLE or GA-PSR-CONNECTED, as shown in FIG. 21. When the UE switches the serving RR entity to GAN, the UE enters the GA-PSR-IDLE state 2120. This transition only occurs when GA-RC is in the GA-RC-REGISTERED state 2110. When the GA-PSR connection is established, the UE transitions from the GA-PSR-IDLE state 2120 to the GA-PSR-CONNECTED state 2130, and when the GA-PSR connection is released, the UE returns to the GA-PSR-IDLE state 2120. After the GA-PSR connection is released, the indication that there is no dedicated resource is passed to the upper layer. [0240] When the handover to GAN is being performed, the UE may also enter the GA-PSR-CONNECTED state 2130 when it is in the GA-RC-REGISTERED state 2110 in the GERAN/UTRAN mode. Similarly, when the handover from GAN is successfully performed, the UE enters the GA-RC-REGISTERED state 2110 in the GERAN/UTRAN mode from the GA-PSR-CONNECTED state 2130. The GA-PSR packet transmission channel (GA-PSR) PTC) provides the association between UE and GANC to transmit GPRS user data on the Up interface. This will be described below during PS NAS signaling in the secondary part V.P.

[0241] IV. GAN Security Mechanism

[0242] GAN supports security mechanisms at the different layers and interfaces described in FIG. 22. The security mechanism 2205 on the Up interface protects the control plane and user plane service flows between the UE 2210 and the GANC 2215 from unauthorized use, data manipulation, and eavesdropping, that is, it supports authentication, encryption, and data integrity mechanisms.

[0243] Network access security 2220 includes a mechanism defined in the 3G Security; Security Architecture, 3GPP TS33.102 standard. The mutual authentication between the user and the core network (CN) 2225 takes place between the MSC/VLR or SGSN and the UE, and is transparent to the GANC. However, there is a password binding between UE-CN authentication and UE-GANC authentication to prevent man-in-the-middle attacks.

[0244] Another application-level security mechanism 2230 may be used in the PS domain to ensure end-to-end communication between the UE 2210 and the application server 2235. For example, in some embodiments, the UE 2210 may run the HTTP protocol in the SSL session to ensure web access.

[0245] On the Up interface, all control planes and user planes sent between UE 2210 and GANC 2215

The service is protected by the IPSec tunnel between UE 2210 and GANC-SEGW. The IPSec tunnel uses the same mechanism as specified in "3G security; Wireless Local Area Network (WLAN) interworking security 3GPP TS 33. 234 to provide mutual authentication ( Use USIM credentials), encryption and data integrity.

[0246] As described above (with respect to FIGS. 9, 12, 15 and 19), some embodiments use a femtocell access point (FAP) to communicatively couple the user equipment UE to the GANCo through a general IP network, as shown in FIG. 9 The FAP architecture of the CS control plane has an IPSec layer 920. Similarly, the FAP architecture of the CS user plane, PS control plane, and PS user plane architecture also includes the 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 remote IP layer of GANC, and are communicatively coupled to their corresponding GANC IPSec layer, thereby providing a gap between GANC and FAP Secure link.

[0247] V. Advanced Process

[0248] A. Mode selection in a multimode terminal

[0249] In addition to UTRAN and possible GERAN radio interfaces, a UE capable of universal access can also support any IP access technology. The UE may be in GERAN/UTRAN operation mode or GAN operation mode. The UE can be configured to operate in one of two modes (ie GERAN/UTRAN or GAN) at any given time. There may be a preferred mode of operation, which can be configured by the user or service provider through various mechanisms (such as device management).

[0250] When powering on, the UE always starts in GERAN/UTRAN mode and performs a normal power-on sequence. In some embodiments, the UE performs such as Non-Access-Stratum functions related to MobileStation (MS) in idle mode", the power-on sequence specified in the 3GPP TS 23.122 standard. After that, the UE can be operated according to user preferences or operations. The mode selection preference determined by the configuration of the quotient is switched to the GAN mode.

[0251] The possible various preferences for the UE are as follows: GERAN/UTRAN only, GERAN/UTRAN preferred, GAN preferred, and GAN only in GERAN/UTRAN only, the UE RR entity remains in GERAN/UTRAN only mode without Switch to GAN mode. In the preferred GERAN/UTRAN, as long as there is PLMN available and not prohibited by GERAN/UTRAN, the UERR entity is in GERAN/UTRAN mode. If no permitted PLMN is available through GERAN/UTRAN, and the UE has successfully registered with the GAN through the general IP access network, the UE switches to the GAN mode. When the PLMN becomes available on GERAN/UTRAN and the PLMN is not forbidden, or the UE deregisters on the general IP access network or loses the connection with the GAN, the UE returns to the GERAN/UTRAN mode.

[0252] In the preferred GAN, when the UE has successfully registered with the GAN through the general IP access network, as long as the GAN is available, the UE switches to and remains in the GAN mode. When the UE deregisters, or otherwise loses its connection with the GAN on the general IP access network, the UE switches to GERAN/UTRAN mode.

[0253] In GAN only, the UE transitions to GAN mode (after the initial power-on sequence in the GERAN/UTRAN mode to obtain cellular network information, but excluding the MM and GMM procedures using the GERAN/UTRAN core network) and does not transition To GERAN/UTRAN mode. During the initial power-on sequence in GERAN/UTRAN mode, the UE shall ignore all paging messages received through the GERAN/UTRAN network.

[0254] B. PLMN Selection

[0255] In some embodiments, there is no change from the PLMN selection process in the UE's NAS layer (MM and above), with the exception of the failure of "scanning in the VPLMN background" in the GAN mode. GANC can only connect to one PLMN. The PLMN selection in the NAS layer does not result in a mode change between GERAN/UTRAN mode and GAN mode. For a specific example of PLMN selection, only PLMNs available through GAN or PLMNs available only through GERAN/UTRAN are provided to the NAS layer (ie, there is no combination of PLMNs available through GERAN/UTRAN and GAN).

[0256] In the case of GAN-enabled UEs, some embodiments require the GANC selection process as part of the process of establishing connectivity between the UE and the GANC. This is during GAN registration when UEs that support GAN can be in two or more paired GANC-PLMNs indicated by the default GANC (ie, in the GA-RC REGISTER REDIRECT (GA-RC-REGISTERED) message) Occurs when a selection is made in. The GANC selection process occurs while the UE is still in GERAN/UTRAN mode and before the UE roams in GAN mode. If the currently selected PLMN is available through GAN, it should be selected. If it is not available, the choice of GANC is a unique implementation.

[0257] If the UE does not have any stored information related to the serving GANC of the cell or AP to which the UE is currently connected, the UE attempts to register with the default GANC (always located in HPLMN) stored in the UE. The UE includes an indication for identifying the GANC as the default GANC in the GA-RC REGISTER REQUEST (GA-RC-REGISTERED request) message. [0258] When the UE attempts to register on the default GANC that includes its instruction to be in the automatic PLMN selection mode, one of the following occurs. If the default GANC is determined to serve the UE, the default GANC responds with a GA-RC REGISTER ACCEPT (GA-RC REGISTER acceptance) message. When the default GANC determines to redirect the UE to another GANC in the HPLMN, the default GANC responds with a GA-RC REGISTER REDIRECT message without including the PLMN identification list.

[0259] When the default GANC determines to redirect the UE to a PLMN that is not HPLMN, the default GANC responds with a GA-RC REGISTER REDIRECT message and includes a list of PLMNs that can provide GAN services to the UE at its current location . The list contains one or more PLMN IDs, as well as their related GANC and SEGW node IDs (in IP address or FQDN format). After the GANC selection process, the GA-RC entity in the UE tries to register on the relevant GANC.

[0260] If at any time the user wishes to perform manual PLMN selection or "user reselection" regardless of whether the UE is in manual or automatic PLMN selection mode, the UE will send a GA-RC REGISTERREQUEST message to the default GANC, including It is an indication that it is in manual PLMN selection mode. The default GANC is not allowed to accept registration. It responds with a GA-RC REGISTER REDIRECT message and includes a list of PLMNs that can provide GAN services to the UE at its current location.

[0261] When the UE includes the identifier of the currently served GSM network in the GA-RC REGISTER REQUEST message, the default GANC uses the identifier to identify the PLMN list to send it to the UE in the response message.

[0262] After successfully registering with the service GANC, the UE does not save the PLMN list. The UE does not use the PLMN list provided to the UE during registration for background scanning. UE cannot use GA in VPLMN unless HPLMN supports GA and authorizes GA.

[0263] C. Re-selection between GERAN/UTRAN and GAN modes

[0264] 1. Roaming (from GERAN/UTRAN mode to GAN mode)

[0265] This procedure can be applied only when the GAN service is available and the UE is not in NC2 mode (applicable if the UE is in GERAN mode and as defined by the Radio subsystem link control 3GPP TS 45.008 standard) and has UE preference for "GAN only", "Preferred GAN", or "Preferred GERAN/UTRAN" if no permitted PLMN is available via GERAN/UTRAN.

[0266] After successful GAN registration, the access mode in the UE is switched to GAN mode. The GA-CSR entity in the UE provides the NAS-related system information received during the GAN registration process to the NAS layer. NAS regards the cell identity allocated by GANC as the current serving cell.

[0267] When in GAN mode, the GERAN-RR and UTRAN RRC entities are separated from the RR-SAP in the UE. result,

This entity does not: (1) Notify the NAS about any GERAN/UTRAN cell reselection and/or changes in the system information of the cell currently camped on; (2) Notify the NAS about any newly discovered PLMN on GERAN or UTRAN; and Yes Act on any paging request message received by GERAN or UTRAN.

[0268] 2. Roaming out (from GAM mode to GERAN/UTRAN mode)

[0269] This process can be applied when the UE is separated from the general IP access network, and its mode selection is "preferred GAN" or "preferred GERAN/UTRAN". When the UE is separated from the general IP access network, according to the prevailing situation, the UE can first deregister with the GANC.

[0270] For the mode selection of "Preferred GAN" and "Preferred GERAN/UTRAN", the UE separates the GA-CSR entity from the RR-SAP, and reattaches the GERAN-RR or UTRAN RRC entity to the RR-SAP and returns to normal The functionality of GERAN-RR or UTRAN RRC. For the "GAN Only" mode selection, the GA-CSR remains attached to the NAS, and the UE remains in the GAN mode (ie, in the "no service" situation).

[0271] D. GAN registration related process

[0272] 1. Discovery and registration for universal access

[0273] The discovery and registration process can only be applied if the UE prefers to operate in "GAN only", "Preferred GAN", or "Preferred GERAN/UTRAN mode if no permitted PLMN is available through GERAN/UTRAN."

[0274] Once the UE has established a connection to the general IP access network, the UE completes the discovery process for the GANC that provides services in the HPLMN of the UE to determine the appropriate GANC to be connected to. The address of the default GANC in the HPLMN of the UE to which the UE can register.

[0275] The UE attempts to register on the default GANC provided by the serving GANC during the discovery process by completing the registration process. By default, the GANC can accept the registration, redirect the UE to another GANC, or reject the registration.

[0276] a) Security gateway identification

[0277] The USIM of the UE includes the FQDN (or IP address) that provides the service GANC and the relevant SEGW, or the UE obtains the information according to the information in the USIM. When the UE does not store any information about other GANCs and related SEGWs, the UE completes the discovery process for the GANC that provides services. As part of the registration process, the default GANC can indicate whether the GANC and SEGW address or the address of the GANC to which the UE is redirected can be stored by the UE.

[0278] The UE may also store the service GANC information, which is used for the GANC service that the UE can use to achieve a successful registration process. The default GANC controls whether to allow the UE to store the service GANC information. When there is no GERAN/UTRAN coverage in the AP area, the stored service GANC information is associated with the AP-ID. When GERAN/UTRAN coverage exists in the AP area, the stored service GANC information is associated with GSM CGI or UTRAN CI. The stored service GANC information is: (1) Service SEGW FQDN or IP address that accompanies successful registration; Service GANC FQDN or IP address that accompanies successful registration; and (3) Optionally, service that accompanies successful registration and if returned from the network GANC TCP port. Different embodiments store different numbers of such entries in the UE are specific implementations. When the default GANC indicates that the UE is allowed to store these addresses, only the last successfully registered GANC association is stored. The UE may preferably join an attached universal IP access network point, and its association with the serving GANC is stored in the memory.

[0279] When connected to a general IP access network, when the UE has a stored service GANC for AP-ID or GERAN/UTRAN cells, the UE attempts to register with the associated service GANC in its memory. The GANC can still reject the UE for any reason, even if it may have previously served the UE. In the case of receiving a registration rejection or if the registration fails for any reason (for example, no response is received), the UE deletes the address serving the GANC from its storage list.

[0280] If the UE does not receive a response to the registration request sent to the serving GANC (which is not the default GANC), the UE re-attempts to register with the default GANC. If the UE does not receive a response to the registration request sent to the default GANC, it uses the GANC that provides the service to try the discovery process to obtain a new default GANCo

[0281] In the case that the UE attempts to register or discover a GANC after failing to register on the GANC, the UE provides the following indication during the registration or discovery process: the UE has tried to register on another GANC, the reason for the failure, and the failed registration The GANC and SEGW addresses. When a UE is connected to a general IP access network, and for the general IP access network, the UE does not have a stored service GANC in its memory, the UE attempts to register with the default GANC.

[0282] b) GANC's capabilities

[0283] GANC-specific information is transmitted to the successfully registered UE.

[0284] c) UE's capabilities

[0285] The GAN-specific capabilities of the UE are transferred to the GANC during registration.

[0286] d) GAN services required

[0287] As part of the registration process, the UE can request the GAN service it needs from the GANC.

[0288] e) GAN mode selection

[0289] The UE (ie, GAN support with Iu mode) transmits its GAN mode support information to GANCo during the discovery and registration process (ie, in the GAN category flag IE). The GAN mode support selection is: A/Gb mode support , Iu mode support, or these two modes support. When no GAN mode support information is received, GANC assumes that the UE only supports A/Gb mode operation.

[0290] The GANC providing the service can use the received GAN mode support information to assign the UE to the appropriate default GANC (for example, if independent A/Gb mode and Iu mode GANC are deployed in the network), or to assign the UE Give the appropriate TCP port on the default GANC (for example, if a separate TCP port is used for A/Gb mode and Iu mode GAN services). The GANC supporting the Iu mode also indicates in the GAN mode indicator IE that the GAN mode is used for the current session, which enables the UE to determine the ability of the Iu mode of the home PLMN.

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

[0292] Table 1: GAN mode selection process related to GAN discovery

[0293]

<td></td><td colspan="3">GAN mode capability of the belonging PLMN</td>

<td>UE's GAN mode capability</td><td>A/Gb only</td><td>Iu only</td><td>Both</td>

<td>A/Gb only</td><td>GANC: Processed into normal A/Gb mode and found UE: Continue to register in A/Gb mode</td><td>GANC: There is no GAN mode support information provided or the A/Gb mode indicated by the UE (only), so it is rejected (non-dedicated) UE: try again next time</td><td>GANC: There is no GAN mode support information provided or the A/Gb mode indicated by the UE (only), so it is processed as normal A/Gb mode discovery. Assign UE to GANCoUE that supports A/Gb: Continue to register in A/Gb mode</td>

[0294]

<td>Iu only</td><td>GANC: Processed into normal A/Gb mode and found UE: There is no GAN mode selection provided by GANC, so interrupt the GAN operation and try again at the next boot</td><td>GANC: The Iu mode indicated by the UE is supported (only), so it accepts and sends the GAN mode mini-character=IuUE: Continue to register in Iu mode</td><td>GANC: The Iu mode indicated by the UE is supported (only), so the GAN mode indicator=Iuo is accepted and sent to assign the UE to the GANC that supports Iu οUE: Continue to register in Iu mode</td>

<td>Both</td><td>GANC: Processed into normal A/Gb discovery UE: There is no GAN mode selection provided by GANC, so continue with Iu mode registration (Note 1)</td><td>GANC: Support the two modes indicated by the UE, so accept and send GAN mode indicator=Iu UE: Continue to register in Iu mode</td><td>GANC: Supports the two modes indicated by the UE, so it accepts and sends GAN mode indicator=Iu. Assign UE to GANCoUE that supports Iu: Continue with Iu mode registration</td>

[0295] Note: As described in Table 2 below, the result of the Iu mode registration of the A/Gb-enabled UE on the A/Gb-enabled GANC is that the UE is placed in the A/Gb mode.

[0296] In some embodiments, the default GANC or the serving GANC uses the received GAN mode support information to redirect the UE to a different GANC or a different TCP port on the current GANC. The GANC supporting the Iu mode also indicates the GAN mode used for the current session in the GAN mode indicator IE.

[0297] Table 2 lists the registration processing for various combinations of the GAN mode capabilities of the UE and the home PLMN

[0298] Table 2: GAN mode selection process related to GAN registration

[0299]

<td></td><td colspan="3">Default/service GAN mode capability of GANC</td>

<td>UE's GAN mode capability</td><td>A/Gb only</td><td>Iu only</td><td>Both</td>

<td>A/Gb only</td><td>GANC: Processed into normal A/Gb mode Registering UE: Continue according to the GAN process of A/Gb mode</td><td>GANC: No GAN mode support information provided or A/Gb mode indicated by the UE (only), so rejected (invalid GANC)</td><td>GANC: There is no GAN mode support information provided or the A/Gb mode indicated by the UE (only), so it is processed as normal A/Gb mode registration. If necessary, the UE is redirected to GANC that supports A/Gb.</td>

[0300]

<td></td><td></td><td>UE: Attempt to register or rediscover with the default GANC (according to the GAN process in A/Gb mode)</td><td>UE: Continue according to the GAN process in A/Gb mode</td>

<td>Iu only</td><td>GANC: Registered as normal A/Gb mode UE: There is no GAN mode selection provided by GANC, so registration is cancelled and processed as registration rejection (invalid GANC)</td><td>GANC: The Iu mode indicated by the UE is supported (only), so the GAN mode indicator = IuUE is accepted and sent: the GAN process continues according to the Iu mode</td><td>GANC: The Iu mode indicated by the UE is supported (only), so the GAN mode indicator=Iu is accepted and sent. UE: The GAN process continues according to the Iu mode</td>

<td>Both</td><td>GANC: Processed as normal A/Gb registration UE: There is no GAN mode selection provided by GANC, so the GAN process according to A/Gb mode continues</td><td>GANC: Support the two modes indicated by the UE, so accept and send the GAN mode indicator=IuUE: Continue the GAN process according to the Iu mode</td><td>GANC: Supports the two modes indicated by the UE, so it accepts and sends GAN mode indicator = Iu or A/Gb (see Note 1 below). If necessary, redirect the UE to a GANC that supports Iu or A/Gb. UE: Continue according to the GAN process of Iu or A/Gb mode</td>

[0301] Note 1: GANC's selection of Iu mode or A/Gb mode can be based on: other information received in the GAN registration message from the UE, information stored in the GANC, and based on the operator (ie, service provider) policy For example, if the GSM RR/UTRAN RRC State IE indicates that the UE is in GERAN dedicated mode, the location of the UE is an area not covered by UTRAN, and the operator wants to minimize the handover between RATs, GANC can guide the UE to use A/Gb mode .

[0302] f) Discovery process

[0303] When a UE supporting GAN first tries to connect to a GAN, the UE needs to recognize the default GANC. Each UE that supports GAN can be configured to have the GANC providing services and the FQDN (or IP address) of the relevant SEGW, or the UE can obtain the FQDN according to the information in the USIM (see^uNumbering, addressing and identification, 3GPP TS 23. 003 standard). The UE establishes a secure IPSec tunnel and TCP connection by using the provided or acquired address to first connect to the GANC-SEGW that provides the service and the GANC in the HPLMN of the UE. The UE obtains the FQDN or IP address of the default GANC in the HPLMN and related SEGW through the discovery process.

[0304] If no GERAN/UTRAN coverage is available when the UE is connected to the GANC for GAN service, the GANC cannot necessarily determine the UE in order to assign the UE to the correct service GANC (for example to enable handover and local-based services) s position. GANC allows the operator to determine the service strategy in this case. For example, the operator can provide services to users through certain restrictions (possibly through the user interface instructions on the UE). When the UE initiates the discovery/registration process and no GERAN/UTRAN coverage is available, GANC may not have sufficient information to correctly route subsequent emergency calls.

[0305] FIG. 23 illustrates the discovery process in some embodiments. The figure shows the UE 2305, the GANC 2315 that provides services, the security gateway SEGW 2320 related to the GANC 2315 that provides services, and the GANC 2315 that provides services

Different messages exchanged between related DNS servers 2325. In the following description, it is assumed that the UE 2305 has mode selection: only GAN or preferred GAN or preferred GERAN/UTRAN, and the UE has been connected to a general IP access network. Different embodiments consider different signal levels to be sufficient to trigger the GAN discovery and registration process. The following steps are taken during the discovery process in some embodiments.

[0306] As shown in FIG. 23, when the UE 2305 has the provided or acquired FQDN of the SEGW for providing services, the UE performs (in step 1) a DNS query (via the universal IP access network interface) to change The FQDN resolves to an IP address. When the UE has the IP address of the SEGW provided to provide services, the DNS step is omitted. Next, the DNS server 2310 returns a response (in step 2), which includes the IP address of the SEGW 2320 that provides the service.

[0307] As shown in the figure, the UE 2305 establishes a secure tunnel to the SEGW 2320 that provides the service (step 3). When the UE 2305 has the provided or acquired FQDN of the GANC 2315 that provides the service, the UE 2305 makes a DNS query (through a secure tunnel) to the DNS server 2325 related to the GANC 2315 that provides the service (step 4) to resolve the FQDN to IP address. When the UE 2305 has the IP address provided by the GANC for providing services, the DNS step will be omitted. The DNS server 2325 returns a response including the IP address of the GANC 2315 that provides the service (step 5).

[0308] The UE 2305 establishes a TCP connection to a well-defined port of the GANC 2315± that provides the service. UE 2305 then uses GA-RC DISCOVERY REQUEST (GA-RC discovery request) to query the GANC 2315 providing the service for the default GANC (step 6) ο This message includes: (1) Cell information: the current UTRAN/GERAN cell ID Or the last LAI successfully registered by the UE, together with an indicator indicating which one it is; (2) General IP access network attachment point information: AP-ID, such as the following in the secondary part VII, the identifier in the GAN (3) UE identification: IMSI; and (4) GAN category flag: including the indication of supporting A/Gb mode and Iu mode.

[0309] Next, the GANC 2315 that provides the service uses the information provided by the UE (for example, cell ID) to return a GA-RC DISCOVERY ACCEPT (GA-RC discovery acceptance) message (step 7) to provide the default GANC and its related The FQDN or IP address of the default SEGW. This allows the UE to be directed to the "local" default GANC in HPLMN to optimize network performance. It may include the GANC port that the UE needs to register. The GAN mode indicator can be included, as described in the GAN mode section of the secondary section above.

[0310] When the GANC 2315 providing the service cannot accept the GA-RC DISCOVERY REQUEST message, it returns a GA-RC DISCOVERY REJECT message indicating the reason for the rejection (step 8). The IPSec tunnel to the serving SEGW 2320 is released (step 9). The same IPSec tunnel can be reused for the GAN registration process. In this case, the IPSec tunnel is not released.

[0311] g) Registration process-normal situation

[0312] After the discovery process, the UE establishes a secure tunnel with a security gateway with the default GANC provided in the discovery process through the GANC providing the service, and attempts to register with the default GANC. The default GANC can become the service GANC for the connection by accepting registration, or the default GANC can redirect the UE performing the registration to a different service GANC.

[0313] GANC redirection may be based on information provided by the UE during the registration process, operator selection strategy, or network load balancing. The GAN registration process provides the following functions: (1) Ensure that the UE is registered with the appropriate GANC entity, that is, use the redirection process; (2) Notify GANC that the UE is now connected through the general IP access network and is available at a specific IP address. GANC maintains the registration context for the purpose of, for example, terminating a call to a mobile device; (3) Provides the UE with operating parameters related to the GAN service. The "system information" message content applicable to the GAN cell is delivered to the UE during the GAN registration process. This allows the UE to switch to the GAN mode and use the core network to trigger the NAS process after the registration process (such as setting

Bit/routing area updates, calls originating from mobile devices, calls terminating from mobile devices, etc.), and (4) enables the UE to request which GAN service is required.

[0314] FIG. 24 shows the registration process in some embodiments. The figure shows different messages exchanged between UE 2405, DNS 2410, GANC 2415 providing services, security gateway SEGW 2420 related to GANC 2415 providing services, and DNS server 2425 related to GANC 2415 providing services. The following steps are completed during the registration process: [0315] As shown in Figure 24, when the UE 2405 is provided with the default or serving SEGW FQDN, the UE performs a DNS query (via the universal IP access network interface) to convert the FQDN to IP Address (step 1). When the UE has the provided IP address for the SEGW, the DNS step is omitted. The DNS server 2410 returns a response (step 2).

[0316] As shown in the figure, the UE 2405 establishes a secure IPSec tunnel to the SEGW 2420 (step 3). If the IPSec tunnel is being reused based on previous discovery or registration, this step can be omitted. When the UE2405 is provided with the default or serving GANC FQDN, the UE then performs a DNS query (via a secure tunnel) to resolve the FQDN into an IP address (step 4) ο When the UE has an IP address for GANC, the DNS step is Omit. Next, the DNS server 2425 returns a response (step 5).

[0317] The UE 2405 then establishes a TCP connection to the TCP port on the GANC. The TCP port can be a known port or a port previously received from the network during discovery or registration. The UE 2405 attempts to register on the GANC by transmitting the GA-RC REGISTER REQUEST (step 6). The message includes: (1) Cell information: the current UTRAN/GERAN cell ID or the latest LAI successfully registered by the UE, together with an indicator indicating which one it is; (2) General IP access network attachment point information: ΑΡ -ID, as defined in the identifiers in GAN in Part VII as follows; (3) UE identity: IMSI; (4) UE capability information; required GAN service; (6) GAN type flag: including support A/Gb mode, support Iu mode instructions.

[0318] When GANC 2415 accepts the registration attempt, GANC 2415 responds with GA-RC REGISTERACCEPT (step 7). In this case, as long as the UE is registered with the GANC, the TCP connection and the secure IPSec tunnel will not be released but will be maintained.

[0319] The GA-RC REGISTER ACCEPT message includes: (1) GAN capability information; and (2) GAN specific system information, including (a) GAN mode indicator: A/Gb mode GAN or Iu mode GAN, (b) ) Cell description of GAN cell, (c) Location-area identification, including mobile country code, mobile network code and location area code corresponding to GAN cell, (d) Cell identification, used to identify the location area corresponding to GAN cell , And (e) the applicable system timer value (for example, for application-level keep-alive message transmission interval, see the "keep-alive" subsection below).

[0320] Alternatively, the GANC 2415 may reject the request. In this case, GANC 2415 responds with GA-RC REGISTER REJECT (GA-RC-REGISTERED rejected) indicating the reason for rejection (step 8). The TCP connection and the secure IPSec tunnel are then released.

[0321] Alternatively, if the GANC 2415 decides to redirect the UE to the (another) service GANC, the GANC 2415 uses the FQDN or IP address that provides the target service GANC and the related SEGW and if the GANC requires use with the service GANC The specific mode provides a GAN mode indicator (for example, if GANC knows that the service GANC only supports A/Gb mode GAN) GA-RC REGISTERREDIRECT to respond (step 9). In this case, the TCP connection is released and the secure IPSec tunnel is selectively released (step 10), depending on whether the network indicates that the same IPSec tunnel can be reused for the next registration. The GA-RC REGISTER REDIRECT message may include: (1) a single service SEGW and GANC address, or (2) a PLMN identification and a list of related service SEGW and GANC addresses. The message may also include an indication of whether the GANC address can be stored in the UE for future use.

[0322] h) Registration process-abnormal situation

[0323] When the service GANC rejects the registration request and does not provide a redirection to another service GANC, the UE re-attempts to register to the default GANC, including indicating the reason for the failed registration attempt, and the service GANC and SEGW to which the registration request failed. The UE also deletes all stored information about the service GANC.

[0324] When the default GANC rejects the registration request and the redirection cannot be provided to the appropriate service GANC, the UE can retry the discovery process for the GANC providing the service (including indicating the reason for the failed registration attempt, and providing in the most recent discovery process) The default GANC). The UE also deletes all stored information about the default GANC.

[0325] 2. Deregistration

[0326] FIG. 25 illustrates deregistration initiated by the UE 2505 in some embodiments. The GA-RC deregistration process allows the UE 2505 to explicitly notify the GANC 2510 that it is leaving the GAN mode by sending a GA-RC DEREGISTER message to the GANC 2510 (step 1) (for example, when the UE 2505 is separated from the general IP access network Time), so that GANC 2510 can release the resources allocated to UE 2505D. When the TCP connection to the UE is suddenly lost, GANC 2510 also supports "Implicit GAN Deregistration".

[0327] FIG. 26 shows deregistration initiated by GANC 2610 in some embodiments. As shown in the figure, GANC 2610 can release the UE registration context autonomously and send a GA-RC DEREGISTER message to UE 2605 (step 1). Alternatively, GANC 2610 can implicitly close the TCP connection with the UE Deregister the UE 2605. During shutdown, the GA-RC sublayer of the UE may ensure that the UE is explicitly separated from the network before completing the GA-RC deregistration process.

[0328] 3. Registration Update

[0329] FIG. 27 shows a registration update in some embodiments. The GA-RC registration update process allows the UE 2705 to update the information in the GANC 2710 regarding the change of the identity of the overlapping GERAN cell or the change of the attached general IP access network point. As shown in the figure, UE 2705 sends a GA-RCREGISTER UPDATE UPLINK (registration update uplink) message conveying update information to GANC 2710. For example, the operators policy may cause UE 2705 to be redirected to another service GANC or Denial of service.

[0330] When UE 2705 detects UTRAN/GERAN coverage after reporting no coverage during GAN registration, the UE sends the GA-RC registration update uplink with update information to GANC. Whenever the attached universal IP access point changes, the UE will send the GA-RC REGISTER UPDATE UPLINK of the attached universal IP access point update information to GANC. When the UE is required to use the new GAN service list When the GANC is updated, the UE then sends the GA-RC REGISTER UPDATE UPLINK message including the new "Required GAN Service" list to the GANC.

[0331] When the GANC 2710 decides to redirect the UE based on the updated information, the GANC 2710 can selectively send GA-RC REGISTER REDIRECT (step 2). GANC 2710 can also selectively deregister the UE 2705 when it receives an update by sending GA-RC-DEREGISTERED to the UE (step 3).

[0332] FIG. 28 shows the process of registering and updating the downlink in some embodiments. The GAN registration update process also allows the GANC 2810 to update the GAN system in the UE 2805 by sending a GA-RC REGISTER UPDATE DOWNLINK (GA-RC-REGISTERED update downlink) message to the UE transmitting the update information (step 1) as needed information.

[0333] 4. Keep alive

[0334] FIG. 29 shows a keep-alive process in some embodiments. The keep alive process is a mechanism between peer GA-RC entities to instruct the UE to still register to GANC. Periodically send GA-RCKEEP ALIVE (GA-RC keep alive) messages (step 1), and the UE 2805 then uses the current The established lower layer connection confirms that GANC 2810 is still available.

[0335] 5. Cell broadcast information

[0336] FIG. 30 shows a cell broadcast information mechanism of some embodiments. Cell broadcast information is a mechanism between peer GA-RC entities, which allows GANC to deliver UE information related to cell broadcast services. UE3005 includes the "Required GAN Service" information in the GA-RC REGISTERREQUEST and The GA-RC REGISTER UPDATEUPLINK message indicates that the UE needs cell broadcast service. GANC 3010 then delivers the required information to UE 1105 in the GA-RCCELL BRODACAST INFO message (step 1).

[0337] E. Authentication

[0338] The Up interface supports the ability to authenticate the UE by using GANC and using GSM or UMTS credentials (for the purpose of establishing a secure tunnel). Use EAP-SIM or EAP-AKA in IKEv2 to perform authentication between UE and GANC.

[0339] F. Encryption and integrity protection

[0340] All control plane and user plane services on the Up interface are sent through the paired IPSec ESP tunnel mode security association (one in each direction) established during the establishment of the IKEv2 security association. Encryption and integrity protection are strengthened through GANC-SEGW through negotiated cryptographic algorithms, based on core network strategies.

[0341] G. GA-CSR connection processing

[0342] The GA-CSR connection of the GAN in the Iu mode is a logical connection of the CS domain between the UE and the GANC. When the upper layer in the UE requests to establish a CS domain signaling connection and the UE is in the GA-CSR-IDLE state (that is, there is no GA-CSR connection), the GA-CSR connection is established. When receiving a successful response from the network, GA-CSR responds to the upper layer: CS and signaling connection has been established, and the UE has entered the equivalent mode of RRC connection mode (BP, GA-CSR-CONNECTED state).

[0343] 1. GA-CSR connection establishment

[0344] FIG. 31 shows the successful and unsuccessful establishment of a GA-CSR connection in some embodiments. As shown in the figure, the UE 3105 initiates the establishment of the GA-CSR connection by sending a GA-CSR REQUEST (GA-CSR request) message to the GANC 3110 (step 1). The message includes the "reason for establishment" indicating the reason for the establishment of the GA-CSR connection.

[0345] When the GANC determines that the connection request can be accepted, the GANC 3110 notifies the UE 3105 of the connection request acceptance by sending GA-CSRREQUEST ACCEPT (GA-CSR request acceptance) (step 2), and the UE enters the GA-CSR-CONNECTED state. On the other hand, when GANC determines that it needs to reject the GA-CSR connection request, GANC 3110 sends a GA-CSR REQUESTREJECT indicating the reason for the rejection to UE 3105 (step 3) to complete the process.

[0346] 2. GA-CSR connection release

[0347] FIG. 32 shows the release of the logical GA-CSR connection between the UE and the GANC in some embodiments. As shown in the figure, MSC 3215 instructs GANC 3210 to release the CS resources allocated to the UE by sending a RANAP Iu release command message to GANC 3210 (step 1).

[0348] Next, the GANC 3210 uses the Iu release complete message to confirm the resource release to the MSC 3215 (step 2). GANC 3210 then uses the GA-CSR RELEASE (GA-CSR release) message to order the UE 3205 to release the resources (step 3) ο Finally, the UE 3205 uses the GA-CSR RELEASE COMPLETE (GA-CSR release complete) message to confirm the resource release to the GANC (Step 4), and the GA-CSR status in the UE changes to GA-CSR-IDLEo

[0349] H. CS Safe Mode Control

[0350] FIG. 33 shows a message flow for security mode control in some embodiments. As shown in the figure, MSC3115 sends the RANAP security mode command message to GANC 3310 (step 1). The message contains the integrity key (IK) and allowed algorithms, and optionally, the encryption key (CK) and allowed algorithms.

[0351] Next, GANC 3310 cancels GA-CSR SECURITY MODE (COMMANDGA-CSR security mode command)

The information is sent to the UE 3305 (step 2). The message indicates integrity protection and encryption settings (that is, can be applied after relocation to UTRAN), and a random number. The UE stores this information for possible future use after relocation to UTRAN.

[0352] Next, the UE 3305 calculates the MAC based on the random number, the UE's IMSI, and the integrity key calculated by the UE. The MAC or "message authentication code" allows GANC to verify that the UE has been able to calculate the same integrity key value as the GANC received from the MSC, thereby preventing a certain "man in the middle" security attack. UE 3305 then sends a GA-CSR SECURITY MODE COMPLETE message to GANC 3310 (step 3) to inform it of the selected algorithm and calculated MAC.

[0353] GANC 3310 then uses the random number, the UE's IMSI, and the integrity key provided by the MSC in step 1 to verify the MAC. When the GANC verifies that the MAC is correct (that is, the MAC calculated by the GANC is the same as the MAC calculated by the UE), it sends a security mode complete message to the MSC 3315 (step 4). The MAC certification that authenticates to the GANC is the same as that authenticated to the core network.

[0354] I. CS NAS Signaling Process

[0355] After the GA-CSR connection is established, NAS signaling can be transmitted from the MAC to the UE and from the UE to the MSC.

[0356] 1. NAS signaling from MSC to UE

[0357] FIG. 34 shows MAC to UE NAS signaling in some embodiments. As shown in the figure, for the NAS signaling from the MAC to the UE, the MSC 3415 sends the NAS PDU to the GANC through the RANAP direct transmission message (step 1). GANC 3410 encapsulates the NAS PDU into the GA-CSR DL to directly transmit the message, and forwards the message to the UE 3405 through the existing TCP connection (step 2) ο

[0358] 2. NAS signaling from UE to MSC

[0359] FIG. 35 shows UE to MSC NAS signaling in some embodiments. As shown in the figure, the UE 3505 receives a request from the NAS layer to transmit an uplink NAS PDU. Assuming that the required signaling connection already exists, the UE 3505 encapsulates the NAS PDU into the GA-CSR DL to directly transmit the message, and sends the message to the GANC 3510 (step 1). GANC 3510 relays the received message to MSC 3515 through RANAP direct message transmission (step 2).

[0360] J. CS call originating from a mobile device

[0361] FIG. 36 shows steps performed during a CS call originating from a mobile device in some embodiments. This process assumes that the UE is in the GAN mode, that is, the UE has successfully registered with the GANC, and the GA-CSR is the serving RR entity for the CS service in the UE. It is also assumed that there is no GA-CSR signaling connection between the UE and the GANC (that is, the GA-CSR-IDLE state). As shown in the figure, perform the GA-CSR connection establishment process (step 1). In some embodiments, the process is performed as described in the GA-CSR connection establishment subsection above. Next, UE 3605 sends the CM service request message to GANC 3610 in the GA-CSR UL direct transmission message.

[0362] Next, the GANC 3610 establishes an SCCP connection to the MSC 3615, and uses the RANAP initial UE message to forward the NAS PDU (ie, the CM service request message) to the MSC 3615 (step 3). The message includes a domain indicator (ie, core network (CN) domain identifier) set to the value "CS domain". RANAP will be used to directly transmit messages between GANC and MSC to send subsequent NAS messages between UE and MSC.

[0363] The MSC 3615 can use the standard UTRAN authentication process to selectively authenticate the UE (step 4). The MSC 3615 can selectively initiate the security mode control process described in the CS security mode control subsection above. UE 3605 sends to the MSC a setup message (step 6) that provides details of the call and its bearer capabilities and supported codecs. This message is included in the GA-CSRUL direct transmission between UE and GANC. GANC forwards the setup message to the MSC.

[0364] Next, the MSC 3615 uses the call continuation message to the GANC to indicate that it has received the call setup and will not accept other call setup information (step 7). GANC forwards the message to the UE in the GA-CSR DL direct transmission message (step 7) ο

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

[0366] GANC 3610 then sends a GA-CSR ACTIVATE CHANNEL (GA-CSR activation channel) message to UE 3605 (step 9), which includes bearer path setup information, such as: (1) channel mode; (2) multi-rate Codec configuration; UDP port and IP address used for uplink RTP stream; and voice sample size.

[0367] Next, UE 3605 sends GA-CSRACTIVATE CHANNEL ACK indicating the UDP port used for the downlink RTP stream to GANC 3610 (step 10). Since the Iu UP support mode is indicated by the MSC in step 8, GANC 3610 sends the Iu UP INITIALISATION (IuUP initialization) packet to the MSC (step 11).

[0368] In the response, the MSC responds with the Iu UP INITIALISATION ACK packet (step 12). GANC 3610 uses the GA-CSR ACTIVATE CHANNEL COMPLETE (GA-CSRACTIVATE CHANNEL) message to notify UE 3605 of the completion of RAB establishment (step 13). Alternatively, steps 11 and 12 may occur before step 9.

[0369] GANC 3610 notifies MSC 3615 that RAB has been established by sending a RANAP RAB allocation response message (step 14). The MSC 3615 uses an alarm message to notify the UE 3505 that the called party is ringing. The message is transmitted to GANC 3610 (step 15), and GANC uses GA-CSR DL to directly transmit the message to UE 3605 (step 15). When the UE has not connected the audio path to the user, it generates a ring back to the calling party. Otherwise, the ringback generated by the network will be returned to the calling party.

[0370] Next, the MSC 3615 informs through a connection message that the called party has responded. The message is transmitted to GANC 3610 (step 16), and the GANC uses GA-CSR DL to directly transmit the message to the UE (step 16). The UE connects the user to the audio path. If the UE is generating ringback, it stops and connects the user to the audio path.

[0371] The UE 3605 then sends a connection confirmation message in the response (step 17), and the two parties are connected for a voice call. This message is included in the GA-CSR UL direct transmission between UE and GANC. GANC forwards the connection confirmation message to the MSC. At this time, the two-way voice service flows between the UE 3605 and the MSC 3615 through the GANC 3610 (step 18).

[0372] 2. UE terminates Iu UP protocol

[0373] Some embodiments use alternative procedures to make CS calls that originate from a mobile device. Figure 37 shows the steps performed during a CS call originating from a mobile device in these embodiments. This process assumes that the UE is in the GAN mode, that is, the UE has successfully registered with the GANC, and the GA-CSR is the serving RR entity for CS service in the UE. It is also assumed that there is no GA-CSR signaling connection between the UE and the GANC (that is, the GA-CSR idle state). Steps 1 to 8 are performed to be the same as the description of steps 1 to 8 shown in FIG. 36 above, so they will not be repeated for the sake of simplicity.

[0374] 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 the GA-CSR ACTIVATE CHANNEL message that the Iu UP support mode is required (step 9), and the UE 3705 Send the Iu UP INITIALISATION packet to the MSC 3715 (step 10). In response, MSC 3715 responds with Iu UP INITIALISATION ACK packet (step 11). Next, UE 3705 sends GA-CSR ACTIVATE CHANNEL ACK to GANC 3710 (step 12).

[0375] GANC 3710 notifies MSC 3715 that RAB has been established by sending a RANAP RAB allocation response message (step

13) o GANC 3710 also sends the GA-CSR ACTIVATE CHANNEL COMPLETE message to UE 3705 (step 14). Steps 15 to 18 are executed as the same as the description of steps 15 to 18 shown in FIG. 36 above, and therefore will not be repeated for the sake of simplicity.

[0376] K. Terminating the CS call on the mobile device

[0377] FIG. 38 shows steps performed during a CS call terminated at a mobile device in some embodiments. The description of this process assumes that the UE is in the GAN mode, that is, the UE has successfully registered with the GANC, and the GA-CSR is the serving RR entity for the CS service in the UE. It is also assumed that there is no GA-CSR signaling connection between the UE and the GANC (that is, the UE is in the GA-CSR idle state). When the CS call terminated on the mobile device arrives at the MSC 3815, as shown in Figure 38, the MSC 3815 sends a RANAP paging message to the GANC 3810 identified by the most recent location update received by it, and includes TMSL if available. The IMSI of the calling mobile device is always included in the request.

[0378] Next, GANC 3810 uses the IMSI provided by MSC 3815 to identify the UE registration context. Then GANC 3810 uses the GA-CSR PAGING REQUEST (GA-CSR paging request) message to page the UE 3805 (step 2). This message includes the TMSI (if available) in the request from the MSC, or it includes only the IMSI of the UE.

[0379] The UE 3805 responds with GA-CSR PAGING RESPONSE. The UE transitions to the GA-CSR connection state. GANC 3810 establishes an SCCP connection to MSC 3815. GANC 3810 then uses the RANAP initial UE message to forward the paging response to MSC 3815 (step 4). The RANAP direct transmission message will be used to send subsequent NAS messages between the UE and the core network between the GANC and the MSC.

[0380] The MSC 3815 can use the standard UTRAN authentication process to selectively authenticate the UE 3805 (step 5) o The MSC can selectively update the security configuration in the UE through the GANC (step 6), as in the CS security mode above Control as described in the secondary part.

[0381] The MSC 3815 then uses the setup message sent to the UE through the GANC to initiate call setup (step 7). GANC forwards the message to UE 3805 in the GA-CSR DL direct transmission message (step 7).

[0382] Next, the UE 3805 responds using GA-CSR UL to directly transmit the call with confirmation after checking its compatibility with the bearer service requested in "Setup" and modifying the bearer service as needed. When "setup" is included in the signal information element, the UE uses the indicated signal to alert the user, otherwise the UE alerts the user after successfully configuring the user plane. GANC 3810 forwards the call confirmation message to MSC 3815 (step 8).

[0383] Next, MSC 3815 uses GANC 3810 to initiate the allocation process, which triggers the establishment of the RTP stream (voice bearer channel) between the GANC and the UE (step 9), which is the same as the above-described CS from the mobile device. Steps 8-14 in the call scenario are the same.

[0384] The UE 3805 then informs the user that it is alerting the user through the alert message contained in the GA-CSR UL DIRECT TRANSFER (step 10). GANC forwards the warning message to the MSC (step 10)_o The MSC sends the corresponding alarm message to the calling party.

[0385] The UE 3805 then informs the called party that it has answered through the connection message contained in the GA-CSR UL DIRECT TRANSFER (step 11). The GANC 3810 forwards the connection message to the MSC 3815 (step 11). The MSC sends the corresponding connection message to the calling party and completes the audio connection. The UE connects the user to the audio path.

[0386] Next, the MSC 3815 confirms to the GANC 3810 through a connection confirmation message (step 12). GANC forwards the message to UE 3805 in GA-CSR DL DIRECT TRANSFER (step 12). Both parties of the call are connected on the audio path. At this time, the two-way voice service flows between the UE and the MSC through the GANC (step 13).

[0387] L. CS Call Clear

[0388] FIG. 39 illustrates call clearing initiated by the UE in some embodiments. As shown in the figure, the UE 3905 sends a disconnect message to the MSC 3915 (step 1) to release the call. This message is included in the GA-CSR UL direct transmission between UE 3905 and GANC 3910. GANC 3910 forwards the disconnect message to the MSC (ie, uses RANAP to directly transmit the message) (step 1).

[0389] Next, the MSC 3915 responds to the GANC with a release message (step 2). GANC uses the GA-CSR DL to directly transmit the message and forward the message to the UE 3905 (step 2). The UE 3905 responds with a release complete message (step 3). This message is included in the GA-CSR UL direct transmission message between UE and GANC. GANC forwards the disconnect message to the MSC (step 3). The MSC triggers the release of the connection (step 4), as described in the GA-CSR connection release subsection above.

[0390] M. CS Switch

[0391] 1. CS handover from GERAN to GAN

[0392] a) GANC terminates the Iu UP agreement

[0393] FIG. 40 shows a CS handover from GERAN to GAN in some embodiments. The description of the handover process from GERAN to GAN assumes the following conditions: (1) UE is in an active call on GERAN; (2) UE mode selection is preferred GAN, or if it is preferred GERAN/UTRAN, then from the current serving cell RxLev fell below the defined threshold. In some embodiments, the threshold may be designated as a fixed value, or may be provided to the UE through GERAN BSS in a dedicated mode; (3) The UE has successfully registered with GANC, allowing the UE to obtain GAN system information; and ( 4) GERAN provides information about neighboring 3G cells, so that one of the cells in the 3G neighbor list matches the 3G cell information related to GANC, as provided in the AS-related components in the system information obtained from GANC Like that. As shown in the figure, UE 4005 starts to include GAN cell information into the measurement report message to 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 an artificially specified value (for example, RxLev = 63), allowing the UE to indicate its preference for GAN.

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

[0395] The MSC 4020 uses a relocation request message to request the target GANC 4010 to allocate resources for handover (step 3). The UE is identified by the included IMSI parameters.

[0396] Since the Iu UP support mode is indicated, GANC 4010 sends the Iu UP INITIALISATION packet to the MSC (step 4). The MSC responds with the Iu UP INITIALISATION ACK packet (step 5).

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

[0398] Next, the GERAN BSC 4015 sends an inter-system to UTRAN handover command message (including a handover to UTRAN command message) to the UE 4005 to initiate a handover to GAN (step 8). The UE does not switch its audio path from GERAN to GAN until the switching is completed (that is, until it sends a GA-CSRHANDOVER COMPLETE message) to keep the audio interruption short.

[0399] The UE 4005 uses a GA-CSR HANDOVER ACCESS (GA-CSR handover access) message to access the GANC 4010 (step 9), and provides the entire inter-system to UTRAN handover command message received from GERAN. GANC 4010 to UE

4005 sends GA-CSRACTIVATE CHANNEL message (step 10), including bearer path setup information, such as: (1) channel mode; (2) multi-rate codec configuration; (3) UDP port and IP for uplink RTP stream Address; and (4) voice sample size.

[0400] Next, the UE 4005 sends a GA-CSR ACTIVATE CHANNEL ACK to the GANC 4010 (step 11), indicating the UDP port used for the downlink RTP stream. GANC 4010 uses the GA-CSRACTIVATE CHANNEL completion message to notify UE 4005 that the RAB establishment has been completed (step 11).

[0401] The UE 4005 sends a GA-CSR handover complete message at the end of the handover process to indicate the completion of the handover process (step 13). It switches users from the GERAN user plane to the GAN user plane. The GANC 4010 uses the relocation detection message to indicate to the MSC 4020 that it has detected the UE (step 14). Now, the CN can selectively switch the user plane from the source GERAN to the target GAN.

[0402] The two-way voice service now flows between the UE 4005 and the MSC 4020 through the GANC 4010 (step 15). The target GANC 4010 uses the relocation complete message to indicate the completion of the handover (step 16). CN now switches the user plane from the source GERAN to the target GAN, provided that it has not performed this operation before.

[0403] The CN uses a clear command message to tear down the connection to the source GERAN (step 17). Finally, the source GERAN 4015 uses a clear complete message to confirm the release of the GERAN resources allocated to the call (step 18).

[0404] b) The UE terminates the IuUP protocol

[0405] Some embodiments use an alternative procedure for CS handover from GERAN to GAN. Figure 41 shows the steps performed during GERAN to GAN in these embodiments. The description of the GERAN to GAN handover process assumes the following conditions: (1) UE is in an active call on GERAN; (2) UE mode selection is preferred GAN, or if it is preferred GERAN/UTRAN, the RxLev from the current serving cell is reduced Below the defined threshold. In some embodiments, the threshold may be designated as a fixed value, or may be provided to the UE through GERAN BSS in a dedicated mode; (3) The UE has successfully registered with the GANC, allowing the UE to obtain GAN system information; and ( 4) GERAN provides information about neighboring 3G cells, so that one of the cells in the 3G neighbor list matches the 3G cell information related to GANC, such as the AS-related component in the system information obtained from GANC Like that. Steps 1 to 3 are executed as the same as the description of steps 1 to 3 shown in FIG. 40 above, so they will not be repeated for the sake of simplicity.

[0406] GANC 4110 sends a GA-CSR ACTIVATE CHANNEL message to UE 4105 (step 4), including bearer path setup information, such as: (1) channel mode; (2) multi-rate codec configuration; (3) for uplink UDP port and IP address of the RTP stream; (4) Voice sample size, and instructions for Iu IP support mode. In some embodiments, GANC 4110 includes radio access bearer (RAB) parameters and Iu IP parameters (eg, Iu IP mode, where the support mode is used for AMR voice calls).

[0407] Since the Iu IP support mode is indicated, the UE 4110 sends the Iu IP INITIALISATION (Iu IP initialization) packet to the IP address and UDP port indicated in the GA-CSR ACTIVATE CHANNEL message (step 5). [0408] The MSC 4115 responds with the Iu UP INITIALISATION ACK packet (step 6). MSC4115 sends the message to the source IP address and UDP port number of the received INITIALISATION packet. UE 4105 sends GA-CSRACTIVATE CHANNEL ACK to GANC 4110 (step 7). GANC 4110 constructs a switch to UTRAN command message and sends it to CN 4115 via a relocation request confirmation message (step 8).

[0409] GANC 4110 uses GA-CSR ACTIVATE CHANNEL COMPLETE message to notify UE 4105 that RAB establishment is complete (step 9). Now, there is an end-to-end audio path between UE 4105 and MSC 4115. MSC 4115 forwards the handover to UTRAN command message in the BSSMAP handover command message to GERAN BSC 4120 (step 10), the end

Ready to switch.

[0410] GERAN BSC 4120 sends (step 11) an inter-system to UTRAN handover command message (including a handover to UTRAN command message) to the UE to initiate a handover to GAN. The UE does not switch its audio path from GERAN to GAN until the switching is completed (ie, until it sends a GA-CSR HANDOVERCOMPLETE message) to keep the audio interruption short.

[0411] The UE uses the GA-CSR handover access message to access the GANC 4110 (step 12), and provides the entire inter-system to UTRAN handover command message received from GERAN. GANC 4110 uses the relocation detection message to indicate that the MSC 4115 has detected the UE (step 13) o MSC 4115 can now selectively convert the user plane from the source GERAN to the target GANO. Now, two-way voice services pass through the GANC 4110 between the UE and the MSC Flow between 4115 (step 14).

[0412] The UE sends a GA-CSR HANDOVER COMPLETE message at the end of the handover process to indicate the completion of the handover process (step 15). It converts users from the GERAN user plane to the GAN user plane.

[0413] The target GANC 4110 uses a relocation complete message to indicate the completion of the handover (step 16) _o MSC 4115 now switches the user plane from the source GERAN to the target GAN, provided that it has not done so before.

[0414] Finally, the MSC 4115 uses a clear command message to tear down the connection to the source GERAN (step 17). The source GERAN uses the Clear Complete message to confirm the release of the GERAN resources allocated to the call (step 18).

[0415] 2. CS handover from UTRAN to GAN

[0416] a) GANC terminates Iu UP grouping

[0417] FIG. 42 shows a CS handover from UTRAN to GAN in some embodiments. The description of the UTRAN to GAN handover procedure assumes the following conditions: (1) UE is in an active call on GERAN; (2) RNC orders the UE to perform inter-frequency measurements (ie, if the GAN cell is allocated with the frequency used in UTRAN Different frequency values), (a) If the UE is in the preferred GAN mode and event 2A is configured, the UE will process the parameters related to event 2A in a GAN-specific manner (such as "Radio Resource Control (RRC) protocol specif ication, 3GPP TS 25. 331 standard, hereinafter referred to as "3GPP TS25.331") in order to carry out EGAN report; (b) When the UE is in the preferred GERAN/UTRAN mode, and the GAN cell has been configured for event 2A, when the event When triggered and the UTRAN cell from the UE's neighbor cell list does not meet the triggering conditions of the event, the UE will only send the measurement on the GAN cell (as in 3GPP TS 25. 331); (3) UTRAN provides information about neighboring cells, so that one of the cells in the neighbor list matches a cell related to GANC, such as the AS-related information in the system information obtained from GANC. As provided in the portion.

[0418] 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 (step 1). The UE 4205 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE 4205 to indicate its preference for GAN.

[0419] Based on the measurement report of the UE and other internal algorithms, the RNC 4215 decides to initiate a handover to the GAN cell. RNC 4215 initiates the preparatory phase of the relocation process (step 2) by sending a relocation requirement message for the identification target (GAN) cell to the MSC.

[0420] Next, steps 3 to 5 shown in FIG. 42 are performed as described in steps 3-5 for the GERAN to GAN handover secondary part above. The target GANC 4210 uses a relocation request confirmation message to confirm the handover request message (step 6), which indicates 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 .

[0421] Next, the MSC 4220 sends a relocation command message to the RNC 4215 to complete the relocation preparation (step 7). RNC 4215 sends a PHYSICAL CHANNEL RECONFIGURATION (PHYSICAL CHANNEL reconfiguration) message to UE 4205 to initiate the handover to GAN (step 8). The UE does not switch its audio path from UTRAN to GAN.

Until the switching is completed (ie, until it sends a GA-CSR HANDOVER COMPLETE message) to keep the audio interruption short. [0422] Next, steps 9-16 shown in FIG. 42 are performed similarly to steps 9-16 for GERAN to GAN handover described above. Next, the MSC 4220 uses the Iu release command to tear down the connection to the source RNC (step 17). Finally, the source RNC 4215 uses Iu release completion to confirm the release of the UTRAN resources allocated to the call (step 18). [0423] b) UE terminates Iu UP packet

[0424] Some embodiments use an alternative procedure for CS handover from UTRAN to GAN. Figure 43 shows the steps performed during UTRAN to GAN in these embodiments. As shown in the figure, the UE starts to include information about the GAN cell in the measurement report message sent to the RNC 4320 (step 1) ° The UE reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE to indicate its preference for GAN.

[0425] Based on the measurement report of the UE and other internal algorithms, the RNC 4320 decides to initiate a handover to the GAN cell. RNC 4320 initiates the preparation phase of the relocation process (step 2) by sending a relocation requirement message identifying the target GAN cell to MSC 4315.

[0426] The MSC 4315 uses a relocation request message to request the target GANC 4310 to allocate resources for handover (step 3). The UE 4305 is identified by the included IMSI parameters.

[0427] GANC 4310 sends a GA-CSR ACTIVATE CHANNEL message to UE 4305 (step 4), the message includes the bearer path setup information received in the relocation request message, such as: (1) For uplink RTP flow UDP port and IP address; (2) Radio Access Bearer (RAB) parameters; and (3) Iu UP parameters (for example, Iu UP mode, where the support mode is used for AMR voice calls).

[0428] Since the Iu UP support mode is indicated, the UE 4305 sends the Iu UP INITIALISATION packet to the IP address and UDP port indicated in the GA-CSR ACTIVATE CHANNEL message (step 5). The message is routed to the core network 4315 (for example, R4 media gateway).

[0429] The MSC 4315 responds with the Iu UP INITIALISATION ACK packet (step 6). The MSC 4315 sends the message to the source IP address and UDP port number of the received initialization packet. UE 4305 sends GA-CSR ACTIVATE CHANNEL ACK to GANC 4310 (step 7).

[0430] The target GANC 4310 uses a relocation request confirmation message to confirm the handover request message (step 8). The relocation request confirmation message indicates that it can support the requested handover and includes the physical information indicating the radio channel to which the UE 4305 should be directed. Channel reconfiguration message.

[0431] GANC 4310 uses the GA-CSR ACTIVATE CHANNEL COMPLETE message to notify the UE of the completion of the 4305 RAB establishment (step 9). Now, there is an end-to-end audio path between UE 4305 and MSC 4315. MSC 4315 sends the relocation command message to RNC 4320 (step 10) to complete the relocation preparation.

[0432] The RNC 4320 sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to initiate a handover to the GAN (step 11). The UE does not switch its audio path from URRAN to GAN until the switching is completed (ie, until it sends a GA-CSR HANDOVER COMPLETE message) to keep the audio interruption short. The UE uses the GA-CSR HANDOVER ACCESS message to access the GANC4310 (step (2), and provides the entire PHYSICAL CHANNELRECONFIGURATION message received from the RNC 4320.

[0433] GANC 4310 uses a relocation detection message to indicate to MSC 4315 that it has detected the UE (step 13) _o The MSC 4315 can now selectively switch the user plane from the source RNC 4320 to the target GANC 4310. Now, the two-way voice service flows between the UE and the MSC 4315 through the GANC 4310 (step 14).

[0434] From the perspective of the UE, the UE sends GA-CSR HANDOVER COMPLETE to indicate the completion of the handover process

(Step 15). The UE converts the user from the UTRAN user plane to the GAN user plane. The target GANC 4310 uses the relocation complete message to indicate the completion of the handover (step 16). CN 4315 now converts the user plane from the source RNC 4320 to the target GANC 4310, provided that it has not done so before.

[0435] Finally, the MSC 4315 uses the Iu release command to tear down the connection to the source RNC 4320 (step 17). Source RNC

4320 uses Iu release completion to confirm the release of the UTRAN resources allocated to the call (step 18).

[0436] 3. CS handover from GAN to GERAN

[0437] FIG. 44 shows a handover process from GAN to GERAN in some embodiments. The process description in this sub-item assumes the following conditions: (1) UE is in an active call in GAN Iu mode; (2) GERAN becomes available and (a) UE mode selection is preferred GERAN/UTRAN, or (b) The UE mode selection is the preferred GAN, and the UE starts to leave GAN coverage based on its local measurements, received RTCP reports, and any uplink quality indications received from GANC. The handover process from GAN to GERAN is always triggered by the UE. As shown in Figure 44, the following steps are performed during the handover from GAN to GERAN.

[0438] When there is a problem with the uplink quality for the ongoing call, GANC 4410 may send GA-CSR UPLINK QUALITY INDICATION (GA-CSR ± uplink quality indication) (step 1). The uplink quality indicator is information sent by the GANC to the UE, indicating the intersection of the uplink quality threshold in the uplink direction. Whenever the UE receives an indication of poor quality, it initiates the handover procedure as described in the next step. Alternatively, the UE may use its local measurement or received RTCP report to decide to initiate the handover process.

[0439] As shown in the figure, UE 4405 sends a GA-CSR HANDOVER INFORMATION (GA-CSR handover information) message to GANC 4410, indicating the channel mode and the order of preference for handover via CGI (for example, lost via C1 path) Parameter list) the list of identified target GERAN cells (step 2), 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-CSRHANDOVER INFORMATION message may include a list of target UTRAN cells arranged in the order of preference for handover, and the received signal strength for each identified UTRAN cell.

[0440] If the serving GANC selects the target GERAN cell, a handover procedure to GERAN is performed. The service GANC 4410 initiates handover preparation by notifying the MSC 4420 that handover is required, using relocation requirements, and including the GERAN cell list provided by the UE (step 3). GANC may only include a subset of the cell list provided by the UE.

[0441] The MSC 4420 then uses the handover request to select the target GERAN cell and request it to allocate the necessary resources (step 4). The target GERAN BSC 4415 constructs a handover command message that provides information about the allocated channel, and sends it to the MSC 4420 through a handover request confirmation message (step 5) ο

[0442] The MSC 4420 uses a relocation command message to notify the GANC 4410 to switch the UE 4405 to GERAN (step 6), and complete the handover preparation phase. GANC sends a GA-CSR handover command to the UE, including the details about target resource allocation sent through GERAN (step 7) ο

[0443] Next, the UE 4405 sends a "Um: Handover Access" message containing the handover reference element (step 8) to allow the target GERAN BSC 4415 to change the handover access from the handover previously sent to the MSC in response to the handover request. The command message is associated. The target GERAN BSC 4415 uses the handover detection message to confirm the handover detection to the MSC 4420 (step 9). [0444] At this time, the MSC 4420 can switch the user plane to the target BSS (step 10). GERAN BSC4415 provides physical information (ie, timing advance) to the UE (step 11) to allow the UE to synchronize with GERAN. The UE 4405 uses the handover complete to notify the GERAN BSC 4415 that the handover is complete (step 12).

[0445] The GERAN BSC 4415 confirms the completion of the handover to the MSC 4420 through the handover complete message (step 13). MSC

The 4420 may use the target CGI for the handover process for charging purposes.

[0446] The two-way voice service now flows between the UE 4405 and the MSC 4420 through the GERAN BSC 4415 (step 14). After receiving the handover completion confirmation, the MSC 4420 instructs the GANC to release any resources allocated to the UE through the Iu release command (step (5).

[0447] Next, GANC 4415 uses a GA-CSR release message to instruct UE 4405 to release resources (step 16).

The GANC 4410 uses the Iu release complete message to confirm the resource release to the MSC 4420 (step 17).

[0448] The UE 4405 uses the GA-CSR RELEASE COMPLETE message to confirm the resource release to the GANC 4410 (step 18). Finally, the UE 4405 can use the GA-CSR DEREGISTER (GA-CSR deregistration) message to deregister from the GANC (step 19).

[0449] 4. CS handover from GAN to UTRAN

[0450] FIG. 45 shows a handover process from GAN to UTRAN of some embodiments. The process description assumes the following conditions: (1) UE is in an active call on GAN; (2) UE can operate in all these modes of GAN, GERAN and UTRAN; (3) URRAN becomes available, and (a) UE is in GERAN/UTRAN mode is preferred, or (b) UE mode selection is preferred GAN, and the UE starts to leave GAN coverage based on its local measurements, received RTCP reports, and any uplink quality indications received from GANC. The handover process starting from the GAN is always triggered by the UE. As shown in Figure 45, the following steps are performed during the handover from GAN to UTRAN.

[0451] If there is a problem with the uplink quality for the ongoing call, the GANC 4510 can send GA-CSR UPLINK QUALITY INDICATION (step 1). The uplink quality indicator is information sent by the GANC 4510 to the UE 4505, indicating the intersection of the uplink quality threshold in the uplink direction. Whenever the UE 4505 receives an indication of poor quality, it initiates the handover procedure as described in the next step. Alternatively, the UE may use its local measurement or received RTCP report to decide to initiate the handover process.

[0452] Next, the UE 4505 sends a GA-CSR HANDOVER INFORMATION message to the serving GANC (step 2), indicating the channel mode and a list of candidate target UTRAN and GERAN cells in the order of preference for handover (step 2), and Include the received signal strength for each identified cell. UTRAN cells are identified by PLMN ID, LAC, and 3G cell identity (defined in 3GPP TS 25.331).

[0453] If the serving GANC 4510 selects UTRAN as the target RAT, a handover procedure to UTRAN is performed. The serving GANC 4510 initiates the handover preparation by notifying the MSC 4520 that handover is required (step 3), using the relocation requirement, and including the UTRAN cell list provided by the UE 4505. GANC 4510 may only include a subset of the cell list provided by UE 4505.

[0454] The MSC 4520 initiates the handover process towards the target RNC 4515 identified by the serving GANC. The MSC 4520 uses a relocation request to request the allocation of necessary resources from the target RNC 4515 (step 4). The target RNC 4515 constructs a physical channel reconfiguration message that provides information about the allocated UTRAN resources, and sends it to the MSC 4520 through a relocation request confirmation message (step 5).

[0455] Next, the MSC 4520 uses a relocation command message (including a physical channel reconfiguration message) to notify the serving GANC 4510 to switch the UE to UTRAN and complete the handover preparation phase.

[0456] The service GANC 4510 sends the GA-CSR HANDOVER COMMAND (GA-CSR handover command) to the UE (step 7), including the details of the target resource allocation sent via UTRAN. The target RNS 4515 completes the uplink synchronization on the Uu interface (step 8).

[0457] The target RNC 4515 uses a relocation detection message to confirm to the MSC that the handover is detected (step 9). MSC 4520

At this time, the user plane can be converted to the target RNS 4515 (step 10).

[0458] Next, the UE 4505 uses the completion of handover to UTRAN to notify the UTRAN RNC 4515 that the handover has been completed (step 11). The UTRAN RNC 4515 confirms the completion of the handover to the MSC 4520 through a relocation complete message (step 12). If the user plane is not converted in step 10, the MSC 4520 converts the user plane to the target RNS.

[0459] The two-way voice service now flows between the UE 4505 and the MSC 4520 through the UTRAN RNC 4515 (step 13). After receiving the handover completion confirmation, the MSC 4520 instructs the serving GANC 4510 to release any resources allocated to the UE through the Iu release command (step 14).

[0460] The serving GANC 4510 then uses the GA-CSR RELEASE message to order the UE 4505 to release the resources (step . The serving GANC 4510 uses the Iu release complete message to confirm the resource release to the MSC 4520 (step .

[0461] The UE 4505 uses the GA-CSR RELEASE COMPLETE message to confirm the resource release to the serving GANC 4510 (step 18). Finally, the UE 4505 can use the GA-RC DEREGISTER message to deregister from the service GANC 4510 (step .

[0462] N. GA-PSR connection processing

[0463] The GA-PSR connection in the Iu mode is a logical connection between the UE and the GANC for the PS domain. When the upper layer in the UE requests to establish a PS domain signaling connection and the UE is in the GA-PSR-IDLEGA-PSR idle state, (that is, when no GA-PSR connection exists), a GA-PSR connection is established. When receiving a successful response from the network, GA-PSR responds to the upper layer: the PS domain signaling connection has been established, and the UE has entered the equivalent state of the RRC connection mode (that is, the GA-PSR-CONNECTED state).

[0464] 1. GA-PSR connection establishment

[0465] FIG. 46 illustrates the successful and unsuccessful establishment of a GA-PSR connection in some embodiments. As shown in the figure, UE 4605 initiates GA-PSR connection establishment (step 1) by sending a GA-PSR REQUEST (GA-PSR request) message to GANC 4610. The message contains the establishment reason indicating the reason for the GA-PSR connection establishment. When the GANC 4610 determines that the GA-PSR connection request can be accepted, the GANC 4610 notifies the acceptance of the connection request by sending GA-PSR REQUEST ACCEPT (GA-PSR request acceptance) (step 2), and the UE enters the GA-PSR-CONNECTED state. Alternatively, when GANC4610 determines to reject the GA-PSR connection request, GANC 4610 sends GA-PSR REQUEST REJECT (GA-PSR request rejection) to UE ZC05, indicating the reason for the rejection, and completes the process.

[0466] 2. GA-PSR connection release

[0467] FIG. 47 shows the release of the logical GA-PSR connection between the UE and the GANC in some embodiments. The following steps are performed during the release. As shown in the figure, 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 (step 1).

[0468] Next, the GANC 4710 uses the Iu release complete message to confirm the resource release to the SGSN 4715 (step 2). Next, GANC 4710 uses GA-PSR RELEASE (GA-PSR release) message to order UE 4705 to release resources. Finally, the UE 4705 uses the GA-PSR RELEASE COMPLETE message to confirm the resource release to the GANC 4710 (step 4), and the GA-PSR status in the UE changes to GA-PSR-IDLEo

[0469] 0. PS Safe Mode Control

[0470] FIG. 48 shows a message flow of PS security mode control in some embodiments. As shown in the figure, SGSN4815 sends the RANAP security mode command message to GANC 4810 (step 1). The message contains the integrity key (IK) and allowed algorithms, and optionally, the encryption key (CK) and allowed algorithms.

[0471] Next, GANC 4810 cancels GA-PSR SECURITY MODE COMMAND (GA-PSR security mode command)

The information is sent to the UE 4805 (step 2). The message indicates integrity protection and encryption settings (that can be applied after relocation to UTRAN), and a random number. The UE stores this information for possible future use after relocation to UTRAN.

[0472] Next, the UE 4805 calculates the message authentication code (MAC) based on the random number, the UEs IMSI and the integrity key calculated by the UE. The UE 4805 then sends the GA-CSR SECURITY MODECOMPLETE message to the GANC 4810 (step 3 ) To inform its selected algorithm and calculated MAC.

[0473] GANC 4810 then uses the random number, the UE's IMSI, and the integrity key provided by SGAN in step 1 to verify the MAC. When GANC verifies that the MAC is correct, it sends a security mode complete message to SGSN 4815 (step 4). The MAC certification that authenticates to the GANC is the same as that authenticated to the core network.

[0474] P. PS NAS Signaling Procedure

[0475] After the GA-PSR connection is established, NAS signaling can be transmitted from the SGSN to the UE and from the UE to the SGSN.

[0476] 1. NAS signaling from SGSN to UE

[0477] FIG. 49 shows NAS signaling from SGSN to UE in some embodiments. As shown in the figure, for the NAS signaling from SGSN to UE, SGSN 4915 sends NAS PDUs to GANC via RANAP direct transmission message (step 1). GANC 4910 encapsulates the NAS PDU into GA-PSR DL to directly transmit the message, and forwards the message to UE 4905 through the existing TCP connection (step 2).

[0478] 2. NAS signaling from UE to SGSN

[0479] FIG. 50 shows UE-to-SGSN NAS signaling in some embodiments. As shown in the figure, the UE 5005 receives a request from the NAS layer to transmit the uplink NAS PDU. Assuming that the required signaling connection already exists, the UE 5005 encapsulates the NAS PDU into a GA-PSR DL DIRECT TRANSFER message and sends the message Go to GANC 5010 (step 1). The GANC 5010 relays the received message to the SGSN 5015 currently serving the UE through the RANAP direct message transmission (step 2).

[0480] Q. GA-PSR Packet Transport Channel Management Process

[0481] The GA-PSR Packet Transport Channel (GA-PSR PTC) provides the association between the UE and the network, and is used to transmit GPRS user data through the Up interface (ie, through the GAN in the Iu mode). PTC uses the GTP-U protocol that runs on UDP transmission. The endpoint address of the PTC is identified by the IP address and UDP port assigned to the UE and the PTC in the network during the PTC-ACTIVE process. The UDP port number used for GTP-U is defined in UTRAN Iu interface data transport &amp; transport signaling", 3GPP TS 25.414 standard, hereinafter referred to as "3GPP TS 25.414".

[0482] Using the same endpoint address can simultaneously activate multiple PTC events between the UE and the network. During the activation process, each PTC event is assigned a unique GTP-U tunnel endpoint ID (one for the UE and one for the network). UE and GANC manage the activation and deactivation of PTC events according to data transmission requests and configurable PTC timers.

[0483] 1. GA-PSR packet transmission channel status

[0484] The UE in the GA-PSR-CONNECTED state may be in one or two PTC sub-states: PTC-STANDBY (PTC standby) or PTC-ACTIVE (PTC active). The PTC-STANDBY sub-state is the initial/default PTC sub-state of the UE when in the GA-PSR-CONNECTED state in the GAN mode. The UE cannot send GPRS user data to the network or receive GPRS user data from the network. The UE needs to activate PTCo before sending any GPRS user data. When the UE successfully establishes a PTC, the UE transitions to the PTC-ACTIVE sub-state.

[0485] In the PTC-ACTIVE sub-state, the UE is in the GA-PSR-CONNECTED state, and the PTC is activated between the UE and the network, and the UE can send GPRS user data to or receive GPRS user data from the network. On the UE side, some events can trigger the activation of GA-PSR PTC. These events include UE initiated uplink user data transmission

Or GANC initiates PTC-ACTIVE, that is, UE receives GA-PSR-ACTIVATE-PTC-REQUEST (GA-PSR-ACTI VATE activation PTC request) message from GANC.

[0486] While successfully activating the PTC and transitioning to the PTC-ACTIVE sub-state, the UE starts the PTC timer. When the PTC timer expires, the UE sends a message to GANC to initiate PTC disablement. After successfully disabling PTC, the UE transitions to the PTC-STANDBY sub-state.

[0487] At any time in the GA-PSR-CONNECTED state and in the PTC-ACTIVE sub-state, the UE can receive a GA-PSR release message. In addition to requesting the release of the GA-PSR session, this is interpreted by the UE as an implicit PTC disable command.

[0488] At any time in the GAN mode, if the serving RR entity switches to GSM-RR/UTRAN-RRC, the GA-PSR is disconnected 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 status of the PTC timer.

[0489] The UE GA-PSR entity maintains one PTC for each activated PDP context. Whenever any uplink user data packet related to the PDP context is sent or a downlink user data packet is received, the PTC timer is restarted. The value of the PTC timer is provided to the UE as part of the GAN registration process (ie in the GA-RC REGISTER ACCEPT message).

[0490] 2. PTC Initial Activation

[0491] FIG. 51 describes the initial activation process of the packet transmission channel assuming that the UE is in the GA-PSR-IDLE state. As shown in the figure, perform the following steps. Perform the GA-PSR connection establishment process (step 1) as described in the GA-PSR connection establishment subsection above. UE 5105 transitions to GA-PSR-CONNECTED state and PTC-STANDBY sub-state. Next, perform the additional PS signaling process (step 2). Examples of these signaling procedures are described in the PDP Context Activation and Network Requested PDP Context Activation subsections below.

[0492] Next, SGSN 5115 initiates the RAB allocation process and includes RAB-ID, CN transport layer address (IP address) and CN Iu transport association (GTP-U terminal endpoint identifier, TEID) for user data (step 3 ). GANC 5110 sends a GA-PSR ACTIVATE PTC REQUEST (GA-PSR activate PTC request) message to the UE to request activation of the packet transport channel (step 4). The message includes RAB-ID, TEID assigned by GANC to UE, GANC IP address and GANC TEID. If GANC is configured to allow UE to send PTC packet (ie GTP-U message) directly to SGSN (ie the configuration shown in Figure 17 ), then GANC sets the IP address of GANC to the IP address of CN, and sets the TEID of GANC to TEID of CN; otherwise, GANC assigns the local address as the GANCIP address and the TEID assigned by GANC as the GANC TEID, and sends the information To the UE (ie the configuration described in Figure 18). UE 5105 confirms PTC-ACTIVE (step 5).

[0493] GANC 5110 sends an RAB allocation response message to SGSN 5115 (step 6) to complete the RAB allocation process. If GANC is configured to allow SGSN 5115 to send GTP-U messages directly to UE5105 (ie the configuration shown in Figure 17), GANC 5110 will set the RAN IP address to the UEs IP address and set the RAN TEID to be allocated by GANC Give the UEs TEID, otherwise, GANC assigns the local address as the RAN IP address and the TEID assigned by GANC as the RAN TEID, and sends this information to the SGSN (ie the configuration described in Figure 18).

[0494] Next, the GANC 5110 uses the GA-PSR ACTIVATE PTC COMPLETE message to notify the UE 5105 of the completion of the RAB establishment (step 7). After receiving the message, the UE transitions to the PTC-ACTIVE sub-state and starts the PTC timer. Next, perform the additional PS signaling process (step 8). Examples of these PS signaling are described in the PDP Context Activation and Network Requested PDP Context Activation subsections below. UE 5105 initiates uplink user data transmission through the established PTC (step 9), and SGSN 5115 can use the same transmission

Channel to send downlink user data packets.

[0495] 3. PTC data forwarding

[0496] FIG. 52 shows the transmission of GPRS user data packets through the GAN packet transmission channel. This scenario assumes that user data is transparently transported between the UE and the core network (ie, the configuration shown in FIG. 17). As shown in the figure, perform the following steps.

[0497] If needed, establish a GAN PTC as described in the PCT initial activation subsection above (step 1). After the GA-PSR PTC is established, the UE 5205 enters the PTC-ACTIVE sub-state and starts the PTC timer. Next, UE 5205 uses the standard GTP-U protocol as specified in GPRS Tunnelling Protocol (GTP) across the Gnand Gp interface, 3GPP TS 29.060 standard (hereinafter referred to as "3GPP TS 29.060") to initiate uplink users Data packet transmission (step 2), and restart the PTC timer.

[0498] Next, the SGSN 5215 uses the same PTC related to the specific PDP context to transmit downlink user data packets (step 3). The standard GTP-U protocol as specified in 3GPP TS 29.060 is used to transmit downlink user data packets. After receiving the downlink user data packet, the UE restarts the related PTC timer. Other uplink user data packets and downlink user data packets are respectively transmitted through the same PTC, as described in steps 2 and 3. After each transmission/reception, the UE restarts the PTC timer. If the configuration shown in Figure 18 is used, the uplink GTP-U packet can be sent from the UE to the GANC and then relayed from the GANC to the SGSN. Similarly, the downlink GTP-U packet can be sent from the SGSN to the GANC. Then relay from GANC to UE.

[0499] 4" Disabled play initiated by $

[0500] FIG. 53 describes a situation when the UE disables the packet transmission channel after the PTC timer expires. The UE is in the GA-PSR-CONNECTED state and the PTC-ACTIVE sub-state. As shown in the figure, perform the following steps.

[0501] The PTC timer associated with the activated packet delivery channel expires (step 1). The UE 5305 sends a GA-PSR DEACTIVATE PTC REQUEST (GA-PSR PTC disable request) message to the GANC 5310 (step 2). The message includes the RAB-ID to identify the PTC and indicates the normal release as the reason for the disabling. Alternatively, the UE may indicate that the PTC timer expires as the reason for disabling.

[0502] Next, GANC 5310 sends a RAB release request message to SGSN 5315 to request the release of the related RAB (step 3). The SGSN 5315 responds with the RAB allocation request indicating the release (step 4).

[0503] GANC 5310 responds to UE 5305 with a GA-PSR DEACTIVATE PTC ACK (GA-PSR PTCACK) message (step 5) to confirm successful deactivation. UE 5305 transitions to the PTC-STANDBY sub-state. GANC 5310 sends an allocation response message to inform SGSN 5315RAB that the release process has been completed (step 6).

[0504] 5. PTC reactivation initiated by MS

[0505] FIG. 54 depicts when the UE is in GA-PSR-CONNECTED (GA-PSR-connected) and PMM-CONNECTED (PMM-connected) states when in some embodiments the reactivation of the packet transmission channel is initiated The situation, for example, the PS signaling connection and the activated PDP context exist between the UE and the CN, but because the PTC timer expires, the PTC was previously disabled by the UE. As shown in the figure, perform the following steps, the UE is in the GA-PSR-CONNECTED state and the PTC-STANDBY sub-state. The UE is in the PMM-CONNECTED state (that is, the PS signaling connection and the activated PDP context exist). [0506] When the UE 5405 has a PDU to send, the UE 5405 sends a service request message (service type value "data") in the GA-PSR UL DIRECTTRANSFER message to the GANC 5410 (step 1). Next, GANC 5410 uses RANAP to directly transmit a message to forward the service request to SGSN 5415 through the existing signaling connection (step 2).

[0507] The SGSN 5415 can selectively initiate the security mode control described in the security mode control subsection above.

Control process (step 3) o SGSN 5415 sends the service acceptance message to GANC 5410 (step 4). GANC 5410 forwards the message to the UE (step 5).

[0508] Next, the UE 5405, GANC 5410 and SGSN 5415 establish a GA-PSR Packet Transport Channel (PTC) (step 6), as described in steps 3-7 of the PTC initial activation secondary part above. The UE transitions to the PTC-ACTIVE sub-state and starts the PTC timer. Finally, the UE 5405 sends an uplink PDU (step 7). Other data transfers are also possible.

[0509] 6. Network initiated PTC disable

[0510] FIG. 55 describes the situation when the network initiates the disabling of the packet transmission channel in some embodiments. The UE is in the GA-PSR-CONNECTED state and the PTC-ACTIVE sub-state. As shown in the figure, perform the following steps.

[0511] Optionally, for example, as a result of an error handling process, the GANC 5510 may initiate a PTC disabling process. If so, GANC 5510 sends RAB release request message to SGSN 5515 (step 1).

[0512] The SGSN 5515 sends an RAB allocation request to request the release of the related RAB (step 2). The release request may include one or more RABs. Next, GANC 5510 requests to disable the related GA-PSR PTC by sending a GA-PSRDEACTIVATE PTC REQUEST message to UE 5505 (step 3).

[0513] The UE 5505 transitions to the PTC-STANDBY sub-state, stops the PTC timer, and sends an acknowledgement back to the GANC (step 4). Repeat steps 3 and 4 for each additional RAB/PTC that needs to be released. Finally, GANC 5510 notifies SGSN 5515 that the release was successful.

[0514] 7. PTC reactivation initiated by the network

[0515] FIG. 56 describes the situation when the network initiates the reactivation of the packet transport channel when the UE is in the GA-PSR-CONNECTED and PMM-CONNECTED states in some embodiments. For example, the PS signaling connection and the activated PDP context are in the UE Exists between the CN and the CN, but the PTC was previously disabled by the UE. The UE is in the GA-PSR connection state and the PTC-STANDBY sub-state. The UE is in the PMM-CONNECTED state (that is, the PS signaling connection and the activated PDP context exist). As shown in the figure, perform the following steps.

[0516] When the SGSN 5615 has a PDU to be sent to the UE 5605, the SGSN 5615 can selectively initiate the security mode control process described in the security mode control subsection above (step 1). UE5605, GANC 5610 and SGSN 5615 establish a GA-PSR Packet Transport Channel (PTC) (step 2), as described in steps 3-7 of the PTC initial activation secondary part above. The UE transitions to the PTC-ACTIVE sub-state and starts the PTC timer. Finally, SGSN 5615 sends a downlink PDU (step 3). Other data transfers are also possible.

[0517] 8. Implicit PTC disabling due to UE deregistration

[0518] As part of the GAN deregistration process, the GANC needs to release all resources allocated to the UE. If the loss of the signaling connection is detected, the GAN deregistration can be initiated explicitly by the UE or implicitly initiated by the GANC (as described in the deregistration subsection above). Figure 57 shows the implicit PTC disabling process of some embodiments. Initially, one or more GA-PSRPTCs related to the UE are in the PTC-ACTIVE state. As shown in the figure, perform the following steps.

[0519] The UE 5705 or GANC 5710 initiates the GAN deregistration process for the UE 5705 (step 1). Optionally, any allocated resources related to the CS domain are released (step 2).

[0520] GANC 5710 initiates the Iu release process to release the corresponding RAB (step 3). SGSN 5715 responds with Iu release command (step 4) ο

[0521] After receiving the Iu release command, GANC 5710 locally disables all related PTCs (step 6) and uses

Iu releases a complete message in response to SGSN 5715.

[0522] R. PDP ± activated below

[0523] FIG. 58 shows a successful UE-initiated PDP context activation process in some embodiments. It is assumed that the UE is in

GA-PSR is idle. As shown in the figure, perform the following steps.

[0524] The GA-PST connection establishment process is performed as described above in the GA-PSR connection establishment subsection (step 1). GANC 5810 uses the RANAP initial UE message to establish the SCCP connection to the SGSN, and forwards the service request message (service type value "signaling") to SGSN 5815 (step 2). RANAP will be used to directly transmit messages between the GANC and the SGSN to send subsequent NAS messages between the UE and the core network.

[0525] SGSN 5815 can use standard UTRAN authentication procedures to selectively authenticate the UE (step 3). SGSN 5815 can selectively initiate the security mode control process described in the security mode control subsection above (step 4). SGSN 5815 responds with a service acceptance message (step 5). GANC5810 forwards the message to UE 5805 (step 5).

[0526] The UE 5805 then sends an Activate PDP Context Request message that provides details about the PDP context to the SGSN 5815 (step 6). This message is included in the GA-PSRUL direct transmission between UE 5805 and GANC 5810. GANC 5810 forwards the PDP Context activation request message to SGSN 5815 (step 6).

[0527] Next, UE 5805, GANC 5810 and SGSN 5815 establish a GA-PSR Packet Transport Channel (PTC) (step 7), as described in steps 3-7 of the above PTC initial activation. The SGSN 5815 uses the Activate PDP Context Accept message to indicate to the GANC that the establishment of the PDP context is complete (step 8). GANC forwards the message to the UE in the GA-PSR UL DIRECT TRANSFER message. Finally, UE 5805 and CN 5815 exchange user data transmission through the established PTC (step 9) ο

[0528] S. PDP requested by the network below activation

[0529] FIG. 59 shows a successful network request PDP context activation process in some embodiments, assuming that the UE is in the GA-PSR-IDLE state. Initially, the SGSN receives the downlink user data to be transmitted to the UE, and the related RAB is not established. The UE is in the PMM-IDLE state. As shown in the figure, SGSN 5915 sends a RANAP paging message to UE 5905 through GANC 5910 to locate the user (step 1). The paging request indicates paging for PS domain signaling.

[0530] GANC 5910 forwards the paging information to UE 5905 in the GA-PSR PAGING REQUEST (GA-PSR paging request) message (step 2). Perform the GA-PSR connection establishment process as described above in the GA-PSR connection establishment secondary part (step 3). Alternatively, the UE 5905 does not use the GA-PSR connection establishment process, but can send GA-PSR PAGING RESPONSE (GA-PSR paging response) message (step 3), and then transition to the GA-PSR CONNECTED state (step 3).

[0531] GANC 5910 establishes an SCCP connection to the SGSN, and uses the RANAP initial UE message to forward the service request message (service type value "Paging Response") (step 4) to the SGSN 5915. RANAP will be used to directly transmit the message in the GANC The subsequent NAS message between the UE 5905 and the core network 5915 is sent between 5910 and SGSN 5915.

[0532] SGSN 5915 can use standard UTRAN authentication procedures to selectively authenticate UE 5905 (step 5)-SGSN 5915 can selectively initiate the security mode control process described in the security mode control subsection above (step 6) .

[0533] Next, SGSN 5915 sends a PDP context activation request message to GANC 5910 (step 7). GANC 5910 forwards the message to UE 5905 in the GA-PSR DL direct transmission message (step 7). The UE 5905 sends an Activate PDP Context Request message that provides details about the PDP context to the SGSN 5915 (step 8). The message is contained in

The GA-PSR UL between UE and GANC is being transmitted directly. GANC 5810 forwards the PDP Context activation request message to SGSN 5915 (step 8).

[0534] UE 5905, GANC 5910, and SGSN 5915 establish a GA-PSR Packet Transport Channel (PTC) (step 9), as described in steps 3-7 of the PTC initial activation secondary part above. The SGSN 5915 uses the Activate PDP Context Accept message to indicate to the GANC that the establishment of the PDP context is complete (step 10). GANC forwards the message to the UE in the GA-PSR DL direct transmission message. Finally, UE 5905 and CN 5915 exchange user data through the established PTC (step 11) ο

[0535] T. SRNS relocation between UTRAN and GAN

[0536] The SRNS relocation procedure is performed to move one or more PS sessions between the Iu mode GAN and UTRAN. The SRNS relocation process relocates the Iu-ps connection point to GAN/UTRAN (in all cases) and SGSN (only for inter-SGSN relocation).

[0537] There is no description in this article to support the Iur interface between UTRAN and GAN. Therefore, only the combined hard handover and SRNS relocation can be applied to GAN-UTRAN SRNS relocation. Therefore, only the "including UE" relocation type is supported.

[0538] 1. SRNS relocation from UTRAN to GAN

[0539] a) Preparation phase

[0540] FIG. 60 shows the UTRAN to GAN SRNS relocation preparation phase in some embodiments. As shown in the figure, perform the following steps.

[0541] In UTRAN, UE 6005 has one or more activated PDP contexts and activated RABs. Next, UE 6005 uses the active GAN cell identification information to detect GAN 6015, executes the registration process (step 2) and enters the GA-RC-REGISTERED state.

[0542] The measurement control message (step 3) from the RNC 6010 to the UE 6005 includes the cell identity of the GAN. The UE starts to include the GAN cell information in the measurement report sent to the RNC (step 3a). In this message, the signal strength indicator of the GAN cell is set to the highest possible value.

[0543] Next, RNC 6010 decides to initiate a combined hard handover and SRNS relocation process. The decision is based on measurement reports and vendor/operator specific standards. After deciding to initiate relocation, RNC 6010 sends the relocation request to the SGSN (step 4).

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

[0545] Upon receiving the relocation request message, GANC 6015 establishes a packet transmission channel with appropriate attributes as defined in the message as required as described in steps 4, 5, and 7 of the PTC initial activation secondary part above ( Step 6). GANC 6015 then sends a relocation request confirmation to the SGSN (step 6a).

[0546] b) Execution phase

[0547] FIG. 61 shows the UTRAN to GAN SRNS relocation execution phase in some embodiments. As shown in the figure, perform the following steps.

[0548] After receiving a positive confirmation of serving the UE 6105 from the GANC 6115, the SGSN 6120 initiates the execution phase by sending a relocation command to the RNC 6110 (step 1). The RNC 6110 instructs the UE 6105 to initiate a physical layer handover by sending a physical channel reconfiguration message to move to the GAN (step 2a).

[0549] When the QoS attributes of any activated RAN require lossless sequential SDU delivery (lossless PDCP), then

The RNC 6110 initiates the forwarding of GTP PDUs to the GANC 6115 (step 2b) and also sends them to the UE 6105 in the downlink direction. The forwarding is routed through the Iu-ps interface. GANC can buffer, send, or discard these forwarded GTP PDUs on the downlink, depending on the QoS profile, network conditions, and whether it supports lossless relocation. The specific implementation is specific to the supplier and/or operator. In addition, GANC can postpone the start of downlink transmission until step 5 below to synchronize the GTP-U sequence number.

[0550] The RNC sends the forwarding SRNS context message to the GAN through the SGSN (steps 2c and 3a). In this message, the old SRNC is used to indicate the next desired sequence number of the uplink and downlink GTP-U packets to the GANC. If QoS attributes require lossless relocation and GANC supports lossless relocation, these sequence numbers are used to ensure the orderly delivery of GTP PDUs.

[0551] Upon receiving the physical channel reconfiguration message, the UE 6105 sends (step 3b) a GA-PSR-HANDOVER-COMPLETE message to the GANC 6115. After receiving this message and the forwarding SRNS context message sent from SGSN 6120 (step 3a), GANC 6115 becomes the serving RNC.

[0552] Upon receiving the GA-PSR-HANDOVER-COMPLETE message from the UE, the GANC 6115 sends a relocation detection message to the SGSN 6120 (step 4). When the UE supports lossless relocation and the QoS of one or more RABs When the attribute requires lossless relocation, the UE initiates the GTP-U sequence number exchange process with the GANC through the newly established PTC (step 5). When GANC 6115 supports lossless relocation and the QoS attributes of one or more RABs require lossless relocation, if the process has not been initiated by the UE, GANC 6115 can also initiate the GTP-U sequence number exchange process.

[0553] After completing the GTP-U sequence number exchange process, GANC 6115 sends a relocation complete message (step 6) to SGSNo. If the GTP-U sequence number exchange is skipped (due to lack of UE support and/or GAN or QoS attributes) It is not needed), the relocation completion is sent just after the relocation detection message. The activated RAB and PDP contexts now move between UE.GANC and SGSN. The SGSN 6120 then releases the Iu-ps connection with the old RNC 6110 (step 7). When the routing area of the GANC cell (indicated to the UE through the GANC) is different from the routing area under the old RNC, the UE 6105 performs the routing area update process (step 8).

[0554] 2. SRNS relocation from GAN to UTRAN

[0555] a) Preparation phase

[0556] FIG. 62 shows a GAN to UTRAN SRNS relocation preparation phase in some embodiments. As shown in the figure, perform the following steps.

[0557] In GAN, UE 6205 is in active packet flow exchange using PDP context and PTC (step 1). If there is an uplink quality problem for the ongoing session, GANC6215 can send GA-PSR UPLINK QUALITY INDICATION (step 2). The uplink quality indicator is information sent by the GANC 6215 to the UE 6205, which indicates the intersection of the uplink quality threshold in the uplink direction. Whenever the UE receives an indication of poor quality, it will initiate the relocation process, as described in the next step. Alternatively, the UE can use its local measurements to decide to initiate the handover procedure.

[0558] Next, the UE decides to initiate the relocation of the SRNS from GAN to UTRAN by sending the GA-PSR-HAND0VER-INFORMATION message to GANC 6215 (step 3). The specific criteria used for this decision will include the situation where the UE leaves GAN coverage (eg based on degraded WLAN signal quality).

[0559] GANC 6215 selects a target RNC based on the content of the GA-PSR-HAND0VER-INFORMATION message (for example, serving the RNC identified by the UE as having the best signal quality). GANC 6215 sends a relocation request message containing the selected RNC information to SGSN 6220 (step 4).

[0560] The SGSN 6220 sends a relocation request to the target RNC 6210 (step 5). RNC 6210 performs the necessary allocation of wireless point and Iu transmission resources (step 6) and returns a relocation request confirmation message to the SGSN (step 7). This message contains the channelization information that the UE needs to access UTRAN.

[0561] b) Execution phase

[0562] FIG. 63 shows the execution phase of GAN to UTRAN SRNS relocation in some embodiments. As shown in the figure, perform the following steps.

[0563] SGSN 6320 starts the execution phase (step 1) by issuing a relocation command to GANC 6315. This message contains channel access information in the target UTRAN cell. GANC 6315 sends GA-PSR-HAND0VER-COMMAND to UE 6305 (step 2a). This message contains information from the relocation command previously received in step 1. At this time, GANC can suspend GTP PDU transmission on the downlink. If GANC supports lossless SRNS relocation and any existing RAB QoS requires lossless SRNS relocation, GANC can initiate the forwarding of GTP PDUs to the destination RNC 6310 through SGSN 6320 (step 2c).

[0564] GANC 6315 also sends the forwarding SRNS context to the destination RNC through the SGSN (steps 2b and 3). As shown in the figure, the GANC sends the forwarded SRNS context message (step 2b) to the SGSN and the SGSN relays the forwarded SRNS context to the target RNC (step 3).

[0565] Upon receiving GA-PSR-HAND0VER-COMMAND, the UE immediately suspends uplink GTPPDU transmission. The UE uses the channel access parameters indicated in the message to immediately start accessing the UTRANo UE's access attempt is detected by the base station and RNC 6310, and reported to the SGSN6320 through the relocation detection message (step 4).

[0566] The UE completes the establishment and configuration of the lower layer, and sends the RRC physical channel reconfiguration completed to the target RNC6310 (step 5a). This triggers the RNC 6310 to send a relocation complete message to the SGSN 6320. At this stage, the target RNC assumes the task of SRNC for the UE.

[0567] The packet data stream is now active via UTRAN (step 6). Next, the SGSN releases the Iu-ps connection by sending an Iu release command message to the GANC (step 7a), and GANC responds to it with an Iu release complete message (step 7b). If the routing area of the cell under the target RNC is different from the routing area under the old GANC cell, the UE 6305 performs the routing area update process (step 8).

[0568] U. Short Message Service

[0569] GAN provides support for circuit switched and packet switched SMS services. The UE attached to the GAN can send and receive SMS messages through the GAN.

[0570] 1. SMS based on CS

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

[0572] The SM-CP protocol uses the GA-CSR UPLINK DIRECTTRANSFER message and the GA-CSR DOWNLINK DIRECT TRANSFER message between the UE and the GANC to effectively tunnel between the UE and the CN, where the GANC is used in the Iu-cs interface The SM-CP message is relayed by the RANAP message transmitted on it. In terms of mobility management and call control processes, secure IPSec tunnels and TCP sessions are used to provide safe and reliable SMS delivery over IP networks.

[0573] 2. PS based SMS

[0574] The delivery of PS-based SMS messages is based on the same mechanism as the delivery of PS mobility management messages and session management signaling messages. In the UE, according to the standard packet switching UMTS implementation mode, the SMS layer (including support for the CM sublayer function

Yes) Use GA-PSR layer services to deliver SMS messages. As far as mobility management and session management signaling are concerned, secure IPSec channels and TCP sessions are used to provide safe and reliable PS-based SMS delivery over IP networks.

[0575] VI. Configuration Information

[0576] A. GAN UARFCN and main scrambling code for switching to GAN

[0577] In some embodiments, the following guidelines are used to select the UMTS absolute radio frequency channel number (UARFCN):

[0578] 1. UARFCN should be allocated according to the allocated UARFCN value of the operator.

[0579] 2. It is hoped that UARFCN will have the same unique number on the entire operator's network to minimize the effort of RNC configuration.

[0580] 3. The primary scrambling code (possible values from 0 to 511) should be allocated according to the value in use by the operator (ie the code used by the macro cell).

[0581] 4. It is hoped that the primary scrambling code is the same and unique number on the entire operator network to minimize the effort of RNC configuration.

[0582] Several options are discussed in more detail below.

[0583] 1. Option 1

[0584] Some embodiments allocate GAN UARFCN according to the DCS frequency band used for GSM. This will result in a DL UARFCN in the range of 1162 to 1513 (including 1162 and 1513). In this scheme, there is no restriction on the selection of a specific primary scrambling code (PSC) for GAN, and any one of the 512 values can be used for specific UARFCN selection.

[0585] In the case where the initial UMTS deployment is in the 1900MHz band, an analog method can be adopted, that is, using UARFCN from the 850MHz band. This will give GAN UARFCN in the range of 4357 to 4458 (including 4357 to 4458). Alternatively, UARFCN from a PCS subband that uses a non-UMTS technology can also be specified. Moreover, there is no restriction on selecting PSC in a given GAN UARFCN.

[0586] 2. Option 2

[0587] The strategy here is to use TDD unpaired spectrum and use its UARFCN range for the purpose of GAN. As part of the UMTS auction, many operators have won TDD unpaired 5MHz spectrum in addition to one or more paired FDDs. The TDD spectrum remains unused, and it may remain in this way in the foreseeable future in the near future.

[0588] Even if a specific operator does not own any TDD spectrum in a given market, it can still use unused TDD spectrum from any operator in the market. This is because it is completely harmless for the UE to perform cell search. A conflict-free process. Even if a given TDD unpaired 5MHz spectrum is used in UTRAN-TDD mode, FDD-only mobile phones may fail beyond the initial synchronization of the physical layer. Many mobile phones planned for the foreseeable future are FDD-only.

[0589] If mobile phones allow these values semantically, these UARFCNs are actually defined in 3G, and infrastructure vendors allow these UARFCN ranges to be provided in their systems, so this method is feasible. The range of UARFCN in this case is: 9504 to 9596 and 10054 to 1012L. As in the case of option 1, there is no restriction in the PSC selection of GAN.

[0590] 3. Option 3

[0591] This plan requires the use of UARFCN with free FDD spectrum for the purpose of GAN. The "idle" spectrum may or may not belong to a specific operator. In many parts of Europe and Asia, FDD spectrum is still unused because the auction bidders either go out of business, or the owner chooses not to deploy services yet due to the cost and unavailability of the equipment.

[0592] VII. Identifiers in GAN

[0593] A. Identifier for UE and General IP Access Network

[0594] The key addressing parameters of the UE and the universal IP access network are: the public IP address of the IMSKUE related to the (U)SIM in the terminal and the universal IP access point (AP-ID) of the attached address. (U) The IMSI related to the SIM is the UEs

Provided to GANC during registration. GANC maintains a record for each registered UE. For example, when GANC receives a RANAP PAGING (RANAP) message, GANC uses IMSI as an index for the appropriate UE record.

[0595] The public IP address of the UE is the source IP that appears in the outermost IP header of the packet received from the UE through the GANC-SEGW. If available, the identifier can be used by the GANC to support local services and fraud detection, or It is used by the service provider to notify that the IP flow of the managed IP network requires special QoS processing.

[0596] The universal IP access point (AP-ID) of the attached address is provided to the GANC by the UE during registration. The AP-ID can be used by GANC to support local services or used by service providers to restrict GAN access to authorized APs.

[0597] B. Service area identifier for GAN

[0598] 1. GAN service area for positioning service and charging

[0599] The Service Area Identifier (SAI) in UMTS can be used to perform location-based routing of calls for services such as emergency services, operators, announcements, and toll-free numbers. SAI can also be used by the core network to identify where calls are initiated/terminated for billing purposes. GANC provides SAI to the core network to indicate the GAN service area of the Iu mode.

[0600] a) Allocate GAN SAI based on UTRAN/GERAN positioning

[0601] In the GAN architecture of the Iu mode, the UE is directly connected to the GANC based on IP. The GAN coverage area can cover the coverage area of UTRAN/GERAN. The logical mapping between GAN cells and SAI can be done in various solutions, such as (but not limited to): (1) GAN SAI for each UTRAN/GERAN cell; (2) For each UTRAN/GERAN routing area the GAN SAI; GAN SAL · single GANC (3) for each UTRAN / GERAN may represent a location area or location of one or more regions SAI (LAI) ο

[0602] VIII. Alternative Embodiments

[0603] In some embodiments, instead of using separate CSR protocol and PSR protocol as described in the above section, a separate protocol (ie, General Access Radio Resource Control (GA-RRC)) is used. The following sections describe the architecture and messaging characteristics of the protocol layer. Only the features that are different from those in the previous embodiment are described. It is obvious to those of ordinary skill in the art that some embodiments adopt different protocols for transferring messages between the user equipment and the network controller, the access point and the network controller, or the user equipment and the access point. For example, some embodiments use RANAP messaging for communication between FAP and UNC or between HNB and HNB gateway.

[0604] A. Control plane and user plane architecture

[0605] The Iu interface standard includes support for ATM and IP-based signaling, and a user data transmission mechanism.

[0606] 1. Circuit Switched (CS) Domain

[0607] a) CS domain-control plane

[0608] FIG. 64 shows a GAN architecture supporting a CS domain control plane of some embodiments. The figure shows the different protocol layers used for UE 6405, general IP network 6410&gt;GANC 6415 and MSC 6420. Figure 64 also shows the main features of the CS domain control plane architecture of the two interfaces Up 6425 and Iu-cs 6430o GAN as follows: The following access layer 6435 and transport IP layer 6440 provide common IP between UE 6405 and GANC 6415 Connectivity. The IPSec layer 6445 provides encryption and data integrity between UE 6405 and GANC 6415. The remote IP layer 6450 is the "internal" IP layer used for the IPSec tunnel mode, and the UE 6405 uses this layer to be addressed by the GANC 6415. The remote IP layer 6450 is configured during the establishment of the IPSec connection.

[0609] In some embodiments, a separate TCP connection 6455 is used to reliably transmit GA-RC 6460 and GA-CSR 6465 signaling between UE 6405 and GANC 6415. TCP connection 6455 is managed through GA-RC6460 and uses remote

The process IP layer comes to 6450 and can be transmitted.

[0610] The General Access Resource Control (GA-RC) protocol 6460 manages Up sessions, including GAN discovery and registration procedures. The General Access Radio Resource Control (GA-RRC) protocol 6465 uses the following connections managed by the GA-RC sublayer 6460 to perform functions equivalent to UMTS-RRC. Note that GA-RRC6465 includes signaling information related to CS service and PS service. GANC 6415 terminates the GA-RRC protocol 6465, and interacts with the RANAP protocol 6470 on the Iu-cs 6430 interface. The NAS protocol is transparently transported between the UE 6405 and the MSC 6420, such as the above MM 6475. In some embodiments, the Iu-cs signaling transport layer 6495 is based on 3GPP TS 25.412.

[0611] b) CS domain-user plane

[0612] FIG. 65 shows the GAN protocol architecture supporting the CS domain user plane in some embodiments. The figure shows the different protocol layers used for UE 6505, general IP network 6510, GANC 6515 and MSC 6520. Figure 65 also shows two interfaces Up 6525 and Iu-cs 6530. The main features of GAN's CS domain user plane architecture are as follows. The following access layer 6535 and transport IP layer 6540 provide general IP connectivity between UE 6505 and GANC 6515.

[0613] The IPSec layer 6545 provides encryption and data integrity. The Iu User Plane (Iu UP) protocol 6550 running on RTP/UDP (6555 and 6560) is used to transmit CS domain user plane data between the UE 6505 and the MSC 6520. Each Iu UP protocol 6550 instance can operate in transparent mode or support mode, as described in "UTRAN Iu interface user plane protocols", 3GPP TS 25.415. The RANAP is used by the MSC to indicate the mode selection to the GANC, or the GA-RRC is used by the GANC to indicate the mode selection to the UE. When operating in GAN mode, support for AMR speechcodec as specified in the General description3GPP TS 26.071 standard is mandatory, while supporting other codecs is optional. In some embodiments, the Iu-cs data transport layer 6595 is according to 3GPP TS 25.414.

[0614] Some embodiments of the GA-RRC protocol are used to implement a protocol stack for GANC, which is different from the protocol stack shown for GANC 6515. In some embodiments, the GANC protocol stack is similar to the GANC 1115 protocol stack shown in FIG. 11. In some embodiments, 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 transfer layer 6595. Similar to the GANC 1115 shown in Figure 11, the GANC in these embodiments enables the CS domain user plane to interact between RTP/UDP and Iu user plane protocols.

[0615] 2. Packet Switched (PS) Domain

[0616] a) PS domain-control plane

[0617] FIG. 66 shows a GAN architecture supporting the PS domain control plane in some embodiments. The figure shows the different protocol layers used for UE 6605, general IP network 6610&gt;GANC 6615 and SGSN 6620. Figure 66 also shows two interfaces Up 6625 and Iu-ps 6630. The main features of GAN's PS domain control plane architecture are as follows: GA-RRC 6635 and the functions of the lower layers are as described in the above sub-part "CS Domain-Control Plane". The GA-RRC protocol 6635 uses the following Up session managed by the GA-RC 6640 to perform functions equivalent to the UTRAN RRC protocol. GA-RRC 6635 includes CS services and signaling messages related to PS services.

[0618] GANC 6615 terminates the GA-RRC protocol 6635, and interacts with the RANAP protocol 6645 on the Iu-ps interface 6630. For example, the NAS protocol 6650 for GMM, SM, and SMS is transparently transmitted between the UE 6605 and the SGSN 6620. In some embodiments, the Iu-ps signaling transport layer 6695 is in accordance with 3GPP TS 25.412.

[0619] b) PS domain-user plane

[0620] FIG. 67 shows a GAN architecture for the PS domain user plane in some embodiments. The figure shows the different protocol layers used for UE 6705, general IP network 6710, GANC 6715 and SGSN 6720. Figure 67 also shows two interfaces

Up 6725 and Iu-ps 6730. The main features of GAN's PS domain user plane architecture are as follows: The following access layer 6735 and transport IP layer 6740 provide universal connectivity between UE 6705 and GANC 6715. The IPSec layer 6745 provides encryption and data integrity. The GTP-U 6750 protocol operates between the UE 6705 and the SGSN 6720, and transmits the upper layer payload (that is, the PS domain user plane data 6755) through the Up 6725 and the Iu-ps interface 6730. User data is transparently transmitted between the UE 6705 and the core network. In some embodiments, the Iu-ps data transmission lower layer 6795 is based on 3GPP TS 25.414. [0621] Some embodiments using the GA-RRC protocol implement a protocol stack for GANC, which is different from the protocol stack shown for GANC 6715. In some embodiments, the GANC protocol stack is similar to the GANC 1815 protocol stack shown in FIG. 18. In these embodiments, GANC has additional protocol layers above the IPSec layer 6745: remote IP, UDP, and GTP-U. In these embodiments, GTP-U in the UE and GTP-U above the UDP layer in the GANC U layer is GA-RRC Part of the agreement. GA7C also has additional IP, UDP and GTP-U layers above the data transmission lower layer 6795. [0622] 3. GA-RC (General Access Resource Control)

[0623] The GA-RC protocol provides a resource management layer with the following functions: discovering and registering with the GANC, registering and updating with the GANC, keeping the application layer active for the GANC, and supporting the identification of APs used for GAN access.

[0624] 1. GA-RC sublayer status

[0625] FIG. 68 shows the GA-RC sublayer in the UE in some embodiments. As shown in the figure, the GA-RC sublayer in the UE can be in one of two states: GA-RC-DEREGISTERED 6805 or GA-RC-REGISTERED 6810. In the GA-RC-DEREGISTERED state 6805, the UE may be in the GAN coverage area, but the UE has not successfully registered with the GANC. When in the GA-RC-DEREGISTERED state 6805, the UE can initiate the GAN registration process. When the TCP or IPSec connection is lost or when the GAN deregistration process is performed, the UE returns to the GA-RC-DEREGISTERED state 6805. [0626] In the GA-RC-REGISTERED state 6810, the UE is registered with the serving GANC. The UE has an IPSec tunnel and a TCP connection established to the serving GANC. Through the IPSec tunnel and the TCP connection, the UE can exchange GA-RC or GA-RRC signaling messages with the GANC. When the UE remains in the GA-RC-REGISTERED state 6805, the UE performs application layer and GANC keep active.

[0627] In the GA-RC-REGISTERED state, the UE can be in UTRAN/GERAN mode 6815 or GAN mode 6820. The UE (1) can be located on GERAN or UTRAN and idle; (2) can be active in GERAN or UTRAN ( For example, GSM RR or UTRAN RRC connection can be established); (3) can "roam to" GAN mode; or can "roam out" GAN mode recently (for example, due to handover from GAN).

[0628] 4. GA-RRC (General Access Radio Resource Control)

[0629] The GA-RRC protocol provides a resource management layer, which is a substitute for UTRAN-RRC and provides the following functions: (1) Establish a transmission channel for CS and PS services between UE and GANC; (2) PS service (4) Direct transmission of NAS messages between the UE and the core network; (5) Other functions such as paging and security configuration; support CS and PS switching between UTRAN/GERAN and GAN; directly transmit NAS messages between UE and core network;

[0630] The GA-RRC sublayer in the UE can be in two states: GA-RRC-IDLE 6825 or GA-RRC-CONNECTED 6830, as shown in FIG. 68. When the UE switches the serving RR entity to GA-RRC and the SAP between NAS and GA-RRC is activated, the UE enters the GA-RRC-IDLE6825 state. This switch can only occur when GA-RC is in the GA-RC-REGISTERED state. When the GA-RRC connection is established, the UE moves from the GA-RRC-IDLE state 6825 to the GA-RRC-CONNECTED state 6830, and returns to the GA-RRC-IDLE state when the GA-RRC connection is released. After the GA-RRC connection is released, the indication that there is no dedicated resource is passed to the upper layer. When the handover to GAN is being performed, the UE can also enter the GA-RRC-CONNECTED state when in the GA-RC-REGISTERED state in the GERAN/UTRAN mode.

Similarly, when the handover to GAN is successfully performed, the UE enters the GA-RC-REGISTERED state in the GERAN/UTRAN mode from the GA-RRC-CONNECTED state.

[0631] B. Advanced Process

[0632] 1. GA-RRC connection processing

[0633] The GA-RRC connection is a logical connection of the CS domain or the PS domain between the UE and the GANC. When the upper layer in the UE requests the GA-RRC to establish a signaling connection and the UE is in idle mode (no RRC connection exists), the GA-RRC connection is established. When receiving a successful response from the network, GA-RRC responds to the upper layer: it has entered the RRC connection mode. The upper layer may then request to send the NAS message to the network.

[0634] a) GA-RRC connection establishment

[0635] i) GA-RRC connection establishment initiated by the UE

[0636] FIG. 69 illustrates the successful (and unsuccessful) establishment of a GA-RRC connection when initiated by the UE according to some embodiments. The UE 6905 initiates the establishment of the GA-RRC connection by sending the GA-RRC REQUEST message to the GANC 6910 (step 1). This message contains the establishment reason indicating the reason for the GA-RRC connection establishment. The message also includes the domain indicator (CS or PS). GANC 6910 sends a successful response to UE 6905 by sending GA-RRCREQUESTACCEPT (step 2), and UE 6905 enters GA-RRC connection mode. Alternatively, GANC 6910 may return a GA-RRCREQUEST REJECT indicating the reason for rejection (step 3).

[0637] ii) GA-RRC connection establishment initiated by the network

[0638] FIG. 70 shows the successful establishment of a GA-RRC connection when initiated through the network in some embodiments. CN 7015 sends a RANAP paging message to GANC 7010 identified by the last location update received by it (step 1), and includes TMSL if available. The IMSI of the paged UE is always included in the request. The indicator (CS or PS) is the same. The paging reason can also be included.

[0639] Next, GANC 7010 uses the IMSI provided through CN 7015 to identify the UE registration context. GANC 7010 then uses GA-RRC PAGING REQUEST message to page UE 7005 (step 2). The UE 7005 responds with a GA-RRC INITIAL DIRECT TRANSFER message (step 3), which contains the NAS message and reason suitable for the domain indicator (CS or PS). Alternatively, the UE 7005 responds with a GA-RRCPAGING RESPONSE message including a NAS message, a domain indicator (CS or PS), and a reason (step 3). UE 7005 enters GA-RRC connection mode. GANC 7010 establishes an SCCP connection to CN 70015. GANC 7010 then uses the RANAP initial UE message to forward the NAS message to CN 7015 (step 4). The RANAP direct transmission message will be used to send subsequent NAS messages between the UE and the core network between the GANC and the CN.

[0640] b) GA-RRC connection release

[0641] FIG. 71 shows the release of the logical GA-RRC connection between the UE and the GANC in some embodiments. CN 7115 instructs GANC 7110 to release the user plane connection allocated to UE 7115 through the RANAP Iu release command message (step 1). GANC 7110 uses Iu release complete message 7125 to confirm the resource release (step 2).

[0642] Next, the GANC 7110 uses the GA-RRC CONNECTION RELEASE message to order the UE 7105 to release resources (step 3). The UE 7105 uses the GA-RRC CONNECTION RELEASECOMPLETE message to confirm the resource release to the GANC 7110 (step 4), and the GA-RRC status in the UE changes to idle.

[0643] c) GA-RRC connection release request

[0644] FIG. 72 illustrates the release of the logical GA-RRC connection between the UE and the GANC when initiated by MS or GANC (ie due to abnormal conditions) according to some embodiments. If the UE or GANC wants to release the signaling connection with the specific CN domain

Connect (and related RAB) while maintaining the GA-RRC connection (for example, releasing the PS domain signaling connection but maintaining the CS domain signaling connection), then this situation applies.

[0645] In this figure, UE 7205 initiates GA-RRC connection release (or CN domain signaling connection release) by sending a GA-RRC RELEASE REQUEST message to GANC 7210 (step 1). The message includes the CN domain identifier (ie, domain indicator) whose value is set to CS or PS, and the reason indicating the reason for the GA-RRC connection release.

[0646] Upon receiving the GA-RRC RELEASE REQUEST from the UE 7205 or due to the local conditions in the GANC 7210, the GANC initiates the Iu for the specific CN domain by sending an Iu release request message to the CN domain entity 7215 (step 2) freed. CN 7215 triggers the release of the above connection (step 3).

[0647] 3. Safe Mode Control

[0648] FIG. 73 shows a message flow for security mode control in some embodiments. CN 7315 sends the RANAP safety mode command message to GANC 7310 (step 1). The message contains the integrity key (IK) and allowed algorithms, and optionally, the encryption key (CK) and allowed algorithms. GANC 7310 sends the GA-RRC SECURITY MODE COMMAND message to UE 7305 (step 2). The message indicates integrity protection and encryption settings (ie, applicable after relocation to UTRAN), and a random number. The UE 7305 stores this information for possible future use after handover to UTRAN.

[0649] Next, the UE 7305 calculates the MAC based on the random number, the UE's IMSI, and the integrity key calculated by the UE. UE 7305 then sends GA-RRC SECURITY MODE COMPLETE to inform it of the selected algorithm and calculated MAC (step 3). GANC 7310 then uses the random number, the UE's IMSI and the integrity key provided by CN 7315 in step 1 to verify the MAC. If the GANC verifies that the MAC is correct, it sends a security mode completion message to CN 7315 (step 4) o MAC proves that the ID for authentication to GANC is the same as the ID for authentication to the core network.

[0650] 4. GA-RRC NAS signaling process

[0651] After the GA-RRC connection is established, NAS signaling can be transmitted from the CN to the UE or from the UE to the CN.

[0652] a) NAS signaling from CN to UE

[0653] FIG. 74 shows NAS signaling from the core network to the UE in some embodiments. For the NAS signaling from CN to UE, the core network 7415 sends the NAS PDU to the GANC through the RANAP direct transmission message (step 1). GANC 7410 encapsulates the NAS PDU into the GA-RRC DL DIRECT TRANSFER message, and forwards the message to the UE 7405 through the existing TCP connection (step 2) o GANC 7410 inserts the CN domain ID based on the CN domain, and GANC 7410 sends the message from the CN The domain receives the direct delivery message.

[0654] b). NAS signaling from UE to CN

[0655] FIG. 75 shows NAS signaling from the UE to the core network in some embodiments. The GA-RRC layer of the UE 7505 receives a request from the NAS layer to deliver the uplink NAS PDU. Since the MM connection (the RR signaling connection) already exists, the GA-RRC of the UE encapsulates the NAS PDU into the GA-RRC UL DIRECTTRANSFER message , And send the message to GANC 7510 (step 1). The GA-RRC UL DIRECTTRANSFER message includes the CN domain ID and NAS-PDU. GANC 7510 directly transmits message 7520 through RANAP to relay the received message to core network 7515 (step 2).

[0656] Some embodiments provide a method and technique for explicitly indicating the initiation of a communication session within an unlicensed mobile access (UMA) network or a universal access network (GAN). In order to facilitate the explicit indication of the start of the communication session, some embodiments use a new message, namely the GA-RRC INITIAL DIRECT TRANSFER message, to replace the first exchanged between the user equipment (UE) and the UMA network or the GAN network controller. DIRECT TRANSFER message. In some embodiments, the GA-RRC IMTIAL DIRECTTRANSFER message is a new message type that distinguishes the message from UPLINK DIRECTTRANSFER

Message and DOWNLINK DIRECT TRANSFER message. In some embodiments, the GA-RRC INITIAL DIRECT TRANSFER message includes an intra-domain NAS node selector (IDNNS), which is to be used by the UMA network or GAN network controller to establish and route the signaling connection to the indicated core network domain Core network node. It is obvious to those of ordinary skill in the art that the GA-RRC INITIAL DIRECT TRANSFER message is an exemplary message for the GA-RRC protocol, and different names can be used for the GA-RRC INITIAL DIRECT TRANSFER message. In addition, it is obvious to those of ordinary skill in the art that different embodiments of UMA networks and GANs and different protocols for UMA networks and GANs similarly use the following INITIAL DIRECT TRANSFER messages described according to some embodiments of the present invention. And the corresponding function.

[0657] FIG. 76 shows the NAS signaling from the initial UE to the core network. The GA-RRC layer of UE 7605 receives a request from the NAS layer to establish a signaling connection to CN 7615. The request also includes a request for the delivery of uplink NAS PDUs. The UE 7605 encapsulates the NAS PDU into the GA-RRC INITIAL DIRECTTRANSFER message and sends the message to GANC 7610 (step 1). The message includes the CN domain identification (identification CS or PS). In some embodiments, the message also includes an intra-domain NAS node selector (IDNNS), which is to be used by the GANC to route the establishment of a signaling connection to the CN node in the indicated CN domain.

[0658] After receiving the GA-RRC INITIAL DIRECT TRANSFER message, the GANC 7610 establishes a signaling connection to the indicated CN domain entity, and the GANC 7610 relays the received message to the core network 7615 through the RANAP initial UE message ( Step 2) o RANAP initial UE message includes NAS PDU. The subsequent NAS PDU from the UE 7605 to the CN domain entity is transmitted in the GA-RRC INITIALDIRECT TRANSFER message, as shown in Figure 75 above. Moreover, the NAS PDU from the CN domain to the UE 7605 is transmitted in the GA-RRC DOWNLINK DIRECT TRANSFER message, as shown in Figure 74 above.

[0659] In some embodiments, the explicit indication of the initiation of the session from the UE to the GANC eliminates the monitoring overhead and releases the resources of the GANC to perform other operations. Without this explicit message transfer (ie GA-RRCINITIAL DIRECT TRANSFER), GANC will continue to monitor every incoming GA-RRCUL DIRECT TRANSFER message from the UE after establishing a connection with the UE (ie through the GA-RRCREQUEST message) To determine whether to start a new session. Specifically, GANC no longer needs to parse and analyze each incoming GA-RRC UL DIRECT TRANSFER to determine the start of a new session. Moreover, in some embodiments, the initiation of the session is indicated explicitly by receiving a GA-RRC INITIALDIRECT TRANSFER message.

[0660] It is obvious to a person of ordinary skill in the art that some embodiments of the present invention perform such an explicit indication of the initiation of a session to other messaging protocols and the interface of the UMA network and the GAN. For example, the equivalent INITIAL DIRECT TRANSFER message can be used in the GA-CSR and GA-PSR messaging protocols.

[0661] Similarly, in the message transmission between the femtocell and the home base station system, the equivalent INITIALDIRECT TRANSFER message can be used to explicitly indicate the initiation of the session, where the message is used for the FAP and GANC or the home base station and the home base station. Between gateways. Figure 77 shows initial UE to core network NAS signaling in the context of a femtocell/home base station system according to some embodiments.

[0662] As shown in the figure, the UE 7705 indicates that it wishes to establish a signaling connection to the CN 7715 by sending a message including the CN domain identifier and IDNNS parameters (step 1). The FAP 7720 processes the request and transmits the INITIALDIRECT TRANSFER message to the network controller 7710 (for example, the gateway GANC of the home base station, etc.) (Step 2) o The INITIAL DIRECT TRANSFER message also includes the CN domain identification and IDNNS parameters received from the UE 7705. The network controller 7710 then passes the initial UE request message to the CN 7715 (step 3). In some embodiments, FAP 7720 is the home base station or

Other tall-based stacked picocell access points operated jointly by UMA network, GAN or other unlicensed networks.

[0663] 5. CS call originating from mobile device

[0664] a) The UE terminates the Iu UP packet

[0665] FIG. 78 shows a CS call process starting from a mobile device in some embodiments. The description of this process assumes that UE 7805 is in GAN mode, that is, UE 7805 has successfully registered with GANC 7810, and GA-RRC is the serving RR entity in UE 7805. It is also assumed that there is no GA-RRC connection between UE 7805 and GANC 7810 (ie, GA-RRC-IDLE state). Perform the GA-RRC connection establishment process (step 1) as described in the above sub-part "GA-RRC connection establishment initiated by the UE". In the case of a request from the upper layer, the UE 7805 sends a CM service request to GANC 7810 in a GA-RRC INITIAL DIRECT TRANSFER message (step 2).

[0666] GANC 7810 establishes an SCCP connection to MSC 7815, and uses RANAP initial UE message to forward the CM service request to CN 7815 (step 3). RANAP will be used to directly transmit messages between GANC 7810 and CN 7815 to send subsequent NAS messages between UE 7805 and core network 7815.

[0667] CN 7815 can use the standard UTRAN authentication process to selectively authenticate UE 7805 (step 4). CN 7815 can selectively initiate the security mode control process described in the above subsection "Security Mode Control" .

[0668] UE 7805 sends to CN 7815 a setup message (step 6) that provides call details and its bearer capabilities and supported codecs. This message is contained in the GA-RRC ULDIRECTTRANSFER between UE 7805 and GANC 7810. GANC 7810 forwards the setup message to CN 7815 (step 6).

[0669] CN 7815 uses the call continuation message to GANC 7810 to indicate that it has received call setup and will not accept other call setup information (step 7). GANC 7810 forwards the message to UE 7805 in the GA-CSR DL DIRECTTRANSFER message (step 7) ο

[0670] CN 7815 uses RANAP RAB allocation request message to request GANC 7810 to allocate call resources (step 8). CN 7815 includes RAB-ID, CN transport layer address (IP address) and CN Iu transport association (UDP port number) for user data. GANC 7810 sends the GA-RRC ACTIVATE CHANNEL message to UE 7805 (step 9), which includes the bearer path setup information received in the RAB allocation request message, such as: (1) Radio Access Bearer (RAB) parameters, such as RAB -ID, the UDP port and IP address used for the uplink RTP stream; and (2) Iu UP parameters (for example, Iu UP mode, where the support mode is used for ARM voice calls).

[0671] Since the Iu UP support mode is indicated, the UE 7805 sends the Iu UP INITIALISATION packet to the IP address and UDP port indicated in the GAP-RRC ACTIVATE CHANNEL message (step 10). The message is routed to the core network 7815 (eg, R4 media gateway). The core network 7815 responds with an IuINITIALISATION ACK packet (step 11). The core network 7815 sends the message to the IP address and UDP port in the received INTIALISATION packet.

[0672] UE 7805 sends GAP-RRC ACTIVATE CHANNEL ACK to GANC 7810 (step 12). GANC informs CN 7815 that the RAB has been established by sending a RANAP RAB allocation response message (step 13). GANC 7810 uses GAP-RRC ACTIVATE CHANNEL COMPLETE message to notify UE 7805 RAB establishment is completed (step 14).

[0673] Now, there is an end-to-end audio path between UE 7805 and CN 7815. UE 7805 can now connect users to this audio path. CN 7815 uses alarm messages to notify UE 7805 that the called party is ringing. The message is transmitted to GANC 7810 (step 15), GANC uses GA-RRC DLDIRECT TRANSFER to forward the message to the UE

7805 (Step .

[0674] When the UE 7805 has not connected the audio path to the user, it generates a ring back to the calling party. Otherwise, the ringback generated by the network will be returned to the calling party. CN 7815 informs via connection message that the called party has answered. The message is transmitted to GANC 7810 (step 16), and the GANC forwards the message to the UE in GA-RRC DL DIRECTTRANSFER 7895 (step 16). The UE 7805 connects the user to the audio path. If the UE 7805 is generating ringback, it stops and connects the user to the audio path.

[0675] In response to this, the UE 7805 sends a connection confirmation message (step 17), and the two parties are connected to make a voice call. This message is contained in the GA-RRC UL DIRECTTRANSFER between UE 7805 and GANC 7810. GANC forwards the connection confirmation message to CN 7815 (step 17). Two-way voice services flow between UE 7805 and CN 7815 through GANC 7810 (step 18).

[0676] b) GANC terminates Iu UP grouping

[0677] Some embodiments utilize an alternative procedure to use the RRC protocol to make a CS call originating from a mobile device. Figure 79 shows the steps performed during the CS call originating from the mobile device in these embodiments. This process assumes that the UE is in the GAN mode, that is, the UE has successfully registered with the GANC, and the GA-RRC is the serving RR entity for the CS service in the UE. It is also assumed that the GA-RRC signaling connection exists between the UE and the GANC (ie, the GA-RRC-IDLE state). As shown in the figure, perform the GA-RRC connection establishment process (step 1). In some embodiments, this process is performed. Next, UE 7905 sends the CM service request message to GANC7910 in the GA-RRC UL DIRECT TRANSFER message (step 2).

[0678] Next, the GANC 7910 establishes an SCCP connection to the core network CN 7915, and uses the RANAP initial UE message to forward the NAS PDU (ie, the CM service request message) to the core network CN 7915 (step 3). The message includes a domain indicator set to the value "CS domain". RANAP will be used to directly transmit messages between the GANC and the core network CN to send subsequent NAS messages between the UE and the core network CN.

[0679] The core network CN 7915 can use the standard UTRAN authentication process to selectively authenticate the UE (step 4). The core network CN 7915 can selectively initiate the security mode control process (step 5). The UE 7905 sends to the core network CN a setup message (step 6) that provides details about the call and its bearer capabilities and supported codecs. This message is contained in the GA-RRC UL DIRECTTRANSFER between UE and GANC. GANC forwards the establishment message to the core network CN.

[0680] Next, the core network CN 7915 uses the call continuation message to the GANC to indicate that it has received call setup and will not accept other call setup information (step 7). GANC forwards the message to the UE in the GA-RRC DL DIRECTTRANSFER message (step 7).

[0681] The core network CN 7915 uses the RANAP RAB allocation request message to request the GANC 7910 to allocate call resources (step 8). The core network CN 7915 includes RAB-ID.CN transport layer address and CN Iu transport association for user data among other parameters, as well as an indication that Iu UP support mode is required.

[0682] GANC 7910 then sends a GA-CSR ACTIVATE CHANNEL message to UE 7905 (step 9), the message includes bearer path setup information, such as: (1) channel mode; (2) multi-rate codec configuration; (3) UDP port and IP address used for uplink RTP stream; and voice sample size.

[0683] Next, UE 7905 sends GA-CSRACTIVATE CHANNEL ACK indicating the UDP port used for the downlink RTP stream to GANC 7910 (step 10). Since the Iu UP support mode is indicated by the core network CN in step 8, GANC 7910 sends the Iu UPINITIALISATION packet to the core network CN (step 11).

[0684] In response to this, the core network CN responds with the Iu UP INITIALISATION ACK packet (step 12).

GANC 7910 uses the GA-RRC ACTIVATE CHANNEL COMPLETE message to notify the UE 7905 of the completion of the RAB establishment (step 13). Alternatively, steps 11 and 12 may occur before step 9.

[0685] GANC 7910 notifies the core network that CN 7915 RAB has been established by sending a RANAP RAB allocation response message (step 14). The core network CN 7915 uses an alarm message to notify the UE 3505 that the called party is ringing. The message is transmitted to GANC 7910 (step 15), and GANC forwards the message to UE 7905 in GA-RRC DLDIRECT TRANSFER (step 15). When the UE has not connected the audio path to the user, it generates a ring back to the calling party. Otherwise, the ringback generated by the network will be returned to the calling party.

[0686] Next, the core network CN 7915 notifies via a connection message that the called party has responded. The message is transmitted to GANC 7910 (step 16), and the GANC uses GA-RRC DL DIRECTTRANSFER to forward the message to the UE (step 16). The UE connects the user to the audio path. If the UE is generating ringback, it stops and connects the user to the audio path.

[0687] The UE 7905 then sends a connection confirmation message in response to this (step 17), and the two parties are connected to make a voice call. This message is contained in the GA-RRC UL DIRECTTRANSFER between UE and GANC. GANC forwards the connection confirmation message to the core network CN. At this time, the two-way voice service flows between the UE 7905 and the core network CN 7915 through the GANC 7910 (step 18).

[0688] FIG. 80 shows an alternative embodiment of a CS call process initiated from a mobile device using the explicit start session indication described above with reference to FIG. 76. The description of this process assumes that UE 8005 is in GAN mode (that is, UE 8005 has successfully registered with GANC 8010, and GA-RRC is the serving RR entity in UE 8005). It is also assumed that there is no GA-RRC connection between UE 8005 and GANC 8010 (ie, GA-RRC-IDLE state). The GA-RRC connection establishment procedure (step 1) is performed as described above and the UE enters the GA-RRC CONNECTED state. If the UE 8005 is already in the GA-RRCCONNECTED state, step 1 can be skipped. In the case of a request from the upper layer, UE 8005 sends the CN domain ID, IDNNS and CM service request to GANC 8010 in the GA-RRC INITIAL DIRECT TRANSFER message (step 2).

[0689] GANC 8010 establishes an SCCP connection to CN 8015 and uses RANAP initial UE message to forward the CM service request to CN 8015 (step 3). The message includes a domain indicator set to the value "CS domain". RANAP will be used to directly transmit messages between GANC 8010 and CN 8015 to send subsequent NAS messages between UE8005 and core network 8015.

[0690] CN 8015 can use standard UTRAN authentication process to selectively authenticate UE 8005 (step 4). Although the steps of the security mode control process described above are optional, CN 8015 can then selectively initiate the security mode control process described above.

[0691] UE 8005 sends to CN 8015 a setup message (step 6) that provides details about the call and its bearer capabilities and supported codecs. This message is contained in the GA-RRCUL DIRECT TRANSFER between UE 8005 and GANC 8010. GANC 8010 forwards the setup message to CN 8015 (step 6).

[0692] CN 8015 uses the call continuation message to GANC 8010 to indicate that it has received call establishment and will not accept other call establishment information (step 7). GANC 8010 forwards the message to UE 8005 in the GA-RRC DL DIRECTTRANSFER message (step 7) ο

[0693] CN 8015 uses RANAP RAB allocation request message to request GANC 8010 to allocate call resources (step 8). CN 8015 includes RAB-ID, CN transport layer address (IP address) and CN Iu transport association (UDP port number) for user data, assuming that the Iu-cs interface is based on IP.

[0694] The Iu bearer is established according to the Iu process (step 9). In the case of ATM-based Iu-cs interface, it includes

Exchange ALCAP signaling between GANC 8010 and CN 8015 to set up ATM virtual circuit. For ATM and IP-based Iu-cs interface types, if Iu UP support mode is required as indicated in the RANAPRAB allocation request message through CN 8015, Iu bearer establishment may also include Iu UP initialization exchange.

[0695] GANC 8010 sends a GA-RRC ACTIVATE CHANNEL message to UE 8005 (step 10), the message includes the bearer path setup information received in the RAB allocation request message, such as: (1) CN domain identifier (that is, including CS domain ); RABID provided by CN in step 8; Channel mode; Multi-rate codec configuration; UDP port and IP address for uplink RTP stream; and Voice sample size.

[0696] UE 8005 sends GA-RRC ACTIVATECHANNEL ACK indicating the UDP port used for the downlink RTP stream to GANC 8010 (step 11). GANC 8010 uses the GA-RRCACTIVATE CHANNEL COMPLETE message to notify UE 8005 that the RAB establishment is complete (step 12). GANC informs CN 8015 that the RAB has been established by sending a RANAP RAB allocation response message (step 13).

[0697] Now, there is an end-to-end audio path between IE 8005 and CN 8015. UE 8005 can now connect users to the audio path. CN 8015 uses alarm messages to notify UE 8005 that the called party is ringing. The message is transmitted to GANC 8010 (step 14), GANC forwards the message to UE 8005 in GA-RRC DL DIRECTTRANSFER (step 14) ο

[0698] When the UE 8005 has not connected the audio path to the user, it generates a ring back to the calling party. Otherwise, the ringback generated by the network will be returned to the calling party. CN 8015 informs via connection message that the called party has answered. The message is transmitted to GANC 8010 (step 15), and the GANC forwards the message to UE 8005 in GA-CSR DL DIRECTTRANSFER (step 15). UE 8005 connects the user to the audio path. If UE 8005 is generating ringback, it stops and connects the user to the audio path.

[0699] UE 8005 then sends a connection confirmation message in the response (step 16), and the two parties are connected to make a voice call. This message is contained in the GA-RRC ULDIRECT TRANSFER between UE 8005 and GANC 8010. GANC forwards the connection confirmation message to CN 8015 (step 16). Two-way voice services flow between UE 8005 and CN 8015 through GANC 8010 (step 17).

[0700] 6. Terminating the CS call on the mobile device

[0701] FIG. 81 shows a CS call process terminated at a mobile device in some embodiments. The description of this process assumes that UE 8105 is in GAN mode (ie, UE 8105 has successfully registered with GANC 8110, and GA-RRC is the serving RR entity in UE 8105. It is also assumed that there is no GA-RRC between UE 8105 and GANC 8110. RRC connection (that is, GA-RRC-IDLE state).

[0702] The call ends when the mobile device arrives at CN 8115. CN 8115 sends a RANAP paging message to the GANC 8110 identified by the most recent location update received by it (step 1). And if available, TMSL is included. The IMSI of the paged mobile device is always included in the request. It is obvious to those of ordinary skill in the art that the paging message can also be sent from the SGSN to the GANC (that is, if there is a Gs interface between the MSC/VLR and the SGSN).

[0703] GANC 8110 uses the IMSI provided through CN 8115 to identify the UE registration context. The GANC then uses the GA-RRC PAGING REQUEST message to page the UE 8105 (step 2). When available in a request from CN 8115, the message includes TMSI. Otherwise, the message only includes the IMSI of UE 8105. The message also includes the CN domain identification (CS or PS) ο

[0704] The UE 8105 responds with a GA-RRC INITIAL DIRECTTRANSFER message including a paging response in some embodiments (step 3). The message includes the CN domain identification (CS or PS). In some embodiments, the message also

Including IDNNSo UE 8105 enters GA-RRC connection mode. GANC8110 establishes an SCCP connection to CN 8115. GANC 8110 then uses the RANAP initial UE message to forward the paging response to CN 8115 (step 4). The RANAP direct transmission message will be used to send subsequent NAS messages between the UE 8105 and the core network 8115 between the GANC 8110 and CN 8115.

[0705] CN 8115 can use standard UTRAN authentication process to selectively authenticate UE 8105 (step 5). Although the procedure for normal update of the security configuration in MS through GANC 8110 is optional, CN 8115 can pass GANC 8110 Normally update the security configuration in the MS (step 6). CN 8115 uses the setup message sent to UE 8105 via GA7C 8110 to initiate call setup (step 7). GANC 8110 forwards the message to UE 8105 in the GA-RRC DL DIRECT TRANSFER message (step 7).

[0706] The UE 8105 uses GA-RRC UL DIRECT TRANSFER to respond with call confirmation after checking its compatibility with the bearer service requested in "Setup" and modifying the bearer service as needed (step 8). If the "setup" includes a signal information element, the UE 8105 uses the indicated signal to alert the user, otherwise the UE 8105 alerts the user after successfully configuring the user plane. GANC8110 forwards the call confirmation message to CN 8115 (step 8). CN 8115 uses GANC 8110 to initiate the allocation process (step 9), which triggers the establishment of the RTP stream (voice bearer channel) between GANC 8110 and UE 8105.

[0707] The UE 8105 then informs the user that it is alerting the user through the alert message contained in the GA-RRC UL DIRECT TRANSFER (step 10). GANC 8110 forwards the warning message to CN 8115 (step 10). CN 8115 sends the corresponding alarm message to the calling party. UE 8105 informs the called party that it has answered through the connection message contained in GA-RRC UL DIRECT TRANSFER (step 11)-GANC 8110 forwards the connection message to CN 8115 (step 11). CN 8115 sends the corresponding connection message to the calling party and connects to the audio. UE 8105 connects the user to this audio path.

[0708] CN 8115 confirms to GANC 8110 through a connection confirmation message (step 12). GANC 8110 forwards the message to UE 8105 in GA-RRC DL DIRECT TRANSFER (step 12). Both parties of the call are connected on the audio path. Two-way voice services flow between UE 8105 and CN8115 through GANC 8110 (step 13).

[0709] 7. CS call clear

[0710] a) CS call release

[0711] FIG. 82 shows call clearing initiated by the UE in some embodiments. As shown in the figure, UE 8205 sends a disconnect message to CN 8215 (step 1) to release the call. This message is contained in the GA-RRC UL DIRECT TRANSFER between UE 8205 and GANC 8210. GANC 8210 forwards the disconnect message to CN 8215 (ie, uses RANAP to directly transmit the message) (step 1).

[0712] CN 8215 responds to GANC 8210 with a release message (step 2). GANC 8210 uses the GA-RRC DL DIRECT TRANSFER message to forward the message to UE 8205 (step 2).

[0713] The UE 8205 responds with a release complete message (step 3). This message is contained in the GA-RRC UL DIRECT TRANSFER message between UE 8205 and GANC 8210. GANC 8210 forwards the disconnect message to CN 8215 (step 3). CN 8215 triggers the release of the connection (step 4), as described in the "GA-CSR Connection Release" subsection.

[0714] b) CS channel release

[0715] FIG. 83 illustrates CS channel release corresponding to the Iu RAB release procedure (ie, only the user plane) according to some embodiments. As shown in the figure, CN 8315 instructs (step 1) GANC 8310 to release through RANAP RAB allocation request message

RAB assigned to UE 8305 (identified by RAB ID). Next, GANC 8310 uses GA-RRC DEACTIVATE CHANNEL to order UE 8305 to release the CS user plane channel (but keep the CS signaling connection) (step 2). The message includes CN domain ID (indicating CS) and RAB ID.

[0716] The UE 8305 uses the GA-RRC DEACIVATE CHANNEL COMPLETE message to confirm the CS channel release to the GANC8310 (step 3). The CS 8305 remains in the GA-RRC-CONNECTED state. GANC 8310 uses RAB allocation response message to confirm resource release to CN 8315 (step 4) ο

[0717] c) CS channel modification

[0718] FIG. 84 illustrates a CS channel modification process that can be used by GANC to modify parameters for an ongoing call according to some embodiments. If the GANC detects "packet loss", for example, and it is impossible or desirable to switch to another GERAN/UTRAN mode, then this procedure can be used if the coding scheme is wrong or in a congested state and should be changed. In some embodiments, GANC can modify the following parameters: channel mode, sample size, IP address, and RTP UDP port.

[0719] As shown in the figure, the call is established (step 1). GANC 8410 sends a GA-RRC MODIFYCHANNEL message to UE 8405 to modify the parameters for the established call (step 2). UE8405 then uses GA-RRC MODIFY CHANNEL ACKNOWLEDGE message to respond to GANC8410 (step 3).

[0720] &amp; CS switch

[0721] a) CS handover from GERAN to GAN

[0722] i) UE terminates Iu UP packet

[0723] FIG. 85 shows a CS handover from GERAN to GAN in some embodiments. The description of the handover process from GERAN to GAN assumes the following conditions: (1) UE is in active call on GERAN; (2) UE mode selection is preferred GAN, or if GERAN/UTRAN is preferred, RxLev from the current serving cell Fell below the defined threshold. In some embodiments, the threshold may be designated as a fixed value, or may be provided to the UE through GERAN BSS in a dedicated mode; (3) The UE has successfully registered with GANC, allowing the UE to obtain GAN system information; and ( 4) GERAN provides information about neighboring 3G cells, so that one of the cells in the 3G neighbor list matches the 3G cell information related to GANC, such as the AS-related component in the system information obtained from GANC Like that.

[0724] The UE starts to include the GAN cell information in the measurement report message to GERAN (step 1). The UE reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE to indicate its preference for GAN.

[0725] Based on the measurement report of the UE and other internal algorithms, the GERAN BSC decides to switch to the GAN cell. BSC 8520 initiates handover preparation by sending a handover requirement message identifying the target 3G RNC (GANC) 8510 to CN8515 (step 2). CN 8515 uses a relocation request message to request the target GANC8510 to allocate resources for handover (step 3). The UE 8505 is identified by the included IMSI parameters.

[0726] GANC 8410 sends a GA-CSR ACTIVATE CHANNEL message to UE 8405 (step 4), including the bearer path setup information received in the relocation request message, such as: (1) UDP port for uplink RTP flow And IP address; (2) Radio Access Bearer (RAB) parameters; and (3) Iu UP parameters (for example, Iu UP mode, where the support mode is used for AMR voice calls).

[0727] Since the Iu UP support mode is indicated, the UE 8505 sends the Iu UP INITIALISATION packet to the IP address and UDP port indicated in the GA-RRC ACTIVATE CHANNEL message (step 5). The message is routed to the core network 8515 (for example, R4 media gateway).

[0728] The core network 8515 responds with the Iu UP INITIALISATION ACK packet (step 6). Core Network

8515 sends the message to the source IP address and UDP port number of the received INITIALISATION packet. UE 8505 sends GA-RRC ACTIVATE CHANNEL ACK to GANC 8510 (step 7). GANC 8510 constructs a switch to UTRAN command message and sends the message to CN 8515 via a relocation request confirmation message (step 8).

[0729] GANC 8510 uses the GA-RRC ACTIVATE CHANNEL COMPLETE message to notify UE8505 that the RAB establishment is completed (step 9). Now, there is an end-to-end audio path between UE 8505 and CN 8515. CN 8515 forwards the switch to UTRAN command message to GERAN BSC 8520 in the BSSMAP switch command message (step 10), and completes the switch preparation.

[0730] GERAN BSC 8520 sends inter-system to UTRAN handover command message (including handover to UTRAN command message) to UE to initiate handover to GAN (step 11) o UE does not switch its audio path from GERAN to GAN until handover Complete (ie until it sends a GA-RRC HANDOVERCOMPLETE message) to keep the audio interruption short.

[0731] The UE uses the GA-RRC HANDOVERACCESS message to access the GANC 8510 (step 12), and provides the entire inter-system to UTRAN handover command message received from GERAN. GANC 8510 uses a relocation detection message to indicate to CN 8515 that it has detected the UE (step 13). CN 8515 can now selectively switch the user plane from the source GERAN to the target GAN. Now, the two-way voice service flows between the UE and CN 8515 through the GANC 8510 (step 14). [0732] The UE 4005 transmits a GA-RRC HANDOVER COMPLETE message at the end of the handover process to indicate the completion of the handover process (step 15). It converts users from the GERAN user plane to the GAN user plane.

[0733] The target GANC 8510 uses a relocation complete message to indicate the completion of the handover (step 16). If CN8515 has not previously converted the user plane from the source GERAN to the target GAN, CN 8515 will now convert the user plane from the source GERAN to the target GAN.

[0734] Finally, CN 8515 uses a clear command message to tear down the connection to the source GERAN (step 17). The source GERAN uses the Clear Complete message to confirm the release of the GERAN resources allocated to the call (step 18).

[0735] ii) GANC terminates Iu UP packet

[0736] FIG. 86 shows an alternative procedure for CS handover from GERAN to GAN in some embodiments. The description of the handover process from GERAN to GAN assumes the following conditions: (1) The UE is in an active call on GERAN; (2) The UE mode selection is the preferred GAN, or if it is the preferred GERAN/UTRAN, the RxLev from the current serving cell drops to all Below the defined threshold. In some embodiments, the threshold may be designated as a fixed value, or may be provided to the UE through GERAN BSS in a dedicated mode; (3) The UE has successfully registered with the GANC, allowing the UE to obtain GAN system information; and ( 4) GERAN provides information about neighboring 3G cells, so that one of the cells in the 3G neighbor list matches the 3G cell information related to GANC, such as the AS-related components in the system information obtained from GANC Like that. As shown in the figure, UE 8605 starts to include GAN cell information into the measurement report message to GERAN BSC48615. The UE 8605 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE to indicate its preference for GAN.

[0737] Based on the measurement report of the UE and other internal algorithms, the GERAN BSC 8615 decides to switch to the GAN cell. BSC 8615 initiates handover preparation by sending a handover demand message identifying the target 3G RNC (GANC) to the MSC (8620) (step 2) ο

[0738] The core network CN (8620) uses a relocation request message to request the target GANC 8610 to allocate resources for handover (step 3). The UE is identified by the included IMSI parameters.

[0739] Since the Iu UP support mode is indicated, the GANC 8610 sends the Iu UP INITIALISATION packet to the core network CN (step 4). The core network CN uses the Iu UP INITIALISATION ACK packet to respond (step

5) ο

[0740] GANC 8610 establishes a handover to UTRAN command message and sends it to the core network CN 8620 through a relocation request confirmation message (step 6). The core network CN forwards the handover to UTRAN command message to the GERAN BSC in the BSSMAP handover command message 8615 (Step 7), complete the handover preparation.

[0741] Next, the GERAN BSC 8615 sends an inter-system to UTRAN handover command message (including a handover to UTRAN command message) to the UE 8605 to initiate a handover to GAN (step 8). The UE does not switch its audio path from GERAN to GAN until the switching is completed (that is, until it sends a GA-RRCHANDOVER COMPLETE message) to keep the audio interruption short.

[0742] The UE 8605 uses the GA-RRC HANDOVER ACCESS message to access the GANC 8610 (step 9), and provides the entire inter-system to UTRAN handover command message received from GERAN. GANC8610 sends a GA-RRC ACTIVATE CHANNEL message to UE 8605 (step 10), including bearer path setup information, such as: (1) channel mode; (2) multi-rate codec configuration; (3) for uplink RTP stream UDP port and IP address; and (4) voice sample size.

[0743] Next, UE 8605 sends GA-RRC ACTIVATE CHANNEL ACK to GANC 8610 (step 11), indicating the UDP port used for the downlink RTP stream. GANC 8610 uses GA-RRCACTIVATE CHANNEL COMPLETE message to notify UE 8605 that RAB establishment is completed (step 11).

[0744] The UE 8605 transmits a GA-RRC HANDOVER COMPLETE message at the end of the handover process to indicate the completion of the handover process (step 13). It converts users from the GERAN user plane to the GAN user plane. The GANC 8610 uses the relocation detection message to indicate to the core network CN (8620) that it has detected the UE (step 14). Now, the CN can selectively switch the user plane from the source GERAN to the target GAN.

[0745] The two-way voice service now flows between the UE 8605 and the core network CN 8620 through the GANC 8610 (step 15). The target GANC 8610 uses a relocation complete message to indicate the completion of the handover (step 16). If the CN has not previously converted the user plane from the source GERAN to the target GAN, the CN now converts the user plane from the source GERAN to the target GANo

[0746] The CN uses a clear command message to tear down the connection to the source GERAN (step 17). Finally, the source GERAN 8615 uses the Clear Complete message to confirm the release of the GERAN resources allocated to the call (step 18).

[0747] Some embodiments provide a method and technique to activate a communication channel before performing a handover from a first authorized wireless communication network to a UMA network or GAN. In this way, while minimizing the delay caused by the handover by performing the channel activation process before the handover, some embodiments perform a more efficient and seamless handover from the authorized wireless network. This function is facilitated by receiving the IMSI of the user equipment to be handed over from the MSC of the core network as part of the handover request or relocation request message sent from the core network to the GANC. Previously, this parameter was not included in the circuit-switched handover request from the core network. As a result, the functions described below are not available, and channel activation is performed only after the mobile device receives a handover command from the BSC on the GERAN side and the mobile device sends a message indicating that the mobile device has received the handover command to the GANC through the Up interface.

[0748] FIG. 87 shows a process 8700 for channel activation before handover to facilitate more seamless handover. In some embodiments, the process 8700 is performed by the GANC of GAN. Process 8700 begins by receiving a relocation request from the core network (8710). Specifically, the relocation request includes the identification parameters (for example, IMSI) of the UE, and the UE triggers the channel activation process between the UE and the GANC before the session is switched to the UMA network or GAN.

[0749] According to some embodiments, the process then performs (8720) the channel activation process. In some embodiments, the channel activation process includes passing the activation channel message from the GANC to the UE. The UE responds with an activation channel confirmation message, GANC

Then use the Activate Channel Complete message to confirm the UE's response. In some other embodiments, the channel activation process of step 8720 only includes a pair of messages exchanged between the UE and the GANC. Specifically, the GANC delivers the relocation request message to the UE, and the UE responds with the relocation request confirmation message sent to the GANC.

[0750] At this stage, the channel between the UE and the GANC is activated. After the channel activation process, GANC delivers messages to enable the core network to continue handover (8730). For example, the GANC transmits the handover to the UTRAN command to the MSC of the core network. Once the GANC receives the relocation complete message (8740), the call is switched to the UMA network or GAN (8750).

[0751] FIG. 88 shows the CS handover process from GERAN to GAN according to the early channel activation process described with reference to FIG. 87. The description of the handover process from GERAN to GAN assumes the following conditions: (1) UE is in an active call on GERAN; (2) UE mode selection is preferred GAN, or if it is preferred GERAN/UTRAN, RxLev from the current serving cell Fell below the defined threshold. In some embodiments, the threshold may be designated as a fixed value, or may be provided to the UE through GERANBSS in a dedicated mode; (3) GANC guides the UE to operate in Iu mode; and (4) GERAN provides information about neighboring 3G The cell information makes one of the cells in the 3G neighbor list match the 3G cell information related to the GANC, as provided in the AS-related component in the system information obtained from the GANC.

[0752] The UE 8805 starts to include the GAN cell information in the measurement report message to GERAN. UE8805 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE 8805 to indicate its preference for GAN.

[0753] Based on the measurement report of the UE and other internal algorithms, the GERAN BSC 8820 decides to switch to the GAN cell. BSC 8820 initiates handover preparation by sending a handover request message identifying the target 3G RNC (GANC) to CN8815 (step 2). CN 8815 uses a relocation request message to request the target GANC8810 to allocate resources for handover (step 3). The UE 8805 is identified by the included IMSI parameters.

[0754] The Iu bearer is established according to the standard Iu procedure (step 4). In the case of an ATM-based Iu-cs interface, it can include exchanging ALCAP signaling between GANC 8010 and CN 8015 to establish an ATM virtual circuit. For ATM and IP-based Iu-cs interface types, if Iu UP support mode is required as indicated in the RANAPRAB relocation request message through CN 8015, Iu bearer establishment may also include Iu UP initialization exchange.

[0755] GANC 8010 then sends a GA-RRC ACTIVATE CHANNEL message to UE 8005 (step 5), which includes the bearer path setup information received in the relocation request message, such as: (1) Radio Access Bearer (RAB) Parameters; (2) Channel mode; (4) Multi-rate codec configuration; (5) UDP port and IP address used for uplink RTP stream; and (4) Voice sample size. UE 8805 sends GA-RRC ACTIVATE CHANNEL ACK to GANC 8810 (step 6), indicating the UDP port used for the downlink RTP stream. GANC 8810 uses GA-RRC ACTIVATE CHANNEL COMPLETE message to notify UE 8805 that RAB establishment is completed (step 7). There is now an end-to-end first frequency path between UE 8805 and CN 8815.

[0756] GANC 8810 constructs a switch to UTRAN command message and sends it to CN 8815 via a relocation request confirmation message (step 8). CN 8815 forwards the switch to UTRAN command message to GERAN BSC 8820 in the BSSMAP switch command message (step 9), and completes the switch preparation.

[0757] The GERAN BSC 8820 sends the inter-system to UTRAN handover command message (including the handover to UTRAN command message) to the UE 8805 to initiate the handover to the GAN (step 10). The UE 8805 does not switch its audio path from GERAN to GAN until the switch is completed (that is, until it sends a GA-RRCHANDOVER COMPLETE message) to keep the audio interruption short.

[0758] The UE 8805 sends a GA-RRC HANDOVER COMPLETE message at the end of the handover process to indicate that the handover has been completed.

The completion of the process (step 11). UE 8805 converts users from GERAN user plane to GAN user plane. GANC 8810 uses a relocation detection message to indicate to CN 8815 that it has detected UE 8805 (step 12). Now, CN 8815 can selectively switch the user plane from the source GERAN to the target GAN. Two-way voice services now flow between UE 8805 and CN 8815 through GANC 8810 (step 13).

[0759] GANC 8810 uses a relocation complete message to indicate that the handover is complete (step 14). If CN 8815 did not switch the user plane from the source GERAN to the target GAN before, CN 8815 now switches the user plane from the source GERAN to the target GAN.

[0760] Finally, CN 8815 uses a clear command message to tear down the connection to the source GERAN (step 15). The source GERAN uses the Clear Complete message to confirm the release of the GERAN resources allocated to the call (step 16).

[0761] FIG. 89 shows an alternative embodiment of CS handover from GERAN to GAN. Steps 1-4 are the same as in Figure 88 above. However, in order to activate the channel, the group of three channel activation messages is replaced with a group of two messages. This group of two messages includes: (1) GA-RRC relocation request message sent from GANC 8910 to UE 8905 (step 5), used to initiate the channel activation process with UE 8905; and (2) sent from UE 8905 to UE 8905 The GA-RRC relocation request confirmation message of GANC 8910 (step 6) is used to confirm the activation of the channel. Once this alternative procedure is used to activate the channel, steps 7-15 correspond to steps 8-16 of Figure 88

[0762] b) CS handover from UTRAN to GAN

[0763] i) The UE terminates the IuUP packet

[0764] The description of the UTRAN to GAN handover procedure assumes the following conditions: (1) The UE is in an active call on GERAN; (2) The RNC orders the UE to perform inter-frequency measurement. When the UE is in the preferred GAN mode and event 2A is configured, the UE processes the parameters related to event 2A in a GAN-specific manner (as described in 3GPP TS25.331) for GAN reporting. When the UE is in the preferred GERAN/UTRAN mode and event 2A has been configured for the GAN cell, the UE only sends the measurement about the GAN cell. When the event is triggered and there is no UTRAN cell in the UEs neighbor cell list that matches the trigger of the event Condition (as described in 3GPP TS 25.331); (3) UTRAN provides information about neighboring cells, so that one of the cells in the neighbor list matches the cell related to GANC, as in the case of subordinate GANC As provided in the AS-related components in the obtained system information.

[0765] FIG. 90 shows the CS handover process from UTRAN to GAN in some embodiments. The UE starts to include information about the GAN cell in the measurement report message sent to the RNC 9020 (step 1). The UE reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE to indicate its preference for GAN.

[0766] Based on the measurement report of the UE and other internal algorithms, the RNC 9020 decides to initiate a handover to the GAN cell. RNC 9020 initiates the preparatory phase of the relocation process (step 2) by sending the relocation requirement message of the identification target (EGAN) cell to CN9015.

[0767] CN 9015 uses a relocation request message to request the target GANC 9010 to allocate resources for handover (step 3). The UE 9005 is identified by the included IMSI parameters.

[0768] GANC 9010 sends a GA-CSR ACTIVATE CHANNEL message to UE 9005 (step 4), which includes the bearer path setup information received in the relocation request message, such as: (1) For uplink RTP flow UDP port and IP address; (2) Radio Access Bearer (RAB) parameters; and (3) Iu UP parameters (for example, Iu UP mode, where the support mode is used for AMR voice calls).

[0769] Since the Iu UP support mode is indicated, the UE 9005 sends the Iu UP INITIALISATION packet to

The IP address and UDP port indicated in the GA-RRC ACTIVATE CHANNEL message (step 5). The message is routed to the core network 9015 (for example, R4 media gateway).

[0770] The core network 9015 responds with the Iu UP INITIALISATION ACK packet (step 6). The core network 9015 sends the message to the source IP address and UDP port number of the received INITIALISATION packet. UE 9005 sends GA-RRC ACTIVATE CHANNEL ACK to GANC 9010 (step 7).

[0771] The target GANC 9010 uses a relocation request confirmation message to confirm the handover request message (step 8). The relocation request confirmation message indicates that it can support the requested handover and includes the physical information indicating the radio channel to which the UE 9005 should be directed. Channel reconfiguration message.

[0772] GANC 9010 uses the GA-RRC ACTIVATE CHANNEL COMPLETE message to notify UE 9005 that RAB establishment is complete (step 9). Now, there is an end-to-end audio path between UE 9005 and CN 9015. CN 9015 sends the relocation command message to RNC 9020 (step 10) to complete the relocation preparation.

[0773] The RNC 9020 sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to initiate the handover to the GAN (step 11). The UE does not switch its audio path from URRAN to GAN until the switching is completed (that is, until it sends a GA-RRC HANDOVER COMPLETE message) to keep the audio interruption short. The UE uses the GA-RRC HANDOVER ACCESS message to access the GANC 9010 (step 12), and provides the entire PHYSICAL CHANNEL RECONFIGURATION message received from the RNC 9020.

[0774] GANC 9010 uses a relocation detection message to indicate to CN 9015 that it has detected the UE (step 13). CN 9015 can now selectively switch the user plane from source RNC 9020 to target GANC 9010. Now, the two-way voice service flows between the UE and CN 9015 through the GANC 9010 (step 14).

[0775] The UE sends a GA-RRC HANDOVER COMPLETE message to indicate the completion of the handover procedure from its point of view (step 15). It converts users from the UTRAN user plane to the GAN user plane. The target GANC 9010 uses the relocation complete message to indicate the completion of the handover (step 16). If CN 9015 did not switch the user plane from the source RNC 9020 to the target GANC 9010 before, CN 9015 now switches the user plane from the source RNC 9020 to the target GANC 9010. [0776] Finally, CN 9015 uses the Iu release command to tear down the connection to the source RNC 9020 (step 17). The source RNC 9020 uses Iu release completion to confirm the release of the UTRAN resources allocated to the call (step 18).

[0777] ii) GANC terminates Iu UP packet

[0778] FIG. 91 shows an alternative procedure for CS handover from UTRAN to GAN using the RRC protocol in some embodiments. The description of the UTRAN to GAN handover process assumes the following conditions: (1) The UE is in an active call on UTRAN; RNC orders the UE to perform inter-frequency measurement (that is, if the GAN cell is allocated with a frequency different from the frequency used in UTRAN Frequency value), (a) If the UE is in the preferred GAN mode and event 2A is configured, the UE will process the parameters related to the event 2A in a GAN-specific manner for EGAN reporting; (b) when the UE is in the preferred GERAN/UTRAN mode , And event 2A has been configured for the GAN cell, the UE only sends the measurement about the GAN cell. When the event is triggered and there is no UTRAN cell in the UEs neighbor cell list that meets the triggering conditions of the event (as in 3GPP TS 25 331); (3) UTRAN provides information about neighboring cells, so that one of the cells in the neighbor list matches a cell related to GANC, as in the system information obtained from GANC, which is related to AS As provided in the weight.

[0779] As shown in FIG. 91, the UE 9105 starts to include information about the GAN cell in the measurement report message sent to the RNC 9115 (step 1). The UE 9105 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE 9105 to indicate its preference for GAN.

[0780] Based on the measurement report of the UE and other internal algorithms, the RNC 9115 decides to initiate a handover to the GAN cell. RNC

9115 initiates the preparatory phase of the relocation process (step 2) by sending the relocation requirement message of the identification target (GAN) cell to the core network CN.

[0781] Next, steps 3 to 5 shown in FIG. 91 are performed similarly to steps 3-5 for the CSR UTRAN to GAN handover in the secondary part of "GANC Terminate Iu UP Packet" above, except for the message It is an RRC message (instead of CSR). The target GANC 9110 uses a relocation request confirmation message to confirm the handover request message (step 6), which indicates that it can support the requested handover and includes a physical channel reconfiguration message indicating the wireless channel to which the UE should be directed .

[0782] Next, the core network CN 9120 sends a relocation command message to the RNC 9115 to complete the relocation preparation (step 7). RNC 9115 sends a PHYSICAL CHANNEL RECONFIGURATION message to UE 9105 to initiate handover to GAN (step 8). The UE does not switch its audio path from UTRAN to GAN until the switching is completed (ie, until it sends a GA-RRC HANDOVER COMPLETE message) to keep the audio interruption short.

[0783] Next, steps 9-16 shown in FIG. 91 are performed similarly to steps 9-16 for CSR UTRAN to GAN handover in the secondary part of "GANC Terminate Iu UP Packet" described above, with the exception of Steps 9-16 in Figure 91 use the RRC protocol instead of the CSR protocol. Next, the core network CN 9120 uses the Iu release command to tear down the connection to the source RNC 9115 (step 17). Finally, the source RNC 9115 uses Iu release completion to confirm the release of the UTRAN resources allocated to the call (step 18).

[0784] As in the above GERAN to GAN handover scenario, some embodiments provide a method and technique for activating the communication channel before performing the handover from UTRAN to UMA network or GAN. The following description of the handover process from UTRAN to GAN assumes the following conditions: (1) UE is in an active call on UTRAN; (2) UE has successfully registered with GANC, allowing UE to obtain GAN system information; GANC has guided MS operation In the Iu mode; and (4) UTRAN provides information about neighboring cells, so that one of the cells in the neighbor list matches a cell related to GANC, as provided in the AS-related component of the system information obtained from GANC .

[0785] FIG. 92 shows an alternative embodiment for performing CS handover from UTRAN to GAN with early channel activation. The UE 9205 starts to include information about the GAN cell in the measurement report message to the RNC 9220 (step 1). The UE 9205 reports the highest signal level for the GAN cell. This is not the actual measured signal level on the GAN, but an artificially specified value that allows the UE 9205 to indicate its preference for GAN.

[0786] Based on the measurement report of the UE 9205 and other internal algorithms, the RNC 9220 decides to initiate a handover to the GAN cell. RNC 9220 initiates the preparation phase of the relocation process (step 2) by sending a handover requirement message identifying the target (GAN) cell to CN 9215. o CN 9215 uses a relocation request message to request the target GANC 9210 to allocate resources for handover ( Step 3). The UE 9205 is identified by the included IMSI parameters.

[0787] The Iu bearer is established according to the standard Iu procedure (step 4). In the case of an ATM-based Iu-cs interface, this can include exchanging ALCAP signaling between the GANC 9210 and CN 9215 to establish an ATM virtual circuit. For ATM and IP-based Iu-cs interface types, if Iu UP support mode is required as indicated in the RANAP relocation request message through CN 9215, Iu bearer establishment may also include Iu UP initialization exchange.

[0788] GANC 9210 then sends a GA-RRC ACTIVATE CHANNEL message to UE 9205 (step 5), which includes the bearer path setup information received in the relocation request message, such as: (1) Radio Access Bearer (RAB) Parameters; (2) Channel mode; (4) Multi-rate codec configuration; (5) UDP port and IP address used for uplink RTP stream; and (4) Voice sample size. UE 9205 sends GA-RRC ACTIVATE CHANNEL ACK to GANC 9210 (step 6), indicating the UDP port used for the downlink RTP stream. GANC 9210 uses GA-RRC ACTIVATE CHANNEL COMPLETE

The message informs the UE 9205 that the RAB establishment is completed (step 7). There is now an end-to-end first frequency path between UE 9205 and CN 9215.

[0789] GANC 9210 uses a relocation request confirmation message to confirm the relocation request message (step 8). The relocation request confirmation message indicates that it can support the requested handover and includes the physical information indicating the radio channel to which the UE 9205 should be directed. Channel reconfiguration message.

[0790] CN 9215 sends a relocation command message to RNC 9220 to complete the relocation preparation (step 9). RNC 9220 sends a PHYSICAL CHANNEL RECONFIGURATION message to UE 9205 to initiate handover to GAN (step 10). The UE 9205 does not switch its audio path from UTRAN to GAN until the switching is completed (ie, until it sends a GA-RRC HANDOVER COMPLETE message) to keep the audio interruption short.

[0791] The UE 9205 sends a GA-RRC RELOCATION COMPLETE message at the end of the handover process to indicate the completion of the handover process (step 11). The UE 9205 converts the user from the UTRAN user plane to the GAN user plane. GANC 9210 uses a relocation detection message to indicate to CN 9215 that it has detected UE 9205 (step 12). Now, CN 9215 can selectively switch the user plane from the source UTRAN to the target GAN. Two-way voice services now flow between UE 9205 and CN 9215 through GANC 9210 (step 13).

[0792] GANC 9210 uses a relocation complete message to indicate that the handover is complete (step 14). If CN 9215 did not convert the user plane from the source GERAN to the target GAN before, CN 9215 now converts the user plane from the source GERAN to the target GAN. CN 9215 then uses the Iu release command message to tear down the connection to the source RNC 9220 (step 15), and the RNC 9220 uses the Iu release complete message to confirm the release of the UTRAN resources allocated to the call (step 16).

[0793] FIG. 93 shows a second alternative embodiment for performing CS handover from UTRAN to GAN with early channel activation. As shown in the figure, steps 1-4 correspond to steps 1-4 in FIG. 92. However, different channel activation procedures appear in steps 5 and 6. Specifically, GANC 9310 passes the GA-RRC relocation request message to the UE 9305 (step 5). The UE 9305 then responds with a GA-RRC relocation request confirmation message (step 6) to indicate the successful activation of the channel. Once the channel is activated, step 7-15 mirrors step 8T6 of Figure 92 in switching the communication session from UTRAN to GAN.

[0794] c) CS handover from GAN to GERAN

[0795] The process description in this sub-item assumes the following situations: (1) UE is in an active call on EGAN; (2) GERAN becomes available; and (i) UE mode selection is preferred GERAN/UTRAN, or (II) is preferably selected GAN mode UE, and the UE based on its local measurements, RTCP reports received and any uplink quality indications received from the GANC to open and start to leave the GAN coverage. The handover process from GAN to GERAN is always triggered by the UE.

[0796] FIG. 94 shows a CS handover process from GAN to GERAN in some embodiments. If there is a problem with the uplink quality for the ongoing call, GANC 9410 can send GA-RRCUPLINK QUALITY INDICATION (step 1). The uplink quality indicator is the information sent by the GANC 9410 to the UE 9405, indicating the intersection of the uplink quality threshold in the uplink direction. Whenever the UE 9405 receives an indication of poor quality, it initiates the handover procedure as described in the next step. Alternatively, the UE 9405 may use its local measurement or received RTCP report to decide to initiate the handover process.

[0797] The UE 9405 sends a GA-RRC HANDOVER INFORMATION message to the GANC9410, indicating the channel mode and the list of target GERAN cells identified by the CGI in the order of preference for handover (for example, arranged by the C1 path loss parameter) (step 2), 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, GA-RRC HANDOVER INFORMATION

The information may include a list of target UTRAN cells arranged in the order of preference for handover, and the received signal strength for each identified UTRAN cell.

[0798] If the serving GANC 9410 selects the target GERAN cell, a handover procedure to GERAN is performed. The service GANC 9410 initiates handover preparation by notifying CN 9415 that handover is required, using relocation requirements, and including the GERAN cell list provided by UE 9405 (step 3). GANC may only include a subset of the cell list provided by UE 9405. [0799] CN 9415 uses a handover request to select the target GERAN cell and request it to allocate the necessary resources (step 4). The target GERAN BSC 9415 establishes a handover command message that provides information about the allocated channel, and sends it to CN 9415 through a handover request confirmation message (step 5) ο

[0800] CN 9415 uses a relocation command message to notify GANC 9410 to switch UE 9405 to GERAN (step 6), and complete the switch preparation phase. GANC 9410 sends GA-RRC HANDOVERCOMMAND to UE 9405, including details about target resource allocation sent via GERAN (step 7)_OThe UE 9405 sends a "Um: Handover Access" message containing the handover reference element (step 8) to allow the target GERAN to associate the handover access with the handover command message previously sent to CN 9415 in response to the handover request.

[0801] The target GERAN uses the handover detection message to confirm the handover detection to CN 9415 (step 9). CN9415 can now switch the user plane to the target BSS (step 10). GERAN provides physical information to UE 9405 (ie, timing advance) (step 11) to allow UE 9405 to synchronize with GERAN. The UE 9405 uses the handover complete to notify GERAN that the handover is complete (step 12).

[0802] GERAN confirms the completion of handover to CN 9415 through a handover complete message (step 13). CN 9415 can use the target CGI used in the switching process for charging purposes. Two-way voice services now flow between UE 9405 and CN 9415 via GERAN (step 14) ο

[0803] After receiving the handover completion confirmation, CN 9415 instructs GANC 9410 to release any resources allocated to UE 9405 through Iu release command (step 15). GANC 9410 uses GA-RRC RELEASE message to order UE 9405 to release resources (step 16). GANC 9410 uses Iu release complete message to confirm resource release to CN 9415 (step 17) ο

[0804] The UE 9405 uses the GA-RRC RELEASE COMPLETE message to confirm the resource release to the GANC 9410 (step 18). Finally, the UE 9405 can use the GA-RC-DEREGISTERED message to deregister from the GANC 9410 (step 19).

[0805] d) CS handover from GAN to UTRAN

[0806] The process description in this sub-item assumes the following conditions: (1) UE is in an active call on GAN; (2) UE can operate in all these modes of GAN, GERAN and UTRAN; (3) UTRAN changes Is available, and (i) the UE is in the preferred GERAN/UTRAN mode, or (ii) the UE mode selection is the preferred GAN, and the UE starts based on its local measurements, received RTCP reports, and any uplink quality indications received from the GANC Leave the GAN coverage.

[0807] FIG. 95 shows the CS handover process from GAN to UTRAN in some embodiments. The handover process from GAN is always triggered by UE 9505. If there is a problem with the uplink quality for the ongoing call, GANC 9510 can send GA-RRC UPLINK QUALITYINDICATION (step 1). The uplink quality indicator is the information sent by the GANC 9510 to the UE 9505, indicating the intersection of the uplink quality threshold in the uplink direction. Whenever the UE 9505 receives an indication of poor quality, it initiates the handover procedure as described in the next step. Alternatively, the UE 9505 may use its local measurement or received RTCP report to decide to initiate the handover procedure.

[0808] UE 9505 sends the GA-RRC HANDOVER INFORMATION message to the service GANC9510 (step 2),

Indicates the channel mode and a list of candidate target UTRAN and GERAN cells in the order of preference for handover, and includes the received signal strength for each identified cell. UTRAN cells are identified by PLMN ID, LAC, and 3G cell identity (defined in 3GPP TS 25.331).

[0809] If the serving GANC 9510 selects UTRAN as the target RAT, the handover procedure to UTRAN is performed. The service GANC 9510 initiates handover preparation by notifying CN 9515 that handover is required (step 3), using relocation requirements, and including the UTRAN cell list provided by UE 9505. GANC 9510 may only include a subset of the cell list provided by UE 9505.

[0810] CN 9515 initiates a handover process to the target RNC 9520 identified by the service GANC 9510. CN9515 uses a relocation request to request the target RNC 9520 to allocate the necessary resources (step 4). The target RNC 9520 establishes a physical channel reconfiguration message that provides information about the allocated UTRAN resources and sends it to CN 9515 through a relocation request confirmation message (step 5).

[0811] CN 9515 uses a relocation command message (including a physical channel reconfiguration message) to notify the service GANC 9510 to switch the UE 9505 to UTRAN and complete the handover preparation phase. The service GANC 9510 sends the GA-RRC HANDOVER COMMAND to the UE 9505 (step 7), including the details of the target resource allocation sent via UTRAN.

[0812] The target RNS completes the uplink synchronization on the Uu interface (step 8). The target RNC 9520 uses a relocation detection message to confirm to CN 9515 that the handover is detected (step 9). CN 9515 can now switch the user plane to the target RNS (step 10). The UE 9505 uses the handover to UTRAN completion to notify the UTRAN that the handover has been completed (step 11). [0813] UTRAN confirms the completion of the handover to CN 9515 through the relocation complete message (step 12). If the user plane is not converted in step 10, CN 9515 will switch the user plane to the target RNS. Two-way voice services now flow between UE 9505 and CN 9515 via UTRAN (step 13).

[0814] After receiving the handover completion confirmation, CN 9515 instructs the serving GANC9510 to release any resources allocated to the UE 9505 through the Iu release command (step 14). The service GANC 9510 then uses the GA-RRC RELEASE message to order the UE 9505 to release resources (step 15) ο

[0815] The service GANC 9510 uses the Iu release complete message to confirm the resource release to CN 9515 (step 16). The UE 9505 uses the GA-RRC RELEASE COMPLETE message to confirm the resource release to the serving GANC 9510 (step 17). Finally, the UE 9505 can use the GA-RC-DEREGISTERED message to deregister from the service GANC 9510 (step 18). [0816] 9. GA-RRC Packet Transport Channel Management Process

[0817] The GA-RRC Packet Transport Channel (GA-RRC PTC) provides the association between the UE and the network, and is used to transmit GPRS user data through the Up interface (ie, through the GAN in the Iu mode). PTC uses the GTP-U protocol that runs on UDP transmission. The endpoint address of the PTC is identified by the IP address and UDP port allocated to the UE and the PTC in the network during the PTC-ACTIVE period. The UDP port number used for GTP-U is defined in 3GPP TS 25.414. Using the same endpoint address can activate multiple PTC events between the UE and the network at the same time. During the activation period, each PTC event is assigned a unique GTP-U tunnel endpoint ID (one for the UE and one for the network). The UE and the GANC manage the activation and deactivation of the PTC event according to the data transmission request and the configurable PTC timer.

[0818] a) GA-RRC packet transport channel status

[0819] The UE in the GA-RRC-CONNECTED state can be in one or two PTC sub-states: PTC-STANDBY or PTC-ACTIVE. PTC-STANDBY is when the UE is in the GA-RRC-CONNECTED state in the GAN mode The initial/default PTC sub-state. The UE cannot use PTC to send GPRS user data to the network or receive GPRS user data from the network. The UE needs to activate the PTC before sending any GPRS user data through the PTC. When the UE successfully establishes the PTC,

The UE transitions to the PTC-ACTIVE sub-state. PTC-ACTIVE is a state: the UE is in the GA-RRC-CONNECTED state, and PTC is activated between the UE and the network, and the UE can send GPRS user data to the network or receive GPRS user data from the network.

[0820] The following are possible trigger events for the activation of GA-RRC PTC on the UE side: (1) UE initiates uplink user data transmission; and (2) GANC initiates PTC activation, which may include UE slave GANC Receive GA-RRC ACTIVATE CHANNEL message. The reception of downlink data from the SGSN can be used as a trigger event for PTC activation initiated by the GANC.

[0821] While successfully activating the PTC and transitioning to the PTC-ACTIVE sub-state, the UE starts the PTC timer. When the PTC timer expires, the UE sends a message to GANC to instruct PTC to disable. After successfully disabling PTC, the UE transitions to the PTC-STANDBY sub-state.

[0822] At any time in the GA-RRC-CONNECTED state and in the PTC-ACTIVE sub-state, the UE can receive a GA-RRC DEACTIVATE CHANNEL message. The UE disables PTC and transitions to the PTC-STANDBY sub-state.

[0823] At any time in the GA-RRC-CONNECTED state and in the PTC-ACTIVE sub-state, the UE can receive a GA-RRC RELEASE message. In addition to requesting to release the GA-RRC session, this is interpreted by the UE as an implicit PTC disable command.

[0824] At any time in GAN mode, if the serving RR entity switches to GSM-RR/UTRAN-RRC, GA-RRC is disconnected from GPRS SAP and the UE enters GERAN/UTRAN mode. At the same time, the UE will release the associated PTC regardless of the status of the PTC timer. The UE GA-RRC entity maintains a PTC for each activated PDP context. The PTC timer is restarted whenever any uplink user data packet related to the PDP context is sent or a downlink user data packet is received. The value of the PTC timer is provided to the UE as part of the GAN registration process (ie in the GA-RC REGISTERACCEPT message).

[0825] b). PTC initial activation

[0826] FIG. 96 shows the initial activation process of the packet transmission channel in some embodiments. The following description assumes that the UE 9605 is in the GA-RRC-IDLE state in some embodiments. Perform the GA-RRC connection establishment process (step 1) as described in the GA-RRC connection establishment item initiated by the UE above. UE9605 transitions to GA-RRC-CONNECTED state and PTC-STANDBY sub-state. Perform additional PS signaling process (step 2).

[0827] CN 9610 (SGSN) initiates the RAB allocation process and includes RAB-ID.CN transport layer address (IP address) and CN Iu transport association (GTP-U endpoint identifier, TEID) for user data (step 3) . GANC 9615 sends a GA-RRC ACTIVATE PTC REQUEST message to UE 9605 to request activation of the packet transport channel (step 4). The message includes the RAB-ID, and the IP address and TEID of the CN to allow the UE 9605 to directly send the PTC packet (ie GTP-U message) to the SGSN.

[0828] The UE 9605 confirms that the PTC is activated and provides the transport layer address (IP address) and the Iu transport association (GTP-U TEID) on the UE side that identifies the PTC (step 5). UE 9605 transitions to the PTC-ACTIVE sub-state and starts the PTC timer.

[0829] After receiving the confirmation, GANC 9615 sends a RAB allocation response message to CN 9610 (SGSN) to complete the RAB allocation process (step 6), and includes the UE's IP address and GTP-U TEID. The PS signaling process is added Execute (step 7), and describe its example in the following PDP context activation and PDP context activation sub-part of network request. UE 9605 initiates transmission of uplink user data through the established PTC, and CN9610 (SGSN) can use the same transmission channel to transmit downlink user data packets (step 8).

[0830] FIG. 97 shows an alternative embodiment for performing an initial activation process of a packet transport channel. The following description assumes that the UE 9705 is in the GA-RRC-IDLE state in some embodiments. Perform the GA-RRC connection establishment process (step 1) as described in the above sub-part "GA-RRC connection establishment initiated by the UE". UE 9705 transitions to

GA-RRC-CONNECTED state and PTC-STANDBY sub-state. The additional PS signaling process is executed (step 2). [0831] CN 9710 (for example, SGSN) initiates the RAB allocation process and includes RAB-ID.CN transport layer address (IP address) and CN Iu transport association (GTP-U endpoint identifier, TEID) for user data (step 3). GANC 9715 sends a GA-RRC ACTIVATE CHANNEL message to UE9705 to request activation of the packet transport channel (step 4). The message includes the CN domain ID and RAB-ID for each RAB, the TEID assigned to UE 9705 by GANC 9715 ("MS TEID" in the figure). The GANC PTC IP address (that is, the purpose of PTC grouping from MS Address) and the TEID of the CN received in step 3.

[0832] UE 9705 confirms PTC activation (step 5). GANC 9715 uses the GA-RRC ACTIVATECHANNEL COMPLETE message to notify the UE 9705 of the completion of the RAB establishment (step 6). After receiving this message, UE 9705 transitions to the PTC-ACTIVE sub-state and starts the PTC timer.

[0833] GANC 9715 sends the RAB allocation response message to the SGSN (step 7) to complete the RAB allocation process. GANC includes RAB-ID, RAN transport layer address (that is, Iu-ps IP address of GANC) and RAN Iu transport association (that is, TEID assigned by GANC to MS) ο Perform additional PS signaling process (step 8) ο

[0834] The UE 9705 then transmits the uplink user data by sending a GA-RRC G-PDU message to the PTC IP address of the GANC received in step 4 (step 9). The message includes the CN TEIDo GANC 9715 received in step 4 relaying the message to CN9710 in the Iu-ps G-PDU message. CN 9710 transmits downlink user data by sending an Iu-ps G-PDU message to the Iu-ps IP address of GANC 9715 received in step 6 (step 10). The message includes the UE TEID received in step 6. GANC relays the message to the UE 9705 in the GA-RRC G-PDU message.

[0835] 3. PTC Data Transmission

[0836] FIG. 98 shows the transmission of GPRS user data packets through the GAN packet transmission channel in some embodiments. If required, establish a GANPTC as described in the subsection "PCT Initial Activation" above (step 1). After the GA-RRC PTC is established, the UE 9805 enters the PTC-ACTIVE sub-state and starts the PTC timer. The UE 9805 transmits the uplink user data packet by sending the GA-RRC G-PDU message to the GANC 9810 (step 2) and restarts the PTC timer. GANC 9810 relays the message to CN 9815 in the Iu-ps G-PDU message.

[0837] CN 9815 (SGSN) transmits downlink user data by sending Iu-ps G-PDU messages to GANC 9810 (step 3). GANC 9810 relays the message to UE 9805 in the GA-RRC G-PDU message. After receiving this message, the UE 9805 restarts the PTC timer.

[0838] d) UE-initiated PTC disable

[0839] FIG. 99 illustrates a situation when the UE disables the packet transmission channel after the PTC timer expires in some embodiments. The UE 9905 is in the GA-RRC-CONNECTED state and the PTC-ACTIVE sub-state (step 1). The PTC timer associated with one of the activated packet transport channels expires.

[0840] The UE 9905 sends a GA-RRC DEACTIVATE PTC REQUEST message to the GANC9910 (step 2), which includes the RAB-ID used to identify the PTC and indicates the normal release as the reason for disabling. GANC 9910 sends the RAB release request message to CN (SGSN) 9915 to request the release of the related RAB (step 3). CN (SGSN) 9915 responds with a RAB allocation request indicating release (step 4).

[0841] GANC 9910 uses the GA-RRC DEACTIVATE PTC ACK message to respond to the UE 9905 (step 5) to confirm the successful deactivation. UE 9905 transitions to the PTC-STANDBY sub-state. GANC

[0842] 9910 sends a RAB allocation response message to notify SGSN 9915 that the RAB release process has been completed (step

6) ο

[0843] FIG. 100 depicts an alternative embodiment of the situation when the UE disables the packet transmission channel after the PTC timer expires in some embodiments. The UE 10005 is in the GA-RRC-CONNECTED state and the PTC-ACTIVE sub-state (step 1). The PTC timer associated with one of the activated packet transport channels expires.

[0844] The UE 10005 sends a GA-RRC DEACTIVATE PTC REQUEST message to the GANC 10010 (step 2). The message includes the CN domain identifier, the RAB-ID used to identify the PTC, and indicates the normal release as the reason for disabling. GANC 10010 sends a RAB release request message to CN (SGSN) 10015 to request the release of related RAB (step 3). CN (SGSN) 10015 responds with a RAB allocation request indicating release (step 4).

[0845] GANC 10010 sends a GA-RRC DEACTIVATE CHANNEL message to UE 10005 (step 5), which includes the CN domain identifier and RAB ID. UE 10005 disables PTC (step 6). Send the GA-RRC DEACTIVATE CHANNEL ACK message to GANC 10010 and transition to the PTC-STANDBY sub-state. GANC 10010 sends (step 7) an RAB allocation response message to notify SGSN 10015 that the RAB release process is complete.

[0846] e) PTC reactivation initiated by the UE

[0847] FIG. 101 describes a situation when the UE initiates the reactivation of the packet transmission channel in some embodiments. The UE is in the GA-RRC-CONNECTED and PMM-CONNECTED states. For example, the PS signaling connection and the activated PDP context exist between the UE 10105 and CN 10115, but in some embodiments, the PTC timer has expired, so the PTC was previously UE is disabled. UE 10105 is in GA-RRC-CONNECTED state and PTC-STANDBY sub-state. The UE 10105 is in the PMM-CONECTED state (that is, the PS signaling connection and the activated PDP context exist).

[0848] UE 10105 has PDUs to send. The UE 10105 sends a service request message (service type value "data") in the GA-RRC UL DIRECTTRANSFER message to the GANC 10110 (step 1). GANC 10110 uses RANAP to directly deliver the message to forward the service request to CN 10115 through the existing signaling connection (step 2).

[0849] CN 10115 can selectively initiate the safe mode control process described in the "safe mode control" subsection above (step 3). CN 10115 responds with a service acceptance message (step 4). GANC 10110 forwards the message to UE 10105 (step 5) ο

[0850] UE 10105, GANC 10110, and CN 10115 establish a GA-RRC Packet Transport Channel (PTC) (step 6), as described in steps 3-6 of "PTC Initial Activation" above. The UE 10105 transitions to the PTC-ACTIVE sub-state and starts the PTC timer. UE 10105 transmits uplink PDU (step 7). Other data transfers are also possible.

[0851] FIG. 102 describes the situation when the UE initiates the reactivation of the packet transmission channel in some alternative embodiments. The UE is in the GA-RRC-CONNECTED and PMM-CONNECTED states and the PTC-STANDBY sub-state (for example, the PS signaling connection and the activated PDP context exist between UE 10205 and CN 10215, but in some embodiments due to the PTC timer Timeout, PTC was previously disabled by UE 10205).

[0852] The UE 10205 has a PDU to send. The UE 10205 sends a service request message (service type value "data") in the GA-RRC UL DIRECTTRANSFER message to GANC 10210 (step 1). GANC 10210 uses RANAP to directly transmit the message to forward the service request to CN 10215 through the existing signaling connection (step 2).

[0853] CN 10215 may selectively initiate the above-mentioned safe mode control process (step 3). CN 10215 responds with a service acceptance message (step 4). GANC 10210 forwards the message to UE 10205 (step 5).

[0854] UE 10205, GANC 10210, and CN 10215 establish a GA-RRC Packet Transport Channel (PTC) (step 6), as described in steps 3-6 of "PTC Initial Activation" above. The UE 10205 transitions to the PTC-ACTIVE sub-state and starts the PTC timer. UE 10205 sends GA-RRC G-PDU to CN 10215 in Iu-ps G-PDU message

To transmit uplink user data (step 7). Other data transfers are also possible.

[0855] f) PTC disabled by the network

[0856] FIG. 55 describes the situation when the network initiates the disabling of the packet transmission channel in some embodiments. The UE 10305 is in the GA-RRC-CONNECTED state and the PTC-ACTIVE sub-state.

[0857] Optionally, for example, as a result of an error handling process, GANC 10310 may initiate a PTC disabling process. If so, GANC 10310 sends a RAB release request message to CN 10315 (step 1). CN (SGSN) 10315 sends a RAB allocation request to request the release of the related RAB (step 2). The release request may include one or more RABs.

[0858] GANC 10310 requests to disable related GA-RRC PTCo by sending a GA-RRC DEACTIVATE PTC REQUEST message to UE 10305 (step 3). In some embodiments, the GA-RRC DEACTIVATE PTC REQUEST message includes a CN domain identifier. UE 10305 transitions to the PTC-STANDBY sub-state, stops the PTC timer, and sends an acknowledgement back to GANC 10310 (step 4). Repeat steps 3 and 4 for each additional RAB/PTC that needs to be released. GANC10310 uses RAB allocation response message to notify CN 10315 that the release is successful (step 5).

[0859] g) PTC reactivation initiated by the network

[0860] i) PDP context activated, PS signaling connection exists

[0861] FIG. 104 describes the situation when the network initiates the reactivation of the packet transmission channel in some embodiments. UE 10405 is in GA-RRC-CONNECTED and PMM-CONNECTED state and PTC-STANDBY sub-state (for example, PS signaling connection and activated PDP context exist between UE and CN, but in some embodiments PTC was previously disabled by UE Up.

[0862] CN 10415 has a PDU to be sent to UE 10405. CN 10415 can selectively initiate the safe mode control process described in the "safe mode control" subsection above (step 1). UE 10405, GANC 10410 and CN 10415 establish a GA-RRC Packet Transport Channel (PTC) (step 2), as described in steps 3-6 of the "PTC Initial Activation" secondary part above. UE 10405 transitions to the PTC-ACTIVE sub-state and starts the PTC timer. Finally, CN 10415 sends a downlink PDU (step 3). Other data transfers are also possible. In some embodiments, the message sending in step 3 includes (1) the Iu-psG-PDU message including the UE TEID and payload sent from CN 10415 to GANC 10410; (2) the Iu-psG-PDU message including UE TEID and payload sent from GANC 10410 to UE 10405, including GA-RRC G-PDU of UE TEID and payload.

[0863] ii) Active PDP context, no PS signaling connection exists

[0864] FIG. 105 shows that when the MS is in the GA-RRC-IDLE and PMM-CONNECTED states, the network initiates the reactivation of the packet transmission channel (for example, no PS signaling connection exists, but there is an active connection between the MS and the CN. PDP context). As shown in the figure, CN 10515 receives downlink user data to be transmitted to UE 10505, and the Iu connection is not established. The UE 10505 is in the PMM-CONECTED state.

[0865] CN 10515 sends a RANAP paging message to UE 10505 through GANC 10510 to locate the user (step 1). The paging request indicates paging for PS domain signaling. GANC 10510 forwards the paging information to UE 10505 in the GA-RRCPAGING REQUEST message (step 2) ο

[0866] UE 10505 responds with a GA-RRC INITIAL DIRECT TRANSFER message (step 3). UE 10505 transitions to the GA-RRC-CONNECTED state. GANC 10510 then establishes a SCCP connection to CN 10515 and uses RANAP initial UE message to forward the service request message (service type value "Paging Response") (step 4) to CN 10515. RANAP will be used to directly transmit the message to the UE 10505 Subsequent NAS messages between CN 10515 are sent between GANC 10510 and CN 10515 (eg SGSN).

[0867] CN 10515 may use standard UTRAN authentication procedures to selectively authenticate UE 10505 (step 5).

CN 10515 normally initiates the security mode control process as described above (step 6) o UE10505, GANC 10510 and CN 10515 establish GA-RRC packet transport channel (PTC) (step 7), as in step 3- of "PTC initial activation" As described in 7. Then, UE 10505 and CN 10515 exchange user data transmission through the established PTC (step 8).

[0868] h) Implicit PTC disablement due to UE deregistration

[0869] FIG. 106 shows a process for implicit PTC disabling in some embodiments. As part of the GAN deregistration process, GANC needs to release all resources allocated to UE 10605. If the loss of the signaling connection is detected, it can be explicitly initiated by UE 10605 or GAN deregistration can be implicitly initiated by GANC 10610. Initially, one or more GA-PSR PTCs related to UE 10605 are in the PTC-ACTIVE state.

[0870] The UE 10605 or GANC 10610 initiates the GAN deregistration process for the UE 10605 (step 1). Optionally, any allocated resources related to the CS domain are released (step 2). Optionally, if there are any allocated resources related to the PS domain, GANC 10610 initiates the Iu release process to release the corresponding RAB (step 3) o CN (SGSN) 10615 responds with the Iu release command (step 4) . After receiving the Iu release command, the GANC 10610 locally disables all relevant PTCs and uses the Iu release complete message to respond to the core network (SGSN) 10615 (step 6) ο

[0871] 10. PDP ± below activation

[0872] FIG. 107 shows a successful UE-initiated PDP context activation process in some embodiments, assuming that the UE is in the GA-RRC-IDLE state. The GA-RRC connection establishment process is performed as described above in the sub-part of "UE Initiated GA-RRC Connection Establishment" (step 1). If the GA-RRC connection already exists (for example, there is an existing CS call in the process), this step is skipped.

[0873] In the case of a request from the upper layer, the UE 10705 sends a service request message (service type value "signaling") to the GANC 10710 in the GA-RRC INITIAL DIRECTTRANSFER message (step 2). In some embodiments, the message includes the CN domain identifier and IDNNSo GANC 10710 to establish an SCCP connection to CN 10715, and uses the RANAP initial UE message to forward the service request to CN 10715 (step 3). RANAP will be used to directly transmit messages between GANC 10710 and CN 10715 to send subsequent NAS messages between UE 10705 and core network 10715.

[0874] The CN 10715 may use a standard UTRAN authentication procedure to selectively authenticate the UE 10715 (step 4). CN 10715 can selectively initiate the safety mode control process described in the above subsection "Safety Mode Control" (step 5).

[0875] CN (SGSN) 10715 responds with a service acceptance message (step 6). GANC 10710 forwards the message to UE 10705 (step 6). The UE 10705 sends an Activate PDP Context Request message that provides details about the PDP context to the CN 10715 (step 7). This message is contained in the GA-RRC UL DIRECT TRANSFER between UE 10705 and GANC 10710. GANC 10710 forwards the activation PDP context request message to CN 10715 (step 7). [0876] UE 10705, GANC 10710, and SGSN 10715 establish a GA-RRC Packet Transport Channel (PTC) (step 8), as described in steps 3-6 of "PTC Initial Activation" above. CN 10715 uses the Activate PDP Context Accept message to indicate to GANC 10710 that the establishment of the PDP context is complete (step 9). GANC forwards the message to UE 10705 in the GA-RRC UL DIRECT TRANSFER message (step 9). UE 10705 and CN 10715 exchange user data transmission through the established PTC (step 10).

[0877] 11. PDP context activation requested by the network

[0878] FIG. 108 shows a successful network request PDP context activation process in some embodiments, assuming that the UE is in the GA-RRC-IDLE state. Initially, CN (SGSN) 10815 receives the downlink user data to be delivered to the UE, and

The related RAB has not been established. The UE is in the PMM-IDLE state.

[0879] CN (SGSN) 10815 sends a RANAP paging message to UE 10805 through GANC 10810 to locate the user (step 1). The paging request indicates paging for PS domain signaling. GANC 10810 forwards the paging information to UE 10805 in the GA-RRC PAGING REQUEST message (step 2). In some embodiments, GA-RRC PAGING REQUEST includes CN domain identification.

[0880] GANC 10805 uses a service request message (service type value "Paging Response") to respond to CN 10815 through GANC 10810 (step 3). The message is encapsulated in a GA-RRC INITIAL DIRECT TRANSFER message, and the GA-RRC INITIAL DIRECT TRANSFER message may include the CN domain ID and IDNNS. UE 10805 then transitions to GA-RRC-CONNECTE. Do GANC 10810 forwards the service request message encapsulated in the RANAP initial UE message to SGSN 10815.

[0881] CN 10815 may use standard UTRAN authentication procedures to selectively authenticate UE 10805 (step 5). CN 10815 can selectively initiate the safe mode control process described in the above "safe mode control" subsection (step 6) ο

[0882] CN 10815 sends a PDP context activation request message to GANC 10810 (step 7) _o GANC10810 forwards the message to UE 10805 in the GA-RRC DL DIRECT TRANSFER message (step 7).

[0883] The UE 10805 sends an activation PDP context request message that provides details about the PDP context to the CN 10815 (step 8). This message is contained in the GA-RRC ULDIRECT TRANSFER between UE 10805 and GANC 10810. GANC forwards the activation PDP context request message to CN 10815 (step 8). UE 10805, GANC 10810, and CN 10815 establish a GA-RRC Packet Transport Channel (PTC) (step 9), as described in steps 3-6 of the "PTC Initial Activation" sub-part above.

[0884] CN 10815 uses the Activate PDP Context Accept message to indicate to GANC 10810 that the establishment of the PDP context is complete (step 10). GANC forwards the message to UE 10805 in the GA-RRC DL DIRECT TRANSFER message (step 10) o UE 10805 and CN 10815 exchange user data transmission through the established PTC (step 11).

[0885] 12. PDP context activation using activated CS session

[0886] FIG. 109 shows a successful UE-initiated PDP context activation process in some embodiments, assuming that the UE 10905 is in GA-RRC-CONNECTED mode (for example, there is a CS session). The GA-RRC connection establishment process is performed as described in the secondary part of the GA-RRC connection establishment initiated by the UE above. If the GA-RRC connection already exists (for example, there is an existing CS call in the process), this step is skipped.

[0887] In the case of a request from the upper layer, the UE 10905 sends a service request message (service type value "signaling") to the GANC 10910 in the GA-RRC INITIAL DIRECTTRANSFER message (step 1). GANC 10910 establishes an SCCP connection to CN 10915 (step 2), and uses the RANAP initial UE message to forward the service request to the CN. RANAP will be used to directly transmit messages between GANC 10910 and CN 10915 to send subsequent NAS messages between UE 10905 and core network 10915.

[0888] CN 10915 may use a standard UTRAN authentication process to selectively authenticate UE 10915 (step 3). CN 10915 can selectively initiate the safety mode control process described in the above subsection "Safety Mode Control" (step 4).

[0889] CN (SGSN) 10915 responds with a service acceptance message (step 5) _o GANC 10910 forwards the message to UE 10905 (step 5). The UE 10905 sends an activation PDP context request message that provides details about the PDP context to the CN 10915 (step 6). This message contains the GA-RRC UL between UE 10905 and GANC 10910

DIRECT TRANSFER. GANC forwards the activation PDP context request message to CN 10915 (step 6).

[0890] UE 10905, GANC 10910, and CN 10915 establish a GA-RRC Packet Transport Channel (PTC) (step 7), as described in steps 3-6 of "PTC Initial Activation" above. CN 10915 uses the Activate PDP Context Accept message to indicate to GANC 10910 that the establishment of the PDP context is complete (step 8). GANC forwards the message to UE 10905 in the GA-RRC DL DIRECT TRANSFER message (step 8). UE 10905 and CN 10915 exchange user data transmission through the established PTC (step 9).

[0891] 13. PS Relocation from UTRAN to GAN

[0892] a) Preparation phase

[0893] The description of the UTRAN to GAN relocation process assumes some situations: (1) In UTRAN, the UE has one or more activated PDP contexts and activated RABs; (2) The UE has successfully registered with the GANC, allowing the UE Obtain GAN system information; (3) GANC guides the UE to operate in Iu mode; and UTRAN provides information about neighboring cells, so that one of the cells in the neighbor list matches the cell related to GANC, as in the one obtained from GANC As provided in the AS-related components in the system information.

[0894] FIG. 110 illustrates the preparation phase of PS relocation from UTRAN to GAN according to some embodiments. As shown in the figure, UE 11005 includes GAN cell information in the measurement report sent to RNC 11015 (step 1). In this message, UE 11005 sets the signal strength indicator of the GAN cell to the highest possible value. Next, RNC 11015 decides to initiate a combined hard handover and SRNS relocation process. In some embodiments, the decision is based on measurement reports and vendor/operator specific criteria. After deciding to initiate relocation, RNC 11015 sends a relocation request message to CN (eg SGSN) 11020 (step 2).

[0895] CN 11020 determines that the target cell is GANC 11010 based on the content of the relocation demand message_o CN11020 then sends a relocation request message to GANC 11010 (step 3). In some embodiments, the relocation request message includes RABTD, CN TE-ID, and GANC-PTC IP address. GANC 11010 then sends a GA-RRC ACTIVATE CHANNEL message (step 4) to UE 11005 to request the activation of the packet transport channel. The message includes CN domain ID.RAB ID, TEID assigned to UE 11005 by GANC 11010 ("MS TEID" in the figure), GANC PTC IP address (that is, the destination address for PTC packets from MS), and in step 3. Received CN TEIDo

[0896] The UE 11005 confirms the PTC activation through the GA-RRC ACTIVE CHANNEL ACK message including the RAB-ID (step 5). GANC 11015 uses the GA-RRC ACTIVATE CHANNELCOMPLETE message to notify UE 11005 of the completion of the RAB establishment (step 6). After receiving this message, UE 11005 transitions to the PTC-ACTIVE sub-state and starts the PTC timer. GANC 11010 sends a relocation request confirmation message to CN 11020 (step 7).

[0897] b) Execution phase

[0898] FIG. 111 shows the PS relocation execution phase from UTRAN to GAN. In some embodiments, the execution phase occurs after receiving a positive confirmation of serving the UE from the GANC. As shown in the figure, CN11120 sends the relocation command to RNC 11115 (step 1). One or more GTP PDUs can be exchanged between GANC 111KRNC 11115 and CN 11120 (Step 2) ο

[0899] The RNC 11115 instructs the UE 11105 to initiate a handover to the GAN through a physical channel reconfiguration message (step 3). RNC 11115 can initiate forwarding of GTP PDUs to GANC 11110 (step 2), while continuing to send them to UE 11105 on the downlink. This forwarding is routed through the Iu-PS interface. GANC 11110 can buffer, send or discard these forwarded GTP PDUs on the downlink, depending on the QoS distribution, network conditions and whether it supports lossless relocation. RNC 11115 also sends forwarding SRNS context messages to GAN through CN 11120. In this message,

The old SRNC is used to indicate the next desired sequence number of the uplink and downlink GTP-U packets to the GANC 11110.

[0900] Upon receiving the physical channel reconfiguration message, the UE 11105 sends the GA-RRC RELOCATIONCOMPLETE message (step 3) to the GANC 11115. After receiving the message and forwarding the SRNS context message, the GANC 11110 becomes the serving RNC. After receiving the GA-RRCRELOCATION COMPLETE message from UE 11105, GANC 11110 sends a relocation detection message to CN11120 (step 4). GANC 11110 sends a relocation complete message to CN 11120 (step 5).

[0901] UE 11105, GANC 11110, and CN 11120 exchange user data through the established PTC (step 6). CN 11120 releases the Iu-ps connection with the old RNC (step 7). If the routing area of the GANC 11110 cell (indicated to the UE 11105 through the GANC 11110) is different from the routing area under the old RNC, the UE 11105 performs the routing area update process (step 8).

[0902] 14. PS relocation from GAN to UTRAN

[0903] a) Preparation phase

[0904] FIG. 112 shows the preparation phase of PS relocation from GAN to UTRAN according to some embodiments. As shown in the figure, the UE 11205 uses the activated PDP context and PTC to perform activated packet flow exchange in the GAN (step 1). If there is an uplink quality problem for the ongoing session, GANC 11210 can send (step 2) GA-RRC UPLINK QUALITY INDICATION. The uplink quality indicator is sent to UE 11205 via GANC 11210 to indicate the uplink direction. Information about the intersection of the uplink quality threshold. Whenever an indication of poor quality is received, the UE 11205 will initiate the relocation process as described in the next step. Alternatively, the UE 11205 may use its local measurements to decide to initiate the handover procedure.

[0905] UE 11205 decides to initiate SRNS relocation from GAN to UTRAN by sending GA-RRC RELOCATION INFORMATION message (step 3) to GANC 11210. GANC 11210 selects the target RNC based on the content of the GA-RRC RELOCATION INFORMATION message. GANC 11210 then sends a relocation request message containing the selected RNC information to CN 11220 (step 4). CN 11220 sends a relocation request to target RNC 11215 (step 5). RNC 11215 performs the necessary allocation of radio and Iu transmission resources (step 6), and RNC 11215 then returns a relocation request confirmation message to CN 11220 (step 7). This message contains a transparent container containing channelization information that UE 11205 needs to access UTRAN.

[0906] b) Execution phase

[0907] FIG. 113 shows the execution phase of PS relocation from GAN to UTRAN according to some embodiments. CN 11320 starts the execution phase by issuing a relocation command to GANC 11310 (step 1). This message contains channel access information in the target UTRAN cell. GANC 11310 sends GA-RRCRELOCATI ON COMMAND to UE 11305 (step 2). This message contains information from the relocation command previously received in step 1. GANC 11310 also sends forwarding SRNS context (step 2) to target RNC 11315 via CN 11320 (eg SGSN). CN 11320 relays the forwarding SRNS context to target RNC 11315 (step 3).

[0908] After receiving the GA-RRC RELOCATION COMMAND, the UE 11305 immediately suspends the transmission of ULGTP PDU. UE 11305 uses the channelization parameters indicated in the message to immediately start accessing UTRAN_O The UE's access attempt is detected by the base station and RNC 11315, and reported to CN 11320 through a relocation detection message (step 4).

[0909] The UE 11305 completes the establishment and configuration of the lower layer, and sends the RRC physical channel reconfiguration to the target RNC 11315 (step 5). This triggers the CN 11320 relocation complete message. At this stage, the target RNC 11315 is

UE 11305 assumes the task of SRNC. The packet data stream is now activated via UTRAN (step 6).

[0910] CN 11320 releases the Iu-ps connection by sending an Iu release command message to GANC 11310 (step 7), and GANC 11310 responds to it with an Iu release complete message (step 7).

[0911] 15. SRNS Relocation

[0912] For the UE in the PMM-CONNECTED state to perform the serving RNS relocation process to move the RAN connection point from the old RNC to the new RNCo, two scenarios will be considered: (1) From RNC to GANC (ie from SRNS relocation from UTRAN to GAN; (2) SRNS relocation from GANC to RNC (that is, from GAN to UTRAN). Based on the support of the Iur interface and lossless SRNS relocation, these processes include several options. In this version of the GAN specification, it is assumed that the Iur interface is not supported. In addition, it is assumed that the PDCP protocol is not included in the GAN scheme in order to optimize data transmission. It is assumed that lossless SRNS relocation is also not supported.

[0913] a) SRNS relocation from UTRAN to GAN

[0914] FIG. 114 shows the SRNS relocation process from UTRAN to GAN for the UE in the PMM-CONNECTED state in some embodiments. It is assumed that the Iur interface and the lossless SRNS relocation process are not supported. Initially, UE 11405 registers for GAN service and is in PMM-CONECTED state. At least one PDP context is active, and the maximum bit rate is greater than 0.

[0915] After detecting the GAN coverage and successfully registering the GAN service, the UE 11405 sends a measurement report (step 1) to the RNC 11410 to indicate the highest signal level for the GAN cell. The RNC 11410 sends a relocation request message (step 2) to the core network (SGSN) 11420 to initiate the SRNS relocation process. This message indicates that GANC 11415 is the target RNC 11410 and includes the information needed to relocate the coordinates.

[0916] The core network (SGSN) 11420 forwards the request to the GANC 11415 (step 3). The message includes the list of RABs to be established and related information. Based on the relocation request message, CN 11420 and GANC11415 establish (step 4) the requested RAB and related PS transmission channels, as explained in the secondary part of the GA-RRC packet transmission channel management process above.

[0917] GANC 11415 responds to the core network 11420 with an acknowledgment including the target RNC 11410 to the source RNC transfer container. The core network (SGSN) 11420 performs relocation by sending a relocation command including the target RNC to the source RNC transfer container to the old RNC (Step 6).

[0918] The RNC 11410 starts to forward data to the UE 11405 for the RAB that is forwarding (step 7). This forwarding is performed only for downlink user data, and is based on the transport layer address received from the GANC 11415 and the Iu transport association.

[0919] The RNC 11140 sends (step 8) a PHYSICAL CHANNEL RECONFIGURATION message to the UE 11405 to initiate relocation to the GAN. RNC 11410 continues the relocation by forwarding (step 9) the SRNS context information to GANC 11415 via the core network (SGSN) 11420. The core network (SGSN) 11420 forwards the SRNS context (step 10) to GANC 11415ο GANC

[0920] 11415 responds with a relocation detection message (step 11).

[0921] The UE 11405 sends a GA-RRC relocation complete message to the GANC 11415 to indicate successful relocation. GANC 11415 sends a relocation complete message to the core network (SGSN) 11420 to complete the process (step 13).

[0922] After receiving the relocation complete message, the core network (SGSN) 11420 switches the user plane from the RNC 11410 to the GANC (UE) and initiates the Iu release process to the RNC 11410 (step 14). After the data forwarding timer expires and after the related resources are released, the RNC 11410 responds to the core network (SGSN) 11420 with an Iu release complete message (step 15).

[0923] 16. Short Message Service

[0924] GAN supports circuit-switched and packet-switched SMS services. A UE attached to GAN and supporting GPRS can send and receive SMS messages through GAN.

[0925] a) SMS based on CS

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

[0927] b). SMS based on PS

[0928] The delivery of PS-based SMS messages is based on the same mechanism as the delivery of PS mobility management messages and session management signaling messages. In the UE, according to the standard packet-switched UMTS implementation, the SMS layer (including supporting the CM sublayer function) uses the services of the RRC (that is, GA-RRC) layer to transmit SMS messages. As far as mobility management and session management signaling are concerned, secure IPSec channels and TCP sessions are used to provide safe and reliable PS-based SMS delivery over IP networks.

[0929] IX. Computer System

[0930] FIG. 115 conceptually shows a computer system, and some embodiments of the present invention are implemented by using the computer system. The computer system 11500 includes a bus 11505, a processor 11510, a system memory 11515, a read-only memory 11520, a permanent storage device 11525, an input device 11530, and an output device 11535.

[0931] The bus 11505 generally represents all system buses, peripheral buses, and chipset buses, and supports communication between internal devices of the computer system 11500. For example, the bus 11505 connects the processor 11510 with the read-only memory 11520, the system memory 11515, and the permanent storage device 11525 in a communication manner.

[0932] The processor 11510 obtains the instructions to be executed and the data to be processed from these different storage units 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) 11520 stores static data and instructions required by the processor 11510 and other modules of the computer. On the other hand, the permanent storage device 11525 is a read-write storage device. The device is a non-volatile storage unit that can store instructions and data even when the computer system 11500 is shut down. Some embodiments of the present invention use mass storage devices (such as magnetic or optical disks and their corresponding disk drives) as permanent storage devices 11525. Some embodiments use one or more removable storage devices (flash cards or memory sticks) as permanent storage devices. Store straight.

[0933] Like the permanent storage device 11525, the system memory 11515 is a read-write storage device. However, unlike the storage device 11525, the system memory is a volatile read-write memory, such as a random access memory. The system memory stores some instructions and data required by the processor at runtime.

[0934] Instructions and/or data required to perform the processes of some embodiments are stored in the system memory 11515, the permanent storage device 11525, the read-only memory 11520, or any combination thereof. For example, according to some embodiments, various storage units contain instructions for processing multimedia items. The processor 11510 obtains the instructions to be executed and the data to be processed from these different storage units, so as to execute the processes of some embodiments.

[0935] The bus 11505 is also connected to input and output devices 11530 and 11535. The input device allows the user to convey information and selection commands to the computer system. The input device 11530 includes an alphanumeric keyboard and a cursor controller. Output

The device 11535 displays images generated by the computer system. Output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Finally, as shown in Figure 115, the bus 11505 also couples the computer 11500 to the network 11565 through a network adapter (not shown). In this case, the computer can be used as a computer network (such as a local area network ("LAN")), a wide area network ("WAN ") or the Internet) or part of the net in the net (such as the Internet).

[0936] Those of ordinary skill in the art should understand that any or all components of the computer system 11500 can be used in combination with the present invention. For example, some embodiments of some or all components of a computer system including UE, FAP, GANC, and other devices described above are described with respect to FIG. 115. In addition, those of ordinary skill in the art will understand that any system configuration can also be used in combination with the present invention or the components of the present invention.

<td>[0937]</td><td colspan="2">X. Definitions and abbreviations</td>

<td>[0938]</td><td colspan="2">The following is a list of definitions and acronyms used</td>

<td>[0939]</td><td>AAA</td><td>Authentication, authorization and billing</td>

<td>[0940]</td><td>AKA</td><td>Authentication key agreement</td>

<td>[0941]</td><td>AP</td><td>Access Point</td>

<td>[0942]</td><td>AS</td><td>Access layer</td>

<td>[0943]</td><td>BSC</td><td>Base Station Controller</td>

<td>[0944]</td><td>BSS</td><td>Base station subsystem</td>

<td>[0945]</td><td>BSSGP</td><td>Base station system GPRS protocol</td>

<td>[0946]</td><td>BSSMAP</td><td>Base station system management application part</td>

<td>[0947]</td><td>cc</td><td>Call control</td>

<td>[0948]</td><td>CGI</td><td>Cell global identification code</td>

<td>[0949]</td><td>CM</td><td>Connection management</td>

<td>[0950]</td><td>CN</td><td>Core Network</td>

<td>[0951]</td><td>CS</td><td>Circuit switching</td>

<td>[0952]</td><td>CTM</td><td>Cellular text phone modem</td>

<td>[0953]</td><td>DNS</td><td>Domain Name System</td>

<td>[0954]</td><td>DTM</td><td>Dual mode transmission</td>

<td>[0955]</td><td>EAP</td><td>Extended authentication protocol</td>

<td>[0956]</td><td>GA-CSR</td><td>Universal Access-Circuit Switched Resources</td>

<td>[0957]</td><td>GA-PSR</td><td>Universal Access-Packet Switching Resources</td>

<td>[0958]</td><td>GA-RC</td><td>Universal Access-Resource Control</td>

<td>[0959]</td><td>GAN</td><td>Universal access network</td>

<td>[0960]</td><td>GANC</td><td>Universal access network controller</td>

<td>[0961]</td><td>ETSI</td><td>European Telecommunications Standards Institute</td>

<td>[0962]</td><td>FCC</td><td>Federal Communications Commission</td>

<td>[0963]</td><td>GAD</td><td>Geographical area description</td>

<td>[0964]</td><td>GERAN</td><td>GSM EDGE wireless access network</td>

<td>[0965]</td><td>GGSN</td><td>Gateway GPRS Support Node</td>

<td>[0966]</td><td>GMM/SM</td><td>GPRS mobility management and session management</td>

<td>[0967]</td><td>GPRS</td><td>General Packet Radio Service</td>

[0968]

[0969]

[0970]

[0971]

[0972]

[0973]

[0974]

[0975]

[0976]

[0977]

[0978]

[0979]

[0980]

[0981]

[0982]

[0983]

[0984]

[0985]

[0986]

[0987]

[0988]

[0989]

[0990]

[0991]

[0992]

[0993]

[0994]

[0995]

[0996]

[0997]

[0998]

[0999]

[1000]

[1001]

[1002]

[1003]

[1004]

[1005]

[1006]

GSM Global System for Mobile Communications

GSN GPRS support node

HLR home location register

HPLMN belongs to PLMN

IETF Internet Engineering Task Force

IKE Internet Key Exchange

IKEv2 IKE version 2

IMEISV International Mobile Equipment Identity and Software Version Number

IMSI International Mobile User Identity

IP Internet Protocol

LA location area

LAI location area identification

LLC logical link control

MAC media access control

MAC message authentication code

MM mobility management

MS mobile station

MSC Mobile Switching Center

MTP1 messaging part layer 1

MTP2 messaging part layer 2

MTP3 messaging part layer 3

NAS non-access layer

PDP packet data protocol

PLMN Public Land Mobile Network

PSAP Public Safety Answering Point-PSAP is an emergency service network element responsible for answering emergency calls

PSTN Public Switched Telephone Network

P-TMSI packet-TMSI

QoS quality of service

RA routing area

RAC routing area code

RAI routing area identification

RANAP Radio Access Network Application Protocol

RAT radio access protocol

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

<td>[1007]</td><td>SEGW</td><td>Security gateway</td>

<td>[1008]</td><td>SGSN</td><td>Serving GPRS Support Node</td>

<td>[1009]</td><td>SIM</td><td>User Identification Module</td>

<td>[1010]</td><td>SMLC</td><td>Service Mobile Positioning Center</td>

<td>[1011]</td><td>SMS</td><td>Short message service</td>

<td>[1012]</td><td>SNDCP</td><td>Subnet Gateway Convergence Protocol</td>

<td>[1013]</td><td>TBF</td><td>Temporary block flow</td>

<td>[1014]</td><td>TC</td><td>Transport channel</td>

<td>[1015]</td><td>TCP</td><td>Transmission Control Protocol</td>

<td>[1016]</td><td>TFO</td><td>No tandem operation</td>

<td>[1017]</td><td>TMSI</td><td>Temporary mobile user identification</td>

<td>[1018]</td><td>TrFO</td><td>No decoder operation</td>

<td>[1019]</td><td>TTY</td><td>Text phone or teletypewriter</td>

<td>[1020]</td><td>UE</td><td>User equipment</td>

<td>[1021]</td><td>UDP</td><td>User Datagram Protocol</td>

<td>[1022]</td><td>UMTS</td><td>Universal Mobile Communication System</td>

<td>[1023]</td><td>UTRAN</td><td>UMTS terrestrial wireless access network</td>

<td>[1024]</td><td>Up</td><td>Up is the interface between UE and GANC</td>

<td>[1025]</td><td>VLR</td><td>Visitor location register</td>

<td>[1026]</td><td>VPLMN</td><td>Access public land mobile network</td>

<td>[1027]</td><td colspan="2">Although the present invention has been described with reference to many specific details, those of ordinary skill in the art will</td>

It is understood that the present invention can be embodied in other specific forms without departing from the spirit of the present invention. For example, the specific sequence of the described processes and their related attributes can be changed. In this way, those of ordinary skill in the art can understand that the present invention is not limited by the above-mentioned exemplary details, but is defined by the appended claims.