WO2013000289A1

WO2013000289A1 - Mobility management method for direct tunnel, network element, and system

Info

Publication number: WO2013000289A1
Application number: PCT/CN2012/072092
Authority: WO
Inventors: 沈炯
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-06-28
Filing date: 2012-03-08
Publication date: 2013-01-03
Also published as: CN102858008A; CN102858008B

Abstract

The present invention relates to a mobility management method for a direct tunnel, a network element, and a system, applied in a scenario that a terminal moves. The method comprises: a target radio network controller (RNC) sending, through a new serving GPRS support node (SGSN) and an original gateway GPRS support node (GGSN) in order, to a new GGSN a downlink media plane tunnel address allocated by the target RNC to the terminal; and the new GGSN allocating an uplink media plane tunnel address to the terminal and sending the uplink media plane tunnel address to the target RNC through the original GGSN and the new SGSN in order. The present invention solves the problem of the alternate route on the basis of implementing the direct tunnel.

Description

Mobility management method, network element and system of direct tunnel

Technical field

The present invention relates to the field of mobile communication technologies, and in particular, to a mobility management method for a direct tunnel, a network element (including a Serving GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN)), and a system.

Background technique

The existing Wideband Code Division Multiple Access (WCDMA) system is an important system and method for implementing service access based on wireless WCDMA technology. The core network architecture of WCDMA is shown in Figure 1. It includes the GPRS (General Packet Radio Service) node (Serving GPRS Support Node, SGSN for short) and the Gateway GPRS Support Node (GGSN). Network element such as home subscriber registration register, in this paper, the home location register (HLR) in 2G (second generation mobile communication technology) and the home subscriber server in 3G (Home Subscriber Server, referred to as HSS) is collectively referred to as the Home Subscriber Register and is represented by HLR/HSS. Since the existing TD-SCDMA (Time Division-Synchronous Code Division Multiple Access) core network uses the same architecture as WCDMA, the following WCDMA refers to WCDMA and TD-SCDMA.

The SGSN is a basic component network element of the GPRS network. It is a new network element device introduced in the Globle System for Mobile Communication (GSM) network to provide GPRS services. It mainly performs routing and forwarding, mobility management, session management, logical link management, authentication and encryption of packet data packets.

The GGSN provides routing and encapsulation of data packets between the WCDMA network and the external data network, acting as a gateway, which includes routing information of PS (Packet Switched) attached users, and routing information is used to tunnel data packets to the MS. The current attachment point, ie, SGSN.

The HLR/HSS is used to store the user's packet domain subscription data and routing information.

RNC is a radio network controller (Radio Network Controller), which is a radio access network. Component for providing mobility management, call processing, link management, and switching mechanisms. In the 3GPP 23.060 R7 version and later, the direct tunnel technology is introduced. The media plane tunnel can be directly established between the RNC and the GGSN, and the media plane data is not forwarded by the SGSN.

The Node B is a base station (wireless transceiver) that communicates with the UE through the Uu interface.

An important feature of the mobile network is that it keeps the continuous transmission and reception of the service while the terminal is continuously moving. This is the switching function. For the WCDMA core network, the handover function is implemented in the relocation process and the handover between 2G and 3G systems. This paper mainly discusses the relocation process and does not involve the handover between 2G and 3G systems.

The relocation process completes the process of changing the access path of the data in the core network with the location of the terminal in the process of using the service data, thereby ensuring the continuity of the service. The relocation process is the most complex process in the mobile communications core network. It involves the functions of data forwarding and routing update.

The relocation process is divided into the following scenarios:

- Service Radio Network Subsystem (SRNS) relocation;

- joint hard handoff and SRNS relocation;

- Cell/UT (UTRAN Registration Area) joint update and SRNS relocation;

- routing area update;

- SRNS relocation is canceled.

Service SRNS relocation process

Service The SRNS relocation procedure is only performed when the MS (terminal) is in the PMM - CONNECTED state, and the Iur interface is used to transmit control signaling and user data.

Serving the SRNS relocation procedure for migrating UTRAN to the CN from a source RNC to a target RNC from a "fixed rest position" on the UTRAN (UMT (Universal Mobile Telecommunication System) Terrestrial Radio Access Network, UMTS Terrestrial Radio Access Network) side Junction. In this process, Iu links are relocated. SGSN SRNS (Serving Wireless Network Subsystem) if the target RNC is connected to the same SGSN connected to the source RNC The internal relocation process is performed, and the process does not perform SGSN handover. If the target RNC and the source RNC are connected to different SGSNs, the service SRNS relocation process of the SGSN handover scenario needs to be performed.

Figure 2a shows the relocation of the RNC when the source RNC (Serving RNC) and the target RNC are connected to different SGSNs. Figure 2b shows the SRNS relocation process and the routing area update process.

After the SRNS relocation process and the RA (Routing Area) are updated, the MS registers with the new SGSN, the MS is in the PMM-CON ECTED state for the new SGSN, and the target RNC acts as the serving RNC.

The SRNS relocation process is illustrated in Figure 3 (based on 3GPP TS 23.060 R7 and later), including the relocation preparation process, the relocation execution process, and the relocation completion process, as follows:

Step 301: The source RNC decides to initiate SRNS relocation;

Step 302: The source RNC sends a Relocation Required message (including a relocation type, a reason, a source ID, a target ID, a source RNC to a target RNC transparent container, etc.) to the original SGSN to initiate a relocation preparation process.

The source RNC to the target RNC transparent container includes information necessary for relocation coordination, security functionality and RRC protocol context information (including UE capacity).

Step 303: The original SGSN sends a "Forward Relocation Request" message to the new SGSN according to the target cell ID. If it is determined that the SRNS relocation is an SRNS relocation between the SGSNs, a relocation resource allocation process is initiated.

Step 304a: The new SGSN sends a relocation request message to the target RNC.

The relocation request message includes a permanent NAS (non-access stratum) UE identification number (such as International Mobile Subscriber Identity (IMSI)), a reason, a CN domain indicator, a transparent container of the source RNC to the target RNC, and a radio access to be set. Bearer (Radio Access Bearer, abbreviated as RAB).

The request message also carries the user plane IP address and TEID of the GGSN for establishing a direct tunnel between the RNC and the GGSN.

Step 304b: The target RNC accepts all necessary resources of the RAB, including Iu, and after the user plane is successfully allocated, establishes an RAB bearer with the new SGSN, and sends a Relocation Request Acknowledge message to the new SGSN. Step 305: After the resource for transmitting user data between the target RNC and the new SGSN is allocated, and the new SGSN is ready for relocation of the SRNS, the new SGSN sends a "Forward Relocation Response" message to the original SGSN. At this point, the relocation resource allocation process was successfully terminated.

Step 306: The original SGSN sends a Relocation Command message to the new RNC to continue the relocation of the SRNS.

The relocation command message includes: the RAB to be released and the RAB subject to data forwarding. The original SGSN determines the RAB subject to data forwarding according to Quality of Service (QoS).

