WO2011134171A1 - 多代移动通信网络中移动性管理流程的处理方法及系统 - Google Patents

多代移动通信网络中移动性管理流程的处理方法及系统 Download PDF

Info

Publication number
WO2011134171A1
WO2011134171A1 PCT/CN2010/072382 CN2010072382W WO2011134171A1 WO 2011134171 A1 WO2011134171 A1 WO 2011134171A1 CN 2010072382 W CN2010072382 W CN 2010072382W WO 2011134171 A1 WO2011134171 A1 WO 2011134171A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility management
network element
management network
old
sgsn
Prior art date
Application number
PCT/CN2010/072382
Other languages
English (en)
French (fr)
Inventor
戚彩霞
王珊珊
陈海永
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2010/072382 priority Critical patent/WO2011134171A1/zh
Priority to CN201080001607.1A priority patent/CN102318402B/zh
Publication of WO2011134171A1 publication Critical patent/WO2011134171A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for processing a mobility management flow in a multi-generation mobile communication network.
  • the logical architecture of the current next-generation mobile communication network is shown in FIG. 1.
  • the user terminal accesses through a local wireless access network
  • the mobile management network element is responsible for location management, connection management, and security of the user terminal.
  • Authentication, gateway selection and other functions the service gateway is the local access gateway of the user terminal, responsible for access technology related connection management and data forwarding, and the data gateway is the gateway for the user terminal to access the external data network.
  • the logical architecture of the next-generation mobile communication network shown in Figure 1 corresponds to the actual network, which may be an evolved packet system (Evolved). Packet System (EPS) network.
  • Evolved evolved packet system
  • EPS Packet System
  • the mobility management network element can be a mobility management entity (Mobility). Management Entity, MME) or GPRS Service Support Node (S4) SGSN), the service gateway may be a Serving Gateway (S-GW), and the data gateway may be a packet data network gateway (Packet Data Network) Gateway, PDN-GW).
  • MME mobility management entity
  • S4 GPRS Service Support Node
  • S-GW Serving Gateway
  • PDN-GW packet data network gateway
  • the current second-generation, third-generation (2G/3G) mobile communication network has a logical architecture as shown in Figure 2.
  • the user terminal passes through the local The radio access network accesses the mobile management network element to aggregate the functions of the mobility management network element and the service gateway in the next generation mobile communication network.
  • the second generation, third generation mobile communication network corresponds to the actual network, and may be a GPRS network or a UMTS network.
  • the mobility management network element may be a GPRS service supporting node (Gn/Gp). Serving GPRS Support Node, Gn/Gp SGSN), the data gateway can be a GPRS gateway support node (Gateway GPRS Support) Node, GGSN).
  • the new mobile management network element of the service user terminal in the currently attached mobile communication network and the service user terminal in the previously attached mobile communication network is not the same node, and the new mobility management network element requests the identity of the user terminal from the old mobility management network element, and obtains the context of the user terminal;
  • the user terminal initiates tracking area update in the network (Tracking Area) Update, TAU), or routing area update (Routeing Area) Update, RAU) process, if the mobile management network element of the service user terminal changes, the new mobility management network element requests the old mobile management network element of the previous service user terminal to acquire the context of the user terminal.
  • Track Area Track Area
  • RAU routing Area update
  • the interface between different mobile management network elements uses GTP (GPRS Tunnelling). Protocol, GPRS Tunneling Protocol, but different versions of GTP are used for different inter-entity communication.
  • the communication between the core network elements of the EPS network adopts the GTPv2 protocol (where MME (Mobility) S10 interface between the Management Entity, the mobility management entity and the MME, S16 interface between the S4 SGSN (GPRS service support node) and the S4 SGSN, S4 The S3 interface is adopted between the SGSN and the MME, and these interfaces all adopt the GTPv2 protocol.
  • MME Mobility Management Entity
  • S4 SGSN GPRS service support node
  • S4 The S3 interface is adopted between the SGSN and the MME, and these interfaces all adopt the GTPv2 protocol.
  • the mobile management network element of the EPS network and the mobile management network element of the 2G/3G network are used for communication.
  • GTPv1 protocol MME and Gn/Gp Gn interface, S4 SGSN and Gn/Gp between SGSNs
  • the SGSN also uses the Gn interface, and the Gn interface uses the GTPv1 protocol.
  • the communication between the mobile management NEs of the 2G/3G network also uses the GTPv1 protocol (Gn/Gp).
  • the Gn interface is also used between the SGSNs, which is the GTPv1 protocol.
  • the prior art has at least the following problem: if the new mobility management network element is the MME node of the EPS network, S4 Any one of the nodes of the SGSN node, the Gn/Gp SGSN, and the S4 SGSN, and the new mobility management network element is Gn/Gp SGSN and S4.
  • the SGSN is a node
  • the node serving the user terminal is S4 SGSN
  • the old mobility management network element is Gn/Gp SGSN and S4.
  • the node of the SGSN is unified, and the new mobility management network element does not know the node type of the old mobility management network element.
  • the new mobility management network element is attached, or the user terminal initiates a TAU or RAU.
  • the new mobility management network element needs to request the identity of the user terminal from the old mobility management network element, or obtain the context of the user terminal.
  • the new mobile management network element cannot know that the node of the old mobile management network element service user terminal is Gn/Gp.
  • the new mobility management network element cannot know whether the GTPv2 protocol or the GTPv1 protocol should be used to communicate with the old mobility management network element.
  • the new mobility management network element sends a GTPv2 request message to the old mobility management network element (Gn/Gp)
  • Gn/Gp the node of the old mobile management network element serving the user terminal
  • the version of the protocol supported by the SGSN is GTPv1.
  • the version of the protocol that receives the GTPv2 request message is inconsistent.
  • the request message of the GTPv2 cannot be directly processed. This will result in several messages being sent before the correct interaction can be established. Signaling messages, wasting network resources.
  • the object of the embodiments of the present invention is to provide a processing method and system for a mobility management process in a multi-generation mobile communication network, and to solve the mobility management process of the user terminal, when the nodes of the new and old mobile management network element service user terminals support If the protocol version is inconsistent and the new mobility management network element does not know the node type of the old mobility management network element service user terminal, the new mobility management network element cannot correctly interact with the old mobility management network element, resulting in an increase in signaling overhead in the network. The consumption of network resources has made it impossible for the new mobile management network element to successfully complete the mobility management process.
  • the embodiment of the invention provides a processing method for a mobility management flow in a multi-generation mobile communication network, where the node of the new mobility management network element is Gn/Gp Any one of the node, MME, and S4 SGSN in which the SGSN and the S4 SGSN are combined, when the new mobility management network element is Gn/Gp SGSN and S4 When the SGSN is unified, the node serving the user terminal is S4 SGSN; the old mobility management network element is Gn/Gp SGSN and S4. A node in which the SGSN is unified, the node of the old mobility management network element serving the user terminal is a Gn/Gp SGSN;
  • the response message is sent to the new mobility management network element, and the protocol version of the response message is The version of the request message sent by the new mobility management network element is consistent;
  • the new mobility management network element completes the mobility management process by using the response message.
  • the embodiment of the present invention further provides a processing system for a mobility management flow in a multi-generation mobile communication network, which is used in a multi-generation mobile communication network composed of a next-generation mobile communication network and a second-generation and third-generation mobile communication network, including :
  • the old side communication processing device is connected to the old mobile management network element in the second generation and third generation mobile communication networks;
  • the new mobility management network element is configured to send a request message requesting user information to the old mobility management network element after receiving an attach request message or a routing area update request message or a tracking area update request message sent by the user terminal; Performing a mobility management process according to the response message replied by the old mobility management network element;
  • the old mobility management network element is configured to reply a response message to the old mobility management network element according to the request information.
  • the old side communication processing device is configured to determine, by the old mobility management network element, the request message sent by the new mobility management network element, when the protocol version of the request message and the old mobility When the protocol version supported by the node of the management network element service user terminal is inconsistent, the response message that is consistent with the protocol version of the request message is used as a response message that the old mobility management network element replies to the new mobility management network element.
  • the new mobility management network element in the mobility management process, when the new mobility management network element cannot learn the node type of the mobility management network element of the service user terminal in the old-side network, the new mobile management network element can still correctly interact with the old mobility management network element.
  • the user information of the user terminal is obtained, so that the new mobility management network element can complete the mobility management process of the user terminal, thereby saving network signaling overhead and saving network resources.
  • FIG. 1 is a logical architecture diagram of a next-generation mobile communication network provided by the prior art
  • FIG. 2 is a logical architecture diagram of a second generation and third generation mobile communication network provided by the prior art
  • FIG. 3 is a schematic flowchart of a processing method according to Embodiment 1 of the present invention.
  • FIG. 4 is a schematic flowchart of a processing method according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic flowchart of a processing method according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic flowchart of a processing method according to Embodiment 4 of the present invention.
  • FIG. 7 is a structural block diagram of a processing system according to Embodiment 5 of the present invention.
  • FIG. 8 is a structural block diagram of an old side communication processing apparatus of a processing system according to Embodiment 5 of the present invention.
  • FIG. 9 is a structural block diagram of another old-side communication processing apparatus of a processing system according to Embodiment 5 of the present invention.
  • FIG. 10 is a structural block diagram of an old side communication processing apparatus of a processing system according to Embodiment 6 of the present invention.
  • FIG. 11 is a structural block diagram of another processing system according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a new side communication processing apparatus of a processing system according to an embodiment of the present invention.
  • the processing method and system for the mobility management flow in the multi-generation mobile communication network are used for the user terminal to communicate in the multi-generation mobile communication network, and the node of the new mobility management network element is Gn/Gp Any one of the node, MME, and S4 SGSN in which the SGSN and the S4 SGSN are combined, and when the new mobility management network element is Gn/Gp SGSN and S4 When the SGSN is unified, the node serving the user terminal is S4 SGSN, and the old mobility management network element is Gn/Gp SGSN and S4. The node of the SGSN is unified, and the node of the old mobile management network element serving user terminal is Gn/Gp.
  • the new mobility management network element when the new mobility management network element performs the mobility management process, the new mobility management network element can still correctly interact with the old mobility management network element when the new mobility management network element does not know the node type of the old mobility management network element service user terminal. Obtaining the user identity and/or context information of the user terminal, completing the mobility management process, so that the user terminal can switch to the new mobility management network element to receive the service, thereby saving the signaling overhead of the network in the attaching process and saving network resources.
  • the embodiment provides a processing method for a mobility management flow in a multi-generation mobile communication network, where the user terminal communicates in a multi-generation mobile communication network.
  • the node of the new mobility management network element is Gn/Gp Any one of the node, MME, and S4 SGSN in which the SGSN and the S4 SGSN are combined, and when the new mobility management network element is Gn/Gp SGSN and S4
  • the node serving the user terminal is S4 SGSN
  • the old mobility management network element is Gn/Gp SGSN and S4.
  • the node of the SGSN is unified, and the node of the old mobile management network element serving user terminal is Gn/Gp.
  • the new mobility management network element is guaranteed to complete the mobility management process for the user terminal (including the attach process or the routing area update or the tracking area update process).
  • the method is described below when the mobility management process is an attach process, and the method includes the following steps:
  • the old mobility management network element receives the new mobility management network element (MME or S4 SGSN node, and when it is the S4 SGSN node, it may be Gn/Gp An identity request message of the GTPv2 sent by the node of the SGSN and the S4 SGSN and the node of the serving user terminal is the S4 SGSN);
  • the old mobile management network element is Gn/Gp SGSN and S4
  • the node of the SGSN is one
  • the node of the old mobile management network element serving user terminal is Gn/Gp SGSN
  • Gn/Gp The SGSN is unable to process the identity request message of the GTPv2
  • the old mobility management network element replies to the new mobile management network element with a response message of the GTPv2 that is consistent with the identity request message protocol version, and the response message of the GTPv2 carries the user identity identifier as the user information
  • New mobile management network element MME or S4
  • the SGSN node After receiving the response message of the GTPv2, the SGSN node can complete the subsequent attach process according to the user information in the response message, so that the user terminal attaches to the new mobility management network element to receive the service.
  • the old mobility management network element converts the mobility management context of the GTPv1 into the mobility management context of the GTPv2, and carries the converted mobility management context and the user identity of the GTPv2 in the response message of the GTPv2 that is replied as User information; or the old mobility management network element carries the mobility management context of the GTPv1 in the container cell of the GTPv2, and carries the container cell and the user identity of the GTPv2 in the response message of the reply GTPv2 as the user information.
  • FIG. 3 shows an attach procedure in an EPS network.
  • the old side access network is a 3GPP access of UTRAN/GERAN, and the corresponding wireless access node is a wireless network control.
  • Radio Network Controller, RNC) / Base Station Subsystem (BSS) old mobile management network elements are Gn/Gp SGSN and S4
  • the SGSN is a unified node;
  • the new side access network is a 3GPP access of GERAN/UTRAN/E-UTRAN, which respectively corresponds to a BSS/RNC/Evolved Node B (Evolved Node) B, eNodeB),
  • the node of the new mobility management network element may be S4 SGSN or MME (when it is an S4 SGSN node, it may be Gn/Gp SGSN and S4)
  • the SGSN is a unified node, and the node serving the user terminal is S4 SGSN), the service gateway can be SGW, the data gateway can be
  • the attaching process in FIG. 3 specifically includes the following steps:
  • Step 1 The user terminal initiates an attach procedure, and sends an attach request message, and the message is sent to the new side S4 through the new side access network.
  • SGSN or MME for the new mobility management network element
  • Step 2 New Side S4
  • the SGSN or the MME finds the old mobility management network element of the service user terminal in the access network on the old side according to the location information of the old mobility management network element in the received attach request message, and the new side S4
  • the SGSN or MME sends a GTPv2 identity request because it does not know whether the node of the old mobility management network element service user terminal is a Gn/Gp SGSN or an S4 SGSN (Identification) Request) message to the old mobile management network element;
  • Step 3 The old mobile management network element is Gn/Gp SGSN and S4
  • the node where the SGSN is unified, when the user is on the old side, the old mobile management network element serves the user terminal is Gn/Gp SGSN; after receiving the identity request message of the GTPv2, the old mobility management network element of the unified node discovers that the service user terminal is Gn/Gp according to the temporary identifier of the user in the request message of the GTPv2.
  • old mobile management network element confirms Gn/Gp
  • the SGSN cannot process the identity request message of the GTPv2 sent by the new mobility management network element, and the old mobility management network element replies with the identity response message of the GTPv2 that is consistent with the identity request message protocol version (Identification) Response) to the new side of the S4 SGSN or MME, the message carries the user identity (International Mobile Subscriber Identity,IMSI);
  • IMSI International Mobile Subscriber Identity
  • the old mobile management network element will be the mobility management context of GTPv1 (Mobility Management). Context, MM Context) is converted into the mobility management context of GTPv2, and the translated mobility management context of GTPv2 is carried along with the user identity in the identity response message of GTPv2 replied to the new mobility management network element; or the old mobility management network element
  • the mobility management context of the GTPv1 is carried in the container cell of the GTPv2, and the container cell and the user identity of the GTPv2 are carried in the identity response message of the GTPv2 replied to the new mobility management network element.
  • Step 4 Authentication/security process, which is an optional process
  • Steps 5 and 6 The new side S4 SGSN or MME registers the location with the HSS, and obtains the subscription data of the user.
  • the old side Gn/Gp SGSN cancels location registration;
  • Step 7 The session establishment process of the MME, the SGW, and the PGW establishes a default bearer, and the step is performed only when the E-UTRAN is accessed;
  • Steps 8, 9 Attachment acceptance and completion
  • Step 10 The bearer update process, the SGW updates the downlink user plane tunnel information, and the step is only performed when the E-UTRAN accesses.
  • the user terminal initiates an attach procedure to the new mobility management network element, and the new side S4
  • the SGSN or MME node new mobility management network element
  • the old side Gn/Gp new mobility management network element
  • the SGSN node confirms that it cannot be processed, and then goes to the new side S4.
  • the SGSN or the MME node replies with the GTPv2 response message that is consistent with the identity request message protocol version, and carries the user identity identifier in the response message of the replied GTPv2, or carries the user identity identifier and the GTPv2 converted from the mobility management context of the GTPv1.
  • the SGSN or the MME node can receive the identity of the user terminal and the mobility management context, thereby successfully completing the attach process, avoiding the signaling overhead of the network in the attach process, and avoiding wasting network resources.
  • the embodiment provides a processing method for a mobility management flow in a multi-generation mobile communication network, and the method is applicable to a user terminal in a multi-generation mobile communication network to initiate a routing area update or a tracking area update when switching to a new mobile management network to receive a service.
  • the process specifically includes the following steps:
  • the old mobility management network element receives the new mobility management network element (S4 SGSN or MME node, which is the S4 SGSN node, and may be Gn/Gp a GTPv2 context request message sent by the SGSN and the S4 SGSN in a node, and the node serving the user terminal is the S4 SGSN);
  • S4 SGSN or MME node which is the S4 SGSN node, and may be Gn/Gp a GTPv2 context request message sent by the SGSN and the S4 SGSN in a node, and the node serving the user terminal is the S4 SGSN
  • the old mobile management network element is Gn/Gp SGSN and S4
  • the node of the SGSN is one
  • the node of the old mobile management network element serving user terminal is Gn/Gp SGSN
  • Gn/Gp The SGSN cannot process the context request message of the GTPv2
  • the old mobility management network element converts the user context of the GTPv1 into the user context of the GTPv2, or carries the user context of the GTPv1 in the container cell of the GTPv2, and replies to the new mobile management network element.
  • the context response message of the GTPv2 with the context request message protocol version is consistent, and the user context of the converted GTPv2 or the container cell of the GTPv2 containing the user context of the GTPv1 is carried in the Context Response message of the GTPv2 that is replied to;
  • New mobile management network element (S4 After receiving the GTPv2 context response message, the SGSN or the MME node can learn the node type and the supported protocol version of the old mobile management network element service user terminal according to the user context of the GTPv2 in the response message or the container cell of the GTPv2.
  • Mobile Management Network Element (S4 After the SGSN or the MME node learns the node type of the old mobility management network element, it sends a correct setup session request message to the SGW to complete the subsequent routing area update or tracking area update process, and implements the user terminal to switch to the new mobility management network element. Accept the service.
  • the old-side mobility management network element may select a bearer identifier of the bearer context as the default bearer identifier carried in the GTPv2 context response message of the reply, or carry the invalid default bearer identifier in the GTPv2 context response message of the reply. .
  • the new mobile management network element (S4 The SGSN or MME node may learn that the old mobility management network element service user terminal is a Gn/Gp SGSN node according to the following information in the received GTPv2 context response message:
  • the response message carries a container cell containing the user context of GTPv1.
  • FIG. 4 shows a routing area update or tracking area update process in an EPS network.
  • the old access network is a 3GPP access of UTRAN/GERAN, and corresponding wireless access respectively.
  • the node is RNC/BSS, and the mobility management network element is Gn/Gp.
  • the SGSN is a unified node; the new access network is the 3GPP access of the GERAN/UTRAN/E-UTRAN, which respectively corresponds to the BSS/RNC/eNodeB, and the mobility management network element can be the S4 SGSN or MME (when it is an S4 SGSN node, it may be a node where Gn/Gp SGSN and S4 SGSN are combined, and the node serving the user terminal is S4) SGSN), the service gateway may be an SGW, the data gateway may be a PGW, and the HSS is responsible for managing and maintaining the subscription information of the home subscriber.
  • the specific steps of the routing area update or tracking area update process in FIG. 4 include:
  • Step 1 The user terminal sends a routing area update/tracking area update request message, and the request message is sent to the new mobility management network element S4 via the new side access network.
  • Step 2 New Mobile Management Network Element S4
  • the SGSN or the MME finds the old mobility management network element of the service user terminal in the old side access network according to the received routing area update request or the location information of the old side in the tracking area update message, and the new mobility management network element S4
  • the SGSN or MME sends a GTPv2 context request (Context) because it does not know whether the old mobility management network element service user terminal is a Gn/Gp SGSN or an S4 SGSN. Request) message to the old mobile management network element;
  • Step 3 The old mobile management network element is Gn/Gp SGSN and S4
  • the node where the SGSN is unified, when the user is on the old side, the old mobile management network element serves the user terminal is Gn/Gp SGSN; after receiving the context request message, the old mobility management network element SGSN unit discovers that the service user terminal is Gn/Gp according to the temporary identifier of the user in the context request message.
  • the old mobility management network element will be the user context of GTPv1 (UE Context) is converted to the user context of GTPv2, or the user context of GTPv1 is carried in the container cell of GTPv2 to the new mobile management network element S4.
  • the SGSN or MME replies to the GTPv2 context response message (Context Response), and carrying the translated GTPv2 user context or the GTPv2 container cell of the GTPv1 user context in the reply GTPv2 context response message;
  • Step 3 may further include: the old mobility management network element selects a bearer identifier of the bearer context as the default bearer identifier is carried in the GTPv2 context response message of the reply, or carries the invalid default bearer identifier in the context response message of the GTPv2.
  • Step 4 New Mobile Management Network Element S4
  • the SGSN or the MME After receiving the response message, the SGSN or the MME sends a context confirmation message to the old mobility management network element, and the new mobility management network element S4.
  • the SGSN or the MME learns that the old mobility management network element is a Gn/Gp SGSN according to the following information in the received GTPv2 context response message:
  • the response message does not carry the service gateway S4/S11/S12 user plane IP address and TEID or carries the invalid service gateway S4/S11/S12 user plane IP address and TEID;
  • the response message carries a container cell containing the user context of GTPv1.
  • Step 5 The new side S4 SGSN or MME (Mobile Management Network Element) learns that the old mobile management network element is Gn/Gp. After the SGSN, select the SGW, and send the correct setup session request message to the SGW;
  • MME Mobile Management Network Element
  • Step 6 The PGW updates the downlink user plane tunnel and the control plane tunnel
  • Step 7 The SGW replies to establish a session response message
  • Steps 8 and 9 The new side S4 SGSN or MME registers the location with the HSS, and obtains the subscription data of the user.
  • the old side Gn/Gp SGSN old mobile management network element cancels location registration;
  • Steps 10, 11 Routing Area Update/Tracking Area Update Complete and Accept.
  • the user terminal when the new side mobility management network element is S4 In the SGSN, the user terminal initiates a routing area update process.
  • the MME is the MME
  • the user terminal initiates a tracking area update process.
  • the user context of GTPv2 includes mobility management context and/or packet data network connection context (Packet Data) Network Connection Context, PDN Connection Context), the user context of GTPv1 includes mobility management context and/or Packet Data Protocol Context (PDP) Context), the user context of GTPv1 mapped to GTPv2 is:
  • the quality of service of the context under Gn/Gp SGSN (Quality of Service, QoS) is mapped to the bearer QoS of the EPS network;
  • MBR Maximum Bit Rate
  • the sending of the correct setup session request message to the SGW means that the setup session request message carries the AMBR cell and does not carry the default bearer identifier.
  • the new mobility management network element is also a node where the Gn/Gp SGSN and the S4 SGSN are unified, the node serving the user terminal is S4.
  • the new mobility management network element knows in step 3 that the old mobility management network element is Gn/Gp
  • the new mobility management network element can switch the S4 SGSN to the Gn/Gp SGSN by Gn/Gp.
  • the SGSN serves the user terminal; then the steps 5-7 are replaced with:
  • Step 5-1 The new mobility management network element Gn/Gp SGSN node after handover sends an update packet data protocol (Packet Data) Protocol, PDP) Update PDP Context Request message to the GGSN;
  • Packet Data Packet Data Protocol
  • PDP Packet Data Protocol
  • Step 6-1 The GGSN replies with an Update PDP Context Response message (Update PDP Context) Response).
  • the new side S4 when the user terminal initiates a routing area update or tracking area update procedure to the new side, the new side S4
  • the SGSN or MME node new mobility management network element
  • the old side Gn/Gp After receiving the Context Request message of the GTPv2, the SGSN node converts the user context from the user context of the GTPv1 to the user context of the GTPv2, or carries the user context of the GTPv1 in the container cell of the GTPv2 to the new side S4.
  • the SGSN or the MME node replies with the GTPv2 context response message that is consistent with the protocol version of the Context Request message, and carries the translated GTPv2 user context or the container cell that carries the GTPv1 user context in the Context Response message of the replied GTPv2.
  • New S4 The SGSN or the MME node can learn the node type of the old mobile management network element service user terminal according to the context in the received response message, further complete the subsequent routing area update or tracking area update process, save signaling overhead in the network, and avoid Waste of network resources.
  • the embodiment provides a processing method for a mobility management flow in a multi-generation mobile communication network, where the user terminal communicates in a multi-generation mobile communication network, and the nodes in the new mobility management network element are Gn/Gp SGSN and S4. Any one of the SGSN-integrated node, the MME, and the S4 SGSN, and when the new mobility management network element is a node where the Gn/Gp SGSN and the S4 SGSN are unified, the node serving the user terminal is S4.
  • the old mobile management network element is a node where the Gn/Gp SGSN and the S4 SGSN are unified, and the node of the old mobile management network element serving the user terminal is Gn/Gp.
  • the new mobility management network element is guaranteed to complete the mobility management process (including the attach process or the routing area update or the tracking area update process), and the method includes the following steps:
  • the method is described below when the mobility management process is an attach process, and the method includes the following steps:
  • the old mobility management network element receives the new mobility management network element (S4 SGSN or MME node, which is the S4 SGSN node, and may be Gn/Gp
  • An identity request message of the GTPv2 sent by the node of the SGSN and the S4 SGSN and the node of the serving user terminal is the S4 SGSN);
  • the old mobility management network element is a node where the Gn/Gp SGSN and the S4 SGSN are unified, the service user terminal is a Gn/Gp SGSN,
  • the old mobile management network element sends a response message consistent with the protocol version of the identity request information as a notification message to notify the new mobility management network element (S4) SGSN or MME node)
  • the protocol version of the node of the old mobility management network element serving user terminal is GTPv1, or the node type of the notification service user terminal is Gn/Gp SGSN;
  • the new mobility management network element (S4 SGSN or MME node) will contact S4.
  • S16 or S3 interface between SGSN nodes is converted to Gn/Gp
  • the Gn interface between the SGSN nodes, the reduced version uses the GTPv1 to send the GTPv1 identity request message, interacts with the old mobility management network element, obtains the user identity and the mobility management context, and completes the subsequent attach process.
  • the response message that is inconsistent with the protocol version of the identity request information may be further used as the reply message of the reply, for example, the identity request message for the GTPv2 may reply the response message of the GTPv1 as the response message of the reply;
  • FIG. 5 shows an attach procedure in an EPS network
  • the old side access network is a 3GPP access of UTRAN/GERAN
  • the corresponding radio access nodes are RNC/BSS, old.
  • the mobility management network element is Gn/Gp SGSN and S4
  • the SGSN is a unified node; the new side access network is a 3GPP access of GERAN/UTRAN/E-UTRAN, which respectively corresponds to a BSS/RNC/eNodeB, and the new mobility management network element can be S4 SGSN or MME (when it is an S4 SGSN node, it may be a node where Gn/Gp SGSN and S4 SGSN are combined, and the node serving the user terminal is S4) SGSN), the service gateway may be an SGW, the data gateway may be a PGW, and the HSS is responsible for managing and maintaining the subscription information of the home subscriber.
  • the attaching process in FIG. 5 specifically includes the following steps:
  • Step 1 The user terminal initiates an attach procedure, and sends an attach request message, and the message is sent to the new mobility management network element S4 through the new side access network.
  • Step 2 New Mobile Management Network Element S 4
  • the SGSN or the MME finds the old mobility management network element of the service user terminal in the old side access network according to the location information of the old side in the received attach request message, and the new mobility management network element S4
  • the SGSN or the MME sends the GTPv2 identity request message to the old mobility management network element because it does not know whether the old mobility management network element service user terminal is a Gn/Gp SGSN or an S4 SGSN.
  • Step 3 The old mobile management network element is Gn/Gp SGSN and S4
  • the node where the SGSN is unified, when the user is on the old side, the old mobile management network element serves the user terminal is Gn/Gp SGSN; after receiving the identity request message of the GTPv2, the old mobility management network element of the SGSN-integrated node discovers that the service user terminal is a Gn/Gp SGSN according to the temporary identifier of the user in the request message, and Gn/Gp
  • the Gn interface between the SGSN and the S4 SGSN or the MME is a GTPv1 interface and does not support the GTPv2 protocol.
  • the old mobile management network element SGSN replies with a response message to notify the new mobility management network element S4 SGSN or MME, the GTP protocol version adopted by the old mobility management network element, or the node type of the service user terminal: the old side Gn/Gp SGSN node notifies the S4 by using the GTPv2 message as a notification message.
  • the version type supported by the SGSN or MME service user terminal node type is GTPv1, or the old mobility management network element notifies the new mobility management network element S4 through the response message of GTPv1 or GTPv2.
  • the node type of the SGSN or MME serving user terminal is Gn/Gp SGSN; in this step, the identity request message for GTPv2, the old side Gn/Gp
  • the SGSN node can also use the GTPv1 message as the reply message of the reply.
  • the response message of the reply may carry a cell indicating that the protocol supported by the old mobility management network element is the GTPv1 protocol, or the carrying cell indicates that the node type of the old mobility management network element is Gn/Gp. SGSN.
  • the response message replied may be an existing identity response message, a version not supported message, or a newly added message, etc., and the type of the response message is not limited);
  • Step 4 New Mobile Management Network Element S4 After receiving the response message of the GTP protocol version of the old mobility management network element, or notifying the response message of the node type, the SGSN or the MME learns that the old mobility management network element supports the GTPv1 protocol, or learns that the old mobility management network element is Gn/Gp.
  • the IP address of the old mobile management network element Gn/Gp SGSN is S4
  • the IP address of the SGSN is different, and the new mobility management network element S4 SGSN or MME changes the destination IP address in the identity request message to the IP address of the Gn/Gp SGSN to resend the request message;
  • Step 5 The old side Gn/Gp SGSN (old mobile management network element) replies to the identity response message of GTPv1;
  • Step 6 Authentication/security process, the process is optional
  • Steps 7, 8 New Side S4
  • the SGSN or the MME New Mobile Management Network Element registers the location with the HSS, and obtains the subscription data of the user, and the old side Gn/Gp SGSN cancels the location registration;
  • Step 9 The session establishment process of the MME, the SGW, and the PGW establishes a default bearer, and the step is only performed when the E-UTRAN is accessed;
  • Steps 10, 11 Attachment acceptance and completion
  • Step 12 The bearer update process, the SGW updates the downlink user plane tunnel information, and the step is only performed when the E-UTRAN accesses.
  • the new mobility management network element is also S4 SGSN and Gn/Gp
  • the node of the SGSN is unified, and the node serving the user terminal is the S4 SGSN.
  • the new mobility management network element learns in step 3 that the old mobility management network element is Gn/Gp
  • the new mobility management network element can switch the S4 SGSN to the Gn/Gp SGSN by Gn/Gp.
  • the SGSN serves the user terminal.
  • the user terminal initiates an attach procedure to the new side, and the new side S4
  • the SGSN or MME node new mobility management network element
  • the old side Gn/Gp new mobile management network element
  • the SGSN node confirms that it cannot be processed, and then responds to the GTPv2 response message that is consistent with the protocol of the identity request message as a notification message to notify the new side S4.
  • the SGSN or the MME node enables the new mobility management network element to establish a correct interaction with the old mobility management network element, obtain the user identity, and the user context, and complete the subsequent attach process, thereby avoiding the signaling overhead of the network added in the attach process, saving A waste of network resources.
  • the method for processing a mobility management process in a multi-generation mobile communication network is provided.
  • the method is applicable to a user terminal to initiate a tracking area update or a routing area update process when the user terminal switches to the new mobile management network to receive a service, and the method specifically includes The following steps:
  • the old mobility management network element receives the new mobility management network element (S4 SGSN or MME node, which is the S4 SGSN node, and may be Gn/Gp a GTPv2 context request message sent by the SGSN and the S4 SGSN in a node, and the node serving the user terminal is the S4 SGSN);
  • S4 SGSN or MME node which is the S4 SGSN node, and may be Gn/Gp a GTPv2 context request message sent by the SGSN and the S4 SGSN in a node, and the node serving the user terminal is the S4 SGSN
  • the old mobile management network element is Gn/Gp SGSN and S4
  • the node of the SGSN is one, the node of the old mobile management network element serving user terminal is Gn/Gp SGSN, Gn/Gp
  • the SGSN cannot process the context request message of the GTPv2, and the old mobility management network element sends a response message as a notification message to notify the new mobility management network element (S4).
  • SGSN or MME node The protocol type of the node type of the old mobility management network element serving user terminal is GTPv1, or the node type of the notification service user terminal is Gn/Gp SGSN;
  • the response message of the reply may carry a cell indicating that the protocol supported by the old mobility management network element is the GTPv1 protocol, or the carrying cell indicates that the node type of the old mobility management network element is Gn/Gp. SGSN.
  • the response message that is replied may be an existing context response message, a version not supported message, or a newly added message, and the type of the response message is not limited.
  • the new mobile management network element (new side S4 SGSN or MME node) receives the notification message, it will work with S4.
  • S16 or S3 interface between SGSN nodes is converted to Gn/Gp
  • the Gn interface between the SGSN nodes, the reduced version uses the GTPv1 to send the GTPv1 SGSN Context Request message, interacts with the old mobility management network element, acquires the user context, completes the subsequent tracking area update or routing area update process, and causes the user terminal to switch to The new mobile management network element accepts the service.
  • the IP address of the SGSN is different from the IP address of the S4 SGSN.
  • the new side S4 SGSN or MME changes the destination IP address in the SGSN Context Request message to the old side Gn/Gp.
  • the request message is sent after the IP address of the SGSN.
  • FIG. 6 shows a tracking area update or routing area update process in an EPS network.
  • the old side access network is a 3GPP access of UTRAN/GERAN, and corresponding wireless connections respectively.
  • the ingress node is RNC/BSS, and the old mobility management network element is Gn/Gp.
  • the SGSN is a unified node; the new side access network is a 3GPP access of GERAN/UTRAN/E-UTRAN, which respectively corresponds to a BSS/RNC/eNodeB, and the new mobility management network element can be S4 SGSN or MME (when it is an S4 SGSN node, it may be a node where Gn/Gp SGSN and S4 SGSN are combined, and the node serving the user terminal is S4) SGSN), the service gateway may be an SGW, the data gateway may be a PGW, and the HSS is responsible for managing and maintaining the subscription information of the home subscriber.
  • the specific steps of the routing area update or tracking area update process in FIG. 6 include:
  • Step 1 The user terminal sends a routing area update or tracking area update request message, and the message is sent to the new mobility management network element S4 via the new side access network.
  • Step 2 New Side S4
  • the SGSN or the MME finds the old mobility management network element of the service user terminal in the old side access network according to the received old area location information in the routing area update or tracking area update request message, and the new side S4 SGSN or MME (New Mobility Management Network Element) because it is not known whether the old mobile management network element service user terminal is Gn/Gp SGSN or S4
  • the SGSN sends a context request message of the GTPv2 to the old mobility management network element;
  • Step 3 The old mobile management network element is Gn/Gp SGSN and S4 The node where the SGSN is unified, when the user is on the old side, the service user terminal is the Gn/Gp SGSN; After receiving the context request message of the GTPv2, the old mobility management network element of the SGSN unified node discovers that the service user terminal is a Gn/Gp SGSN according to the temporary identifier of the user in the request message, and Gn/Gp The Gn interface between the SGSN and the S4 SGSN or the MME is a GTPv1 interface and does not support GTPv2.
  • the SGSN (old mobile management network element) replies with a response message as a notification message to notify the new side S4
  • the current protocol version of the SGSN or MME is GTPv1, or the old mobility management network element notifies the S4 by replying to the GTPv2 response message.
  • the node type of the SGSN or the MME old mobile management network element service user terminal is Gn/Gp SGSN.
  • the response message of the GTPv1 may also be returned as a notification message to notify the new side S4.
  • the current protocol version of the old mobility management network element is GTPv1S4 SGSN or the current protocol version of the MME is GTPv1, or the node type of the service user terminal is Gn/Gp. SGSN.
  • the response message of the reply may carry a cell to indicate the GTPv1 protocol, or carry a cell to indicate Gn/Gp.
  • the node type of the SGSN; the response message that is replied may be an existing context response message, a version not supported message, or a newly added message, etc., and does not limit the type of the response message;
  • Step 4 New Side S4 After receiving the notification message of the GTP protocol version of the old mobility management network element or the notification message of the node type, the SGSN or the MME (the new mobility management network element) learns that the old mobility management network element supports GTPv1, or learns that the old mobility management network element is Gn. /Gp SGSN, the new side S4 SGSN or MME converts the S16 or S3 interface into a Gn interface, and sends a GTPv1 SGSN Context Request message to the old mobility management network element;
  • the new side S4 SGSN or MME sends the request message after changing the destination IP address in the SGSN Context Request message to the IP address of the Gn/Gp SGSN.
  • Step 5 The old-side SGSN replies to the SGSN context response message of the GTPv1, and the message carries the context of the user terminal.
  • Step 6 The new side S4 SGSN or MME replies to the SGSN context confirmation message
  • Step 7 The new side S4 SGSN or MME selects the SGW, and establishes a control plane tunnel with the SGW;
  • Step 8 The PGW updates the downlink user plane tunnel and the control plane tunnel
  • Step 9 The SGW replies to the session establishment response message
  • Steps 10 and 11 The new side S4 SGSN or MME registers the location with the HSS, and obtains the subscription data of the user.
  • the old side Gn/Gp SGSN cancels location registration;
  • Steps 12, 13 Routing Area Update/Tracking Area Update Complete and Accept.
  • the user terminal when the new side mobility management network element is S4 In the SGSN, the user terminal initiates a routing area update process.
  • the MME is the MME
  • the user terminal initiates a tracking area update process.
  • the user context includes a mobility management context and/or a PDP context.
  • the new mobility management network element is also Gn/Gp SGSN and S4
  • the node of the SGSN is unified.
  • the new mobility management network element learns in step 3 that the old mobility management network element is Gn/Gp
  • the new mobility management network element can switch the S4 SGSN to the Gn/Gp SGSN by Gn/Gp.
  • the SGSN serves the user terminal. Steps 7-9 above can be replaced by:
  • Step 7-1 The Gn/Gp SGSN sends an update PDP context request message to the GGSN.
  • Step 8-1 The GGSN replies with an Update PDP Context Response message.
  • the user terminal initiates a tracking area update or routing area update process to the new mobility management network element, and the new side S4
  • the SGSN or MME node new mobility management network element
  • the old side Gn/Gp old mobile management network element
  • the SGSN node After receiving the context request message of the GTPv2, the SGSN node notifies that the new mobility management network element is notified by the notification message, so that the new mobility management network element can confirm the node type of the old mobility management network element service user terminal and the node support.
  • the protocol version so that the old mobile management network element can establish correct interaction, obtain the user context, complete the follow-up tracking area update or the routing area update process, and enable the user terminal to switch to the new mobile management network element to receive the service, thereby avoiding tracking area update or routing.
  • the signaling overhead of the network is increased in the area update process, which saves network resources waste.
  • the embodiment provides a processing system for a mobility management flow in a multi-generation mobile communication network, which can be used in a multi-generation mobile communication network composed of a next-generation mobile communication network and a second-generation and third-generation mobile communication network, and the system is available.
  • the system includes:
  • the new mobility management network element 23 is configured to send a request message requesting user information to the old mobility management network element after receiving an attach request message or a routing area update request message or a tracking area update request message sent by the user terminal; And completing the mobility management process according to the response message replied by the old mobility management network element;
  • the old mobility management network element 21 is configured to reply a response message to the new mobility management network element 23 according to the request information.
  • the old side communication processing device 22 is configured to determine, by the old mobility management network element 21, the request message sent by the new mobility management network element 23, when the protocol version of the request message is When the protocol version supported by the node of the old mobility management network element service user terminal is inconsistent, the response message that is consistent with the protocol version of the request message is used as a response message that the old mobility management network element replies to the new mobility management network element.
  • the old-side communication processing device 22 in the above system specifically includes:
  • the receiving unit 221 is configured to receive the request message sent by the old mobility management network element 21 and sent by the new mobility management network element 23;
  • the request message processing unit 222 is configured to determine a node type of the old mobility management network element service user terminal according to the user temporary identifier in the request message received by the receiving unit 221, and determine a service user according to the node type. a version of the protocol supported by the node of the terminal, when the protocol version of the request message is inconsistent with the protocol version supported by the node type of the old mobility management network element service user terminal, and the response message is consistent with the protocol version of the request message. As a response message that the old mobility management network element 21 replies to the new mobility management network element 23, and carries the user identity identifier as the user information in the response message;
  • the sending unit 223 is configured to send a reply response message that is determined by the request message processing unit 222.
  • the request message processing unit 222 in the old side communication processing device 22 further includes:
  • the conversion processing sub-unit 224 is configured to convert the context information into a protocol version with the old mobility management network element request message when the protocol version of the request message is inconsistent with the protocol version supported by the node type of the service user terminal. Consistent context information, and the converted context information is carried as user information in the response message of the reply.
  • the conversion processing sub-unit 224 may convert the mobility management context of the GTPv1 into the mobility management context of the GTPv2 for the identity request message of the GTPv2 sent by the attach procedure; the context request message sent for the routing area update or the tracking area update procedure,
  • the user context of GTPv1 can be converted to the user context of GTPv2.
  • the request message processing unit 222 in the old-side communication processing device 22 further includes:
  • a cell processing sub-unit 225 configured to: when the protocol version of the request message is inconsistent with a protocol version supported by a node type of the old mobility management network element serving user terminal, carry the context information in the container cell, and The container cell is carried in a response message of the reply.
  • the cell processing sub-unit 225 may carry the mobility management context of the GTPv1 in the container cell of the GTPv2, and the container cell including the mobility management context of the GTPv1 Carrying in the response message of the reply; for the routing area update or the context request message sent by the tracking area update process, the cell processing sub-unit 225 can carry the user context of the GTPv1 in the container cell and will include the user context of the GTPv1 The container cell is carried in a response message of the reply;
  • the new mobility management network element S4 In the mobility management process of the new mobility management network element for the user terminal (including: attach process, tracking area update, or routing area update process), the new mobility management network element S4
  • the SGSN or MME node cannot know that the old mobility management network element is a Gn/Gp SGSN node, the old side Gn/Gp
  • the SGSN node receives the context request message of the GTPv2, and confirms that the response message cannot be processed, and returns a response message that is consistent with the version of the request message protocol to the new mobility management network element, and carries the user information in the response message of the reply.
  • the new mobility management network element can complete the subsequent mobility management process according to the user information, which saves signaling overhead in the network and avoids waste of network resources.
  • the embodiment provides a processing system for a mobility management flow in a multi-generation mobile communication network, and the processing system can be used in a multi-generation mobile communication network composed of a next-generation mobile communication network and a second-generation and third-generation mobile communication network.
  • the system is also used to implement the processing method in the above embodiment, which is basically the same as the system structure of the above-mentioned fifth embodiment.
  • the difference is the structure of the old-side communication processing device. As shown in FIG. 10, the old-side communication processing device includes:
  • a receiving unit 2211 a request message processing unit 2212, and a notification message transmitting unit 2213;
  • the receiving unit 2211 is configured to receive the request message sent by the new side communication processing device 24;
  • the request message processing unit 2212 is configured to determine a node type of the old mobility management network element service user terminal according to the user temporary identifier in the request message received by the receiving unit, and determine a service user terminal according to the node type. a protocol version supported by the node, when the protocol version of the request message is inconsistent with the protocol version supported by the node type of the service user terminal, the response message that is consistent with the protocol version of the request message is used as the reply message of the reply, The notification message is used to notify the new mobility management network element that the old mobility management network element serves the node type of the user terminal and/or the protocol version supported by the node of the service user terminal;
  • the notification message sending unit 2213 is configured to send a response message as a notification message that is replied to the new side communication processing device.
  • the request message processing unit in the old side communication processing device further includes:
  • the indication information setting sub-unit 22121 is configured to carry the indication information (such as the indication cell) in the reply notification message, and indicate the node type of the old mobility management network element service user terminal and/or the node of the service user terminal by using the indication information.
  • the supported protocol version is configured to carry the indication information (such as the indication cell) in the reply notification message, and indicate the node type of the old mobility management network element service user terminal and/or the node of the service user terminal by using the indication information.
  • the supported protocol version is configured to carry the indication information (such as the indication cell) in the reply notification message, and indicate the node type of the old mobility management network element service user terminal and/or the node of the service user terminal by using the indication information.
  • the new mobility management network element can learn the node type of the old mobility management network element and the protocol version supported by the node, and can correctly establish interaction with the old mobility management network element to complete the subsequent mobility management process. It saves signaling overhead in the network and avoids waste of network resources.
  • the new side communication processing device 24 and the new mobile management network in the next generation mobile communication network may be further included.
  • the element 23 communication connection is configured to determine a response message received by the new mobility management network element 23, and determine a node type of the old mobility management network element service user terminal.
  • the new side communication processing device 24 specifically includes:
  • the receiving unit 241 is configured to receive a response message received by the new mobility management network element 23 and replied from the old mobility management network element 21;
  • the determining unit 242 determines the response message, determines the node type of the old mobile management network element 21 serving the user terminal, and further determines the protocol version supported by the node of the old mobility management network element 21.
  • the new side communication processing device 24 described above may further include:
  • the node type conversion unit 243 learns that the node type of the old mobility management network element serving user terminal is Gn/Gp SGSN, and the new mobility management network element is Gn/Gp, according to the determination result of the determining unit 242. a node in which the SGSN and the S4 SGSN are unified, and the node of the new mobility management network element serving the user terminal is an S4 SGSN, and the node of the new mobility management network element serving the user terminal is from the S4
  • the SGSN is replaced by a Gn/Gp SGSN, and the Gn/Gp SGSN serves the user terminal.
  • the new mobility management network element determines the node type of the old mobility management network element and the supported protocol version
  • the new mobility management network element is also S4 SGSN and Gn/Gp.
  • the node of the SGSN is unified, and the node serving the user terminal is the S4 SGSN, and the new mobility management network element is switched from the S4 SGSN to the Gn/Gp SGSN by Gn/Gp.
  • the SGSN serves the user terminal, and can maintain the GGSN node shape unchanged, and reduce the conversion of context, QoS, etc. on the GGSN.
  • the old mobile management network element is Gn/Gp SGSN and S4.
  • the node of the SGSN is unified, and the service user terminal is Gn/Gp.
  • the new mobility management network element does not know the old mobile management network element node type and uses the GTPv2 protocol to communicate with the old mobility management network element, the connection process or the tracking area update or the routing area update process can be guaranteed to be normal, saving the operation.
  • the signaling overhead in the network avoids the waste of network resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明涉及一种多代移动通信网络中移动性管理流程的处理方法及系统，属通信技术领域。该方法包括：接收新移动管理网元发送的请求用户信息的请求消息；当收到的所述请求消息的协议版本与老移动管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息；通过所述响应消息使所述新移动管理网元完成移动性管理流程。该方法使新移动管理网元在不知道老侧网络中服务用户终端的老移动管理网元的节点类型时，仍然能够获取用户终端的身份标识或用户终端的上下文，使用户终端可以继续在新侧网络内接受服务，可节约网络内的信令开销或避免流程中断。

