WO2015054847A1

WO2015054847A1 - Communication method, local gateway, base station, mme, and system

Info

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

Abstract

Provided are a communication method, a local gateway (L-GW), a base station, an MME, and a system. The method comprises: an L-GW receives a delete session request; the L-GW, according to the delete session request, deletes an established bearer; the L-GW sends a delete session response, thereby establishing a connection between a UE and the L-GW. Since the UE is able to use different IP addresses to connect to different L-GWs and corresponding base stations, and initiate a session, single-point failure within a communication system is thus avoided, and communication security is further improved.

Description

Communication method, local gateway, base station, MME, and system

TECHNICAL FIELD Embodiments of the present invention relate to communication technologies, and in particular, to a communication method, a local gateway, a base station, an MME, and a system.

Background technique

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 an attach request message to the base station eNB of the cell in which it is located, and then, The eNB selects a mobility management entity (Mobility Management Entity, hereinafter referred to as ΜΜΕ) that the UE can attach according to the attachment request information, and selects a Serving Gateway (hereinafter referred to as S-GW) and a packet data network gateway (which may be attached). The Packet Data Network Gateway (hereinafter referred to as P-GW), and the P-GW allocates an IP address to the UE, that is, establishes an EPS bearer between the UE and the P-GW, and considers it to be an EPS default bearer.

During the process from the start-up to the shutdown of the UE, the default bearer will always provide services for the UE. After the UE moves, it camps on another base station. Further, the eNB may select another MME for the UE, and the MME may select an appropriate S-GW for the mobile UE, but the P-GW does not change, that is, P -GW as an anchor for mobility management is fixed.

However, if the P-GW fails or is a safety issue, it will cause a single point of failure and a single point of security in the communication system. Summary of the invention

The embodiments of the present invention provide a communication method, a local gateway, a base station, an MME, and a system, to solve the problem of single point failure and single point security caused by P-GW in the existing communication system.

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

The local gateway L-GW receives the create session request;

The L-GW establishes a bearer according to the creation session request;

The L-GW sends a create session response. In a first possible implementation manner of the first aspect, after the sending the bearer response, the method further includes:

The L-GW receives a delete session request;

Deleting the established bearer according to the deletion session request by the L-GW;

The L-GW sends a delete session response.

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

The L-GW receives a create session request sent by the base station corresponding to the L-GW, where the create session request is that the base station corresponding to the L-GW receives the initial context setup request sent by the MME or 7 Sent after the request is established;

The L-GW establishes a bearer according to the create session request, and includes:

And establishing, by the L-GW, a bearer for a specific user between the base station corresponding to the L-GW and the L-GW;

The sending creates a session response, including:

Sending a create session response to the base station corresponding to the L-GW, so that the

The radio resource control RRC connection reconfiguration is performed between the base station corresponding to the L-GW and the user equipment UE.

According to a second possible implementation manner of the first aspect, in a third possible implementation manner, the receiving, by the L-GW, a delete session request includes:

The L-GW receives the delete session request sent by the base station corresponding to the L-GW, where the delete session request is sent by the base station corresponding to the L-GW to the mobility management entity MME. Transmitted after deactivating the bearer request;

Deleting the bearer according to the deletion session request, the L-GW includes:

The L-GW deletes a bearer for a specific user between the L-GW and a base station corresponding to the L-GW;

The sending a delete bearer response includes:

Sending a delete session response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW sends a deactivation bearer response to the MME.

In a fourth possible implementation manner of the first aspect, the local gateway L-GW receives the create session request, including: Receiving, by the L-GW, a create session request sent by the MME, where the create session request is sent by the MME after receiving an attach request or a PDN connection request sent by the base station corresponding to the L-GW;

The sending creates a session response, including:

And sending a create session response to the MME, so that the MME sends an initial context setup request or a seven-layer setup request to the base station corresponding to the L-GW.

According to the first possible implementation manner of the first aspect, in a fifth possible implementation, the receiving, by the L-GW, a delete session request includes:

The L-GW receives a delete session request sent by the MME, where the delete session request is that the MME determines to initiate a detach process after receiving a PDN detach request or detach request forwarded by the UE through the corresponding base station. Or sent by the HSS after sending a cancel location message to the MME;

The sending a delete session response includes:

Sending a delete session response to the MME, so that the MME sends a deactivation bearer request to the base station corresponding to the L-GW or sends a detach accept message to the UE or the MME receives the terminal to send The de-attach accept message.

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

Receiving, by the base station, an initial context setup request or a bearer setup request sent by the MME; sending a create session request to the L-GW corresponding to the base station;

Receiving a create session response sent by the corresponding L-GW;

Perform RRC connection reconfiguration.

In a first possible implementation manner of the second aspect, after performing the RRC connection reconfiguration, the method further includes:

Receiving a deactivation bearer request sent by the MME, where the deactivation bearer request carries an LBI Identification

Sending a delete session request to the L-GW corresponding to the base station;

Receiving a deletion session response sent by the corresponding L-GW;

Sending a deactivation bearer response to the MME.

According to the second aspect, and any one of the first possible implementation manners of the second aspect, in a second possible implementation manner, if the base station receives the initial context setup request sent by the MME, performing the RRC connection reconfiguration After that, it also includes:

Sending an initial context setup response to the MME, where the 7-layer setup response includes an evolved packet system bearer quality of service;

If the base station receives the bearer setup request sent by the MME, the performing the RRC connection reconfiguration includes:

A 7-load setup response is sent to the MME.

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

The MME sends an initial context setup request to the base station, so that the base station establishes a bearer between the L-GWs corresponding to the base station;

And the MME receives an initial context setup response returned by the base station, where the bearer setup response includes an evolved packet system bearer quality of service.

In a first possible implementation manner of the third aspect, after the receiving the initial context setup response returned by the base station, the method further includes:

Transmitting a bearer setup request to the base station, so that the base station establishes a corresponding to the base station

7| between L-GWs;

Receiving a bearer setup response returned by the base station.

According to the third aspect, and the first possible implementation manner of the third aspect, in a second possible implementation, after the receiving the initial context setup response returned by the base station, the method further includes:

Sending a deactivation bearer request to the base station, so that the base station ends an established bearer between the L-GWs corresponding to the base station, where the deactivation bearer request carries an LBI identifier;

Receiving a deactivation bearer response returned by the base station.

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

Sending, by the MME, a create session request to the L-GW, so as to establish a bearer with the L-GW; Receiving a create session response returned by the LG W.

In a first possible implementation manner of the fourth aspect, after the receiving the session response that is returned by the L-GW, the method further includes:

Sending a delete session request to the L-GW to end the bearer established between the L-GW and the L-GW;

Receive the delete session response sent by the L-GW.

According to the fourth aspect, and the first possible implementation manner of the fourth aspect, in a second possible implementation, before the sending, by the MME, the create session request to the L-GW, the method further includes:

The MME receives an attach request sent by a base station corresponding to the L-GW, where the attach request carries a distributed mobility management DMM identifier;

Performing authentication and location update according to the attach request;

After receiving the create session response returned by the L-GW, the method further includes:

And sending an initial context setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

According to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, before the sending the delete session request to the L-GW, the method further includes: receiving a detach request sent by the UE; After receiving the delete session response sent by the L-GW, the method further includes: sending an attach accept message to the UE;

Or, before the sending the delete session request to the L-GW, the method further includes: sending a detach request to the UE; after receiving the delete session response sent by the L-GW, the method further includes: receiving an attach accept sent by the UE Message.

According to the fourth aspect, and any one of the first possible implementation manners of the fourth aspect, in a fourth possible implementation manner, before the sending, by the MME, the create session request to the L-GW, the method further includes:

The MME receives a PDN connection request sent by the base station corresponding to the L-GW; and after receiving the create session response returned by the L-GW, the MME further includes:

And transmitting a bearer setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

According to a fourth possible implementation of the fourth aspect, in a fifth possible implementation Before the sending the delete session request to the L-GW, the method further includes:

Receiving, by the receiving terminal, a PDN disconnection request sent by the base station corresponding to the L-GW; and after receiving the delete session response sent by the L-GW, the method further includes:

And sending a deactivation bearer request to the corresponding base station, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

In a fifth aspect, the embodiment of the present invention provides a local gateway L-GW, including: a receiving module, configured to receive a create session request;

a processing module, configured to establish a bearer according to the creating a session request;

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

In a first possible implementation manner of the fifth aspect, the receiving module is further configured to: after the sending module sends the create session response, receive a delete session request;

The processing module is further configured to: after the receiving module receives the delete session request, delete the established bearer;

The sending module is further configured to send a delete session response after the processing module deletes the established bearer.

In a second possible implementation manner of the fifth aspect, the receiving module is specifically configured to create a session request sent by a base station corresponding to the L-GW, where the create session request is the L- The base station corresponding to the GW is sent after receiving the initial context setup request or the bearer setup request sent by the MME;

The processing module is specifically configured to establish a bearer for a specific user between the base stations corresponding to the L-GW;

The sending module is configured to send a session establishment response to the base station corresponding to the L-GW, so that the RRC connection between the base station corresponding to the L-GW and the user equipment UE is performed. Reconfiguration.

According to a first possible implementation manner of the fifth aspect, in a third possible implementation, the receiving module is specifically configured to delete a session request sent by a base station corresponding to the L-GW, and the deleting session The request is that the base station corresponding to the L-GW sends after receiving the deactivation bearer request sent by the mobility management entity MME;

The processing module is specifically configured to delete a bearer for a specific user between the base stations corresponding to the L-GW; The sending module is configured to send a delete session response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW sends a deactivation bearer response to the MME.

In a fourth possible implementation manner of the fifth aspect, the receiving module is configured to receive a create session request sent by the MME, where the create session request is that the MME receives the L-GW corresponding to the L-GW. And the processing module is configured to: establish a bearer for a specific user between the L-GW and the base station corresponding to the L-GW, where the base station sends an attach request or a PDN connection request;

The sending module is specifically configured to send a create session response to the MME, so that the MME sends an initial context setup request or a bearer setup request to the base station corresponding to the L-GW.

According to the first possible implementation manner of the fifth aspect, in a fifth possible implementation, the receiving module is configured to receive a delete session request sent by the MME, where the delete session request is that the MME is receiving After the UE sends a cancel request message or a detach request by the corresponding base station, or the MME decides to initiate a detach procedure or the HSS sends a cancel location message to the MME, and then sends the message to the MME;