Step 307: After receiving the relocation command message from the PS domain, the source RNC starts the data forwarding timer, and the source RNC starts to forward the data.

Data forwarding in SRNS relocation should be performed through the Iu interface, meaning that the data exchange between the source SRNC and the target RNC is replicated in the source SRNC and sent to the target RNC at the IP layer.

Step 308: When the relocation preparation process is successfully terminated, and the source RNC is ready, the source RNC triggers the execution of the SRNS relocation by sending an RRC (Radio Resource Control) message provided in the "target RNC to the source RNC transparent container" to the MS. .

The RRC message may be a physical channel reconfiguration message (Physical Channel Reconfiguration), and the message carries the UE information element and the CN transparent container.

Step 309: When receiving the relocation execution trigger, the target RNC shall send a relocation detection message to the new SGSN. When the relocation detection message is sent, the target RNC shall initiate the source RNC operation.

Step 310: The target SRNC sends the RAN mobility information to the source RNC, including the local area identifier and the routing cell identifier, and the serial number between the terminal and the SRNC. After receiving this message, the terminal starts sending uplink packets to the target RNC.

After the terminal completes the reconfiguration, it sends a RAN mobility information confirmation message to the target RNC, informing the target RNC that it is ready to receive downlink data.

Step 311: The target SRNC sends a relocation complete message to the new SGSN to initiate a relocation completion process, where the target SRNC address is carried. If the direct SR tunnel mode is used, the relocation complete message carries the target SRNC address media plane address, and the target SRNC media plane Tunnel endpoint identifier (TEID).

Step 312: If the SRNS relocation is a relocation between the SGSNs, the new SGSN sends a Forward Relocation Complete message to the original SGSN. The original SGSN returns a confirmation of the forwarded relocation complete message.

Step 313: If the SRNS relocation is a relocation between the SGSN SRNS, or the SRNS relocation is a relocation using the direct tunnel in the SGSN SRNS, the new SGSN sends an Update PDP (Packet Data Protocol Context) context request. The message (which carries the new SGSN address, the SGSN tunnel endpoint identifier, the target RNC address for the media plane, the RNC TEID, the negotiated QoS) to the relevant GGSN; if it is the direct tunneling mode, the new SGSN sends the updated PDP context request message. Carrying the new SGSN control plane address, the new SGSN control plane tunnel endpoint identifier, the target RNC address media plane address, the target RNC media plane tunnel endpoint identifier and the DTK Direct Tunnel Indicator) and the associated QoS and other related information to the relevant GGSN, and the GGSN updates them. The PDP context field, and returns an Update PDP Context Response message, carrying the GGSN tunnel endpoint identifier, and the like.

