WO2014090012A1

WO2014090012A1 - Internal switching method and device for high rate packet data serving gateway

Info

Publication number: WO2014090012A1
Application number: PCT/CN2013/084229
Authority: WO
Inventors: 洪芸芸; 罗永胜; 刘其锋; 贾树森
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-12-10
Filing date: 2013-09-25
Publication date: 2014-06-19
Also published as: CN103874141A

Abstract

Disclosed are an internal switching method and device for a high rate packet data serving gateway. The method comprises: a target high rate packet data serving gateway (T-HSGW) receiving a switching response message from a source high rate packet data serving gateway (S-HSGW), wherein the switching response message carries PDN unique identification information about each PDN connection between the S-HSGW and a packet data network (PDN); and the T-HSGW establishing a PDN connection between the T-HSGW and the PDN according to the PDN unique identification information. By means of the present invention, a T-HSGW can quickly locate to all of the PDN connections and reestablish a connection, thereby realizing Inter-HSGW switching under an MUPSAP scene.

Description

The present invention relates to the field of communications, and in particular to a method and an apparatus for internally switching a high-speed packet data serving gateway. BACKGROUND With the rapid development of mobile communication technologies and the increasing demand for high-speed data services, High Rate Packet Data (HRPD) networks are constantly evolving. In order to achieve interoperability with an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), the HRPD evolves into an Evolved High Rate Packet Data (eHRPD). 1 is a schematic diagram of an architecture of interoperability between eHRPD and E-UTRAN according to the related art. As shown in FIG. 1, an eHRPD network is composed of the following network elements: an evolved access network (evolved access network, e-referred to as eAN), and an evolution The Evolving Packet Control Function (ePCF) and the HRPD Serving Gateway (HSGW) are used. The E-UTRAN network consists of the following network elements: Mobility Management (Mobility Management) Entity, referred to as MME), Packet Data Network Gateway (PGW), Serving Gateway (SGW), E-TURAN base station, etc. The eHRPD has enhanced the functionality of the original HRPD wireless and packet core network. eHRPD also brings a series of new features, such as: Packet Data Network (PDN) support, bearer multiplexing, network-side Quality of Service (QoS), single access point name Multiple PDN Connections to A Single APN (MUPSAP for short). In the eHRPD network, the MUPSAP function allows a user equipment (User Equipment, UE for short) to establish multiple PDN connections to an Access Point Name (APN), and each PDN connection uses a PDN-ID (PDN Identifier). + User Context Identifier unique identifier; but in the current Inter-HSGW handover, the S-HSGW (Source-HSGW) sends the user's context information and the like to the T-HSGW (Target-HSGW) through the HAck message, and the context information carried therein In the HI Context Parameter TLVs, most of the Type Length Values (TLVs) contain only PDN-ID information, but no User Context Identifier or other information that uniquely identifies the PDN connection. Included in the TLV The PDN-ID information is used to distinguish between multiple PDN-connected users. However, in the MUPSAP scenario, multiple PDN connections cannot be effectively distinguished. As a result, the Inter-HSGW function is abnormal or impossible in the MUPSAP scenario. Referring to FIG. 2, FIG. 2 is a flowchart of an Inter-HSGW handover of an UE in an active state according to the related art. As shown in FIG. 2, in the current technology, the handover procedure of the Inter-HSGW in the active state of the UE includes the following steps: S201, the UE establishes a session by using the S-eAN/ePCF, the S-HSGW, and the P-GW, and the UE passes the S-eAN/ePCF,

The S-HSGW and the P-GW send and receive data packets.

5202, UE and/or S-eAN decides that the UE needs to be transferred to T-eAN.

5203: The S-eAN and the T-eAN use the A13 or A16 signaling to transmit the eHRPD wireless session context to the T-eAN, where the HI address on the S-HSGW is included. S204, the T-eAN/ePCF sends an All Registration Request (RRQ) indication switch to the T-HSGW, where

The HI address of the S-HSGW, the MSID of the UE, and the A10 connection set of the UE.

