WO2017121206A1

WO2017121206A1 - Bearer establishment method and system, mme and sgw

Info

Publication number: WO2017121206A1
Application number: PCT/CN2016/108442
Authority: WO
Inventors: 陶望胜
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-01-15
Filing date: 2016-12-02
Publication date: 2017-07-20
Also published as: CN106982472B; CN106982472A

Abstract

A bearer establishment method and system, an MME and an SGW. The method comprises: an MME receiving a session establishment response message returned by a destination SGW, wherein the session establishment response message carries a message indicating a PDN connection and/or a bearer failing to be established by the destination SGW; the MME notifying a source PGW by means of a source SGW to release the PDN connection and/or the bearer failing to be established by the destination SGW; and the MME sending a bearer modification request to the destination SGW.

Description

Bearer establishment method and system, and MME and SGW

Technical field

The present disclosure relates to the field of mobile communications, for example, to a bearer establishment method and system, and a mobility management entity MME and a serving gateway SGW.

Background technique

The Serving Gate Way (SGW) changes the intra-office handover procedure. The new SGW receives the Create Session Request of the Mobility Management Entity (MME) and creates a Public Data Network (PDN). Connection, but due to resources or other factors, there is a failure of the user part of the PDN connection to be created, or some of the PDN connection fails to be created. The MME is the 3rd Generation Partnership Project (3GPP) protocol LTE connection. Enter the key control node of the network. In the relevant protocol, as in the Technical Specification TS 23.401 or the interface protocol TS 29.274, it is not described how the serving gateway notifies the PDN GateWay (PGW) to release the corresponding failure when the user part PDN connection creation fails. The PDN connection or bearer ensures that the user bearer is consistent with the other PWs in the PGW.

In the process of changing the intra-office handover in the SGW, how to ensure that the PGW is consistent with the user bearer of the destination SGW (or the new SGW), an effective solution has not been proposed.

Summary of the invention

The present disclosure provides a bearer establishment method and system, an MME, and an SGW, which are used to solve the technical problem that the related technologies cannot guarantee that the PGW and the destination SGW are consistent in the SGW.

In one aspect, an embodiment of the present disclosure provides a bearer establishment method, including:

The MME receives the create session response message returned by the destination SGW, where the create session response message carries an indication message of the PDN connection and/or bearer that the destination SGW fails to create; the MME notifies the source PGW to release the source through the source SGW. The destination SGW creates a failed PDN connection and/or bearer; the MME sends a modify bearer request to the destination SGW.

Optionally, before the MME receives the create session response message returned by the destination SGW, the method further includes: the MME sending a create session request to the destination SGW.

Optionally, the MME sends N creation session requests to the destination SGW, where the MME is connected. Receiving the M response messages returned by the destination SGW, where the M response messages are set to indicate that the M PDN connection fails to be created, the MME notifies the source PGW to release the destination SGW by the source SGW. The PDN connection includes: the MME notifying the source PGW to release the M PDN connections indicated by the M pieces of response messages by using the source SGW; and sending, by the MME, the modify bearer request to the destination SGW, including: The MME sends an NM modified bearer request to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

Optionally, the indication message of the failed bearer is used to indicate that the failed bearer is created, and the PDN where the failed bearer is created.

Optionally, the MME sends N creation session requests to the destination SGW, and the MME receives N response messages returned by the destination SGW, where the M response messages have M response messages. In the case that the part of the PDN connection corresponding to the PDN connection fails to be created, the MME notifies the source PGW to release the bearer that the destination SGW fails to create, including: the MME notifies the source through the source SGW. The source PGW releases the bearer that fails to be created under the M PDN connections corresponding to the M message response message; the MME sends a modify bearer request to the destination SGW, where the MME sends N modifications to the destination SGW. A bearer request, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