The processing module is specifically configured to delete a bearer for a specific user between the L-GW and a base station corresponding to the L-GW;

The sending module is specifically configured to send a delete session response to the MME, so that the MME sends a deactivation request to the base station corresponding to the L-GW or sends a detach request to the UE. The message or the MME receives the detach accept message sent by the terminal.

In a sixth aspect, an embodiment of the present invention provides a base station, including:

a receiving module, configured to receive an initial context setup request or a bearer setup request sent by the MME, and after the sending module sends a create session request, receive a create session response sent by the corresponding L-GW;

The sending module is configured to send the create session request to an L-GW corresponding to the base station;

And a processing module, configured to perform RRC connection reconfiguration after the receiving module receives the created session response sent by the corresponding L-GW.

In a first possible implementation manner of the sixth aspect, the receiving module is further configured to: after the processing module performs RRC connection reconfiguration, receive a deactivation bearer request sent by the MME, where The deactivation bearer request carries an LBI identifier;

The sending module is further configured to: after the receiving module receives the deactivation bearer request sent by the MME, send a delete session request to the L-GW corresponding to the base station; and receive the corresponding L in the receiving module. After the delete session response sent by the GW, sending a deactivation bearer response to the MME;

The receiving module is further configured to: after the sending module sends the delete session request, receive the delete session response sent by the corresponding L-GW.

According to the sixth aspect, and any one of the first possible implementation manners of the sixth aspect, in a second possible implementation, the sending module is further configured to perform RRC connection reconfiguration in the processing module. Thereafter, an initial context setup response is sent to the MME, where the bearer setup response includes an evolved packet system bearer quality of service, and a bearer setup response is sent to the MME.

In a seventh aspect, an embodiment of the present invention provides an MME, including:

a sending module, configured to send an initial context setup request to the base station, so that the base station establishes a bearer between the L-GWs corresponding to the base station;

And a receiving module, configured to receive an initial context setup response returned by the base station, where the bearer setup response includes an evolved packet system bearer quality of service.

In a first possible implementation manner of the seventh aspect, the sending module is further configured to: after the receiving module receives an initial context setup response returned by the base station, send a bearer setup request to the base station, so that The base station establishes a bearer between the L-GWs corresponding to the base station, and the receiving module is further configured to: after the sending module sends the bearer setup request, receive a bearer setup response returned by the base station.

According to any one of the seventh aspect and the first possible implementation manner of the seventh aspect, in a second possible implementation, the sending module is configured to receive, at the receiving module, an initial returned by the base station After the context establishment response, the deactivated bearer request is sent to the base station, so that the base station ends the established bearer between the L-GWs corresponding to the base station, where the deactivated bearer request carries the LBI identifier;

The receiving module is further configured to: after the sending module sends the deactivation bearer request, receive a deactivated bearer response returned by the base station.

In an eighth aspect, an embodiment of the present invention provides an MME, including: a sending module, configured to send a create session request to the L-GW, so as to establish a bearer with the L-GW;

And a receiving module, configured to receive a create session response returned by the L-GW.

In a first possible implementation manner of the eighth aspect, after the receiving the session response sent by the L-GW, the method further includes:

The sending module is further configured to: after the receiving module receives the create session response returned by the L-GW, send a delete session request to the L-GW, so that the end is established with the L-GW. Load

The receiving module is further configured to: after the sending module sends the delete session request, receive a delete session response sent by the L-GW.

According to the eighth aspect, and the first possible implementation manner of the eighth aspect, in a second possible implementation, the MME further includes: a processing module,

The receiving module is further configured to: before the sending module sends the create session request, receive an attach request sent by a base station corresponding to the L-GW, where the attach request carries a distributed mobility management DMM identifier;

The processing module is configured to perform authentication and location update according to the receiving module receiving the attach request;

The sending module is further configured to: after the receiving module receives the created session response returned by the L-GW, send an initial context setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

According to a second possible implementation manner of the eighth aspect, in a third possible implementation, the receiving module is further configured to: before the sending module sends the delete session request, receive a detachment sent by the UE. Request

The sending module is further configured to: after the receiving module receives the delete session response sent by the L-GW, send an attach accept message to the UE;

Or,

The processing module is further configured to send a detach request to the UE before the sending module sends a delete session request to the L-GW;

The receiving module is further configured to: after receiving the delete session response sent by the L-GW, receive an attach accept message sent by the UE. According to any of the eighth aspect and the first possible implementation manner of the eighth aspect, in a fourth possible implementation, the receiving module is further configured to send the sending module to the L-GW to create Before receiving the session request, receiving a PDN connection request sent by the base station corresponding to the L-GW;

The sending module is further configured to: after the receiving module receives the created session response returned by the L-GW, send a bearer setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

According to a fourth possible implementation manner of the eighth aspect, in a fifth possible implementation, the receiving module is further configured to: before the sending module sends a delete session request to the L-GW, the receiving terminal a PDN disconnection request sent by the base station corresponding to the L-GW; the processing module is further configured to: after the receiving module receives the delete session response sent by the L-GW, send the deactivate to the corresponding base station Carrying a request, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

A ninth aspect, the embodiment of the present invention provides a communication system, including: a local gateway L-GW provided by any device embodiment of the present invention, a base station provided by any device embodiment of the present invention, and any device embodiment of the present invention The mobility management entity MME provided.

In a first possible implementation manner of the ninth aspect, an interface is set between the L-GW and the MME corresponding to the L-GW.

In a second possible implementation manner of the ninth aspect, the interface between the L-GW and the MME corresponding to the L-GW is not set.

A tenth 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 program code stored in the memory, to perform the first aspect of the present invention, the first to fifth possible implementations of the first aspect Communication method.

According to a tenth aspect, an embodiment of the present invention provides a base station, including: a transmitter, a receiver, a memory, and a processor respectively connected to the transmitter, the receiver, and the memory, where A set of program code is stored, and the processor is configured to invoke the program code stored in the memory to perform the communication method provided by the second aspect of the present invention, the first to second possible implementations of the first aspect. According to an eleventh aspect, an embodiment of the present invention provides a mobility management entity MME, 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 program code stored in the memory to perform the third aspect, the third aspect, the first to the second, the fourth aspect, and the third aspect of the present invention The communication method provided by the first to fifth possible implementations of the four aspects.

The twelfth aspect, the embodiment of the present invention provides a communication system, including: the local gateway L-GW according to claim 40, the base station according to claim 41, and the method according to claim 42 Mobility Management Entity MME.

The communication method provided in this embodiment receives a create session request through the L-GW, and establishes a default bearer according to the create session request, and the L-GW sends a create session response, thereby establishing a connection between the UE and the L-GW, and Different IP addresses can be used to connect and initiate sessions with different L-GWs and corresponding base stations, thereby avoiding single points of failure in the communication system and further improving communication security.

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 still 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 flowchart of a communication method according to still another embodiment of the present invention;

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

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

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

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

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

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

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

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

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

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

FIG. 18 is a schematic structural diagram of a base station according to an embodiment of the present invention; FIG.

FIG. 19 is a schematic structural diagram of an MME according to an embodiment of the present invention; FIG.

20 is a schematic structural diagram of an MME according to still another embodiment of the present invention;

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

FIG. 22 is a schematic structural diagram of a base station according to still another embodiment of the present invention; FIG.

FIG. 23 is a schematic structural diagram of an MME according to still another embodiment of the present invention. The embodiment of the present invention is applied to a network in a distributed mobility management (DMM) network, or a network in which a DMM network and an EPS network coexist, wherein the DMM network in the embodiment of the present invention is The existing EPS network is further improved. The specific implementation includes at least two types. The first implementation manner is to set a local gateway (Local Gateway) corresponding to the base station for each base station of the existing EPS network. The following is abbreviated as L-GW. The second implementation manner is to set an L-GW corresponding to the multiple base stations for multiple base stations of the existing EPS network.

Regardless of the implementation manner of the foregoing, the DMM network can be divided into two application scenarios. In the first application scenario, no interface is set between the MME and the L-GW, and the bearer between the UE and the network side device is established and modified. The process is performed by the MME through the base station and the L-GW corresponding to the base station; in the second application scenario, an interface is set between the MME and the L-GW, which is similar to the processing in the EPS network, L- The GW is equivalent to the combination of the S-GW and the P-GW, and the functions and functions of the L-GW are similar to those of the S-GW and the P-GW in the EPS network. The details will be specifically described below.

The following is a detailed description of the DMM network or the network where the DMM network and the EPS network coexist. Bright.

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 specifically includes the following steps:

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

Specifically, the L-GW can receive the create session request in the at least two scenarios. In the first scenario, after the UE is powered on, the device needs to establish an attach with the network device, and the second scenario is to establish an attach between the UE and the network device. After that, the UE needs to establish a new packet data network (PDN) connection with the network side device.

Further, in this embodiment, the application scenario in which the L-GW receives the request for creating a session is divided into two types according to whether an interface is set between the MME and the L-GW. The first application scenario is in the MME and the L-GW. When there is no interface, the L-GW receives a create session request sent by the base station corresponding to the L-GW, and the create session request is sent by the base station corresponding to the L-GW after receiving the initial context setup request sent by the MME; In a second application scenario, when an interface exists between the MME and the L-GW, the L-GW receives a create session request sent by the MME, where the create session request is an attach request sent by the MME to receive the base station corresponding to the L-GW or Sent after the PDN connection request.

Step 102: The L-GW establishes a default bearer according to the create session request.

In this embodiment, according to whether an interface is set between the MME and the L-GW,

The L-GW establishes a default bearer according to the creation of a session request into two application scenarios. In the first application scenario, when there is no interface between the MME and the L-GW, the L-GW establishes a session request with the base station, and establishes a session request with the base station. In the second application scenario, when an interface exists between the MME and the L-GW, the L-GW establishes a default bearer with the MME according to the create session request sent by the MME.

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

The L-GW sends a session response. The first scenario is that when there is no interface between the MME and the L-GW, the L-GW sends a session response to the base station that sends the session request to make the base station. Radio resource control (RRC) connection reconfiguration is performed with the user equipment UE, that is, the air interface signaling connection is reconfigured between the base station and the UE; the second application scenario is between the MME and the L-GW. L-GW to MME when interface exists A create session response is sent to cause the MME to send an initial context setup request to the base station that sent the attach request.

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:

After the L-GW sends a create bearer response in step 103 of the embodiment shown in FIG. 1, the method may further include:

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

