WO2017000694A1

WO2017000694A1 - Data forwarding method and device

Info

Publication number: WO2017000694A1
Application number: PCT/CN2016/082514
Authority: WO
Inventors: 卢飞; 朱进国
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-06-29
Filing date: 2016-05-18
Publication date: 2017-01-05
Also published as: CN106332189A; CN106332189B

Abstract

A data forwarding method, comprising: in a tracking area update procedure, transmitting, by a destination mobility management unit, to a base station a request message requesting to establish a forwarding channel used to forward data buffered at an original serving gateway (SGW) to the base station; and when receiving a response message returned by the base station and carrying base station information about the forwarding channel, transmitting, by the destination mobility management unit, the base station information about the forwarding channel to a related network element to establish the forwarding channel. The above method addresses the problems in which a base station cannot receive data buffered at an original SGW and the received data is disorganized in a tracking area update procedure.

Description

Method and device for implementing forwarding data

Technical field

The present application relates to, but is not limited to, the field of communication technologies, and in particular, to a method and an apparatus for implementing forwarding data.

Background technique

The 3rd Generation Partnership Project (3GPP) standardization working group is currently working on the Packet Switch Core (PS Core) and the Global Mobile Telecommunications System Radio Access Network ( The evolution of the Universal Mobile Telecommunication System Radio Access Network (UTRAN), the subject of this research is called System Architecture Evolution (SAE), which aims to make Evolved Packet Core (EPC) available. Higher transmission rate, resulting in shorter transmission delays, while optimizing packets, and supporting Evolved UTRAN (E-UTRAN), UTRAN, Wireless Local Area Network (WLAN) and others Mobility management between non-3GPP access networks.

The current SAE architecture is shown in Figure 1. It includes the following network elements: Evolved RAN (E-RAN), Packet Data Network (PDN), and evolved packets. E-Packet Core. The evolved packet network includes the following network element: Mobility Management Entity (MME). In the Global Mobile Telecommunications System (UMTS), the mobility management unit is SGSN (Serving GPRS Support Node, Serving GPRS). Supporting node); Serving Gateway (SGW); Packet Data Network Gateway (PDN Gateway, PGW for short); Policy and Charging Rules Function (PCRF); Home Subscriber Server (Home Subscriber Server, referred to as HSS).

In the related art, the user equipment (UE) may be in a power saving state (PSM). In this state, the MME cannot page to the UE, and the UE is also in an unreachable state. If the SGW receives the downlink data, it knows that the UE is in an unreachable state. In this state, the SGW will cache the data. When the UE moves to the new MME in the idle state, and the new MME selects a new SGW, the original SGW needs to forward the data in order to enable the UE to receive the cached data. FIG. 2 is a process for implementing forwarding data in a tracking area update (TAU) process in the related art, and the process includes the following steps:

In step 201, the UE sends a TAU request message to the eNodeB (evolved Node B, the evolved Node B), where the message includes a Globally Unique Temporary Identity (GUTI) of the user;

Step 202, the eNodeB selects the MME, and forwards the TAU request message to the newly selected destination MME.

Step 203: The destination MME obtains the original MME corresponding to the UE according to the GUTI carried in the TAU request, and sends a context request message to the original MME, where the context request message carries the original GUTI obtained in step 202;

Step 204: The original MME returns a context response message to the destination MME, where the message carries the Mobility Management (MM) context and the bearer context of the UE. If the downlink data is cached on the SGW, the original MME responds in the context. The message also needs to indicate that the data cache is to be transmitted;

Step 205: The destination MME re-selects a new SGW, and sends a setup session request message to the destination SGW, where the message carries the IP address of the MME (Internet Protocol) and the Tunnel Endpoint Identifier (TEID). ), the International Mobile Subscriber Identity (IMSI) of the UE, and the bearer context information of the UE;

Step 206: The destination SGW sends an update bearer request message to the PGW, where the message carries the control plane IP address and TEID of the SGW, the user plane IP address and the TEID of the downlink SGW of the S5 interface;

Step 207, the PGW returns an update bearer response message to the destination SGW; the PGW sends an end end marker to the original SGW;

Step 208: The destination SGW returns a session establishment response message to the destination MME, where the message carries the IP address and TEID of the control plane of the SGW, and the user plane IP address and TEID of the uplink SGW of the S1-U interface.

Step 209: The destination MME returns a TAU accept message to the UE, where the message carries a re-allocated GUTI and a tracking area identity (TAI) list. After receiving the new GUTI, the UE needs to return a TAU complete message to the MME. ;

Step 210: The destination MME sends a setup context request message to the eNodeB, where the message carries the user plane IP address and TEID of the uplink SGW of the S1-U interface.

