TWM320260U - Wireless communication system for implementing a single tunnel combined hard hanover and serving radio network subsystem relocation - Google Patents

Description

M320260, eight, new description: [Technical field] The present invention relates to a wireless communication system. More specifically, the present invention relates to an apparatus for supporting a handover and serving radio network subsystem (SRNS) relocation process in a single tunnel general packet radio service (GPRS) based wireless communication system. ^ [Background] • Figure 1 shows a conventional GPRS/third generation (3G) wireless communication system architecture 100, which illustrates various interfaces/protocols and users between various network entities. Data transfer interface. The wireless communication system 1 〇 0 peak includes at least one serving GPRS support node (SGSN) 105 and at least one gateway 01^ support node (GGSN) 110. The wireless communication system 1 further includes a universal terrestrial radio access network (UTRAN) 115 including one or more radio access networks (μν), a base station system (BSS), and a radio network controller (rnc) (not shown). • The system 100 also includes a plurality of wireless transmit/receive units (WTRUs) 120, each of which includes a terminal device (ΤΕ) 125 coupled to a mobile terminal (〇). By stabilizing (anch〇r) the interconnection at the GGSN 110

Network protocol (IP) session and facilitates multi-layer mobility by supporting the MMSN 105's Mobility Management (MM) protocol for IP and non-IP services/services, thereby facilitating the wireless communication system. Awkward mobility. Fig. 2A shows how a dual tunnel is established in the conventional wireless communication system 1 of Fig. 1 to provide 6 M320260 IP connectivity for user plane traffic. As shown in FIG. 2A, the GPRS Companion Protocol (GTp) User Plane (GTP-U) is established between the GGSN 2〇5 and the SGSN 21〇 with the track 200, and the second user plane is established along with the track 225. Sgsn2i 〇 and benefit line grid control (4) (10) C) 215. Both contacts are dedicated to the same user. The GTP channel 220 has a user plane and a control plane. The user channel 22S is an IP channel' which has a user plane and a RAN Application Part (raNAP) control plane for controlling message transmission. When performing an internal handover of the SGSN, the SGSN 21 switches the tunnel from the old to the new RNC. The combined hard and SRNS re-granulation process is used to move the Negotiated Source Service (SRNC) to the core, network (CN) connection point to the RAN-side, while also performing the determined hard handoff. In this process, the 匕 link is relocated. If the target RNC is connected to the same-SGSN as the source SRNC, then the S(}SN internal SRNS relocation procedure is performed. If the routing area is changed, then the procedure is followed by the SGSN internal routing area update procedure. The SGSN informs it by The old routing area is also processed to detect that it is an SGSN internal routing area update. In this case, the SGSN has the necessary information related to the WTRU' and does not need to inform the HLR about the new WTRU location. If the target RNC is connected to a different The SGSN from the source SRNC performs the SRNS relocation process between the SGSNs. The process is followed by the routing area update process between the SGSNs. The Routing Area Update (RAU) is used to minimize the grouping of wireless communication systems into clusters. Paging traffic. Each cluster includes community cells (NodeBs). Each cluster is defined by a unique identifier (ie, route region identifier 7 M320260 ()). Those in the wireless communication system that pass through the cluster boundary must be executed. This is called the registration process of the routing area update. The WTRU tells the core gateway which area of the system the WTRu is in. For example, (4) TRU reception By terminating the call, the core network pages the WTRU in the last known routing area. This eliminates the need to send messages to the entire system, which in turn greatly reduces the Μβ between the systems. More processing gods are assigned to the producer traffic. The RAU can require a new connection between the GGSN and the new Cong^. Compared to the processing and message formats of the two tunnels, it is necessary to target the single tunnel. New Processing and Message Formats. In the evolution to the All-IP Network (AIPN), most services and applications migrate to the IP-based platform. _ Migration requires lp connectivity, and the resulting traffic does not have to be at the SGSN. Therefore, the single tunnel function is expected to reduce the relay and processing power at the SGSN. [New content] The present invention relates to a method for relocating a serving radio network subsystem (SRNS), which method includes at least one WTRU, source j ^C, target RNC, old SGSN, new SGSN, and GGSN are implemented in the wireless communication system. The old GTP-U tunnel is established between the source rnc and the GGSN. The source RNC sends a relocation request message to the old SGSN. The old SGSN sends a Forward Relocation Request message to the new SGSN. The new SGSN sends a Relocation Request message to the target RNC indicating the single tunnel operation, the TUSN's Track End Identity (TEID), the WTRU's identification number, and the WTRU. The packet data protocol (PDP) address. The new SGSN sends an update ρχ)ρ 8 M320260 context request message to the GGSN, which is a simple list of the teid of the target leg ^. The GGSN updates the target RNC_ with the combination of the WTRU's pDp address and identification number. The new GTP_U tunnel is established between the target RNC and the GGSN, and the old GTP-U tunnel is released. DETAILED DESCRIPTION OF THE INVENTION When the following is indignant, the term "wireless recording/receiving unit (WTRu), package, but not for the device (10)), mobile station, fixed or mobile user unit, pager, mobile phone, personal Digital Assistant (PDA), computer or any other type of device that operates in a wireless environment towel. When scaling, the term "base station, including but not limited to NGde_B, site controller, access point (AP) ) or any other type of interface connection device that can operate in a wireless environment. The features of the present invention can be incorporated in an integrated circuit (IC) or can be configured in a circuit including a plurality of interconnected devices. According to the present invention, the ip session at the GGSN is passed through the prison and multi-layer mobility is allowed, and the GpRS (3G or higher) system is gamified by supporting the existing MM agreement for non-Ip services/services provided by the SGSN. Mobility. Figure 2B illustrates a single user plane tunnel path in accordance with the present invention. The single user plane tunnel 230 reduces the SGSN 21() revenue and processing power. In the dual tunnel approach shown in Figure 2A, the SGSN 21 〇 wGTp tunnel 220 and the user plane tunnel 2 to rnc 215 are both terminated, which means that SGSN 2H) decodes the packets transmitted in both directions and They are converted into different protocol formats for the two tunnels 22〇 and 225. In the single tunnel approach shown in Figure 9B, the SGSN 210\ establishes only the tunnel between the GGSN 205f and the RNC 215' via two separate interfaces/protocols (RANAP-C and GTP-C). In the single tunnel path, the SGSN 210f no longer participates in the user plane service. Thus, user traffic passes through the SGSN 2HT unchanged in both directions (i.e., unchanged). The SGSN 210 is no longer involved in user plane processing. Only RNC 215' and GGSN 205f are allowed to perform/work on user plane traffic. The SGSN 210f only manages the control traffic associated with the user (including MM, RAU, etc.) and its IP-based traffic. The SGSN 210f uses the GTP control plane to communicate with the GGSN 205 and to communicate with the rnc 215 using the RANAP control plane to - connect 215' and GGSN 205'. When a handover occurs between RNCs, SGSN 210' is responsible for providing new RNC TEID information to the GGSN 205' and the establishment of a single tunnel 230. Figure 3 shows a prior art tunnel agreement stack based on the existing GPRS protocol. The GTP-U tunnel transfers (ie, tunnels) user data between UTRAN (which includes raN, bss, and dirty ^) and 3G_SGSN and between 3G-SGSN and 3G-GGSN. Figure 4 shows the use of the face-to-face agreement stack according to the present invention.