Step 314: After receiving the forwarding relocation complete message, the original SGSN sends an Iu release command (Iu

The Release Command message is sent to the source RNC. When the RNC data forwarding timer expires, the source RNC responds with an Iu Release Complete message.

Step 315: After the MS completes the reconfiguration process, if the new routing area identifier is different from the previous one, the MS initiates a routing area update process.

The routing area update process is to register the current location information of the MS in the new SGSN, and the new

The SGSN information is updated to the HLR. The routing area update part of this flow is only a subset of the RA update process performed because the MS is in the PMM-CON ECTED state.

Joint hard handoff and SRNS relocation process

Joint hard handoff and SRNS relocation are used for situations where there is no Iur interface between RNCs, and the process is only performed when the MS is in the PMM - CONNECTED state.

When the joint hard handover and SRNS relocation procedures are used to perform hard handover determined by UTRAN, the UTRAN is migrated from the source RNC to the target RNC on the UTRAN side to the CN (core network) connection. Point. In this process, the Iu link is relocated. If the target RNC is connected to the same SGSN as the source RNC, the relocation procedure inside the SGSN SRNS is performed. If the SGSN to which the target RNC is connected is different from the SGSN to which the source RNC is connected, the SRNS relocation procedure between the SGSNs is performed. After performing this process, the routing area update process between the SGSNs is then performed.

Cell/URA joint update and SRNS relocation process

This process is only performed for the MS in the PMM-CON ECTED state, where Iur carries control signaling but no user data.

The cell/URA joint update and SRNS relocation are used to migrate the UTRAN from the source SRNC to the target RNC to the CN connection point on the UTRAN side when performing cell reselection in the UTRAN. In this process, the Iu link is relocated.

Routing area update

When the attached MS detects that it has entered the new RA or the periodic RA update timer expires, a routing area update is required.

The SGSN detects that it also manages the pre-RAS and detects that it is a routing area update inside the SGSN. In this case, the SGSN has the necessary information of the MS, so it is not necessary to notify the GGSN or the HLR of the new MS location, so the GGSN handover is not performed. In the routing area update between SGSNs, only the MS is not in the PMM connection state, the new SGSN sends a PDP context update request to the GGSN. In the PMM connection state, the PDP context change request is in the service SRNS relocation process or the joint hard handover and the SRNS are heavy. The positioning process is completed.

The routing area update process is shown in Figure 4 (based on 3GPP TS 23.060 R6 version), as follows: Step 401: If the RRC connection has not been established, an RRC connection is established. The MS sends a Routing Area Update Request message (Packet Temporary Mobile Subscriber Identity P-TMSI, Pre-RAI, Pre-P-TMSI Signature, Update Type, Follow on Request) to the new SGSN.

Step 402: If the RA update is a routing area update between the SGSNs, and the MS is previously in the PMM-IDLE (Packet Domain Mobility Management - Idle) state, the new SGSN sends an SGSN Context Request message (pre-P-TMSI, pre-RAI, pre-P- TMSI signature) to the original SGSN, get the MS MM And PDP context.

In step 402a, the original SGSN sends an SRNS Context Request message to the source SRNC, and obtains an SRNS Context Request Reply.

Step 403: The original SGSN sends an SGSN context request response to the new SGSN.

Step 404, security processing function.

Step 405: If the RA update is a routing area update between the SGSNs, the new SGSN sends an SGSN context confirmation message to the original SGSN.

Step 406: The original SGSN sends a data forwarding command to the source SRNC.

Step 407, if the source SRNC has buffered data in step 402a, the source SRNC forwards the data to the original SGSN.

Step 408: The original SGSN forwards data to the new SGSN.

Step 409: If the RA update is a routing area update between the SGSNs, and the MS is not in the PMM connection state, the new SGSN sends an Update PDP Context Request (also referred to as a PDP Context Change Request) message to the original GGSN, and the original GGSN sends a PDP context change to the new SGSN. Answer.

Step 410: If the RA update is an RA update between the SGSNs, the new SGSN notifies the HLR of the change of the SGSN by sending an update location (SGSN number, SGSN address, IMSI) to the HLR.

Step 411: If the RA update is an RA update between the SGSNs, the HLR sends a Cancel Location (IMSSI, Cancellation Type) to the original SGSN, and the original SGSN releases the original Iu resource.

Step 412: If the RA update is a routing area update between the SGSNs, the HLR sends an Insert User Data (IMSI, Contract Data) message to the new SGSN.

Step 413: If the RA update is an RA update between the SGSNs, the HLR authenticates the new SGSN by sending an Update Location Ack (IMSI).

Step 414 to step 419 are the wireless side route update process.

The industry is currently proposing a variety of new mobile management technologies, the essence of which is user identity and location separation technology. There are solutions for the Subscriber Identifier & Locator Separation Network (SILSN) in the prior art, such as host-based implementations such as HIP. (Host Identity Protocol) technology, and router-based implementation such as Location Identity Separation Protocol (LISP) technology, each of which is supported by a variety of technologies, the identity of the end user in these schemes (represented as AID in the text) The data is not changed. The location identifier (represented as RID in the text) is allocated according to the location of the terminal to implement routing and forwarding of data packets.

FIG. 5 shows a network architecture of identity and location separation (SILSN). The network topology of the SILSN architecture is divided into an access network and a backbone network with no overlapping relationships in the topology relationship, and the access network is located at the edge of the backbone network. Responsible for accessing all terminals, and the backbone network is responsible for routing and forwarding data packets between terminals. In the network, the AID is used as the user identity of the terminal, and remains unchanged during the terminal movement. The RID is the location identifier assigned by the network to the terminal and is used in the backbone network. It should be noted that the identity and location identifiers may have different names in different SILSN architectures, but the essence is the same.

In the SILSN architecture, the terminal may be one or more of a mobile terminal, a fixed terminal, and a nomadic terminal, such as a mobile phone, a landline telephone, a computer, a server, and the like.

In the SILSN architecture, the access network is used to provide a Layer 2 (physical layer and link layer) access device for the terminal, and maintains a physical access link between the terminal and the ASR.

In the SILSN architecture, the main network elements of the backbone network include:

An Access Service Router (ASR) is an edge router of the backbone network. It is used to allocate RIDs to terminals, maintain AID-RID mapping information of terminals, and register AID-RID bindings to ILRs and query terminals. Implement routing and forwarding of data packets. The terminal must access the backbone network through the ASR. The RID assigned by the ASR to the terminal contains the address information of the ASR, or the ASR, and the RID is used as the destination address of the data packet, and the data packet is routed to the ASR.

A common router (CRM), the core router of the backbone network, is used to perform routing based on the RID in the data packet, and forwards the data packet with the RID as the destination address.

The Identity Location Register (ILR) is used to store and maintain the identity and location identifier mapping information of the home user terminal. The text is also written as AID-RID mapping information to process registration, deregistration and query of the terminal location. ; Optionally, the backbone network may further include:

An Internet Service Router (ISR) has interfaces with traditional IP networks, ASRs, and ILRs to implement interworking between identity and location separation networks and traditional IP networks.

It can be seen that in order to implement the normal forwarding of the packet, the ASR needs to allocate the RID to the terminal when the terminal accesses, and needs to register the AID of the user with the RID to update the binding of the terminal in the ILR. RID. In an example, the ASR maintains the peer information of the terminal for each terminal (also referred to as connection information between the terminal and the communication peer, or communication relationship information between the terminal and the communication peer), where the terminal includes the terminal AID and its communication pair. The correspondence information of the terminal AID may further include AID-RID mapping information of the terminal.

WCDMA systems can provide users with multiple types of business applications, but there are also many application problems, such as:

The GGSN is unchanged and there is a route bypass. The GGSN remains unchanged during the connection and use of the service. In this way, when the user moves, it is possible to move to a place far away from the GGSN and close to the service source, thereby causing the path to be bypassed, resulting in waste of transmission resources and prolonged delay.

Using a static public address as the IP address of the terminal has a great limitation on the mobility of the user. A static public IP address can only be removed from a fixed gateway due to route planning. Once you move to a remote location, you cannot access the external network nearby. Inevitably, routing is detoured, resulting in wasted transmission resources and prolonged delays.

Summary of the invention

The object of the present invention is to provide a mobility management method, a network element and a system for a direct tunnel to solve the problem of route bypass.

To solve the above technical problem, the present invention provides a mobility management method for a direct connection tunnel, which is applied in a scenario in which a terminal moves, the method includes:

The target radio network controller (RNC) sequentially transmits the downlink media plane tunnel address allocated by the target RNC to the terminal to the new GGSN through the new serving GPRS support node (SGSN) and the original gateway GPRS support node (GGSN); The new GGSN allocates an uplink media plane tunnel address to the terminal, and sequentially sends the uplink media plane tunnel address to the target RNC through the original GGSN and the new SGSN. The step of the target RNC sending the downlink media plane tunnel address to the new GGSN includes: the target RNC sending the first message to the new SGSN;

Receiving, by the new SGSN, the first message, and sending a second message to the original GGSN; the original GGSN receiving the second message, and sending a third message to the new GGSN; and

Receiving, by the new GGSN, the third message, where the first to third messages carry the downlink media plane tunnel address;

The step of the new GGSN transmitting the uplink media plane tunnel address to the target RNC by using the original GGSN, the new SGSN includes:

Sending, by the new GGSN, a fourth message to the original GGSN;

Receiving, by the original GGSN, the fourth message, and sending a fifth message to the new SGSN; and

The new SGSN receives the fifth message and sends a sixth message to the target RNC; the fourth to sixth messages all carry the uplink media plane tunnel address;

The first to sixth messages are existing or newly added messages. The first message is a relocation complete message, the second message is an update PDP context request, the third message is a PDP context push message, and the fourth message is a PDP context push response message, the fifth message To update the PDP context response, the sixth message is a notification message. The third message further carries information required to implement handover of the terminal, and the new GGSN allocates the uplink media plane tunnel address according to information required to implement handover of the terminal. The step of the original GGSN receiving the second message and sending the third message to the new GGSN includes: after receiving the second message, the original GGSN determines whether a handover is needed, and selects a new GGSN when determining the handover, and The selected new GGSN sends the third message. The scenarios in which the terminal moves include: Serving RNS Relocation scenario, Combined Hard Handover and SRNS Relocation scenario, and joint cell/URA and SRNS relocation ( Combined Cell I URA Update and SRNS Relocation ) scenario. The uplink media plane tunnel address and the downlink media plane tunnel address both include a media plane address and a media plane tunnel endpoint identifier (TEID) of the corresponding network element. The present invention also provides a Serving GPRS Support Node (SGSN), which includes an uplink message processing module and a downlink message processing module, where the SGSN is used as a new SGSN in a scenario in which the terminal moves, where

The uplink message processing module is configured to: receive a first message sent by a target radio network controller (RNC), and send a second message to the original gateway GPRS support node (GGSN), where both the first message and the second message are carried a downlink media plane tunnel address allocated by the target RNC to the terminal;

The downlink message processing module is configured to: receive a fifth message sent by the original GGSN, and send a sixth message to the target RNC, where the fifth message and the sixth message both carry the uplink media allocated by the new GGSN to the terminal. Face tunnel address. The first message is a relocation complete message, the second message is an update PDP context request, the fifth message is an update PDP context response, and the sixth message is a notification message. The scenario in which the terminal moves includes: Serving RNS Relocation scenario, Combined Hard Handover and SRNS Relocation scenario, combined cell/URA and SRNS relocation ( Combined Cell I URA Update and SRNS Relocation ) scenario. The uplink media plane tunnel address includes a media plane address and a media plane tunnel endpoint identifier (TEID) of the new GGSN, and the downlink media plane tunnel address includes a media plane address and a media plane TEID of the target RNC. The invention also provides a gateway GPRS support node (GGSN), comprising a receiving module and a ground An address allocation module and a sending module, where the GGSN is used as an original GGSN or a new GGSN in a scenario in which the terminal moves, where

The receiving module is configured to: when the GGSN is used as the original GGSN, receive the second message sent by the new SGSN and the fourth message sent by the new GGSN; and when the GGSN is used as the new GGSN, receive the original GGSN to send Third news;

The sending module is configured to: when the GGSN is used as the original GGSN, send a third message to the new GGSN, and send a fifth message to the new SGSN; and, when the GGSN is used as the new GGSN, send the first message to the original GGSN Four messages;

The address allocation module is configured to: allocate an uplink media plane tunnel address to the terminal when the GGSN is used as a new GGSN;

The second message and the third message both carry a downlink media plane tunnel address allocated by the target radio network controller (RNC) for the terminal, and the fourth message and the fifth message both carry the uplink media plane tunnel address. The second message is an update PDP context request, the third message is a PDP context push message, the fourth message is a PDP context push response message, and the fifth message is an update PDP context response. The third message further carries information required to implement handover of the terminal; the address allocation module is configured to allocate the uplink media plane tunnel address according to information required to implement handover of the terminal. The GGSN further includes a handover control module, where the handover control module is configured to: when the GGSN is used as the original GGSN, select a new GGSN when determining handover; the sending module is configured to be selected to the handover control module The new GGSN sends the third message. The uplink media plane tunnel address includes a media plane address and a media plane tunnel endpoint identifier (TEID) of the new GGSN, and the downlink media plane tunnel address includes a media plane address and a media plane TEID of the target RNC. The scene in which the terminal moves includes: service RNS relocation (Serving RNS)

Relocation ) scenario, joint hard handoff and SRNS relocation ( Combined Hard Handover and SRNS Relocation scenario, Combined Cell I URA Update and SRNS Relocation scenario.

The present invention also provides a mobility management system for a direct tunnel, including the Serving GPRS Support Node (SGSN) described above and the Gateway GPRS Support Node (GGSN) described above.

The mobility management method, the network element and the system of the direct tunnel of the invention realize the interaction of the media plane tunnel address of the information between the target RNC and the new GGSN according to a certain path, realize the mobility management of the direct tunnel, and avoid the route. Roundabout. BRIEF abstract

The drawings are intended to provide a further understanding of the invention, and are intended to be illustrative of the invention. In the drawing:

Figure 1 is an architectural diagram of a packet domain of an existing WCDMA system;

Figure 2a is a schematic diagram of the SRNS relocation and routing area update;

Figure 2b is a schematic diagram of SRNS relocation and routing area update;

3 is a flow chart of a prior SRNS relocation process;

4 is a flow chart of an existing routing area update;

Figure 5 is a schematic diagram of a SILSN network architecture;

6 is a schematic diagram of a WCDMA core network architecture with a SILSN architecture according to the present invention; FIG. 7 is a schematic flowchart of a method for SRNS relocation according to Embodiment 1 of the present invention; FIG. 8 is a schematic diagram of a hard handover for joint according to Embodiment 2 of the present invention; Schematic diagram of the method of relocating with SRNS;

9 is a schematic flowchart of a method for cell/URA joint update and SRNS relocation according to Embodiment 3 of the present invention;

10 is a schematic flowchart of a method for routing area update according to Embodiment 4 of the present invention;

11 is a schematic diagram of a mobility management method of a direct tunnel according to the present invention; 12 is a schematic structural diagram of a module of an SGSN according to the present invention;

Figure 13 is a block diagram showing the structure of a GGSN of the present invention;

Figure 14 is a schematic diagram of an implementation system for establishing a direct tunnel in accordance with the present invention.

Preferred embodiment of the invention

It should be noted that, since the TD-SCDMA core network architecture is consistent with the WCDMA core network architecture, the solution of the present invention is equally applicable in the TD-SCDMA core network, and the following WCDMA refers to WCDMA and TD-SCDMA.

As shown in FIG. 11, the mobility management method of the direct tunnel of the present invention includes:

Step 111: In the downlink address transmission step, the target radio network controller (RNC) sequentially sends the downlink media plane tunnel address allocated by the target RNC to the terminal to the new GGSN through the new serving GPRS support node (SGSN) and the original gateway GPRS support node (GGSN). ;

Specifically, the step of the target RNC transmitting the downlink media plane tunnel address to the new GGSN by using the new SGSN and the original GGSN, including:

The target RNC sends a first message to the new SGSN;

Receiving, by the new SGSN, the first message, and sending a second message to the original GGSN, the original GGSN receiving the second message, and sending a third message to the new GGSN; and the new GGSN receiving the first message The third message, the first to third messages all carrying the downlink media plane tunnel address. Step 112: The uplink address transmission step, the new GGSN allocates an uplink media plane tunnel address to the terminal, and sequentially passes the original GGSN, and the new SGSN sends the uplink media plane tunnel address to the target RNC. Specifically, the step of the new GGSN sending the uplink media plane tunnel address to the target RNC by using the original GGSN, the new SGSN, includes:

Sending, by the new GGSN, a fourth message to the original GGSN;

Receiving, by the original GGSN, the fourth message, and sending a fifth message to the new SGSN; The new SGSN receives the fifth message and sends the sixth message to the target RNC; the fourth to sixth messages all carry the uplink media plane tunnel address;

The foregoing first to sixth messages are existing or newly added messages.

Preferably, the third message further carries information required by the terminal to implement handover (such as: IMSI and/or AID of the MS, PDP context information (including a new SGSN, a new RNC address and TEID, DTI), MS And the information about the authentication information, the new GGSN allocates the uplink media plane tunnel address according to the information required to implement handover of the terminal.

In the present invention, preferably, after receiving the second message, the original GGSN determines whether switching is required, determines a new GGSN when switching, and sends the third message to the selected new GGSN.

The control plane tunnel address of the present invention includes a control plane address of the corresponding network element and a control plane tunnel endpoint identifier (TEID), and the media plane tunnel address includes a media plane address of the corresponding network element and a media plane tunnel endpoint identifier (TEID).

In order to facilitate the description of the present invention, the implementation of the technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Hereinafter, the present invention provides a mobility management method for a WCDMA core network that supports identity identification and location separation of a terminal in an WCDMA system using an identity location separation architecture to avoid routing bypass. Specifically, the above SILSN architecture is applied to a WCDMA system to implement unfixed anchor point switching. It should be noted that the SILSN architecture is only used to specifically illustrate embodiments of the present invention, and the flow of the present invention is also widely applicable to other identity location separation architectures.

According to the SILSN architecture and the working principle of the related art, it can be understood that when the terminal moves across the ASR, the new ASR on the side of the switch needs to allocate the RID to the terminal, encapsulate the packet sent by the MS, and decapsulate the packet sent to the MS. The original ASR that cuts out the side deletes the AID-RID mapping information of the terminal, and forwards the packet sent to the MS to the new ASR. At the same time, the new ASR or the original ASR needs to update the AID-RID mapping relationship of the MS in the ILR, and if the ASR and the ISR cache the AID-RID mapping locally, a mechanism is needed to notify the ASR and the ISR of the AID-RID mapping change.

Figure 6 shows the architecture of a WCDMA core network with a SILSN architecture: The GGSN is used as the function of the ASR. There is an interface SI with the ILR. The interface SI is used to query the ILR for the RID of the communication peer, and to register, change, and delete the AID-RID mapping relationship of the MS.

There is a signaling interface S2 and a data interface D2 between the GGSN and the ISR. The signaling interface S2 is used to notify the ISR of the AID-RID binding change when the GGSN is switched, and can also be used for the GGSN to notify the ISR to register and delete the AID-RID binding. set. The data interface D2 between the GGSN and the ISR is used by the GGSN to forward the data sent by the MS to the external network and the ISR forwards the data addressed to the MS to the GGSN.

The data interface D3 between the ISR and the external network is outside the scope of this patent.

The invention is not limited to the above architecture. Since the radio access network may use other architectures, in other architectures the target RNC may be other radio side network elements.

In the relocation preparation process based on the above WCDMA core network architecture, the GGSN no longer needs to be anchored, and the GGSN can be switched according to the handover of the SGSN to reduce route detour.

The following is a description of the improvements that have been made to the original system to achieve unfixed anchor switching, including related functions and processes.

In the text, when a network element is used as the original network element to process the terminal handover, the terminal is called a cut-out terminal. When a network element is used as the target side network element to process the terminal handover, the terminal is called the cut-in terminal. . In this paper, the network element that is connected to the communication peer of the terminal is simply referred to as the peer network element. In addition, when the function of a certain network element is expressed, the user terminal accessing the network element is called a terminal, and access The user terminal that the user terminal of the network element communicates is called a communication peer.

Embodiment 1

This embodiment is based on the WCDMA core network architecture described in FIG. 5, and describes the SRNS relocation process of the anchorless GGSN. There is no data loss in the handover process. After the handover is completed, the MS data packet is routed through the new GGSN to reduce route bypass.

As shown in FIG. 7, the process of the SRNS relocation process in this embodiment includes:

Steps 701-711: Steps 301-311 with the existing SRNS relocation process.

Step 712. The new SGSN signals the original SGSN by sending a Forward Relocation Complete message, and the SRNS relocation process is completed. Steps 712 and 713 can occur simultaneously. Step 712 and existing Process step 312 is the same.

Step 713a. The new SGSN sends an Update PDP Context Request message to the original GGSN (which carries the new SGSN address for the control plane, SGSN TEID (Tunnel Endpoint Identifier), new RNC address for the media plane, RNC TEID, negotiated QoS, DTI Etc.), step 313 with the existing SRNS relocation process.

Step A. After receiving the update PDP context request message, the original GGSN determines whether to switch the GGSN according to the new SGSN address carried in the message. Here, it is determined whether the GGSN needs to be switched according to the local policy or the external server to obtain information. If the handover GGSN is not the same as the existing subsequent procedure, this embodiment mainly describes the case of switching the GGSN.

If the original GGSN decides to switch the GGSN, it can obtain the address of the new GGSN by querying the local configuration or querying the external server according to the address of the new SGSN (ie, selecting a new GGSN); after obtaining the new GGSN address, the original GGSN sends the new GGSN to the new GGSN. The PDP context push message may include the IMSI and/or AID of the MS, the PDP context information (including the new SGSN, the address and TEID of the new RNC, DTI), and the authentication information of the MS. The purpose of the PDP context push message is to notify the new GGSN that the handover is required, and to send the MS-related PDP context, authentication information, etc. to the new GGSN, not limited to one message.

Step B. After receiving the PDP context push message sent by the original GGSN, the new GGSN allocates its own address as the RID of the MS, and the RID may be the address (ie, the second address information) of receiving the original GGSN message, or may be It is a new IP address of the newly allocated new GGSN. At the same time, the new GGSN allocates a GTP (GPRS Tunneling Protocol) tunnel (including the control plane and the media plane TEID) for the context of the received MS.

Step C1. The new GGSN sends a PDP context push message response to the original GGSN, and the response includes whether the new GGSN accepts the handover, the IMSI of the MS, the new GGSN address (which may be the same as the IP address of the original GGSN message received, or may be different), the new GGSN control plane And media plane TEID, MS AID, RID assigned to MS, temporary forwarding TEID (if MS needs GGSN to sort PDU packet with PDU sequence number), temporary PDU (protocol data unit) serial number (if MS needs GGSN to PDU) The data packet is sorted by PDU serial number) and other information.

Step C2. The original GGSN receives the PDP context push message response sent by the new GGSN. If the new GGSN does not accept the handover, the original GGSN may select another GGSN to repeat according to the policy and configuration. Step A; It is also possible to stop the handover attempt and complete the SRNS relocation process using the existing process. If the new GGSN accepts the handover, the original GGSN sends a PDP context switch message to the new GGSN, which may include information such as the IMSI and/or AID of the MS, the uplink and downlink PDU sequence number (if the MS needs the GGSN to sort the PDU data packet with the PDU sequence number).

If the MS needs the GGSN to sort the downlink PDU data packet with the PDU sequence number, the original GGSN starts to send the downlink data packet to the temporary forwarding TEID of the new GGSN, and uses the temporary PDU sequence number; after receiving the new GGSN, the downlink PDU sequence number is used for sorting. The media plane TEID of the new RNC is sent to the new RNC.

If the MS does not need the GGSN to sort the downlink PDU packets with the PDU sequence number, the original GGSN can forward to the new RNC using the media plane TEID of the new RNC. The GGSN does not need to allocate the temporary forwarding TEID and the temporary PDU sequence number in the case that the GGSN does not need to allocate the PDU sequence number of the downlink PDU data packet. The PDP context push message response in the step C1 does not need to carry the temporary forwarding TEID and the temporary PDU sequence. The original GGSN may not send the PDP context switch message in step C2 to the new GGSN, and the new GGSN sends the data plane TEID of the new RNC to the new RNC when receiving the data addressed to the MS.

The original GGSN can directly encapsulate the uplink data packet of the forwarding MS, or forward it to the new GGSN by using the media plane TEID of the new GGSN.

Step 713b: The original GGSN sends an update PDP context response to the new SGSN, which is consistent with the original flow step 313 update PDP context response message format, but the media plane TEID and the control plane TEID fill in the media plane TEID of the new GGSN received in step C1. And the control plane TEID; the GGSN address of the media plane and the GGSN address of the control plane fill in the GGSN address of the media plane of the new GGSN and the GGSN address of the control plane received in step C1. After this step, if the direct tunneling mode is not used, the new SGSN starts to send media plane data to the new GGSN instead of the original GGSN.

Step C3. If the direct SGSN is used, the new SGSN notifies the new RNC of the new GGSN's media plane address and TEID. After this step, the new RNC starts to send media plane data to the new GGSN instead of the original GGSN. Step D. The original GGSN may, according to the communication peer table of the MS, find all the peer GGSNs associated with the MS (except the new GGSN), send a message of the MS AID-RID mapping change, and receive the AID-RID. Map the response to the change message.

Step E. The original GGSN sends a message of AID-RID mapping change to the ILR, and receives the response of the ILR.

Step F: After receiving the response of the AID-RID mapping change message sent by all the peers (GGSN, ISR, ILR), the original GGSN may stop forwarding data to the new GGSN, and delete related information; meanwhile, send a stop forwarding message to the new GGSN. After receiving the message, the new GGSN may delete the allocated temporary forwarding TEID and the temporary PDU sequence number.

If the PDU sequence number is not required to be ordered, the stop forwarding message may not be sent to the new GGSN. Step F may also set a forwarding timer in the original GGSN, and send a stop forwarding message to the new GGSN after the timer expires.

The aging mechanism may also be used for the temporary forwarding TEID and the temporary PDU sequence number in the new GGSN, and the stop forwarding message may not be sent to the new GGSN.

Step 714. Upon receiving the forwarding relocation complete message, the original SGSN sends an Iu release command to the source RNC. When the RNC data forwarding timer expires, the source RNC releases the message with the Iu release completion message. Step 714 is consistent with existing process step 314.

Step 715. The MS initiates a routing area update procedure. Since the MS is in the PMM-CON ECTED mode, it is only a subset of the RA update process performed. Step 715 is consistent with existing process step 315.

Steps A through F of this embodiment are changes to the different existing processes of this patent, which are triggered by the PDP context update message of the new SGSN for seamless handover of the GGSN. Unlike the joint hard handoff and SRNS relocation process, the combined cell/URA and SRNS relocation procedures differ in the wireless side and therefore do not affect the description of the above embodiments. Steps A to F of this embodiment are also applicable to the joint hard handover and SRNS relocation process of the existing process and the joint cell/URA update and SRNS relocation process, which are triggered by the PDP context update message of the new SGSN, and realize seamless GGSN. Switch.

In addition, this embodiment may also have the following variants/alternatives:

For example, in step C2, the original GGSN may also send the saved AID-RID cache of the communication peer to the new GGSN.

For example, in step D, there are multiple ways to notify the correspondent peer: In the first mode, step D is not performed, only step E is performed, and the update of the mapping information of the AID-RID is notified by the ILR;

Method 2, using the broadcast notification method.

For example, the original GGSN may not forward the data sent to the MS to the new GGSN, and the forwarding time is longer than the time of all the GGSNs to cache the AID-RID mapping, ensuring that the original GGSN forwards all the peer GGSNs due to the AID-RID cache aging. , query the ILR to get the packet before the new AID-RID mapping.

When the original GGSN receives the data sent to the MS, it can notify the peer network element (GGSN, ISR) that the MS has switched to the new GGSN.

For example, step D and / or E can also be performed by the new GGSN, which can send the communication peer list of the cached MS to the new GGSN.

For example, if there are multiple PDP contexts between the original GGSN and the MS, the original GGSN performs step A-F when receiving the last PDP context change notification, and then passes multiple PDP contexts to the new GGSN.

Embodiment 2

This embodiment describes the joint hard handover and SRNS relocation procedure based on the WCDMA core network architecture described in FIG. 5. After the joint hard handover and the SRNS relocation procedure are completed, the MS is associated with the new SGSN and the new GGSN.

Step 801: The source RNC initiates joint hard handover and SRNS relocation of the PS domain. Join the existing hard handoff and SRNS relocation process.

Step 802: The source RNC sends a Relocation Required message to the original SGSN to initiate a relocation preparation process. The relocation request includes a relocation type, a cause, a source cell ID, a target cell ID, and a source. RNC to the target RNC transparent container and other content. Unlike step 702, the relocation type is set to "involving UE" here. Same as existing joint hard handover and SRNS relocation procedures.

Steps 803-807: Similar to steps 703-707, the same as the existing joint hard handover and SRNS relocation procedure. Step 808: The source RNC sends an RRC message to the MS to trigger the execution of the SRNS relocation. The terminal sends an RRC message to the target RNC. Same as existing joint hard handover and SRNS relocation procedures.

Step 809: The source RNC sends a Forward RNC Context (Forward SRNC Context) message to the target RNC through the original SGSN and the new SGSN. Same as existing joint hard handoff and SRNS relocation process.

Step 810: When the target RNC finds that the terminal is in its service area, it sends a Relocation Detect message to the new SGSN. Same as existing joint hard handover and SRNS relocation procedures.

Step 811: When the target RNC receives the RRC message sent by the terminal (step 808), it sends a Relocation Complete message to the new SGSN. Same as existing joint hard handover and SRNS relocation procedures.

Step 812: The new SGSN sends a Forward Relocation Complete message to notify the original SGSN that the SRNS relocation process has been completed. Steps 812 and 813 can occur simultaneously. Join the existing joint hardswitch and SRNS relocation process.

Step 813a: The new SGSN sends an Update PDP Context Request message to the original GGSN (which carries the new SGSN address for the control plane, SGSN TEID (Tunnel Endpoint Identifier), new RNC address for the media plane, RNC TEID, negotiated QoS, DTI Etc.), with existing joint hard handoff and SRNS relocation procedures.

Step A: Same as the first step of the embodiment.

Step B: Same as step 8 of the first embodiment.

Step C1: The same procedure as in the first step Cl.

Step C2: Same as step C2 of the first embodiment.

Step 813b: Same as Embodiment 1 step 713b.

Step C3: Step C3 is the same as Embodiment 1.

Step D: Same as step 0 of the first embodiment.

Step E: The same as step 1 of the embodiment.

Step F: Same as step F of the first embodiment.

Step 814: Receive a forwarding relocation complete message, and the original SGSN sends an Iu release command to the source. RNC. When the RNC data forwarding timer expires, the source RNC releases the message response with the Iu release. Same as existing joint hard handover and SRNS relocation procedures.

Step 815: The location update process, with the existing joint hard handover and SRNS relocation process. Furthermore, this embodiment can also have the same variations as the first embodiment.

Embodiment 3

This embodiment describes the joint cell/URA and SRNS relocation procedure based on the WCDMA core network architecture described in FIG. 5. After the joint cell/URA and SRNS relocation procedures are completed, the MS associates with the new SGSN and the new GGSN.

Step 901: The terminal sends a Cell Update message to the source RNC, or sends the message

URA Update or Cell Update or GRA Update. The cell/URA and SRNS relocation procedures associated with the existing.

Steps 902-909: Similar to the first step 702-709 of the first embodiment. The cell/URA and SRNS relocation procedures associated with the existing.

Step 910: The target RNC sends a Cell Update Confirm message to the terminal, or sends a URA Update Confirm or a Cell Update Confirm or a GRA Update Confirm. The terminal sends a RAN Mobility Information Confirm message to the target RNC. . The existing cell/URA and SRNS relocation procedures.

Step 911: When the target RNC receives the RAN mobility information confirmation message sent by the terminal (step 910), it sends a Relocation Complete message to the new SGSN. The cell/URA and SRNS relocation procedures associated with the existing.

Step 912: The new SGSN sends a Forward Relocation Complete message to notify the original SGSN that the SRNS relocation process has been completed. Step 912 and step 913 can occur simultaneously. The existing cell/URA and SRNS relocation procedures.

Step 913a: The new SGSN sends an Update PDP Context Request message to the original GGSN (which carries the new SGSN address for the control plane, SGSN TEID (Tunnel Endpoint Identifier), new RNC address for the media plane, RNC TEID, negotiated QoS, DTI Etc.), with the existing joint cell/URA and SRNS relocation procedures. Step A: Same as the first step of the embodiment.

Step B: Same as step 8 of the first embodiment.

Step C1: The same procedure as in the first step Cl.

Step C2: Same as step C2 of the first embodiment.

Step 913b: Same as step 713b of the first embodiment.

Step C3: Same as step C3 of the first embodiment.

Step D: Same as step 0 of the first embodiment.

Step E: The same as step 1 of the embodiment.

Step F: Same as step F of the first embodiment.

Step 914: Receive a forwarding relocation complete message, and the original SGSN sends an Iu release command to the source.

RNC. When the RNC data forwarding timer expires, the source RNC releases the message with the Iu release completion message. There is a joint cell/URA and SRNS relocation process.

Step 915: The location update process, with the existing combined cell/URA and SRNS relocation procedures. Furthermore, this embodiment can also have the same variations as the first embodiment.

Embodiment 4

This embodiment describes the routing area update process based on the WCDMA core network architecture described in FIG. 5. After the routing area update is completed, the MS associates with the new SGSN and the new GGSN.

Steps 1001-1008: Same as the existing routing area update procedure steps 401-408.

Step 1009a: The new SGSN sends an Update PDP Context Request message to the original GGSN (which carries the new SGSN address, SGSN TEID (Tunnel Endpoint Identifier), a new RNC address for the media plane, RNC TEID, negotiated QoS, etc.), with the existing route. Zone update step 409.

Step A: After receiving the update PDP context request message, the original GGSN determines whether to switch the GGSN according to the new SGSN address carried in the message. Here, it is determined whether the GGSN needs to be switched according to the local policy or the external server to obtain information. If the handover GGSN is not the same as the existing subsequent procedure, this embodiment mainly describes the case of switching the GGSN. If the original GGSN decides to switch the GGSN, it can query the local configuration according to the address of the new SGSN, and query the external server to obtain the address of the new GGSN. After obtaining the new GGSN address, the original GGSN sends a PDP context push message to the new GGSN, and the PDP context pushes. The message may include information such as the IMSI and/or AID of the MS, the PDP context information (including the address and TEID of the new SGSN), and the authentication information of the MS. The purpose of the PDP context push message here is to notify the new GGSN MS that the handover is required, and to send the MS-related PDP context, authentication information, etc. to the new GGSN, not limited to one message.

Step B: After receiving the PDP context push message sent by the original GGSN, the new GGSN allocates its own address as the RID of the MS, and the RID may be the address (ie, the second address information) of receiving the original GGSN message, or may be It is a new IP address of the newly allocated new GGSN. At the same time, the new GGSN allocates a GTP (GPRS Tunneling Protocol) tunnel (including the control plane and the media plane TEID) for the context of the received MS.

Step C1: The new GGSN sends a PDP context push message response to the original GGSN, and the response includes whether the new GGSN accepts the handover, the IMSI of the MS, and the new GGSN address (which may be the same as the IP address of the original GGSN message received, or may be different), the new GGSN control plane. And the media face TEID, the MS's AID, and the RID assigned to the MS.

Step C2: The original GGSN receives the PDP context push message response sent by the new GGSN. If the new GGSN does not accept the handover, the original GGSN may select another GGSN according to the policy and configuration to repeat step A; or may not perform the handover attempt, using the existing The process completes the service SRNS relocation process.

The original GGSN can forward to the new SGSN using the media plane TEID of the new SGSN. The original GGSN can directly encapsulate the uplink data packet of the forwarding MS, or forward the new GGSN to the new GGSN by using the media plane TEID of the new GGSN.

Step 713b: The original GGSN sends an update PDP context response to the new SGSN, which is consistent with the original flow step 313 update PDP context response message format, but the media plane TEID and the control plane TEID fill in the media plane TEID of the new GGSN received in step C1. And the control plane TEID; the GGSN address of the media plane and the GGSN address of the control plane fill in the GGSN address of the media plane of the new GGSN received in step C1 and the GGSN address used for the control plane. After this step, the new SGSN starts sending data to the new GGSN instead of to the original GGSN. Step D.: The original GGSN may, according to the communication peer table of the MS, find all the associated GGSNs (except the new GGSN) associated with the MS, send a message of the MS AID-RID mapping change, and receive a response of the AID-RID mapping change message.

Step E.: The original GGSN sends a message of AID-RID mapping change to the ILR, and receives the response of the ILR.

Steps 1010-1019: Same as the existing routing area update process steps 410-419.

Furthermore, this embodiment can also have the same variations as the first embodiment.

Since the TD-SCDMA core network and the WCDMA core network use the same architecture, the technical solution of the present invention can also be applied to the core network of TD-SCDMA and similar architectures.

In order to implement the foregoing method, the present invention further provides a Serving GPRS Support Node (SGSN), which is particularly relevant to the present invention. As shown in FIG. 12, the SGSN includes an uplink message processing module and a downlink message processing module, which occur at the terminal. In the mobile scenario, when the SGSN is used as a new SGSN: the uplink message processing module is configured to: receive a first message sent by a target radio network controller (RNC), and send a second message to an original gateway GPRS support node (GGSN), The first message and the second message both carry the downlink media plane tunnel address allocated by the target RNC for the terminal;

The downlink message processing module is configured to: receive a fifth message sent by the original GGSN, and send a sixth message to the target RNC, where the fifth message and the sixth message both carry the new GGSN for the terminal Upstream media plane tunnel address.

Further, the first message is a relocation complete message, the second message is an update PDP context request, the fifth message is an update PDP context response, and the sixth message is a notification message.

The present invention also provides a gateway GPRS support node (GGSN), which is particularly relevant to the present invention. As shown in FIG. 13, the GGSN includes a receiving module, an address assigning module, and a sending module, where the terminal moves:

When the GGSN is used as the original GGSN, the receiving module is configured to: receive the second message sent by the new SGSN, and receive the fourth message sent by the new GGSN; The block is configured to: send a third message to the new GGSN, and send a fifth message to the new SGSN; the second message and the third message both carry the downlink media plane allocated by the target radio network controller (RNC) to the terminal. a tunnel address, where the fourth media message and the fifth message carry the uplink media plane tunnel address;

When the GGSN is used as the new GGSN, the receiving module is further configured to receive the third message sent by the original GGSN; the sending module is further configured to send the fourth message to the original GGSN; The terminal is assigned the uplink media plane tunnel address.

Further, the second message is an update PDP context request, the third message is a PDP context push message, the fourth message is a PDP context push response message, and the fifth message is an update PDP context response.

Preferably, the third message further carries information required for the handover of the terminal, and the address allocation module of the new GGSN allocates the uplink media plane tunnel address according to the information required to implement handover of the terminal.

Further, the GGSN further includes a handover control module, where the handover control module is configured to: when the GGSN is used as the original GGSN in the scenario in which the terminal moves, select the new GGSN when determining handover; The third message is sent to the new GGSN selected to be selected by the handover control module.

In the present invention, the uplink media plane tunnel address includes a media plane address and a media plane TEID of the new GGSN, and the downlink media plane tunnel address includes a media plane address and a media plane TEID of the target RNC.

The scenario in which the terminal moves includes: Serving RNS Relocation scenario, Combined Hard Handover and SRNS Relocation scenario, combined cell/URA and SRNS relocation ( Combined Cell I URA Update and SRNS Relocation ) scenario.

In addition, the present invention also provides an implementation system for establishing a direct tunnel, such as the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN), as shown in FIG.