Step 211: The eNodeB sends a setup context response message to the MME, where the message carries the user plane IP address and TEID of the downlink eNodeB of the S1-U interface.

Step 212: The destination MME sends an update bearer request message to the destination SGW, where the message carries the user plane IP address and TEID of the S1-U interface downlink eNodeB obtained in step 211.

Step 213: The destination SGW returns an update bearer response message to the destination MME.

Step 214, the destination MME selects the forwarding anchor SGW, and sends a forwarding tunnel request message to the forwarding anchor SGW, where the message carries the IMDI and the user plane IP address and TEID of the S1-U interface downlink eNodeB obtained in step 211;

The forwarding anchor SGW may be the same SGW as the destination SGW, or may be the same SGW as the destination SGW; in FIG. 2, the forwarding anchor SGW is the same SGW as the destination SGW;

Step 215: The forwarding anchor SGW returns a forwarding tunnel response message to the destination MME, where the message carries the forwarding IP address and TEID of the forwarding anchor point SGW.

In step 216, the destination MME returns a context confirmation message to the original MME. If the step 214 and the step 215 are performed, the context confirmation message carries the forwarding IP address and the TEID of the forwarding anchor SGW obtained in step 215; if step 214 and the step 215 is not executed, the context confirmation message carries the user plane IP address and TEID of the S1-U interface downlink eNodeB obtained in step 211;

Step 217, the original MME sends a bearer update request message to the original SGW, where the message carries the user plane IP address and TEID obtained in step 216;

If the step 214 and the step 215 are performed, the user plane IP address and the TEID carried in the bearer update request message are the forwarding IP address and the TEID of the forwarding anchor SGW; if the step 214 and the step 215 are not performed, the bearer update is performed. The user plane IP address and TEID carried in the request message are the user plane IP address and TEID of the downlink eNodeB of the S1-U interface;

Step 218: The original SGW returns a bearer update response message to the original MME.

Step 219: The original MME sends a release session request message to the original SGW; the original SGW releases all the information of the UE;

Step 220: The original SGW sends a release session response message to the original MME.

The downlink data buffered on the original SGW can be forwarded through the original SGW->eNodeB (as shown by the thick line in FIG. 2), or through the original SGW-> forwarding anchor SGW->eNodeB (as shown in Figure 2) Forwarded as indicated by the thick line.

From the above steps, it can be found that since the eNodeB does not know that the network side will establish a forwarding tunnel for it, if the filtering software such as a firewall is installed on the eNodeB, the data on the forwarding tunnel not established by the eNodeB may be discarded (that is, the eNodeB). It is possible to discard data forwarded from the original SGW or the forwarding anchor SGW). On the other hand, even if the eNodeB can receive data from the forwarding tunnel and data from the destination SGW, the data received from the two different senders may affect each other and cause out-of-order, causing the received data to be unresolved normally.

In response to the above problems, there is currently no solution.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a method and a device for implementing forwarding data, which can solve the problem that the base station does not receive the data buffered on the original serving gateway and the received data is out of order during the tracking area update process.

An embodiment of the present invention provides a method for implementing forwarding data, where the method includes:

During the tracking area update process, the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station; the forwarding tunnel is configured to forward data buffered on the original serving gateway to the base station;

After receiving the response message of the base station end information of the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.

Optionally, the implementation method further includes the following features:

The destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station, including:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting to establish a forwarding tunnel.

Optionally, the implementation method further includes the following features:

After receiving the response message of the base station end information of the forwarding tunnel that is returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel, including:

After receiving the initial context setup response message of the base station end information of the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.

Optionally, the implementation method further includes the following features:

Sending the base station information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel, including:

Transmitting the base station information of the forwarding tunnel to the original mobility management unit, where the original mobility management unit sends the base station information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the base station and the original serving gateway; or,

Sending the base station information of the forwarding tunnel to the anchor service gateway that forwards the data to establish a forwarding tunnel between the anchor service gateway and the base station, and sending the information of the anchor service gateway end of the forwarding tunnel to the original mobile The management unit sends, by the original mobility management unit, the anchor service gateway end information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the anchor service gateway and the original serving gateway.

Optionally, the implementation method further includes the following features:

The base station end information of the forwarding tunnel includes: base station end IP address information and tunnel end point identifier (TEID) information of the forwarding tunnel.

Optionally, the implementation method further includes the following features:

The base station includes: an evolved Node B; and the mobility management unit includes: a mobility management entity (MME).

During the tracking area update process, the destination service gateway obtains the first data cached on the original service gateway;

After the destination service gateway sends all the first data buffered on the original serving gateway to the base station, the second data acquired from the packet data network gateway is sent to the base station.