The 'player plane', where the user plane tunnel from the UTRAN does not terminate at the 3G-SGSN. In the post, the former TRAN was terminated at the melon (five) viewpoint. The UTRAN and GGSN show that the Ip track can be GTp based or any common Π> tunnel. In a preferred embodiment, the tunnel is used as an IP tunnel. Figure 5 is a diagram of a transmission M320260 - diagram for a method for single-track construction in accordance with the present invention. The single tunneling function reduces tearing, relaying and processing by reducing the need for protocol conversion between the RNC and GGSN interfaces and by enabling direct user plane interleaving between the packet switched (ps) domain and the GGSN. power. However, the single-tunnel approach will not eliminate the need for a 1% flow-based control. For control plane signaling, read and call/session management, the SGSN is still required, and the SGSN decides when to establish a single tunnel instead of establishing a dual tunnel. • The SN/RNC TEID for the user plane should be connected to the corresponding TEID of the other endpoints of the Nagasaki Road (ie, the RNC TEID is advertised to the GGSN and the GGSN TEID is advertised to the RNC). GGSN TEID. In the case of handover between RNCs, the SGSN is responsible for updating and providing the GGSN with the establishment of new rnc TEID information and a single tunnel. Figure 5 illustrates a single tunnel setup procedure (Packet Data Protocol (PDP) context initiation) in accordance with the present invention, which includes the WTRU 5〇5, 10 Radio Access Network (RAN) / Radio Network Controller ( It is implemented in a wireless communication system of 510, SGSN 515 and GGSN 520. The WTRU 5〇5 sends a Start PDP Context Request to the SGSN 515, which includes pDp type, ^ address, APN, Quality of Service (Q〇s) data, etc. (step 525). The SGSN 515 causes the initiation of the PDP context request to take effect, selects the ApN, and maps the APN to the GGSN 520 (step 530). The SGSN 515 determines if a single tunnel is supported and/or requested and records the presence of the RNC TEID (step 530). The SGSN 515 creates a PDP context request, which includes a PDp type, a PDP address, an APN, a single tunnel request, a rnc TEID, a q〇s, etc. M320260. (Step 535 > GGSN 520 establishes a PDP context response, which includes a pDP type, a PDP address , APN, indicator of granting a single tunnel, GGSN ΤΕΠ), QoS, etc. (step 540). The WTRU 505 and the RAN/RNC 510 establish a Radio Access Bearer (RAB) (step 545). In step 550, the SGSN 515 and the RAN/RNC 510 exchange tunnel setup signaling, including the mobile station International Subscriber Directory Number (MSISDN), PDP address, and GGSN TEID, and the SGSN 515 receives an acceptance indication from the GGSN to establish the After the tunnel # sends tunnel establishment information to the RAN/RNC 510. The SGSN 515 sends an Update PDP Context Request to the GGSN 520 (step 560) to establish the new tunnel by notifying the GGSN 520 of the RNC TEID associated with the request, and the GGSN 520 sends an Update PDP Context Response to the SGSN 515 (step

Step 565) to confirm/deny the establishment of the tunnel and related attributes (RNC TEID, PDP type, PDP address, user ID, etc.). The SGSN 515 inserts the GGSN address into its PDP context, transmits the pDp address received from the GGSN (step 570) and prepares for the return to be sent to the WTRU 5〇5. Therefore, if necessary, SGSN 515 updates GGSN 520

