WO2016141591A1

WO2016141591A1 - Service continuity achieving method, device and system

Info

Publication number: WO2016141591A1
Application number: PCT/CN2015/074110
Authority: WO
Inventors: 邓强; 张万强
Original assignee: 华为技术有限公司
Priority date: 2015-03-12
Filing date: 2015-03-12
Publication date: 2016-09-15
Also published as: CN106797632A; CN106797632B

Abstract

Provided in embodiments of the present invention are a service continuity achieving method, device and system. The method comprises: receiving, by a relay UE, a first message transmitted by a remote UE in an offline state, the first message comprising a first IP address allocated to the remote UE by a PGW; transmitting, by the relay UE, according to the first message, a second message to an MME so as to enable the MME to transmit a third message to the PGW, the second message and the third message each comprising the first IP address; the third message is used by the PGW to determine a binding relationship; determining, by the relay UE, according to the first IP address and a second IP address, the binding relationship and realizing, by the relay UE, according to the binding relationship, a communication between the PGW and the remote UE. The present invention addresses a problem in the prior art of a communication interruption when the remote UE changes from an online state to an offline state.

Description

Method, device and system for realizing business continuity

Technical field

Embodiments of the present invention relate to communication technologies, and in particular, to a method, apparatus, and system for implementing service continuity.

Background technique

ProSe (Proximity Service) is a type of user equipment (UE, User Equipment) defined by the 3rd Generation Partnership Project (3GPP) that utilizes long-term evolution (LTE, Long Term Evolution) without going through a base station. Technology for methods of proximity discovery and proximity communication.

In the prior art, an important scenario of the ProSe application is to enable a remote UE without an out of network to access the network through a relay UE with network coverage. When the Remote UE accesses the network through the Relay UE: the Relay UE allocates an Internet Protocol (IP) address (ie, IP_1) to the Remote UE; the Remote UE packs the data according to the IP_1, and packages the data through the proximity communication. The subsequent data is sent to the Relay UE; after receiving the packed data, the Relay UE replaces the IP_1 with the IP address of the Relay UE (ie, IP_2), and passes the packet between the Relay UE and the Packet Data Gateway (PGW, PDN Gateway). A data network (PDN, Packet Data Network) connection transmits the replaced data. Similarly, when the Relay UE receives the data to be sent to the Remote UE through the PDN connection, the IP_2 in the data is replaced with IP_1, and the replaced data is sent to the Remote UE through the proximity communication.

However, in the prior art, there is a problem that communication is interrupted when the remote UE changes from the network state to the off-network state.

Summary of the invention

The embodiment of the invention provides a method, a device and a system for implementing service continuity, which are used to solve the problem that communication is interrupted when the remote UE changes from the network state to the off-network state in the prior art.

In a first aspect, the present invention provides a method of implementing business continuity, the method comprising:

The relay UE receives the first message sent by the remote UE in the off-network state, where the first message includes a first IP address allocated by the PGW to the remote UE;

The relaying UE sends a second message to the mobility management entity MME according to the first message, so that the MME sends a third message to the PGW, where the second message and the third message are both included. The first IP address, wherein the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the The second IP address is an IP address assigned to the relay UE by the PGW;

The relaying UE determines the binding relationship according to the first IP address and the second IP address, and implements the PGW and the remote end by using the relay UE according to the binding relationship. Communication between UEs

With reference to the first aspect, in a first possible implementation manner of the first aspect, the relay UE, according to the binding relationship, implements communication between the PGW and the remote UE, including:

Receiving, by the relay UE, the first data packet that is sent by the remote UE by using the proximity communication; the first data packet includes the first IP address; and the relay UE adopts the The second IP address tunnel encapsulates the first data packet to obtain a second data packet; the relay UE sends the second data packet to the PGW, so that the PGW pairs the second data Obtaining the first data packet after the packet is decapsulated by the tunnel; and/or,

The relaying UE receives the third data packet sent by the PGW; the third data packet is the fourth that the PGW sends the second IP address pair to the remote UE according to the binding relationship. a data packet obtained after the tunnel is encapsulated by the data packet; the fourth data packet includes the first IP address; and the relay UE performs tunnel decapsulation on the third data packet to obtain the fourth data packet. And transmitting the fourth data packet to the remote UE by using proximity communication.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the first message further includes an identifier of the remote UE;

The relaying UE, before sending the second message to the MME according to the first message, further includes:

The relaying UE sends a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE;

Receiving, by the relay UE, a fifth message sent by the MME, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates the relay UE and the PGW. Inter-packet data network PDN connection.

With the second possible implementation of the first aspect, in a third possible implementation manner of the first aspect, if the result identifier indicates that a PDN connection between the relay UE and the PGW is newly established, The second message is a PDN connection request message, the third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay;

Or, if the result identifier indicates that the PDN connection between the relay UE and the PGW is not newly created, the second message is a bearer resource modification request message, and the third message is a bearer resource command message.

With the second or the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the relaying, by the relaying UE, the fourth message, to the MME, includes:

Transmitting, by the relay UE, the fourth message to the MME by using a proximity service function entity ProSe Function; or

The relay UE directly sends the fourth message to the MME.

With the fourth possible implementation of the first aspect, in a fifth possible implementation manner of the first aspect, the relaying, by the relay UE, sending the fourth message to the MME by using a ProSe function, includes:

The relay UE sends an eleventh message to the ProSe Function;

The ProSe Function sends a twelfth message to the home subscription server HSS according to the eleventh message;

Sending, by the HSS, the fourth message to the MME according to the twelfth message;

The eleventh message and the twelfth message each include an identifier of the remote UE and an identifier of the relay UE.

In conjunction with the first aspect or the first to fifth aspects of the first aspect, in a sixth possible implementation manner of the first aspect, if the relay UE determines the remote end The neighboring communication of the UE has ended, and the relaying UE releases the binding relationship.

In a second aspect, the present invention provides a method of implementing business continuity, the method comprising:

The mobility management entity MME receives the second message sent by the relay user equipment UE, where the second message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

The MME sends a third message to the PGW according to the second message, where the third message includes the first IP address, where the third message is used by the PGW to determine a binding relationship. The binding relationship includes a correspondence between the first IP address and a second IP address, where the The second IP address is an IP address assigned to the relay UE by the PGW.

With reference to the second aspect, in a first possible implementation manner of the second aspect, before the MME receives the second message sent by the relaying UE, the method further includes:

Receiving, by the MME, a fourth message sent by the relaying UE, where the fourth message includes an identifier of the remote UE and an identifier of the relaying UE;

Determining, according to the fourth message, whether to establish a packet data network PDN connection between the relay UE and the PGW according to the fourth message;

Sending, by the MME, a fifth message to the relay UE, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates a new connection between the relay UE and the PGW. PDN connection.

With reference to the first possible implementation of the second aspect, in a second possible implementation manner of the second aspect, the MME determines, according to the fourth message, whether to create the new relay UE and the PGW. PDN connections between:

Determining, by the MME, the context of the remote UE according to the identifier of the remote UE, where the context of the remote UE includes an IP address of a remote UE and an IP address of a PGW in each PDN connection of the remote UE;

Determining, by the MME, the context of the relay UE according to the identifier of the relay UE, where the context of the relay UE includes an IP address of a relay UE and an IP address of a PGW in each PDN connection of the relay UE ;

The MME determines whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE.

With the second possible implementation of the second aspect, in a third possible implementation manner of the second aspect, if the MME is different from the MME of the remote UE, the MME is configured according to the remote end The identifier of the UE determines the context of the remote UE, including:

Sending, by the MME, a sixth message to the MME of the remote UE, where the sixth message includes an identifier of the remote UE;

The MME receives a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE.

In a fourth possible implementation manner of the second aspect, the second message is a PDN connection request message, where the third The information is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay; or the second message is a bearer resource modification request message, and the third message is a bearer resource command message. .

With reference to the fourth possible implementation of the second aspect, in a fifth possible implementation manner of the second aspect, the PDN connection request message further includes an identifier of the remote UE;

After the MME receives the second message sent by the relaying UE, the MME further includes:

Determining, by the MME, the context of the remote UE according to the identifier of the remote UE, and establishing, between the relay UE and the PGW, according to the context of the remote UE and the first IP address. PDN connection.

With the fourth possible implementation of the second aspect, in a sixth possible implementation manner of the second aspect, if the MME determines to establish a PDN connection between the relay UE and the PGW, The method also includes:

The MME adds a correspondence between the first IP address and the PGW in the context information of the relay UE.

The MME establishes a PDN connection between the relay UE and the PGW according to the first IP address in the PDN connection request message and the correspondence between the first IP address and the PGW.

With the possible implementation of the first to sixth aspects of the second aspect, in a seventh possible implementation manner of the second aspect, the MME receives the fourth message sent by the relay UE, including :

Receiving, by the MME, the fourth message sent by the relay UE by using a proximity service function entity ProSe Function; or

The MME receives the fourth message that the relay UE sends directly to the MME.

With reference to the seventh possible implementation of the second aspect, in an eighth possible implementation manner of the second aspect, the MME receives a fourth message sent by the home subscription server HSS according to the twelfth message, the tenth The second message is a message that is sent by the ProSe Function to the HSS after receiving the eleventh message sent by the relay UE, where the eleventh message and the twelfth message both include the remote end The identity of the UE and the identity of the relay UE.

In combination with the second aspect or the first to the eighth aspect of any of the possible aspects of the second aspect, In a ninth possible implementation manner of the second aspect, after the MME receives the second message sent by the relaying UE, the method further includes:

Receiving, by the MME, an eighth message that is sent by the remote UE in a network state, where the eighth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

And sending, by the MME, a ninth message to the PGW according to the eighth message, where the ninth message includes the release identifier.

In a third aspect, the present invention provides a method for implementing business continuity, the method comprising:

The packet data gateway PGW receives the third message sent by the mobility management entity MME, where the third message includes the first Internet Protocol IP address allocated by the PGW to the remote UE;

Determining, by the PGW, the binding relationship according to the third message, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the PGW Relaying the IP address of the UE;