According to the above description, compared with the prior art, the present invention can support the identity identification and location separation of the terminal, avoid routing detours, and can be based on the existing relocation process as much as possible without affecting the existing heavy weight. The consistency of the positioning process has good feasibility.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention. The present invention may be embodied in various other embodiments without departing from the spirit and scope of the invention. Various changes and modifications may be made to the invention, and such changes and modifications are intended to be included within the scope of the appended claims.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

Industrial applicability

Compared with the prior art, the present invention implements the interaction of the media plane tunnel address of the information between the target RNC and the new GGSN according to a certain path, realizes the mobility management of the direct tunnel, and avoids the route bypass.

Claims

Claim

A mobility management method for a direct tunnel, which is characterized in that, in a scenario in which a terminal moves, the method includes:

The target radio network controller (RNC) sequentially transmits the downlink media plane tunnel address allocated by the target RNC to the terminal to the new GGSN through the new serving GPRS support node (SGSN) and the original gateway GPRS support node (GGSN);

The new GGSN allocates an uplink media plane tunnel address to the terminal, and sequentially passes the original GGSN, and the new SGSN sends the uplink media plane tunnel address to the target RNC.

2. The method of claim 1, wherein the step of the target RNC transmitting the downlink media tunnel address to the new GGSN comprises: the target RNC transmitting the first message to the new SGSN;