Description

多代移动通信网络中移动性管理流程的处理方法及系统
技术领域
本发明涉及通信技术领域，尤其涉及一种多代移动通信网络中移动性管理流程的处理方法及系统。
发明背景
目前的下一代移动通信网络的逻辑架构如图1所示，在该下一代网络中，用户终端通过本地的无线接入网络接入，移动管理网元负责用户终端的位置管理、连接管理、安全认证、网关选择等功能，服务网关是用户终端的本地接入网关，负责接入技术相关的连接管理和数据转发，数据网关是用户终端访问外部数据网络的网关。图1所示的下一代移动通信网络的逻辑架构对应实际网络，可以是演进的分组系统（Evolved Packet System，EPS）网络，对于UTRAN/GERAN/E-UTRAN接入网，移动管理网元可以是移动性管理实体（Mobility Management Entity，MME）或者GPRS服务支撑节点（Serving GPRS Support Node，S4 SGSN），服务网关可以是服务网关（Serving Gateway，S-GW），数据网关可以是报文数据网络网关（Packet Data Network Gateway，PDN-GW）。
目前的第二代，第三代（2G/3G）移动通信网络的逻辑架构如图2所示，在该第二代，第三代（2G/3G）移动通信网络中，用户终端通过本地的无线接入网接入，移动管理网元集合了下一代移动通信网络中的移动管理网元和服务网关的功能。所述的第二代，第三代移动通信网络对应实际网络，可以是GPRS网络，或者UMTS网络，对于UTRAN/GERAN接入网，移动管理网元可以是GPRS服务支撑节点（Gn/Gp Serving GPRS Support Node，Gn/Gp SGSN），数据网关可以是GPRS网关支撑节点（Gateway GPRS Support Node，GGSN）。
若用户终端附着到移动通信网络，而之前用户终端在移动通信网络中去附着，若当前附着的移动通信网络中服务用户终端的新移动管理网元与之前去附着的移动通信网络中服务用户终端的老移动管理网元不是同一个节点，则新移动管理网元会向老移动管理网元请求认证用户终端的身份，并获取用户终端的上下文；
类似的，若由于移动或者其他的一些原因，用户终端在网络中发起跟踪区域更新（Tracking Area Update，TAU），或者路由区域更新（Routeing Area Update，RAU）流程，如果服务用户终端的移动管理网元发生变化，新移动管理网元会向之前服务用户终端的老移动管理网元请求获取用户终端的上下文。
不同移动管理网元之间通信的接口采用GTP（GPRS Tunnelling Protocol，GPRS隧道协议）协议，但对于不同的实体间通信，采用的GTP协议版本不同。EPS网络（下一代移动通信网络）的核心网网元之间通信采用GTPv2协议（其中，MME（Mobility Management Entity，移动管理实体）和MME之间为S10接口，S4 SGSN（GPRS服务支撑节点）和S4 SGSN之间采用S16接口，S4 SGSN和MME之间采用S3接口，这些接口均采用GTPv2协议），EPS网络的移动管理网元和2G/3G网络（第二代，第三代移动通信网络）的移动管理网元之间通信采用GTPv1协议（MME和Gn/Gp SGSN之间采用Gn接口，S4 SGSN和Gn/Gp SGSN也采用Gn接口，Gn接口采用GTPv1协议），2G/3G网络的移动管理网元之间通信也采用GTPv1协议（Gn/Gp SGSN之间也采用Gn接口，为GTPv1协议）。
从上述对服务用户终端的移动管理网元发生变化的附着或路由区域更新或跟踪区域更新流程介绍中，发现现有技术至少存在下述问题：若新移动管理网元为EPS网络的MME节点、S4 SGSN节点、Gn/Gp SGSN和S4 SGSN合一的节点中的任一种，且在新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时，服务用户终端的节点为S4 SGSN，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，且新移动管理网元不知道老移动管理网元的节点类型，当用户终端从老移动管理网元去附着后在新移动管理网元附着，或者用户终端发起TAU或者RAU流程从老移动管理网元切换到新移动管理网元时，新移动管理网元需要向老移动管理网元请求认证用户终端的身份，或者获取用户终端的上下文。但由于新移动管理网元无法知道老移动管理网元服务用户终端的节点是Gn/Gp SGSN还是S4 SGSN，因此新移动管理网元无法知道应该采用GTPv2协议还是GTPv1协议与老移动管理网元通信。当新移动管理网元发送GTPv2的请求消息给老移动管理网元（Gn/Gp SGSN与S4 SGSN合一节点）时，老移动管理网元服务用户终端的节点是Gn/Gp SGSN，所支持的协议版本为GTPv1，与收到GTPv2的请求消息的协议版本不一致，无法直接处理该GTPv2的请求消息，会导致要经几次消息传递，才能建立正确交互，增加了网络内的信令消息，浪费网络资源。
发明内容
本发明实施例的目的是提供一种多代移动通信网络中移动性管理流程的处理方法及系统，解决用户终端的移动性管理流程中，当新、老移动管理网元服务用户终端的节点所支持的协议版本不一致，且新移动管理网元不知道老移动管理网元服务用户终端的节点类型的情况下，新移动管理网元无法与老移动管理网元正确交互，导致网络内信令开销增加，消费网络资源，使新移动管理网元不能顺利完成移动性管理流程的问题。
本发明实施例的目的是通过下述技术方案实现的：
本发明实施例提供一种多代移动通信网络中移动性管理流程的处理方法，新移动管理网元的节点为Gn/Gp SGSN和S4 SGSN合一的节点、MME、S4 SGSN中的任一种，当新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时服务用户终端的节点为S4 SGSN；老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，所述老移动管理网元服务用户终端的节点为Gn/Gp SGSN；包括：
接收新移动管理网元发送的请求用户信息的请求消息；
当收到的所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息，所述响应消息的协议版本与所述新移动管理网元发送的请求消息的版本一致；
通过所述响应消息使所述新移动管理网元完成移动性管理流程。
本发明实施例还提供一种多代移动通信网络中移动性管理流程的处理系统，用在由下一代移动通信网络和第二代、第三代移动通信网络构成的多代移动通信网络中，包括：
老侧通信处理装置，老侧通信处理装置与所述第二代、第三代移动通信网络中的老移动管理网元通信连接；
所述新移动管理网元，用于在接收用户终端发送的附着请求消息或路由区域更新请求消息或跟踪区域更新请求消息后，向所述老移动管理网元发送请求用户信息的请求消息；并根据所述老移动管理网元回复的响应消息完成移动性管理流程；
所述老移动管理网元，用于根据所述请求信息向所述老移动管理网元回复响应消息；
所述老侧通信处理装置，用于对所述老移动管理网元收到的由所述新移动管理网元发送的所述请求消息进行判断，当所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为老移动管理网元回复给所述新移动管理网元的响应消息。
本发明实施例的技术方案，在移动性管理流程中，当新移动管理网元不能获知老侧网络中服务用户终端的移动管理网元的节点类型时，仍能与老移动管理网元正确交互，获取用户终端的用户信息，使新移动管理网元能够完成用户终端的移动性管理流程，从而节约了网络的信令开销，节省了网络资源。
附图简要说明
图1为现有技术提供的下一代移动通信网络的逻辑架构图；
图2为现有技术提供的第二代、第三代移动通信网络的逻辑架构图；
图3为本发明实施例一提供的处理方法的流程示意图；
图4为本发明实施例二提供的处理方法的流程示意图；
图5为本发明实施例三提供的处理方法的流程示意图；
图6为本发明实施例四提供的处理方法的流程示意图；
图7为本发明实施例五提供的处理系统的结构框图；
图8为本发明实施例五提供的处理系统的老侧通信处理装置的结构框图；
图9为本发明实施例五提供的处理系统的另一种老侧通信处理装置的结构框图；
图10为本发明实施例六提供的处理系统的老侧通信处理装置的结构框图；
图11为本发明实施例提供的另一种处理系统的结构框图；
图12为本发明实施例提供的处理系统的新侧通信处理装置的结构框图。
实施本发明的方式
下面结合附图和具体实施例对本发明作进一步地详细描述。
本发明实施例提供的多代移动通信网络中移动性管理流程的处理方法及系统，用于用户终端在多代移动通信网络中通信，新移动管理网元的节点为Gn/Gp SGSN和S4 SGSN合一的节点、MME、S4 SGSN中的任一种，且当新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时服务用户终端的节点为S4 SGSN，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，老移动管理网元服务用户终端的节点为Gn/Gp SGSN的情况下，在新移动管理网元进行移动性管理流程时，可在新移动管理网元不知道老移动管理网元服务用户终端的节点类型时，仍能与老移动管理网元正确交互，获取用户终端的用户身份标识和/或上下文信息，完成移动性管理流程，使用户终端可以切换至新移动管理网元接受服务，从而节约附着流程中网络的信令开销，节省网络资源。
实施例一
本实施例提供一种多代移动通信网络中移动性管理流程的处理方法，用于用户终端在多代移动通信网络中通信，在用户终端的移动性管理流程中，新移动管理网元的节点为Gn/Gp SGSN和S4 SGSN合一的节点、MME、S4 SGSN中的任一种，且当新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时服务用户终端的节点为S4 SGSN，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，老移动管理网元服务用户终端的节点为Gn/Gp SGSN的情况下，保证新移动管理网元完成对用户终端的移动性管理流程（包括附着流程或路由区域更新或跟踪区域更新流程）。
下面针对移动性管理流程为附着流程时，对该方法进行说明，该方法包括下述步骤：
老移动管理网元接收新移动管理网元（MME或S4 SGSN节点，当为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN）发送的GTPv2的身份请求消息；
若老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，该老移动管理网元服务用户终端的节点为Gn/Gp SGSN，Gn/Gp SGSN无法处理GTPv2的身份请求消息，老移动管理网元向新移动管理网元回复与身份请求消息协议版本一致的GTPv2的响应消息，所述GTPv2的响应消息中携带用户身份标识作为用户信息；
新移动管理网元（MME或S4 SGSN节点）收到GTPv2的响应消息后，可根据响应消息中的用户信息完成后续的附着流程，实现用户终端附着至新移动管理网元接受服务。
进一步的，老移动管理网元将GTPv1的移动性管理上下文转换为GTPv2的移动性管理上下文，并将转换后的GTPv2的移动性管理上下文和用户身份标识均携带在回复的GTPv2的响应消息中作为用户信息；或者老移动管理网元将GTPv1的移动性管理上下文携带在GTPv2的容器信元中，并将该GTPv2的容器信元和用户身份标识均携带在回复的GTPv2的响应消息中作为用户信息。
下面结合图3对上述方法作具体说明，图3所示为EPS网络内的附着流程，图中老侧接入网为UTRAN/GERAN的3GPP接入，分别对应的无线接入节点为无线网络控制器（Radio Network Controller，RNC）/基站子系统（Base Station Subsystem，BSS），老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点；新侧接入网为GERAN/UTRAN/E-UTRAN的3GPP接入，分别对应为BSS/RNC/演进的节点B（Evolved Node B，eNodeB），新移动管理网元的节点可以为S4 SGSN或MME（为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN），服务网关可以为SGW，数据网关可以为PGW，家乡用户寄存器（Home Subscriber Server，HSS）负责归属地用户签约信息的管理和维护。
图3中的附着流程具体包括下述步骤：
步骤1：用户终端发起附着流程，发送附着请求消息，该消息经过新侧接入网发送给新侧S4 SGSN或MME（为新移动管理网元）；
步骤2：新侧S4 SGSN或MME根据收到的附着请求消息中的老移动管理网元位置信息找到老侧的接入网中服务用户终端的老移动管理网元，新侧S4 SGSN或MME因为不知道老移动管理网元服务用户终端的节点是Gn/Gp SGSN还是S4 SGSN，发送GTPv2的身份请求（Identification Request）消息给老移动管理网元；
步骤3：老移动管理网元是Gn/Gp SGSN和S4 SGSN合一的节点，用户在老侧时，老移动管理网元服务用户终端的是Gn/Gp SGSN；合一节点的老移动管理网元收到GTPv2的身份请求消息后，根据该GTPv2的请求消息中的用户临时标识发现服务用户终端的是Gn/Gp SGSN，老移动管理网元确认Gn/Gp SGSN无法处理新移动管理网元发送的GTPv2的身份请求消息，老移动管理网元回复与身份请求消息协议版本一致的GTPv2的身份响应消息（Identification Response）给新侧的S4 SGSN或MME，消息中携带用户身份标识（International Mobile Subscriber Identity，IMSI）；
进一步的，老移动管理网元将GTPv1的移动性管理上下文（Mobility Management Context，MM Context）转换为GTPv2的移动性管理上下文，并将转换后的GTPv2的移动性管理上下文与用户身份标识一同携带在向新移动管理网元回复的GTPv2的身份响应消息中；或者老移动管理网元将GTPv1的移动性管理上下文携带在GTPv2的容器信元中，并将该GTPv2的容器信元和用户身份标识均携带在向新移动管理网元回复的GTPv2的身份响应消息中。
步骤4：认证/安全过程，该步骤为可选过程；
步骤5、6：新侧S4 SGSN或MME向HSS登记位置，并获取用户的签约数据，老侧Gn/Gp SGSN取消位置登记；
步骤7：MME，SGW和PGW的会话建立过程，建立缺省承载，该步骤只在E-UTRAN接入时执行；
步骤8、9：附着接受和完成；
步骤10：承载更新过程，SGW更新下行用户面隧道信息，该步骤只在E-UTRAN接入时执行。
通过本实施例的方法，使用户终端在向新移动管理网元发起附着流程，新侧S4 SGSN或MME节点（新移动管理网元）无法识别老移动管理网元（老侧Gn/Gp SGSN节点）的节点类型时，老侧Gn/Gp SGSN节点（老移动管理网元）收到GTPv2的身份请求消息后，确认无法处理后，向新侧S4 SGSN或MME节点回复与身份请求消息协议版本一致的GTPv2的响应消息，并在回复的GTPv2的响应消息中携带用户身份标识，或携带用户身份标识和从GTPv1的移动性管理上下文转换后的GTPv2的移动性管理上下文，或携带用户身份标识和包含GTPv1的移动性管理上下文的GTPv2的容器信元。使得新侧S4 SGSN或MME节点可以收到用户终端的身份标识，以及移动性管理上下文，从而顺利完成附着流程，避免了附着流程中网络的信令开销，避免了浪费网络资源。
实施例二
本实施例提供一种多代移动通信网络中移动性管理流程的处理方法，该方法适用于多代移动通信网络中用户终端在切换至新移动管理网络接受服务时，发起路由区域更新或跟踪区域更新流程，该方法具体包括下述步骤：
老移动管理网元接收新移动管理网元（S4 SGSN或MME节点，为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN）发送的GTPv2的上下文请求消息；
若老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，该老移动管理网元服务用户终端的节点为Gn/Gp SGSN，Gn/Gp SGSN无法处理GTPv2的上下文请求消息，则老移动管理网元将GTPv1的用户上下文转换为GTPv2的用户上下文，或者将GTPv1的用户上下文携带在GTPv2的容器信元中，向新移动管理网元回复与上下文请求消息协议版本一致的GTPv2的上下文响应消息，在回复的GTPv2的上下文响应消息中携带转换后的GTPv2的用户上下文或包含GTPv1的用户上下文的GTPv2的容器信元；
新移动管理网元（S4 SGSN或MME节点）收到GTPv2的上下文响应消息后，可根据响应消息中的GTPv2的用户上下文或GTPv2的容器信元，获知老移动管理网元服务用户终端的节点类型及支持的协议版本，新移动管理网元（S4 SGSN或MME节点）获知老移动管理网元的节点类型后，则发送正确的建立会话请求消息给SGW，来完成后续的路由区域更新或跟踪区域更新流程，实现用户终端切换至新移动管理网元接受服务。
进一步的，老侧移动管理网元可选择一个承载上下文的承载标识作为缺省承载标识携带在回复的GTPv2的上下文响应消息中，或者携带无效的缺省承载标识在回复的GTPv2的上下文响应消息中。
而新移动管理网元（S4 SGSN或MME节点）可根据收到的GTPv2的上下文响应消息中的如下信息获知老移动管理网元服务用户终端的是Gn/Gp SGSN节点：
（1）如果响应消息中没有携带SGW（服务网关）控制面IP地址和隧道标识或者携带了无效的SGW控制面IP地址和隧道标识；
（2）响应消息中没有携带SGW用户面IP地址和隧道标识或者携带了无效的SGW用户面IP地址和隧道标识；
（3）响应消息中没有携带缺省承载标识或者携带无效的缺省承载标识；
（4）响应消息中携带包含GTPv1的用户上下文的容器信元。
下面结合图4对上述方法作具体说明，图4所示为EPS网络内的路由区域更新或跟踪区域更新流程，图中老接入网为UTRAN/GERAN的3GPP接入，分别对应的无线接入节点为RNC/BSS，移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点；新接入网为GERAN/UTRAN/E-UTRAN的3GPP接入，分别对应为BSS/RNC/eNodeB，移动管理网元可以为S4 SGSN或MME（为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN），服务网关可以为SGW，数据网关可以为PGW，HSS负责归属地用户签约信息的管理和维护。
图4中的路由区域更新或跟踪区域更新流程具体步骤包括：
步骤1：用户终端发送路由区域更新/跟踪区域更新请求消息，该请求消息经过新侧接入网发送给新移动管理网元S4 SGSN或MME；
步骤2：新移动管理网元S4 SGSN或MME根据收到的路由区域更新请求或跟踪区域更新消息中的老侧的位置信息找到老侧接入网中服务用户终端的老移动管理网元，新移动管理网元S4 SGSN或MME因为不知道老移动管理网元服务用户终端的是Gn/Gp SGSN还是S4 SGSN，发送GTPv2的上下文请求（Context Request）消息给老移动管理网元；
步骤3：老移动管理网元是Gn/Gp SGSN和S4 SGSN合一的节点，用户在老侧时，老移动管理网元服务用户终端的是Gn/Gp SGSN；老移动管理网元SGSN合一节点收到上下文请求消息后，根据上下文请求消息中的用户临时标识发现服务用户终端的是Gn/Gp SGSN，老移动管理网元将GTPv1的用户上下文（UE Context）转换为GTPv2的用户上下文，或者将GTPv1的用户上下文携带在GTPv2的容器信元中，向新移动管理网元S4 SGSN或MME回复GTPv2的上下文响应消息（Context Response），并在回复的GTPv2的上下文响应消息中携带转换后的GTPv2的用户上下文或者包括GTPv1的用户上下文的GTPv2的容器信元；
步骤3还可以包括，老移动管理网元选择一个承载上下文的承载标识作为缺省承载标识携带在回复的GTPv2的上下文响应消息中，或者携带无效的缺省承载标识在GTPv2的上下文响应消息中。
步骤4：新移动管理网元S4 SGSN或MME收到响应消息后，发送上下文确认消息给老移动管理网元，新移动管理网元S4 SGSN或MME根据收到的GTPv2的上下文响应消息中的如下信息获知老移动管理网元为Gn/Gp SGSN：
（1）如果响应消息中没有携带服务网关S4/S11控制面IP（网际协议，Internet Protocol）地址和TEID（Tunnel Endpoint Identifier，隧道端点标识）或者携带了无效的服务网关S4/S11控制面IP地址和TEID；
（2）响应消息中没有携带服务网关S4/S11/S12用户面IP地址和TEID或者携带了无效的服务网关S4/S11/S12用户面IP地址和TEID；
（3）响应消息中没有携带缺省承载标识或者携带了无效的缺省承载标识；
（4）响应消息中携带了包含GTPv1的用户上下文的容器信元。
步骤5：新侧S4 SGSN或MME（移动管理网元）获知老移动管理网元是Gn/Gp SGSN后，选择SGW，并发送正确的建立会话请求消息给SGW；
步骤6：PGW更新下行用户面隧道和控制面隧道；
步骤7：SGW回复建立会话响应消息；
步骤8、9：新侧S4 SGSN或MME向HSS登记位置，并获取用户的签约数据，老侧Gn/Gp SGSN（老移动管理网元）取消位置登记；
步骤10、11：路由区域更新/跟踪区域更新完成和接受。
本实施例中，当新侧移动管理网元为S4 SGSN时，用户终端发起路由区域更新流程，为MME时，用户终端发起跟踪区域更新流程。
GTPv2的用户上下文包括移动性管理上下文和/或分组数据网络连接上下文（Packet Data Network Connection Context, PDN Connection Context），GTPv1的用户上下文包括移动性管理上下文和/或分组数据协议上下文（Packet Data Protocol Context, PDP Context）, GTPv1的用户上下文映射为GTPv2的用户上下文为：
将Gn/Gp SGSN下的上下文的服务质量（Quality of Service，QoS）映射为EPS网络的承载QoS；
将签约最大比特率（Maximum Bit Rate，MBR）映射为聚合MBR（Aggregate Maximum Bit Rate，AMBR）等，本实施例中不再一一列举。
所谓发送正确的建立会话请求消息给SGW是指：建立会话请求消息中携带AMBR信元，不携带缺省承载标识。
进一步的，如果新移动管理网元也是Gn/Gp SGSN和S4 SGSN合一的节点，服务用户终端的节点为S4 SGSN，当新移动管理网元在步骤3获知老移动管理网元为Gn/Gp SGSN后，为了保持GGSN节点形态不变，减少GGSN上上下文，QoS等的转换工作，新移动管理网元可以将S4 SGSN切换到Gn/Gp SGSN，由Gn/Gp SGSN来服务用户终端；则5～7步骤替换为：
步骤5-1：切换后的新移动管理网元Gn/Gp SGSN节点发送更新分组数据协议（Packet Data Protocol，PDP）上下文请求（Update PDP Context Request）消息给GGSN；
步骤6-1：GGSN回复更新PDP上下文响应消息（Update PDP Context Response）。
通过本实施例的方法，当用户终端在向新侧发起路由区域更新或跟踪区域更新流程，新侧S4 SGSN或MME节点（新移动管理网元）无法识别老侧Gn/Gp SGSN节点（老移动管理网元）时，老侧Gn/Gp SGSN节点收到GTPv2的上下文请求消息，确认无法处理后，则将用户上下文从GTPv1的用户上下文转换为GTPv2的用户上下文，或者将GTPv1的用户上下文携带在GTPv2的容器信元中，向新侧S4 SGSN或MME节点回复与上下文请求消息的协议版本一致的GTPv2的上下文响应消息，在回复的GTPv2的上下文响应消息中携带转换后的GTPv2的用户上下文或者携带包含GTPv1的用户上下文的容器信元，使新S4 SGSN或MME节点可根据收到的响应消息中的上下文，获知老移动管理网元服务用户终端的节点类型，进一步完成后续的路由区域更新或跟踪区域更新流程，节约网络中的信令开销，避免网络资源浪费。
实施例三
本实施例提供一种多代移动通信网络中移动性管理流程的处理方法，用于用户终端在多代移动通信网络中通信，在新移动管理网元的节点为Gn/Gp SGSN和S4 SGSN合一的节点、MME、S4 SGSN中的任一种，且当新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时服务用户终端的节点为S4 SGSN，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，老移动管理网元服务用户终端的节点为Gn/Gp SGSN的情况下，保证新移动管理网元完成移动性管理流程（包括附着流程或路由区域更新或者跟踪区域更新流程），该方法包括下述步骤：
下面针对移动性管理流程为附着流程时，对该方法进行说明，该方法包括下述步骤：
老移动管理网元接收新移动管理网元（S4 SGSN或MME节点，为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN）发送的GTPv2的身份请求消息；
若老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，服务用户终端的为Gn/Gp SGSN, 则老移动管理网元发送与身份请求信息的协议版本一致的响应消息作为通知消息通知新移动管理网元（S4 SGSN或MME节点）该老移动管理网元服务用户终端的节点采用的协议版本为GTPv1，或通知服务用户终端的节点类型为Gn/Gp SGSN；
新移动管理网元（S4 SGSN或MME节点）收到通知消息后，将与S4 SGSN节点之间的S16或S3接口转换为与Gn/Gp SGSN节点之间的Gn接口，降低版本采用GTPv1发送GTPv1的身份请求消息，与老移动管理网元进行交互，获取用户身份标识及移动性管理上下文，完成后续的附着流程。
上述方法流程中，进一步也可以采用与身份请求信息的协议版本不一致的响应消息作为回复的通知消息，如针对GTPv2的身份请求信息，可以回复GTPv1的响应消息作为回复的响应消息；
下面结合图5对上述方法作具体说明，图5所示为EPS网络内的附着流程，老侧接入网为UTRAN/GERAN的3GPP接入，分别对应的无线接入节点为RNC/BSS，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点；新侧接入网为GERAN/UTRAN/E-UTRAN的3GPP接入，分别对应为BSS/RNC/eNodeB，新移动管理网元可以为S4 SGSN或MME（为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN），服务网关可以为SGW，数据网关可以为PGW，HSS负责归属地用户签约信息的管理和维护。
图5中的附着流程具体包括下述步骤：
步骤1：用户终端发起附着流程，发送附着请求消息，该消息经过新侧接入网发送给新移动管理网元S4 SGSN或MME；
步骤2：新移动管理网元S 4 SGSN或者MME根据收到的附着请求消息中的老侧的位置信息找到老侧接入网中服务用户终端的老移动管理网元，新移动管理网元S4 SGSN或MME因为不知道老移动管理网元服务用户终端的是Gn/Gp SGSN还是S4 SGSN，发送GTPv2的身份请求消息给老移动管理网元；
步骤3：老移动管理网元是Gn/Gp SGSN和S4 SGSN合一的节点，用户在老侧时，该老移动管理网元服务用户终端的是Gn/Gp SGSN；SGSN合一节点的老移动管理网元收到GTPv2的身份请求消息后，根据该请求消息中的用户临时标识发现服务用户终端的是Gn/Gp SGSN，而Gn/Gp SGSN与S4 SGSN或MME之间的Gn接口为GTPv1的接口，不支持GTPv2协议。老移动管理网元SGSN回复响应消息通知新移动管理网元S4 SGSN或MME，该老移动管理网元采用的GTP协议版本，或者服务用户终端的节点类型：老侧Gn/Gp SGSN节点通过GTPv2的消息作为通知消息通知S4 SGSN或MME 服务用户终端节点类型支持的版本类型为GTPv1，或者老移动管理网元通过GTPv1或者GTPv2的响应消息通知新移动管理网元S4 SGSN或MME服务用户终端的节点类型为Gn/Gp SGSN；该步骤中，针对GTPv2的身份请求消息，老侧Gn/Gp SGSN节点也可用GTPv1的消息作为回复的通知消息。
进一步的，回复的响应消息中可以携带信元表示老移动管理网元支持的协议为GTPv1协议，或者携带信元表示老移动管理网元的节点类型为Gn/Gp SGSN。（所回复的响应消息可以是现有的身份响应消息、版本不支持消息，或者是新增的消息等，不对该响应消息的类型加以限制）；
步骤4：新移动管理网元S4 SGSN或MME收到老移动管理网元的通知GTP协议版本的响应消息，或者通知节点类型的响应消息后，获知老移动管理网元支持GTPv1协议，或者获知老移动管理网元为Gn/Gp SGSN节点；则新移动管理网元S4 SGSN或MME将S16或S3接口转换为Gn接口，发送GTPv1的身份请求消息给老移动管理网元；
进一步的，若老移动管理网元Gn/Gp SGSN的IP地址与S4 SGSN的IP地址不同，新移动管理网元S4 SGSN或MME将身份请求消息中的目的IP地址改为Gn/Gp SGSN的IP地址再发送请求消息；
步骤5：老侧Gn/Gp SGSN（老移动管理网元）回复GTPv1的身份响应消息；
步骤6：认证/安全过程，该过程可选；
步骤7，8：新侧S4 SGSN或MME（新移动管理网元）向HSS登记位置，并获取用户的签约数据，老侧Gn/Gp SGSN取消位置登记；
步骤9：MME，SGW和PGW的会话建立过程，建立缺省承载，该步骤只在E-UTRAN接入时执行；
步骤10，11：附着接受和完成；
步骤12：承载更新过程，SGW更新下行用户面隧道信息，该步骤只在E-UTRAN接入时执行。
进一步的，本实施例中，如果新移动管理网元也是S4 SGSN和Gn/Gp SGSN合一的节点，且服务用户终端的节点为S4 SGSN，当新移动管理网元在步骤3获知老移动管理网元为Gn/Gp SGSN后，为了保持GGSN节点形态不变，减少GGSN上上下文，QoS等的转换工作，新移动管理网元可以将S4 SGSN切换到Gn/Gp SGSN，由Gn/Gp SGSN来服务用户终端。
通过本实施例的方法，使用户终端在向新侧发起附着流程，新侧S4 SGSN或MME节点（新移动管理网元）无法识别老侧Gn/Gp SGSN节点（老移动管理网元）时，老侧Gn/Gp SGSN节点收到GTPv2的身份请求消息后，确认无法处理后，则通过回复与身份请求消息的协议一致的GTPv2的响应消息作为通知消息，通知新侧S4 SGSN或MME节点，使得新移动管理网元可以与老移动管理网元建立正确交互，获取用户身份标识，及用户上下文，完成后续的附着流程，避免了附着流程中增加网络的信令开销，节省了网络资源浪费。
实施例四
本实施例提供一种多代移动通信网络中移动性管理流程的处理方法，该方法适用于用户终端在切换至新移动管理网络接受服务时，发起跟踪区域更新或路由区域更新流程，该方法具体包括下述步骤：
老移动管理网元接收新移动管理网元（S4 SGSN或MME节点，为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN）发送的GTPv2的上下文请求消息；
若老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，该老移动管理网元服务用户终端的节点为Gn/Gp SGSN，Gn/Gp SGSN无法处理GTPv2的上下文请求消息，则老移动管理网元发送响应消息作为通知消息通知新移动管理网元（S4 SGSN或MME节点）该老移动管理网元服务用户终端的节点类型采用的协议版本为GTPv1，或通知服务用户终端的节点类型为Gn/Gp SGSN；
进一步的，回复的响应消息中可以携带信元表示老移动管理网元支持的协议为GTPv1协议，或者携带信元表示老移动管理网元的节点类型为Gn/Gp SGSN。其中，所回复的响应消息可以是现有的上下文响应消息、版本不支持消息，或者是新增的消息等，不对该响应消息的类型加以限制。
新移动管理网元（新侧S4 SGSN或MME节点）收到通知消息后，将与S4 SGSN节点之间的S16或S3接口转换为与Gn/Gp SGSN节点之间的Gn接口，降低版本采用GTPv1发送GTPv1的SGSN上下文请求消息，与老移动管理网元进行交互，获取用户上下文，完成后续的跟踪区域更新或路由区域更新流程，使用户终端切换至新移动管理网元接受服务。该步骤中，若老侧Gn/Gp SGSN的IP地址与S4 SGSN的IP地址不同，新侧S4 SGSN或MME将SGSN上下文请求消息中的目的IP地址改为老侧Gn/Gp SGSN的IP地址后再发送请求消息。
下面结合图6对上述方法作具体说明，图6所示为EPS网络内的跟踪区域更新或路由区域更新流程，图中老侧接入网为UTRAN/GERAN的3GPP接入，分别对应的无线接入节点为RNC/BSS，老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点；新侧接入网为GERAN/UTRAN/E-UTRAN的3GPP接入，分别对应为BSS/RNC/eNodeB，新移动管理网元可以为S4 SGSN或MME（为S4 SGSN节点时，可以是Gn/Gp SGSN和S4 SGSN合一的节点，且服务用户终端的节点为S4 SGSN），服务网关可以为SGW，数据网关可以为PGW，HSS负责归属地用户签约信息的管理和维护。
图6中的路由区域更新或跟踪区域更新流程具体步骤包括：
步骤1：用户终端发送路由区域更新或跟踪区域更新请求消息，该消息经过新侧接入网发送给新移动管理网元S4 SGSN或MME；
步骤2：新侧S4 SGSN或MME（新移动管理网元）根据收到的路由区域更新或跟踪区域更新请求消息中的老侧位置信息找到老侧接入网中服务用户终端的老移动管理网元，新侧S4 SGSN或MME（新移动管理网元）因为不知道老移动管理网元服务用户终端的是Gn/Gp SGSN还是S4 SGSN，发送GTPv2的上下文请求消息给老移动管理网元；
步骤3：老移动管理网元是Gn/Gp SGSN和S4 SGSN合一的节点，用户在老侧时，服务用户终端的是Gn/Gp SGSN； SGSN合一节点的老移动管理网元收到GTPv2的上下文请求消息后，根据请求消息中的用户临时标识发现服务用户终端的是Gn/Gp SGSN，而Gn/Gp SGSN和S4 SGSN或MME之间的Gn接口为GTPv1的接口，不支持GTPv2。老侧Gn/Gp SGSN（老移动管理网元）回复响应消息作为通知消息通知新侧S4 SGSN或MME当前采用的GTP协议版本，或者服务用户终端的节点类型：老移动管理网元通过回复GTPv2的响应消息通知S4 SGSN或MME当前的协议版本为GTPv1，或者老移动管理网元通过回复GTPv2的响应消息通知S4 SGSN或MME老移动管理网元服务用户终端的节点类型为Gn/Gp SGSN；该步骤中，也可以回复GTPv1的响应消息作为通知消息，通知新侧S4 SGSN或MME，老移动管理网元当前的协议版本为GTPv1S4 SGSN或MME当前的协议版本为GTPv1，或者服务用户终端的节点类型为Gn/Gp SGSN。
进一步的，回复的响应消息中可以携带信元表示GTPv1协议，或者携带信元表示Gn/Gp SGSN的节点类型；所回复的响应消息可以是现有的上下文响应消息、版本不支持消息，或者是新增的消息等，不以限制该响应消息的类型；
步骤4：新侧S4 SGSN或MME（新移动管理网元）收到老移动管理网元GTP协议版本的通知消息，或者节点类型的通知消息后，获知老移动管理网元支持GTPv1，或者获知老移动管理网元为Gn/Gp SGSN，则新侧S4 SGSN或MME将S16或S3接口转换为Gn接口，发送GTPv1的SGSN上下文请求消息给老移动管理网元；
进一步的，如果老侧Gn/Gp SGSN（老移动管理网元）的IP地址与S4 SGSN的IP地址不同，新侧S4 SGSN或MME将SGSN上下文请求消息中的目的IP地址改为Gn/Gp SGSN的IP地址后再发送请求消息；
步骤5：老侧SGSN回复GTPv1的SGSN上下文响应消息，消息中携带用户终端的上下文；
步骤6：新侧S4 SGSN或MME回复SGSN上下文确认消息；
步骤7：新侧S4 SGSN或MME选择SGW，并与SGW之间建立控制面隧道；
步骤8：PGW更新下行用户面隧道和控制面隧道；
步骤9：SGW回复会话建立响应消息；
步骤10、11：新侧S4 SGSN或MME向HSS登记位置，并获取用户的签约数据，老侧Gn/Gp SGSN取消位置登记；
步骤12、13：路由区域更新/跟踪区域更新完成和接受。
本实施例中，当新侧移动管理网元为S4 SGSN时，用户终端发起路由区域更新流程，为MME时，用户终端发起跟踪区域更新流程。
用户上下文包括移动性管理上下文和/或PDP上下文。
进一步的，本实施例中，如果新移动管理网元也是Gn/Gp SGSN和S4 SGSN合一的节点，当新移动管理网元在步骤3获知老移动管理网元为Gn/Gp SGSN后，为了保持GGSN节点形态不变，减少GGSN上上下文，QoS等的转换工作，新移动管理网元可以将S4 SGSN切换到Gn/Gp SGSN，由Gn/Gp SGSN来服务用户终端。上述步骤7～9步骤则可替换为：
步骤7-1：Gn/Gp SGSN发送更新PDP上下文请求消息给GGSN；
步骤8-1：GGSN回复更新PDP上下文响应消息。
通过本实施例的方法，使用户终端在向新移动管理网元发起跟踪区域更新或路由区域更新流程，新侧S4 SGSN或MME节点（新移动管理网元）无法识别老侧Gn/Gp SGSN节点（老移动管理网元）时，老侧Gn/Gp SGSN节点收到GTPv2的上下文请求消息后，确认无法处理后，则通过通知消息通知新移动管理网元，使得新移动管理网元可确认老移动管理网元服务用户终端的节点类型及节点支持的协议版本，从而可与老移动管理网元建立正确交互，获取用户上下文，完成后续跟踪区域更新或路由区域更新流程，使用户终端切换至新移动管理网元接受服务，避免了跟踪区域更新或路由区域更新流程中增加网络的信令开销，节省了网络资源浪费。
实施例五
本实施例提供一种多代移动通信网络中移动性管理流程的处理系统，可用在由下一代移动通信网络和第二代、第三代移动通信网络构成的多代移动通信网络中，该系统可用于实现上述实施例中的方法，如图7所示，该系统包括：
新移动管理网元23、老移动管理网元21和老侧通信处理装置22；其中，老侧通信处理装置22与所述第二代、第三代移动通信网络中的老移动管理网元21通信连接；
所述新移动管理网元23，用于在接收用户终端发送的附着请求消息或路由区域更新请求消息或跟踪区域更新请求消息后，向所述老移动管理网元发送请求用户信息的请求消息；并根据所述老移动管理网元回复的响应消息完成移动性管理流程；
所述老移动管理网元21，用于根据所述请求信息向所述新移动管理网元23回复响应消息；
所述老侧通信处理装置22，用于对所述老移动管理网元21收到的由所述新移动管理网元23发送的所述请求消息进行判断，当所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为老移动管理网元回复给所述新移动管理网元的响应消息。
如图8所示，上述系统中的老侧通信处理装置22，具体包括：
接收单元221、请求消息处理单元222和发送单元223；
其中，所述接收单元221，用于接收所述老移动管理网元21收到的从所述新移动管理网元23发送的所述请求消息；
所述请求消息处理单元222，用于根据所述接收单元221收到的所述请求消息中的用户临时标识确定老移动管理网元服务用户终端的节点类型，并根据所述节点类型确定服务用户终端的节点支持的协议版本，当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为老移动管理网元21向新移动管理网元23回复的响应消息，并在所述响应消息中携带用户身份标识作为用户信息；
所述发送单元223，用于发送所述请求消息处理单元222确定的回复用响应消息。
上述老侧通信处理装置22中的请求消息处理单元222还包括：
转换处理子单元224，用于当所述请求消息的协议版本与所述服务用户终端的节点类型支持的协议版本不一致时，将上下文信息转换为与所述老移动管理网元请求消息的协议版本一致的上下文信息，并将转换后的上下文信息作为用户信息携带在回复的响应消息中。
该转换处理子单元224，针对附着流程发送的GTPv2的身份请求消息，可将GTPv1的移动性管理上下文转换为GTPv2的移动性管理上下文；针对路由区域更新或跟踪区域更新流程发送的上下文请求消息，可将GTPv1的用户上下文转换为GTPv2的用户上下文。
如图9所示，上述老侧通信处理装置22中的请求消息处理单元222还包括：
信元处理子单元225，用于当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，将上下文信息携带在容器信元中，并将所述容器信元携带在回复的响应消息中。
针对附着流程发送的GTPv2的身份请求消息，该信元处理子单元225可将GTPv1的移动性管理上下文携带在GTPv2的容器信元中，并将包括GTPv1的移动性管理上下文的所述容器信元携带在回复的响应消息中；针对路由区域更新或跟踪区域更新流程发送的上下文请求消息，该信元处理子单元225可将GTPv1的用户上下文携带在容器信元中，并将包括GTPv1的用户上下文的所述容器信元携带在回复的响应消息中；
通过本实施例的处理系统，在新移动管理网元针对用户终端的移动性管理流程中（包括：附着流程、跟踪区域更新或路由区域更新流程），新移动管理网元S4 SGSN或MME节点无法获知老移动管理网元为Gn/Gp SGSN节点时，老侧Gn/Gp SGSN节点（老移动管理网元）收到GTPv2的上下文请求消息，确认无法处理后，向新移动管理网元回复与请求消息协议版本一致的响应消息，并在回复的响应消息中携带用户信息，使新移动管理网元可根据用户信息，完成后续的移动性管理流程，节约了网络内的信令开销，避免了网络资源浪费。
实施例六
本实施例提供一种多代移动通信网络中移动性管理流程的处理系统，该处理系统可用在由下一代移动通信网络和第二代、第三代移动通信网络构成的多代移动通信网络中，该系统也用于实现上述实施例中的处理方法，与上述实施例五的系统结构基本相同，不同的是老侧通信处理装置的结构，如图10所示，该老侧通信处理装置包括：
接收单元2211、请求消息处理单元2212和通知消息发送单元2213；
所述接收单元2211，用于接收新侧通信处理装置24发送的所述请求消息；
所述请求消息处理单元2212，用于根据所述接收单元收到的所述请求消息中的用户临时标识确定老移动管理网元服务用户终端的节点类型，并根据所述节点类型确定服务用户终端的节点支持的协议版本，当所述请求消息的协议版本与所述服务用户终端的节点类型支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为回复的通知消息，所述通知消息用于通知所述新移动管理网元该老移动管理网元服务用户终端的节点类型和/或服务用户终端的节点支持的协议版本；
所述通知消息发送单元2213，用于发送回复给新侧通信处理装置的作为通知消息的响应消息。
上述老侧通信处理装置中的请求消息处理单元还包括：
指示信息设置子单元22121，用于在回复的通知消息中携带指示信息（如指示用的信元），通过指示信息指示老移动管理网元服务用户终端的节点类型和/或服务用户终端的节点支持的协议版本。
通过本实施例的处理系统，使新移动管理网元可以获知老移动管理网元的节点类型及节点所支持的协议版本，可以与老移动管理网元正确建立交互，完成后续的移动性管理流程，节约了网络内的信令开销，避免了网络资源浪费。
进一步的，如图11所示，在上述实施例五、六的处理系统中，还可以包括新侧通信处理装置24，该新侧通信处理装置24与下一代移动通信网络中的新移动管理网元23通信连接，用于对所述新移动管理网元23接收的响应消息进行判断，确定所述老移动管理网元服务用户终端的节点类型。
如图12所示，该新侧通信处理装置24具体包括：
接收单元241和判断单元242；
其中，所述接收单元241，用于接收由新移动管理网元23收到的从老移动管理网元21回复的响应消息；
所述判断单元242，对所述响应消息进行判断，确定所述老移动管理网元21服务用户终端的节点类型，进而确定老移动管理网元21的节点所支持的协议版本。
上述的新侧通信处理装置24还可以包括：
节点类型转换单元243，根据所述判断单元242的判断结果获知老移动管理网元服务用户终端的节点类型为Gn/Gp SGSN后，且所述新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，同时该新移动管理网元服务用户终端的节点为S4 SGSN，则将所述新移动管理网元服务用户终端的节点从S4 SGSN换为Gn/Gp SGSN，由Gn/Gp SGSN来服务用户终端。
通过该新侧通信处理装置24，在新移动管理网元确定老移动管理网元的节点类型及所支持的协议版本后，在新移动管理网元也为S4 SGSN和Gn/Gp SGSN合一的节点，且服务用户终端的节点为S4 SGSN，将新移动管理网元从S4 SGSN切换到Gn/Gp SGSN，由Gn/Gp SGSN来服务用户终端，可保持GGSN节点形态不变，减少GGSN上上下文，QoS等的转换工作。
综上所述，通过本发明实施例的方案，在老移动管理网元是Gn/Gp SGSN和S4 SGSN合一的节点，服务用户终端的是Gn/Gp SGSN时，新移动管理网元在不知道老移动管理网元节点类型且采用GTPv2协议与老移动管理网元进行通信时，可保证附着流程或跟踪区域更新或路由区域更新流程正常进行，节约了网络内的信令开销，避免了网络资源的浪费。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一可读取存储介质中，所述的存储介质可以为，如：ROM/RAM、磁碟、光盘等。
当然，以上所述是本发明的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也视为本发明的保护范围。