Specifically, according to whether an interface is configured between the MME and the L-GW, the embodiment can be applied to at least two scenarios:

In the first scenario, the interface between the MME and the L-GW is not set. In this scenario, according to the information sent by the UE, the embodiment may be further divided into three implementation manners. The first implementation manner, if the UE and the network side The device has established a plurality of PDN connections, and the UE may send a PDN disconnection request to the MME through the base station, and the MME sends a deactivation bearer request to the base station, where the deactivated bearer request carries the LBI identifier, that is, the default identifier of the PDN connection. Then, the L-GW receives a delete session request sent by the base station corresponding to the L-GW, where the delete session request is used to connect to a line between the L-GW that the UE indicates to connect and the base station corresponding to the L-GW. In the second implementation manner, if the UE and the network side device have established multiple PDN connections, the UE may send a detach request to the MME through the base station, or the MME may send a detach request to the UE through the base station, or, the HSS Sending a cancel location message to the MME, whether the UE or the MME or the HSS initiates detachment, the MME may send a deactivation bearer request for each PDN connection to the base station, and then, the L-GW receives the base station corresponding to the L-GW. Sending a delete session request for each PDN connection, where the delete session request is used to connect a PDN connection between the L-GW and the base station corresponding to the L-GW; and the third implementation manner, if the UE and the network The eNB may send a detach request to the MME through the base station, or the MME may send a detach request to the UE through the base station, whether it is the UE or The MME may send a deactivation request to the base station, and then the L-GW receives the delete bearer request sent by the base station corresponding to the L-GW, where the delete bearer request is used to detach the L- The connection between the GW and the base station corresponding to the L-GW.

In the second scenario, an interface is configured between the MME and the L-GW. In this scenario, according to the information sent by the UE, the embodiment may be further divided into two implementation manners. The first implementation manner, if the UE and the network side The device has established a plurality of PDN connections, and the UE may send a PDN disconnection request to the MME through the base station, and the MME sends a delete session request to the L-GW corresponding to the base station, where the delete session request is used to connect to the UE indication. A PDN connection is established between the L-GW and the MME. In a second implementation manner, if the UE and the network-side device have established multiple PDN connections, the UE may send a detach request to the MME through the base station, or the MME may pass The base station sends a detach request to the UE, or the HSS sends a cancel location message to the MME, whether the UE or the MME or the HSS initiates detachment, and the MME may send a delete session for each PDN connection to the L-GW corresponding to the base station. a request, where the deletion session request is used to connect to a PDN connection between the L-GW and the MME; and the third implementation manner, if the UE and the network side The MME can send a detach request to the MME through the base station. Alternatively, the MME can send a detach request to the UE through the base station. The MME can send the detach request to the MME. The GW sends a delete bearer request, where the delete bearer request is used to detach the connection between the L-GW and the MME.

Step 202: The L-GW deletes the established bearer according to the deletion session request.

In the first scenario, the interface between the MME and the L-GW is not set. In this scenario, according to the information sent by the UE, the embodiment may be further divided into two implementation manners. The first implementation manner, if the UE and the network side The device has established multiple PDN connections, and the UE may send a PDN disconnection request to the MME through the base station, and after the L-GW receives the delete session request sent by the base station corresponding to the L-GW, deletes the L-GW and the L- a PDN connection indicated by the UE between the base stations corresponding to the GW; in a second implementation manner, if the UE and the network side device have established multiple PDN connections, the UE may send a detach request to the MME through the base station, or the MME may Sending a detach request to the UE by the base station, or the HSS sends a cancel location message to the MME, Regardless of whether the UE or the MME or the HSS initiates the detachment, after the L-GW receives a deletion session request for each PDN connection sent by the base station corresponding to the L-GW, the deletion corresponds to the L-GW at the L-GW. A PDN connection between the base stations.

In the second scenario, an interface is configured between the MME and the L-GW. In this scenario, according to the information sent by the UE, the embodiment may be further divided into two implementation manners. The first implementation manner, if the UE and the network side The device has established a plurality of PDN connections, and the UE sends a PDN disconnection request to the MME through the base station. After the L-GW receives the delete session request sent by the MME, the L-GW deletes a PDN connection indicated by the UE between the L-GW and the MME. In the second implementation manner, if the UE and the network side device have established multiple PDN connections, the UE may send a detach request to the MME through the base station, or the MME may send a detach request to the UE through the base station, or the HSS sends the detach request to the MME. Cancel the location message, whether it is the UE or the MME or the HSS initiated detachment, after the L-GW receives a deletion session request for each PDN connection sent by the MME, deletes a PDN connection between the L-GW and the MME. .

Step 203: The L-GW sends a delete session response.

Specifically, when there is no interface between the MME and the L-GW, the L-GW sends a delete session response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW sends a deactivated bearer response to the MME. When an interface exists between the MME and the L-GW, the L-GW sends a delete session response to the MME, so that the MME sends a deactivation bearer request to the base station corresponding to the L-GW or sends a detach accept message or the MME receiving terminal to the terminal. The sent de-attach accept message.

3 is a schematic flowchart of a communication method according to still another embodiment of the present invention; as shown in FIG. 3, the embodiment is applicable to a DMM network, or a network where a DMM network and an EPS network coexist, regardless of where the embodiment is applied. The network may include at least two implementation manners. In the first implementation manner, each base station of the existing EPS network is connected to a corresponding local gateway (Local Gateway, hereinafter referred to as L-GW), and the second implementation manner , connecting multiple base stations of the existing EPS network to a corresponding L-GW. In the above-mentioned implementation manner, when the interface is not set between the MME and the L-GW, the communication method may specifically include the following steps:

Step 301: The base station receives an initial context setup request or a bearer setup request sent by the MME.

In this embodiment, the base station receives the request sent by the MME into two cases. In the first scenario, after the UE needs to establish an attachment with the network side device, the base station may receive the MME. The initial scenario establishment request; the second scenario, after the UE has established a connection with the network side device, the UE needs to establish a new packet data network (PDN) connection with the network side device, and the base station can receive A bearer setup request sent by the MME.

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

In this embodiment, the base station sends a create session request to the L-GW corresponding to the base station to establish a request between the base station and the L-GW corresponding to the base station, regardless of which request is sent by the MME. |Loaded.

The base station allocates a base station tunnel end identifier and an address to the L-GW corresponding to the base station, and the base station sends a create session request to the L-GW corresponding to the base station, and receives the base station from the L-GW corresponding to the base station. After the created session request is sent, the L-GW corresponding to the base station allocates the L-GW tunnel endpoint identifier and address, thereby completing the establishment of the tunnel between the base station and the L-GW corresponding to the base station, and the tunnel can be used. The endpoint identifier and address are used to identify the bearer, that is, the TEID (Tunnel Endpoint Identifier) and the address are used to identify a bearer.

Step 303: The base station receives a create session response sent by the corresponding L-GW.

In this embodiment, the base station receives the create session response sent by the corresponding L-GW, so that the RRC connection reconfiguration is performed between the base station corresponding to the L-GW and the user equipment UE.

Step 304: The base station performs RRC connection reconfiguration with the UE, that is, reconfiguration of the air interface signaling connection between the base station and the UE.

In the communication method provided by the embodiment, after the base station receives the initial context setup request or the bearer setup request sent by the MME, the base station sends a create session request to the L-GW corresponding to the base station, and the base station receives the corresponding L-GW transmission. A session response is created. Then, the base station performs RRC connection reconfiguration with the UE, so as to establish a connection between the UE and the L-GW, and the UE can use different IP addresses to connect with different L-GWs and corresponding base stations and initiate a session. , thereby avoiding a single point of failure in the communication system and further improving the security of the communication.

After the RRC connection reconfiguration is performed by the base station and the UE in step 304 of the embodiment, the base station may further include:

Step 305: The base station sends an initial context setup response to the MME.

Establishing a bearer between the base station and the corresponding L-GW, and establishing an RRC between the base station and the UE After the connection reconfiguration, the base station can send an initial context setup response to the MME. Step 306: The base station receives a deactivation bearer request sent by the MME.

In this embodiment, the base station may receive the deactivation bearer request sent by the MME in at least two scenarios. In the first scenario, the UE and the network side device have established at least one PDN connection, and the UE sends the PDN to the MME. In the scenario of the connection request, the base station receives the deactivation bearer request sent by the MME, where the deactivation bearer request is used to deactivate a PDN connection between the base station and the L-GW corresponding to the base station. In the second scenario, the UE and the network side device have established at least one PDN connection, and in the scenario that the UE sends a detach request to the MME, the base station receives the deactivation bearer request sent by the MME for each PDN connection, where The bearer request is deactivated to deactivate a PDN connection between the base station and the L-GW corresponding to the base station.

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

Specifically, the base station may send a delete session request to the L-GW corresponding to the base station in the at least three scenarios. In the first scenario, the UE and the network side device have established at least one PDN connection, and the UE sends the PDN to the MME. In a scenario of the connection request, the base station may send a deletion session request for each PDN connection to the L-GW corresponding to the base station, where the deletion session request is used to delete the L-GW corresponding to the base station and the base station. A PDN connection. In the second scenario, the UE and the network side device have established at least one PDN connection, and in a scenario where the UE sends a detach request to the MME, the base station may send a deletion for each PDN connection to the L-GW corresponding to the base station. a session request, where the delete session request is used to delete a PDN connection between the base station and the L-GW corresponding to the base station.

Step 308: The base station receives a delete session response sent by the corresponding L-GW.

In this embodiment, after the L-GW corresponding to the base station deletes the PDN connection, the base station may receive the delete session response sent by the corresponding L-GW.

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

After the base station and the L-GW corresponding to the base station delete the PDN connection, the base station may send a deactivation bearer response to the MME.

Further, in step 301, if the base station receives the initial context setup request sent by the MME, after performing the RRC connection reconfiguration, the base station may further include:

The base station sends an initial context setup response to the MME; Further, in step 301, if the base station receives the bearer setup request sent by the MME, the RRC connection reconfiguration may further include:

The base station sends a 7-load setup response to the MME.

It should be noted that an interface is provided between the MME and the L-GW. In this manner, the functions and processing modes of the base station are similar to those of the base station in the EPS network, and are not described in this embodiment.

4 is a schematic flowchart of a communication method according to still another embodiment of the present invention; as shown in FIG. 4, the embodiment is applicable to a DMM network, or a network where a DMM network and an EPS network coexist, and at least two implementation manners are included. The first implementation manner is to connect each base station of the existing EPS network to a corresponding L-GW. In the second implementation manner, multiple base stations of the existing EPS network are connected to a corresponding L-GW. In the above-mentioned implementation manner, when the interface is not set between the MME and the L-GW, the communication method may specifically include the following steps:

Step 401: The MME sends an initial context setup request to the base station, so that the base station establishes a bearer between the L-GWs corresponding to the base station.

In this embodiment, when the UE is initially attached, the UE may send an attach request to the MME through the base station, and then the MME sends an initial context setup request to the base station, so that the base station establishes an L-GW corresponding to the base station. An initial PDN connection, where the initial context setup request carries the attach accept information, and the DMM identifier is added to the attach accept information, where the DMM identifier is that the MME allows the UE to access the network with the DMM feature. in.

Step 402: The MME receives an initial context setup response returned by the base station.

Specifically, after the base station establishes a bearer with the L-GW corresponding to the base station, and after the UE performs RRC connection reconfiguration with the base station, the MME receives an initial context setup response returned by the base station, where the initial context setup response carries Establish bearer information, for example, PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR (Access Point Name) -Aggregate Maximum Bit Rate, access point name - aggregate maximum rate, etc. The MME stores the information of the bearers for future base station re-establishment of the UE context in a service request (Service Request) procedure.

In the communication method provided in this embodiment, the initial context setup is sent to the base station by the MME. So that the base station triggers the L-GW corresponding to the base station to establish a bearer, and then receives the initial context setup response returned by the base station, thereby establishing a connection between the UE and the L-GW, and because the UE can use different The IP address is connected to different L-GWs and corresponding base stations and initiates a session, thereby avoiding a single point of failure in the communication system and further improving the security of the communication.

On the basis of the foregoing embodiment, after the UE is attached to the network, after the step 402, that is, after the UE has established the attachment, the UE may further include:

Step 403: The MME sends a create session request to the base station, so that the base station establishes a bearer between the L-GW corresponding to the base station.

In this embodiment, after the UE sends the PDN connection request to the MME, the MME sends a create session request to the base station, so that the base station triggers the L-GW corresponding to the base station to establish a bearer, that is, the base station triggers the L- corresponding to the base station. The GW establishes a bearer, where the bearer setup request carries the PDN connection accepting information, and adds a DMM identifier (DMM-enabled) to the PDN connection accepting information, where the DMM identifier is that the MME allows the UE to access the network having the DMM characteristic. in.

Step 404: The MME receives a create session response returned by the base station.

Specifically, after the base station and the L-GW corresponding to the base station establish a bearer, and after the UE performs RRC connection reconfiguration with the base station, the MME receives a create session response returned by the base station, where the create session response carries the established bearer. Information such as PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, etc.

On the basis of the foregoing embodiment, after the step 402, that is, after the UE has established the attachment, the method may further include:

Step 405: The MME sends a deactivation bearer request to the base station, so that the base station triggers the L-GW corresponding to the base station to end the established bearer.

Specifically, the embodiment may be divided into three implementation manners. In the first implementation manner, if the UE and the network side device have established multiple PDN connections, the UE may send a PDN disconnection request to the MME through the base station, and the MME sends the PDN to the base station. Sending a deactivation bearer request, where the deactivation bearer request is used to connect the UE to connect to a PDN connection between the base station and the L-GW corresponding to the base station, that is, to end the L-GW corresponding to the base station and the base station. An established bearer is provided; in the second implementation manner, if the UE and the network side device have established multiple PDN connections, The UE may send a detach request to the MME through the base station, or the MME may send a detach request to the UE by using the eNB, and the MME may send a deactivation request to the eNB, whether the MME or the MME initiates the detach request. Deactivating a bearer request to connect all the established PDN connections between the base station and the L-GW corresponding to the base station, that is, ending all bearers established between the base station and the L-GW corresponding to the base station; The MME may send a detach request to the MME through the base station, or the MME may send a detach request to the UE by using the base station, whether the MME or the MME initiates the detach request, the MME. The deactivated bearer request may be sent to the base station, where the deactivated bearer request is used to delete the bearer between the L-GW and the base station corresponding to the L-GW.

Step 406: The MME receives a deactivated bearer response returned by the base station.

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 embodiment is applicable to a DMM network, or a network where a DMM network and an EPS network coexist, and at least two implementation manners are included. In the first implementation manner, each base station of the existing EPS network is connected to a corresponding local gateway (Local Gateway, hereinafter referred to as L-GW), and the second implementation manner is to connect multiple base stations of the existing EPS network with A corresponding L-GW is connected. In any of the above implementation manners, when the interface is set between the MME and the L-GW, the communication method may specifically include the following steps:

Step 501: The MME sends a create session request to the L-GW to establish a bearer with the L-GW.

In this embodiment, when the UE is initially attached, the UE may send an attach request to the MME through the base station, where the attach request carries the DMM-enabled and the L-GW address, and the MME sends a create session request to the L-GW according to the attach request. So that a bearer is established between the L-GW and the MME.

Step 502: The MME receives a create session response returned by the L-GW.

Specifically, after the MME establishes a bearer with the L-GW, the MME receives the create session response returned by the L-GW.

In the communication method provided by the embodiment, the MME sends a create session request to the L-GW, so that the L-GW establishes a bearer relationship with the MME, and the MME receives the create session response returned by the L-GW, and the UE can be established. The connection between the L-GWs, and because the UE can use different IP addresses to connect with different L-GWs and corresponding base stations and initiate a session, and then The single point of failure in the communication system is avoided, and the security of the communication is further improved.

On the basis of the foregoing embodiment, after the MME receives the create session response returned by the L-GW, the MME may further include:

Step 503: The MME sends a delete session request to the L-GW, so as to end the load established between the L-GW and the L-GW.

Step 504: The MME receives a delete session response sent by the L-GW.

Further, before the sending, by the MME, the create session request to the L-GW, the MME may further include:

Step 505: The MME receives an attach request sent by the base station corresponding to the L-GW.

The attach request carries a distributed mobility management DMM identifier;

Step 506: The MME performs authentication and location update according to the attach request.

Correspondingly, after the MME can receive the create session response returned by the L-GW, the MME may further include:

The MME sends an initial context setup request to the corresponding base station to enable the corresponding base station to perform RRC reconfiguration.

Further, before the sending, by the MME, the deletion session request to the L-GW, the method further includes:

The MME receives the detach request sent by the UE;

After the MME receives the delete session response sent by the L-GW, the MME may further include:

The MME sends an attach accept message to the UE;

Or,

Before the MME sends the delete session request to the L-GW, the method may further include: sending, by the MME, a detach request to the UE;

Receiving an attach accept message sent by the UE.

The MME receives the PDN connection request sent by the base station corresponding to the L-GW; Correspondingly, after the MME can receive the create session response returned by the L-GW, the MME may further include:

The MME sends a bearer setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

Further, before the sending, by the MME, the deletion session request to the L-GW, the MME may further include:

The MME receives the PDN detachment request sent by the terminal through the base station corresponding to the L-GW. After the MME receives the delete session response sent by the L-GW, the MME may further include:

The MME sends a deactivation bearer request to the corresponding base station, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

6 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 6, in a DMM network or a network in which a DMM network and an EPS network coexist, and there is no setting between an MME and an L-GW in a DMM network. In the scenario of the interface, the communication method may specifically include the following steps:

Step 601: The UE sends an attach request to the base station, where the attach request carries information such as a UE identifier and a packet data network type (PDN Type).

Step 602: The base station forwards an attach request to the MME.

Specifically, when the base station has the capability to establish a bearer with the L-GW through an internal interaction process, the base station preferentially selects the DMM network, and adds a DMM-enabled identifier to the attach request.

For example, in the case where the EPS network and the DMM network coexist, when the MME receives the attach request including the DMM-enabled identifier, the MME can determine whether to connect according to the APN and/or network policy information carried in the attach request sent by the UE. Go to the DMM network, if yes, go to step 603. If not, access the EPS network and perform the attachment process of the existing EPS network. In the case of only the DMM network, the base station accesses the DMM network.

Step 603: Perform authentication on the UE that initiates the attach request.

In this embodiment, the MME, the HSS (Home Subscriber Server, the home subscriber server) and the like authenticate the UE. If the authentication succeeds, the process proceeds to step 604. If the authentication fails, the UE attach request is rejected.

Step 604: The MME sends a location update message to the HSS, to request the UE from the HSS. Sign data information.

In this embodiment, the UE initiates the connection request with the MME for the first time. Therefore, the MME does not have the subscription data information of the UE, and the MME needs to send a location update message to the HSS to request the subscription data information of the UE. The location update message carries information such as MME Identity, IMSI, and ME Identity.

Step 605: The MME sends a location update response message to the HSS, where the location update response message carries the subscription data information and the IMSI information of the UE.

Step 606: The MME sends an Initial Context Setup Request to the base station to establish a bearer between the base station and the L-GW.

Specifically, the base station is a base station that sends an attach request, and the initial context setup request sent to the base station carries at least an attach accept message, and carries an DMM-enabled identifier in the attach accept message, and further, the initial context The establishment request may also carry IMSI, MSISDN, APN, Default EPS Bearer QoS, PDN Type, APN-AMBR, EPS Bearer Identity, and the like.

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

After receiving the initial context setup request sent by the MME, the base station allocates a base station TEID (Tunnel Endpoint Identifier) and a base station address of the user plane carried in the L-GW.

Step 608: The L-GW initiates an IP-CAN (IP-Connectivity Access Network) session establishment process to the PCRF.

In this embodiment, if a dynamic PCC (Policy and Charging Control) is deployed, the B-J L-GW initiates IP-CAN to the PCRF (Policy and Charging Rules Function). The session establishment process and obtaining the PCC policy information of the UE.

Step 609: The L-GW sends a Create Session Response to the base station, where the Create Session Response carries the L-GW TEID and the L-GW address of the user plane of the bearer.

It should be noted that, for each UE, at least one PDN connection may be established between the L-GW and the base station, where the PDN connection includes a default bearer, where the bearer corresponds to one user tunnel, and the user tunnel may use one Endpoint identification of the user plane tunnel, ie base Station tunnel endpoint identifier and L-GW tunnel endpoint identifier.

Step 610: The base station sends RRC connection reconfiguration information to the UE.

Step 611: 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 air interface signaling connection between the UE and the base station.

Step 612: The base station sends an initial context setup response to the MME.

Specifically, the base station sends an initial context setup response to the MME, where the initial context setup response carries bearer information between the base station and the L-GW, where the bearer information carries a PDN Type,

PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, etc. The MME stores the bearer information between the base station and the L-GW, and is used by the base station to reconstruct the UE context in the Service Request process.

Step 613: The UE sends a direct transmission message to the base station, where the direct transmission message carries an attachment completion message. Step 614: The base station forwards an attach complete message to the MME.

After the base station forwards the attach complete message to the MME in this embodiment, the UE may perform uplink data transmission and downlink data transmission with the L-GW.

Step 615: The MME sends a notification request message to the HSS.

Specifically, the notification request information carries an APN and an L-GW identity pair for mobility management of the user equipment, for example, after the user equipment moves, causing mobility management generated when the user equipment accesses the non-3GPP network.

Step 616: The HSS sends a notification response message to the MME.

FIG. 7 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 7, in a DMM network or a network in which a DMM network and an EPS network coexist, and an interface exists between the MME and the L-GW in the DMM network. in the case of.

Step 701: The UE sends an attach request to the base station, where the attach request carries information such as a UE identifier and a packet data network type (PDN Type).

Step 702: The base station forwards an attach request to the MME.

Specifically, when the base station is configured with the corresponding L-GW, but the bearer cannot be established through the process of internal interaction, the base station preferentially selects the DMM network, and adds the DMM-enabled identifier and the L-GW corresponding to the base station in the attach request. address.

For example, in the case where the EPS network and the DMM network coexist, when the MME receives After the attachment request is included, it may be determined whether to access the DMM network according to the APN and/or network policy information carried in the attach request sent by the UE, if yes, proceed to step 703, if not, access to the DMM network. And carry out the attachment process of the existing EPS network. In the case of only the DMM network, the base station accesses the DMM network.

Step 703: Perform authentication on the UE that initiates the attach request.

In this embodiment, the MME, the HSS (Home Subscriber Server, the home subscriber server) and the like authenticate the UE. If the authentication succeeds, the process proceeds to step 704. If the authentication fails, the UE attach request is rejected.

Step 704: The MME sends a location update message to the HSS, to request the HSS subscription data information from the HSS.

In this embodiment, the UE initiates the connection request with the MME for the first time. Therefore, the MME does not have the subscription data information of the UE, and the MME needs to send a location update message to the HSS to request the subscription data information of the UE, where The location update message carries information such as MME Identity, IMSI, and ME Identity.

Step 705: The HSS sends a location update response message to the MME, where the location update response message carries the subscription data information and the IMSI information of the UE.

Step 706: The MME sends a create session request to the L-GW.

In this embodiment, the MME sends a create session request to the corresponding L-GW according to the L-GW address carried in the attach request sent by the base station.

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

In this embodiment, if a 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 708: The L-GW sends a create session response to the MME, where the created session response carries the user plane L-GW TEID and the L-GW address (L-GW address) of the bearer.

Step 709: The MME sends an initial context setup request to the corresponding base station to establish a bearer between the base station and the L-GW.

Specifically, the base station is a base station that sends an attach request, and the create session request sent by the MME to the base station carries at least an attach accept message, and carries an DMM-enabled identifier in the attach accept message, and further, the create session request It can also carry L-GW and Information carried between the MMEs.

Step 710: The base station sends RRC connection reconfiguration information to the UE.

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

Step 712: The base station sends an initial context setup response to the MME.

Specifically, the base station sends an initial context setup response to the MME, where the initial context setup response carries the base station TEID of the user plane and the base station address.

Step 713: The UE sends a direct transmission message to the base station, where the direct transmission message carries an attachment completion message. Step 714: The base station forwards the attach complete message to the MME.

After the base station forwards the attach complete message to the MME in this embodiment, the UE may perform uplink data transmission with the L-GW.

Step 715: The MME sends a modify bearer request to the L-GW, where the modify bearer request carries the base station TEID and the base station address.

Step 716: The L-GW sends a modify bearer response to the MME, configured to respond to the modify bearer request.

After step 716, the UE may perform downlink data transmission with the L-GW.

Step 717: The MME sends a notification request message to the HSS.

Step 718: The HSS sends notification response information to the MME.

FIG. 8 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 8, in a network where a DMM network or a DMM network and an EPS network coexist, there is no setting between the MME and the L-GW in the DMM network. In the scenario of the interface, the UE establishes a connection with the L-GW. If the UE requests to establish a PDN connection with the L-GW, the specific steps may include: Step 801: The UE sends a PDN connection request to the MME.

Specifically, the UE sends a PDN connection request to the MME by using the base station, where the PDN connection request carries information such as the UE identifier and the packet data network type, and the DMM-enabled identifier is added by the base station. Step 802: The MME sends a bearer setup request to the base station.

Specifically, the MME sends a bearer setup request to the base station that forwards the PDN connection request, where the bearer setup request carries at least the PDN connection accept message, and the DMN-enabled identifier is carried in the PDN connection accept message, and further, the bearer The establishment request may also carry information of IMSI, MSISDN, APN, Default EPS Bearer QoS, PDN Type, APN-AMBR, and EPS Bearer Identity.

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

After receiving the bearer setup request sent by the MME, the base station allocates a base station TEID (Tunnel Endpoint Identifier) and a base station address of the user plane carried between the L-GW and the L-GW.

Step 804: The L-GW initiates an IP-CAN session establishment process to the PCRF.

Step 805: The L-GW sends a Create Session Response to the base station, where the Create Session Response carries the L-GW TEID and the L-GW address of the user plane of the bearer.

Step 806: The base station sends RRC connection reconfiguration information to the UE.

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

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

Specifically, the base station sends a bearer setup response to the MME, where the bearer setup response carries the bearer information between the base station and the L-GW, where the bearer information carries the PDN Type, PDN Address, EPS Bearer Identity, EPS Bearer QoS, APN- AMBR and so on. Therefore, the MME stores bearer information between the base station and the L-GW, and is used by the base station to reconstruct the UE context in the Service Request process.

Step 809: The UE sends a direct transmission message to the base station, where the direct transmission message carries an attachment completion message. Step 810: The base station forwards an attach complete message to the MME.

Step 811: The MME sends notification request information to the HSS. Specifically, the notification request information carries the pair of ΑΡΝ and L-GW identifiers, and is used for mobility management of the user equipment, for example, after the user equipment moves, causing mobility management generated when the user equipment accesses the non-3GG network.

Step 812: The HSS sends a notification response message to the UI.

FIG. 9 is a schematic flowchart of a communication method according to still another embodiment of the present invention, as shown in FIG.

In the scenario where the DMM network or the DMM network and the EPS network coexist, in the scenario where the MME and the L-GW in the DMM network have an interface between the UE and the L-GW, the following steps may be included:

Step 901: The UE sends a PDN connection request to the MME.

Specifically, the UE sends a PDN connection request to the MME through the base station connected to the UE, where the PDN connection request carries at least information such as the UE identifier and the packet data network type, and the DMM-enabled identifier and the L-GW address are added by the base station. Information.

Step 902: The MME sends a create session request to the L-GW.

Specifically, the MME sends a create session request to the corresponding L-GW according to the L-GW address carried in the PDN connection request sent by the UE.

Step 903: The L-GW initiates an IP-CAN session establishment process to the PCRF.

Step 904: The L-GW sends a create session response to the MME that sends the session creation request. The L-GW sends a create session response to the MME, where the create session response carries

L-GW TEID and L-GW address of the user plane allocated by the L-GW.

Step 905: The MME sends a bearer setup request to the corresponding base station, to establish a bearer between the base station and the L-GW.

Specifically, the base station is a base station that forwards the PDN connection request in step 901, and the bearer setup request sent by the MME to the base station carries at least a PDN connection accept message, and carries a DMM-enabled identifier in the PDN connection accept message. Further, the bearer setup request may further carry information carried between the L-GW and the MME.

Step 906: The base station sends RRC connection reconfiguration information to the UE.

Step 907: 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 UE. Reconfiguration of the air interface signaling connection with the base station.

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

Specifically, the base station sends a bearer setup response to the MME, where the bearer setup response carries the base station TEID of the user plane and the base station address.

Step 909: The UE sends a direct transmission message to the base station, where the direct transmission message carries an attachment completion message. Step 910: The base station forwards an attach complete message to the MME.

Step 911: The MME sends a modify bearer request to the L-GW, where the modify bearer request carries the base station TEID and the base station address.

Step 912: The L-GW sends a modify bearer response to the MME, where the response is sent to modify the bearer request.

After step 912, the UE may perform downlink data transmission with the L-GW.

Step 913: The MME sends a notification request message to the HSS.

Step 914: The HSS sends notification response information to the MME.

10 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 10, the applicable scenario of this embodiment is that in a DMM network or a network in which a DMM network and an EPS network coexist, an MME in a DMM network After the interface is not set up with the L-GW, after multiple PDN connections have been established between the UE and the L-GW, the following steps may be included:

Step 1001: The UE sends a PDN connection request to the MME.

Specifically, the UE sends a PDN connection request to the MME through the base station, and the PDN de-connection request is used for de-connection of the PDN connection between the UE and the L-GW. The PDN de-connect request includes an LBI (Linked EPS Bearer Identifier), which is used to indicate the default bearer of the connected PDN connection.

The de-connection of the PDN connection may also be initiated by ΜΜΕ, for example, when the UE subscribes to data modification or lack of resources, etc., it decides to release the PDN connection of the UE.

For the de-connection of a certain PDN connection of the UE, the UE may initiate a PDN disconnection request, Or the PDN is triggered by the MME to connect.

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

Specifically, the MME sends a deactivated bearer request to the base station that forwards the PDN detachment request, where the deactivated bearer request includes an LBI, and the deactivated bearer request is used to deactivate the default bearer identifier between the base station and the L-GW. All bearers of the LBI's PDN connection.

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

The base station sends a delete session request to the L-GW according to the information carried in the deactivated bearer request sent by the MME, where the delete session request includes an LBI, and the delete session request is used to delete the default bearer identifier between the base station and the L-GW. All bearers of the LBI's PDN connection.

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

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

Step 1005: The L-GW sends a delete session response to the base station, in response to deleting the session request.

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

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

Step 1008: The base station sends a deactivation bearer response to the MME, to notify the MME that all bearers of the PDN connection with the default 7-digit LBI are deleted between the UE and the L-GW.

Step 1009: The UE sends a direct transmission message to the base station, where the direct transmission message carries a deactivated EPS bearer context accept message.