The PDP context in the middle reflects any changes in QoS attributes caused by the establishment of the RAN in step 545. A parent exchange is established between 510 and GGSN 520, which includes the MSISDN, PDP address, RNC TEID, and GGSN TEID (step 575). The SGSN 515 sends a Start PDP Context Accept signal to the WTRU 505 indicating the presence of a signal tunnel (step 580). Figure 6 shows the system configuration prior to the implementation of the handover procedure in accordance with the present invention. 12 M320260 Figure 7 shows the system configuration after a handover procedure using SRNS relocation and routing area update using a single tunnel approach in accordance with the present invention. After performing the SRNS relocation and routing area update of FIG. 8, the single tunnel between the GGSN and the source RNC shown in FIG. 6 (when the source RNC plays the role of the serving RNC (SRNC)) switches during the handover process. Go to the new single tunnel between the GGSN and the target RNC shown in Figure 7 (when the target RNC plays the role of SRNC). 8 is a signaling diagram of an SRNS relocation procedure using a single tunnel approach implemented in a wireless communication system including a WTRU 805, a source RNC 810, a target RNC 815, an old, in accordance with an embodiment of the present invention. SGSN 820, new SGSN 825, and GGSN 830. In step 832, an old tunnel is established between the source RNC 810 and the GGSN 830. In step 834, source RNC 810 decides to perform/initiate SRNS relocation. At that time, both the uplink and downlink user profiles are flowed through at least one of the following tunnels: the radio bearer between the WTRU 805 and the source RNC 810 (the data flows via the target RNC 815 acting as the drifting RNC); the source RNC 810 and A GTP user plane tunnel between the old SGSNs 820; and a GTP user plane tunnel between the old SGSN 820 and the GGSN 830. In step 836, the source RNC 810 sends a re-bit request message (including a relocation type, a reason, a source ID, a target ID, a transparent container from the source RNC to the target RNC) to the old SGSN 820. The source ruler nc 810 sets the relocation type to "WTRU not participating". Source RNC to M320260 The RNC transparent container includes the necessary information for relocation coordination, security functions, and wireless power control (RRC) protocol context information (including Wer capabilities). The SGSN 820 sells from the target 确定) to determine whether the SRNS relocation is an internal SRNS relocation or a _s relocation between the SGSNs. In the case of SRNS relocation between SGSNs, the old offense 82〇 sends a forward relocation request message to the new SGSN 825 (imsi, t·signal, MM context, PDP context, target identity, transparent container, RANAP cause) And start the re-granulation resource allocation process (step (4). For the allocation to the area where the RAN f is connected to the rural CN node, the old SGSN 820 can be in the pool area (p〇〇larea) if it is provided If the RAN node is connected to multiple CN nodes, there are multiple target SGSNs for each relocation target, in which case the old SGSN 820 will select one from among them as the new sgsn 825c> pDp context contains the user The GGSN address of the plane and the uplink ΤΕΠ3 for the data (the old SGSN 820 and the new SGSN 825 send the uplink packet to the GGSN address and the uplink TEID for the data). At the same time, the timer is in the old SGSN 820. The MM and PDP contexts begin. The forward relocation request message of step 838 is only applicable to the case of SRNS relocation between SGSNs. In step 840, the new SGSN 825 sends to the target RNC 815. Relocation request message (including permanent non-access stratum (NAS) WTRU identity, cause, CN domain indicator, source RNC to target RNC transparent container, RAB to be set.) M320260 According to the present invention, the relocation request message also indicates a single tunnel Operation, the TEDD of the GGSN 830, and the association between the MSISDN of the WTRU 805 and the PDP address of the TEID with the GGSN 830. In step 842, the RAB is established in accordance with the present invention and the tunnel setup at the target RNC 815 is established. Only the Iu bearer of the RAB is set between the rnc 815 and the new SGSN 825 because the current RAN will be relocated between the WTRU 805 and the target RNC 815 when the target RNC 815 plays the role of the SRNC. The RAB, RAB information element may contain information such as RAB ID, RAB parameters, transport layer address, and Iu transport association. The raB ID information element contains the network layer " Service Access Point Identifier (NSAPI) value, The RAB parameter information element provides a quality of service (QoS) profile (profiie). The transport layer address is the SGSN address for the user data, and the Iu transport association corresponds to the uplink TEID resource. After successfully allocating all necessary resources for acceptance including the Iu user plane, the target RNC 815 transmits a relocation request response message (RAB setting, RAB setting failure) to the new SGSN 825 (step 844). Each rab to be set is deprecated by a transport layer address that is the address of the target RNC 815 for the user profile, and the iu transport association corresponds to the user profile. Downlink TEID. For each target to be set, the target. 815 can receive both downlink user packets from both the source RNC 810 and the new SGSN 825; When a resource for transmission of 15 M320260* user data between the target RNC 815 and the new SGSN 825 is allocated, and the new SGSN 825 is ready for relocation of the SRNS, the relocation response message is forwarded (cause, cause) And the RAB setup information) is sent from the new SGSN 825 to the old SGSN 820 (step 846). The forward relocation response message indicates that the target RNC 815 is ready to receive the forwarded downlink PDU from the source rNC 81 (i.e., the relocation source allocation procedure was successfully terminated). The j^NAp cause is information from the target RNC 815 and to be forwarded to the source RNC 810. The RAB setup information is an information element for each ρ^Β that contains the RNC TEID and RNC IP addresses of the material forwarded from the source RNC 810 to the target RNC 815. If the target rnc 815 or the new SGSN 825 does not succeed in 'allocating resources, then the RAB Setup Information Element contains only NSAPI, which indicates that the source RNC 810 should release the resources associated with the NSAPI. The forwarding relocation response message of step 846 is only applicable to the case of SRNS relocation between SGSNs. The old SGSN 820 continues the relocation of the SRNS by sending a relocation command message (the RAB to be released and the rab subordinate to the data forwarding) to the source RNC 810 (step 848). The old SGSN 820 determines the RABs that are subordinate to the material forwarding based on the QoS, and those RABs will be included in the RABs that are subordinate to the data forwarding. The RAB ’ information element for each subordinated data forwarding will contain the raB ID, transport layer address, and iu transport correlation. These are the same transport layer address and Iu transport associations that the target RNC 815 has sent to the new SGSN 825 in the relocation request response message of step 844 and these are used to forward the downlink PDU from the source rnC 810 to the target RNC 815. . The source RNC 810 is now ready to forward the M320260 downlink user profile directly to the target RNC 815 via the Iu interface. This forwarding is only performed for the downlink data. In step 850, based on the q〇s profile, the source rnc 810 can begin forwarding data to the target rnc 815 for the RABs that are subordinate to the material forwarding. Data forwarding at the SRNS relocation will be performed through the Iu interface, which means that the material exchanged between the source RNC 810 and the target RNC 815 is replicated at the source RNC 810 and routed to the target 815 at the lp layer. For each radio bearer using the Lossless Packet Data Set Protocol (pDcp), the GTP-PDUs associated with the transmitted but not yet acknowledged pdqm>du are replicated and along with their associated downlink pDcp sequence at the IP layer. Routed to the target RNC 815. Source 81〇 continues to transmit a copy of the downlink data and receives the uplink data. Before the role of the service_€ has been taken over by the target RNC 815, and when the downlink user plane data begins to reach the destination J^C 815, the target 8I5 can buffer or discard the arriving downlink according to the associated qgS profile. Road GTP-PDU. It should be noted that the order of steps 85 〇 876 SR of the SRNS-like bit process shown in Fig. 8 does not necessarily reflect the order of the events, and may be performed in a different order or simultaneously. For example, the source brain can initiate data forwarding in step 850, and the re-clamp execution message can be sent almost simultaneously (step Μ 2) except in the case where the required delivery order of step 852 is triggered at step 85. The target abdomen ^ milk can be sent to the temple to re-clamp the position; ^ message (step μ #) and billion action information message (step 856). Thus, the target RNC 815 can receive the ran line 17 M320260 dynamic information confirmation message (step 858) while the data forwarding (step 85 〇) is in progress and before the new SGSN 825 receives the update PDp message (step 862). ^ Before the relocation execution message is sent in step 852 for the uplink and downlink f-material transmissions in the source, the source RNC (10) is suspended for the RAN, which requires the order of delivery. Source_ will start the data forwarding timer. When the source RNC 81G is ready, the source C(10) triggers the execution of the SRNS relocation by transmitting a relocation execution message (SRNS Context) via the Iur to the target rnc 815. The process of transferring the SRNS context from the source rnc 81 to the target 815' is also to transfer the SRNS role from the source RNC 810 to the target pjsjc 815. The SRNS context is transmitted for each rab of interest, and the SRNS context contains the sequence number of the GTP_PDU to be sent in the uplink and downlink directions next and the data to be used for transmitting and receiving data from the WTRU 805. A PDCP sequence number. For a PDP context (Q〇s profile) that uses an undesired delivery order, the target does not use the sequence number of the GTP-PDU to be transmitted next. The PDCP sequence number is only sent by the source RNC 810 for radio bearers, which use lossless PDCP. When the radio bearer is set or reconfigured, the use of the lossless PDCP is selected by the source RNC 810. If the order of delivery (QoS profile) is required, then consecutive GTP-PDU sequence numbers should be maintained throughout the lifetime of the PDP context. Therefore, during the entire SRNS relocation procedure for the PDP context using the required delivery order (QoS profile), the responsible GTP-U entities M320260 (RNC and GGSN) will be in terms of uplink and downlink, respectively. A consecutive GTp_pDu sequence number is assigned to the user packet belonging to the same-PDP context. In step 854, the target_815 sends a relocation detection message to the new SGSN 825 upon receiving the relocation execution trigger. For the 8-leg relocation type "WTRU is not participating," the relocation execution trigger is to receive the relocation execution message from the Iur interface in step. When the relocation detection message is sent in step 854, the target RNC 815 will start the SRNC. Operation. The target RNC 815 transmits a RAN mobility information message containing the WTRU information element and the CN poor element in step 856. The WTRU information element includes, among other things, a new SRNC identity and a user radio network temporary identity (S- RNI1). The CN information element includes, among other things, location area identification and routing area identification. All occurrences of the WTRU 8〇5 are present.

The process is coordinated in the letter connection. The X target RNC 815 establishes and/or restarts rlc and exchanges pDcp sequence numbers (pDcp sequence number (SNU), PDCP sequence number downlink (SND)) between the target 815 and the WTRU 805. The pDcp SND is the PDCP sequence number of the downlink packet of the τ-sensitive sequence of each wireless WTRU 8G5, and the lossless PDCP4DCPSND of the wireless dodge c__ confirms all mobile terminated before the SRNC relocation Packet. If the PDCP SND acknowledges receipt of the packet forwarded from the source RNC 810, the target c will still discard the packets. The PDCP SNU is the PDcp sequence number of the next expected uplink packet received by the RNC in each radio bearer, which uses the lossless PDCp in the 19 M320260 source RNC 810. The pDCp SNU acknowledges all WTRU-originated packets successfully transmitted before the SRNc is relocated. If the pDCp SNU acknowledges receipt of the packet received in the source rNC 81, the WTRU 805 will discard the packets. Upon receiving the RAN mobility information message at step 856, the WTRU 805 may begin transmitting uplink user lean to target 815. When the WTRU 805 reconfigures itself, it sends a _ mobility information confirmation message to the target rnc 815 at step 858'. This indicates that the WTRU 805 is also ready to receive downlink data from the target rnc 815. In step 860, the new SGSN 825 sends an Update PDP Context Request message to the GGSN 83 in step 86, indicating the single-channel configuration and the TEID of the target RNC 815 in accordance with the present invention. In response, ggsn 83 〇 updates the TEID of the target RNC 815 with the PDP address to the MSISDN of the WTRU 805. Therefore, the SGSN 825 sends the name of the new connection to which the GGSN 83 forwards the data. Once the information is received, (5) View 830 updates the information associated with this track (i.e., the new destination). For all RANs, the target RNC 815 initiates uplink reception of the data and begins transmissions to the uplink GTp_pdu of the new SGSN 825, and the target RNC 815 begins processing the downlink GTP_PDUs that have been buffered and arrived, and begins to Downlink transmission of the WTRU 805. Once the relocation detection message is received at step 854, the user plane can be switched from the source RNC 810 to the target inverse 815. If SRNS relocation is SRNS relocation between SGSNs, then new sgsn 20 M320260

825 sends an update PDP context request message (new SGSN address, SGSN TEID, negotiated Q〇S) to the GGSN of interest. The GGSN updates the PDP context field of the GGSN and returns an update pDp context response (GGSNTEID) in step 862. Then, at step 864, a new GTP user plane tunnel is established between the target RNC 815 and the GGSN 830 in accordance with the present invention. If the new SGSN 825 has received an Update PDP Context Response message from the GGSN 830, the new SGSN 825 forwards the uplink user profile to the GGSN 83 through the new GTP User Plane Tunnel. Otherwise, the new SGSN 825 forwards the uplink subscriber profile to the Ip address and TEID of the GGSN 83(), which was received by the Forward Relocation Request message in step (10) before the new SGSN. When the target RNC 815 receives the RAN mobility information acknowledgement message in step 858 (i.e., successfully exchanges the ID and S_RNTI of the target RNC 815 with the WTRU 8〇5 via the radio protocol), at step 866, the target 815 passes the new SGSN 825. Wei repositions the completion message and initiates the relocation process. The purpose of the relocation completion process is to pass the target RNC 815 to the CN, and the SRNS is re-clamped. If the leader plane is not re-positioned and the relocation is completed, the CN switches the user plane, source leg "810 to the target RNC 815. If the SRNS relocates the SRNS relocation between the SGSNs, then in step _, the new sgsn 825 signals the completion of the SRNS relocation procedure by sending a forward relocation complete message. 21 M320260 . -a receives the replanted 4, or if SRNS relocation occurs between the SGSNs, then in step 87, the old sgsn 82〇 sends (4) the re-grained message to the new SGSN. And at step 872 'the old SGSN 820 sends an Iu Release Command message to the source rnc 810. When the RNC lean feed forwarding timer expires, at step 874, source 81 〇 responds with an Iu release completion message. After the WTRU 805 has completed the RNTI relocation procedure, and if the new routing area identity is different from the old one, then in step 876, the WTRU 805 initiates a routing area update procedure. Figure 9 shows the system configuration prior to the hard-switching and SRNS relocation combined with the single tunnel and the routing area update procedure in accordance with the implementation of the present invention. Figure 10 shows the system configuration after a hard-switching and SRNS relocation combined with a single tunnel and a routing area update procedure in accordance with an implementation of the present invention.

11 is a transmission diagram of a single tunnel-based hard handover and SRNS relocation procedure implemented in a wireless communication system, including a WTRU 1105, a source RNC 1110, in accordance with another embodiment of the present invention. Target RNC 1115, old SGSN 1120, new SGSN 1125, and GGSN 1130. The process of Figure 11 can be applied to both SRNS relocation within the SGSN and SRNS re-determination between the SGSNs. Moreover, the signaling process can be applied to the relocation of the BSS to the RNS, and vice versa, as well as to the relocation of the BSS to the BSS. In step 1132, an old tunnel is established between the source RNC 1110 and the GGSN 1130. In step 1134, the source RNC 1110 decides to execute/start the combination 22 M320260 0 hard handoff # SRNS . The uplink, downlink, and downlink user data are all streamed via at least one of the following tunnels: the radio bearer between the WTRU 1105 and the source RNC 1110 (no drift is available); the source RNC 1110 and the old SGSN 112〇 Between the GTp user planes; and the GTp user plane tunnel between the old SGSN 1120 and the GGSN 113〇. At step 1136, the source RNC 111 sends a re-bit request message (including a relocation type, a reason, a source ID, a target ID, a transparent container from the source RNC to the target RNC) to the old SGSN 112. The source excitation type 111 sets the relocation type to "WTRU is not participating." Source to target Xin. Transparent containment includes the necessary information for relocation coordination, security functions, and protocol context information (including WTRU capabilities). The old SGSN 1120 determines from the target SR) that the SRNS relocation is an SRNS relocation within sgsn or an SRNS relocation between SGSNs. In the case of SRNS relocation between SGSNs, the old SGSN 112 initiates relocation by sending a Forward Relocation Request message (imsi, teid, MM context, PDP context, target identity, transparent margin) to the new SGSN 1125. Resource allocation process (step 1138). For an area allocated to an internal domain connection using a node to multiple cn nodes, the old SGSN 112G may have multiple relocations for each relocation in the pool area (if it provides an internal domain connection of the RAN node to multiple CN nodes) Target SGSN of the target, in this case, the old SGSN 1120 will select one from among them as the new SGSN 11254DP context containing the GGSN address for the user plane and the upper 23 M320260 subscription link TEID for the data (old SGSN 1120 and new The SGSN 1125 sends the money GGSN button and the pin-up_uplink TmD to the uplink key packet. At the same time the 'timer starts on the mm and PDP context in the old SGSN 1120. The forwarding relocation request message of step 1138 is only applicable to the case of SRNS relocation of the guilty. In step 1140, the new SGSN 1125 sends a re-carry request message (including a permanent non-access stratum (NAS) WTRU identity, a reason, a CN domain indicator, a source RNC to a target transparent container, a RAB to be set) to the target c 1115. For an area allocated to an internal domain connection using a negotiation node to a plurality of CN nodes, if the old SGSN 112 provides an internal domain connection of the node to the plurality of CN nodes, the old sgsn 1120 may have multiple in the pool area. For each retargeting target SGSN, in this case, the old SGSN 112 will select one from among them as the new SGSN 1125. The 4DP context contains the GGSN address for the user plane and the uplink TmD for the profile (old The SGSN 112 and the new SGSN 1125 send the uplink packet to the GGSN address and the uplink TEID for the data. At the same time the 'timer starts on the MM and PDP contexts in the old sgsn 1120. The Forward Relocation Request message is only applicable to the case of SRNS relocation between SGSNs. According to the present invention, the relocation request message also indicates a single tunnel operation, ΤΕΠ of the GGSN 1130, and an association between the MSISDN of the WTRU 1105 and the PDP address of the TEID having the GGSN 1130. In step 1142, the rab is established in accordance with the present invention and the tunnel settings at the target RNC 1115 are established. Only the iu bearer of the RAB is set between the target rnC1115 and the new sgsn1125 24 M320260, because the existing rnc 1115 will relocate the existing between the WTRU 11〇5 and the target 1115 when the role of the SRNC is played. For each requested RAB, the information element of the RAB may contain information such as RAB ID, RAB parameters, transport layer address, and Iu transport association. The RAB ID information element contains the Network Layer Service Access Point Identifier (NSAPI) value, while the RAB Parameter Information Element provides an overview of the Quality of Service (Q〇S). The transport layer address is the SGSN address for the user data, and the Iu transport association corresponds to the uplink TmD data. After successfully allocating all necessary resources for acceptance including the IU user plane, the target RNC 1115 sends a relocation request to the new SGSN 1125 (RAB setting, RAB setting button) (step 1144). Each of the to-be-sets is defined by a transport layer address that is the address of the target RNC 1115 for the user profile, and the Iu transport association corresponds to the downlink for the user profile. Road 1. For each RAB to be set, the target RNC 1115 can receive the downlink user packet from both the source RNC 1110 and the new SGSN 1125. When the resource for the user miscellaneous transmission between the target RNC 1115 and the new SGSN 1125 is allocated, and the new SGSN HU is ready for SRNS re-clamping, the relocation response message is forwarded (cause, transparent b^H^) RANAP^^ . @#RNC ttfl) ^ SGSN 1125 is developed to the old SGSN 1120 (step, step 1146). The forward relocation response message indicates that the target RNC im has been admitted to receive 25 M320260 from the source. • The forwarded PDU is forwarded (ie, the relocation resource allocation process is successfully terminated) RAN transparent container and RANAP cause are The information from the target coffee (::1115) is forwarded to the source RNC 1110. The target RNC information is an information element for the parent RAB to be set, which contains the RNC of the data forwarded from the source coffee (2; 1110 to the target RNC 1115). TEID and RNC IP address. The forwarding relocation response message of step 1146 is only applicable to the case of SRNS relocation between SGSNs. • Old SGSN 1120 sends a relocation command message to the source RNC 1110 (RAB to be released and subordinated The data forwarding rab) continues the relocation of the SRNS (step 1148). The old SGSN 1120 determines the RABs that are subordinate to the material forwarding based on Q〇S - and those RABs should be included in the RAB subordinate to the data forwarding. The RAB 'information element for each subordinate to the data forwarding will contain the rab ID, the transport layer address, and the iu transport correlation. These are the relocations of the target RNC 1115 at step 1144. The same transport layer address that has been sent to the new SGSN 1125 in the response message is associated with the transport signal, and these are used to forward the downlink PDU from the source RNC 1110 to the target RNC 1115. The source RNC 1110 is now ready to pass the Iu The interface forwards the downlink user profile directly to the target RNC 1115. The ^ forwarding is performed only for the downlink data. In step 1150, according to the Q〇s profile, the source rnc 111〇 can begin to be subordinate to the data forwarding. The data is forwarded to the target (10) c 1115. Data forwarding at the SRNS relocation will be performed through the Iu interface, which means that the material exchanged between the source RNC 1110 and the target RNC 1115 is replicated in the source RNC 1110, and at 1] The layer is routed to the target version. 26 M320260 • For each radio bearer using the Lossless Packet Data Set Protocol (PDCP), the GTP-PDU associated with the PDCP-PDU that has been transmitted but not yet acknowledged is copied and The IP layers are routed along with their associated downlink pDcp sequence numbers to the target RNC 1115. The source RNC 1110 continues to transmit copies of the downlink data and receives uplink data. Before the role of the service j^C has not been taken over by the target RNC 1115, and when the downlink user plane begins to arrive at the destination RNC 1115, the target • 1115 can buffer or discard the arrival according to the relevant Q〇s profile. Downlink GTP-PDU. It should be noted that step 11 of the hard handoff and relocation process of the single tunnel is combined in Fig. 11 (the order of M184 does not necessarily reflect the order in which the events occur and may be performed in a different order or simultaneously. For example, source The RNC 1110 may begin data forwarding in step 115, transmitting the RRC message to the WTRU 1105 and forwarding the SRNS context message to the old SGSN almost simultaneously.

• Before the RRC message is sent in step 1152, the uplink and downlink _tree·turn axis are suspended in 1110. The RRC message is, for example, reconfigured for the physical channel to the relocation, or between the system to the BSS (four), or from the handover of the B#s^ or the relocation of the BSS to the BSS. Switch commands. When the source RNC 1110 is ready, the source sends an RRC message, such as a physical channel reconfiguration, to the WTRUll 〇 5, which is provided to the source (10) transparent device in the target coffee 1115, for example, the physical channel 27 M320260 element, CN information The element) message triggers the execution of the relocation of the SRNS (step 1152). The WTRU information element includes, among other things, a new SRNC identity and an S-RNTI. The CN information element includes, among other things, a location area identifier and a routing area identifier. The source RNC 1110 continues to perform relocation of the SRNS by transmitting a forward SRNS context message (raB context) to the target RNC 1115 via the old SGSN 1120 and the new SGSN 1125 (steps 1154, 1156, and 1160). From the new SGSN 1125 to the old SGSN 1120, forwarding the SRNS context message is acknowledged by forwarding the SRNS Context Response message (step 1158). The purpose of this process is to transfer the SRNS context from the source RNC 1110 to the target RNC 1115 and the SRNS role from the source RNC 1110 to the target RNC 1115. The SRNS context is sent for each rab of interest, and the SRNS context contains the sequence number of the GTP PDUs to be transmitted in the uplink and downlink directions next and the data to be used for transmitting and receiving data from the WTRU 1105. A PDCP sequence number. The PCDP_sequence number is only transmitted by the source rnc 1110 for radio bearers that use lossless pDCP. The use of lossless PDCP is selected by the source RNC 1110 when setting up or reconfiguring the radio bearer. For a PDP context (qos profile) that uses an undesired delivery order,

The target RNC ms does not use the sequence number of the GTP-PDU to be transmitted next. If the order of delivery (Q〇S profile) is required, then consecutive GTp_pDU sequence numbers should be maintained throughout the lifetime of the pDp context. Therefore, during the entire SRNS relocation process for the pDp context using the required delivery order (Q〇s profile), responsible (}11>-1; entity 28 M320260 (RNC 1110 and 1115, and GGSN 1130) The uplink and downlink user packets belonging to the same PDP context will be assigned consecutive GTP-PDU sequence numbers. The target RNC 1115 establishes and/or restarts the RLC and exchanges the PDCP sequence number between the target RNC 1115 and the WTRU 1105. (PDCP-SNU, PDCP-SND). The PDCP-SND is the PDCP sequence number of the next expected downlink packet received by the WTRU 1105 in each radio bearer, using the lossless PDCP in the source RNC 1110 The PDCP-SND acknowledges all mobile terminated packets successfully transmitted before the SRNC relocation. If the PDCP-SND acknowledges receipt of the packet forwarded from the source RNC 1110, the target 1115 will discard the packets. The PDCP-SNU is in each radio bearer. The next expected PDCP sequence number of the expected uplink packet received by rnc, the radio bearer uses the lossless PDCP in the source RNC 1110. The PDCP-SNU confirms that the SRNC is relocated before All mobile original packets transmitted. If the pDCp-SNU acknowledgment Φ receives the packets received in the source milk busy 1110, the wtru 1105 will discard the packets. The target RNC 1115 sends a new sgsn 1164 when it receives the relocation execution trigger. Clamping detection information (step 1164). For the SRNS relocation type "WTRU is not participating, the relocation execution trigger may be received from the Uu interface (ie, when the target rnc detects the WTRU Cong on the lower layer). The target RNC 1115 starts the SRNC operation when the relocation detection message is sent in step 1164. In step 1166, the new S(10) 1125 sends a further 29 M320260 new PDP context request message to the GGSNU3, indicating the single-channel configuration and target according to the present invention. In response, the GGSN 113 updates the TEID of the target RNC 1115 with the PDP address to the MSISDN of the WTRU 1105. For all RABs, the target RNC 1115 initiates the uplink reception of the data and begins. The transmission of the uplink GTP-PDU to the new SGSN 1125' and the target RNC 1115 begins processing the downlink GTP-PDU that has been buffered and arrived, and Start downlink transmission to the WTRU 1105

Upon receiving the relocation detection message at step 1164, the CN can switch the user plane from the source RNC 1110 to the target rnc 1115. If the SRNS relocation is an SRNS relocation between the SGSNs, the new SGSN 1125 sends an Update PDP Context Request message (new SGSN Bit Address, SGSN TEHD, Negotiated Q〇s) to the GGSN of interest. The GGSN updates its PDP Context Block and returns an Update pdp Context Response (GGSN TEID) at step 1170. At step 1174, according to the present invention, a new Kenten is established between the targets _0: 1115 and 008 > 11130? User plane tunnel. If the new SGSN 1125 has received an Update PDP Context Response message from the GGSN 1130, the new SGSN 1125 forwards the uplink user profile to the GGSN 1130 via the new GTP User Plane. Otherwise, the new SGSN 1125 forwards the uplink user profile to the IP address and TEID of the GGSN 1130, which was received by the Forward Relocation Request message at step U38 prior to the new SGSN 1125. 30 M320260, when the WTRU 1105 reconfigures itself, it sends an RRC message (e.g., physical channel reconfiguration complete message) to the target RNC 1115. If a forwarding SRNS context message with a sequence number is received at step 1160, then the packet exchange with the WTRU 1105 can begin. If the message has not been received, the target 1115 can begin packet transmission for all RABs, which does not require maintaining the order of delivery. When the target RNC 1115 receives the rrc message in step 1168, in step 1172, the target coffee. The 1115 initiates the relocation completion process by sending a relocation to the new SGSN II25. The purpose of the relocation completion process is to indicate to the CN through the target RNC 1115 that the SRNS relocation has been completed. If the user plane has not been switched at the time of relocation detection and once the relocation is completed, the CN switches the user plane from the source 1〇<[(: 111〇 to the target RNC 1115. If the SRNS relocation is between the SGSNs) SRNS relocates, then in step 1176, the new SGSN 1125 signals the completion of the SRNS relocation procedure to the old SGSN 1120 by transmitting a Forward Relocation Complete message. Upon receiving the Forward Relocation Complete message, or if an SGSN has occurred The inter-SRNS relocation, then in step 1178, the old sgsn 1120 Xiaoxin SGSN sends a Forward Relocation Complete Answer message, and in step 1180, the old SGSN 1120 sends a Rush Command message to the source port 111. When the RNC Data Forwarding Timer Upon expiration, in step 1182, the source RNC 1110 responds with a ju release completion message. After the WTRU 1105 has completed the relocation procedure, and if the new routing area identifier is different from the old one, then at step 1184, the WTRU 1104 M320260 Initiating the routing_update process. The features and elements of the novel are better in the preferred embodiment: Interpret, but each feature or element can be used alone without the above, other features and elements of the square handle, or in combination with the elements and elements of the (4) .

The method or flow chart described by Wang Zhong can be implemented by a computer program software implemented in a computer readable storage medium, executed by a general purpose computer or processor. Examples of computer readable age ships include only items. Reactive memory (R〇M), random access memory (mm), scratchpad, cache memory, semiconductor memory device, magnetic media such as internal hard disk and removable disk, magneto-optical media And such as CD-ROM disks and

Optical media such as digital multi-function disk (DVD). Suitable processors include, for example, general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with the DSP core, Controller, microcontroller, specific function integrated circuit (ASIC), field programmable gate array (FPGAS) circuit, any integrated circuit and/or state machine. The processor associated with the software can be used to implement a radio frequency transmitter that can be used in a WTRU, user equipment, terminal, base station, radio network controller, or any host. The WTRU may be used in conjunction with modules implemented as hardware and/or software, such as cameras, video camera modules, video phones, speaker phones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keyboards, Bluetooth 8 Module, FM radio unit, liquid crystal display (LCD) display unit, organic light emitting diode (qleD) display 32 M320260 display unit, digital music player, media player, video game player module, internet Road browser and / or any wireless local area network (WLAN) module.

33 M320260 [Description of the Drawings], the following description of the preferred embodiments can be understood in more detail. These preferred embodiments are given by way of example and are understood in conjunction with the accompanying drawings. : 1 shows a conventional GPRS and 3 〇 wireless communication system; FIG. 2A shows the establishment of a conventional double tunnel; FIG. 2B shows the establishment of a single tunnel according to the present invention; FIG. 3 shows the existing Technical tunneling stack; Figure 4 shows a single tunnel protocol stack configured in accordance with the present invention; Figure 5 illustrates a single tunnel establishment process (Packet Data Protocol (PDP) context initiation) in accordance with the present invention; 6 illustrates a system configuration prior to implementing a re-clamping process and routing area update using a single-pass path in accordance with the present invention; FIG. 7 illustrates a re-positioning process using a single-pass path in accordance with the present invention and System configuration after routing area update; Figure 8 is a transmission diagram of the SRNS relocation process according to the present invention; Figure 9 shows a hard handover and SRNS relocation combined with a single tunnel according to the implementation of the present invention And the system configuration before the routing area update process; FIG. 10 shows the system configuration after the hard handover and SRNS relocation combined with the single tunnel and the routing area update procedure according to the implementation of the present invention; FIG. 11 shows The implementation of another new embodiment incorporates a single tunnel hard handoff and a signaling scheme for the SRNS relocation process. 34

Claims (1)

Patent Application Range: A wireless communication system for implementing Service Radio Network Subsystem (SRNS) relocation, including: (a) Source Radio Network Controller (RNC); (b) Gate This General Packet Radio Service a (GpRS) support node (GGSN) coupled to the target rnc via a first GpRS Tunneling Protocol (GTp) User Plane (GTP-U) tunnel; and (c) a target RNC coupled to the second Grp_u tunnel The GGSN, wherein the second GTP-U tunnel is established between the target belly c and the GGSN, and the first GTp_u tunnel is released when performing SRNS relocation. The wireless communication system of claim 1, further comprising: (d) at least one wireless transmission/reception unit (WTRU) electrically coupled to at least one of the source RNC and the target RNC; e) a service GPRS support point (§GSN), electrically coupled to the source RNC; and (f) a second SGSN electrically coupled to the first SGSN and the target RNC 'where the second SGSN includes Means for transmitting a relocation request message to the target, and means for receiving a forward relocation request message sent by the first SGSN, the relocation request message indicating a single tunnel operation, a tunnel end identity (TEID) of the GGSN, The WTRU's identification and the WTRU's Packet Data Protocol (pDp) address. The wireless communication system of claim 2, wherein the second SGSN includes means for transmitting an update pDp request message to the GGSN, The GGSN indicates the single tunnel operation and the TEID of the target RNC. No. 4. A wireless communication system for implementing hard handover and service radio network subsystem (SRNS) relocation combined with a single tunnel, the system comprising: ^ (a) source radio network controller (rnc); (b) gateway general packet radio service (GpRs) support node (GGSN), which passes the first GPRS tunneling protocol (GTp) a user plane (GTP-U) tunnel coupled to the target RNC; and (C) a target RNC coupled to the GGSN via a second GTPW tunnel, wherein the second gtp-u tunnel is established at the target and the GGSN And the first GTMJ tunnel is released when performing hard handover and SRNS relocation combined with a single tunnel. 5. The wireless communication system of claim 4, further comprising: (d) at least one WTRU, electrically coupled to at least one of the source RNC and the target RNC (4) a first serving GPRS support node (SGSN) electrically coupled to the source RNC; and (f) a second SGSN electrically coupled to the first SGSN and the target RNC 'where the first SGSN includes Thanks for this goal. Means for transmitting a relocation request message and for receiving the first SGSN 37 And a means for forwarding a relocation request message sent by the M320260, the relocation request message indicating a single tunnel operation, a tunnel end identity (TEID) of the GGSN, an identification number of the WTRU, and a Packet Data Protocol (PDP) address of the WTRU. 6. The wireless communication system of claim 5, wherein the second SGSN comprises means for transmitting an update PDP context request message to the GGSN, the GGSN indicating a single tunnel operation and a TEID of the target RNC. 38 M320260 VII. Designated representative map: (1) The representative representative of the case is: (8). (ii) A brief description of the component symbols of this representative diagram: 8 3 0 Gateway General Packet Radio Service Support Node (GGSN) 810, 815 Radio Network Controller (RNC) 820, 825 Support Node (SGSN) 805 Wireless Transmission/Reception Unit (WTRU)