Claims (23)

  1. 一种多代移动通信网络中移动性管理流程的处理方法，新移动管理网元的节点为Gn/Gp SGSN和S4 SGSN合一的节点、MME、S4 SGSN中的任一种，当新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点时服务用户终端的节点为S4 SGSN；老移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，所述老移动管理网元服务用户终端的节点为Gn/Gp SGSN；其特征在于，包括：
    接收新移动管理网元发送的请求用户信息的请求消息；
    当收到的所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息，所述响应消息的协议版本与所述新移动管理网元发送的请求消息的版本一致；
    通过所述响应消息使所述新移动管理网元完成移动性管理流程。
  2. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述新移动管理网元发送的请求用户信息的请求消息为附着流程的GTPv2的身份请求消息，或路由区域更新或跟踪区域更新流程的GTPv2的上下文请求消息。
  3. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述当收到的所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息，所述响应消息的协议版本与所述新移动管理网元发送的请求消息的版本一致包括：
    当收到的所述请求消息为GTPv2的身份请求消息，老移动性管理网元服务用户终端的节点支持的协议版本为GTPv1，与所述GTPv2的身份请求消息的协议版本不一致，
    则向所述新移动管理网元回复GTPv2的身份响应消息，所述回复的GTPv2的身份响应消息中携带用户身份标识；
    或
    将GTPv1的移动性管理上下文转换为GTPv2的移动性管理上下文，向所述新移动管理网元回复GTPv2的身份响应消息，所述回复的GTPv2的身份响应消息中携带用户身份标识和转换后的GTPv2的移动性管理上下文；
    或
    将GTPv1的移动性管理上下文携带在容器信元中，向所述新移动管理网元回复GTPv2的身份响应消息，所述回复的GTPv2的身份响应消息中携带用户身份标识和包含GTPv1的移动性管理上下文的容器信元。
  4. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述当收到的所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息，所述响应消息的协议版本与所述新移动管理网元发送的请求消息的版本一致包括：
    当收到的所述请求消息为GTPv2的上下文请求消息，老移动性管理网元服务用户终端的节点支持的协议版本为GTPv1，与所述GTPv2的上下文请求消息的协议版本不一致，
    则将GTPv1的用户上下文转换为GTPv2的用户上下文，向所述新移动管理网元回复GTPv2的上下文响应消息，所述回复的GTPv2的上下文响应消息中携带转换后的GTPv2的用户上下文；
    或
    将GTPv1的用户上下文携带在容器信元中，向所述新移动管理网元回复GTPv2的上下文响应消息，所述回复的GTPv2的上下文响应消息中携带包含GTPv1的用户上下文的容器信元。
  5. 如权利要求4所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述方法还包括：
    在回复的所述GTPv2的上下文响应消息中携带一个承载的承载标识作为缺省承载标识；或在回复的所述GTPv2的上下文响应消息中携带无效的缺省承载标识。
  6. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    若回复的响应消息为GTPv2的上下文响应消息，且所述GTPv2的上下文响应消息中，没有携带或携带无效的SGW控制面IP地址和隧道标识或者携带无效的SGW控制面IP地址和隧道标识；
    则所述新移动管理网元根据所述GTPv2的上下文响应消息获知老移动管理网元服务用户终端的节点为Gn/Gp SGSN；
    所述新移动管理网元发送携带AMBR信元，不携带缺省承载标识的建立会话请求消息给服务网关建立会话，完成后续的移动性管理流程。
  7. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    若回复的响应消息为GTPv2的上下文响应消息，且所述GTPv2的上下文响应消息中，携带无效的SGW用户面IP地址和隧道标识或者没有携带无效的SGW用户面IP地址和隧道标识；
    则所述新移动管理网元根据所述GTPv2的上下文响应消息获知老移动管理网元服务用户终端的节点为Gn/Gp SGSN；
    所述新移动管理网元发送携带AMBR信元，不携带缺省承载标识的建立会话请求消息给服务网关建立会话，完成后续的移动性管理流程。
  8. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    若回复的响应消息为GTPv2的上下文响应消息，且所述GTPv2的上下文响应消息中，携带无效的缺省承载标识；或者没有携带缺省承载标识；
    则所述新移动管理网元根据所述GTPv2的上下文响应消息获知老移动管理网元服务用户终端的节点为Gn/Gp SGSN；
    所述新移动管理网元发送携带AMBR信元，不携带缺省承载标识的建立会话请求消息给服务网关建立会话，完成后续的移动性管理流程。
  9. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    若回复的响应消息为GTPv2的上下文响应消息，且所述GTPv2的上下文响应消息中，携带包含GTPv1的用户上下文的容器信元；
    则所述新移动管理网元根据所述GTPv2的上下文响应消息获知老移动管理网元服务用户终端的节点为Gn/Gp SGSN；
    所述新移动管理网元发送携带AMBR信元，不携带缺省承载标识的建立会话请求消息给服务网关建立会话，完成后续的移动性管理流程。
  10. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    根据所述响应消息使所述新移动管理网元确定老移动管理网元服务用户终端的节点类型为Gn/Gp SGSN后，且所述新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，服务用户终端的节点为S4 SGSN，则所述新移动管理网元将服务用户终端的节点从S4 SGSN切换为Gn/Gp SGSN；
    所述新移动管理网元以转换后的Gn/Gp SGSN节点完成后续的移动性管理流程。
  11. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述当收到的所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，向所述新移动管理网元回复响应消息，所述响应消息的协议版本与所述新移动管理网元发送的请求消息的版本一致包括：
    当收到的所述请求消息为GTPv2的身份请求消息或GTPv2的上下文请求消息，服务用户终端的节点支持的协议版本为GTPv1，与所述GTPv2的身份请求消息或GTPv2的上下文请求消息的协议版本不一致，向所述新移动管理网元回复GTPv2的响应消息作为通知消息，通知所述新移动管理网元该老移动管理网元服务用户终端的节点类型和/或服务用户终端的节点支持的协议版本。
  12. 如权利要求11所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述方法进一步包括：所述GTPv2的响应消息中通过携带节点类型信元指示该老移动管理网元服务用户终端的节点类型和/或携带节点支持协议版本指示服务用户终端的节点支持的协议版本。
  13. 如权利要求1所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述通过所述响应消息使所述新移动管理网元完成移动性管理流程包括：
    根据所述响应信息使所述新移动管理网元获知老移动管理网元服务用户终端的节点支持的协议版本，所述新移动管理网元采用与所述老移动管理网元服务用户终端的节点支持的协议版本一致的协议版本重新发送请求消息，并从对应该请求消息回复的响应消息中获取用户信息；
    利用所述用户信息使所述新移动管理网元完成后续的移动性管理流程。
  14. 如权利要求13所述的多代移动通信网络中移动性管理流程的处理方法，其特征在于，所述新移动管理网元采用与所述老移动管理网元服务用户终端的节点支持的协议版本一致的协议版本重新发送请求消息还包括：
    若所述老移动管理网元的节点S4 SGSN的IP地址与节点Gn/Gp SGSN的IP地址不同，所述新移动管理网元将发送的请求消息中的目的IP地址改为所述老移动管理网元的节点Gn/Gp SGSN的IP地址再发送。
  15. 一种多代移动通信网络中移动性管理流程的处理系统，用在由下一代移动通信网络和第二代、第三代移动通信网络构成的多代移动通信网络中，其特征在于，包括：
    新移动管理网元、老移动管理网元和老侧通信处理装置；其中，老侧通信处理装置与所述第二代、第三代移动通信网络中的老移动管理网元通信连接；
    所述新移动管理网元，用于在接收用户终端发送的附着请求消息或路由区域更新请求消息或跟踪区域更新请求消息后，向所述老移动管理网元发送请求用户信息的请求消息；并根据所述老移动管理网元回复的响应消息完成移动性管理流程；
    所述老移动管理网元，用于根据所述请求信息向所述新移动管理网元回复响应消息；
    所述老侧通信处理装置，用于对所述老移动管理网元收到的由所述新移动管理网元发送的所述请求消息进行判断，当所述请求消息的协议版本与老移动性管理网元服务用户终端的节点支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为老移动管理网元回复给所述新移动管理网元的响应消息。
  16. 如权利要求15所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述老侧通信处理装置包括：
    接收单元、请求消息处理单元和发送单元；
    所述接收单元，用于接收所述老移动管理网元收到的从所述新移动管理网元发送的所述请求消息；
    所述请求消息处理单元，用于根据所述接收单元收到的所述请求消息中的用户临时标识确定老移动管理网元服务用户终端的节点类型，并根据所述节点类型确定服务用户终端的节点支持的协议版本，当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为回复的响应消息，并在所述响应消息中携带用户身份标识作为用户信息；
    所述发送单元，用于发送所述请求消息处理单元确定的回复的响应消息。
  17. 如权利要求16所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述请求消息处理单元还包括：
    转换处理子单元，用于当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，将上下文信息转换为与所述请求消息的协议版本一致的上下文信息，并将转换后的上下文信息携带在回复的响应消息中。
  18. 如权利要求16所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述请求消息处理单元还包括：
    信元处理子单元，用于当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，将上下文信息携带在容器信元中，并将所述容器信元携带在回复的响应消息中。
  19. 如权利要求15所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述老侧通信处理装置包括：
    接收单元、请求消息处理单元和通知消息发送单元；
    所述接收单元，用于接收老移动管理网元收到的从所述新移动管理网元发送的所述请求消息；
    所述请求消息处理单元，用于根据所述接收单元收到的所述请求消息中的用户临时标识确定老移动管理网元服务用户终端的节点类型，并根据所述节点类型确定服务用户终端的节点支持的协议版本，当所述请求消息的协议版本与所述老移动管理网元服务用户终端的节点类型支持的协议版本不一致时，以与所述请求消息的协议版本一致的响应消息作为回复的通知消息，所述通知消息用于指示该老移动管理网元服务用户终端的节点类型和/或服务用户终端的节点支持的协议版本；
    所述通知消息发送单元，用于发送作为通知消息的所述响应消息。
  20. 如权利要求19所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述请求消息处理单元还包括：
    指示信息设置子单元，用于在回复的通知消息中携带指示信息，通过指示信息指示老移动管理网元服务用户终端的节点类型和/或服务用户终端的节点支持的协议版本。
  21. 如权利要求15所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述系统还包括：
    新侧通信处理装置，与下一代移动通信网络中的新移动管理网元通信连接；用于对所述新移动管理网元接收的响应消息进行判断，确定所述老移动管理网元服务用户终端的节点类型。
  22. 如权利要求21所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述新侧通信处理装置包括：
    接收单元和判断单元；
    所述接收单元，接收由新移动管理网元收到的从老移动管理网元回复的响应消息；
    所述判断单元，对所述响应消息进行判断，确定所述老移动管理网元服务用户终端的节点类型。
  23. 如权利要求22所述的多代移动通信网络中移动性管理流程的处理系统，其特征在于，所述新侧通信处理装置还包括：
    节点类型转换单元，用于在确定老移动管理网元服务用户终端的节点类型为Gn/Gp SGSN后，且所述新移动管理网元为Gn/Gp SGSN和S4 SGSN合一的节点，则将所述新移动管理网元服务用户终端的节点从S4 SGSN换为Gn/Gp SGSN。