Step 1010: The base station sends a deactivated EPS bearer context accept message to the MME. FIG. 11 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 11, the applicable scenario of this embodiment is that, in a DMM network or a network in which a DMM network and an EPS network coexist, an MME in a DMM network In the scenario that the interface exists with the L-GW, after multiple PDN connections have been established between the UE and the L-GW, the following steps may be included:

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

Specifically, the UE sends a PDN disconnection request to the MME through the base station connected to the UE, where the PDN disconnection request is used for de-connection of the PDN connection between the UE and the L-GW. among them, The PDN de-connection request includes an LBI (Linked EPS Bearer Identifier), which is used to indicate a default bearer of the connected PDN connection.

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 de-connection request may be initiated by the UE, or the PDN may be triggered by the MME to connect.

Step 1102: The MME sends a delete session request to the L-GW, where the delete session request includes an LBI, and the delete session request is used to delete all bearers of the PDN connection with the default bearer identifier LBI between the MME and the L-GW.

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

Step 1104: The L-GW sends a delete session response to the MME.

Specifically, the MME sends an MME that deletes the session request to the L-GW in step 1102, and the L-GW sends a delete session response to the MME to respond to the delete session request.

Step 1105: The MME sends a deactivation bearer request to the corresponding base station, where the deactivation bearer request includes an LBI, and is used to deactivate all bearers of the PDN connection with the default bearer identifier LBI between the base station and the L-GW.

Specifically, the base station is a base station that forwards the PDN de-connection request in step 1101.

Step 1106: The base station sends RRC connection reconfiguration information to the UE.

Step 1107: 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 1108: The base station sends a deactivation bearer response to the MME.

Step 1109: The UE sends a direct transmission message to the base station, where the direct transmission message carries a deactivated EPS bearer context accept message.

Step 1110: The base station sends a deactivate bearer context accept message to the MME.

FIG. 12 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 12, in the embodiment, the MME and the L-GW in the DMM network are applicable to the DMM network or the network where the DMM network and the EPS network coexist. In the scenario where there is no interface between the DMM network After the attachment has been established, the following steps can be included:

Step 1201: The UE sends a detach request to the MME through the base station, where the detach request is used to request detachment of the UE.

Step 1202: The MME sends a deactivation bearer request to the base station, where the UE and the L-GW have multiple PDN connections, and the MME sends a deactivation bearer request for each PDN connection. Each deactivation bearer request includes an LBI for deactivating all bearers of the PDN connection whose default bearer identifier between the base station and the L-GW is LBI.

Step 1203: The base station sends a delete session request to the corresponding L-GW, so that the corresponding L-GW deletes the established PDN connection; the UE and the L-GW have multiple PDN connections, and the base station connects for each PDN. Send a delete session request. Each delete session request includes an LBI for deleting a PDN connection between the base station and the L-GW with a default bearer identifier of LBI.

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

Step 1205: The L-GW sends a delete session response to the base station.

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

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

Step 1208: Perform RRC connection translation between the base station and the UE.

That is, the MME passes the UE context release command (UE Context Release

The command indicates that the air interface signaling connection is released between the base station and the UE, and then the base station informs the MME that the RRC connection is successfully released through the UE Context Release Complete message.

FIG. 13 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 13, in the embodiment, the MME and the L-GW in the DMM network are applicable to the DMM network or the network where the DMM network and the EPS network coexist. In the scenario where an interface exists, after the connection has been established in the DMM network, the following steps may be included:

Step 1301: The UE sends a detach request to the MME through the base station, where the detach request is used to request detachment of the UE.

Step 1302: The MME sends a delete session request to the L-GW, so that the L-GW delete is established. Establish a PDN connection. There are multiple PDN connections between the UE and the L-GW, and the MME sends a delete session request for each PDN connection. Each deletion session request includes an LBI for deleting a PDN connection between the base station and the L-GW with a default bearer identifier of LBI.

Step 1303: Perform an IP-CAN session termination procedure between the L-GW and the PCRF.

Step 1304: The L-GW sends a delete session response to the MME.

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

Step 1306: Perform RRC connection translation between the base station and the UE.

That is, the MME passes the UE context release command (UE Context Release

FIG. 14 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 14, in the embodiment, the MME and the L-GW in the DMM network are applicable to the DMM network or the network where the DMM network and the EPS network coexist. In the scenario where no interface exists, after the connection has been established in the DMM network, the following steps can be included:

Step 1401: The MME initiates a detach request to the UE by using the base station, where the detach request is used to notify the detachment of the UE.

Step 1402: The MME sends a deactivation request to the base station, how many PDN connections are 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 all bearers of the PDN connection whose default bearer identifier is LBI between the base station and the L-GW.

Step 1403: The base station sends a delete session request to the corresponding L-GW, so that the corresponding L-GW deletes the established PDN connection; the UE and the L-GW have multiple PDN connections, and the base station sends and deletes for each PDN connection. Session request. Each deletion session request includes an LBI for deleting a PDN connection between the base station and the L-GW with a default bearer identifier of LBI.

Step 1404: The IP-CAN session termination process is performed between the L-GW and the PCRF.

In this embodiment, if a dynamic PCC is deployed, the L-GW initiates an IP-CAN session termination procedure to the PCRF. Step 1405: The L-GW sends a delete session response to the base station.

Step 1406: The base station sends a deactivation bearer response to the MME, in response to deactivating the bearer request.

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

Step 1408: Perform RRC connection translation between the base station and the UE.

That is, the MME instructs the base station to release the air interface signaling connection between the UE and the UE through the UE context release command (UE Context Release Command), and then the base station informs the MME that the RRC connection is successfully released through the UE Context Release Complete message.

FIG. 15 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 15, in an embodiment, a MME and an L-GW in a DMM network are applicable to a DMM network or a network in which a DMM network and an EPS network coexist. In the scenario where an interface exists, after the connection has been established in the DMM network, the following steps may be included:

Step 1501: The MME initiates a detach request to the UE by using the base station, where the detach request is used to notify the detachment of the UE.

Step 1502: The MME sends a delete session request to the L-GW, so that the corresponding L-GW deletes the established PDN connection. There are multiple PDN connections between the UE and the L-GW, and the base station sends a delete session request for each PDN connection. Each delete session request includes an LBI for deleting the PDN connection between the base station and the L-GW with a default bearer identifier of LBI.

Step 1503: Perform an IP-CAN session termination procedure between the L-GW and the PCRF.

Step 1504: The L-GW sends a delete session response to the MME.

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

Step 1506: Perform RRC connection translation between the base station and the UE.

That is, the MME instructs the base station to perform the air interface signaling connection between the base station and the UE through the UE context release command (UE Context Release Command), and then the base station informs the MME that the RRC connection is successfully released through the UE Context Release Complete message. .

FIG. 16 is a schematic flowchart of a communication method according to still another embodiment of the present invention. As shown in FIG. 16, the embodiment is applicable to a DMM network or a network in which a DMM network and an EPS network coexist, and an MME and an L-GW in a DMM network. In the scenario where there is an interface, or MME and L-GW In the scenario where no interface exists, after the connection has been established in the DMM network, the following steps can be included:

Step 1601: The HSS sends a Cancel Location message to the MME. Step 1602: Perform a detach process between the UE, the base station, the L-GW, the MME, and the PCRF. Specifically, in a scenario where there is no interface between the MME and the L-GW, the process is as shown in FIG. 14 . In the scenario where an interface exists between the MME and the L-GW, the process is as shown in FIG. 15 .

Step 1603: The MME sends a cancel location response to the HSS.

Step 1604: Perform RRC connection translation between the base station and the UE.

FIG. 17 is a schematic structural diagram of an L-GW according to an embodiment of the present invention. As shown in FIG. 16, the L-GW includes: a receiving module 1701, configured to receive a create session request; and a processing module 1702, configured to create a session according to the Request to establish a bearer; a sending module 1703, configured to send a create session response.

Further, the receiving module 1701 is further configured to: after the sending module sends the create session response, receive a delete session request; the processing module 1702 is further configured to: after the receiving module receives the delete session request, delete The established bearer; the sending module 1703 is further configured to: after the processing module deletes the established bearer, send a delete session response.

Further, the receiving module 1701 is specifically configured to create a session request sent by the base station corresponding to the L-GW, where the create session request is that the base station corresponding to the L-GW receives the initial sent by the MME. The processing module 1702 is specifically configured to establish a bearer for a specific user between the base stations corresponding to the L-GW, and the sending module 1703 is specifically configured to be used after the context establishment request or the bearer setup request is sent. Sending a session establishment response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW and the user equipment UE perform radio resource control RRC connection reconfiguration.

Further, the receiving module 1701 is specifically configured to delete a session request sent by a base station corresponding to the L-GW, where the delete session request is that the base station corresponding to the L-GW receives mobility management. Transmitted after the deactivation of the bearer request sent by the entity MME; The module 1702 is specifically configured to delete a bearer for a specific user between the base stations corresponding to the L-GW, and the sending module 1703 is specifically configured to send, by the base station corresponding to the L-GW, a delete session response. And causing the base station corresponding to the L-GW to send a deactivation bearer response to the MME.

Further, the receiving module 1701 is specifically configured to receive a create session request sent by the MME, where the create session request is after the MME receives an attach request or a PDN connection request sent by the base station corresponding to the L-GW. The sending module 1702 is specifically configured to establish a bearer for a specific user between the base station corresponding to the L-GW and the L-GW; the sending module 1703 is specifically configured to The MME sends a create session response, so that the MME sends an initial context setup request or a bearer setup request to the base station corresponding to the L-GW.

Further, the receiving module 1701 is specifically configured to receive a delete session request sent by the MME, where the delete session request is after the MME receives the PDN disconnection request or the detach request sent by the UE through the corresponding base station. The MME determines to initiate the detach procedure or the HSS sends the cancel location message to the MME, and the processing module 1702 is specifically configured to delete the specific eNB between the L-GW and the base station corresponding to the L-GW. The sending module 1703 is configured to send a delete session response to the MME, so that the MME sends a deactivation bearer request to the base station corresponding to the L-GW or sends the request to the UE. The detach accept message or the MME receives the detach accept message sent by the terminal.

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 the technical effect are similar, and details are not described herein again.

FIG. 18 is a schematic structural diagram of a base station according to an embodiment of the present invention. As shown in FIG. 18, the base station includes: a receiving module 1801, configured to receive an initial context setup request or a bearer setup request sent by an MME, and send a create session request in a sending module. Receiving a create session response sent by the corresponding L-GW; the sending module 1802, configured to send the create session request to an L-GW corresponding to the base station; and the processing module 1803, configured to After receiving the creation session response sent by the corresponding L-GW, the receiving module performs RRC connection reconfiguration.

Further, the receiving module 1801 is further configured to: after the RRC connection reconfiguration is performed by the processing module, receive a deactivation bearer request sent by the MME, where the deactivated bearer request carries The sending module 1802 is further configured to: after the receiving module receives the deactivation bearer request sent by the MME, send a delete session request to the L-GW corresponding to the base station; and in the receiving module After receiving the delete session response sent by the corresponding L-GW, sending a deactivation bearer response to the MME; the receiving module 1801 is further configured to: after the sending module sends the delete session request, receive the corresponding The L-GW sends a delete session response.

Further, the sending module 1802 is further configured to: after the RRC connection reconfiguration is performed by the processing module, send an initial context setup response to the MME, where the bearer setup response includes an evolved packet system bearer quality of service, and The MME sends a bearer setup response.

The base station in 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 the technical effect are similar, and are not described herein again.

FIG. 19 is a schematic structural diagram of an MME according to an embodiment of the present invention. As shown in FIG. 19, the MME includes: a sending module 1901, configured to send an initial context setup request to a base station, so that the base station establishes a corresponding to the base station. a bearer between the L-GWs, and a receiving module 1902, configured to receive an initial context setup response returned by the base station, where the bearer setup response includes an evolved packet system bearer quality of service.

Further, the sending module 1901 is further configured to: after the receiving module receives the initial context setup response returned by the base station, send a bearer setup request to the base station, so that the base station establishes an L corresponding to the base station. The receiving module 1902 is further configured to: after the sending module sends the bearer setup request, receive a bearer setup response returned by the base station.

Further, the sending module 1901 is configured to: after the receiving module receives the initial context setup response returned by the base station, send a deactivation bearer request to the base station, so that the base station ends the corresponding to the base station. The bearer is established between the L-GWs, and the deactivated bearer request carries the LBI identifier. The receiving module 1902 is further configured to: after the sending module sends the deactivated bearer request, receive the returned by the base station. Deactivate the bearer response.

The MME 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 the technical effect are similar, and details are not described herein again.

FIG. 20 is a schematic structural diagram of an MME according to still another embodiment of the present invention, as shown in FIG. 20, The MME includes: a sending module 2001, configured to send a create session request to the L-GW, so as to establish a bearer with the L-GW; and a receiving module 2002, configured to receive a create session response returned by the L-GW.

Further, after receiving the create session response returned by the L-GW, the method further includes: the sending module 2001, further configured to: after the receiving module receives the create session response returned by the L-GW, to the The L-GW sends a delete session request to end the bearer established between the L-GW; and the receiving module 2002 is further configured to: after the sending module sends the delete session request, receive the L-GW to send Delete session response.

Further, the MME further includes: a processing module 2003, where the receiving module 2002 is further configured to: before the sending module sends the create session request, receive an attach request sent by a base station corresponding to the L-GW, where The attaching request carries the DMM identifier; the processing module 2003 is configured to perform the authentication and the location update according to the receiving module, and the sending module 2001 is further configured to receive, by the receiving module, the After the session response is returned by the L-GW, an initial context setup request is sent to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

Further, the receiving module 2002 is further configured to: before the sending module sends the deletion session request, receive a detach request sent by the UE; the sending module 2001 is further configured to receive, by the receiving module, an L-GW. After the sent session response is sent, the attach accept message is sent to the UE; or the processing module 2003 is further configured to send a detach request to the UE before the sending module sends the delete session request to the L-GW. The receiving module 2002 is further configured to: after receiving the delete session response sent by the L-GW, receive an attach accept message sent by the UE.

Further, the receiving module 2002 is further configured to: before the sending module sends a create session request to the L-GW, receive a PDN connection request sent by the base station corresponding to the L-GW; the sending module 2001, further And after the receiving module receives the create session response returned by the L-GW, sending a bearer setup request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

Further, the receiving module 2002 is further configured to: before the sending module sends a delete session request to the L-GW, the receiving terminal sends a PDN disconnection request sent by the base station corresponding to the L-GW; The processing module 2003 is further configured to receive the L-GW at the receiving module After the sent delete session response, the deactivated bearer request is sent to the corresponding base station, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

The communication system of the embodiment of the present invention includes:

The L-GW, the base station provided by any device embodiment of the present invention, and the mobility management entity MME provided by any device embodiment of the present invention.

Further, an interface is set between the L-GW and the MME corresponding to the L-GW. Or, further, an interface is not set between the L-GW and the MME corresponding to the L-GW.

The communication system of this embodiment can be used to perform the technical solution of the embodiment of the communication method provided by the embodiment shown in FIG. 1 of the present invention. The implementation principle and technical effects are similar, and details are not described herein again.

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

The L-GW of the present embodiment can 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. 22 is a schematic structural diagram of a base station according to still another embodiment of the present invention. As shown in FIG. 22, the base station includes: a transmitter 2201, a receiver 2202, a memory 2203, and the transmitter 2201, the receiver 2202, and The processor 2204 is connected to the memory 2203, wherein the memory 2203 stores a set of program codes, and the processor 2204 is configured to invoke the program code stored in the memory 2203 to perform the implementation shown in FIG. 3 of the present invention. The communication method provided in the example.

The base station of this embodiment may be used to perform the technical solution of the embodiment of the communication method provided by the embodiment shown in FIG. 3, and the implementation principle and the technical effect are similar, and details are not described herein again.

FIG. 23 is a schematic structural diagram of an MME according to still another embodiment of the present invention. As shown in FIG. 23, the MME includes a transmitter 2301, a receiver 2302, a memory 2303, and the foregoing, respectively. The machine 2301, the receiver 2302 and the processor 2304 connected to the memory 2303, wherein the memory 2303 stores a set of program codes, and the processor 2304 is configured to invoke the program code stored in the memory 2303. The communication method provided in the embodiment shown in FIG. 4 or FIG. 5 of the present invention is executed.

It should be noted that the MME shown in FIG. 23 may be used to implement the method provided by the embodiment shown in FIG. 4 or FIG. 5 of the present invention, and the description about the MME is the same as the foregoing method embodiment, and details are not described herein again.

In another embodiment of the present invention, the communication system may include a local gateway L-GW as shown in FIG. 21, a base station as shown in FIG. 22, and a mobility management entity MME as shown in FIG.

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

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; 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 local gateway L-GW receives the create session request;

The L-GW establishes a bearer according to the create session request;

The L-GW sends a create session response.

2. The method according to claim 1, characterized in that, after sending the create bearer response, it further includes:

The L-GW receives the delete session request;

The L-GW deletes the established bearer according to the session deletion request;

The L-GW sends a delete session response.

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

The L-GW receives a session creation request sent by the base station corresponding to the L-GW. The session creation request is when the base station corresponding to the L-GW receives an initial context establishment request sent by the MME or 7 Sent after loading the establishment request;

The L-GW establishes a bearer according to the create session request, including:

The L-GW establishes a bearer for a specific user between the L-GW and the base station corresponding to the L-GW;

The sending of the create session response includes:

Send a create session response to the base station corresponding to the L-GW, so that the

Radio resource control RRC connection reconfiguration is performed between the base station corresponding to the L-GW and the user equipment UE.

4. The method according to claim 2, characterized in that the L-GW receives a delete session request, including:

The L-GW receives a deletion session request sent by the base station corresponding to the L-GW, and the deletion session request is received by the base station corresponding to the L-GW and sent by the mobility management entity MME. Sent after deactivating the bearer request;

The L-GW deletes the bearer according to the delete session request, including:

The L-GW deletes the bearer for a specific user between the L-GW and the base station corresponding to the L-GW; The sending of a bearer deletion response includes:

Send a delete session response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW sends a deactivation bearer response to the MME.

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

The L-GW receives a create session request sent by the MME, and the create session request is sent by the MME after receiving an attach request or a PDN connection request sent by the base station corresponding to the L-GW;

The sending of the create session response includes:

Send a create session response to the MME, so that the MME sends an initial context establishment request or a carrier establishment request to the base station corresponding to the L-GW.

6. The method according to claim 2, characterized in that the L-GW receives a delete session request, including:

The L-GW receives a deletion session request sent by the MME. The deletion session request is when the MME receives a PDN deconnection request or a detachment request forwarded by the UE through the corresponding base station or the MME decides to initiate a detachment process. Or sent after the HSS sends a location cancellation message to the MME;

The L-GW deletes the bearer according to the delete session request, including:

The L-GW deletes the bearer for a specific user between the L-GW and the base station corresponding to the L-GW;

The sending of a delete session response includes:

Send a delete session response to the MME, so that the MME sends a deactivation bearer request to the base station corresponding to the L-GW or sends a detachment acceptance message to the UE or the MME receives the message sent by the terminal. The detach accept message.

7. A communication method, characterized by including:

The base station receives the initial context establishment request or bearer establishment request sent by the MME; sends a create session request to the L-GW corresponding to the base station; Receive the create session response sent by the corresponding L-GW;

Perform RRC connection reconfiguration.

8. The method according to claim 7, characterized in that, after performing the RRC connection reconfiguration, it further includes:

Receive a deactivation bearer request sent by the MME, where the deactivation bearer request carries the LBI identifier;

Send a delete session request to the L-GW corresponding to the base station;

Receive the delete session response sent by the corresponding L-GW;

Send a deactivation bearer response to the MME.

9. The method according to claim 7 or 8, characterized in that, if the base station receives the initial context establishment request sent by the MME, after performing the RRC connection reconfiguration, it further includes: sending an initial context establishment response to the MME. , the 7-carrier establishment response includes the evolved packet system bearer service quality;

If the base station receives the bearer establishment request sent by the MME, after performing the RRC connection reconfiguration, it also includes:

Send a 7-bearer setup response to the MME.

10. A communication method, characterized by including:

The MME sends an initial context establishment request to the base station, so that the base station establishes a bearer between the L-GW corresponding to the base station;

The MME receives the initial context establishment response returned by the base station, and the bearer establishment response includes the evolved packet system bearer service quality.

11. The method according to claim 10, characterized in that, after receiving the initial context establishment response returned by the base station, further comprising:

Send a bearer establishment request to the base station, so that the base station establishes a bearer between the L-GW corresponding to the base station;

Receive the bearer establishment response returned by the base station.

12. The method according to claim 10 or 11, characterized in that, after receiving the initial context establishment response returned by the base station, it further includes:

Send a deactivation bearer request to the base station, so that the base station ends the established bearer with the L-GW corresponding to the base station, where the deactivation bearer request carries the LBI identifier; Receive a deactivation bearer response returned by the base station.

13. A communication method, characterized by including:

The MME sends a create session request to the L-GW to establish a bearer with the L-GW; and receives a create session response returned by the L-GW.

14. The method according to claim 13, characterized in that, after receiving the create session response returned by the L-GW, further comprising:

Send a delete session request to the L-GW to end the bearer established with the L-GW;

Receive the delete session response sent by the L-GW.

15. The method according to claim 13 or 14, characterized in that the MME

Before L-GW sends the create session request, it also includes:

The MME receives an attachment request sent by the base station corresponding to the L-GW, where the attachment request carries a distributed mobility management DMM identifier;

Perform authentication and location update according to the attachment request;

Send an initial context establishment request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

16. The method according to claim 15, characterized in that, before sending the delete session request to the L-GW, further comprising: receiving a detachment request sent by the UE; and receiving the delete session sent by the L-GW. After the response, the method further includes: sending an attachment acceptance message to the UE; or, before sending the delete session request to the L-GW, the method further includes: sending a detachment request to the UE; and receiving the deletion message sent by the L-GW. After the session response, the method further includes: receiving an attachment accept message sent by the UE.

17. The method according to claim 13 or 14, characterized in that, before the MME sends a session creation request to the L-GW, it further includes:

The MME receives the PDN connection request sent by the base station corresponding to the L-GW; after receiving the create session response returned by the L-GW, it also includes:

Send a bearer establishment request to the corresponding base station, so that the corresponding base station performs RRC reconfiguration.

18. The method according to claim 17, characterized in that: the said L-GW Before sending a delete session request, also include:

Receiving the PDN deconnection request sent by the terminal through the base station corresponding to the L-GW; After receiving the delete session response sent by the L-GW, it also includes:

Send a deactivation bearer request to the corresponding base station, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

19. A local gateway L-GW, characterized by including:

Receiving module, used to receive session creation requests;

A processing module, configured to establish a bearer according to the create session request;

Send module, used to send create session response.

20. The L-GW according to claim 19, wherein the receiving module is further configured to receive a delete session request after the sending module sends the create session response;

The processing module is also configured to delete the established bearer after the receiving module receives the delete session request;

The sending module is also configured to send a delete session response after the processing module deletes the established bearer.

21. The L-GW according to claim 19, characterized in that the receiving module is specifically used to create a session request sent by the base station corresponding to the L-GW, and the session creating request is the session creation request related to the L-GW. The base station corresponding to the L-GW is sent after receiving the initial context establishment request or bearer establishment request sent by the MME;

The processing module is specifically used to establish a bearer for a specific user between base stations corresponding to the L-GW;

The sending module is specifically configured to send a create session response to the base station corresponding to the L-GW, so that a radio resource control RRC connection is performed between the base station corresponding to the L-GW and the user equipment UE. Reconfigure.

22. The L-GW according to claim 20, characterized in that, the receiving module is specifically used to delete a session request sent by the base station corresponding to the L-GW, and the session deleting request is the deletion session request related to the L-GW. The base station corresponding to the L-GW is sent after receiving the deactivation bearer request sent by the mobility management entity MME;

The processing module is specifically configured to delete a bearer for a specific user between the base stations corresponding to the L-GW; The sending module is specifically configured to send a delete session response to the base station corresponding to the L-GW, so that the base station corresponding to the L-GW sends a deactivation bearer response to the MME.

23. The L-GW according to claim 19, characterized in that,

The receiving module is specifically configured to receive a create session request sent by the MME. The create session request is sent by the MME after receiving an attach request or a PDN connection request sent by the base station corresponding to the L-GW;

The processing module is specifically used to establish a bearer for a specific user between the L-GW and the base station corresponding to the L-GW;

The sending module is specifically configured to send a create session response to the MME, so that the MME sends an initial context establishment request or a carrier establishment request to the base station corresponding to the L-GW.

24. The L-GW according to claim 20, characterized in that,

The receiving module is specifically configured to receive a deletion session request sent by the MME. The deletion session request is initiated by the MME after receiving the PDN deconnection request or detachment request forwarded by the UE through the corresponding base station or the MME decides to initiate the deletion session request. Sent during the detachment process or after the HSS sends a cancel location message to the MME;

The processing module is specifically used to delete the bearer for a specific user between the L-GW and the base station corresponding to the L-GW;

The sending module is specifically configured to send a delete session response to the MME, so that the MME sends a deactivation load request to the base station corresponding to the L-GW or sends a detachment acceptance message to the UE, or The MME receives the detachment accept message sent by the terminal.

25. A base station, characterized by including:

The receiving module is configured to receive the initial context establishment request or the bearer establishment request sent by the MIME, and after the sending module sends the create session request, receive the create session response sent by the corresponding L-GW;

The sending module is configured to send the create session request to the L-GW corresponding to the base station;

The processing module is configured to perform RRC connection reconfiguration after the receiving module receives the create session response sent by the corresponding L-GW.

26. The base station according to claim 25, characterized in that, The receiving module is also configured to receive a deactivation bearer request sent by the MME after the processing module performs RRC connection reconfiguration, where the deactivation bearer request carries an LBI identifier; the sending module is also configured to After the receiving module receives the deactivation bearer request sent by the MME, it sends a delete session request to the L-GW corresponding to the base station; and after the receiving module receives the delete session response sent by the corresponding L-GW, it sends a delete session request to the L-GW corresponding to the base station. The MME sends a deactivation bearer response;

The receiving module is also configured to receive a delete session response sent by the corresponding L-GW after the sending module sends the delete session request.

27. The base station according to claim 25 or 26, characterized in that,

The sending module is also configured to send an initial context establishment response to the MME after the RRC connection reconfiguration is performed by the processing module, where the 7-carrier establishment response includes the evolved packet system bearer service quality, and to the MME Send bearer establishment response.

28. A mobility management entity MME, characterized by including:

A sending module, configured to send an initial context establishment request to the base station, so that the base station establishes a bearer between the L-GW corresponding to the base station;

A receiving module, configured to receive an initial context establishment response returned by the base station, where the bearer establishment response includes the evolved packet system bearer service quality.

29. The MME according to claim 28, characterized in that,

The sending module is also configured to send a bearer establishment request to the base station after the receiving module receives the initial context establishment response returned by the base station, so that the base station establishes an L-GW corresponding to the base station. carrying space;

The receiving module is further configured to receive a bearer establishment response returned by the base station after the sending module sends the bearer establishment request.

30. The MME according to claim 28 or 29, characterized in that,

The sending module is configured to send a deactivation bearer request to the base station after the receiving module receives the initial context establishment response returned by the base station, so that the base station ends the communication between the L-GW corresponding to the base station. The bearer has been established between, and the deactivation bearer request carries the LBI identifier;

The receiving module is further configured to receive a deactivation bearer response returned by the base station after the sending module sends the deactivation bearer request.

31. A mobility management entity MME, characterized by including:

A sending module, configured to send a create session request to the L-GW to establish a bearer with the L-GW;

A receiving module, configured to receive a create session response returned by the L-GW.

32. The MME according to claim 31, characterized in that, after receiving the create session response returned by the L-GW, it further includes:

The sending module is also configured to send a delete session request to the L-GW after the receiving module receives the create session response returned by the L-GW, so as to end the session established with the L-GW. load;

The receiving module is further configured to receive a delete session response sent by the L-GW after the sending module sends the delete session request.

33. The MME according to claim 31 or 32, further comprising: a processing module,

The receiving module is further configured to receive an attachment request sent by the base station corresponding to the L-GW before the sending module sends the session creation request, where the attachment request carries a distributed mobility management DMM identifier;

The processing module is configured to receive the attachment request according to the receiving module, and perform authentication and location update;

The sending module is also configured to send an initial context establishment request to the corresponding base station after the receiving module receives the create session response returned by the L-GW, so that the corresponding base station performs RRC reconfiguration.

34. The MME according to claim 33, characterized in that,

The receiving module is also configured to receive a detachment request sent by the UE before the sending module sends the delete session request;

The sending module is also configured to send an attachment acceptance message to the UE after the receiving module receives the delete session response sent by the L-GW;

or,

The processing module is also configured to send a detachment request to the UE before the sending module sends a delete session request to the L-GW;

The receiving module is also configured to, after receiving the delete session response sent by the L-GW, receive The attach accept message sent by the UE.

35. The MME according to claim 31 or 32, characterized in that,

The receiving module is also configured to receive a PDN connection request sent by the base station corresponding to the L-GW before the sending module sends a session creation request to the L-GW;

The sending module is also configured to send a bearer establishment request to the corresponding base station after the receiving module receives the create session response returned by the L-GW, so that the corresponding base station performs RRC reconfiguration.

36. The MME according to claim 35, characterized in that,

The receiving module is also configured to receive a PDN deconnection request sent by the terminal through the base station corresponding to the L-GW before the sending module sends a delete session request to the L-GW; the processing module is also configured to After the receiving module receives the delete session response sent by the L-GW, it is used to send a deactivation bearer request to the corresponding base station, so that the corresponding base station performs RRC connection reconfiguration on the terminal.

37. A communication system, characterized in that it includes: the local gateway L-GW according to any one of claims 19-24, the base station according to any one of claims 25-27, and the base station according to any one of claims 25-27. The mobility management entity MME described in any one of 28-36.

38. The system according to claim 37, wherein an interface is provided between the L-GW and the MME corresponding to the L-GW.

39. The system according to claim 37, characterized in that there is no interface provided between the L-GW and the MME corresponding to the L-GW.

40. 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-6.

41. A base station, 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 a set of programs is stored in the memory code, and the processor is configured to call the program code stored in the memory to execute the method according to any one of claims 7-9.

42. A mobility management entity MME, characterized in that it includes: a transmitter, a receiver, a memory, and a process connected to the transmitter, the receiver, and the memory respectively. The processor, wherein a set of program codes is stored in the memory, and the processor is configured to call the program codes stored in the memory to execute the method according to any one of claims 10-18.

43. A communication system, characterized in that it includes: the local gateway L-GW as claimed in claim 40, the base station as claimed in claim 41, and the mobility management entity MME as claimed in claim 42.