Optionally, the MME, by using the source SGW, notifies the source PGW to release the PDN connection and/or the bearer that the destination SGW fails to create, including: the MME sends a delete return request to the SGW; and the SGW sends the source PGW to the source And sending a delete call request, where the delete call request is used to instruct the source PGW to release the PDN connection and/or bearer that the destination SGW fails to create.

On the other hand, an embodiment of the present disclosure further provides a bearer establishment method, including:

The destination SGW receives a create session request sent by the MME; the destination SGW creates a PDN connection and/or a bearer in response to the create session request; the destination SGW returns a create session response message to the MME, where the create session response The message carries the indication message that the destination SGW fails to create a PDN connection and/or bearer.

Optionally, after the destination SGW returns a create session response message to the MME, the method further includes: the destination SGW receiving a modify bearer request sent by the MME, where the modify bearer request is The MME is sent after the source SGW notifies the source PDN gateway PGW to release the PDN connection and/or bearer that the destination SGW fails to create.

In another aspect, an embodiment of the present disclosure further provides an MME, including:

The receiving module is configured to receive the create session response message returned by the destination SGW, where the create session response message carries the indication of the PDN connection and/or bearer that the destination SGW fails to create. The notification module is configured to notify the source PGW to release the PDN connection and/or bearer that the destination SGW fails to be created by the source SGW. The first sending module is configured to send a modify bearer request to the destination SGW.

Optionally, the foregoing apparatus further includes: a second sending module, configured to send a create session request to the destination SGW before receiving the create session response message returned by the destination SGW.

Optionally, the notification module is configured to send, by the MME, N creation session requests to the destination SGW, where the MME receives M response messages returned by the destination SGW, and the M response messages are set. In order to indicate that the M PDN connection creation fails, the source SGW is notified by the source SGW to release the M PDN connections indicated by the M response messages; the first sending module is configured to The destination SGW sends an NM strip modification bearer request, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

Optionally, the notification module is configured to send, by the MME, N creation session requests to the destination SGW, where the MME receives N response messages returned by the destination SGW, where the N response messages are If the M-type response message is set to indicate that the part of the PDN connection corresponding to the PDN connection fails to be created, the source SGW is notified by the source SGW to release the M PDN connections corresponding to the M response messages. The first sending module is configured to send N modified bearer requests to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

In another aspect, an embodiment of the present disclosure further provides an SGW, including:

a first receiving module, configured to receive a create session request sent by the MME; a creating module, configured to create a PDN connection and/or a bearer in response to the create session request; and a returning module, configured to return a create session response message to the MME, The creation session response message carries an indication message of the PDN connection and/or bearer that the SGW fails to create.

Optionally, the SGW further includes: a second receiving module, configured to: after the SGW returns a create session response message to the MME, receive a modify bearer request sent by the MME, where the modify bearer request is The MME is sent after the source SGW notifies the source PDN gateway PGW to release the PDN connection and/or bearer that the SGW fails to create.

In another aspect, an embodiment of the present disclosure further provides a bearer setup system, including: any one of the foregoing MMEs, any one of the foregoing SGWs, and a source SGW and a PGW.

In still another aspect, an embodiment of the present disclosure further provides a non-transitory computer readable storage medium storing computer executable instructions for performing any of the foregoing bearer establishment methods.

In still another aspect, an embodiment of the present disclosure further provides an electronic device including one or more processors, a memory, and one or more programs, the one or more programs being stored in a memory, When executed by one or more processors, any of the above described bearer establishment methods are performed.

In still another aspect, an embodiment of the present disclosure further provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when When the program instructions are executed by the computer, the computer is caused to perform any of the above-described bearer establishment methods.

After the destination SGW responds to the request to create a session request, the destination SGW notifies the MME of the PDN connection that failed to be created or the host that failed to be created, and the MME notifies the PGW to release the PND connection or bearer that fails to be created by the destination SGW. The problem that the PGW can be consistent with the user load of the destination SGW cannot be ensured in the SGW change intra-office handover process in the related art, and the PGW can be consistent with the user bearer of the destination SGW.

DRAWINGS

1 is a flowchart of a method for establishing a bearer in an embodiment of the present disclosure;

2 is a flow chart of another method of a bearer establishment method in an embodiment of the present disclosure;

3 is a structural block diagram of an MME in an embodiment of the present disclosure;

4 is a structural block diagram of an SGW in an embodiment of the present disclosure;

5 is a structural block diagram of a bearer establishment system in an embodiment of the present disclosure;

6 is a flowchart of a method for ensuring that a PGW is consistent with a user bearer in a destination SGW network element when a destination PGW fails to be created in the embodiment of the present disclosure;

7 is a flowchart of a method for ensuring that a part of a bearer under one or more PDN connections fails to be created in the destination SGW, and that the PGW is consistent with the user bearer in the destination SGW network element in the embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of hardware of a mobility management entity MME according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of hardware construction of a serving gateway SGW according to an embodiment of the present disclosure.

detailed description

In order to solve the problem that the PGW can not guarantee the user bearer of the new SGW in the SGW change intra-office handover process, the embodiment of the present disclosure provides a bearer establishment method and apparatus, and the following implementations are implemented in conjunction with the accompanying drawings and embodiments. The example will be described in detail. It is understood that the specific embodiments described herein are merely illustrative of the embodiments of the present disclosure Further, the features of the following embodiments and embodiments may be combined with each other without conflict.

The embodiment of the present disclosure provides a bearer establishing method, and the process of the method is as shown in FIG. 1 , including S102, S104 and S106.

In S102, the MME receives the create session response message returned by the destination SGW, where the create session response message carries an indication message of the PDN connection and/or bearer that the destination SGW fails to create;

In S104, the MME, by using the source SGW, notifies the source PGW to release the PDN connection and/or bearer that the destination SGW fails to create;

In S106, the MME sends a modify bearer request to the destination SGW.

In the embodiment of the present disclosure, after the destination SGW receives the modify bearer request, the destination SGW notifies the MME of the PDN connection that failed to be created or the bearer that failed to be created, and the MME notifies the PGW that the destination SGW fails to be created. The PND connection or bearer can solve the problem that the PGW can be consistent with the user of the destination SGW in the SGW change intra-office handover process, so that the PGW is consistent with the user bearer of the destination SGW.

For the destination SGW, the following operations can be implemented, as shown in FIG. 2, including S202, S204, and S206.

In S202, the destination SGW receives a create session request sent by the MME.

In S204, the destination SGW creates a PDN connection and/or bearer in response to the create session request;

In S206, the destination SGW returns a create session response message to the MME, where the create session response message carries an indication message of the PDN connection and/or bearer that the destination SGW fails to create.

Correspondingly, after the destination SGW returns a create session response message to the MME, the MME may notify the source PGW to release the PDN connection and/or bearer that the destination SGW fails to be created by the source SGW, and the MME sends a modify bearer request to the destination SGW. The destination SGW receives the modify bearer request sent by the MME, so that the PGW can be consistent with the user bearer of the destination SGW.

Assuming that the user has N PDN connections, the MME will send N create session requests to the destination SGW.

The following describes the failure of the PDN connection creation and the failure of the bearer creation:

1) The PDN connection creation fails, which can include:

S1: The MME sends N creation session requests to the destination SGW.

S2: The MME receives the M response messages returned by the destination SGW, where the M response messages may be set to indicate that the M PDN connection creation fails.

S3: the MME notifies the source PGW to release the M PDN connections indicated by the M response messages by using the source SGW.

S4: The MME sends an N-M modified bearer request to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

2) The bearer creation fails, which can include:

S1: The MME sends N creation session requests to the destination SGW.

S2: The MME receives the N response messages returned by the destination SGW, where the M response messages of the N response messages are used to indicate that the part of the PDN connection corresponding to the response message fails to be created, that is, the M response message is used. Indicates the bearer that failed to be created, and the PDN where the failed bearer is created.

S3: The MME sends the source SGW to notify the source PGW to release the bearer that fails to be created under the M PDN connections corresponding to the M response messages.

S4: The MME sends N modified bearer requests to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

The MME may notify the source PGW to release the failed PDN connection and/or bearer by deleting the session request. The MME may send a delete call request to the SGW. The SGW sends a delete call request to the source PGW, where the callback request is deleted. A failed PDN connection and/or bearer is created for instructing the source PGW to release the destination SGW.

An MME, an SGW, and a bearer setup system are also provided in this embodiment, and the apparatus can implement the foregoing embodiments and optional implementation manners. As used below, the term "unit" or "module" may implement a combination of software and/or hardware of a predetermined function. Although the devices described in the following embodiments may be implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated. FIG. 3 is a block diagram of an optional structure of an MME according to an embodiment of the present disclosure. As shown in FIG. 3, the method may include: a receiving module 301, a notification module 302, and a first sending module 303.

The receiving module 301 is configured to receive the create session response message returned by the destination SGW, where the create session response message carries an indication message of the PDN connection and/or bearer that the destination SGW fails to create;

The notification module 302 is configured to notify the source PGW to release the PDN connection and/or bearer that the destination SGW fails to be created by the source SGW.

The first sending module 303 is configured to send a modify bearer request to the destination SGW.

In an embodiment, the foregoing apparatus may further include: a second sending module, configured to send a create session request to the destination SGW before receiving the create session response message returned by the destination SGW.

In an embodiment, the notification module 302 is configured to send, by the MME, N creation session requests to the destination SGW, and the MME receives M response messages returned by the destination SGW, where the M response messages are used. Notifying that the M PDN connection fails to be created by the source SGW The source PGW releases the M PDN connections indicated by the M response messages. The first sending module 303 may be configured to send an NM modified bearer request to the destination SGW, where N is a positive integer and M is positive. Integer, N is greater than or equal to M.

In an embodiment, the notification module 302 may be configured to send, by the MME, N creation session requests to the destination SGW, where the MME receives N response messages returned by the destination SGW, and the N responses If the M message response message is used to indicate that the part of the PDN connection corresponding to the PDN connection fails to be created, the source SGW is notified by the source SGW to release the M messages corresponding to the M response messages. The PDN connection creates a bearer that fails. The first sending module 303 can be configured to send N modify bearer requests to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.

FIG. 4 is a block diagram of an optional structure of a PGW according to an embodiment of the present disclosure, which may include:

The first receiving module 401 is configured to receive a create session request sent by the MME.

a creating module 402, configured to create a PDN connection and/or bearer in response to the create session request;

The returning module 403 is configured to return a create session response message to the MME, where the create session response message carries an indication message of the PDN connection and/or bearer that the SGW fails to create;

The second receiving module 404 is configured to: after the SGW returns a create session response message to the MME, receive a modify bearer request sent by the MME, where the modify bearer request is that the MME notifies the source PDN through the source SGW. The gateway PGW releases the PDN connection that was created after the SGW failed to be created and/or sent.

In this embodiment, a bearer establishment system is further provided. As shown in FIG. 5, the system may include an MME as shown in FIG. 3 and an SGW as shown in FIG. 4, and a source SGW and a PGW. The establishment of the bearer can be achieved.

Optional implementation

Considering that in the related art protocol, as in the technical specification TS 23.401 or the interface protocol TS 29.274, the SGW changes the intra-office handover procedure, and the PGW user bearer information cannot be consistent with other network elements: the destination SGW After a PDN connection is created on the MME's Create Session Request, the PDN connection fails to be created in the user part or the PB connection fails to be created.

In the process of the SGW changing the intra-office handover, the PGW connection or the PDN connection fails to notify the PGW to fail to notify the PDN connection or the bearer resource. . In this embodiment, for the 3GPP protocol In the SGW change intra-office handover procedure, the PGW is notified by the source SGW by sending a Delete Session Request or a Delete Bearer Command before the MME sends a Modify Bearer Request to the new SGW. The destination SGW is configured to create a PDN connection or bearer that fails. This ensures that the PGW is consistent with the user bearer information of other NEs.

There are two situations:

Case 1, PDN connection creation failed

The user has multiple PDN connections. When the SGW changes the intra-office SGW handover procedure, the MME receives all the Create Session Responses of the new SGW reply. The reason value of one or more of the messages is not "requested." "("Request Accepted"). Before sending the modify bearer request (Modify Bearer Request) to the destination SGW, the MME sends a Delete Session Request message to the source SGW for each failed PDN connection, carries an indication flag (Indication Flags) field, and indicates the flag. The operation indication (Operation Indication) in the (Indication Flags) field is 1.

According to the method of the embodiment, after the SGW receives the Delete Session Request, the operation indication (Operation Indication) is valid, and the Delete Session Request message is sent to the PGW to release the corresponding PDN connection. .

Case 2, bearer creation failed

The user has one or more PDN connections. When the SGW changes the intra-office SGW handover procedure, the MME receives the created bearer response (Create Session Response) of the destination SGW, and the created bearer context of one or more messages (Bearer) In the Contexts Created field, it indicates that the next one or more bearers of the PDN are failed to be created.

Before sending the modify bearer request (Modify Bearer Request) to the destination SGW, the MME sends a Delete Bearer Command (Delete Bearer Command) message to the source SGW for the PDN connection with the partial bearer failure, and carries the bearer that the PDN fails to create in the new SGW. After receiving the Delete Bearer Command message, the source SGW forwards the message to the PGW to notify it to release the bearer corresponding to the failure.

An example is as follows:

Example 1

As shown in FIG. 6, S601-S605 may be included.

In S601, the user has multiple PDN connections. For each PDN connection, the MME sends a Create Session Request to the destination SGW (ie, a new SGW) to notify the destination SGW. Create the PDN connection;

In S602, the destination SGW fails to create one or a part of the PDN connection due to resources or other factors. For the PDN connection that fails to be created, the destination SGW replies with a Create Session Response to the MME, and the Carry is not a "request to accept" ( "Request Accepted").

In S603, the MME continues the handover process, but sends a Delete Session Request (Delete Session Request) to the source SGW, and carries the indication flag (Indication Flags) and the indication flag (Indication) before sending the Modify Bearer Request to the destination SGW. The Operation Indication of the Flags is 1, and the MME waits or does not wait for the Delete Session Response (Delete Session Response);

In S604, the source SGW receives the Delete Session Request and checks the operation indication (Operation Indication), and sends a Delete Session Request to the PGW to notify it to release the corresponding PDN connection.

In S605: the MME sends a Modify Bearer Request message to the destination SGW to continue the handover process.

Example 2

As shown in FIG. 7, S701-S705 may be included.

In S701, the user has one or more PDN connections. For each PDN connection, the MME sends a Create Session Request to the destination SGW to notify the destination SGW to create the PDN connection.

In S702, the destination SGW fails to create a partial bearer under one or more PDN connections due to resources or other factors. When the destination SGW creates a session response (Create Session Response) for each PDN connection reply, the failed bearer is also carried. The Bearer Context Created has been created, but the corresponding reason value is not "Request Accepted".

In S703, the MME continues the handover process, but sends a Delete Bearer Command to the source SGW before sending the Modify Bearer Request to the destination SGW.

In S704, the source SGW forwards a Delete Bearer Command to the PGW to notify it to release the bearer that fails under the PDN connection.

In S705, the MME continues the handover procedure and sends a Modify Bearer Request to the destination SGW.

In the above manner, in the SGW change intra-office handover procedure, it can be guaranteed that when the SGW occurs due to the purpose When the bearer fails to be created or the PDN is lost, the PGW network element can release the corresponding failed bearer, so that the user bearer information on the PGW and the SGW is consistent.

The embodiment of the present disclosure further provides a non-transitory computer readable storage medium storing computer executable instructions for performing any of the above-described bearer establishment methods applied to a mobility management entity.

The embodiment of the present disclosure further provides a non-transitory computer readable storage medium storing computer executable instructions for performing any of the above-described bearer establishment methods applied to a service gateway.

As shown in FIG. 8 , a hardware structure diagram of a mobility management entity MME is further provided in the embodiment of the present disclosure. As shown in FIG. 8 , the mobility management entity includes:

A processor 810 and a memory 820; may further include a communication interface 830 and a bus 840.

The processor 810, the memory 820, and the communication interface 830 can complete communication with each other through the bus 840. Communication interface 830 can be used for information transmission. The processor 810 can invoke logic instructions in the memory 820 to perform any of the bearer setup methods applied to the mobility management entity in the above embodiments.

In addition, the logic instructions in the memory 820 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

As shown in FIG. 9, a hardware structure diagram of a serving gateway SGW is further provided in the embodiment of the present disclosure. As shown in FIG. 9, the service gateway includes:

A processor 910 and a memory 920; may further include a communications interface 930 and a bus 940.

The processor 910, the memory 920, and the communication interface 930 can complete communication with each other through the bus 940. Communication interface 930 can be used for information transfer. The processor 910 can invoke logic instructions in the memory 920 to perform any of the bearer setup methods applied to the serving gateway in the above embodiments.

Moreover, the logic instructions in memory 920 described above may be implemented in the form of software functional units and sold or used as separate products, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

In summary, by the technology provided by the embodiment of the present disclosure, the destination SGW notifies the MME that the failed PDN connection or the failed bearer is created before the destination SGW receives the modify bearer request, and the MME may notify the MME. The PGW releases the PND connection or the bearer that the destination SGW has failed to be created, so that the problem that the PGW and the destination SGW are not consistent with the user in the SGW can be ensured.

Those skilled in the art will appreciate that the above-described modules or steps of the present disclosure may be implemented in a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, optionally They may be implemented by program code executable by the computing device such that they may be stored in the storage device for execution by the computing device and, in some cases, may be performed in a different order than that illustrated herein. Or the steps described, either separately as a plurality of integrated circuit modules, or as a plurality of modules or steps in a single integrated circuit module.

Industrial applicability

The embodiments of the present disclosure provide a bearer establishment method and system, and a mobility management entity MME and a serving gateway SGW, which can solve the problem that the PGW cannot be consistent with the user bearer of the destination SGW in the SGW change intra-office handover process, and the PGW can be made. It is consistent with the user bearer of the destination SGW.

Claims

A bearer establishment method includes:

The mobile management entity MME receives the create session response message returned by the destination service gateway SGW, where the create session response message carries an indication message of the public data network PDN connection and/or bearer of the destination SGW creation failure;

The MME notifies the source PDN gateway PGW to release the PDN connection and/or bearer that the destination SGW fails to create through the source SGW;

The MME sends a modify bearer request to the destination SGW.
The method according to claim 1, before the MME receives the create session response message returned by the destination SGW, the method further includes:

The MME sends a create session request to the destination SGW.
The method according to claim 2, wherein the MME sends N creation session requests to the destination SGW, and the MME receives M response messages returned by the destination SGW, and the M response messages are set. In order to indicate that the M PDN connection fails to be created, the MME notifies the source PGW to release the PDN connection that the destination SGW fails to create through the source SGW, including:

The MME notifying, by the source SGW, the source PGW to release the M PDN connections indicated by the M pieces of response messages;

Sending, by the MME, a modify bearer request to the destination SGW, including:

The MME sends an (N-M) modified bearer request to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.
The method of claim 2, wherein the indication message of the failed bearer is used to indicate that the failed bearer is created, and the PDN where the failed bearer is created.
The method according to claim 4, wherein the MME sends N creation session requests to the destination SGW, and the MME receives N response messages returned by the destination SGW, in the N response messages. If the M response message is set to indicate that the bearer of the PDN connection corresponding to the response message fails to be created, the MME notifies the source PGW to release the bearer that the destination SGW fails to create, including:

And the MME, by using the source SGW, to notify the source PGW to release the bearer that fails to be created under the M PDN connections corresponding to the M response messages;

Sending, by the MME, a modify bearer request to the destination SGW, including:

The MME sends N modified bearer requests to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.
The method according to any one of claims 1 to 5, wherein the MME notifies the source PGW to release the PDN connection and/or bearer that the destination SGW fails to create through the source SGW, including:

Sending, by the MME, a deletion return request to the SGW;

The SGW sends a delete callback request to the source PGW, where the delete callback request is used to instruct the source PGW to release the PDN connection and/or bearer that the destination SGW fails to create.
A bearer establishment method includes:

The destination serving gateway SGW receives the create session request sent by the mobility management entity MME;

Creating, by the destination SGW, a public data network PDN connection and/or bearer in response to the create session request;

The destination SGW returns a create session response message to the MME, where the create session response message carries an indication message of the PDN connection and/or bearer that the destination SGW fails to create.
The method of claim 7, after the destination SGW returns a create session response message to the MME, the method further includes:

The destination SGW receives the modify bearer request sent by the MME, where the modify bearer request is sent by the MME after the source SGW notifies the source PDN gateway PGW to release the PDN connection and/or bearer that the destination SGW fails to create. of.
A mobility management entity MME, comprising:

a receiving module, configured to receive a create session response message returned by the destination service gateway SGW, where the create session response message carries an indication message of a PDN connection and/or bearer of the public data network PDN that fails to be created by the destination SGW;

a notification module, configured to notify the source PGW by the source SGW to release the PDN connection and/or bearer that the destination SGW fails to create;

The first sending module is configured to send a modify bearer request to the destination SGW.
The MME according to claim 9, further comprising:

The second sending module is configured to send a create session request to the destination SGW before receiving the create session response message returned by the destination SGW.
The MME according to claim 10, wherein

The notification module is configured to send, by the MME, N creation session requests to the destination SGW, and the MME receives M response messages returned by the destination SGW, where the M response messages are set to indicate that there is an M In the case that the PDN connection creation fails, the source SGW is notified by the source SGW to release the M PDN connections indicated by the M response messages.

The first sending module is configured to send (N-M) a modified bearer request to the destination SGW, where Where N is a positive integer, M is a positive integer, and N is greater than or equal to M.
The MME according to claim 10, wherein

The notification module is configured to send, by the MME, N creation session requests to the destination SGW, the MME receives N response messages returned by the destination SGW, and the M response messages have M responses. If the message is set to indicate that the part of the PDN connection corresponding to the PDN connection fails to be created, the source SGW notifies the source PGW to release the M PDNs corresponding to the M response message. Carrying;

The first sending module is configured to send N modify bearer requests to the destination SGW, where N is a positive integer, M is a positive integer, and N is greater than or equal to M.
A service gateway SGW, comprising:

a first receiving module, configured to receive a create session request sent by the MME;

Creating a module, configured to create a public data network PDN connection and/or bearer in response to the create session request;

The returning module is configured to return a create session response message to the MME, where the create session response message carries an indication message of the PDN connection and/or bearer that the SGW fails to create.
The SGW of claim 13 further comprising:

The second receiving module is configured to: after the SGW returns a create session response message to the MME, receive a modify bearer request sent by the MME, where the modify bearer request is that the MME notifies the source PDN gateway by using the source SGW The PGW releases the PDN connection that was created after the SGW failed to be created and/or sent.
A bearer establishment system comprising: the MME according to any one of claims 9 to 12, the SGW according to claim 13 or 14, and a source SGW and a PGW.
A non-transitory computer readable storage medium storing computer executable instructions for performing the bearer establishment method of any one of claims 1-6, 7-8.