Optionally, the implementation method further includes the following features:

The destination service gateway obtains the first data cached on the original service gateway, including:

The destination service gateway receives the first data sent by the original service gateway, and after receiving the data end identifier, determines that all the first data cached on the original service gateway is received.

Optionally, the implementation method further includes the following features:

After the destination service gateway sends the first data cached on the original serving gateway to the base station, the second data that is obtained from the packet data network gateway is sent to the base station, including:

If the destination service gateway does not detect the data end identifier in the first data cached on the received original service gateway, it is determined that the first data is not received, and the destination service gateway buffers the second data from the packet data network gateway.

Optionally, the implementation method further includes the following features:

The data end identifier is created by the packet data network gateway or created by the original service gateway.

Optionally, the implementation method further includes the following features:

The destination service gateway obtains the first data from the original service gateway as a data forwarding anchor service gateway;

The destination mobility management unit selects the destination serving gateway as the data forwarding anchor service gateway after learning that the base station does not support the establishment of the forwarding tunnel. The forwarding tunnel is used to forward the data buffered on the original serving gateway to the base station.

Optionally, the implementation method further includes the following features:

The destination mobility management unit learns that the base station does not support establishing a forwarding tunnel, including:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting to establish a forwarding tunnel;

After receiving the initial context setup response message returned by the base station, if the initial context setup response message does not include the base station end information of the forwarding tunnel, the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel.

Optionally, the implementation method further includes the following features:

An embodiment of the present invention provides an apparatus for implementing forwarding data, which is applied to a mobility management unit, and includes:

The requesting module is configured to: in the tracking area update process, send, as the destination mobility management unit, a request message for requesting to establish a forwarding tunnel to the base station; where the forwarding tunnel is used to forward the data cached on the original serving gateway to the Base station

The response receiving and processing module is configured to: after receiving the response message of the base station end information carrying the forwarding tunnel returned by the base station, the destination mobile management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the Said forwarding tunnel.

Optionally, the implementation device further includes the following features:

The request module is set to:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting establishment of a forwarding tunnel.

Optionally, the implementation device further includes the following features:

The response receiving and processing module is set to:

Optionally, the implementation device further includes the following features:

The response receiving and processing module is configured to send the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel by:

Transmitting the base station end information of the forwarding tunnel to the original mobility management unit, by the original mobile tube The processing unit sends the base station end information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the base station and the original serving gateway; or

Optionally, the implementation device further includes the following features:

An embodiment of the present invention provides an apparatus for implementing forwarding data, which is applied to a service gateway, and includes:

The data receiving module is configured to: obtain, as the destination service gateway, the first data cached on the original serving gateway during the tracking area update process;

The data sending module is configured to: after the first data buffered on the original serving gateway is sent to the base station as the destination serving gateway, send the second data acquired from the packet data network gateway to the base station.

Optionally, the implementation device further includes the following features:

The data receiving module is configured to: receive, as the destination service gateway, the first data sent by the original serving gateway, and after receiving the data end identifier, determine that all the first data buffered on the original serving gateway is received.

Optionally, the implementation device further includes the following features:

The data sending module is configured to: if the destination service gateway does not detect the data end identifier in the first data cached on the received original serving gateway, determine that the first data is not received, and serve as a destination service gateway cache. Second data from the packet data network gateway.

Optionally, the implementation device further includes the following features:

The data receiving module is set to:

And the destination service gateway obtains the first data from the original service gateway as a data forwarding anchor service gateway;

Optionally, the implementation device further includes the following features:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting establishment of a forwarding tunnel;

Optionally, the implementation device further includes the following features:

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, and when the computer executable instructions are executed, implementing the foregoing method for implementing forwarding data applied to the mobility management unit side.

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, and when the computer executable instructions are executed, implementing the foregoing method for implementing forwarding data applied to a service gateway side.

Compared with the related art, a method and an apparatus for implementing forwarding data provided by an embodiment of the present invention, in a tracking area update process, a destination mobility management unit sends a request to establish a forwarding tunnel to a base station. The request message, after receiving the response message of the base station information carrying the forwarding tunnel returned by the base station, transmitting the base station information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel, and the base station can Received data cached on the original service gateway. In addition, if the base station does not support the establishment of the forwarding tunnel, after the destination serving gateway obtains the first data buffered on the original serving gateway as the data forwarding anchor service gateway, after transmitting the first data to the base station, the packet data will be transmitted from the packet data. The second data acquired by the network gateway is sent to the base station, so that the problem that the base station receives the data out of order during the tracking area update process can be solved.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic structural diagram of an evolved packet network system in related art;

2 is a signaling interaction diagram of data forwarding in a tracking area update process in the related art;

FIG. 3 is a flowchart of a method for implementing forwarding data according to an embodiment of the present invention;

4 is a flowchart of another method for implementing forwarding data according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an apparatus for implementing forwarding data according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of another apparatus for implementing forwarding data according to an embodiment of the present invention;

7 is a signaling interaction diagram of data forwarding in Embodiment 1 of the present invention;

FIG. 8 is a signaling interaction diagram of data forwarding in Embodiment 2 of the present invention.

Embodiments of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

As shown in FIG. 3, an embodiment of the present invention provides a method for implementing forwarding data, where the method includes the following steps:

Step S10, in the tracking area update process, the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station; the forwarding tunnel is used to forward data buffered on the original serving gateway to the base station;

Step S20: After receiving the response message of the base station end information carrying the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.

The method may also include the following features:

Optionally, the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station, including:

Optionally, after receiving the response message of the base station end information of the forwarding tunnel that is returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel, including:

After receiving the initial context setup response message carrying the base station end information of the forwarding tunnel, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.

Optionally, the base station end information of the forwarding tunnel is sent to the relevant network element to establish the forwarding tunnel, including:

Transmitting the base station end information of the forwarding tunnel to the original mobility management unit, and then sending, by the original mobility management unit, the base station end information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the base station and the original serving gateway. ;or,

Sending the base station information of the forwarding tunnel to the anchor service gateway that forwards the data to establish a forwarding tunnel between the anchor service gateway and the base station, and sending the information of the anchor service gateway end of the forwarding tunnel to the original mobile And the management unit further sends, by the original mobility management unit, the anchor service gateway information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the anchor service gateway and the original serving gateway.

Optionally, the base station end information of the forwarding tunnel includes: base station end IP address information and tunnel end point identifier (TEID) information of the forwarding tunnel.

Optionally, the anchor service gateway end information of the forwarding tunnel includes: an anchor point service gateway end IP address information and a tunnel end point identifier (TEID) information of the forwarding tunnel.

Optionally, the base station includes: an evolved Node B (eNodeB); the mobility management unit includes: a mobility management entity (MME);

In the 3G network system, the base station includes: a UMRAN (UMTS Terrestrial Radio Access Network); the mobility management unit includes: an SGSN (Serving GPRS Support Node).

As shown in FIG. 4, an embodiment of the present invention provides a method for implementing forwarding data, where the method includes the following steps:

Step S30, in the tracking area update process, the destination service gateway acquires the first data cached on the original service gateway;

Step S40: After the destination service gateway sends all the first data buffered on the original serving gateway to the base station, the second data acquired from the packet data network gateway is sent to the base station.

The method may also include the following features:

Optionally, the destination service gateway obtains the first data cached on the original service gateway, including:

Optionally, the destination service gateway sends the first data that is cached on the original serving gateway to the base station, and then sends the second data that is obtained by the packet data network gateway to the base station, including:

Optionally, the data end identifier is created by a packet data network gateway (PGW) or created by the original service gateway.

The destination mobility management unit selects the destination service gateway as the data forwarding anchor service gateway after learning that the base station does not support the establishment of the forwarding tunnel; the forwarding tunnel is used to slow down the original service gateway. The stored data is forwarded to the base station.

Optionally, the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel, and includes:

Optionally, the destination mobility management unit may also learn, by using local configuration information, that the base station does not support establishing a forwarding tunnel.

As shown in FIG. 5, an embodiment of the present invention provides an apparatus for implementing forwarding data, which is applied to a mobility management unit, and includes:

The device may also include the following features:

Optionally, the requesting module is configured to: send, as the destination mobility management unit, an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting to establish a forwarding tunnel.

Optionally, the response receiving and processing module is configured to: after receiving the initial context setup response message of the base station end information carrying the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel The relevant network element is given to establish the forwarding tunnel.

Optionally, the response receiving and processing module is configured to send the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel by:

Optionally, the base station includes: an evolved Node B; the mobility management unit includes: a mobility management entity (MME);

As shown in FIG. 6, an embodiment of the present invention provides an apparatus for implementing forwarding data, which is applied to a service gateway, and includes:

a data receiving module, configured to acquire, as a destination service gateway, the first data cached on the original serving gateway during the tracking area update process;

The data sending module is configured to: after the first data buffered on the original serving gateway is sent to the base station as the destination service gateway, send the second data obtained from the packet data network gateway to Base station.

The device may also include the following features:

Optionally, the data receiving module is set to:

The destination service gateway receives the first data sent by the original service gateway, and after receiving the data end identifier, determines that all the first data buffered on the original service gateway is received.

Optionally, the data sending module is set to:

Optionally, the data end identifier is created by a packet data network gateway or created by the original service gateway.

Optionally, the data receiving module is configured to: obtain the first data from the original serving gateway by using the destination serving gateway as a data forwarding anchor service gateway;

Optionally, the base station includes: an evolved Node B; and the mobility management unit includes: a mobility management entity (MME).

The solution of the embodiment of the present application is described below by using specific embodiments.

Embodiment 1

The embodiment of the present invention provides a method for implementing forwarding data. In this embodiment, the eNodeB supports establishing a forwarding tunnel. As shown in FIG. 7, the method includes the following steps:

Step 701: The UE sends a TAU request message to the eNodeB, where the message includes a Globally Unique Temporary Identity (GUTI) of the user.

Step 702, the eNodeB selects the MME, and forwards the TAU request message to the newly selected destination MME.

Step 703: The destination MME obtains the original MME corresponding to the UE according to the GUTI carried in the TAU request, and sends a context request message to the original MME, where the context request message carries the original GUTI obtained in step 702.

Step 704: The original MME returns a context response message to the destination MME, where the message carries the Mobility Management (MM) context and the bearer context of the UE. If the downlink data is cached on the SGW, the original MME responds in the context. The message also needs to indicate that the data cache is to be transmitted;

Step 705: The destination MME reselects the new SGW, and sends a setup session request message to the destination SGW, where the message carries the IP address of the destination MME and the Tunnel Endpoint Identifier (TEID). International Mobile Subscriber Identity (IMSI) of the UE, bearer context information of the UE;

Step 706: The destination SGW sends an update bearer request message to the PGW, where the message carries the control plane IP address and TEID of the destination SGW, and the user plane IP address and TEID of the downlink SGW of the S5 interface.

Step 707, the PGW returns an update bearer response message to the destination SGW; the PGW sends an end end marker to the original SGW;

Step 708: The destination SGW returns a session establishment response message to the destination MME, where the message carries the IP address and TEID of the control plane of the destination SGW, and the user plane IP address and TEID of the uplink SGW of the S1-U interface.

Step 709: The destination MME returns a TAU accept message to the UE, where the message carries a re-submission After the GUTI and the tracking area identity (TAI) list are configured, the UE needs to return a TAU completion message to the destination MME after receiving the new GUTI.

Step 710: The destination MME sends a setup context request message to the eNodeB, where the message carries the user plane IP address and the TEID of the uplink SGW of the S1-U interface. The message also carries a request for establishing a forwarding tunnel.

Step 711: The eNodeB sends a setup context response message to the destination MME, where the message carries the user plane IP address and the TEID of the S1-U interface downlink eNodeB. If the eNodeB supports the establishment of the forwarding tunnel in the TAU process, the eNodeB also returns in the response message. IP address and TEID of the eNodeB that forwards the tunnel;

Step 712: The destination MME sends an update bearer request message to the destination SGW, where the message carries the user plane IP address and TEID of the S1-U interface downlink eNodeB obtained in step 711. The destination SGW may also be notified in the bearer update request message: The eNodeB supports establishing a forwarding tunnel in the TAU process;

Step 713: The destination SGW returns an update bearer response message to the destination MME.

Step 714, the destination MME selects the forwarding anchor SGW, and sends a forwarding tunnel request message to the forwarding anchor SGW, where the message carries the IMSI and the IP address and TEID of the eNodeB of the forwarding tunnel obtained in step 711;

The forwarding anchor SGW may be a different SGW than the destination SGW, or may be the same SGW as the destination SGW; in FIG. 7, the forwarding anchor SGW is the same SGW as the destination SGW;

Step 715: The forwarding anchor SGW returns a forwarding tunnel response message to the destination MME, where the message carries the forwarding IP address and TEID of the anchor SGW.

Step 716: The destination MME returns a context acknowledgment message to the original MME, where the context acknowledgment message carries the forwarding IP address and TEID of the anchor SGW obtained in step 715; if the 714 and 715 are not performed, the MME returns the context to the original MME. The acknowledgment message carries the IP address and TEID of the eNodeB of the forwarding tunnel obtained in step 711;

Step 717: The original MME sends a bearer update request message to the original SGW, where the message carries the IP address and TEID of the forwarding tunnel obtained in step 716;

Step 718: The original SGW returns a bearer update response message to the original MME.

Step 719: The original MME sends a release session request message to the original SGW; the original SGW releases all the information of the UE;

Step 720: The original SGW sends a release session response message to the original MME.

The downlink data buffered on the original SGW can be forwarded through the original SGW->eNodeB (as shown by the thick line in FIG. 7), or through the original SGW-> forwarding anchor SGW->eNodeB (as shown in Figure 7). Forwarded as indicated by the thick line.

Optionally, after all the data buffered by the original SGW is completely forwarded, if the original SGW does not receive the End Marker sent by the PGW, the original SGW needs to add an end marker (End Marker) at the end of the buffered data transfer end, and the End marker may Help the eNodeB to rearrange the data.

Embodiment 2

The embodiment of the present invention provides a method for implementing forwarding data. In this embodiment, the eNodeB does not support establishing a forwarding tunnel. As shown in FIG. 8, the method includes the following steps:

Step 801: The UE sends a TAU request message to the eNodeB, where the message includes a Globally Unique Temporary Identity (GUTI) of the user.

Step 802, the eNodeB selects the MME, and forwards the TAU request message to the newly selected destination MME.

Step 803: The destination MME obtains the original MME corresponding to the UE according to the GUTI carried in the TAU request, and sends a context request message to the original MME, where the context request message carries the original GUTI obtained in step 802.

Step 804: The original MME returns a context response message to the destination MME, where the message carries the Mobility Management (MM) context and the bearer context of the UE. If the downlink data is cached on the SGW, the original MME responds in the context. The message also needs to indicate that the data cache is to be transmitted;

Step 805: The destination MME re-selects a new SGW, and sends a setup session request message to the destination SGW, where the message carries the IP address of the destination MME and the Tunnel Endpoint Identifier (TEID). International Mobile Subscriber Identity (IMSI) of the UE, bearer context information of the UE;

Step 806: The destination SGW sends an update bearer request message to the PGW, where the message carries the control plane IP address and TEID of the SGW, and the user plane IP address and TEID of the downlink SGW of the S5 interface.

Step 807, the PGW returns an update bearer response message to the destination SGW; the PGW sends an end end marker to the original SGW;

Step 808: The destination SGW returns a session establishment response message to the destination MME, where the message carries the IP address and TEID of the control plane of the SGW, and the user plane IP address and TEID of the uplink SGW of the S1-U interface.

Step 809: The destination MME returns a TAU accept message to the UE, where the message carries a re-allocated GUTI and a tracking area identity (TAI) list. After receiving the new GUTI, the UE needs to return a TAU complete message to the MME. ;

Step 810: The destination MME sends a setup context request message to the eNodeB, where the message carries the user plane IP address and the TEID of the uplink SGW of the S1-U interface. The message also carries a request for establishing a forwarding tunnel.

In step 811, the eNodeB sends a setup context response message to the MME. The eNodeB does not support the establishment of the forwarding tunnel in the TAU process. The message carries the user plane IP address and TEID of the S1-U interface downlink eNodeB.

Step 812: The destination MME sends an update bearer request message to the destination SGW, where the message carries the user plane IP address and TEID of the S1-U interface downlink eNodeB obtained in step 811. The destination SGW may also be notified in the bearer update request message: The eNodeB does not support establishing a forwarding tunnel in the TAU process;

Step 813: The destination SGW returns an update bearer response message to the destination MME.

In step 814, the eNodeB does not support the establishment of the forwarding tunnel in the TAU process, so the destination MME selects the destination SGW as the forwarding anchor SGW, and sends a forwarding tunnel request message to the forwarding anchor SGW, where the message carries the IMSI and is obtained in step 811. The user plane IP address and the TEID of the downlink eNodeB of the S1-U interface; the SGW can also learn that the eNodeB does not support establishing a forwarding tunnel in the TAU process by using a local configuration manner;

Step 815, the forwarding anchor SGW returns a forwarding tunnel response message to the destination MME, where the message carries the forwarding IP address and TEID of the forwarding anchor point SGW;

Step 816, the destination MME returns a context confirmation message to the original MME, where the message carries the forwarding IP address and TEID of the forwarding anchor SGW obtained in step 815;

Step 817: The original MME sends a bearer update request message to the original SGW, where the message carries the forwarding IP address and TEID of the forwarding anchor SGW obtained in step 816;

Step 818, the original SGW returns a bearer update response message to the original MME.

Step 819, the original MME sends a release session request message to the original SGW; the original SGW releases all the information of the UE;

Step 820: The original SGW sends a release session response message to the original MME.

The downlink data thus buffered on the original SGW is forwarded by the path original SGW-> forwarding anchor SGW (the forwarding anchor SGW is the destination SGW)->eNodeB (shown as a thick line in FIG. 8).

Optionally, after all the data buffered by the original SGW is completely forwarded, if the original SGW does not receive the End Marker sent by the PGW, the original SGW needs to add an end marker (End Marker) at the end of the buffered data forwarding, and the eNodeB does not support When forwarding data in the tracking area update process, after receiving the End Marker, the destination SGW considers that there is no more data to be received on the forwarding tunnel, and discards the End Marker; the eNodeB supports forwarding data during the tracking area update process, so the destination SGW needs to After all the data on the forwarding tunnel is transmitted to the eNodeB, the data received from the PGW is sent to the eNodeB. If the cached data of the original SGW has not been completely forwarded to the eNodeB through the forwarding tunnel and the data from the PGW is received, the destination SGW first buffers the data from the PGW.

The foregoing embodiment provides a method and an apparatus for implementing forwarding data. During a tracking area update process, the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station, and receives the base station that carries the forwarding tunnel returned by the base station. After the response message of the end information, the base station end information of the forwarding tunnel is sent to the relevant network element to establish the forwarding tunnel, and the base station can receive the data cached on the original serving gateway by using the forwarding tunnel. In addition, if the base station does not support the establishment of the forwarding tunnel, after the destination serving gateway obtains the first data buffered on the original serving gateway as the data forwarding anchor service gateway, after transmitting the first data to the base station, the packet data will be transmitted from the packet data. The second data acquired by the network gateway is sent to the base station, so that the problem that the base station receives the data out of order during the tracking area update process can be solved.

In addition, an embodiment of the present invention further provides a computer readable storage medium, where a computer can be stored. Executing an instruction to implement the above-described method of implementing forwarding data applied to the mobility management unit side when the computer executable instructions are executed.

In addition, an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, and when the computer executable instructions are executed, implementing the foregoing method for implementing forwarding data applied to a service gateway side.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function. This application is not limited to any specific combination of hardware and software.

It should be noted that various other embodiments and modifications may be made by those skilled in the art without departing from the spirit and scope of the application, Corresponding changes and modifications are intended to fall within the scope of the appended claims.

Industrial applicability

The embodiment of the present invention provides a method and an apparatus for implementing forwarding data, which can solve the problem that the base station cannot receive the data cached on the original serving gateway and the received data is out of order during the tracking area update process.

Claims

A method for implementing forwarding data, the method comprising:

During the tracking area update process, the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station; the forwarding tunnel is configured to forward data buffered on the original serving gateway to the base station;

After receiving the response message of the base station end information of the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.
The implementation method of claim 1, wherein the destination mobility management unit sends a request message for requesting to establish a forwarding tunnel to the base station, including:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting to establish a forwarding tunnel.
The implementation method of claim 2, wherein the destination mobility management unit sends the base station information of the forwarding tunnel to the relevant network after receiving the response message of the base station information carrying the forwarding tunnel returned by the base station The element is used to establish the forwarding tunnel, including:

After receiving the initial context setup response message of the base station end information of the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.
The implementation method of claim 3, wherein the transmitting the base station information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel comprises:

Transmitting the base station information of the forwarding tunnel to the original mobility management unit, where the original mobility management unit sends the base station information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the base station and the original serving gateway; or,

Sending the base station information of the forwarding tunnel to the anchor service gateway that forwards the data to establish a forwarding tunnel between the anchor service gateway and the base station, and sending the information of the anchor service gateway end of the forwarding tunnel to the original mobile a management unit, the anchor point of the forwarding tunnel is used by the original mobility management unit The serving gateway end information is sent to the original serving gateway to establish a forwarding tunnel between the anchor service gateway and the original serving gateway.
The implementation method according to any one of claims 1 to 4, wherein the base station end information of the forwarding tunnel comprises: base station end network protocol IP address information of the forwarding tunnel and tunnel end point identifier TEID information.
The implementation method according to any one of claims 1 to 4, wherein the base station comprises: an evolved Node B; the mobility management unit comprises: a mobility management entity MME.
A method for implementing forwarding data, the method comprising:

During the tracking area update process, the destination service gateway obtains the first data cached on the original service gateway;

After the destination service gateway sends all the first data buffered on the original serving gateway to the base station, the second data acquired from the packet data network gateway is sent to the base station.
The implementation method of claim 7, wherein the destination service gateway obtains the first data cached on the original service gateway, including:

The destination service gateway receives the first data sent by the original service gateway, and after receiving the data end identifier, determines that all the first data buffered on the original service gateway is received.
The implementation method of claim 7, wherein the destination service gateway sends the first data buffered on the original serving gateway to the base station, and sends the second data acquired from the packet data network gateway to the base station. include:

If the destination service gateway does not detect the data end identifier in the received first data cached on the original serving gateway, it is determined that the first data is not received, and the destination service gateway caches the packet from the packet data network gateway. Second data.
The implementation method of claim 8, wherein the data end identifier is created by a packet data network gateway or created by the original service gateway.
The implementation method according to any one of claims 7 to 10, wherein the destination service gateway acquires the first data cached on the original service gateway, including:

The destination service gateway obtains the first data from the original service gateway as a data forwarding anchor service gateway;

The destination mobility management unit selects the destination serving gateway as the data forwarding anchor service gateway after learning that the base station does not support the establishment of the forwarding tunnel. The forwarding tunnel is used to forward the data buffered on the original serving gateway to the base station.
The implementation method of claim 11, wherein the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel, and includes:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting establishment of a forwarding tunnel;

After receiving the initial context setup response message returned by the base station, if the initial context setup response message does not include the base station end information of the forwarding tunnel, the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel.
The implementation method according to any one of claims 7 to 10, wherein the base station comprises: an evolved Node B; and the mobility management unit comprises: a mobility management entity MME.
An apparatus for implementing forwarding data, applied to a mobility management unit, comprising:

The requesting module is configured to: in the tracking area update process, send, as the destination mobility management unit, a request message for requesting to establish a forwarding tunnel to the base station; where the forwarding tunnel is used to forward the data cached on the original serving gateway to the Base station

The response receiving and processing module is configured to: after receiving the response message of the base station end information carrying the forwarding tunnel returned by the base station, the destination mobile management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the Said forwarding tunnel.
The implementation device of claim 14, wherein the request module is configured to:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting establishment of a forwarding tunnel.
The implementation device of claim 15, wherein the response receiving and processing module is configured to:

After receiving the initial context setup response message of the base station end information of the forwarding tunnel returned by the base station, the destination mobility management unit sends the base station end information of the forwarding tunnel to the relevant network element to establish the forwarding tunnel.
The implementation device of claim 16, wherein the response receiving and processing module is configured to send the base station end information of the forwarding tunnel to an associated network element to establish the forwarding tunnel by:

Transmitting the base station information of the forwarding tunnel to the original mobility management unit, where the original mobility management unit sends the base station information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the base station and the original serving gateway; or,

Sending the base station information of the forwarding tunnel to the anchor service gateway that forwards the data to establish a forwarding tunnel between the anchor service gateway and the base station, and sending the information of the anchor service gateway end of the forwarding tunnel to the original mobile The management unit sends, by the original mobility management unit, the anchor service gateway end information of the forwarding tunnel to the original serving gateway to establish a forwarding tunnel between the anchor service gateway and the original serving gateway.
The implementation device according to any one of claims 14 to 17, wherein the base station end information of the forwarding tunnel comprises: base station end network protocol IP address information of the forwarding tunnel and tunnel end point identification TEID information.
The implementation device according to any one of claims 14 to 17, wherein the base station comprises: an evolved Node B; the mobility management unit comprises: a mobility management entity MME.
An apparatus for implementing forwarding data, applied to a service gateway, includes:

The data receiving module is configured to: obtain, as the destination service gateway, the first data cached on the original serving gateway during the tracking area update process;

The data sending module is configured to: after the first data buffered on the original serving gateway is sent to the base station as the destination serving gateway, send the second data acquired from the packet data network gateway to the base station.
The implementation device of claim 20, wherein the data receiving module is configured to: The destination service gateway receives the first data sent by the original service gateway, and after receiving the data end identifier, determines that all the first data buffered on the original service gateway is received.
The implementation device of claim 20, wherein the data sending module is configured to: if the destination service gateway does not detect the data end identifier in the first data buffered on the received original serving gateway, determine the The first data is not received, and the second data from the packet data network gateway is buffered as the destination service gateway.
The implementation device of claim 21, wherein the data end identification is created by a packet data network gateway or created by the original service gateway.
The implementation device according to any one of claims 20 to 23, wherein the data receiving module is configured to:

And the destination service gateway obtains the first data from the original service gateway as a data forwarding anchor service gateway;

The destination mobility management unit selects the destination serving gateway as the data forwarding anchor service gateway after learning that the base station does not support the establishment of the forwarding tunnel. The forwarding tunnel is used to forward the data buffered on the original serving gateway to the base station.
The implementation device of claim 24, wherein the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel, and includes:

The destination mobility management unit sends an initial context setup request message to the base station, where the initial context setup request message carries indication information for requesting establishment of a forwarding tunnel;

After receiving the initial context setup response message returned by the base station, if the initial context setup response message does not include the base station end information of the forwarding tunnel, the destination mobility management unit learns that the base station does not support establishing a forwarding tunnel.
The implementation device according to any one of claims 20 to 23, wherein the base station comprises: an evolved Node B; the mobility management unit comprises: a mobility management entity MME.