The PGW implements communication between the PGW and the remote UE by using the relay UE according to the binding relationship.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the third message is a bearer resource command message or a session establishment request message; if the third message is a session establishment request message, The PGW, before determining the binding relationship according to the third message, further includes:

Assigning, by the PGW, the second IP address to the relay UE;

Correspondingly, the PGW determines the binding relationship according to the third message, and the PGW determines the binding relationship according to the first IP address and the second IP address.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the PGW, according to the binding relationship, is implemented by the relay UE The communication between the PGW and the remote UE includes:

Receiving, by the PGW, the second data packet sent by the relay UE, where the second data packet is a data packet obtained by tunneling the first data packet by the relay UE according to the second IP address; The first data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address, and the PGW performs tunnel decapsulation on the second data packet to obtain the first data packet. a data packet; and/or,

The PGW sends a fourth data packet to the remote UE according to the second IP address. Performing tunnel encapsulation, obtaining a third data packet, and forwarding the third data packet to the relay UE, so that the relay UE performs tunnel decapsulation on the third data packet to obtain the fourth And transmitting the fourth data packet to the remote UE by using proximity communication.

With reference to the third aspect or the first to the second aspect of the third aspect, in a third possible implementation manner of the third aspect, the PGW passes the After the relay UE implements the communication between the PGW and the remote UE, the method further includes:

The PGW receives the ninth message sent by the MME, where the ninth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

The PGW cancels the binding relationship according to the ninth message.

In a fourth aspect, the present invention provides a method for implementing business continuity, the method comprising:

The remote user equipment UE determines that the remote UE changes from the in-network state to the off-network state;

The remote UE sends a first message to the relay UE, so that the relay UE determines a binding relationship according to the first message, where the first message includes a PGW that is allocated to the remote UE. An IP address.

In conjunction with the fourth aspect, in a first possible implementation manner of the fourth aspect, the first message further includes an identifier of the remote UE.

With the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, after the remote UE sends the first message to the relay UE, the method further includes:

After the remote UE changes from the off-network state to the network state, the eighth message is sent to the mobility management entity MME, where the eighth message includes a release identifier, where the release identifier is used to indicate that the PGW is removed. Describe the binding relationship.

In a fifth aspect, the present invention provides an apparatus for implementing service continuity, where the apparatus is a relay user equipment UE; the apparatus includes:

a transceiver module, configured to receive a first message sent by a remote UE in an off-network state, where the first message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

The transceiver module is further configured to send, according to the first message, a second message to the mobility management entity MME, so that the MME sends a third message, the second message, and the third message to the PGW. The message includes the first IP address, where the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address. Relationship, the second IP address is an IP address assigned by the PGW to the relay UE;

a processing module, configured to determine the binding relationship according to the second IP address and the first IP address included in the first message received by the transceiver module;

The transceiver module is further configured to implement communication between the PGW and the remote UE by using the relay UE according to the binding relationship determined by the processing module.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the transceiver module is specifically configured to:

Receiving, by the remote UE, the first data packet sent by the proximity communication; the first data packet includes the first IP address; and according to the binding relationship, using the second IP address to the first data The packet is tunnel encapsulated to obtain a second data packet, and the second data packet is sent to the PGW, so that the PGW obtains the first data packet after performing tunnel decapsulation on the second data packet; and /or,

Receiving a third data packet sent by the PGW; the third data packet is a tunnel encapsulation of the fourth data packet sent by the PGW to the remote UE by using the second IP address according to the binding relationship. a data packet obtained afterwards; the fourth data packet includes the first IP address; tunnel decapsulating the third data packet, obtaining the fourth data packet, and the fourth data by proximity communication The packet is sent to the remote UE.

With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the first message further includes an identifier of the remote UE, and the transceiver module And the fourth message is sent to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE, and receives a fifth message sent by the MME, where the The five message includes a result identifier, where the result identifier is used to indicate whether the relay UE establishes a packet data network PDN connection between the relay UE and the PGW.

With the second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, if the result identifier indicates that the PDN connection between the relay UE and the PGW is newly established, The second message is a PDN connection request message, the third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay;

With reference to the second or the third possible implementation manner of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the transceiver module is specifically configured to: use the proximity service function entity ProSe Function to the MME Sending the fourth message; or sending the fourth message directly to the MME.

With reference to the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the transceiver module is specifically configured to: send an eleventh message to the ProSe Function, so that the The ProSe Function sends a twelfth message to the home subscription server (HSS) according to the eleventh message, and triggers the HSS to send a fourth message to the MME according to the twelfth message; wherein the eleventh message and the The twelfth message includes the identifier of the remote UE and the identifier of the relay UE.

With reference to the fifth aspect, or any one of the first to fifth aspects of the fifth aspect, in a sixth possible implementation manner of the fifth aspect, if the processing module determines the remote UE The proximity communication is terminated, and the binding relationship is released.

In a sixth aspect, the present invention provides an apparatus for implementing service continuity, where the apparatus is a mobility management entity MME, and the apparatus includes:

a receiving module, configured to receive a second message sent by the relay user equipment UE, where the second message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

a sending module, configured to send, according to the second message received by the receiving module, a third message to the PGW, where the third message includes the first IP address, where the third message is used by the The PGW determines a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is an IP address allocated by the PGW to the relay UE. .

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the device further includes: a processing module; the receiving module is further configured to receive a fourth message sent by the relay UE, The fourth message includes an identifier of the remote UE and an identifier of the relay UE;

The processing module is configured to determine, according to the fourth message received by the receiving module, whether to establish a packet data network PDN connection between the relay UE and the PGW;

The sending module is further configured to send a fifth message to the relay UE, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates the new relay UE and PDN connection between the PGWs.

With reference to the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the processing module is specifically configured to:

Determine a context of the remote UE according to the identifier of the remote UE, where the context of the remote UE includes an IP address of a remote UE and an IP address of a PGW in each PDN connection of the remote UE;

Determining, according to the identifier of the relay UE, a context of the relay UE, where the context of the relay UE includes an IP address of a relay UE and an IP address of a PGW in each PDN connection of the relay UE;

Determining whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE.

With reference to the first possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, if the MME is different from the MME of the remote UE, the sending module is further configured to: Sending a sixth message to the MME of the remote UE, where the sixth message includes an identifier of the remote UE;

The receiving module is further configured to receive a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE, and a context of the remote UE includes the remote UE The IP address of the remote UE and the IP address of the PGW in each PDN connection;

The processing module is specifically configured to determine a context of the relay UE according to an identifier of the relay UE, where a context of the relay UE includes an IP address of a relay UE in each PDN connection of the relay UE And determining, by the IP address of the PGW, whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE received by the receiving module.

In a fourth possible implementation manner of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the second message is a PDN connection request message, and the third message is Establishing a request message for the session, the second message further including a request identifier for indicating that the request type is a relay; or

The second message is a bearer resource modification request message, and the third message is a bearer resource command message.

With reference to the fourth possible implementation manner of the sixth aspect, in a fifth possible implementation manner of the sixth aspect, the PDN connection request message further includes an identifier of the remote UE;

The processing module is further configured to determine a context of the remote UE according to the identifier of the remote UE, and establish the relay UE according to a context of the remote UE and the first IP address. PDN connection between the PGWs.

With the fourth possible implementation manner of the sixth aspect, in a sixth possible implementation manner of the sixth aspect, if the processing module determines to establish a PDN connection between the relay UE and the PGW, The processing module is further configured to:

Adding a correspondence between the first IP address and the PGW in the context information of the relay UE; according to the first IP address and the first IP address in the PDN connection request message, and the PGW Corresponding relationship, establishing a PDN connection between the relay UE and the PGW.

With reference to the possible implementation of the first to sixth aspects of the sixth aspect, in a seventh possible implementation manner of the sixth aspect, the receiving module is specifically configured to: receive the relay UE by using a neighboring The fourth message sent by the serving function entity ProSe Function; or receiving the fourth message sent by the relay UE directly to the MME.

With reference to the seventh possible implementation manner of the sixth aspect, in the eighth possible implementation manner of the sixth aspect, the receiving module is specifically configured to: receive, by the home subscription server, the HSS according to the twelfth message a fourth message, the twelfth message is a message that is sent by the ProSe Function to the HSS after receiving the eleventh message sent by the relay UE; wherein the eleventh message and the twelfth message The message includes an identifier of the remote UE and an identifier of the relay UE.

In a ninth possible implementation manner of the sixth aspect, the receiving module is further configured to receive the presence of the network in the ninth possible implementation manner of the sixth aspect or the sixth aspect An eighth message sent by the remote UE in the state, where the eighth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

The sending module is further configured to send a ninth message to the PGW according to the eighth message received by the receiving module, where the ninth message includes the release identifier.

In a seventh aspect, the present invention provides an apparatus for implementing service continuity, the apparatus being a packet data gateway PGW; the apparatus comprising:

a transceiver module, configured to receive a third message sent by the mobility management entity MME, where the third message includes a first Internet Protocol IP address that is allocated by the PGW to the remote user equipment UE;

a processing module, configured to determine, according to the third message received by the transceiver module, a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where The second IP address is an IP address assigned to the relay UE by the PGW;

With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, the third message is a bearer resource command message or a session establishment request message; if the third message is a session establishment request message, The processing module is specifically used to:

Allocating the second IP address to the relay UE;

Determining a binding relationship according to the first IP address and the second IP address.

With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, the transceiver module is specifically configured to:

Receiving, by the relay UE, a second data packet, where the second data packet is a data packet obtained by tunneling the first data packet by the relay UE according to the second IP address; The data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address, and the second data packet is tunnel decapsulated to obtain the first data packet; and/ or,

Performing tunnel encapsulation on the fourth data packet to be sent to the remote UE according to the second IP address, obtaining a third data packet, and forwarding the third data packet to the relay UE, so that the The relay UE obtains the fourth data packet after performing tunnel decapsulation on the third data packet, and sends the fourth data packet to the remote UE by using proximity communication.

With reference to the seventh aspect, or any one of the first to the second aspect of the seventh aspect, in a third possible implementation manner of the seventh aspect, the transceiver module is further configured to receive the MME a ninth message that is sent, where the ninth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

The processing module is further configured to cancel the binding relationship according to the ninth message received by the transceiver module.

In an eighth aspect, the present invention provides an apparatus for implementing service continuity, where the apparatus is a remote user equipment UE; the apparatus includes:

a processing module, configured to determine that the remote UE changes from a network state to a disconnection state;

a sending module, configured to send, by the processing module, the first message to the relay UE, when the processing module determines that the remote UE becomes an off-network state, so that the relay UE determines a binding relationship according to the first message; The first message includes a first IP address allocated by the PGW to the remote UE.

In conjunction with the eighth aspect, in a first possible implementation manner of the eighth aspect, the first message further includes an identifier of the remote UE.

With reference to the eighth aspect, or the first possible implementation manner of the eighth aspect, in a second possible implementation manner of the eighth aspect, the sending module is further configured to:

According to a ninth aspect, the present invention provides a system for implementing service continuity, the system comprising: the relay UE, the sixth aspect of the first to sixth aspects of the fifth aspect or the fifth aspect, or The MME according to any one of the first to ninth aspects of the sixth aspect, the PGW of the first aspect to the third aspect of the seventh aspect, and the eighth aspect or the eighth aspect The remote UE of any one of the first to the second.

The present invention provides a method, apparatus, and system for implementing service continuity, in which a relay UE receives a first message sent by a remote UE in an off-network state, and the first message includes a PGW allocated to the remote UE. a first IP address, the relay UE sends a second message to the MME according to the first message, so that the MME sends a third message to the PGW, where the second message and the third message include a first IP address, where the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, and the second The IP address is an IP address assigned to the relay UE by the PGW; the relay UE determines the binding relationship according to the first IP address and the second IP address, and according to the binding The communication between the PGW and the remote UE is implemented by the relaying UE, so that when the remote UE changes from the network state to the offline state, the remote UE can continue to use the network state in the network state. The IP address used by the peer to perform communication is communicated; thereby solving the prior art, The problem by the UE at the distal end of the mesh state to off-network state, communication is interrupted.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

FIG. 1 is a schematic diagram of an application scenario of a method for implementing service continuity according to the present invention;

2 is a flowchart of Embodiment 1 of a method for implementing service continuity according to the present invention;

3 is a flowchart of Embodiment 2 of a method for implementing service continuity according to the present invention;

4 is a flowchart of Embodiment 3 of a method for implementing service continuity according to the present invention;

FIG. 5 is a flowchart of Embodiment 4 of a method for implementing service continuity according to the present invention;

6 is a flowchart of Embodiment 5 of a method for implementing service continuity according to the present invention;

7 is a flowchart of Embodiment 6 of a method for implementing service continuity according to the present invention;

FIG. 8 is a schematic structural diagram of Embodiment 1 of an apparatus for implementing service continuity according to the present invention;

9 is a schematic structural diagram of Embodiment 2 of an apparatus for implementing service continuity according to the present invention;

10 is a schematic structural diagram of Embodiment 4 of an apparatus for implementing service continuity according to the present invention;

11 is a schematic structural diagram of Embodiment 5 of an apparatus for implementing service continuity according to the present invention;

12 is a schematic structural diagram of Embodiment 7 of an apparatus for implementing service continuity according to the present invention;

13 is a schematic structural diagram of Embodiment 9 of an apparatus for implementing service continuity according to the present invention;

14 is a schematic structural diagram of Embodiment 11 of an apparatus for implementing service continuity according to the present invention;

15 is a schematic structural diagram of Embodiment 13 of an apparatus for implementing service continuity according to the present invention;

FIG. 16 is a schematic structural diagram of Embodiment 15 of an apparatus for implementing service continuity according to the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a schematic diagram of an application scenario of a method for implementing service continuity according to the present invention; as shown in FIG. 1 , the application scenario includes: UE1, UE2, PGW, and a peer end. When UE1 is in the network state (that is, UE1 is in the network), UE1 performs service communication with the opposite end based on IP1; when UE1 moves out of the network from position L1 in the direction indicated by the dotted arrow in FIG. 1 (for example, moving to position L2) At the same time, UE1 changes from the network access state to the off-network state (that is, UE1 is the remote UE). After the UE1 changes from the network access state to the off-network state, the UE1 can access the network through the UE2 (that is, the UE2 is the relay UE); and when the UE1 accesses the network through the UE2, the UE2 allocates an IP2 to the UE1. When the UE needs to send data, UE1 The data packet is transmitted to the UE2 according to the IP2, and the UE2 replaces the IP2 in the data packet with the IP address (for example, IP3) of the UE2, and then transmits the replaced data packet through the PDN connection between the UE2 and the PGW.

In the prior art, after the UE1 changes from the network state to the off-network state, the IP address used for communication with the peer end changes from IP1 to IP3 (that is, the IP address changes), causing UE1 to be in the network state. The communication established by the peer is interrupted. Therefore, in the prior art, when the remote UE changes from the network state to the off-network state, the communication is interrupted.

It should be noted that the peer end may be a UE or a server or the like outside the network.

FIG. 2 is a flowchart of Embodiment 1 of a method for implementing service continuity according to the present invention. As shown in FIG. 2, the method in this embodiment may include:

Step 201: The relay UE receives the first message sent by the remote UE in the off-network state, where the first message includes a first IP address allocated by the PGW to the remote UE.

Optionally, the first IP address may be an IP address used when the remote UE is in a network state and communicates with the peer.

Step 202: The relay UE sends a second message to the MME according to the first message, so that the MME sends a third message to the PGW, where the second message and the third message include Said first IP address;

The third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is the PGW. The IP address assigned to the relay UE.

It should be noted that, since the IP addresses of the UEs are all allocated to the PGW, the mapping between the default bearer identifier of the relay UE and the second IP address is saved in the PGW; the PGW may be based on the default bearer of the relay UE. The identification determines the second IP address.

Step 203: The relay UE determines the binding relationship according to the first IP address and the second IP address, and implements the PGW and the device by using the relay UE according to the binding relationship. Communication between remote UEs.

In the prior art, the remote UE (where the remote UE may be the UE that accesses the network through the relay UE) changes from the on-network state to the off-network state, and the remote UE does not use the in-network state. The IP address communicates with other devices in the network, but uses the IP address assigned by the relay UE to perform proximity communication (in which two UEs do not communicate through the base station, it may be called a neighbor). Near communication), and communicates with other devices through the relay UE, and the IP address when the relay UE communicates with other devices is the IP address of the relay UE. In the present invention, the relay UE receives the first message sent by the remote UE in the off-network state, the first message includes a first IP address allocated by the PGW to the remote UE, and the relay UE is configured according to the Transmitting, by the first message, a second message, to the MME, to enable the MME to send a third message to the PGW, where the second message and the third message both include the first IP address; wherein the third message Determining, by the PGW, a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the relay UE by the PGW The IP address of the relay UE is determined according to the first IP address and the second IP address, and the PGW is implemented by the relay UE according to the binding relationship. Communication between the remote UEs.

In the prior art, after the remote UE changes from the network state to the offline state, the remote UE communicates with the relay UE by using the IP address assigned by the relay UE, and communicates with other devices through the relay UE. And the IP address of the relaying UE and the other device is the IP address of the relaying UE; therefore, when the remote UE changes from the in-network state to the offline state, the remote UE is in the network state and communicates with the opposite end. The IP address used at the time is different from the IP address of the relay UE, and the remote UE is interrupted by the communication established with the peer when the network state changes to the offline state. In the present invention, the first message sent by the remote UE in the off-network state is received by the relay UE, where the first message includes a first IP address allocated by the PGW to the remote UE; the relay UE Sending, according to the first message, a second message to the MME, to enable the MME to send a third message to the PGW, where the second message and the third message both include the first IP address; wherein the third The message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the relay by the PGW The IP address of the UE; the relay UE determines the binding relationship according to the first IP address and the second IP address, and implements the PGW by using the relay UE according to the binding relationship. The communication with the remote UE enables the remote UE to continue to use the IP address and the pair used when the remote UE is in the network state and the opposite end after the network state changes from the network state to the offline state. End communication; thereby solving the prior art, when the remote UE changes from the network state to the off-network state , the problem of communication interruption.

In the embodiment of the present invention, the relaying UE receives the first message sent by the remote UE in the off-network state, where the first message includes a first IP address that is allocated by the PGW to the remote UE; Sending, by the UE, a second message to the MME according to the first message, so that the MME sends the PGW to the PGW. Sending a third message, where the second message and the third message both include the first IP address, where the third message is used by the PGW to determine a binding relationship, and the binding relationship includes the first a correspondence between the IP address and the second IP address, where the second IP address is an IP address assigned by the PGW to the relay UE; and the relay UE is configured according to the first IP address and the first And determining, by the second IP address, the binding relationship, and implementing, by the relay UE, communication between the PGW and the remote UE according to the binding relationship; After being in the off-network state, the remote UE can continue to use the IP address used by the remote UE to perform the service in the network state and the peer end to communicate with the peer end; thereby solving the prior art, when the remote UE is in the network state The communication is interrupted when it becomes off-network.

FIG. 3 is a flowchart of Embodiment 2 of a method for implementing service continuity according to the present invention. As shown in FIG. 3, the method in this embodiment may include:

Step 301: The MME receives a second message sent by the relay UE, where the second message includes a first IP address allocated by the PGW to the remote UE.

Step 302: The MME sends a third message to the PGW according to the second message, where the third message includes the first IP address, where the third message is used by the PGW to determine binding. a relationship, the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is an IP address allocated by the PGW to the relay UE.

Optionally, the sending, by the MME, the third message to the PGW, the MME sending, by using a serving gateway (SGW, Serving), a third message to the PGW;

Specifically, the sending, by the MME, the third message to the PGW by using the SGW may be:

The MME sends a tenth message to the SGW, so that the SGW performs protocol correlation processing on the tenth message to obtain a third message, and sends the third message to the PGW.

The tenth message includes the first IP address.

In the embodiment of the present invention, after receiving the second message including the first IP address sent by the relay UE, the MME sends a third message including the first IP address to the PGW; and after the PGW obtains the first IP address, And determining a binding relationship according to the third message.

4 is a flowchart of Embodiment 3 of a method for implementing service continuity according to the present invention. As shown in FIG. 4, the method in this embodiment may include:

Step 401: The PGW receives a third message sent by the MME, where the third message includes a first IP address that is allocated by the PGW to the remote UE.

Step 402: The PGW determines, according to the third message, a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is The IP address assigned by the PGW to the relay UE;

Step 403: The PGW implements communication between the PGW and the remote UE by using the relay UE according to the binding relationship.

In the embodiment of the present invention, the third message sent by the MME is received by the PGW; the third message includes a first IP address that is allocated to the remote UE by the PGW when the remote UE is in the network state; Determining, by the third message, a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, and the PGW passes the relay UE according to the binding relationship. The communication between the PGW and the remote UE is implemented, so that when the remote UE changes from the network state to the offline state, the remote UE can continue to use the network when the remote UE is in the network state and the opposite end. The IP address communicates with the peer end; thereby solving the problem that the communication is interrupted when the remote UE changes from the network state to the off-network state in the prior art.

FIG. 5 is a flowchart of Embodiment 4 of a method for implementing service continuity according to the present invention. As shown in FIG. 5, the method in this embodiment may include:

Step 501: The remote UE determines that the remote UE changes from a network state to a disconnected state.

Step 502: The remote UE sends a first message to the relay UE, so that the relay UE determines a binding relationship according to the first message, where the first message includes a PGW allocated to the remote end. The first IP address of the UE.

In the embodiment of the present invention, after the remote UE determines that the remote UE changes from the network state to the offline state, the first message is sent to the relay UE, where the first message includes the first IP address, and the relay UE is obtained. After the first IP address, the binding relationship can be determined according to the first message.

FIG. 6 is a flowchart of Embodiment 5 of a method for implementing service continuity according to the present invention. As shown in FIG. 6, the method in this embodiment may include:

Step 601: The remote UE sends a first message to the relay UE after the network status changes to the offline status, where the first message includes the first IP address and the remote end allocated by the PGW to the remote UE. The identity of the UE;

Optionally, the first message may be a direct communication request message.

Step 602: The relay UE sends a fourth message to the MME, where the fourth message includes the The identifier of the remote UE and the identifier of the relay UE;

Optionally, the fourth message may be a non-access stratum (NAS, Non-Access Stratum) request message.

Optionally, the relay UE may send a fourth message to the MME by using a ProSeimity Service Function (ProSe Function).

Further, the MME may send a fourth message to the MME by using the ProSe Function and a Home Subscriber Server (HSS).

It should be noted that, since the relay UE may be connected to the PGW, or may not be connected to the PGW, the first message may include the remote UE in addition to the first IP address. And the MME is configured to enable the MME to determine, according to the identifier of the remote UE, whether to establish a PDN connection between the relay UE and the PGW, or modify a PDN connection between the relay UE and the PGW. .

Step 603: The MME determines, according to the fourth message, whether to establish a PDN connection between the relay UE and the PGW.

Optionally, the MME determines, according to the fourth message, whether to establish a PDN connection between the relay UE and the PGW, including:

Optionally, the MME determines, according to the context of the remote UE and the context of the relay UE, whether to establish a PDN connection between the relay UE and the PGW, including:

Determining, by the MME, an IP address of a PGW in a PDN connection corresponding to the first IP address according to a context of the remote UE, where the MME determines, according to a context of the relay UE, each PDN connection of the relay UE Whether the IP address of the PGW includes the IP address of the PGW in the PDN connection corresponding to the first IP address; if not, the MME determines to create the new relay UE A PDN connection with the PGW.

Optionally, if the MME is different from the MME of the remote UE, determining, by the MME, the context of the remote UE according to the identifier of the remote UE, including:

Optionally, the sixth message may be a context request message, and the seventh message may be a context response message.

Optionally, the MME may obtain the identifier of the MME of the remote UE according to the identifier of the remote UE, that is, the identifier of the MME of the remote UE may be reflected in the identifier of the remote UE.

Step 604: The MME sends a fifth message to the relay UE.

The fifth message includes a result identifier, where the result identifier is used to indicate that the relay UE does not newly establish a PDN connection between the relay UE and the PGW.

Optionally, the fifth message may be a NAS response message.

It should be noted that the fourth message may further include the first IP address, so that the MME can determine the IP address of the PGW according to the context of the remote UE and the first IP address.

or,

The fourth message may not include the first IP address, and the MME may determine whether to create or modify the IP address (IP_i) of the remote UE according to the context of the remote UE and the context of the relay UE. A PDN connection between the PGWs corresponding to the UE and the IP_i; correspondingly, the fifth message may include a result identifier corresponding to each IP_i.

Step 605: The relay UE sends a second message to the MME, where the second message includes the first IP address.

Optionally, the second message may be a bearer resource modification request message.

Optionally, when the relay UE is connected to multiple PGWs, the relay UE has multiple IP addresses; at this time, the MME may enable the relay UE to determine the manner by including the second IP address in the fifth message. Which of the plurality of IP addresses is an IP address (ie, a second IP address) connected to the PGW.

Step 606: The MME sends a third message to the PGW according to the second message, where the third message includes the first IP address.

Optionally, the third message may be a bearer resource command message.

Step 607: The PGW determines a binding relationship according to the third message.

The binding relationship includes a correspondence between the first IP address and the second IP address, where the second IP address is an IP address allocated by the PGW to the relay UE.

Optionally, the manner in which the PGW obtains the second IP address is similar to the step 202, and details are not described herein again.

Step 608: The relay UE determines the binding relationship according to the first IP address and the second IP address.

It should be noted that, when the relay UE determines the binding relationship, the relay UE may obtain any time after the first IP address and the second IP address.

Step 609: The relay UE and the PGW implement communication between the PGW and the remote UE according to the binding relationship.

Specifically, the relay UE and the PGW perform tunnel communication according to the binding relationship, and the remote UE performs proximity communication with the relay UE to implement between the PGW and the remote UE. Communicating and further implementing communication between the remote UE and the peer.

Optionally, step 609 can include:

Receiving, by the relay UE, the first data packet that is sent by the remote UE by using the proximity communication; the first data packet includes the first IP address; and the relay UE adopts the The second IP address tunnel encapsulates the first data packet to obtain a second data packet; the relay UE sends the second data packet to the PGW, so that the PGW pairs the second data Obtaining the first data packet after the packet is decapsulated by the tunnel;

It should be noted that, because the first data packet is a data packet sent by the remote UE to the peer end, the source IP address of the first data packet is the first IP address, and the destination IP address is the IP address of the peer end. When the relay UE tunnels the first data packet according to the second IP address, the first data packet is encapsulated in the second data packet, and the source IP address of the second data packet is the second IP address, and the destination IP address is The IP address of the end. Since the second IP address is an IP address assigned to the relay UE by the PGW, the second data packet can be routed to the PGW. The PGW obtains the first data packet encapsulated in the second data packet by decapsulating; because the destination IP address of the first data packet is the IP address of the opposite end, Therefore, the first data packet can be routed to the opposite end; after receiving the first data packet, the opposite end can confirm that the first data is from the remote UE according to the source IP address of the first data packet.

Optionally, step 609 may further include:

It should be noted that, because the fourth data packet is a data packet sent by the peer end to the remote UE, the destination IP address of the fourth data packet is the first IP address; and the PGW may be included according to the fourth data packet. The first IP address is determined, and the fourth data packet is determined to be a data packet sent by the peer end to the remote UE.

In this embodiment, the MME determines whether to establish a PDN connection between the relay UE and the PGW, and when determining to modify the PDN connection between the relay UE and the PGW, respectively, in the relay UE and the The PGW side determines a binding relationship; the relay UE and the PGW implement communication between the PGW and the remote UE according to the binding relationship; After the out-of-network state, the remote UE can continue to use the IP address used by the remote UE to perform the service in the network state and the peer end to communicate with the peer end. This solves the problem in the prior art that the remote UE is in the network state. The communication is interrupted when it becomes off-network.

Optionally, after step 609, the method may further include:

After the remote UE changes from the off-network state to the network state, the eighth message is sent to the MME, where the eighth message includes a release identifier, where the release identifier is used to instruct the PGW to release the binding Relationship

After receiving the eighth message, the MME sends a ninth message to the PGW according to the eighth message, where the ninth message includes the release identifier;

The PGW receives the ninth message sent by the MME, and releases the binding relationship.

Optionally, the eighth message may be a Service Request message or a Tracking Area Update message; and the ninth message may be a Modify Bearer Req message.

It should be noted that the relay UE may determine that the proximity communication with the remote UE has ended. Unbinding the relationship.

It should be noted that, in the embodiment, the second IP address of the relay UE is an IP address allocated by the PGW to the relay UE before the remote UE is in a disconnected state.

FIG. 7 is a flowchart of Embodiment 6 of a method for implementing service continuity according to the present invention. As shown in FIG. 7, the method in this embodiment may include:

Step 701: The remote UE sends a first message to the relay UE after the network status changes to the offline status, where the first message includes a first IP address allocated by the PGW to the remote UE, and the remote end. The identity of the UE;

It should be noted that step 701 is similar to step 601, and details are not described herein again.

Step 702: The relay UE sends a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE.

It should be noted that step 702 is similar to step 602, and details are not described herein again.

Step 703: The MME determines, according to the fourth message, whether to establish a PDN connection between the relay UE and the PGW.

It should be noted that step 703 is similar to step 603, and details are not described herein again.

Step 704: The MME sends a fifth message to the relay UE.

The fifth message includes a result identifier, where the result identifier is used to indicate that the relay UE newly establishes a PDN connection between the relay UE and the PGW.

Step 705: The relay UE sends a second message to the MME, where the second message includes the first IP address and a request identifier for indicating that the request type is a relay.

Optionally, the second message may be a PDN connection request message.

Step 706: The MME establishes a PDN connection between the relay UE and the PGW according to the second message.

Optional, mode 1:

The PDN connection request message may further include an identifier of the remote UE;

Correspondingly, the step 706 is specifically: the MME determines the context of the remote UE according to the identifier of the remote UE, and establishes the middle according to the context of the remote UE and the first IP address. Following the PDN connection between the UE and the PGW.

Method 2:

If the MME determines in step 703, the PDN between the relay UE and the PGW is newly established. After the connection, step 703 may further include:

Correspondingly, the step 706 is specifically: the MME establishes the relay UE and the PGW according to the first IP address in the PDN connection request message and the correspondence between the first IP address and the PGW. PDN connection between.

Step 707: The MME sends a third message to the PGW according to the second message, where the third message includes the first IP address.

Optionally, the third message may be a session establishment request message.

Step 708: The PGW allocates the second IP address to the relay UE, and determines a binding relationship according to the first IP address and the second IP address.

Step 709: The relay UE determines the binding relationship according to the first IP address and the second IP address.

It should be noted that, due to the newly established PDN connection between the relay UE and the PGW, the PGW newly allocates a second IP address for it (the PDN connection is established between the relay UE and the PGW) Previously, the relay UE cannot obtain the second IP address; therefore, the PGW can enable the relay UE to obtain the first manner by sending a second IP address to the relay UE. And determining an binding relationship according to the first IP address and the second IP address.

Step 710: The relay UE and the PGW implement communication between the PGW and the remote UE according to the binding relationship.

It should be noted that step 710 is similar to step 609, and details are not described herein again.

In this embodiment, the MME determines whether to establish a PDN connection between the relay UE and the PGW, and establishes a PDN connection between the relay UE and the PGW when determining that the relay UE establishes a PDN connection with the PGW. And determining, by the relay UE and the PGW, a binding relationship, where the relaying UE and the PGW implement communication between the PGW and the remote UE according to the binding relationship; After the state of the network is changed to the off-network state, the IP address used by the remote UE to perform the service in the network state and the peer end can be continuously communicated with the opposite end; The problem that the communication is interrupted when the remote UE changes from the network state to the off-network state exists in the prior art.

FIG. 8 is a schematic structural diagram of Embodiment 1 of a device for implementing service continuity according to the present invention; the device is a relay UE; as shown in FIG. 8 , the device in this embodiment may include: a transceiver module 801 and a processing module 802. The transceiver module 801 is configured to receive a first message sent by a remote UE in an off-network state, where the first message includes a first IP address that is allocated by the PGW to the remote UE, and the transceiver module 801 is further configured to: Sending, by the MME, a second message, according to the first message, to enable the MME to send a third message to the PGW, where the second message and the third message each include the first IP address; The third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the PGW The IP address of the relaying UE; the processing module 802, configured to determine the binding relationship according to the second IP address and the first IP address included in the first message received by the transceiver module 801; The transceiver module 801 is further configured to implement communication between the PGW and the remote UE by using the relay UE according to the binding relationship determined by the processing module 802.

The device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 2, and the implementation principle and technical effects are similar, and details are not described herein again.

Apparatus for implementing business continuity

Optionally, on the basis of the device embodiment 1 for implementing the service continuity of the present invention, the transceiver module 801 is specifically configured to:

Receiving, by the remote UE, a first data packet sent by proximity communication; the first data packet includes the first IP address;

Decapsulating the first data packet by using the second IP address to obtain a second data packet, according to the binding relationship;

Sending the second data packet to the PGW, so that the PGW obtains the first data packet after performing tunnel decapsulation on the second data packet.

Optionally, the transceiver module 801 is further configured to:

Receiving a third data packet sent by the PGW; the third data packet is a tunnel encapsulation of the fourth data packet sent by the PGW to the remote UE by using the second IP address according to the binding relationship. a data packet obtained afterwards; the fourth data packet includes the first IP address;

Performing tunnel decapsulation on the third data packet, obtaining the fourth data packet, and passing the proximity The communication transmits the fourth data packet to the remote UE.

Optionally, the first message may further include an identifier of the remote UE.

Correspondingly, the transceiver module 801 is further configured to:

Sending a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE, and receives a fifth message sent by the MME, where the fifth message includes a result. And the result identifier is used to indicate whether the relay UE establishes a PDN connection between the relay UE and the PGW.

Optionally, if the result identifier indicates that a PDN connection between the relay UE and the PGW is newly established, the second message is a PDN connection request message, and the third message is a session establishment request message, where The second message further includes a request identifier for indicating that the request type is a relay; or, if the result identifier indicates that a PDN connection between the relay UE and the PGW is not newly created, the second message is The resource modification request message is carried, and the third message is a bearer resource command message.

Optionally, the transceiver module 801 is specifically configured to: send the fourth message to the MME by using a ProSe Function; or send the fourth message directly to the MME.

Further, the transceiver module 801 is specifically configured to: send an eleventh message to the ProSe Function, so that the ProSe Function sends a twelfth message to the home subscription server HSS according to the eleventh message, triggering the The HSS sends a fourth message to the MME according to the twelfth message, where the eleventh message and the twelfth message both include an identifier of the remote UE and an identifier of the relay UE.

Optionally, if the processing module 802 determines that the proximity communication with the remote UE has ended, the binding relationship is released.

The device in this embodiment may be used to perform the technical solution of the relaying UE side in the method embodiment shown in FIG. 6 or FIG. 7. The implementation principle and technical effects are similar, and details are not described herein again.

FIG. 9 is a schematic structural diagram of Embodiment 2 of an apparatus for implementing service continuity according to the present invention; the apparatus is an MME; as shown in FIG. 9, the apparatus in this embodiment may include: a receiving module 901 and a sending module 902. The receiving module 901 is configured to receive a second message that is sent by the relaying UE, where the second message includes a first IP address that is allocated by the PGW to the remote UE, and the sending module 902 is configured to receive the a second message, the third message is sent to the PGW, where the third message includes the first IP address, where the third message is used by the PGW to determine a binding relationship, where the binding relationship includes Corresponding relationship between the first IP address and the second IP address, the second The IP address is an IP address assigned to the relay UE by the PGW.

The device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 3, and the implementation principle and technical effects are similar, and details are not described herein again.

10 is a schematic structural diagram of Embodiment 4 of an apparatus for implementing service continuity according to the present invention. As shown in FIG. 10, in addition to the third embodiment of the apparatus for implementing service continuity, the apparatus may further include: a processing module 903. . The receiving module 901 is further configured to receive a fourth message that is sent by the relaying UE, where the fourth message includes an identifier of the remote UE and an identifier of the relaying UE, and a processing module 903 is configured to: The fourth message received by the receiving module 901, determining whether the relay UE establishes a PDN connection between the relay UE and the PGW, and the sending module 902 is further configured to send a fifth to the relay UE. a message, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE establishes a PDN connection between the relay UE and the PGW.

Method A: Optionally, the processing module 903 is specifically configured to:

Mode B: Optionally, if the MME is different from the MME of the remote UE, the sending module 902 is further configured to send a sixth message to the MME of the remote UE, where the sixth message includes the The identifier of the remote UE;

The receiving module 901 is further configured to receive a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE, and a context of the remote UE includes each of the remote UEs The IP address of the remote UE and the IP address of the PGW in the PDN connection;

The processing module 903 is specifically configured to determine a context of the relay UE according to the identifier of the relay UE, where a context of the relay UE includes an IP address of a relay UE in each PDN connection of the relay UE, and Determining whether to create a new IP address between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE received by the receiving module 901 PDN connection.

It should be noted that, in this embodiment, the MME may determine, according to the mode A or the mode B, whether the relay UE establishes a PDN connection between the relay UE and the PGW.

Optionally, the second message is a PDN connection request message, the third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay; or

Mode 1: Optionally, the PDN connection request message further includes an identifier of the remote UE;

The processing module 903 is further configured to determine a context of the remote UE according to the identifier of the remote UE, and establish the relay UE and the location according to the context of the remote UE and the first IP address. Describe the PDN connection between PGWs.

Mode 2: Optionally, if the processing module 903 determines to establish a PDN connection between the relay UE and the PGW, the processing module 903 is further configured to add the foregoing information in the context information of the relay UE. Corresponding relationship between an IP address and the PGW; establishing the relay UE and the PGW according to the first IP address in the PDN connection request message and the correspondence between the first IP address and the PGW PDN connection between.

It should be noted that the MME may establish a PDN connection between the relay UE and the PGW according to the manner of the mode 1 or the mode 2.

Optionally, the receiving module 901 is specifically configured to receive the fourth message that is sent by the relay UE by using a proximity service function entity ProSe Function; or receive the foregoing that the relay UE sends directly to the MME Four messages.

Further, the receiving module 901 is specifically configured to receive the fourth message sent by the home subscription server HSS according to the twelfth message, where the twelfth message is sent by the ProSe Function to the relay UE. The message sent to the HSS after the eleventh message; wherein the eleventh message and the twelfth message both include an identifier of the remote UE and an identifier of the relay UE.

Optionally, the receiving module 901 is further configured to receive an eighth message that is sent by the remote UE in a network state, where the eighth message includes a release identifier, where the release identifier is used to indicate that the PGW is released. The binding relationship;

The sending module 902 is further configured to send, according to the eighth message received by the receiving module 901, the PGW Sending a ninth message, the ninth message including the release identifier.

The device in this embodiment may be used to implement the technical solution on the MME side of the method embodiment shown in FIG. 6 or FIG. 7. The implementation principle and technical effects are similar, and details are not described herein again.

FIG. 11 is a schematic structural diagram of Embodiment 5 of a device for implementing service continuity according to the present invention; the device is a PGW; as shown in FIG. 11, the device in this embodiment may include: a transceiver module 1101 and a processing module 1102. The transceiver module 1101 is configured to receive a third message sent by the MME, where the third message includes a first IP address that is allocated by the PGW to the remote UE, and the processing module 1102 is configured to receive, according to the receiving, by the transceiver module 1101. a third message, the binding relationship is determined, the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the relay UE by the PGW The transceiver module 1101 is further configured to implement communication between the PGW and the remote UE by using the relay UE according to the binding relationship determined by the processing module 1102.

The device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 4, and the implementation principle and technical effects are similar, and details are not described herein again.

Apparatus for implementing business continuity

Optionally, the third message is a bearer resource command message or a session establishment request message, where the third message is a session establishment request message, if the third message is a session establishment request message, Module 1102, specifically for:

Allocating the second IP address to the relay UE;

Optionally, the transceiver module 1101 is specifically configured to:

Receiving, by the relay UE, a second data packet, where the second data packet is a data packet obtained by tunneling the first data packet by the relay UE according to the second IP address; The data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address;

And performing tunnel decapsulation on the second data packet to obtain the first data packet.

Optionally, the transceiver module 1101 is further configured to:

Performing tunnel encapsulation on the fourth data packet to be sent to the remote UE according to the second IP address, obtaining a third data packet, and forwarding the third data packet to the relay UE, so that the The relaying UE performs tunnel decapsulation on the third data packet to obtain the fourth data packet, and the The fourth data packet is sent to the remote UE by proximity communication.

Optionally, the transceiver module 1101 is further configured to receive the ninth message sent by the MME, where the ninth message includes a de-identification, where the de-identification is used to instruct the PGW to cancel the binding relationship;

The processing module 1102 is further configured to cancel the binding relationship according to the ninth message received by the transceiver module 1101.

The device in this embodiment can be used to implement the technical solution on the PGW side of the method embodiment shown in FIG. 6 and FIG. 7. The implementation principle and technical effects are similar, and details are not described herein again.

FIG. 12 is a schematic structural diagram of Embodiment 7 of a device for implementing service continuity according to the present invention; the remote UE; as shown in FIG. 12, the device in this embodiment may include: a processing module 1201 and a sending module 1202. The processing module 1201 is configured to determine that the remote UE changes from the in-network state to the off-network state, and the sending module 1202 is configured to: when the processing module 1201 determines that the remote UE becomes the off-network state, The UE sends a first message, so that the relay UE determines a binding relationship according to the first message, where the first message includes a first IP address allocated by the PGW to the remote UE.

The device in this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 5, and the implementation principle and technical effects are similar, and details are not described herein again.

Apparatus for implementing business continuity Example 8

Optionally, the first message further includes the identifier of the remote UE, based on the seventh embodiment of the device for implementing the service continuity.

Optionally, the sending module 1202 is further configured to:

The device in this embodiment may be used to perform the technical solution on the remote UE side of the method embodiment shown in FIG. 6 and FIG. 7. The implementation principle and technical effects are similar, and details are not described herein again.

The present invention further provides a system for implementing service continuity, the system comprising: a device for implementing service continuity, a relay UE according to Embodiment 1 or Embodiment 2, and a device embodiment 3 or an embodiment for implementing service continuity. The remote MME described in Embodiment 7 or Embodiment 8 of the MME, the device for implementing the service continuity, or the PGW and the current service continuity.

The system of this embodiment can be used to implement the technical solution of the method embodiment shown in FIG. 6 and FIG. The implementation principle and technical effect are similar, and will not be described here.

FIG. 13 is a schematic structural diagram of Embodiment 9 of a device for implementing service continuity according to the present invention; the device is a relay UE; as shown in FIG. 13, the device in this embodiment may include: a transceiver 1301 and a processor 1302. The transceiver 1301 is configured to receive a first message sent by a remote UE in an off-network state, where the first message includes a first IP address allocated by the PGW to the remote UE, and the transceiver 1301 is further configured to: Sending, according to the first message, a second message to the mobility management entity MME, so that the MME sends a third message to the PGW, where the second message and the third message each include the first IP An address, where the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is The IP address of the PGW is allocated to the relay UE; the processor 1302 is configured to determine the binding relationship according to the first IP address and the second IP address; the processor 1302 is further configured to perform The binding relationship is implemented, and communication between the PGW and the remote UE is implemented by the relay UE.

Apparatus for implementing business continuity

Optionally, the transceiver 1301 is further configured to receive, by the remote UE, the first data packet sent by the remote UE by using the neighboring communication, where the first data packet includes The first IP address;

The processor 1302 is configured to perform tunnel encapsulation on the first data packet by using the second IP address according to the binding relationship, to obtain a second data packet.

The transceiver 1301 is further configured to send the second data packet to the PGW, so that the PGW obtains the first data packet after performing tunnel decapsulation on the second data packet.

Optionally, the transceiver 1301 is further configured to receive a third data packet sent by the PGW, where the third data packet is sent by the PGW according to the binding relationship by using the second IP address pair. a data packet obtained after tunnel encapsulation of the fourth data packet of the remote UE; the fourth data packet includes the first IP address;

The processor 1302 is further configured to perform tunnel decapsulation on the third data packet to obtain the fourth data packet.

The transceiver 1301 is further configured to send the fourth data packet to the remote end by using proximity communication UE.

Correspondingly, the transceiver 1301 is further configured to:

Sending a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE, and receives a fifth message sent by the MME, where the fifth message includes a result. And the result identifier is used to indicate whether the relay UE establishes a packet data network PDN connection between the relay UE and the PGW.

Optionally, if the result identifier indicates that a PDN connection between the relay UE and the PGW is newly established, the second message is a PDN connection request message, and the third message is a session establishment request message, where The second message further includes a request identifier for indicating that the request type is a relay;

Or, if the result identifier indicates that the second message of the relaying UE is not newly created, the third message is a bearer resource command message.

Optionally, the transceiver 1301 is specifically configured to: send the fourth message to the MME by using a ProSe Function; or send the fourth message directly to the MME.

Further, the transceiver 1301 is specifically configured to: send an eleventh message to the ProSe Function, so that the ProSe Function sends a twelfth message to the home subscription server HSS according to the eleventh message, triggering the HSS Transmitting, by the twelfth message, a fourth message to the MME, where the eleventh message and the twelfth message each include an identifier of the remote UE and an identifier of the relay UE.

Optionally, if the processor 1302 determines that the proximity communication with the remote UE has ended, the binding relationship is cancelled.

FIG. 14 is a schematic structural diagram of Embodiment 11 of the device for implementing service continuity according to the present invention; the device is an MME; as shown in FIG. 14, the device in this embodiment may include: a first communication interface 1401, a processor 1402, and a Two communication interfaces 1403. The first communication interface 1401 is configured to receive a second message sent by the relay user equipment UE, where the second message includes a first IP address allocated by the PGW to the remote UE, and the processor 1402 is configured to perform according to the first The second message received by the communication interface 1401 generates a third message, the third message includes the first IP address, and the second communication interface 1403 is configured to send the third message generated by the processor 1402 to The PGW; wherein, the The third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the PGW The IP address of the relay UE.

Apparatus for implementing business continuity

Optionally, the first communication interface 1401 is further configured to receive a fourth message sent by the relay UE, where the fourth message includes the The identifier of the remote UE and the identifier of the relay UE; the processor 1402, configured to determine, according to the fourth message received by the first communication interface 1401, whether the relay UE establishes the relay UE and the a packet data network PDN connection between the PGWs, and generating a fifth message, wherein the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates the relay UE and the PGW The first communication interface 1401 is further configured to send the fifth message generated by the processor 1402 to the relay UE.

Method A: Optionally, the processor 1402 is specifically configured to:

Determining, according to the identifier of the remote UE, a context of the remote UE, where the context of the remote UE includes an IP address of a remote UE and an IP address of a PGW in each packet data network PDN of the remote UE;

Mode B: Optionally, if the MME is different from the MME of the remote UE, the device further includes a third communication interface, and the third communication interface is configured to send the sixth message to the MME of the remote UE. a message, the sixth message includes an identifier of the remote UE, and a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE, and the remote UE The context includes an IP address of the remote UE and an IP address of the PGW in each PDN connection of the remote UE;

The processor 1402 is specifically configured to determine, according to the identifier of the relay UE, the relay UE The context of the relay UE includes the IP address of the relay UE and the IP address of the PGW in each PDN connection of the relay UE, and the context of the remote UE received according to the third communication interface. Determining, by the context of the relaying UE, whether to establish a PDN connection between the relay UE and the PGW.

Optionally, the second message is a PDN connection request message, the third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay; or The second message is a bearer resource modification request message, and the third message is a bearer resource command message.

The processor 1402 is further configured to determine a context of the remote UE according to the identifier of the remote UE, and establish the relay UE and the location according to the context of the remote UE and the first IP address. Describe the PDN connection between PGWs.

Mode 2: Optionally, if the processor 1402 determines to establish a PDN connection between the relay UE and the PGW, the processor 1402 is further configured to:

Optionally, the first communication interface 1401 is configured to receive the fourth message sent by the relay UE by using a proximity service function entity ProSe Function; or receive the location that the relay UE directly sends to the MME The fourth message.

Further, the first communication interface 1401 is configured to receive the fourth message sent by the home subscription server HSS according to the twelfth message, where the twelfth message is that the ProSe Function receives the relay UE. The message sent to the HSS after the eleventh message is sent; wherein the eleventh message and the twelfth message both include an identifier of the remote UE and an identifier of the relay UE.

Optionally, the first communication interface 1401 is further configured to receive an eighth message sent by the remote UE in a network state, where the eighth message includes a release identifier, where the release identifier is used to refer to The PGW is shown to release the binding relationship; according to the eighth message, a ninth message is sent to the PGW, where the ninth message includes the release identifier.

FIG. 15 is a schematic structural diagram of Embodiment 13 of the device for implementing service continuity according to the present invention; the device is a PGW; as shown in FIG. 15, the device in this embodiment may include: a communication interface 1501 and a processor 1502. The communication interface 1501 is configured to receive a third message sent by the mobility management entity MME, where the third message includes a first IP address that is allocated by the PGW to the remote UE, and the processor 1502 is configured to use the communication interface 1501. Receiving the third message, determining a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the PGW Relaying the IP address of the UE; the processor 1502 is further configured to implement, by using the relay UE, communication between the PGW and the remote UE according to the binding relationship.

Apparatus for implementing business continuity

Optionally, the third message is a bearer resource command message or a session establishment request message, where the third message is a session establishment request message, if the third message is a session establishment request message, The processor 1502 is specifically configured to:

Allocating the second IP address to the relay UE;

Optionally, the communication interface 1501 is further configured to receive a second data packet sent by the relay UE, where the second data packet is used by the relay UE to tunnel the first data packet according to the second IP address. a data packet obtained after the encapsulation; the first data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address;

The processor 1502 is specifically configured to perform tunnel decapsulation on the second data packet to obtain the first data packet.

Optionally, the processor 1502 is further configured to perform tunnel encapsulation on the fourth data packet to be sent to the remote UE according to the second IP address, to obtain a third data packet.

The communication interface 1501 is further configured to forward the third data packet to the relay UE, so that the relay UE obtains the fourth data packet after performing tunnel decapsulation on the third data packet, and Will The fourth data packet is sent to the remote UE by proximity communication.

Optionally, the communication interface 1501 is further configured to receive the ninth message sent by the MME, where the ninth message includes a de-identification, where the de-identification is used to instruct the PGW to cancel the binding relationship;

The processor 1502 is further configured to release the binding relationship according to the ninth message received by the communication interface 1501.

FIG. 16 is a schematic structural diagram of Embodiment 15 of the apparatus for implementing service continuity according to the present invention; the remote UE; as shown in FIG. 16, the apparatus in this embodiment may include: a processor 1601 and a transmitter 1602. The processor 1601 is configured to determine that the remote UE changes from the in-network state to the off-network state, and the transmitter 1602 is configured to: when the processor 1601 determines that the remote UE becomes the off-network state, The UE sends a first message, so that the relay UE determines a binding relationship according to the first message, where the first message PGW is allocated to the first IP address of the remote UE.

Apparatus for implementing business continuity

Optionally, on the basis of the fifteenth embodiment of the device for implementing the service continuity of the present invention, the first message further includes an identifier of the remote UE.

Optionally, the transmitter 1602 is further configured to:

One of ordinary skill in the art will appreciate that all or part of the steps to implement the various method embodiments described above may be accomplished by hardware associated with the program instructions. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

A method for implementing business continuity, the method comprising:

The relay user equipment UE receives the first message sent by the remote UE in the off-network state, where the first message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

The relaying UE sends a second message to the mobility management entity MME according to the first message, so that the MME sends a third message to the PGW, where the second message and the third message are both included. The first IP address, wherein the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the The second IP address is an IP address assigned to the relay UE by the PGW;

The relaying UE determines the binding relationship according to the first IP address and the second IP address, and implements the PGW and the remote end by using the relay UE according to the binding relationship. Communication between UEs.
The method according to claim 1, wherein the relaying UE performs communication between the PGW and the remote UE according to the binding relationship, including:

Receiving, by the relay UE, the first data packet that is sent by the remote UE by using the proximity communication; the first data packet includes the first IP address; and the relay UE adopts the The second IP address tunnel encapsulates the first data packet to obtain a second data packet; the relay UE sends the second data packet to the PGW, so that the PGW pairs the second data Obtaining the first data packet after the packet is decapsulated by the tunnel; and/or,

The relaying UE receives the third data packet sent by the PGW; the third data packet is the fourth that the PGW sends the second IP address pair to the remote UE according to the binding relationship. a data packet obtained after the tunnel is encapsulated by the data packet; the fourth data packet includes the first IP address; and the relay UE performs tunnel decapsulation on the third data packet to obtain the fourth data packet. And transmitting the fourth data packet to the remote UE by using proximity communication.
The method according to claim 1 or 2, wherein the first message further includes an identifier of the remote UE;

The relaying UE, before sending the second message to the MME according to the first message, further includes:

The relaying UE sends a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE;

Receiving, by the relay UE, a fifth message sent by the MME, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates the relay UE and the PGW. Inter-packet data network PDN connection.
The method according to claim 3, wherein, if the result identifier indicates that a PDN connection between the relay UE and the PGW is newly established, the second message is a PDN connection request message, where the The third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay;

Or, if the result identifier indicates that the PDN connection between the relay UE and the PGW is not newly created, the second message is a bearer resource modification request message, and the third message is a bearer resource command message.
The method according to claim 3 or 4, wherein the relaying the UE sends a fourth message to the MME, including:

Transmitting, by the relay UE, the fourth message to the MME by using a proximity service function entity ProSe Function; or

The relay UE directly sends the fourth message to the MME.
The method according to claim 5, wherein the relaying the UE sends the fourth message to the MME by using a ProSe Function, including:

The relay UE sends an eleventh message to the ProSe Function;

The ProSe Function sends a twelfth message to the home subscription server HSS according to the eleventh message;

Sending, by the HSS, the fourth message to the MME according to the twelfth message;

The eleventh message and the twelfth message each include an identifier of the remote UE and an identifier of the relay UE.
The method according to any one of claims 1 to 6, wherein if the relay UE determines that the proximity communication with the remote UE has ended, the relay UE releases the binding relationship.
A method for implementing business continuity, the method comprising:

The mobility management entity MME receives the second message sent by the relay user equipment UE, where the second message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

The MME sends a third message to the PGW according to the second message, where the third message includes the first IP address, where the third message is used by the PGW to determine a binding relationship. The binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is an IP address allocated by the PGW to the relay UE.
The method according to claim 8, wherein before the MME receives the second message sent by the relaying UE, the method further includes:

Receiving, by the MME, a fourth message sent by the relaying UE, where the fourth message includes an identifier of the remote UE and an identifier of the relaying UE;

Determining, according to the fourth message, whether to establish a packet data network PDN connection between the relay UE and the PGW according to the fourth message;

Sending, by the MME, a fifth message to the relay UE, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates a new connection between the relay UE and the PGW. PDN connection.
The method according to claim 9, wherein the MME determines, according to the fourth message, whether to establish a PDN connection between the relay UE and the PGW, including:

Determining, by the MME, the context of the remote UE according to the identifier of the remote UE, where the context of the remote UE includes an IP address of a remote UE and an IP address of a PGW in each PDN connection of the remote UE;

Determining, by the MME, the context of the relay UE according to the identifier of the relay UE, where the context of the relay UE includes an IP address of a relay UE and an IP address of a PGW in each PDN connection of the relay UE ;

The MME determines whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE.
The method according to claim 10, wherein if the MME is different from the MME of the remote UE, the MME determines the context of the remote UE according to the identifier of the remote UE, including:

Sending, by the MME, a sixth message to the MME of the remote UE, where the sixth message includes an identifier of the remote UE;

The MME receives a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE.
The method according to any one of claims 9 to 11, wherein the second message is a PDN connection request message, the third message is a session establishment request message, and the second message is further Include a request identifier indicating that the request type is a relay; or,

The second message is a bearer resource modification request message, and the third message is a bearer resource command message.
The method according to claim 12, wherein the PDN connection request message further includes an identifier of the remote UE;

After the MME receives the second message sent by the relaying UE, the MME further includes:

Determining, by the MME, the context of the remote UE according to the identifier of the remote UE, and establishing, between the relay UE and the PGW, according to the context of the remote UE and the first IP address. PDN connection.
The method according to claim 12, wherein if the MME determines to establish a PDN connection between the relay UE and the PGW, the method further includes:

The MME adds a correspondence between the first IP address and the PGW in the context information of the relay UE.

After the MME receives the second message sent by the relaying UE, the MME further includes:

The MME establishes a PDN connection between the relay UE and the PGW according to the first IP address in the PDN connection request message and the correspondence between the first IP address and the PGW.
The method according to any one of claims 9 to 14, wherein the MME receives the fourth message sent by the relay UE, including:

Receiving, by the MME, the fourth message sent by the relay UE by using a proximity service function entity ProSe Function; or

The MME receives the fourth message that the relay UE sends directly to the MME.
The method according to claim 15, wherein the MME receives the fourth message sent by the relay UE by using a ProSe Function, including:

The MME receives the fourth message sent by the home subscription server HSS according to the twelfth message, and the twelfth message is that the ProSe Function receives the eleventh message sent by the relay UE, and then sends the message to the HSS. And the sent message, wherein the eleventh message and the twelfth message both include an identifier of the remote UE and an identifier of the relay UE.
The method according to any one of claims 8 to 16, after the MME receives the second message sent by the relaying UE, the method further includes:

Receiving, by the MME, an eighth message that is sent by the remote UE in a network state, where the eighth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

And sending, by the MME, a ninth message to the PGW according to the eighth message, where the ninth message includes the release identifier.
A method for implementing business continuity, the method comprising:

The packet data gateway PGW receives the third message sent by the mobility management entity MME, where the third message includes the first Internet Protocol IP address allocated by the PGW to the remote user equipment UE;

Determining, by the PGW, the binding relationship according to the third message, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is allocated to the PGW Relaying the IP address of the UE;

The PGW implements communication between the PGW and the remote UE by using the relay UE according to the binding relationship.
The method according to claim 18, wherein the third message is a bearer resource command message or a session establishment request message; if the third message is a session establishment request message, the PGW is according to the third The message, before determining the binding relationship, also includes:

Assigning, by the PGW, the second IP address to the relay UE;

Correspondingly, the PGW determines the binding relationship according to the third message, and the PGW determines the binding relationship according to the first IP address and the second IP address.
The method according to claim 18 or 19, wherein the PGW implements communication between the PGW and the remote UE by using the relay UE according to the binding relationship, including:

Receiving, by the PGW, the second data packet sent by the relay UE, where the second data packet is a data packet obtained by tunneling the first data packet by the relay UE according to the second IP address; The first data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address, and the PGW performs tunnel decapsulation on the second data packet to obtain the first data packet. a data packet; and/or,

Decoding, by the PGW, the fourth data packet to be sent to the remote UE according to the second IP address, obtaining a third data packet, and forwarding the third data packet to the relay UE, And causing the relay UE to perform tunnel decapsulation on the third data packet to obtain the fourth data packet, where And transmitting the fourth data packet to the remote UE by using proximity communication.
The method according to any one of claims 18 to 20, wherein after the PGW implements communication between the PGW and the remote UE by using the relay UE according to the binding relationship, Also includes:

The PGW receives the ninth message sent by the MME, where the ninth message includes a de-identification; wherein the de-identification is used to instruct the PGW to cancel the binding relationship;

The PGW cancels the binding relationship according to the ninth message.
A method for implementing business continuity, the method comprising:

The remote user equipment UE determines that the remote UE changes from the in-network state to the off-network state;

The remote UE sends a first message to the relay UE, so that the relay UE determines a binding relationship according to the first message, where the first message includes a packet data gateway PGW assigned to the remote end The first IP address of the UE.
The method according to claim 22, wherein the first message further comprises an identifier of the remote UE.
The method according to claim 22 or 23, wherein after the remote UE sends the first message to the relay UE, the method further includes:

After the remote UE changes from the off-network state to the network state, the eighth message is sent to the mobility management entity MME, where the eighth message includes a release identifier, where the release identifier is used to indicate that the PGW is removed. Describe the binding relationship.
An apparatus for implementing service continuity, characterized in that the apparatus is a relay user equipment UE; the apparatus comprises:

a transceiver module, configured to receive a first message sent by a remote UE in an off-network state, where the first message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

The transceiver module is further configured to send, according to the first message, a second message to the mobility management entity MME, so that the MME sends a third message, the second message, and the third message to the PGW. The message includes the first IP address, where the third message is used by the PGW to determine a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, The second IP address is an IP address allocated by the PGW to the relay UE;

a processing module, configured to receive, according to the second IP address, the first cancellation received by the transceiver module Determining the binding relationship by the first IP address included in the information;

The transceiver module is further configured to implement communication between the PGW and the remote UE by using the relay UE according to the binding relationship determined by the processing module.
The device according to claim 25, wherein the transceiver module is specifically configured to:

Receiving, by the remote UE, the first data packet sent by the proximity communication; the first data packet includes the first IP address; and according to the binding relationship, using the second IP address to the first data The packet is tunnel encapsulated to obtain a second data packet, and the second data packet is sent to the PGW, so that the PGW obtains the first data packet after performing tunnel decapsulation on the second data packet; and /or,

Receiving a third data packet sent by the PGW; the third data packet is a tunnel encapsulation of the fourth data packet sent by the PGW to the remote UE by using the second IP address according to the binding relationship. a data packet obtained afterwards; the fourth data packet includes the first IP address; tunnel decapsulating the third data packet, obtaining the fourth data packet, and the fourth data by proximity communication The packet is sent to the remote UE.
The apparatus according to claim 25 or 26, wherein the first message further comprises an identifier of the remote UE;

The transceiver module is further configured to: send a fourth message to the MME, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE, and receives a fifth message sent by the MME; The fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE establishes a packet data network PDN connection between the relay UE and the PGW.
The device according to claim 27, wherein, if the result identifier indicates that a PDN connection between the relay UE and the PGW is newly established, the second message is a PDN connection request message, where the The third message is a session establishment request message, and the second message further includes a request identifier for indicating that the request type is a relay;

Or, if the result identifier indicates that the PDN connection between the relay UE and the PGW is not newly created, the second message is a bearer resource modification request message, and the third message is a bearer resource command message.
The device according to claim 27 or 28, wherein the transceiver module is specifically configured to:

Transmitting the fourth message to the MME by using a proximity service function entity ProSe Function; or,

Sending the fourth message directly to the MME.
The device according to claim 29, wherein the transceiver module is specifically configured to:

Sending an eleventh message to the ProSe Function, so that the ProSe Function sends a twelfth message to the home subscription server HSS according to the eleventh message, triggering the HSS to send the PDCCH according to the twelfth message. Sending a fourth message, where the eleventh message and the twelfth message each include an identifier of the remote UE and an identifier of the relay UE.
The apparatus according to any one of claims 25 to 30, wherein the binding relationship is released if the processing module determines that the proximity communication with the remote UE has ended.
An apparatus for implementing service continuity, characterized in that the apparatus is a mobility management entity MME; the apparatus comprises:

a receiving module, configured to receive a second message sent by the relay user equipment UE, where the second message includes a first Internet Protocol IP address allocated by the packet data gateway PGW to the remote UE;

a sending module, configured to send, according to the second message received by the receiving module, a third message to the PGW, where the third message includes the first IP address, where the third message is used by the The PGW determines a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second IP address is an IP address allocated by the PGW to the relay UE. .
The device according to claim 32, wherein the device further comprises: a processing module;

The receiving module is further configured to receive a fourth message sent by the relay UE, where the fourth message includes an identifier of the remote UE and an identifier of the relay UE;

The processing module is configured to determine, according to the fourth message received by the receiving module, whether to establish a packet data network PDN connection between the relay UE and the PGW;

The sending module is further configured to send a fifth message to the relay UE, where the fifth message includes a result identifier, where the result identifier is used to indicate whether the relay UE creates the new relay UE and PDN connection between the PGWs.
The device according to claim 33, wherein the processing module is specifically configured to:

Determine a context of the remote UE according to the identifier of the remote UE, where the context of the remote UE includes an IP address of a remote UE and an IP address of a PGW in each PDN connection of the remote UE;

Determining, according to the identifier of the relay UE, a context of the relay UE, where the context of the relay UE includes an IP address of a relay UE and an IP address of a PGW in each PDN connection of the relay UE;

Determining whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE.
The device according to claim 33, wherein, if the MME is different from the MME of the remote UE, the sending module is further configured to: send a sixth message to the MME of the remote UE, where The sixth message includes an identifier of the remote UE;

The receiving module is further configured to receive a seventh message sent by the MME of the remote UE, where the seventh message includes a context of the remote UE, and a context of the remote UE includes the remote UE The IP address of the remote UE and the IP address of the PGW in each PDN connection;

The processing module is specifically configured to determine a context of the relay UE according to an identifier of the relay UE, where a context of the relay UE includes an IP address of a relay UE in each PDN connection of the relay UE And determining, by the IP address of the PGW, whether to establish a PDN connection between the relay UE and the PGW according to the context of the remote UE and the context of the relay UE received by the receiving module.
The device according to any one of claims 33 to 35, wherein the second message is a PDN connection request message, the third message is a session establishment request message, and the second message further includes The request type is a request ID of the relay; or,

The second message is a bearer resource modification request message, and the third message is a bearer resource command message.
The apparatus according to claim 36, wherein the PDN connection request message further includes an identifier of the remote UE;

The processing module is further configured to determine a context of the remote UE according to the identifier of the remote UE, and establish the relay UE according to a context of the remote UE and the first IP address. PDN connection between the PGWs.
The device according to claim 36, wherein the processing module is further configured to: if the processing module determines to establish a PDN connection between the relay UE and the PGW, the processing module is further configured to:

Adding a correspondence between the first IP address and the PGW in the context information of the relay UE; according to the first IP address and the first IP address in the PDN connection request message Establishing a PDN connection between the relay UE and the PGW in a corresponding relationship with the PGW.
The device according to any one of claims 33 to 38, wherein the receiving module is specifically configured to:

Receiving, by the relay UE, the fourth message sent by the proximity service function entity ProSe Function; or

Receiving the fourth message that the relay UE sends directly to the MME.
The device according to claim 39, wherein the receiving module is specifically configured to:

Receiving the fourth message sent by the home subscription server HSS according to the twelfth message, where the twelfth message is a message sent by the ProSe Function to the HSS after receiving the eleventh message sent by the relay UE The eleventh message and the twelfth message each include an identifier of the remote UE and an identifier of the relay UE.
Apparatus according to any one of claims 32 to 40, wherein

The receiving module is further configured to receive an eighth message that is sent by the remote UE in a network state, where the eighth message includes a release identifier, where the release identifier is used to instruct the PGW to release the binding Relationship

The sending module is further configured to send a ninth message to the PGW according to the eighth message received by the receiving module, where the ninth message includes the release identifier.
An apparatus for implementing business continuity, characterized in that the apparatus is a packet data gateway PGW; the apparatus comprises:

a transceiver module, configured to receive a third message sent by the mobility management entity MME, where the third message includes a first Internet Protocol IP address that is allocated by the PGW to the remote user equipment UE;

a processing module, configured to determine, according to the third message received by the transceiver module, a binding relationship, where the binding relationship includes a correspondence between the first IP address and a second IP address, where the second The IP address is an IP address assigned to the relay UE by the PGW;

The transceiver module is further configured to implement communication between the PGW and the remote UE by using the relay UE according to the binding relationship determined by the processing module.
The device according to claim 42, wherein the third message is a bearer resource command message or a session establishment request message;

If the third message is a session establishment request message, the processing module is specifically configured to:

Allocating the second IP address to the relay UE;

Determining a binding relationship according to the first IP address and the second IP address.
The device according to claim 42 or 43, wherein the transceiver module is specifically configured to:

Receiving, by the relay UE, a second data packet, where the second data packet is a data packet obtained by tunneling the first data packet by the relay UE according to the second IP address; The data packet is a data packet sent by the remote UE, and the first data packet includes the first IP address, and the second data packet is tunnel decapsulated to obtain the first data packet; and/ or,

Performing tunnel encapsulation on the fourth data packet to be sent to the remote UE according to the second IP address, obtaining a third data packet, and forwarding the third data packet to the relay UE, so that the The relay UE obtains the fourth data packet after performing tunnel decapsulation on the third data packet, and sends the fourth data packet to the remote UE by using proximity communication.
A device according to any one of claims 42 to 44, wherein

The transceiver module is further configured to receive a ninth message sent by the MME, where the ninth message includes a release identifier, where the release identifier is used to instruct the PGW to cancel the binding relationship;

The processing module is further configured to cancel the binding relationship according to the ninth message received by the transceiver module.
An apparatus for implementing service continuity, wherein the apparatus is a remote user equipment UE; the apparatus includes:

a processing module, configured to determine that the remote UE changes from a network state to a disconnection state;

a sending module, configured to send, by the processing module, the first message to the relay UE, when the processing module determines that the remote UE becomes an off-network state, so that the relay UE determines a binding relationship according to the first message; The first message includes a first IP address allocated by the packet data gateway PGW to the remote UE.
The apparatus according to claim 46, wherein the first message further comprises an identifier of the remote UE.
The device according to claim 46 or 47, wherein the sending module is further configured to:

After the remote UE changes from the off-network state to the network state, the eighth message is sent to the mobility management entity MME, where the eighth message includes a release identifier, where the release identifier is used to indicate that the PGW is removed. Describe the binding relationship.
A system for implementing business continuity, characterized in that the system comprises: the relay user equipment UE according to any one of claims 25 to 31, and the mobility management entity according to any one of claims 32 to 41. The MME, the packet data gateway PGW according to any one of claims 42 to 45, and the remote UE according to any one of claims 46 to 48.