PCT/CN2010/072382 2010-04-30 2010-04-30 多代移动通信网络中移动性管理流程的处理方法及系统 WO2011134171A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2010/072382 WO2011134171A1 (zh) 2010-04-30 2010-04-30 多代移动通信网络中移动性管理流程的处理方法及系统
CN201080001607.1A CN102318402B (zh) 2010-04-30 2010-04-30 多代移动通信网络中移动性管理流程的处理方法及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/072382 WO2011134171A1 (zh) 2010-04-30 2010-04-30 多代移动通信网络中移动性管理流程的处理方法及系统

Publications (1)

Publication Number Publication Date
WO2011134171A1 true WO2011134171A1 (zh) 2011-11-03

Family

ID=44860784

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/072382 WO2011134171A1 (zh) 2010-04-30 2010-04-30 多代移动通信网络中移动性管理流程的处理方法及系统

Country Status (2)

Country Link
CN (1) CN102318402B (zh)
WO (1) WO2011134171A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3506675A4 (en) * 2016-08-29 2020-01-22 ZTE Corporation METHOD AND APPARATUS FOR UPDATING A NETWORK SIDE POSITION AREA

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112492337B (zh) * 2020-11-26 2023-05-23 北京达佳互联信息技术有限公司 一种通信方法、通信装置、服务器和存储介质
CN114793187B (zh) * 2021-01-07 2024-03-01 大唐移动通信设备有限公司 L2tp消息的处理方法、装置及存储介质
CN115190173B (zh) * 2022-07-08 2024-02-23 迈普通信技术股份有限公司 一种网络通信方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030021256A1 (en) * 2001-07-09 2003-01-30 Samsung Electronics Co., Ltd. Packet data transmitting method in a CDMA mobile communication system
WO2008058124A2 (en) * 2006-11-06 2008-05-15 Velocent Systems Incorporated Method and apparatus regarding monitoring a streaming/conversational-class data session to detect when a mobile data flow has been dropped by a mobile network
CN101541056A (zh) * 2008-03-19 2009-09-23 大唐移动通信设备有限公司 一种用于不同gtp版本的系统间互操作的方法及装置
CN101635913A (zh) * 2008-07-25 2010-01-27 华为技术有限公司 Gprs隧道协议gtp用户面协议版本通知方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030021256A1 (en) * 2001-07-09 2003-01-30 Samsung Electronics Co., Ltd. Packet data transmitting method in a CDMA mobile communication system
WO2008058124A2 (en) * 2006-11-06 2008-05-15 Velocent Systems Incorporated Method and apparatus regarding monitoring a streaming/conversational-class data session to detect when a mobile data flow has been dropped by a mobile network
CN101541056A (zh) * 2008-03-19 2009-09-23 大唐移动通信设备有限公司 一种用于不同gtp版本的系统间互操作的方法及装置
CN101635913A (zh) * 2008-07-25 2010-01-27 华为技术有限公司 Gprs隧道协议gtp用户面协议版本通知方法和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3506675A4 (en) * 2016-08-29 2020-01-22 ZTE Corporation METHOD AND APPARATUS FOR UPDATING A NETWORK SIDE POSITION AREA