Sending, by the new GGSN, a fourth message to the original GGSN;

The first to sixth messages are existing or newly added messages.

3. The method according to claim 2, wherein the first message is a relocation complete message, The second message is an update packet data protocol (PDP) context request, the third message is a PDP context push message, the fourth message is a PDP context push response message, and the fifth message is an update PDP context response, The sixth message is a notification message.

The method of claim 2, wherein the third message further carries information required to implement handover of the terminal, and the new GGSN allocates the uplink media plane according to information required to implement handover of the terminal. Tunnel address.

The method of claim 2, wherein the step of the original GGSN receiving the second message and sending the third message to the new GGSN comprises: after receiving the second message, the original GGSN determines whether A handover is required, a new GGSN is selected when the handover is decided, and the third message is sent to the selected new GGSN.

The method according to any one of claims 1 to 5, wherein the scenario in which the terminal moves includes: Serving RNS Relocation scenario, joint hard handover, and SRNS relocation ( Combined Hard Handover) And SRNS Relocation ) scenario, and the Combined Cell / URA Update and SRNS Relocation scenario.

The method according to any one of claims 1 to 5, wherein the uplink media plane tunnel address and the downlink media plane tunnel address both include a media plane address and a media plane tunnel endpoint identifier (TEID) of the corresponding network element. .