5205, the T-HSGW returns the All Registration Response (RRP) to the T-eAN/ePCF.

5206. The T-HSGW sends a handover initialization message to the S-HSGW, requesting a session context, a subscription context, and the like. S207: The S-HSGW returns a handover response HAck to the T-HSGW. The message includes a minimum effective information set of all established PDN connections, where most of the PDN connection-related TLVs only contain PDN-ID information; the H-HSGW receives After the message, all the PDN links are rebuilt.

S208, HSGW and 3GPP2 AAA perform HSGW reset processing, T-HSGW sends ULR to 3GPP2 AAA to indicate that the UE has replaced a new serving gateway, 3GPP2 AAA sends CLR to S-HSGW to indicate that it has been deleted, and S-HSGW returns to CLA In response, the last 3GPP2 AAA returns a ULA response to the T-HSGW indicating that the HSGW has successfully reset.

5209. The T-HSGW sends a PBU to the PGW, and updates the BCE (Binding Cache Entry) of the UE by using the address of the T-HSGW as a new MAG (Mobile Access Gateway).

5210, the PGW updates the BCE and returns a PBA response to the T-HSGW. S211. The PGW sends a BRI message to the S-HSGW to release the original PDN connection, and the S-HSGW returns the BRA response. 5212. The T-eAN/ePCF sends an All-RRQ message to the T-HSGW to indicate that the flow is activated.

5213, T-HSGW returns A11-RRP response to T-eAN/ePCF.

After the S110, after the T-HSGW finds that there is no data packet transmission on the H2 tunnel, the T-HSGW sends an HI message to the S-HSGW to close the H2 tunnel between the T-HSGW and the S-HSGW. .

5215, the S-HSGW returns a HAck response to the T-HSGW to confirm that the tunnel has been successfully deleted.

5216. The S-HSGW sends an All-Registration Update message to the S-eAN/ePCF requesting to delete the user resource on the S-HSGW.

5217, S-eAN/ePCF returns an Al 1 -Registration Ack message confirmation request to the S-HSGW. S218: The S-eAN/ePCF sends an All-RRQ (lifetime=0) to the S-HSGW to request to release the user.

S219: The S-HSGW returns an A11-RRP response confirmation request to the S-eAN/ePCF, and releases the user resource on the S-HSGW. It can be seen from the above process that if the PDN connection established on the S-HSGW is MUPSAP and the PDN-ID is the same, in the step S207, most of the PDN-related TLVs in the HAck message contain only PDN-ID information. For example: PCO Info TLVs, PDN Related Address Info TLVs PMIPv6 Info TLVs, etc., do not carry information that can identify a unique PDN link. This will not be able to distinguish which TDN connections the TLVs correspond to. At this point, these PDN links will fail to rebuild on the T-HSGW, eventually causing the Inter-HSGW handover to fail. For the related art, it is impossible to distinguish which PDN connection information is corresponding to these TLVs, which causes the PDN link to fail to reestablish on the T-HSGW, which ultimately leads to the problem that the Inter-HSGW handover fails. Currently, no effective solution has been proposed. SUMMARY OF THE INVENTION The present invention provides an internal handover method and apparatus for a high speed packet data serving gateway to at least solve the above problems. According to an aspect of the present invention, an internal handover method of a high speed packet data serving gateway is provided, comprising: a target high speed packet data serving gateway (T-HSGW) receiving a handover response from a source high speed packet data serving gateway (S-HSGW) Message, where the handover response message carries the S-HSGW and the packet data network PDN unique identification information of each PDN connection between the network (PDN); The T-HSGW establishes a PDN connection between the T-HSGW and the PDN according to the PDN unique identification information. Preferably, the handover response message carries PDN connection related information, where the PDN connection related information carries PDN unique identification information. Preferably, the PDN connection related information includes one of the following: a protocol configuration option information (PCO Info TLV), a packet data network related address information (PDN Related Address Info TLV), and a PMIPv6 Info TLV. Preferably, the PDN unique identification information includes: a PDN identifier and extended identifier information. Preferably, the extended identification information includes one of the following: a User Context Identifier, a PDN connection ID, a UE IPv4 Address, and a UE IPv6 Address. Preferably, the PDN unique identification information is: PDN Info extended TLV. Preferably, the handover scenario applicable to the method includes one of the following: a high-speed packet data service gateway in the MUPSAP scenario in the UE activation state, an Inter-HSGW, and an Inter-HSGW in the MUPSAP scenario in the UE sleep state. According to another aspect of the present invention, an internal switching apparatus for a high speed packet data serving gateway is provided, comprising: a receiving module configured to receive a handover response message from a source high speed packet data serving gateway (S-HSGW), wherein The response message carries PDN unique identification information of each PDN connection between the S-HSGW and the packet data network (PDN); and the reconstruction module is configured to establish a target high-speed packet data service gateway (T-HSGW) according to the PDN unique identification information. PDN connection with the PDN. Preferably, the handover response message carries PDN connection related information, where the PDN connection related information carries PDN unique identification information. Preferably, the PDN connection related information includes one of the following: a protocol configuration option information (PCO Info TLV), a packet data network related address information (PDN Related Address Info TLV), and a PMIPv6 Info TLV. Preferably, the PDN unique identification information includes: a PDN identifier and extended identifier information. Preferably, the extended identification information includes one of the following: a user context identifier (User Context Identifier),

