WO2015054850A1

WO2015054850A1 - Communication method, communication device, and communication system

Info

Publication number: WO2015054850A1
Application number: PCT/CN2013/085334
Authority: WO
Inventors: 何宁; 朱雷; 熊春山; 麦肯·彼得
Original assignee: 华为技术有限公司
Priority date: 2013-10-16
Filing date: 2013-10-16
Publication date: 2015-04-23
Also published as: CN105264956A

Abstract

Provided are a communication method, a communication device, and a communication system. In the communication method, a first local gateway (L-GW) receives a create session request, said request carrying an address identifier of a second L-GW or an address identifier of a packet data network gateway (P-GW); the first L-GW, according to the create session request, establishes a connection with the second L-GW or with the P-GW, thereby completing the connection between the first L-GW and the second L-GW, or completing the connection between the first L-GW and the P-GW; the first L-GW sends a create session response, thus switching a UE between different networks.

Description

Communication method, communication device and communication system

TECHNICAL FIELD The present invention relates to communication technologies, and in particular, to a communication method, a communication device, and a communication system. The existing Evolved Packet System (hereinafter referred to as EPS) architecture is centralized mobility management. In the EPS architecture, when the terminal device UE initially attaches, the UE sends the attachment request information to the base station eNB of the cell in which it is located. Then, the eNB selects a Mobility Management Entity (hereinafter referred to as MME) to which the UE can attach according to the attach request information, and selects, by the MME, a Serving Gateway (hereinafter referred to as S-GW) and a packet that can be attached. A Packet Data Network Gateway (P-GW), and the P-GW allocates an IP address to the UE, that is, an EPS bearer is established between the UE and the P-GW, and is considered to be an EPS default bearer.

If the P-GW fails or has a security problem, it will cause a single point of failure and a single point of security in the communication system. Therefore, the Distributed Mobility Management (DMM) network is introduced, that is, a local gateway (hereinafter referred to as L_GW) corresponding to the base station is set for each base station of the existing EPS network. Or, an L_GW corresponding to the multiple base stations is set for multiple base stations of the existing EPS network.

However, the user equipment UE cannot perform network switching in the scenario where the EPS network and the D network coexist, or in the scenario of the D匪 network of different cells. SUMMARY OF THE INVENTION The embodiments of the present invention provide a communication method, a communication device, and a communication system, which can perform network switching in a scenario where an EPS network and a D-network coexist, or in a scenario of a D-network of a different cell.

In a first aspect, an embodiment of the present invention provides a communication method, including: The first local gateway L-GW receives the create session request, where the create session request carries the address identifier of the second L-GW or the address identifier of the packet data network gateway P-GW, the second L-GW, the The P-GW is connected before the user equipment UE switches to the first L-GW, and the UE is currently connected to the first L-GW;

The first L-GW establishes with the second L-GW or the according to the create session request

a connection between P-GWs;

The first L-GW sends a create session response.

In a first possible implementation manner, the first local gateway L-GW receives a create session request, including:

The first L-GW receives a create session request sent by the first base station corresponding to the first L-GW, where the create session request includes an address identifier of the second L-GW;

And establishing, by the first L-GW, a connection with the second L-GW or the P-GW according to the creating a session request, including:

Establishing, by the first L-GW, a connection with the second L-GW according to the creation session request;

The first L-GW sends a create session response, including:

The first L-GW sends a create session response to the first base station.

In a second possible implementation, the first local gateway L-GW receives the create session request, including:

The first L-GW receives a create session request sent by the first mobility management entity MME corresponding to the first L-GW, where the create session request includes an address identifier of the second L-GW; The first L-GW establishes a connection with the second L-GW or the P-GW according to the creation session request, and includes:

The first L-GW sends a create session response, including:

The first L-GW sends a create session response to the first MME.

In a third possible implementation, the first local gateway L-GW receives the create session request, including:

The first L-GW receives a creation session sent by the first base station corresponding to the first L-GW Requesting, the creating a session request includes an address identifier of the P-GW;

The first L-GW establishes a connection with the P-GW according to the create session request; the first L-GW sends a create session response, including:

The first L-GW sends a create session response to the first base station.

In a fourth possible implementation, the first local gateway L-GW receives the create session request, including:

The first L-GW receives a create session request sent by the first mobility management entity MME corresponding to the first L-GW, where the create session request includes an address identifier of the P-GW; And establishing, by the L-GW, a connection with the second L-GW or the P-GW according to the creating a session request, including:

The first L-GW sends a create session response to the first MME.

With reference to any one of the first aspect to the second possible implementation of the first aspect, in a fifth possible implementation, the first L-GW establishes a The connection between the second L-GW or the P-GW includes:

Sending, by the first L-GW, a proxy binding update or modifying a bearer request to the second L-GW; the first L-GW receiving a proxy binding response or modifying a bearer response sent by the second L-GW .

With reference to the first aspect, the third possible implementation of the first aspect, or the fourth possible implementation of the first aspect, in a sixth possible implementation, the first L-GW Establishing a connection with the second L-GW or the P-GW according to the creating a session request, including:

Transmitting, by the first L-GW, a proxy binding update or modifying a bearer request to the P-GW; the first L-GW receiving a proxy binding response or modifying a bearer response sent by the P-GW. In a second aspect, an embodiment of the present invention provides a communication method, including:

The second local gateway L-GW receives the proxy binding update or modify the bearer request, and the second L-GW connects to the first L-GW or the packet data network gateway P_GW before the user equipment UE switches Pick up

The second L-GW establishes a connection with the first L-GW or the P-GW according to the proxy binding update or modify bearer request;

The second L-GW sends a proxy binding response or a modified bearer response.

In a first possible implementation, the second local gateway L-GW receives the proxy binding update or modify the bearer request, including:

The second local gateway L-GW receives the proxy binding update sent by the first L-GW or modifies the bearer request;

The second L-GW establishes a bearer with the first L-GW or the P-GW according to the proxy binding update or modify the bearer request, and includes:

The second L-GW establishes a connection with the first L-GW according to the proxy binding update or modify bearer request;

Sending, by the second L-GW, a proxy binding response or modifying a bearer response, including:

The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW. In a second possible implementation, the second local gateway L-GW receives the proxy binding update or modify the bearer request, including:

Receiving, by the second local gateway, the proxy binding update or modifying the bearer request sent by the P-GW;

The second L-GW establishes a connection with the first L-GW or the P-GW according to the proxy binding update or modify bearer request, and includes:

The second L-GW establishes a connection with the P-GW according to the proxy binding update or modify bearer request;

The second L-GW sends a proxy binding response or a modified bearer response to the P-GW.

With reference to the second aspect, the first possible implementation manner of the second aspect, in a third possible implementation, after the sending, by the second L-GW, the proxy binding response or modifying the bearer response, the method further includes:

The second local gateway L-GW receives the proxy binding update or delete session request sent by the first L-GW;

The second L-GW deletes a connection with the first L-GW; The second L-GW sends a proxy binding response or a delete session response to the first L-GW. With the second aspect or the second possible implementation of the second aspect, in a fourth possible implementation, after the sending, by the second L-GW, the proxy binding response or modifying the bearer response, the method further includes:

The second local gateway L-GW receives the proxy binding update or delete session request sent by the P-GW;

The second L-GW deletes a connection with the P-GW;

The second L-GW sends a proxy binding response or a delete session response to the P-GW.

In a third aspect, an embodiment of the present invention provides a communication method, including:

The second local gateway L-GW receives the proxy binding update or deletes the session request;

The second L-GW deletes the connection with the first L-GW or the connection with the packet data network gateway P-GW, where the first L-GW is currently connected by the user equipment UE, a second L-GW or the P-GW connected before the UE is connected to the first L-GW;

The second L-GW sends a proxy binding response or deletes a session response.

In a first possible implementation manner, the second local gateway L-GW receives the proxy binding update or deletes the session request, and includes:

The second L-GW receives a proxy binding update or delete session request sent by the first L-GW; the second L-GW deletes a connection with the first L-GW or with the P-GW Connections, including:

The second L-GW deletes the connection with the first L-GW, where the first L-GW is currently connected by the user equipment UE, and the second L-GW is the first connection of the UE to the UE L-GW connected before;

The second L-GW sends a proxy binding response or deletes the session response, including:

Sending, by the second L-GW, a proxy binding response or deleting a session response to the first L-GW, to enable the first L-GW to reach the first base station or the first corresponding to the first L-GW The MME sends a delete session response.

In a second possible implementation, the second local gateway L-GW receives the proxy binding update or deletes the session request, including:

The second L-GW receives the proxy binding update or delete session request sent by the P-GW; the second L-GW deletes the connection with the P-GW, including: The second L-GW deletes the connection with the P-GW, where the first L-GW is currently connected by the user equipment UE, and the P-GW connects the first L- to the UE. The GW is connected before; the second L-GW sends a proxy binding response or deletes the session response, including:

Sending, by the second L-GW, a delete session response to the P-GW, to enable the P-GW to send a proxy binding response or delete a session response to the first serving gateway S-GW corresponding to the P-GW. .

With reference to any one of the third aspect to the second possible implementation manner of the third aspect, in a third possible implementation manner, the second local gateway L-GW receives the first L-GW sending Before deleting the session request, it also includes:

Receiving, by the second L-GW, a modified bearer request sent by the first L-GW;

The second L-GW sends a modify bearer response to the first L-GW.

In a fourth aspect, an embodiment of the present invention provides a communication method, including: when a user equipment UE is handed over from a second base station to a first base station,

The first local gateway L-GW receives the modify bearer request;

The first L-GW changes the stored current serving node information of the UE from the second base station information to the first base station information, where the first base station and the second base station correspond to the same first L-GW; The first L-GW sends a modify bearer response.

In a first possible implementation, the first L-GW receives the modify bearer request, and includes:

Receiving, by the first L-GW, a modify bearer request sent by the first base station;

The first L-GW sends a modify bearer response, including:

The first L-GW sends a modify bearer response to the first base station.

In a second possible implementation, the first L-GW receives the modify bearer request, and includes:

Receiving, by the first L-GW, a modify bearer request sent by the first MME;

The first L-GW sends a modify bearer response, including:

The first L-GW sends a modify bearer response to the first MME.

In a fifth aspect, an embodiment of the present invention provides a communication method, including: when a user equipment is handed over from a second base station to a first base station,

The first mobility management entity MME receives the path switch request sent by the first base station, where the path switch request carries the distributed mobility management Dali identifier and the first local network. Off the L-GW address, the path switching request, so that the first L-GW modifies information of the second base station stored in the first L-GW to information of the first base station, the first base station and the The second base station corresponds to the same first L-GW;

The path that the first MME switches to the first base station according to the path switching request is that the first base station is connected to the first L-GW;

The first router sends a path switch response to the first base station, so that the first base station notifies the second base station to perform resource release.

In a sixth aspect, an embodiment of the present invention provides a local gateway, including:

a receiving module, configured to receive a create session request, where the create session request carries an address identifier of the second local gateway L-GW or an address identifier of the packet data network gateway P-GW, the second L-GW, the The P-GW is connected before the user equipment UE switches to the L-GW, and the UE is currently connected to the L-GW;

a processing module, configured to establish a connection with the second L-GW or the P-GW according to the create session request;

A sending module, configured to send a create session response.

In a first possible implementation manner, the receiving module is specifically configured to receive a create session request sent by the first base station corresponding to the L-GW, where the create session request includes the second L-GW Address identifier

The processing module is specifically configured to establish a connection with the second L-GW according to the creation session request;

The sending module is specifically configured to send a create session response to the first base station.

In a second possible implementation manner, the receiving module is specifically configured to receive a create session request sent by a first mobility management entity MME corresponding to the L-GW, where the create session request includes the second Address identifier of the L-GW;

The sending module is specifically configured to send a create session response to the first MME.

In a third possible implementation,

The receiving module is configured to receive a create session request sent by the first base station corresponding to the L-GW, where the create session request includes an address identifier of the P-GW; The processing module is specifically configured to establish a connection with the P-GW according to the creation session request;

In a fourth possible implementation,

The receiving module is configured to receive a create session request sent by the first mobility management entity LIE corresponding to the first L-GW, where the create session request includes an address identifier of the P-GW;

The processing module is specifically configured to establish a connection with the P-GW according to the create session request;

With reference to any one of the sixth aspect to the fourth possible implementation manner of the sixth aspect, in a fifth possible implementation, the sending module is further configured to send to the second L-GW The proxy binds to update or modify the bearer request;

The receiving module is further configured to receive a proxy binding response or a modified bearer response sent by the second L-GW.

With reference to the sixth aspect, the third possible implementation manner of the sixth aspect, or the fourth possible implementation manner of the sixth aspect, in the sixth possible implementation manner, the sending module is further used Sending a proxy binding update or modifying a bearer request to the P-GW;

The receiving module is further configured to receive a proxy binding response or modify a bearer response sent by the P-GW.

In a seventh aspect, the embodiment of the present invention provides a local gateway, including:

a receiving module, configured to receive a proxy binding update or modify a bearer request, where the local gateway L-GW is connected before the user equipment UE switches to the first L-GW or the packet data network gateway P-GW;

a processing module, configured to establish, according to the proxy binding update or modify a bearer request, a connection with the first L-GW or the P-GW;

A sending module, configured to send a proxy binding response or modify a bearer response.

In a first possible implementation manner, the receiving module is specifically configured to receive a proxy binding update or modify a bearer request sent by the first L-GW;

The processing module is specifically configured to update or modify a bearer request according to the proxy binding, and build Establishing a connection with the first L-GW;

The sending module is specifically configured to send a proxy binding response or modify a bearer response to the first L-GW.

In a second possible implementation, the receiving module is specifically configured to receive a proxy binding update or modify a bearer request sent by the P-GW;

The processing module is specifically configured to establish, according to the proxy binding update or modify a bearer request, a connection with the P-GW;

The sending module is specifically configured to send a proxy binding response or modify a bearer response to the P-GW.

With reference to the first possible implementation of the seventh aspect to the seventh aspect, in a third possible implementation, the receiving module is further configured to receive a proxy binding update sent by the first L-GW or Delete the session request;

The processing module is further configured to delete a connection with the first L-GW;

The sending module is further configured to send a proxy binding response or delete a session response to the first L-GW.

With reference to the second possible implementation of the seventh aspect to the seventh aspect, in a fourth possible implementation, the receiving module is further configured to receive a proxy binding update sent by the P-GW or Delete the session request;

The processing module is further configured to delete a connection with the P-GW;

The sending module is further configured to send a proxy binding response or delete a session response to the P-GW.

In an eighth aspect, an embodiment of the present invention provides a local gateway, including:

a receiving module, configured to receive a proxy binding update or delete a session request;

a processing module, configured to delete a connection with the first local gateway L-GW or a connection with the packet data network gateway P-GW, where the first L-GW is currently connected by the user equipment UE, the L - GW or the P-GW is connected before the UE is connected to the first L-GW;

A sending module, configured to send a proxy binding response or delete a session response.

In a first possible implementation manner, the receiving module is specifically configured to receive a proxy binding update or delete a session request sent by the first L-GW;

The processing module is specifically configured to delete a connection with the first L-GW, the first L-GW The user equipment UE is currently connected, and the L-GW is connected before the UE is connected to the first L-GW;

The sending module is specifically configured to send a proxy binding response or a delete session response to the first L-GW, so that the first L-GW sends a first base station or a first corresponding to the first L-GW. An MME sends a delete session response.

In a second possible implementation manner, the receiving module is specifically configured to receive a proxy binding update or delete session request sent by the P-GW;

The processing module is specifically configured to delete the connection with the P-GW, where the first L-GW is currently connected by the user equipment UE, and the P-GW is the UE connected to the first L -GW connected before;

The sending module is specifically configured to send a delete session response to the P-GW, so that the P-GW sends a proxy binding response or deletes a session response to the first serving gateway corresponding to the P-GW.

With reference to any one of the second aspect to the second possible implementation of the eighth aspect, in a third possible implementation, the receiving module is further configured to receive the first L- Modifying the bearer request sent by the GW;

The sending module is further configured to send a modify bearer response to the first L-GW.

A ninth aspect, the embodiment of the present invention provides a local gateway, including: when a user equipment UE is handed over from a second base station to a first base station,

a receiving module, configured to receive a modify bearer request;

a processing module, configured to change the stored current UE service node information from the second base station information to the first base station information, where the first base station and the second base station correspond to the same local gateway;

A sending module, configured to send a modified bearer response.

In a first possible implementation manner, the receiving module is specifically configured to receive a modify bearer request sent by the first base station;

The sending module is specifically configured to send a modified bearer response to the first base station.

In a second possible implementation manner, the receiving module is specifically configured to receive a modify bearer request sent by the first MME;

The sending module is specifically configured to send a modify bearer response to the first MME. A tenth aspect, the embodiment of the present invention provides a mobility management entity, including: when a user equipment is handed over from a second base station to a first base station,

a receiving module, configured to receive a path switch request that is sent by the first base station, where the path switch request carries a distributed mobility management DMM identifier and a first local gateway L-GW address, where the path switch request is And causing the first L-GW to modify information of the second base station stored in the first L-GW to information of the first base station, where the first base station and the second base station correspond to the same first L-GW ;

a processing module, configured to switch, according to the path switching request, a path of the first base station to be connected to the first L-GW by the first base station;

And a sending module, configured to send a path switch response to the first base station, to perform resource release between the first base station and the second base station.

In an eleventh aspect, an embodiment of the present invention provides a local gateway L-GW, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, where Storing a set of program code in the memory, and the processor is configured to invoke the program code stored in the memory, and perform any one of the sixth aspect to the sixth possible implementation manner of the first aspect The method described.

In a twelfth aspect, an embodiment of the present invention provides a local gateway L-GW, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, where Storing a set of program code in the memory, and the processor is configured to invoke program code stored in the memory, and perform any one of a second aspect to a fifth possible implementation of the second aspect The method described.

In a thirteenth aspect, an embodiment of the present invention provides a local gateway L-GW, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, where Storing a set of program code in the memory, and the processor is configured to invoke program code stored in the memory, and perform any one of a third aspect to a third possible implementation of the third aspect The method described.

In a fourteenth aspect, an embodiment of the present invention provides a local gateway L-GW, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, where Storing a set of program codes in the memory, and the processor is configured to invoke the program code stored in the memory, and perform the second aspect to the second aspect of the fourth aspect A method as claimed in any of the preceding embodiments.

In a fifteenth aspect, an embodiment of the present invention provides a mobility management entity, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, Wherein the memory stores a set of program codes, and the processor is configured to invoke program code stored in the memory to perform the method described in a possible implementation of the fifth aspect.

According to the foregoing technical solution, the communication method, the communication device, and the communication system provided by the embodiment of the present invention receive a create session request by using the first local gateway L-GW, where the create session request carries the address identifier of the second L-GW or An address identifier of the packet data network gateway P-GW, and then the first L-GW establishes a connection with the second L-GW or the P-GW according to the creation session request, thereby completing the first L-GW and the second L - The connection between the GWs, or the connection between the first L-GW and the P_GW, the first L-GW sends a Create Session Response, thereby enabling the UE to switch between different networks. BRIEF DESCRIPTION OF THE 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. The drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

1 is a schematic flow chart of a communication method according to an embodiment of the present invention;

2 is a schematic flowchart of a communication method according to another embodiment of the present invention;

3 is a schematic flowchart of a communication method according to still another embodiment of the present invention;

4 is a schematic flowchart of a communication method according to still another embodiment of the present invention;

FIG. 5 is a schematic flowchart diagram of a communication method according to still another embodiment of the present invention; FIG.

6 is a schematic diagram of a signaling flow of a communication method according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a signaling flow of a communication method according to another embodiment of the present invention; FIG.

8 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention;

9 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention;

FIG. 10 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; FIG.

FIG. 11 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; FIG. FIG. 12 is a schematic flow chart of a communication method according to still another embodiment of the present invention;

13 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

FIG. 14 is a schematic flow chart of a communication method according to still another embodiment of the present invention;

15 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

16 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

17 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

18 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

19 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

20 is a schematic flow chart of a communication method according to still another embodiment of the present invention.

21 is a schematic structural diagram of an L-GW according to an embodiment of the present invention;

FIG. 22 is a schematic structural diagram of an L-GW according to another embodiment of the present invention; FIG.

FIG. 23 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention; FIG.

24 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention;

25 is a schematic structural diagram of a mobility management entity according to an embodiment of the present invention;

26 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention;

Figure 27 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention;

28 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention;

29 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention;

FIG. 30 is a schematic structural diagram of an MME according to another embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill 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 flowchart of a communication method according to an embodiment of the present invention; as shown in FIG. 1 , the communication method includes the following steps on the basis of maintaining service continuity of the UE:

Step 101: The first local gateway L-GW receives a create session request.

The creation session request carries the address identifier or packet data network of the second L-GW. The address identifier of the gateway P-GW.

In this embodiment, the second L-GW and the P-GW are connected before the UE is handed over to the first L-GW, where the second L-GW or the P-GW may allocate an IP address to the UE, and While the UE uses the first L-GW to allocate a new IP address, the UE may also use the IP address before the current handover, and the UE is currently connected to the first L-GW.

This embodiment is applicable to the following applicable scenarios:

In the first applicable scenario, the UE performs handover between networks of different cells, where the network before and after the UE handover is a network supporting the D-function, which is referred to as a D-network, and in the current network connected to the UE, the first There is no interface between the first MME corresponding to the first L-GW, and the MME corresponding to the first L-GW is the MN 5 serving the UE.

Specifically, after establishing a connection between the UE and the first base station corresponding to the first L-GW, the first L-GW may receive a create session request sent by the first base station corresponding to the first L-GW, where the session is created. The request includes an address identifier of the second L-GW, where the UE is currently connected to the first base station corresponding to the first L-GW, and the UE is connected to the second L-GW before connecting with the first L-GW, and the UE further The IP address assigned by the second L-GW to the UE before the current handover may be used.

In a second applicable scenario, the UE performs handover between networks of different cells, where the networks are all D-networks, and in the current UE-connected D-network, the first L-GW and the first L-GW An interface is provided between the corresponding MMEs.

Specifically, after the UE establishes a connection with the first base station, the first L-GW may receive a create session request sent by the first MME, where the create session request includes an address identifier of the second L-GW, where the UE and the UE The first L-GW is connected to the second L-GW before the connection is made, and the UE may also use the IP address allocated by the second L-GW to the UE before the current handover.

In a third applicable scenario, the UE switches from the EPS network to the DMM network, and in the DMM network that the UE is currently connected to, the first L-GW has no interface with the MME corresponding to the first L-GW.

Specifically, after establishing a connection between the UE and the first base station corresponding to the first L-GW, the first L-GW may receive a create session request sent by the first base station corresponding to the first L-GW, where the session is created. The request includes an address identifier of the P-GW, where the UE is connected to the P-GW before the connection with the first L-GW, and the UE may also use the IP that is not allocated by the second L-GW for the UE. address.

The fourth applicable scenario, the UE switches from the EPS network to the DMM network, and the UE is currently connected. In the DMM network, an interface is provided between the first L-GW and the MME corresponding to the first L-GW.

Specifically, after establishing a connection between the UE and the first base station corresponding to the first L-GW, the first L-GW may receive a create session request sent by the first MME corresponding to the first L-GW, where the session is created. The request includes an address identifier of the P-GW, where the UE is connected to the P-GW before the connection with the first L-GW, and the UE may also use the IP that is not allocated by the second L-GW for the UE. address. .

Step 102: The first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request.

In this embodiment, corresponding to the applicable scenario in step 101, the step 102 may be specifically as follows:

In the first applicable scenario or in the second applicable scenario, the first L-GW establishes a connection with the second L-GW according to the create session request, and thus, the second L-GW is equivalent to the EPS of the prior art. The function of the P-GW in the network, the first L-GW is equivalent to the function of the S-GW in the EPS network of the prior art.

Specifically, in the first applicable scenario or in the second applicable scenario, step 102, first

The L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, and specifically includes:

Sending, by the first L-GW, a proxy binding update or modifying a bearer request to the second L-GW;

The first L-GW receives the proxy binding response sent by the second L-GW or modifies the bearer response.

In the third applicable scenario or in the fourth applicable scenario, the first L-GW establishes a connection with the P-GW according to the create session request, so that the first L-GW is equivalent to the EPS network in the prior art. The function of the S-GW.

Specifically, in the third applicable scenario or in the fourth applicable scenario, the step 102, the first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, and may specifically include :

The first L-GW sends a proxy binding update or a modification bearer request to the P-GW;

The first L-GW receives the proxy binding response sent by the P-GW or modifies the bearer response.

Step 103: The first L-GW sends a create session response.

In this embodiment, corresponding to the applicable scenario in step 101, the step 103 may be specifically as follows: In the first applicable scenario or in the third applicable scenario, the first L-GW sends a create session response to the first base station.

In the second applicable scenario or in the fourth applicable scenario, the first L-GW sends a create session response to the first MME.

The communication method provided by the embodiment receives the create session request by the first local gateway L-GW, where the create session request carries the address identifier of the second L-GW or the address identifier of the packet data network gateway P-GW, and then, The first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, thereby completing the connection between the first L-GW and the second L-GW, or completing the first L- The connection between the GW and the P-GW, the first L-GW sends a session creation response, thereby implementing handover of the UE between different networks.

2 is a schematic flowchart of a communication method according to another embodiment of the present invention; as shown in FIG. 2, the communication method specifically includes the following steps:

Step 201: The second L-GW receives the proxy binding update or modifies the bearer request.

In this embodiment, the second L-GW is connected before the UE is handed over to the first L-GW or the P-GW, where the first L-GW or the P-GW may allocate a new IP address to the UE, and The UE can not only use the new IP address, but also use the IP address before the current handover.

It should be noted that an implementation method of this embodiment may be applicable to the first applicable scenario or the second applicable scenario in the embodiment shown in FIG. 1 , and may also be applied to a new applicable scenario, such as a fifth applicable scenario or The sixth applicable scenario.

In the fifth applicable scenario, if the UE switches from the DMM network to the EPS network, and the MN that is connected before the UE is switched, the interface between the second L-GW and the MME corresponding to the second L-GW is not set.

In the sixth application scenario, if the UE switches from the DMM network to the EPS network, and the MME connected to the UE before the switching, the second L-GW and the MME corresponding to the second L-GW are provided with an interface.

Specifically, the second L-GW may receive the proxy binding update or modify the bearer request sent by the first L-GW or the P-GW, in any of the foregoing applicable scenarios.

Step 202: The second L-GW establishes a connection with the first L-GW or the P-GW according to the proxy binding update or modify the bearer request.

Specifically, an implementation method of this embodiment is applicable to the first mode in the embodiment shown in FIG. In the scenario or the second applicable scenario, the second L-GW establishes a connection with the first L-GW according to the proxy binding update or modify the bearer request; and the second L in the fifth applicable scenario or the sixth applicable scenario. The GW establishes a connection with the P-GW according to the proxy binding update or modification of the bearer request.

Step 203: The second L-GW sends a proxy binding response or modifies a bearer response.

Specifically, an implementation method of this embodiment is applicable to the first applicable scenario or the second applicable scenario in the embodiment shown in FIG. 1, where the second L-GW sends a proxy binding response or modification to the first L-GW. Carrying a response; in the fifth applicable scenario or the sixth applicable scenario, the second L-GW sends a proxy binding response or a modified bearer response to the P-GW.

The communication method provided in this embodiment is to receive a proxy binding update or modify a bearer request by using the second local gateway L-GW, where the second L-GW is connected before the UE switches to the first L-GW or the P-GW, After the UE switches to the first L-GW or the P-GW, the second L-GW can still use the IP address allocated by the second L-GW for the UE; the second L-GW updates or modifies the bearer request according to the proxy binding, and establishes with the first a connection between the L-GW or the P-GW; the second L-GW sends a proxy binding response or modifies the bearer response, thereby completing the connection between the second L-GW and the first L-GW or the P-GW, and further Realize the handover of the UE between different networks.

On the basis of the foregoing embodiment, in the first applicable scenario or the second applicable scenario, after the step 203, the second L-GW, or the second P-GW sends the proxy binding response or the modified bearer response, Includes:

Step 204: The second L-GW receives the proxy binding update or delete session request sent by the first L-GW.

In this embodiment, when the UE switches from one DMM network cell to another DMM network cell, whether there is an interface between the MME and the first L-GW in the new DMM network, regardless of whether the UE is currently connected to the D-network, After performing the reconstruction of the PDN connection, the UE does not need the IP address assigned by the second L_GW or the second P-GW, so that the PDN connection can be disconnected, so that the second local gateway L-GW can receive the proxy sent by the first L-GW. Bind updates or delete session requests.

Step 205: The second L-GW deletes the bearer between the first L-GW and the first L-GW.

Step 206: The second L-GW sends a proxy binding response or a delete session response to the first L-GW. On the basis of the foregoing embodiment, in the fifth adaptation scenario and the sixth adaptation scenario, after the step 203, the second L-GW, or the second P-GW sends the proxy binding response or the modified bearer response, the method may further include : The second local gateway L-GW receives the proxy binding update or delete session request sent by the P-GW; the second L-GW deletes the connection with the P-GW;

Specifically, when the UE switches from the D-network to the EPS network, whether the interface exists between the MME and the first L-GW in the D-network connected to the UE, after the EPS network performs the PDN connection reconstruction, the UE does not need to The IP address allocated by the second L-GW is connected to the PDN connection, so that the second local gateway L-GW can receive the proxy binding update or delete session request sent by the P-GW, and then perform the above method.

FIG. 3 is a schematic flowchart of a communication method according to still another embodiment of the present invention; as shown in FIG. 3, the communication method specifically includes the following steps:

Step 301: The second L-GW receives the delete session request.

In an implementation manner of this embodiment, when the UE switches from one DMM network cell to another DMM network cell, whether there is an interface between the MME and the first L-GW in the DMM network currently connected by the UE, in the new After the DMM network cell performs the reconstruction of the PDN connection, the UE may not need the IP address assigned by the second L-GW or the second P-GW, so that the PDN connection can be disconnected, that is, the second local gateway L-GW can receive the deletion. Session request.

In another implementation manner of this embodiment, when the UE switches from one DMM network cell to one EPS network cell, after the new EPS network cell performs the PDN connection reconstruction, the UE may not need to allocate the second L-GW. The IP address, so that the PDN connection can be disconnected, that is, the second L-GW receives the delete session request sent by the P-GW, so that the connection between the second L-GW and the P_GW is deleted.

Step 302: The second L-GW deletes the connection with the first L-GW or the connection with the P_GW.

In an implementation manner of this embodiment, the second local gateway L-GW may receive the delete session request, so that the second L-GW deletes the connection between the first L-GW and the second L-GW, where The first L-GW is the L-GW to which the UE is currently connected, and the second L-GW is connected before the UE connects to the first L_GW.

In another implementation manner of this embodiment, the second L-GW receives the delete session request sent by the P-GW, so that the connection between the second L-GW and the P-GW is deleted, and the P-GW is the user equipment. The second L-GW that is currently connected by the UE is connected before the UE connects to the P-GW. Step 303: The second L-GW sends a delete session response.

Specifically, in an implementation manner of this embodiment, when the UE switches from one DMM network cell to another DMM network cell, whether there is an interface between the MME and the first L-GW in the DMM network currently connected by the UE After the second local gateway L-GW receives the delete session request, the second L-GW may send a delete session response to the first L-GW, so that the first L-GW sends the first base station or the first corresponding to the first L-GW. An MME sends a delete session response.

In another implementation manner of this embodiment, when the UE switches from one DMM network cell to one EPS network cell, after the second L-GW receives the delete session request sent by the P-GW, the second L-GW sends a P to the P The GW sends a delete session response, so that the P-GW sends a delete session response to the first S-GW corresponding to the P-GW.

In this embodiment, the second local gateway L-GW receives the delete session request, so as to delete the connection between the first L-GW and the second L-GW or the connection between the second L-GW and the P_GW, and then The second L-GW sends a delete session response, thereby deleting the connection between the first L-GW and the second L-GW, or establishing a connection between the first L-GW and the P-GW, so that the UE can switch. Go to other network cells.

Further, before receiving the deletion session request sent by the first L-GW, the second local gateway L-GW may further include:

The second L-GW receives the modified bearer request sent by the first L-GW;

The second L-GW sends a modified bearer response to the first L-GW.

FIG. 4 is a schematic flowchart of a communication method according to still another embodiment of the present invention; as shown in FIG. 4, the communication method specifically includes the following steps:

Step 401: The first L-GW receives the modify bearer request.

In this embodiment, the UE may perform handover between different base stations, that is, the first base station and the second base station. In a applicable scenario of the present embodiment, when the data service occurs before the UE performs the handover, the data service is performed. In the scenario where the relocation does not occur, and the first base station and the second base station correspond to the same L-GW, the first base station may send a path switch request to the corresponding first MME.

In an implementation manner of this embodiment, an interface exists between the MME and the first L-GW, and the first L-GW may receive the modify bearer request sent by the first base station.

In another implementation manner of this embodiment, an interface exists between the MME and the first L-GW, where An L-GW may receive a modify bearer request sent by the first MME.

Step 402: The first L-GW changes the stored current serving node information of the UE from the second base station information to the first base station information.

In this embodiment, whether the interface exists between the MME and the first L-GW, the first L-GW may modify the information of the originally stored second base station to the information of the first base station, where the first base station and the first base station The second base station corresponds to the same first L-GW, wherein the information of the first base station includes an address of the data transmission and a tunnel end point identifier (TEID).

Step 403: The first L-GW sends a modify bearer response.

In an implementation manner of this embodiment, the interface between the MME and the first L-GW does not exist, and the first L-GW sends a modify bearer response to the first base station.

In another implementation manner of this embodiment, an interface exists between the MME and the first L-GW, and the first L-GW may send a modify bearer response to the first MME.

In this embodiment, the first L-GW receives the modify bearer request, and then the first L-GW changes the stored current serving node information of the UE from the second base station information to the first base station information, and the first L-GW sends the information. The bearer response is modified so that the UE can switch to other network cells.

FIG. 5 is a schematic flowchart of a communication method according to still another embodiment of the present invention; as shown in FIG. 5, the communication method specifically includes the following steps:

Step 501: The first MME receives a path switch request sent by the corresponding first base station.

The path switching request carries the Dili identifier and the first L-GW address, and the path switching request is used to enable the first L-GW to modify the information of the second base station stored in the first L-GW to the information of the first base station. The first base station and the second base station correspond to the same first L-GW.

Specifically, the UE may perform handover between different base stations, that is, the first base station and the second base station. In a applicable scenario, the UE performs data service switching when a data service occurs before the handover occurs. In the scenario where no relocation occurs, the first base station and the second base station correspond to the same L-GW, and the first MME receives the path switch request sent by the corresponding first base station.

In this embodiment, the first MME receives the path switch request sent by the corresponding first base station, where the path switch request carries the information of the first base station, where the information includes the address and TEID of the data transmission.

Step 502: The first MME switches the path of the first base station to the first base according to the path switching request. The station is connected to the first L-GW.

Step 503: The first switch sends a path switch response to the first base station.

In the communication method provided by the embodiment, the first MME receives the path switching request sent by the corresponding first base station, where the path switching request carries the Dili identifier, and the first base station and the second base station correspond to the same first L-GW, and then The first MME switches the path of the first base station according to the path switching request to the first base station to connect with the first L-GW, and the first MME sends a path switching response to the first base station, so that the first base station notifies the second base station. Release resources. Therefore, the first MME switches the path of the first base station according to the path switching request to the first base station to connect with the first L-GW, and the UE can switch from the first base station to the second base station while maintaining the continuity of the data connection.

FIG. 6 is a schematic diagram of a signaling process of a communication method according to an embodiment of the present invention; as shown in FIG. 6, the UE performs handover between networks of different cells, where the networks before and after the UE handover are all Dy networks, and There is no interface between the L-GW and the MME in the first DMM network to which the current UE is connected. Specifically, in a scenario where the UE switches from the second DMM network cell to the third DMM network cell, and then switches to the first DMM network cell that is currently connected with the UE, the second L-GW in the second DMM network is When the UE is connected, the UE is assigned an IP address. When the UE switches to the currently connected first DMM network cell, the UE may continue to use the IP address allocated by the second L-GW.

The communication method may specifically include the following steps:

Step 601: Perform a decision trigger switch between the first base station and the third base station.

The first base station in this embodiment is the base station to which the UE is currently connected, that is, the first base station is in the first D-network, and the third base station is the base station that the UE last connected before switching to the first base station, that is, the third base station. In the third DMM network. The first base station and the third base station trigger the handover according to the measurement result of the wireless link.

Step 602: The third base station sends a handover request to the third MME corresponding to the third base station, where the third MME corresponding to the third base station is that the third MME may serve the UE connected to the third base station. The first MME corresponding to the first base station is that the first MME may serve the UE connected to the first base station.

Step 603: The third MME sends a forwarding relocation request to the first MME.

In this embodiment, the forwarding relocation request carries UE context information.

Step 604: The first MME sends a handover request to the first base station.

Specifically, the first MME informs the first base station of the EPS bearer context of each PDN connection. Step 605: The first base station sends a create session request to the first L-GW corresponding to the first base station.

The create session request includes an address identifier of the second L-GW, where the second L-GW is in the second DMM network, and the IP address allocated by the second L-GW to the UE can always be Used by the UE.

Step 606: The first L-GW initiates an IP-CAN (IP-Connectivity Access Network) session establishment or modification process to the PCRF (Polic icy and Charging Rules Function).

In this embodiment, if dynamic PCC (Polic and Charging Control) is deployed, the first L-GW initiates an IP-CAN session establishment or modification process to the PCRF, and obtains PCC policy information of the UE.

Step 607: The first L-GW sends a proxy binding update or a modify bearer request to the second L-GW. In this embodiment, the proxy binding update or modify bearer request is used to establish a connection between the first L-GW and the second L-GW.

Step 608: The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW. Step 609: The first L-GW sends a create session response to the first base station.

Step 610: The first base station sends a handover request response to the first MME.

The handover request response carries a Dili identity.

Step 611: The first MME sends a forwarding relocation response to the third MME.

Step 612: The third router sends a handover command to the third base station.

Step 613: The third base station sends a handover command to the UE.

Step 614: The UE sends a handover confirmation to the first base station.

Step 615: The first base station sends a handover notification to the first MME.

Step 616: The UE performs a tracking area update process.

It should be noted that, if the PMIP protocol is adopted between the first L-GW and the second L-GW, then the first L-GW sends a proxy binding update (Proxy Binding Update) to the second L-GW. PBU), correspondingly, step 608, the second L_GW sends a Proxy Binding Acknowledgement (PBA) message to the first L_GW to establish tunnel information between the first L-GW and the second L-GW. .

After establishing the tunnel information between the first L-GW and the second L-GW, the third device needs to be released. The L-GW resource, specifically, the method for releasing the third L-GW resource may be:

The step 607 and the step 608 in the embodiment shown in FIG. 6 may further perform the step: the third L-GW receives the binding revocation indication sent by the second L-GW (Binding Revocation Indication) Referring to the BRI message, the EPS bearer context information about this PDN connection is deleted. Or the release of the third L-GW resource may be performed by the step 612 and the step 613: the third L-GW receives the delete session request sent by the third base station, and deletes the EPS bearer context about the PDN connection. information. It should be noted that if the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required.

If the GTP protocol is adopted between the first L-GW and the second L-GW, then the first L_GW sends a modify bearer request to the second L-GW, and correspondingly, step 608, the second L-GW The first L_GW sends a modify bearer response message to establish bearer information between the first L-GW and the second L-GW.

After the bearer information between the first L-GW and the second L-GW is established, the resource of the third L-GW needs to be released. Specifically, the method for releasing the third L-GW resource may be:

The step 612 and the step 613 in the embodiment shown in FIG. 6 may further perform the step: the third L-GW receives the delete session request sent by the third base station, and deletes the EPS bearer context information about the PDN connection. .

It should be noted that if the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required.

It should be noted that, in an implementation manner of this embodiment, if the UE switches from the second DMM network to the third EPS network, and then switches to the first DMM network, and in the first DMM network that the UE is currently connected, In a scenario where there is no interface between the L-GW and the first MME, the basic principle of the UE handover method is basically the same as the basic principle of the embodiment shown in FIG. 6, except that the third L-GW corresponds to the P-GW. And the third network needs to increase the S-GW resource release process, that is, after the third P-GW receives the binding revocation indication message sent by the second L-GW, the third P-GW may perform the following steps: The S-GW sends a delete bearer request, and the third S-GW sends a delete bearer response to the third P_GW; or, after the third E sends a handover command to the third base station, the third E sends a delete session to the third S-GW. The request, and the third S-GW send a delete session response to the third MME. If the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required. And if the UE directly switches from the second EPS network to the first DMM network, the second L-GW is equivalent to the P-GW, and the process of releasing the S-GW resource release is needed in the second network, that is, in the second P-GW. After receiving the proxy binding update or modifying the bearer request sent by the first L-GW, sending a delete bearer request to the second S-GW, where the second S-GW sends a delete bearer response to the second P-GW; or, the second After the MME sends the handover command to the second base station, the second MME sends a delete session request to the second S-GW, and the second S-GW sends a delete session response to the second MME.

FIG. 7 is a schematic diagram of a signaling flow of a communication method according to another embodiment of the present invention, as shown in FIG.

The UE performs handover between networks of different cells, where the networks before and after the UE handover are all DMM networks, and an interface is set between the local gateway L-GW and the MME in the first D-network connected by the current UE. . Specifically, in a scenario where the UE switches from the second DMM network cell to the third DMM network cell, and then switches to the first DMM network cell that is currently connected with the UE, the second L-GW in the second DMM network is When the UE is connected, the UE is assigned an IP address. When the UE switches to the currently connected first DMM network cell, the UE may continue to use the IP address assigned by the second L-GW.

The communication method may specifically include the following steps:

Step 701: Perform a decision trigger switch between the first base station and the third base station.

The first base station in this embodiment is a base station to which the UE is currently connected, that is, the first base station is in the first

In the D-network, the third base station is the base station that the UE last connected before switching to the first base station, that is, the third base station is in the third DMM network. The first base station and the third base station trigger the handover according to the measurement result of the wireless link.

Step 702: The third base station sends a handover request to a third MME corresponding to the third base station. In this embodiment, the third MME corresponding to the third eNB may be that the third MME may serve the UE connected to the third eNB, and the first MME corresponding to the first eNB may be the first MME. Serving the UE connected to the first base station.

Step 703: The third MME sends a forwarding relocation request to the first MME, where the forwarding relocation request carries UE context information.

Step 704: The first E sends a handover request to the first base station.

Specifically, the first MME informs the first base station of the EPS bearer context of each PDN connection. Step 705: The first base station sends a handover request notification to the first MME corresponding to the first base station, where the handover request notification carries a Dili identifier and a first L-GW address identifier, where the first L-GW is In the first DMM network. The DMM identity and the first L_GW address identifier indicate that the first base station supports the Dali service and that the first MME is required to establish a connection between the first base station and the first L-GW. Step 706: The first E-E sends a create session request to the first L-GW, where the create session request carries the second L-GW address identifier.

Step 707: The first L-GW initiates an IP-CAN session establishment or modification process to the PCRF.

In this embodiment, if dynamic PCC is deployed, the L-GW initiates an IP-CAN session establishment or modification process to the PCRF, and obtains PCC policy information of the UE.

Step 708: The first L-GW sends a proxy binding update or a modify bearer request to the second L-GW. Step 709: The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW. Step 710: The first L-GW sends a create session response to the first MME.

Step 71: The first MME sends a forwarding relocation response to the third MME.

Step 712: The first MME sends a handover request completion message to the first base station, where the handover request completion message includes an address of the uplink data transmission of the first L-GW corresponding to the first base station.

TEID o

Step 713: The third router sends a handover command to the third base station.

Step 714: The third base station sends a handover command to the UE.

Step 715: The UE sends a handover confirmation to the first base station.

Step 716: The first base station sends a handover notification to the first MME.

Step 717: The first E sends a modify bearer request to the first L-GW.

Step 718: The first L-GW sends a modify bearer response to the first MME.

Step 719: The UE performs a tracking area update process.

It should be noted that, if the PMIP protocol is adopted between the first L-GW and the second L-GW, the step 708, the first L-GW sends a proxy binding update to the second L-GW, and correspondingly, the step 709. The second L-GW sends a proxy binding response message to the first L-GW to establish tunnel information between the first L-GW and the second L-GW.

After the tunnel information between the first L-GW and the second L-GW is established, the resource of the third L-GW needs to be released. Specifically, the method for releasing the third L-GW resource may be:

The step 708 and the step 709 in the embodiment shown in FIG. 7 may further perform the step: the third L-GW receives the BRI message sent by the second L-GW, and deletes the EPS bearer related to the PDN connection. Contextual information. Or the release of the third L-GW resource may be performed between step 71 1 and step 712: the third L-GW receives the delete session request sent by the third MN, and deletes the EPS about the PDN connection. Host context information. It should be noted that if the UE directly from the second network The network switches to the first network, and the process of releasing the third L-GW resource is not required.

If the GTP protocol is adopted between the first L-GW and the second L-GW, the step 708, the first L_GW sends a modify bearer request to the second L-GW, and correspondingly, step 709, the second L-GW The first L_GW sends a modify bearer response message to establish bearer information between the first L-GW and the second L-GW.

After establishing the bearer information between the first L-GW and the second L-GW, the third device needs to be released.

The L-GW resource, specifically, the method for releasing the third L-GW resource may be:

A step may be further performed between the step 71 1 and the step 712 in the embodiment shown in FIG. 7 : the third L-GW receives the delete session request sent by the third MME, and deletes the EPS about the PDN connection. Host context information.

It should be noted that, in the implementation manner of the first embodiment, if the UE switches from the second DMM network to the third EPS network, and then switches to the first DMM network, and in the first DMM network that the UE is currently connected, the first L In the scenario where an interface is set between the GW and the first MME, the basic principle of the method for UE handover is basically the same as the basic principle of the embodiment shown in FIG. 7 , except that the third L-GW corresponds to the P-GW, and The process of the S-GW resource release is required to be performed in the third network, that is, after the third P-GW receives the binding revocation indication message sent by the second L-GW, the following steps may be performed: the third P-GW goes to the third S. - The GW sends a delete bearer request, and the third S-GW sends a delete bearer response to the third P-GW; or, after the first MME sends the forward relocation response to the third MME, the third MME sends the third MME to the third S-GW. Sending a delete session request, and the third S-GW sends a delete session response to the third MME. If the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required. And if the UE directly switches from the second EPS network to the first D-network, the second L-GW is equivalent to the P-GW, and the process of releasing the S-GW resource needs to be added in the second network, that is, in the second P- After receiving the proxy binding update or modifying the bearer request sent by the first L-GW, the GW sends a delete bearer request to the second S-GW, and the second S-GW sends a delete bearer response to the second P-GW; or, After transmitting the forwarding relocation response to the second MME, the second E sends a deletion session request to the second S-GW, and the second S-GW sends a deletion session response to the second MME.

FIG. 8 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG. 8, the UE performs handover between networks of different cells, where the networks before and after UE handover are DMM networks, and Local gateway L-GW and MME in the first D-network connected by the current UE There is an interface between them. Specifically, in a scenario where the UE switches from the second DMM network cell to the third DMM network cell, and then switches to the first DMM network cell that is currently connected with the UE, the second L-GW in the second DMM network is When the UE is connected, the UE is assigned an IP address. When the UE switches to the currently connected first DMM network cell, the UE may continue to use the IP address assigned by the second L-GW.

Specifically, after the UE switches to the currently connected first DMM network cell, and the first MME knows that the first base station supports the Dili network, the communication method may specifically include the following steps: Step 801: The first base station and the first base station Decision-making trigger switching is performed between the third base stations.

Step 802: The third base station sends a handover request to a third MME corresponding to the third base station. In this embodiment, the third MME corresponding to the third eNB may be that the third MME may serve the UE connected to the third eNB, and the first MME corresponding to the first eNB may be that the first MME may be Serving with the UE connected to the first base station.

Step 803: The third MME sends a forwarding relocation request to the first MME.

The forwarding relocation request carries UE context information.

Step 804: The first E sends a create session request to the first L-GW.

The create session request carries a second L-GW address.

Step 805: The first L-GW initiates an IP-CAN session establishment or modification process to the PCRF.

In this embodiment, if dynamic PCC is deployed, the L-GW initiates an IP-CAN session establishment procedure to the PCRF, and obtains PCC policy information of the UE.

Step 806: The first L-GW sends a proxy binding update or a modify bearer request to the second L-GW. Step 807: The second L-GW sends a proxy binding response or a modified bearer response to the first L_GW. Step 808: The first L-GW sends a create session response to the first MME.

Step 809: The first router sends a handover request to the first base station.

Step 810: The first base station sends a handover request response to the first MME.

Step 81: The first MME sends a forwarding relocation response to the third MME.

Step 812: The third E sends a handover command to the third base station. Step 813: The third base station sends a handover command to the UE.

Step 814: The UE sends a handover confirmation to the first base station.

Step 815: The first base station sends a handover notification to the first MME.

Step 816: The first E sends a modify bearer request to the first L-GW.

Step 817: The first L-GW sends a modify bearer response to the first MME.

Step 818: The UE performs a tracking area update process.

It should be noted that, if the PMIP protocol is adopted between the first L-GW and the second L-GW, then the first L-GW sends a proxy binding update to the second L-GW, and correspondingly, the step 807. The second L-GW sends a proxy binding response message to the first L-GW to establish tunnel information between the first L-GW and the second L-GW.

The step 806 and the step 807 in the embodiment shown in FIG. 8 may further perform the step: the third L-GW receives the BRI message sent by the second L-GW, and deletes the EPS bearer related to the PDN connection. Contextual information. Or the release of the third L-GW resource may be performed by the step 81 1 and the step 812: the third L-GW receives the delete session request sent by the third MME, and deletes the EPS bearer related to the PDN connection. Contextual information. It should be noted that if the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required.

If the GTP protocol is adopted between the first L-GW and the second L-GW, then the first L-GW sends a modify bearer request to the second L-GW, and correspondingly, step 807, the second L- The GW sends a modify bearer response message to the first L_GW to establish bearer information between the first L-GW and the second L-GW.

A step may be further performed between the step 81 1 and the step 812 in the embodiment shown in FIG. 8 : the third L-GW receives the delete session request sent by the third MME, and deletes the EPS about the PDN connection. Host context information.

It should be noted that, in an implementation manner of this embodiment, if the UE switches from the second DMM network to the third EPS network, and then switches to the first DMM network, and the first D In the scenario where the interface is configured between the first L-GW and the first MME, the basic principle of the UE handover method is basically the same as the basic principle of the embodiment shown in FIG. 8. The difference is that the third L-GW corresponds. In the P-GW, and the third network needs to increase the S-GW resource release process, that is, after the third P-GW receives the binding revocation indication message sent by the second L-GW, the following steps may be performed: - The GW sends a delete bearer request to the third S-GW, and the third S-GW sends a delete bearer response to the third P-GW; or, after the first MME sends the forward relocation response to the third MME, the third MME Sending a delete session request to the third S-GW, and transmitting a delete session response to the third MME by the third S-GW. If the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required. And if the UE directly switches from the second EPS network to the first D-network, the second L-GW is equivalent to the P-GW, and the process of releasing the S-GW resource needs to be added in the second network, that is, in the second P- After receiving the proxy binding update or modifying the bearer request sent by the first L-GW, the GW sends a delete bearer request to the second S-GW, and the second S-GW sends a delete bearer response to the second P-GW; or, After transmitting the forwarding relocation response to the second MME, the second E sends a deletion session request to the second S-GW, and the second S-GW sends a deletion session response to the second MME.

In the implementation method of the first embodiment, if the UE switches from the second DMM network to the third EPS network and then switches to the first EPS network, the process of the UE switching in the subsequent EPS network may be performed according to the EPS process. Here, a reconstruction process in which the UE switches from the second DMM network to the third EPS network is described. Specifically, it can be divided into two usage scenarios. The first applicable scenario is that the second MME in the second D-network does not know whether the second base station supports the D-network, and the process is basically the same as the embodiment shown in FIG. 7. The difference is that The first L-GW corresponds to the P-GW. In the second applicable scenario, the second MME in the second DMM network knows that the second base station supports the DMM network, and the process is basically the same as the embodiment shown in FIG. 8, except that the first L-GW corresponds to the P-GW.

FIG. 9 is a schematic diagram of a signaling process of a communication method according to still another embodiment of the present invention; as shown in FIG. 9, the UE performs handover between networks of different cells, where the networks before and after UE handover are DMM networks, and There is no interface between the local gateway L-GW and the MME in the first D-network of the current UE connection. Specifically, when the UE is in the ECM-IDLE state, the UE switches from the second DMM network cell to the third DMM network cell, and then switches to the first DMM network cell that is currently connected with the UE, in the second DMM network. When the second L-GW is connected to the UE, the UE is assigned an IP address. When the UE switches to the currently connected first DMM network cell, the UE may continue to use the IP address allocated by the second L-GW. The communication method may specifically include the following steps:

Step 901: The UE performs a tracking area update trigger.

Step 902: The UE sends a tracking area update request to the first base station.

Step 903: The first base station sends a tracking area update request to the first MME, where the tracking area update request carries the Dili identifier.

Step 904: The first MME sends a context request to the third MME to request the context information of the UE.

Step 905: The third MME sends a context response to the first MME, where the context response carries context information of the UE in the third MME.

Step 906: The first MME sends a bearer setup request to the first base station, where the bearer setup request carries the EPS bearer context list, that is, the EPS bearer context information including the PDN connection to be established.

Step 907: The first base station sends a create session request to the first L-GW.

Step 908: The first L-GW initiates an IP-CAN session establishment or modification process to the PCRF.

Step 909: The first L-GW sends a proxy binding update or a modify bearer request to the second L-GW to establish a connection between the first L-GW and the second L-GW.

Step 910: The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW. Step 91: The first L-GW sends a create session response to the first base station.

Step 912: The first base station sends a bearer setup response to the first MME.

Step 913: The first MME sends a context response to the third MME.

Step 914: The first E sends an update location to the HSS.

Step 915: The HSS sends a delete location to the third MME to delete the context of the UE in the third MME.

Step 916: The third ray sends a delete location response to the HSS.

Step 917: The HSS sends an update location response to the first MME. Step 918: The first E sends a tracking area update acceptance to the UE.

It should be noted that, if the PMIP protocol is adopted between the first L-GW and the second L-GW, the step 909, the first L-GW sends a proxy binding update to the second L-GW, and correspondingly, the step 910. The second L-GW sends a proxy binding response message to the first L-GW to establish a connection between the first L-GW and the second L-GW.

After the connection between the first L-GW and the second L-GW is established, the resource of the third L-GW needs to be released. Specifically, the method for releasing the third L-GW resource may be:

The step 909 and the step 910 in the embodiment shown in FIG. 9 may further perform the step: the third L-GW receives the binding revocation indication message sent by the second L-GW, and deletes the PDN connection. The EPS carries context information. Or the release of the third L-GW resource may be performed by the step 913 and the step 914: the third E sends a deactivation bearer request to the third base station, where the deactivation bearer request carries the operation identifier (Operat i on Indicating), to inform the third base station that only the EPS bearer resource of the reconstructed PDN connected to the third L-GW needs to be deleted, and then the third base station sends a delete session request to the third L-GW, and then deletes EPS bearer context information about this PDN connection. It should be noted that if the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required.

If the GTP protocol is adopted between the first L-GW and the second L-GW, then the first L-GW sends a modify bearer request to the second L-GW, and correspondingly, step 910, the second L- The GW sends a modify bearer response message to the first L-GW to establish a connection between the first L-GW and the second L-GW.

The step 912 and the step 913 in the embodiment shown in FIG. 9 may further perform the step of: the third E sends a deactivation bearer request to the third base station, where the deactivation bearer request carries the operation identifier In order to inform the third base station that the EPS bearer resource of the reconstructed PDN connection on the third L-GW needs to be deleted, and then the third base station sends a delete session request to the third L-GW, and then delete the EPS bearer context about the PDN connection. information.

It should be noted that, in an implementation manner of this embodiment, if the UE switches from the second DMM network to the third EPS network, and then switches to the first DMM network, and the UE is currently connected. In a DMM network, in a scenario where there is no interface between the first L-GW and the first MME, the basic principle of the UE handover method is basically the same as the basic principle of the embodiment shown in FIG. 9, and the difference is that the third L-GW Corresponding to the P-GW, and the process of adding the S-GW resource release is required in the third network, that is, after the third P-GW receives the binding revocation indication message sent by the second L-GW, the following steps may be performed: The P-GW sends a delete bearer request to the third S-GW, and then the third S-GW sends a delete bearer response to the third P-GW; or, after the first MME sends the context response to the third MME, the third The MME sends a delete session request to the third S-GW, and the third S-GW sends a delete session response to the third MME. If the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required. And if the UE directly switches from the second EPS network to the first DMM network, the second L-GW is equivalent to the P-GW, and the process of releasing the S-GW resource needs to be added in the second network, that is, in the second P-GW. After receiving the proxy binding update or modifying the bearer request sent by the first L-GW, sending a delete bearer request to the second S-GW, and sending, by the second S-GW, the delete bearer response to the second P-GW; or, the first After the MME sends the context response to the second MME, the second MME sends a delete session request to the second S_GW, and the second S-GW sends a delete session response to the second MME.

FIG. 10 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG. 10,

The UE performs handover between networks of different cells, where the networks before and after the UE handover are all DMM networks, and an interface is set between the local gateway L-GW and the MME in the first D-network connected by the current UE. . Specifically, when the UE is in the ECM-IDLE state, the UE switches from the second DMM network cell to the third DMM network cell, and then switches to the first DMN network cell that is currently connected with the UE, and the second DMM network When the second L-GW is connected to the UE, the UE is assigned an IP address, and when the UE switches to the currently connected first DMM network cell, the UE may continue to use the IP address allocated by the second L-GW.

The communication method may specifically include the following steps:

Step 1001: The UE performs a tracking area update trigger.

Step 1002: The UE sends a tracking area update request to the first base station.

Step 1003: The first base station sends a tracking area update request to the first MME, where the tracking area update request carries the Dili identifier and the address identifier of the first L-GW.

Step 1004: The first MME sends a context request to the third MME to request the uplink information of the UE.

Step 1005: The third MME sends a context response to the first MME, where the context response carries Context information with the UE in the third MME.

Step 1006: The first MME sends a create session request to the first L-GW, where the create session request includes an address identifier of the second L-GW, where the second L-GW is in the second DMM network, and the The IP address allocated by the second L-GW to the UE can always be used by the UE during the UE handover process.

Step 1007: The first L-GW initiates an IP-CAN session establishment or modification process to the PCRF. In this embodiment, if dynamic PCC is deployed, the L-GW initiates an IP-CAN session establishment or modification process to the PCRF, and obtains PCC policy information of the UE.

Step 1008: The first L-GW sends a proxy binding update or a modify bearer request to the second L-GW to establish a connection between the first L-GW and the second L-GW.

Step 1009: The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW. Step 1010: The first L-GW sends a create session response to the first MME.

Step 101: The first MME sends a context response to the third MME.

Step 1012: The first E sends an update location to the HSS.

Step 1013: The HSS sends the deletion location to the third MME.

The deletion location is used to delete the context of the UE in the third ray.

Step 1014: The third ray sends a delete location response to the HSS.

Step 1015: The HSS sends an update location response to the first MME.

Step 1016: The first E sends a tracking area update acceptance to the UE.

It should be noted that, if the PMIP protocol is adopted between the first L-GW and the second L-GW, then step 1008, the first L-GW sends a proxy binding update to the second L-GW, and correspondingly, the step 1009. The second L-GW sends a proxy binding response message to the first L-GW to establish a connection between the first L-GW and the second L-GW.

A step may be further performed between the step 1008 and the step 1009 in the embodiment shown in FIG. 10: the third L-GW receives the binding revocation indication message sent by the second L-GW, and deletes the PDN connection. The EPS carries context information. Or the release of the third L-GW resource may be further performed by the step 101 1 and the step 1012: the third E sends a delete session request to the third L-GW, and the EPS about the PDN connection is deleted. Host context information. It should be noted that if the UE directly switches from the second network to the first network, the process of releasing the third L-GW resource is not required. If the GTP protocol is adopted between the first L-GW and the second L-GW, then the first L-GW sends a modify bearer request to the second L-GW, and correspondingly, step 1009, the second L- The GW sends a modify bearer response message to the first L-GW to establish a connection between the first L-GW and the second L-GW.

Steps may be further performed between step 101 1 and step 1012 in the embodiment shown in FIG. 10: the third E sends a delete session request to the third L-GW, and then the EPS bearer context about the PDN connection is deleted. information.

It should be noted that, in an implementation manner of this embodiment, if the UE switches from the second DMM network to the third EPS network, and then switches to the first DMM network, and in the first DMM network that the UE is currently connected, In a scenario where an interface is provided between an L-GW and the first MME, the basic principle of the UE handover method is basically the same as the basic principle of the embodiment shown in FIG. 10, except that the third L-GW corresponds to the P-GW. And the process of the S-GW resource release is required to be performed in the third network, that is, after the third P-GW receives the binding revocation indication message sent by the second L-GW, the third P-GW may perform the following steps: The third S-GW sends a delete bearer request, and the third S-GW sends a delete bearer response to the third P-GW; or, after the first MME sends a context response to the third MME, the third MME sends the third S-GW to the third S-GW. Sending a delete session request, and the third S-GW sends a delete session response to the third MME. If the UE switches directly from the second network to the first network, the process of releasing the third L-GW resource is not required. And if the UE directly switches from the second EPS network to the first DMM network, the second L-GW is equivalent to the P-GW, and the process of releasing the S-GW resource needs to be added in the second network, that is, in the second P-GW. After receiving the proxy binding update or modifying the bearer request sent by the first L-GW, sending a delete bearer request to the second S-GW, and sending, by the second S-GW, the delete bearer response to the second P-GW; or, the first After the MME sends the context response to the second MME, the second MME sends a delete session request to the second S_GW, and the second S-GW sends a delete session response to the second MME.

In the implementation method of the first embodiment, if the UE switches from the second DMM network to the third EPS network and then switches to the first EPS network, the process of the UE switching in the subsequent EPS network may be according to the EPS process of the prior art. That is, therefore, the UE is switched from the second DMM network here. A reconstruction process to the third EPS network. The process of the UE switching from the second DMM network to the third EPS network is basically the same as the embodiment shown in FIG. 10, except that the first L-GW corresponds to the P-GW, and the tracking area update request is received in step 1003. The Dili logo and the address identifier of the first L-GW are not carried in the middle.

FIG. 1 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG.

The UE may perform handover between different base stations, that is, the first base station and the third base station, and the first base station and the third base station correspond to the same L-GW. An applicable scenario in this embodiment is that the interface is not configured between the first eNB and the first MME, where the communication method includes:

Step 1 101: The first base station sends a modify bearer request to the first L-GW.

In this embodiment, the modified bearer request is used to update the IP address and the TEID of the downlink data transmission of the UE in the first L-GW, that is, the information of the third base station in the first L-GW is modified as the first base station. Ft is self-defeating.

Step 1 102: The first L-GW sends a modify bearer response to the first base station.

Step 1 103: The first base station sends a path switch request to the first node.

It should be noted that the path switching request carries the Dili identifier.

Step 1 104: The first base station receives a path switch response sent by the first port.

Step 1 105: The first base station sends a resource release request to the third base station.

The resource release request causes the second base station to release resources with the UE.

Step 1 106: The UE performs a tracking area update process.

12 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG. 12, a UE may perform handover between different base stations, that is, a first base station and a third base station, and the first base station and the third base station Corresponding to the same L-GW. An applicable scenario in this embodiment is that an interface is configured between the first base station and the first MME, where the communication method includes:

Step 1201: The first base station sends a path switch request to the first MME, where the path switch request carries the Dili identifier and the address identifier of the first L-GW.

Step 1202: The first MME sends a modify bearer request to the first L-GW.

In this embodiment, the modified bearer request is used to update the IP address and the TEID of the downlink data transmission of the UE in the first L-GW, that is, the information of the third base station in the first L-GW is modified to be the first base station. Information.

Step 1203: The first L-GW sends a modify bearer response to the first MME.

Step 1204: The first switch sends a path switch response to the first base station.

Step 1205: The first base station sends a resource release request to the third base station.

The resource release request causes the third base station to release resources between the UE and the UE, that is, to release resources between the UE and the third base station to which the UE is connected before switching to the first base station.

Step 1206: The UE performs a tracking area update process.

13 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG. 13, a UE may perform handover between different base stations, that is, a first base station and a third base station, and the first base station and the third base station Corresponding to the same L-GW. An application scenario in this embodiment is that the interface between the first eNB and the first MME is not set. In the scenario where the MME is relocated, the communication method includes:

Step 1301: Perform a decision trigger switch between the first base station and the third base station.

Step 1302: The third base station sends a handover request to the third MME.

Step 1303: The third MME sends a forwarding relocation request to the first MME.

Step 1304: The first E sends a handover request to the first base station.

Step 1305: The first base station sends a handover request response to the first MME.

The handover request response carries a Dili identity.

Step 1306: The first ray sends a forwarding relocation response to the third ray E.

Step 1307: The third E sends a handover command to the third base station.

Step 1308: The third base station sends a handover command to the UE.

Step 1309: The UE sends a handover confirmation to the first base station.

Step 1310: The first base station sends a modify bearer request to the first L-GW.

The modified bearer request is used to update the IP address and the TEID of the downlink data transmission of the UE in the first L-GW, that is, the information of the third base station in the first L-GW is modified as the information of the first base station.

Step 131: The first L-GW sends a modify bearer response to the first base station.

Step 1312: The first base station sends a handover notification to the first MME.

Step 1313: The UE performs a tracking area update process.

14 is a schematic diagram of a signaling flow of a communication method according to still another embodiment of the present invention; as shown in FIG. 14, a UE may perform handover between different base stations, that is, a first base station and a third base station, and the first base station Corresponding to the same L-GW as the third base station. An application scenario in this embodiment is that an interface is configured between the first base station and the first MME, and the communication method includes:

Cong

Less 1401, the decision between the base station and the third base station is triggered to switch.

Cong

The less than 1402, the second base station sends a handover request to the third MME.

Cong

Less 1403, second brother. The MME sends a forward relocation request to the first MME.

Cong

Less than 1404, the MME sends a handover request to the first base station.

Cong

Less than 1405, the second base station sends a handover request notification to the first MME.

The handover request notification carries the Dili identity and the first L-GW address identifier.

Step 1406: The first MME sends a forwarding relocation response to the third MME.

Step 1407: The third E sends a handover command to the third base station.

Step 1408: The third base station sends a handover command to the UE.

Step 1409: The UE sends a handover confirmation to the first base station.

Step 1410: The first base station sends a handover notification to the first MME.

Step 141 1. The first E sends a modify bearer request to the first L-GW.

Step 1412: The first L-GW sends a modify bearer response to the first MME.

Step 1413: The UE performs a tracking area update process.

FIG. 15 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 15, the applicable scenario in this embodiment is that a UE performs handover between different cells, and the network architectures of the cells are the same, that is, The D-network, and after the UE establishes a PDN connection with the current cell, the UE may initiate a PDN connection to connect, and may release a PDN connection that the UE no longer needs. The UE releases the tunnel or bearer information of the L_GW between the DMM network currently connected by the UE and the D-network connected to the UE, that is, the resource between the first L-GW and the second L-GW. In the scenario that no interface is set between the MME and the L-GW in the DMM network, the resource release between the first L-GW and the second L-GW may include the following steps:

Step 1501: The UE sends a PDN connection to the MME to connect to the MME.

The MME in this embodiment corresponds to the first L-GW. The UE may send a PDN connection de-connection request to the MME through the base station, where the PDN connection de-connection request is used to connect the UE to the second L_GW. A PDN connection between the second L-GW and the L_GW connected before the UE connects to the current DMM network. Step 1502: The MME sends a deactivation bearer request to the base station.

Specifically, the base station is a base station currently connected to the UE, and the MME sends a deactivation bearer request to the base station that forwards the PDN connection to the connection request.

Step 1503: The base station sends a delete session request to the first L-GW.

Step 1504: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connection resources between the UE and the second L-GW. Therefore, the proxy binding update carries the IP address assigned by the second L-GW to the UE, to delete the IP address. Corresponding PDN connection. Or deleting the session request includes an LBI (Linked EPS Bearer Identifier), which is used to delete the PDN connection whose default bearer identifier is LBI between the first L_GW and the second L_GW.

Step 1505: The second L-GW initiates an IP-CAN session termination process to the PCRF.

In this embodiment, if a dynamic PCC is deployed, the second L-GW initiates an IP-CAN session termination procedure to the PCRF.

Step 1506: The second L-GW sends a proxy binding response or deletes the session response to the first L-GW. Step 1507: The first L-GW sends a delete session response to the base station, in response to deleting the session request.

Step 1508: The base station sends RRC connection reconfiguration information to the UE, to modify the air interface signaling connection.

Step 1509: The UE sends an RRC connection reconfiguration complete message to the base station.

Step 1510: The base station sends a deactivation bearer response to the MME.

The deactivation bearer response is used to inform the MN that the PDN connection between the first L-GW and the second L-GW has been deleted.

Step 1511: The UE sends a direct transmission message to the base station.

The direct transmission message carries a deactivated EPS bearer context accept message.

Step 1512: The base station sends a deactivated EPS bearer context accept message to the MME.

It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the Dali network, whether the UE is currently connected to the DMM network, or the UE is currently connected to the EPS network. The principle is basically similar to the principle of the embodiment shown in FIG. 15, except that the second L-GW corresponds to the P-GW or the first L-GW corresponds to the P_GW. It should be noted that the detachment of the PDN connection may also be initiated by the MME. For example, when the UE subscribes to data modification or lack of resources, the MME decides to release the PDN connection of the UE.

For the de-connection of a certain PDN connection of the UE, the PDN connection may be initiated by the UE to connect to the connection, or the MME may trigger the PDN connection to connect.

FIG. 16 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 16, the applicable scenario in this embodiment is that a UE performs handover between different cells, and the network architectures of the cells are the same, that is, The D-network, and after the UE establishes a PDN connection with the current cell, the UE may initiate a PDN connection to connect, and may release a PDN connection that the UE no longer needs. The UE releases the tunnel or bearer information of the L_GW between the DMM network currently connected by the UE and the D-network connected to the UE, that is, the resource between the first L-GW and the second L-GW. In the scenario that an interface exists between the MME and the L-GW in the DMM network, the resource release between the first L-GW and the second L-GW may include the following steps:

Step 1601: The UE sends a PDN connection to the MME through the base station to connect to the MME.

Specifically, the UE sends a PDN connection de-connection request to the MME through a base station connected to the UE, where the PDN connection de-connection request is used to connect the PDN connection between the UE and the second L-GW, where the second L-GW is the UE. Connect to the L-GW connected before the current Delicate network.

The detachment of the PDN connection may also be initiated by the MME. For example, when the UE subscribes to data modification or lack of resources, the MME decides to release the PDN connection of the UE.

Step 1602: The MME sends a delete session request to the first L-GW.

Step 1603: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connection resources between the UE and the second L-GW. Therefore, the proxy binding update carries the IP address assigned by the second L-GW to the UE, to delete the IP address. Corresponding PDN connection. Or deleting the session request includes an LBI, and deleting the PDN connection with the default bearer identifier LBI between the first L_GW and the second L-GW.

Step 1604: The second L-GW initiates an IP-CAN session termination procedure to the PCRF.

In this embodiment, if dynamic PCC is deployed, the L-GW initiates an IP-CAN session termination procedure to the PCRF.

Step 1605: The second L-GW sends a proxy binding response or a delete session response to the first L-GW. Step 1606: The first L-GW sends a delete session response to the MME.

Specifically, the MME is an MME corresponding to the first L-GW, and the first L_GW sends a delete session response to the MME, in response to deleting the session request.

Step 1607: The MME sends a deactivation bearer request to the base station.

Specifically, the base station is connected to the first L-GW, that is, the base station corresponding to the first L-GW. The deactivation bearer request is used to deactivate all bearers of the PDN connection between the UE and the MME.

Specifically, the base station is a base station that forwards the PDN connection de-connection request in step 1601. Step 1608: The base station sends RRC connection reconfiguration information to the UE, to modify the air interface signaling connection.

Step 1609: The UE sends an RRC connection reconfiguration complete message to the base station.

In this embodiment, the UE sends the RRC connection reconfiguration complete information to the base station, thereby completing the reconfiguration of the RRC connection between the UE and the base station.

Step 1610: The base station sends a deactivation bearer response to the MME.

Step 161 1. The UE sends a direct transmission message to the base station.

Step 1612: The base station sends a deactivation bearer context accept message to the MME.

It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the Dali network. If the UE is currently connected to the DMM network, the principle of the embodiment shown in FIG. Basically the same, the difference is that the second L-GW corresponds to the P-GW, and the rest of the same parts will not be described again. If the UE is currently connected to the EPS network, the principle is basically the same as that of the embodiment shown in FIG. 16. The difference is that the first L-GW corresponds to the S-GW or the P-GW. Specifically, in the embodiment shown in FIG. Step 1602 corresponds to the MME sending a delete session request to the P_GW through the S-GW, and then, step 1603 corresponds to the P-GW sending a proxy binding update or deletion session request to the second L-GW, where the second L-GW For the L-GW to which the UE is previously connected, the rest of the same parts will not be described again.

FIG. 17 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 17, the applicable scenario of the present embodiment is that a UE performs handover between different cells, and the network architectures of the cells are the same, that is, The D-network, and after the UE establishes a PDN connection with the current cell, the UE may initiate a detach request to release the connection between the UE and the network. In a scenario where there is no interface between the MME and the L-GW in the DMM network, the detaching of the UE may include the following steps: Step 1701: The UE initiates a detach request to the MME by using the base station.

The detach request is used to request detachment of the UE.

In this embodiment, the MME is a MN corresponding to the first L-GW, and the current UE is connected to the first L-GW through the base station.

Step 1702: The MME sends a deactivation bearer request to the base station.

There may be multiple PDN connections between the UE and the L-GW, and the MME sends a deactivation bearer request for each PDN connection. Each deactivation bearer request includes an LBI for deactivating a PDN connection between the UE and the L-GW with a default bearer identifier of LBI.

Step 1703: The base station sends a delete session request to the corresponding first L-GW, so that the corresponding first L-GW deletes the established PDN connection.

Step 1704: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connections between the UE and the second L-GW. Therefore, the proxy binding update carries the IP address assigned by the second L-GW to the UE, to delete the IP address. PDN connection. Or deleting the session request includes an LBI (Linked EPS Bearer Identifier), which is used to delete the PDN connection whose default bearer identifier is LBI between the first L_GW and the second L_GW.

Step 1705: The second L-GW initiates an IP-CAN session termination process to the PCRF.

Step 1706: The second L-GW sends a proxy binding response or a delete session response to the first L-GW. Step 1707: The first L-GW sends a delete session response to the base station.

Step 1708: The base station sends a deactivation bearer response to the MME to respond to the deactivation of the bearer request.

Step 1709: The MME sends a detach accept message to the UE by using the base station.

Step 1710: Perform RRC connection release between the base station and the UE.

That is, the MME indicates that the air interface signaling connection is released between the base station and the UE through the UE context release command (UE Context Release Co匪and), and then the base station informs the MME that the RRC connection is successful through the UE Context Release Complete message. freed.

It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the DMM network, regardless of whether the UE is currently connected to the DMM network, or The UE is currently connected to the EPS network, and the principle is basically similar to the principle of the embodiment shown in FIG. 17, except that the second L-GW corresponds to the P-GW or the first L-GW corresponds to the P_GW.

FIG. 18 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 18, the applicable scenario is that the UE performs handover between different cells, and the network architectures of the cells are the same, that is, D The network, and after the UE establishes a PDN connection with the current cell, the UE may initiate a detach request to release the connection between the UE and the network. In a scenario where an interface exists between the MME and the L-GW in the DMM network, the detaching of the UE may include the following steps: Step 1801 The UE initiates a detach request to the MME by using the base station.

Step 1802: The MME sends a delete session request to the first L-GW.

The delete session request causes the first L-GW to delete the established PDN connection.

Step 1803: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connection resources between the UE and the second L-GW. Therefore, the proxy binding update carries the IP address assigned by the second L-GW to the UE, to delete the IP address. Corresponding PDN connection. Or deleting the LBI included in the session request to delete the PDN connection with the default bearer identifier LBI between the first L-GW and the second L-GW.

Step 1804: The second L-GW initiates an IP-CAN session termination procedure to the PCRF.

Step 1805: The second L-GW sends a proxy binding response or deletes the session response to the first L-GW. Step 1806: The first L-GW sends a delete session response to the MME.

Step 1807: The MME sends a detach accept message to the UE.

Step 1808: Perform an RRC connection release between the base station and the UE.

That is, the MME indicates that the air interface signaling connection is released between the base station and the UE through the UE context release command (UE Context Rel ease Co and ), and then the base station informs the MME that the RRC connection is successful through the UE Context Release Complete message. freed.

It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the Dali network. If the UE is currently connected to the DMM network, the principle of the embodiment shown in FIG. Basically the same, the difference is that the second L-GW corresponds to the P-GW, and the rest of the same parts will not be described again. If the UE is currently connected to the EPS network, the principle is basically the same as that of the embodiment shown in FIG. 18, except that the first L-GW corresponds to the S-GW or the P-GW. Specifically, FIG. 18 Step 1802 in the illustrated embodiment corresponds to the MME sending a delete session request to the P_GW through the S-GW, and then, in step 1803, the P-GW sends a proxy binding update or delete session request to the second L-GW, where The second L-GW is the L-GW connected before the UE, and the rest of the same parts are not described again.

FIG. 19 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 19, the applicable scenario is that the UE performs handover between different cells, and the network architectures of the cells are the same, that is, D The network, and after the UE establishes a PDN connection with the current cell, the MME may initiate a detach request to release the connection between the UE and the network. In a scenario where there is no interface between the MME and the L-GW in the DMM network, the detaching of the UE may include the following steps: Step 1901: The MME initiates a detach request to the UE by using the base station.

The detach request is used to notify the UE to attach.

Step 1902: The MME sends a deactivation bearer request to the base station.

Step 1903: The base station sends a delete session request to the corresponding first L-GW.

The delete session request causes the corresponding L-GW to delete the established PDN connection.

Step 1904: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connections between the UE and the second L-GW. Therefore, the proxy binding update session request carries a proxy binding deletion session request to delete the first L-GW and the first The bearer between the two L-GWs, that is, the first L-GW sends a delete session request for each PDN connection. Each delete session request includes an LBI for deleting a PDN connection whose default bearer identifier is LBI between the first L-GW and the second L-GW.

Step 1905: The second L-GW initiates an IP-CAN session termination process to the PCRF.

Step 1906: The second L-GW sends a proxy binding response or deletes the session response to the first L-GW. Step 1907: The first L-GW sends a delete session response to the base station.

Step 1908: The base station sends a deactivation bearer response to the MME to respond to the deactivation of the bearer request.

Step 1909: The UE sends a detach accept message to the MME by using the base station.

Step 1910: Perform an RRC connection release between the base station and the UE.

That is, the MME indicates the air interface between the base station and the UE through the UE context release command. The signaling connection is released, and then the base station informs the LG ERRC connection to be successfully released through the UE context release completion message.

It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the Dali network, whether the UE is currently connected to the DMM network, or the UE is currently connected to the EPS network. The principle is basically similar to the principle of the embodiment shown in FIG. 19, except that the second L-GW corresponds to the P-GW.

FIG. 20 is a schematic diagram of a signaling procedure of a communication method according to still another embodiment of the present invention; as shown in FIG. 20, the applicable scenario is that the UE performs handover between different cells, and the network architectures of the cells are the same, that is, D The network, and after the UE establishes a PDN connection with the current cell, the MME may initiate a detach request to release the connection between the UE and the DMM network. In a scenario where an interface exists between the MME and the L-GW in the D-network, the detaching of the UE may include the following steps: Step 2001: The MME initiates a detach request to the UE by using the eNB, and the detach request is used to notify the UE. Go to the attachment.

Step 2002: The MME sends a delete session request to the first L-GW.

In this embodiment, the delete session request causes the first L-GW to delete the established PDN connection.

Step 2003: The first L-GW sends a proxy binding update or delete session request to the second L-GW. In this embodiment, there may be multiple PDN connection resources between the UE and the second L-GW. Therefore, the proxy binding update carries the IP address assigned by the second L-GW to the UE, to delete the IP address. Corresponding PDN connection. Or deleting the LBI included in the session request to delete the PDN connection with the default bearer identifier LBI between the first L-GW and the second L-GW.

Step 2004: The second L-GW initiates an IP-CAN session termination procedure to the PCRF.

Step 2005: The second L-GW sends a proxy binding response or deletes the session response to the first L-GW. Step 2006: The first L-GW sends a delete session response to the MME.

Step 2007 The UE sends a detach accept message to the MME.

Step 2008: The RRC connection is released between the base station and the UE.

That is, the MME indicates that the air interface signaling connection between the base station and the UE is released by using the UE context release command (UE Context Rel ease Co and ), and then the base station releases through the UE context. The UE Context Relity Complete message informs the MME that the RRC connection is successfully released. It should be noted that the UE may also switch between cells of different network architectures, that is, switch between the EPS network and the Dali network. If the UE is currently connected to the DMM network, the principle of the embodiment shown in FIG. Basically the same, the difference is that the second L-GW corresponds to the P-GW, and the rest of the same parts will not be described again. If the UE is currently connected to the EPS network, the principle is the same as that of the embodiment shown in FIG. 20, except that the first L-GW corresponds to the S-GW or the P-GW. Specifically, in the embodiment shown in FIG. Step 2002 corresponds to the MME sending a delete session request to the P_GW through the S-GW, and then, in step 2003, the P-GW sends a proxy binding update or delete session request to the second L-GW, where the second L-GW For the L-GW connected to the previous UE, the rest of the same parts will not be described again.

FIG. 21 is a schematic structural diagram of an L-GW according to an embodiment of the present invention. As shown in FIG. 21, the L-GW includes: a receiving module 2101, a processing module 2102, and a sending module 2103. among them,

The receiving module 2101 is configured to receive a create session request, where the session request carries an address identifier of the second local gateway L-GW or an address identifier of the packet data network gateway P-GW, where the second L-GW and the P-GW are users. The device UE is connected to the L-GW before being connected, and the UE is currently connected to the L_GW;

The processing module 2102 is configured to establish a connection with the second L-GW or the P-GW according to the create session request.

The sending module 2103 is configured to send a create session response.

Further, the receiving module 2101 is specifically configured to receive a create session request sent by the first base station corresponding to the L-GW, where the create session request includes an address identifier of the second L-GW;

The processing module 2102 is specifically configured to establish a connection with the second L-GW according to the create session request.

The sending module 2103 is specifically configured to send a create session response to the first base station.

Further, the receiving module 2101 is configured to receive a create session request sent by the first mobility management entity MME corresponding to the L-GW, where the create session request includes an address identifier of the second L-GW;

The sending module 2103 is specifically configured to send a create session response to the first MME.

Further, the receiving module 2101 is specifically configured to receive the first base station corresponding to the L-GW. Sending a session request, creating a session request including an address identifier of the P-GW;

The processing module 2102 is specifically configured to establish a connection with the P-GW according to the create session request. The sending module 2103 is specifically configured to send a create session response to the first base station.

Further, the receiving module 2101 is configured to receive a create session request sent by the first mobility management entity MME corresponding to the first L-GW, where the session request includes an address identifier of the P-GW.

The processing module 2102 is specifically configured to establish a connection with the P-GW according to the create session request. The sending module 2103 is specifically configured to send a create session response to the first MME.

Further, the sending module 2103 is further configured to send a proxy binding update or modify a bearer request to the second L-GW;

The receiving module 2101 is further configured to receive a proxy binding response sent by the second L-GW or modify the bearer response.

Further, the sending module 2103 is further configured to send a proxy binding update or modify a bearer request to the P-GW;

The receiving module 2101 is further configured to receive a proxy binding response sent by the P-GW or modify the bearer response.

FIG. 22 is a schematic structural diagram of an L-GW according to another embodiment of the present invention. As shown in FIG. 22, the L-GW includes: a receiving module 2201, a processing module 2202, and a sending module 2203. among them,

The receiving module 2201 is configured to receive a proxy binding update or modify a bearer request, where the local gateway L-GW is configured to switch to the first L-GW or the packet data network gateway P_GW before the processing module 2202 The proxy binding updates or modifies the bearer request, establishing a connection with the first L-GW or the P-GW;

The sending module 2203 is configured to send a proxy binding response or modify a bearer response.

Further, the receiving module 2201 is specifically configured to receive a proxy binding sent by the first L-GW to update or modify the bearer request.

The processing module 2202 is specifically configured to establish a connection with the first L-GW according to the proxy binding update or modify the bearer request.

The sending module 2203 is specifically configured to send a proxy binding response or modify a bearer response to the first L-GW.

Further, the receiving module 2201 is specifically configured to receive a proxy binding update sent by the P-GW. Or modify the bearer request;

The processing module 2202 is specifically configured to establish a connection with the P-GW according to the proxy binding update or modify the bearer request.

The sending module 2203 is specifically configured to send a proxy binding response or modify a bearer response to the P-GW. Further, the receiving module 2201 is further configured to receive a proxy binding update sent by the first L-GW or delete the session request;

The processing module 2202 is further configured to delete the connection with the first L-GW.

The sending module 2203 is further configured to send a proxy binding response or delete the session response to the first L-GW.

Further, the receiving module 2201 is further configured to receive a proxy binding update or delete session request sent by the P-GW;

The processing module 2202 is further configured to delete the connection between the P-GW and the P-GW.

The sending module 2203 is further configured to send a proxy binding response or delete the session response to the P-GW. FIG. 23 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 23, the L-GW includes: a receiving module 2301, a processing module 2302, and a sending module 2303. among them,

The receiving module 2301 is configured to receive a proxy binding update or delete a session request.

The processing module 2302 is configured to delete the connection between the first local gateway L-GW or the connection with the packet data network gateway P-GW, where the first L-GW is currently connected by the user equipment UE, L-GW or The P-GW is connected before the UE connects to the first L-GW;

The sending module 2303 is configured to send a proxy binding response or delete a session response.

Further, the receiving module 2301 is specifically configured to receive a proxy binding sent by the first L-GW to update or delete the session request.

The processing module 2302 is specifically configured to delete the connection with the first L-GW, where the first L-GW is currently connected by the user equipment UE, and the L-GW is connected before the UE connects to the first L-GW;

The sending module 2303 is configured to send a proxy binding response or a delete session response to the first L-GW, so that the first L-GW sends a delete session response to the first base station or the first MME corresponding to the first L-GW.

Further, the receiving module 2301 is specifically configured to receive a proxy binding update sent by the P-GW or delete the session request.

The processing module 2302 is specifically configured to delete the connection with the P-GW, where the first L_GW is a user. The device is currently connected to the UE, and the P-GW is connected before the UE connects to the first L-GW;

The sending module 2303 is specifically configured to send a delete session response to the P-GW, so that the P-GW is

The first serving gateway corresponding to the P-GW sends a proxy binding response or deletes the session response.

Further, the receiving module 2301 is further configured to receive a modified bearer request sent by the first L-GW;

The sending module 2303 is further configured to send a modify bearer response to the first L-GW.

FIG. 24 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 24, the L-GW includes: a receiving module 2401, a processing module 2402, and a sending module 2403. among them,

When the user equipment UE switches from the second base station to the first base station,

The receiving module 2401 is configured to receive a modify bearer request.

The processing module 2402 is configured to change the stored current serving node information of the UE from the second base station information to the first base station information, where the first base station and the second base station correspond to the same local gateway;

The sending module 2403 is configured to send a modify bearer response.

Further, the receiving module 2401 is specifically configured to receive a modified bearer request sent by the first base station;

The sending module 2403 is specifically configured to send a modify bearer response to the first base station.

Further, the receiving module 2401 is specifically configured to receive a modified bearer request sent by the first MME;

The sending module is specifically configured to send a modified bearer response to the first MME.

FIG. 25 is a schematic structural diagram of a mobility management entity according to an embodiment of the present invention. As shown in FIG. 25, the L-GW includes: a receiving module 2501, a processing module 2502, and a sending module 2503. Wherein, when the user equipment switches from the second base station to the first base station,

The receiving module 2501 is configured to receive a path switching request sent by the corresponding first base station, where the path switching request carries a distributed mobility management Dali identifier and a first local gateway L-GW address, and the path switching request is used to make the first L- The GW modifies the information of the second base station stored in the first L-GW to the information of the first base station, where the first base station and the second base station correspond to the same first L-GW;

The processing module 2502 is configured to switch, according to the path switching request, the path of the first base station to be connected to the first L-GW by the first base station;

The sending module 2503 is configured to send a path switch response to the first base station, so that the first base station notifies the second base station to perform resource release. FIG. 26 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 26, the local gateway L-GW includes: a transmitter 2601, a receiver 2602, a memory 2603, and a transmitter 2601, a receiver 2602, and The processor 2604 is connected to the memory 2603. The memory 2603 stores a set of program codes, and the processor 2604 is configured to call the program code stored in the memory 2603 to execute the communication method provided by the embodiment shown in FIG. 1 of the present invention.

The L-GW of this embodiment may be used to perform the technical solution of the embodiment of the communication method provided by the embodiment of the present invention. The implementation principle and technical effects are similar, and details are not described herein again.

FIG. 27 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 27, the L-GW includes: a transmitter 2701, a receiver 2702, a memory 2703, and a transmitter 2701, a receiver 2702, and a memory 2703, respectively. The connected processor 2704, wherein the memory 2703 stores a set of program codes, and the processor 2704 is configured to call the program code stored in the memory 2703 to execute the communication method provided by the embodiment shown in FIG. 2 of the present invention.

The L-GW of the present embodiment can be used to perform the technical solution of the embodiment of the communication method provided by the embodiment of the present invention. The implementation principle and technical effects are similar, and details are not described herein again.

28 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 28, the L_GW includes: a transmitter 2801, a receiver 2802, a memory 2803, and a transmitter 2801, a receiver 2802, and a memory 2803, respectively. The processor 2804 is configured to store a set of program codes in the memory 2803, and the processor 2804 is configured to call the program code stored in the memory 2803 to execute the communication method provided by the embodiment shown in FIG. 3 of the present invention.

The L-GW of this embodiment may be used to implement the technical solution of the embodiment of the communication method provided by the embodiment of the present invention. The implementation principle and technical effects are similar, and details are not described herein again.

FIG. 29 is a schematic structural diagram of an L-GW according to still another embodiment of the present invention. As shown in FIG. 29, the L-GW includes: a transmitter 2901, a receiver 2902, a memory 2903, and a transmitter 2901, a receiver 2902, and a memory 2903, respectively. The connected processor 2904, wherein the memory 2903 stores a set of program codes, and the processor 2904 is configured to call the program code stored in the memory 2903 to execute the communication method provided by the embodiment shown in FIG. 4 of the present invention.

FIG. 30 is a schematic structural diagram of an MME according to another embodiment of the present invention. As shown in FIG. 30, the L-GW includes: a transmitter 3001, a receiver 3002, a memory 3003, and a transmitter 3001, respectively. The processor 3004 is connected to the processor 3003, wherein the memory 3003 stores a set of program codes, and the processor 3004 is configured to call the program code stored in the memory 3003 to perform the communication provided by the embodiment shown in FIG. 5 of the present invention. method.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, when executed, The steps of the foregoing method embodiments are performed; and the foregoing storage medium includes: various media that can store program codes, such as ROM, RAM, disk or optical disk.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting thereof; 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

claims

1. A communication method, characterized by including:

The first local gateway L-GW receives a session creation request, and the session creation request carries the address identifier of the second L-GW or the address identifier of the packet data network gateway P-GW. The second L-GW, the The P-GW is the user equipment UE connected before switching to the first L-GW, and the UE is currently connected to the first L-GW;

The first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request;

The first L-GW sends a create session response.

2. The method according to claim 1, wherein the first local gateway L-GW receives a session creation request, including:

The first L-GW receives a session creation request sent by the first base station corresponding to the first L-GW, where the session creation request includes the address identification of the second L-GW;

The first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, including:

The first L-GW establishes a connection with the second L-GW according to the create session request;

The first L-GW sends a create session response, including:

The first L-GW sends a create session response to the first base station.

3. The method according to claim 1, wherein the first local gateway L-GW receives a session creation request, including:

The first L-GW receives a create session request sent by the first mobility management entity MME corresponding to the first L-GW, where the create session request includes the address identification of the second L-GW; The first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, including:

The first L-GW sends a create session response, including:

The first L-GW sends a create session response to the first MME.

4. The method according to claim 1, characterized in that the first local gateway L-GW Receive session creation requests, including:

The first L-GW receives a session creation request sent by the first base station corresponding to the first L-GW, where the session creation request includes the address identification of the P-GW;

The first L-GW sends a create session response to the first base station.

5. The method according to claim 1, wherein the first local gateway L-GW receives a session creation request, including:

The first L-GW receives a create session request sent by the first mobility management entity MME corresponding to the first L-GW, where the create session request includes the address identification of the P-GW; the first The L-GW establishes a connection with the second L-GW or the P-GW according to the create session request, including:

The first L-GW sends a create session response to the first MME.

6. The method according to any one of claims 1 to 3, characterized in that the first L-GW establishes a connection with the second L-GW or the P-GW according to the create session request. connections, including:

The first L-GW sends a proxy binding update or a bearer modification request to the second L-GW; the first L-GW receives a proxy binding response or a bearer modification response sent by the second L-GW. .

7. The method according to any one of claims 1, 4, and 5, characterized in that, the first L-GW establishes a connection with the second L-GW or the P_GW according to the create session request. connections, including:

The first L-GW sends a proxy binding update or bearer modification request to the P-GW; and the first L-GW receives the proxy binding response or bearer modification response sent by the P-GW.

8. A communication method, characterized by including:

The second local gateway L-GW receives the proxy binding update or bearer modification request, and the second The L-GW is connected before the user equipment UE switches to the first L-GW or the packet data network gateway P-GW;

The second L-GW establishes a connection with the first L-GW or the P-GW according to the proxy binding update or bearer modification request;

The second L-GW sends a proxy binding response or a modified bearer response.

9. The method according to claim 8, characterized in that,

The second local gateway L-GW receives the proxy binding update or bearer modification request, including: the second local gateway L-GW receives the proxy binding update or bearer modification request sent by the first L-GW;

The second L-GW establishes a bearer with the first L-GW or the P-GW according to the proxy binding update or bearer modification request, including:

The second L-GW establishes a connection with the first L-GW according to the proxy binding update or bearer modification request;

The second L-GW sends a proxy binding response or a bearer modification response, including:

The second L-GW sends a proxy binding response or a modified bearer response to the first L-GW.

10. The method according to claim 8, characterized in that,

The second local gateway L-GW receives the proxy binding update or bearer modification request, including: the second local gateway L-GW receives the proxy binding update or bearer modification request sent by the P-GW;

The second L-GW establishes a connection with the first L-GW or the P-GW according to the proxy binding update or bearer modification request, including:

The second L-GW establishes a connection with the P-GW according to the proxy binding update or bearer modification request;

11. The method according to claim 8 or 9, characterized in that, after the second L-GW sends a proxy binding response or a bearer modification response, it further includes:

The second local gateway L-GW receives the proxy binding update or session deletion request sent by the first L-GW;

The second L-GW deletes the connection with the first L-GW; The second L-GW sends a proxy binding response or a delete session response to the first L-GW.

12. The method according to claim 8 or 10, characterized in that, after the second L-GW sends a proxy binding response or a modified bearer response, it further includes:

The second local gateway L-GW receives the proxy binding update or session deletion request sent by the P-GW;

The second L-GW deletes the connection with the P-GW;

13. A communication method, characterized by including:

The second local gateway L-GW receives the proxy binding update or delete session request;

The second L-GW deletes the connection with the first L-GW or the connection with the packet data network gateway P-GW, the first L-GW is currently connected to the user equipment UE, and the second L-GW deletes the connection with the first L-GW or the connection with the packet data network gateway P-GW. The second L-GW or the P-GW is connected before the UE connects to the first L-GW;

The second L-GW sends a proxy binding response or a delete session response.

14. The method according to claim 13, characterized in that,

The second local gateway L-GW receives the proxy binding update or delete session request, including: the second L-GW receives the proxy binding update or delete session request sent by the first L-GW; the second L-GW receives the proxy binding update or delete session request sent by the first L-GW; -GW deletes the connection with the first L-GW or the connection with the P-GW, including:

The second L-GW deletes the connection with the first L-GW, the first L-GW is currently connected to the user equipment UE, and the second L-GW is connected to the first L-GW for the UE. L_GW was connected before;

The second L-GW sends a proxy binding response or a delete session response, including:

The second L-GW sends a proxy binding response or a delete session response to the first L-GW, so that the first L-GW sends a proxy message to the first base station or the first base station corresponding to the first L-GW. The MME sends a delete session response.

15. The method according to claim 13, characterized in that,

The second local gateway L-GW receives the proxy binding update or delete session request, including: the second L-GW receives the proxy binding update or delete session request sent by the P-GW; the second L-GW receives the proxy binding update or delete session request sent by the P-GW; -GW deletes the connection with P-GW, including:

The second L-GW deletes the connection with the P-GW, and the first L-GW is a user The device UE is currently connected to, and the P-GW was connected to the first L-GW before the UE connected to it; the second L-GW sends a proxy binding response or a delete session response, including:

The second L-GW sends a delete session response to the P-GW, so that the P-GW sends a proxy binding response or a delete session response to the first serving gateway S-GW corresponding to the P-GW. .

16. The method according to any one of claims 13 to 15, characterized in that, before the second local gateway L-GW receives the delete session request sent by the first L-GW, it further includes:

The second L-GW receives the modification bearer request sent by the first L-GW;

The second L-GW sends a modify bearer response to the first L-GW.

17. A communication method, characterized in that it includes: when the user equipment UE is handed over from the second base station to the first base station,

The first local gateway L-GW receives the bearer modification request;

The first L-GW changes the stored current serving node information of the UE from the second base station information to the first base station information, and the first base station and the second base station correspond to the same first L-GW; The first L-GW sends a modify bearer response.

18. The method according to claim 17, wherein the first L-GW receives a bearer modification request, including:

The first L-GW receives the modification bearer request sent by the first base station;

The first L-GW sends a modification bearer response, including:

The first L-GW sends a modification bearer response to the first base station.

19. The method according to claim 17, wherein the first L-GW receives a bearer modification request, including:

The first L-GW receives the modification bearer request sent by the first MME;

The first L-GW sends a modification bearer response, including:

The first L-GW sends a modify bearer response to the first MME.

20. A communication method, characterized in that it includes: when the user equipment switches from the second base station to the first base station,

The first mobility management entity MME receives the corresponding path switching request sent by the first base station, where the path switching request carries the distributed mobility management ID and the first local gateway L-GW address, and the path Handover request to cause the first L-GW to modify the information of the second base station stored in the first L-GW to the information of the first base station, the first base station and the second base station Corresponding to the same first L-GW;

The first MME switches the path of the first base station according to the path switching request to connect the first base station to the first L-GW;

The first MN sends a path switching response to the first base station, so that the first base station notifies the second base station to release resources.

21. A local gateway, characterized by including:

A receiving module, configured to receive a session creation request, where the session creation request carries the address identifier of the second local gateway L-GW or the address identifier of the packet data network gateway P-GW, the second L-GW, the P-GW is the user equipment UE connected before switching to the L-GW, and the UE is currently connected to the L-GW;

A processing module configured to establish a connection with the second L-GW or the P-GW according to the create session request;

Send module, used to send create session response.

22. The local gateway according to claim 21, characterized in that,

The receiving module is specifically configured to receive a session creation request sent by the first base station corresponding to the L-GW, where the session creation request includes the address identification of the second L-GW;

The processing module is specifically configured to establish a connection with the second L-GW according to the create session request;

The sending module is specifically configured to send a session creation response to the first base station.

23. The local gateway according to claim 21, characterized in that,

The receiving module is specifically configured to receive a session creation request sent by the first mobility management entity MME corresponding to the L-GW, where the session creation request includes the address identification of the second L-GW;

24. The local gateway according to claim 21, characterized in that,

The receiving module is specifically configured to receive a session creation request sent by the first base station corresponding to the L-GW, where the session creation request includes the address identification of the P-GW;

The processing module is specifically configured to establish a connection with the P-GW according to the create session request. connections between;

25. The local gateway according to claim 21, characterized in that,

The receiving module is specifically configured to receive a session creation request sent by the first mobility management entity MN corresponding to the first L-GW, where the session creation request includes the address identification of the P-GW;

26. The local gateway according to any one of claims 21-23, wherein the sending module is further configured to send a proxy binding update or bearer modification request to the second L-GW;

The receiving module is also configured to receive a proxy binding response or a modified bearer response sent by the second L-GW.

27. The local gateway according to any one of claims 21, 24, and 25, wherein the sending module is further configured to send a proxy binding update or bearer modification request to the P-GW;

The receiving module is also configured to receive a proxy binding response or a bearer modification response sent by the P-GW.

28. A local gateway, characterized by including:

A receiving module, configured to receive a proxy binding update or bearer modification request, where the local gateway L-GW is connected to the user equipment UE before switching to the first L-GW or packet data network gateway P-GW;

A processing module configured to establish a connection with the first L-GW or the P-GW according to the proxy binding update or bearer modification request;

Sending module, used to send proxy binding responses or modify bearer responses.

29. The local gateway according to claim 28, characterized in that,

The receiving module is specifically configured to receive a proxy binding update or bearer modification request sent by the first L-GW;

The processing module is specifically used to update or modify the bearer request according to the proxy binding, and Establish a connection with the first L-GW;

The sending module is specifically configured to send a proxy binding response or a bearer modification response to the first L-GW.

30. The local gateway according to claim 28, characterized in that,

The receiving module is specifically configured to receive a proxy binding update or bearer modification request sent by the P-GW;

The processing module is specifically configured to establish a connection with the P-GW according to the proxy binding update or bearer modification request;

The sending module is specifically configured to send a proxy binding response or a bearer modification response to the P-GW.

31. The local gateway according to claim 28 or 29, wherein the receiving module is further configured to receive a proxy binding update or session deletion request sent by the first L-GW;

The processing module is also configured to delete the connection with the first L-GW;

The sending module is also configured to send a proxy binding response or a delete session response to the first L-GW.

32. The local gateway according to claim 28 or 30, wherein the receiving module is further configured to receive a proxy binding update or session deletion request sent by the P-GW;

The processing module is also used to delete the connection with the P-GW;

The sending module is also configured to send a proxy binding response or a delete session response to the P-GW.

33. A local gateway, characterized by including:

The receiving module is used to receive proxy binding update or delete session requests;

A processing module configured to delete the connection with the first local gateway L-GW or the connection with the packet data network gateway P-GW, where the first L-GW is currently connected to the user equipment UE, and the L -GW or the P-GW is connected before the UE connects to the first L-GW;

Send module, used to send proxy binding response or delete session response.

34. The local gateway according to claim 33, characterized in that,

The receiving module is specifically configured to receive the proxy binding update or deletion sent by the first L-GW. session request;

The processing module is specifically used to delete the connection with the first L-GW, the first L-GW is currently connected to the user equipment UE, and the L-GW is connected to the first L-GW for the UE. -GW was connected before;

The sending module is specifically configured to send a proxy binding response or a delete session response to the first L-GW, so that the first L-GW sends a message to the first base station or the third base station corresponding to the first L-GW. An MME sends a delete session response.

35. The local gateway according to claim 33, characterized in that,

The receiving module is specifically configured to receive the proxy binding update or delete session request sent by the P-GW;

The processing module is specifically used to delete the connection with the P-GW, the first L-GW is currently connected to the user equipment UE, and the P-GW is connected to the first L-GW for the UE. -GW was connected before;

The sending module is specifically configured to send a delete session response to the P-GW, so that the P-GW sends a proxy binding response or a delete session response to the first serving gateway corresponding to the P-GW.

36. The local gateway according to any one of claims 33 to 35, characterized in that the receiving module is further configured to receive a bearer modification request sent by the first L-GW;

The sending module is also configured to send a modification bearer response to the first L-GW.

37. A local gateway, characterized in that it includes: when the user equipment UE is handed over from the second base station to the first base station,

The receiving module is used to receive modification bearer requests;

A processing module configured to change the stored current serving node information of the UE from the second base station information to the first base station information, where the first base station and the second base station correspond to the same local gateway;

The sending module is used to send the modification bearer response.

38. The local gateway according to claim 37, characterized in that,

The receiving module is specifically configured to receive a bearer modification request sent by the first base station; the sending module is specifically configured to send a bearer modification response to the first base station.

39. The local gateway according to claim 37, characterized in that, The receiving module is specifically configured to receive a bearer modification request sent by the first MME; the sending module is specifically configured to send a bearer modification response to the first MME.

40. A mobility management entity, characterized in that it includes: when the user equipment is handed over from the second base station to the first base station,

A receiving module, configured to receive a path switching request sent by the corresponding first base station, where the path switching request carries a distributed mobility management DMM identifier and a first local gateway L-GW address, where the path switching request ends with causing the first L-GW to modify the information of the second base station stored in the first L-GW to the information of the first base station, and the first base station and the second base station correspond to the same first L-GW ;

A processing module configured to switch the path of the first base station to connect the first base station to the first L-GW according to the path switching request;

A sending module, configured to send a path switching response to the first base station to release resources between the first base station and the second base station.

41. A local gateway L-GW, characterized in that it includes: a transmitter, a receiver, a memory, and a processor connected to the transmitter, the receiver, and the memory respectively, wherein: in the memory A set of program codes is stored, and the processor is configured to call the program codes stored in the memory to execute the method according to any one of claims 1-7.

42. A local gateway L-GW, characterized in that it includes: a transmitter, a receiver, a memory, and a processor connected to the transmitter, the receiver, and the memory respectively, wherein: in the memory A set of program codes is stored, and the processor is configured to call the program codes stored in the memory to execute the method according to any one of claims 8-12.

43. A local gateway L-GW, characterized in that it includes: a transmitter, a receiver, a memory, and a processor connected to the transmitter, the receiver, and the memory respectively, wherein: in the memory A set of program codes is stored, and the processor is configured to call the program codes stored in the memory to execute the method according to any one of claims 13-16.

44. A local gateway L-GW, characterized in that it includes: a transmitter, a receiver, a memory, and a processor connected to the transmitter, the receiver, and the memory respectively, wherein: in the memory A set of program codes is stored, and the processor is configured to call the program codes stored in the memory to execute the method according to any one of claims 17-19.

45. A mobility management entity EL, characterized in that it includes: a transmitter, a receiver, a memory and a processor respectively connected to the transmitter, the receiver and the memory, wherein a set of program codes is stored in the memory, and the processor is used to call the program code stored in the memory, The method as claimed in claim 20 is performed.