A service GPRS support node (SGSN), comprising an uplink message processing module and a downlink message processing module, wherein the SGSN is used as a new SGSN in a scenario in which the terminal moves, wherein the uplink message processing module is configured to: receive a first message sent by the target radio network controller (RNC), and a second message sent to the original gateway GPRS support node (GGSN), where the first message and the second message carry the downlink media allocated by the target RNC for the terminal Face tunnel address;

The downlink message processing module is configured to: receive a fifth message sent by the original GGSN, and send a sixth message to the target RNC, where the fifth message and the sixth message both carry a new GGSN The uplink media plane tunnel address assigned by the terminal.

The SGSN according to claim 8, wherein the first message is a relocation complete message, the second message is an update packet data protocol (PDP) context request, and the fifth message is an update PDP context response. The sixth message is a notification message.

The SGSN according to claim 8, wherein the scenario in which the terminal moves includes: a Serving RNS Relocation scenario, a Combined Hard Handover and SRNS Relocation scenario, Combined Cell I URA Update and SRNS Relocation scenario.

The SGSN according to claim 8, wherein the uplink media plane tunnel address includes a media plane address and a media plane tunnel endpoint identifier (TEID) of the new GGSN, and the downlink media plane tunnel address includes a media plane of the target RNC. Address and media face TEID.