PDN connection ID (PDN connection ID), terminal IPv4 address (UE IPv4 Address), terminal IPv6 address (UE IPv6 Address). Preferably, the PDN unique identification information is: PDN Info extended TLV. Preferably, the handover scenario applicable to the device includes one of the following: a high-speed packet data service gateway in the MUPSAP scenario in the UE activation state, an Inter-HSGW internal handover, and an Inter-HSGW in the MUPSAP scenario in the UE sleep state. With the present invention, the extended identification information is added by using the handover response message sent by the S-HSGW to the T-HSGW to achieve a unique identification of each PDN connection, and it is solved in the related art that it is impossible to distinguish which TDN connection these TLVs correspond to. The information causes the PDN link to fail to reestablish on the T-HSGW, which ultimately leads to the problem of Inter-HSGW handover failure. In this way, the T-HSGW can quickly locate all PDN connections and re-establish the connection, thus implementing the MUPSAP scenario. The effect of the Inter-HSGW switch. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic structural diagram of interoperation between eHRPD and E-UTRAN according to the related art; FIG. 2 is a flowchart of Inter-HSGW handover of an UE in an activated state according to the related art; FIG. 4 is a flow chart of Inter-HSGW handover of a UE in an activated state according to a preferred embodiment of the present invention; and FIG. 5 is a high speed according to an embodiment of the present invention. A block diagram of the internal switching device of the packet data service gateway. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. 3 is a flowchart of an internal handover method of a high speed packet data serving gateway according to an embodiment of the present invention. As shown in FIG. 3, the method mainly includes the following steps (step S302 - step S304): Step S302, the target high speed packet data serving gateway (T-HSGW) receives a handover response message from the source high speed packet data serving gateway (S-HSGW), where the handover response message carries the S-HSGW and the packet data network (PDN) PDN unique identification information between each PDN connection. Step S304, the T-HSGW establishes a PDN connection between the T-HSGW and the PDN according to the PDN unique identification information. In this embodiment, the handover response message carries the PDN connection related information, where the PDN connection related information carries the PDN unique identification information. In this embodiment, the PDN connection related information may include one of the following: PCO Info TLV PDN Related Address Info TLV, ΡΜΙΡνό Info TLV In this embodiment, the PDN unique identification information may include: a PDN identifier and extended identifier information. The extended identifier information includes one of the following: a user context identifier (User Context Identifier), a PDN connection identifier (PDN connection ID), and a UE IPv4 Address UE IPv6 Address. In this embodiment, the PDN unique identifier information may be: PDN Info extended TLV. It should be noted that, in this embodiment, the handover scenario that is applicable to the method includes: inter-HSGW of the high-speed packet data service gateway in the MUPSAP scenario in the UE activation state, and the following: the MUPSAP scenario in the UE sleep state. Under the Inter-HSGW. In a practical application, in the HAck message with the PDN connection reestablishment information sent by the S-HSGW to the T-HSGW, all TLVs related to the PDN connection carry information capable of uniquely identifying the PDN connection; for example, in the PCO Info TLV, PDN Related Address Info TLV, ΡΜΙΡνό Info TLV, etc., adds the extended User Context Identifier information, and carries the PDN-ID + User Context Identifier information to uniquely identify the PDN connection to which it belongs. After the T-HSGW receives the HAck message, it can determine which PDN connection the TLVs belong to according to the information that can be uniquely identified in the TLVs associated with the PDN connection, and the TDN connections can be re-established. Related information, such as PCO Info, PDN Related Address Info, and PMIPv6 Info, completes the reconstruction of all PDN connections, and ensures that the Inter-HSGW handover is successful in the MUPSAP scenario. In the HAck message sent by the S-HSGW to the T-HSGW, all TLVs related to the PDN connection, such as PCO Info TLV PDN Related Address Info TLV, PMIPv6 Info TLV, etc., may be added on the basis of existing PDN-IDs. Carry the PDN Connection ID to uniquely identify the PDN connection. In the HAck message sent by the S-HSGW to the T-HSGW, all the TLVs associated with the PDN connection may additionally carry the UE IPv4 Address, the UE IPv6 Address or other information to uniquely identify the PDN based on the existing PDN-ID. connection. In the HAck message sent by the S-HSGW to the T-HSGW, the PDN Info Extended TLV is used to carry all PDN connection information under the same PDN connection, such as PCO Info PDN Related Address Info, PMIPv6 Info, etc. by extending the PDN Info Extended TLV. Therefore, it can be confirmed which PDN connection the PDN connection information belongs to in the MUPSAP scenario. The internal handover (Inter-HSGW) method of the high speed packet data serving gateway provided by the above embodiment is further described below with reference to FIG. 4 and the preferred embodiment. 4 is a flowchart of Inter-HSGW handover of an UE in an active state according to a preferred embodiment of the present invention. As shown in FIG. 4, the flow includes the following steps (step S402-step S438): Step S402, the UE passes S-eAN /ePCF, S-HSGW, and P-GW establish a session, and the UE sends and receives data packets through S-eAN/ePCF, S-HSGW, and P-GW. Step S404, the UE and/or the S-eAN decide that the UE needs to be transferred to the T-eAN. Step S406, the EHRPD radio session context is transmitted to the T-eAN by using the A13 or A16 signaling between the S-eAN and the T-eAN, where the HI address on the S-HSGW is included. Step S408: The T-eAN/ePCF sends an All Registration Request (RRQ) indication handover to the T-HSGW, where the HI address of the S-HSGW, the MSID of the UE, and the A10 connection set of the UE are included. In step S410, the T-HSGW returns an Al1 registration response (RRP) to the T-eAN/ePCF. Step S412, the T-HSGW sends a handover initialization message to the S-HSGW, requesting information such as a session context, a subscription context, and the like. Step S414, the S-HSGW returns a handover HAck to the T-HSGW, where all the PDN connection related information carries information that can uniquely identify the PDN connection, for example, may be in PCO Info TLV, PDN Related Address Info TLV, ΡΜΙΡνό Info TLV, etc. The PDN-ID is added to the extended User Context Identifier information, and the PDN-ID + User Context Identifier information is carried to uniquely identify the PDN connection to which the PDN connection belongs.