Also Published As

Publication number Publication date
CN102318402A (zh) 2012-01-11
CN102318402B (zh) 2014-12-03

Similar Documents

Publication Publication Date Title
WO2015167261A1 (en) Method and apparatus for transmitting a handover report and an rlf report
WO2014104705A1 (en) Method and system for supporting fast recovery of user equipment
WO2014046431A2 (en) Method for correctly establishing a local ip access service
WO2011142567A2 (en) Handover method supporting terminal mobility
WO2010126326A2 (en) Method and apparatus for supporting local ip access in a femto cell of a wireless communication system
WO2013051845A2 (ko) 이동 통신 시스템에서 사용자 단말의 접속 제어 방법 및 장치
WO2010021475A2 (en) Method and apparatus for performing switching in mobile communication system
WO2017030399A1 (en) Ue access method and apparatus
WO2010050758A2 (en) Data forwarding method and system for vertical handover
WO2011139096A2 (en) Method and apparatus for performing handover
WO2013133663A1 (ko) 무선 통신 시스템에서 서비스를 제어하기 위한 방법
WO2019078683A1 (ko) 다중 무선 접속 기술을 지원하는 무선 통신 시스템에서 데이터 송수신 방법 및 장치
WO2011147358A1 (zh) 机器类型通讯设备的业务控制方法和相关装置及系统
WO2015037947A1 (en) Method and device for setting up local breakout bearers
WO2013187728A1 (ko) 네트워크 쉐어링을 위한 공용 지역 이동 네트워크 선택 방법
WO2016003177A1 (ko) 저전력 단말의 통신 효과를 높이는 방법 및 장치
WO2013005992A2 (en) Method for avoiding handover failure
WO2014003455A1 (en) Method for determining access control
WO2012138110A2 (en) A method for guaranteeing establishment of local ip access correctly
WO2015012631A1 (en) Method for resolving security issues using nh and ncc pairs in mobile communication system
EP2559294A2 (en) Apparatus and method for a handover in mobile communication system
WO2013151332A1 (ko) 무선 통신 시스템에서 패킷 스위치 서비스 핸드오버 방법 및 장치
EP3420752A1 (en) Circuit switched fallback method and device
WO2014065636A1 (en) Mobile terminal preparation
WO2014069938A1 (en) Method of automatically adjusting mobility parameter

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080001607.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10850504

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10850504

Country of ref document: EP

Kind code of ref document: A1