12. A gateway GPRS support node (GGSN), comprising: a receiving module, an address allocation module, and a sending module, where the GGSN is used as an original GGSN or a new GGSN in a scenario in which the terminal moves, where

The second message and the third message both carry a downlink media plane tunnel address allocated by the target radio network controller (RNC) for the terminal, and the fourth message and the fifth message both carry the uplink media plane tunnel address.

13. The GGSN according to claim 12, wherein the second message is update packet data A protocol (PDP) context request, the third message is a PDP context push message, the fourth message is a PDP context push response message, and the fifth message is an update PDP context response.

The GGSN according to claim 12, wherein the third message further carries information required to implement handover of the terminal; the address allocation module is configured to switch information required according to implementation of the terminal The upstream media plane tunnel address.

The GGSN according to claim 12, further comprising a handover control module, wherein the handover control module is configured to: when the GGSN is used as the original GGSN, select a new GGSN when determining handover; the sending module is configured to Sending the third message to a new GGSN selected by the handover control module.

The GGSN according to any one of claims 12 to 15, wherein the uplink media plane tunnel address comprises a media plane address of a new GGSN and a media plane tunnel endpoint identifier (TEID), and the downlink media plane tunnel address Includes the media face address and media face TEID of the target RNC.

The GGSN according to any one of claims 12 to 15, wherein the scenario in which the terminal moves includes: Serving RNS Relocation scenario, joint hard handover, and SRNS relocation ( Combined Hard Handover) And SRNS Relocation ) scenario, Combined Cell / URA Update and SRNS Relocation scenario.

A mobility management system for a direct tunnel, comprising the Serving GPRS Support Node (SGSN) according to any one of claims 8 to 11 and the gateway according to any one of claims 12 to 17. GPRS Support Node (GGSN).