After receiving the message, the H-HSGW starts to re-establish all PDN links according to the PDN connection unique identifier in which the PDN connection is correctly located. Step S416, the HSGW reset process is performed between the HSGW and the 3GPP2 AAA, the T-HSGW sends the ULR to the 3GPP2 AAA to instruct the UE to replace a new serving gateway, and the 3GPP2 AAA sends the CLR to the S-HSGW to indicate that it has been deleted, and the S-HSGW returns The CLA responds, and the last 3GPP2 AAA returns a ULA response to the T-HSGW indicating that the HSGW has successfully reset. Step S418, the T-HSGW sends a PBU to the PGW, and uses the address of the T-HSGW as the new MAG (Mobile).

Access Gateway) to update the BCE (Binding Cache Entry) of the UE. In step S420, the PGW updates the BCE and returns a PBA response to the T-HSGW. Step S422, the PGW sends a BRI message to the S-HSGW to release the original PDN connection, and the S-HSGW returns to the BRA response. Step S424, the T-eAN/ePCF sends an Al1-RRQ message to the T-HSGW to indicate that the flow has been activated. Step S426, the T-HSGW returns an A11-RRP response to the T-eAN/ePCF. Step S428, after S110, within a configurable time, once the T-HSGW finds that there is no data packet transmission on the H2 tunnel, the T-HSGW sends an HI message to the S-HSGW, and closes the H2 between the T-HSGW and the S-HSGW. tunnel. Step S430, the S-HSGW returns a HAck response to the T-HSGW to confirm that the tunnel has been successfully deleted. Step S432, the S-HSGW sends an All-Registration Update message to the S-eAN/ePCF, requesting to delete the user resource on the S-HSGW. In step S434, the S-eAN/ePCF returns an Al 1 -Registration Ack message confirmation request to the S-HSGW. Step S436, the S-eAN/ePCF sends an Al l-RRQ (lifetime=0) to the S-HSGW to request release of the user. Step S438, the S-HSGW returns an A11-RRP response confirmation request to the S-eAN/ePCF, and releases the user resource on the S-HSGW. As shown in the foregoing preferred embodiment, in the inter-Hsgw handover process in the MUPSAP scenario of the eHRP network, the information about the PDN connection can be uniquely identified in all the PDN connection related information in the HAck message, and the T-HSGW can quickly locate the information. The PDN connection corresponding to each PDN connection related information solves the problem that the Inter-HSGW cannot be performed in the MUPSAP scenario, and further corrects the reconstruction of all PDN connections. Obviously, the internal switching method of the high speed packet data service gateway provided by the above embodiment is adopted.

The handover response message sent by the S-HSGW to the T-HSGW adds the extended identification information to enable unique identification of each PDN connection, enabling the T-HSGW to quickly locate all PDN connections and re-establish the connection, thereby implementing the MUPSAP scenario. Inter-HSGW handover. 5 is a structural block diagram of an internal switching apparatus of a high speed packet data serving gateway according to an embodiment of the present invention. The apparatus is used to implement the internal switching method of the high speed packet data serving gateway provided by the foregoing embodiment. As shown in FIG. 5, the apparatus is as shown in FIG. The main components include: a receiving module 10 and a reconstruction module 20. The receiving module 10 is configured to receive a handover response message from a source high speed packet data serving gateway (S-HSGW), where the handover response message carries each PDN between the S-HSGW and the packet data network (PDN) The connected PDN unique identification information; the reconstruction module 20 is configured to establish a PDN connection between the target high speed packet data serving gateway (T-HSGW) and the PDN according to the PDN unique identification information. In this embodiment, the handover response message carries the PDN connection related information, where the PDN connection related information carries the PDN unique identification information. In this embodiment, the PDN connection related information may include one of the following: PCO Info TLV, PDN Related Address Info TLV ΡΜΙΡνό Info TLVo In this embodiment, the PDN unique identification information may include: a PDN identifier and extended identifier information. The extended identifier information includes one of the following: a user context identifier (User Context Identifier), a PDN connection identifier (PDN connection ID), and a UE IPv4 Address UE IPv6 Address o. In this embodiment, the PDN unique identifier information may be: PDN Info Extended TLV. It should be noted that the handover scenario applicable to the internal handover apparatus of the high-speed packet data service gateway provided by the embodiment may be that the high-speed packet data service gateway in the MUPSAP scenario in the UE activation state internally switches the Inter-HSGW, or may be the UE. Inter-HSGW in the MUPSAP scenario in the dormant state. With the internal switching apparatus of the high-speed packet data serving gateway provided by the foregoing embodiment, the extended identification information is added by the handover response message sent by the S-HSGW to the T-HSGW to enable unique identification of each PDN connection, and the T-HSGW can be enabled. Quickly locate all PDN connections and re-establish connections to implement Inter-HSGW switching in the MUPSAP scenario. From the above description, it can be seen that the present invention achieves the following technical effects: The extended identification information is added by using a handover response message sent by the S-HSGW to the T-HSGW to enable a unique identification of each PDN connection. In the related art, it is impossible to distinguish which TDN is associated with which PDN connection information, resulting in this The failure of the PDN link to rebuild on the T-HSGW eventually leads to the problem of Inter-HSGW handover failure, which enables the T-HSGW to quickly locate all PDN connections and re-establish the connection, thus implementing Inter- in the MUPSAP scenario. The effect of HSGW switching. Industrial Applicability The technical solution provided by the present invention adds the extended identification information to the handover response message sent by the S-HSGW to the T-HSGW to enable unique identification of each PDN connection. In this way, the T-HSGW can quickly locate All PDN connections are set and re-established to achieve Inter-HSGW switching in the MUPSAP scenario. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. An internal handover method for a high speed packet data service gateway, comprising:

The target high speed packet data serving gateway T-HSGW receives a handover response message from the source high speed packet data serving gateway S-HSGW, wherein the handover response message carries each of the S-HSGW and the packet data network PDN PDN unique identification information of the PDN connection;

The T-HSGW establishes a PDN connection between the T-HSGW and the PDN according to the PDN unique identification information.

The method according to claim 1, wherein the handover response message carries PDN connection related information, where the PDN connection related information carries the PDN unique identification information.

The method according to claim 2, wherein the PDN connection related information comprises one of the following: protocol configuration option information PCO Info TLV, packet data network related address information PDN Related Address Info TLV ΡΜΙΡνό Info TLVo

The method according to claim 2, wherein the PDN unique identification information comprises: a PDN identifier and extended identifier information.

5. The method according to claim 4, wherein the extended identification information comprises one of the following:

User context ID User Context

The PDN connection identifies the PDN connection ID, the terminal IPv4 address, the UE IPv4 Address, and the terminal IPv6 address, the UE IPv6 Address.

The method according to claim 2, wherein the PDN unique identification information is: PDN Info extended TLV.

The method according to any one of claims 1 to 6, wherein the switching scenario to which the method is applicable includes one of the following:

High-speed packet data service gateway internal switching in the MUPSAP scenario in the UE active state Inter-HSGW in the MUPSAP scenario in the sleep state of the Inter-HSGW UE.

8. An internal switching device for a high speed packet data service gateway, comprising: a receiving module, configured to receive a handover response message from the source high speed packet data serving gateway S-HSGW, where the handover response message carries a PDN of each PDN connection between the S-HSGW and the packet data network PDN Unique identification information;

And a reestablishing module, configured to establish a PDN connection between the target high speed packet data service gateway T-HSGW and the PDN according to the PDN unique identification information.

The apparatus according to claim 8, wherein the handover response message carries PDN connection related information, where the PDN connection related information carries the PDN unique identification information.

10. The apparatus according to claim 9, wherein the PDN connection related information comprises one of the following: protocol configuration option information PCO Info TLV, packet data network related address information PDN Related Address Info TLV ΡΜΙΡνό Info TLVo

The device according to claim 9, wherein the PDN unique identification information comprises: a PDN identifier and extended identifier information.

12. The apparatus according to claim 11, wherein the extended identification information comprises one of the following:

User context ID User Context

The device according to claim 9, wherein the PDN unique identification information is: PDN Info extended TLV.

14. Apparatus according to any one of claims 8 to 13 wherein the switching scenarios applicable to the apparatus comprise one of the following: