CN103155688B

CN103155688B - The processing method of a kind of carrying, system and device

Info

Publication number: CN103155688B
Application number: CN201180001575.XA
Authority: CN
Inventors: 陆峰; 银宇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2011-08-31
Filing date: 2011-08-31
Publication date: 2016-07-13
Anticipated expiration: 2031-08-31
Also published as: CN103155688A; WO2013029245A1

Abstract

The present invention relates to communication technical field, particularly relate to the processing method of a kind of carrying, system and device.The processing method of a kind of carrying provided by the invention, after source network side shifting managed network element knows the information of carrying that target network side can not create or retain, described source network side shifting managed network element trigger source network-side service gateway sends the second deletion conversation request message to block domain data network gateway, and described second deletes conversation request message carries the information of the carrying that described target network side can not create or retain.By method provided by the invention so that when being moved management process, block domain data network gateway can the delete target network side information of carrying that can not create or retain.

Description

Method, system and device for processing load bearing

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, a system, and an apparatus for processing a bearer.

Background

In The process of developing a network to be broadband and mobile, 3GPP (The3rd generation partnership project, third generation partnership project) proposes an LTE (long term evolution) plan on a mobile access network side, that is, an E-UTRAN (evolved universal mobile telecommunications system terrestrial radio access network); an SAE (system architecture evolution) plan, namely EPC (evolved packet core), is proposed on the core network side. The E-UTRAN and the EPC constitute an EPS (evolved packet System). The UE (user equipment) can access the EPC through any one of an access mode of E-UTRAN, UTRAN (universal mobile telecommunications system terrestrial radio access network ), GERAN (GSM EDGE radio access network, GSM/EDGE radio access network). Fig. 1 is a current wireless evolution network architecture diagram.

As shown in fig. 1, the EPC specifically includes, but is not limited to, an MME (mobility management entity), an SGSN (serving GPRS support node), an SGW (serving gateway), and a PGW (packet domain data network gateway). Wherein, the MME/SGSN is mainly responsible for NAS (non Access stratum) signaling management, bearing management, tracking and paging management in the user idle mode and other functions; the SGW is mainly responsible for functions of local mobility anchor points, mobility anchor points in a 3GPP system, lawful monitoring of relevant information and the like; the PGW is mainly responsible for policy enforcement and charging and lawful interception related functions. Wherein, the MME and the SGSN are collectively referred to as a mobility management network element.

As shown in fig. 1, the radio access portion of the 2G network is GERAN, and is composed of BTS (base transceiver station) and BSC (base station controller); the radio access part of the 3G network is UTRAN, and is composed of an RNC (radio network controller) and a NodeB (node B); the radio access part of the LTE network is E-UTRAN, and is composed of enodebs (evolved node bs).

When moving from the service range of one radio access network element to the service range of another radio access network element, the UE in the idle state may trigger a TAU (tracking area location update) flow or a RAU (routing area location update) flow; the UE in the connected state may trigger a Handover procedure. The TAU flow, RAU flow and Handover flow are collectively referred to as a mobility management flow. The mobility management procedure may trigger a change of MME/SGSN corresponding to the UE and may trigger a change of SGW corresponding to the UE. When the network element is triggered to change, the bearer context of the UE needs to be established on the target network side, and the bearer context of the UE needs to be deleted on the source network side. In the embodiment of the invention, the network where the UE is located before moving is called a source network side, and the network where the UE is located after moving is called a target network side.

Fig. 2 is a schematic diagram of an implementation process of UE triggering TAU procedure, where:

step S202-step S203: UE sends TAU request message to target network side MME;

step S204-step S207: the target network side MME acquires the bearing context information of the UE from the source network side MME through the context response message, and indicates that the SGW in the TAU flow of the source network side MME has changed through the context confirmation message;

step S208-step S211: creating a bearing context of the UE at a target network side, and updating a bearing between an SGW and a PGW at the target network side;

step S218-step S219: and deleting the bearing context of the UE on the source network side MME and the source network side SGW.

Through the analysis of the prior art, the inventor considers that the prior art has at least the following problems:

when a mobility management procedure occurs, in the prior art, only the source network side MME and the source network side SGW delete the bearer context created by the source network side for the UE, and the default packet domain data network gateway PGW will continue to remain as the bearer context created by the UE, however, when the mobility management procedure occurs, some bearers may not be created or retained at the target network side due to a local policy or other reasons, so that information of these bearers may be stored in the PGW for a long time, resulting in a waste of bearer context resources in the EPC network.

Disclosure of Invention

Embodiments of the present invention provide a method, a system, and a device for processing a bearer, so that when a mobility management procedure occurs, a packet domain data network gateway PGW may delete information of a bearer that cannot be created or retained by a target network side.

The embodiment of the invention provides a bearing processing method, which comprises the following steps:

the source network side mobile management network element acquires the information of the load which can not be created or reserved by the target network side;

and the source network side mobile management network element triggers the source network side service gateway to send a second session deletion request message to the packet domain data network gateway, wherein the second session deletion request message carries the information of the bearers which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearers which cannot be created or reserved by the target network side.

Another method for processing a bearer according to an embodiment of the present invention includes:

a source network side service gateway receives a trigger instruction sent by a source network side mobile management network element, wherein the trigger instruction is sent after the source network side mobile management network element acquires information of a bearer which cannot be created or reserved by a target network side;

and the source network side service gateway sends a second session deletion request message to the packet domain data network gateway according to the trigger indication, wherein the second session deletion request message carries the information of the bearer which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearer which cannot be created or reserved by the target network side.

An embodiment of the present invention provides a mobility management network element, including:

a learning unit, configured to learn information of bearers that cannot be created or reserved by a target network side;

a sending unit, configured to trigger a source network side serving gateway to send a second delete session request message to a packet domain data network gateway after the learning unit learns information of bearers that cannot be created or reserved by a target network side, where the second delete session request message carries information of bearers that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearers that cannot be created or reserved by the target network side.

The embodiment of the invention provides a service gateway, which comprises:

the mobile management network element comprises a receiving unit and a sending unit, wherein the receiving unit is used for receiving a trigger instruction sent by a mobile management network element at a source network side, and the trigger instruction is sent after the mobile management network element at the source network side acquires information of a bearer which cannot be created or reserved at a target network side;

a sending unit, configured to send a second delete session request message to the packet data network gateway according to the trigger indication received by the receiving unit, where the second delete session request message carries information of a bearer that cannot be created or reserved by the target network side, so that the packet data network gateway deletes the information of the bearer that cannot be created or reserved by the target network side.

The embodiment of the invention provides a bearing processing system, which comprises: a source network side mobile management network element, a source network side service gateway, a packet domain data network gateway, wherein,

the source network side mobile management network element is used for triggering the source network side service gateway to send a second session deletion request message to the packet domain data network gateway after acquiring the information of the bearer which cannot be created or reserved by the target network side;

the source network side service gateway is configured to receive a trigger instruction sent by a source network side mobility management network element, and send a second delete session request message to a packet data network gateway according to the trigger instruction, where the second delete session request message carries information of a bearer that cannot be created or reserved by the target network side;

and the packet domain data network gateway is used for deleting the information of the bearer which cannot be created or reserved by the target network side according to the information of the bearer which cannot be created or reserved by the target network side and is carried in the second session deletion request message after receiving the second session deletion request message sent by the source network side service gateway.

In the method and system for processing a bearer, the mobility management network element and the serving gateway provided in the embodiments of the present invention, when a mobility management procedure occurs, the source network side mobility management network element may obtain information of a bearer that cannot be created or reserved by the target network side, and trigger the PGW to delete the information of the bearer that cannot be created or reserved by the target network side, so that redundant bearer information is no longer reserved in the PGW, and a network side bearer context resource is saved.

Drawings

Fig. 1 is a current wireless evolution network architecture diagram;

fig. 2 is a schematic diagram of an implementation process of UE triggering TAU procedure;

fig. 3 is a method for processing a bearer according to an embodiment of the present invention;

fig. 4 is a processing method of a bearer according to a second embodiment of the present invention;

fig. 5 is a processing method of a bearer according to a third embodiment of the present invention;

fig. 6 is a processing method of a bearer according to a fourth embodiment of the present invention;

fig. 7 is a flowchart of implementing a fifth embodiment of the method according to the present invention;

fig. 8 is a flowchart of an implementation of a sixth embodiment of the method according to the present invention;

fig. 9 is a flowchart of an implementation of a seventh embodiment of the method according to the present invention;

fig. 10 is a flowchart of an implementation of an eighth embodiment of the method according to the present invention;

fig. 11 is a flowchart of an implementation of a ninth embodiment of the method according to the present invention;

fig. 12 is a flowchart of a tenth implementation of a method according to an embodiment of the present invention;

fig. 13 is a mobility management element according to an embodiment of the present invention;

fig. 14 is another mobility management element according to an embodiment of the present invention;

fig. 15 is a service gateway according to an embodiment of the present invention;

fig. 16 is a processing system of a bearer according to an embodiment of the present invention.

Detailed Description

The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

As shown in fig. 3, a method for processing a bearer according to an embodiment of the present invention includes:

s301: the source network side mobile management network element obtains the information of the load bearing which can not be created or reserved by the target network side.

The source network side mobility management element may acquire the information of the bearers that cannot be created or reserved by the target network side by using any one of the following two ways:

in the first mode, the target network side notifies: the source network side mobile management network element receives a notification message sent by a target network side mobile management network element, and obtains information of bearers that cannot be created or reserved by the target network side according to the notification message.

In the second mode, the source network side mobility management network element determines that: the source network side mobile management network element determines the information of the bearer which can not be created or reserved by the target network side according to the information of the bearer created or reserved by the target network side, wherein the information of the bearer created or reserved by the target network side comprises one of the following information or any combination thereof: the method comprises the following steps that the UE carries context information, EPS carrying state information elements, a local strategy of a target network side and information whether the target network side supports the establishment of LIPA (local IP access) PDN (packet data network) connection; when the mobility management network element is not changed in the mobility management process, that is, the source network side mobility management network element and the target network side mobility management network element are the same mobility management network element, the information of the bearer context information of the UE, the local policy of the target network side, and whether the target network side supports LIPAPDN connection creation is stored in the source network side mobility management network element, and the EPS bearer state information element is sent by the UE; when a mobility management network element changes in a mobility management process, that is, a source network side mobility management network element and a target network side mobility management network element are different mobility management network elements, the bearer context information of the UE is stored by the source network side mobility management network element, the EPS bearer state information element is sent to the target network side mobility management network element by the UE and forwarded to the source network side mobility management network element by the target network side mobility management network element, the information about the local policy of the target network side and whether the target network side supports LIPAPDN connection creation is forwarded to the source network side mobility management network element by the target network side mobility management network element, it needs to be noted that when a handover process is triggered, the basis information for creating or reserving bearers by the target network side does not include the EPS bearer state information element.

S302: and the source network side mobile management network element triggers the source network side service gateway to send a second session deletion request message to the packet domain data network gateway, wherein the second session deletion request message carries the information of the bearers which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearers which cannot be created or reserved by the target network side.

The second session deletion request message may be implemented by a first session deletion request message carrying an operation identifier (operation indication, abbreviated as OI) and sent by the source network side mobility management element to the source network side serving gateway SGW. The SGW at the source network side triggers, according to the operation identifier, sending a second delete session request message to a packet domain data network gateway PGW, where in a specific implementation, the operation identifier is set to a specific value, for example, 1; further, if the first delete session request message has no operation identifier set or has an operation identifier set to a non-specific value, the SGW on the source network side may not send a second delete session request message to the PGW.

The first delete session request message carries information of bearers that cannot be created or reserved by the target network side, the SGW of the source network side sends a second delete session request message to the PGW according to the received first delete session request message, and when the PGW receives the second delete session request message, the information of the bearers that cannot be created or reserved by the target network side is deleted.

In the method for processing a bearer provided in the embodiment of the present invention, when a mobility management procedure occurs, a source network side mobility management network element may acquire information of a bearer that cannot be created or reserved by a target network side, and may trigger a PGW to delete the information of the bearer that cannot be created or reserved by the target network side through the source network side, so that redundant bearer information is no longer reserved in the PGW, and a bearer context resource of the network side is saved.

As shown in fig. 4, a method for processing a bearer according to a second embodiment of the present invention includes:

s401: and the target network side mobile management network element determines the information of the load which cannot be created or reserved by the target network side.

The target network side mobility management network element determines information of bearers that the target network side cannot create or reserve according to the information of the bearers created or reserved by the target network side, wherein the information of the bearers created or reserved by the target network side includes one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection. If the mobility management network element is not changed, namely the mobility management network element at the target network side and the mobility management network element at the source network side are the same mobility management network element, the mobility management network element at the target network side acquires the context information of the UE stored by the mobility management network element at the target network side, the local policy at the target network side and the information of whether the target network side supports the establishment of the LIPAPDN connection, and acquires an EPS bearer state cell sent by the UE; if the mobility management network element changes, that is, the target network side mobility management network element and the source network side mobility management network element are different mobility management network elements, the target network side mobility management network element obtains a local policy of the target network side stored by the target network side mobility management network element and information whether the target network side supports LIPAPDN connection creation, and obtains bearer context information of the user equipment sent by the source network side mobility management network element and an EPS bearer state cell sent by the user equipment.

S402: and the target network side mobile management network element sends a notification message to the source network side mobile management network element.

In addition to making the source network side mobility management element know information of bearers that cannot be created or reserved by the target network side through the notification message, an embodiment of the present invention further provides another bearer processing method, as shown in fig. 5, the target network side mobility management element may further send, to the source network side mobility management element, basis information of the bearers that the target network side creates or reserves, and the source network side mobility management element determines, according to the basis information of the bearers that the target network side creates or reserves, information of the bearers that the target network side cannot create or reserve, specifically, the method includes:

s501: the mobile management network element at the target network side determines the basis information of the creation or reservation of the load at the target network side;

s502: and the target network side mobile management network element sends the basis information of the target network side created or reserved load to the source network side mobile management network element, and indicates the source network side mobile management network element to determine the information of the load which can not be created or reserved by the target network side.

In the bearer processing methods provided in the above two embodiments, when a mobility management procedure occurs, the source network side mobility management element may obtain information of a bearer that cannot be created or reserved by the target network side by sending a notification message or basis information of a bearer created or reserved by the target network side to the source network side mobility management element.

As shown in fig. 6, a method for processing a bearer according to a fourth embodiment of the present invention includes:

s601: the method comprises the steps that a source network side service gateway receives a trigger instruction sent by a source network side mobile management network element, wherein the trigger instruction is sent after the source network side mobile management network element acquires information of a bearer which cannot be created or reserved by a target network side.

The receiving, by the source network side service gateway, the trigger instruction sent by the source network side mobility management network element includes: a first delete session request message carrying an operation identifier and sent by a source network side mobility management network element, where the operation identifier is set to a specific value, for example, 1.

S602: and the source network side service gateway sends a second session deletion request message to the packet domain data network gateway according to the trigger indication, wherein the second session deletion request message carries the information of the bearers which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearers which cannot be created or reserved by the target network side.

And the source network side service gateway judges whether the trigger indication carries an operation identifier set as a specific value, and if so, sends a second session deletion request message to the packet domain data network gateway.

And after receiving a second session deletion request message sent by the service gateway at the source network side, the packet domain data network gateway deletes the information of the bearer which cannot be created or reserved at the target network side.

In the method for processing a bearer according to the embodiment of the present invention, when a mobility management procedure occurs, an SGW on a source network side triggers a PGW to delete information of a bearer that cannot be created or reserved on a target network side according to a trigger instruction sent by a mobility management network element on the source network side, so that redundant bearer information is no longer reserved in the PGW, and a bearer context resource on the network side is saved.

The embodiment of the invention is suitable for all wireless access network types and all mobile management process types. In order to make the technical solutions of the present invention clear and fully understood by those skilled in the art, the following are respectively described by taking TAU procedure and Handover procedure as examples.

As shown in fig. 7, a flowchart is an implementation flowchart of a fifth method embodiment according to an embodiment of the present invention, where the embodiment is directed to an application scenario in which an MME and an SGW change simultaneously when a TAU procedure occurs, that is, a target network side MME and a source network side MME are not the same MME, and a target network side SGW and a source network side SGW are not the same SGW, and the embodiment includes:

s701: the method comprises the steps that UE sends a tracking area location update request (TAURequest) message to a target network side MME;

the TAURequest message comprises a GUTI (globally unique temporary identifier) identifier and an EPS bearing state (EPSbererstatus) cell, wherein the GUTI identifier is used for positioning a source network side MME, and the EPS bearing state cell is used for describing EPS bearing context activation state information in UE;

the epsbedirerstatus cell describes the bearer context activation state by 16 EBI (EPS bearer identity) identifiers, each EBI occupies one bit, EBI (0) -EBI (4) are set to be "0" for standby, EBI (5) -EBI (15) use "0" to indicate that the corresponding EPS bearer context is deactivated, and use "1" to indicate that the corresponding EPS bearer context is activated;

s702: the target network side MME sends a context request (ContextRequest) message to the source network side MME;

s703: after receiving a ContextRequest message sent by a target network side MME, a source network side MME sends a context response (ContextResponse) message to the target network side MME;

the context message contains bearer context information of the UE, the bearer context information of the UE is described by an epspdn connections cell, and specifically includes information such as a bearer context (beartercontext) cell, a default bearer identifier (linkedpsserelld), and an access point name (access point name, APN) related to PDN connection, and the bearer context cell contains information such as a bearer identifier (epsbedirerid), a bearer service quality (BearerLevelQoS), a service gateway user name IP address, and a tunnel breakpoint identifier (tunnel endpoint identifier, TEID); each PDN connection is uniquely identified by an identifier of a corresponding default bearer (DefaultBearer), and a context of each PDN connection includes all bearer contexts of the PDN connection, specifically, a bearer context corresponding to a default bearer and bearer contexts corresponding to zero to multiple dedicated bearers, where each bearer context is uniquely identified by a bearer identifier;

s704: the target network side MME determines the information of the load bearing which can not be created or reserved by the target network side;

the target network side MME determines, according to the information of the bearer created or reserved by the target network side, information of the bearer that the target network side cannot create or reserve, where the situation that the target network side cannot create or reserve the bearer can be divided into the following several ways:

(1) the target network side MME determines the information of the bearer which cannot be created or reserved by the target network side according to the inconsistency between the EPS bearer state information element acquired from the UE and the bearer context information of the UE acquired from the source network side MME, wherein the inconsistency is as follows: the EPS bearing state information element obtained from the UE indicates that the activated bearing is not in one-to-one correspondence with the bearing transmitted by the source network side MME; for example, the EPS bearer status information element indicates that the default bearer 5 exists, the bearer context transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, and at this time, after the target network side MME is determined, it may be determined that the target network side cannot create or retain the default bearer 6;

(2) the target network side MME determines the information of the bearers which can not be created or reserved by the target network side according to a local policy, wherein the local policy can comprise an access PDN connection quantity and/or a bearer context quantity control policy, and at the moment, the target network side MME can not successfully create all the bearers of the UE due to the control policy, so that part of the bearers can not be created or reserved on the target network side; for example, the bearer context transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, but the target network side MME can only create the default bearer 5 because the number of the bearer contexts that have already been created on the target network side MME has reached the upper limit of the number of the bearer contexts that are allowed to be created, and at this time, after the target network side MME is determined, it can be determined that the target network side cannot create or retain the default bearer 6;

(3) when UE (user equipment) establishing LIPAPDN connection on a source network side moves, a target network side MME (mobility management entity) judges that the established LIPAPDN connection cannot be reserved on the target network side; for example, the bearer context information transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, where the default bearer 6 is lippdn connection, the default bearer 5 is conventional PDN connection, and the source network side HeNB (HomeEvolvedNodeB) and the target network side HeNB are not in the same home base station network, and at this time, after the target network side MME is determined, it may be determined that the target network side cannot create or retain the default bearer 6;

s705: the target network side MME sends a notification message to the source network side MME, in this embodiment, the notification message may adopt a context response (ContextAck) message;

the ContextAck message may explicitly (directly) indicate information of a bearer that cannot be created or reserved by the target network side, or implicitly (indirectly) indicate information of a bearer that cannot be created or reserved by the target network side, and a specific implementation manner thereof may be implemented by one or a combination of the following manners:

(1) the ContextAck message carries a default bearer identifier (linkedpepsteareld) or an Access Point Name (APN), wherein the default bearer identifier or the access point name may directly correspond to an identifier of a bearer that cannot be created or reserved by the target network side, for example, the default bearer identifier or the access point name may be included in a context "contextended" cell to be deleted, and directly indicates an identifier of a bearer that cannot be created or reserved by the target network side; or, the default bearer identifier or the access point name corresponds to an identifier of a bearer that can be created or reserved by the target network side, implicitly indicates information of a bearer that cannot be created or reserved by the target network side, and the source network side MME learns information of a bearer that cannot be created or reserved by the remaining target network side through locally stored bearer context information of the user equipment and the learned information of a bearer that can be created or reserved by the target network side; or,

(2) the ContextAck message carries an epsbedirerstatus cell, different values (e.g., 1 or 0) in corresponding bits in the epsbedirerstatus cell respectively indicate bearers that the target network side can create or reserve and bearers that the target network side cannot create or reserve, and the source network side MME learns information of the bearers that the target network side cannot create or reserve according to the epsbedirerstatus cell; or,

(3) the context tag message carries a LIPAPDN connection unsupported identifier (lipapdnconnectionnotsupported indication, abbreviated as LPCNSI) to indicate that the LIPAPDN connection cannot be created or reserved on the target network side;

in addition, the context tag message also carries a service gateway change identification (SGWChangeIndication, abbreviated as SGWCI) identification to indicate that the TAU flow has selected a new SGW;

s706: a target network side MME sends a CreateSessionRequest message to a target network side SGW;

the CreateSessionRequest message carries a default bearer identifier of a bearer that can be created or reserved by the target network side, and in addition, the step S706 triggers execution of the step S707;

the step is of PDN granularity, if a plurality of PDN connections (load bearing) can be created or reserved on a target network side, a plurality of creatESessionRequest messages are correspondingly triggered, each creatESessionRequest message corresponds to a related PDN connection, and the step is not triggered for PDN connections which cannot be created or reserved on the target network side;

s707: a target network side SGW sends a modification load request (ModifyBearerRequest) message to a PGW;

wherein the step is of PDN granularity;

s708: a target network side SGW receives a modified bearer response (ModifBearerResponse) message sent by a PGW;

s709: a target network side MME receives a CreateSession response message sent by a target network side SGW;

s710: the source network side MME learns the information of the bearers that the target network side cannot create or retain according to the ContextAck message sent by the target network side MME received in the aforementioned step S705;

it should be noted that step S710 may occur before, after, or concurrently with step S706, and there is no precedence order, and after receiving the ContextAck message sent by the target network side MME, the source network side MME may execute this step;

s711: a source network side MME sends a first delete session request (DeleteSessionRequest) message to a source network side SGW;

for a bearer that cannot be created or reserved by the target network side, the source network side MME may be triggered to send a first delete session request message carrying an operation identifier OI to the source network side SGW, where in a specific implementation, the OI identifier is set to 1, and the OI identifier is used to instruct the source network side SGW to send a second delete session request message to the PGW;

the step is in PDN granularity, if a plurality of PDN connections cannot be created or reserved on a target network side, a plurality of first session deletion request messages are correspondingly triggered, each first session deletion request message corresponds to a relevant PDN connection, and each first session deletion request message carries a default bearer identifier;

s712: a source network side SGW sends a second delete session request (DeleteSessionrequest) message to a PGW according to the received first delete session request message carrying an operation identifier;

wherein, the second delete session request message carries the information of the bearer which can not be created or reserved by the target network side;

s713: after receiving a second session deletion request message sent by a source network side SGW, a PGW deletes bearer information that cannot be created or retained by a target network side according to the bearer information that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response (deletessessionresponse) message to the source network side SGW;

s714: a source network side MME receives a first delete session response (DeleteSessionResponse) message sent by a source network side SGW;

s715: the source network side MME sends a third delete session request (DeleteSessionRequest) message to the source network side SGW;

after the information of the bearers which cannot be created or reserved by the target network side is deleted, the source network side MME initiates a deletion process of the remaining bearer contexts of the UE in the source network side SGW;

wherein, the step is UE granularity, at this time, the third delete session request message carries a scope identifier (SI identifier for short), and the SI identifier is set to 1, which indicates the source network side SGW to release all PDN connection contexts of the UE, and at this time, the OI identifier is set to 0, so that the source network side SGW does not need to send the delete session request message to the PGW;

s716: the source network side MME receives a third delete session response (deletessessionresponse) message sent by the source network side SGW.

In this embodiment, in addition to obtaining the information of the bearers that cannot be created or reserved by the target network side through the notification message, the source network side MME may determine the information of the bearers that cannot be created or reserved by the target network side by receiving the information of the bearers that are created or reserved by the target network side and sent by the target network side MME. Specifically, the EPS bearer status information element, the local policy of the target network side, and the information whether the target network side supports the establishment of LIPAPDN connection may be forwarded to the source network side MME through the context response message, and after the source network side MME receives the context response message carrying the information according to the establishment or retention of the bearer by the target network side, the source network side MME determines the information of the bearer that the target network side cannot establish or retain.

In the fifth embodiment of the method provided in the present invention, when a tracking area location update procedure occurs, the source network MME instructs the source network serving gateway to send a second delete session request message to the PGW, which can trigger the PGW to delete information of bearers that cannot be created or reserved by the target network side, so that redundant bearer information is not retained in the PGW any more, thereby saving bearer context resources of the network side, in addition, the source network MME can learn information of bearers that cannot be created or reserved by the target network side through a notification message or bearer creation or reservation basis information of the target network side, so that the way for the source network MME to learn information of bearers that cannot be created or reserved by the target network side is more flexible, and then, the delete session request operation is classified, and the source network side and the packet data gateway delete bearer information that cannot be created or reserved by the target network side first, and then, the bearer information which can be created or reserved by the rest target network side of the user equipment is deleted on the source network side, so that the operability and flexibility of deleting the created bearer context information of the UE by the source network side are enhanced.

As shown in fig. 8, a flowchart is an implementation flowchart of a sixth embodiment of the method according to an embodiment of the present invention, where, for an application scenario in which an MME does not change and an SGW changes when a TAU procedure occurs, that is, an MME on a target network side and an MME on a source network side are the same MME, and an SGW on the target network side and an SGW on the source network side are not the same SGW, the embodiment includes:

s801: UE sends TAURequest message carrying EPS bearing state information element to MME;

s802: the MME determines the information of the load which can not be created or reserved by the target network side;

the MME determines, according to the information of the bearer created or reserved by the target network side, information of a bearer that cannot be created or reserved by the target network side, where the situation that the target network side cannot create or reserve the bearer can be divided into the following modes:

(1) the MME determines the information of the bearer which cannot be created or reserved by the target network side according to the inconsistency between the EPS bearer state information acquired from the UE and the bearer context information of the UE stored by the MME, wherein the inconsistency is as follows: the EPS bearing state cell obtained from the UE indicates that the activated bearing and the bearing stored by the UE are not in one-to-one correspondence; for example, the EPS bearer status information element indicates that the default bearer 5 exists, and the bearer context of the UE stored by the MME itself includes the contexts of the default bearer 5 and the default bearer 6, and at this time, the MME determines that the target network side cannot create or retain the default bearer 6 after determining;

(2) when the UE establishing the LIPAPDN connection on the source network side moves, the MME judges that the established LIPAPDN connection cannot be reserved on the target network side; for example, the bearer context information of the UE stored by the MME itself includes the contexts of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPAPDN connection, the default bearer 5 is conventional PDN connection, the source network side HeNB and the target network side HeNB are not in the same home base station network, and at this time, the MME determines that the target network side cannot create or retain the default bearer 6 after the MME determines;

in this embodiment, the MME may further determine, according to a local policy, information of bearers that cannot be created or reserved by the target network side, where the local policy may include an access PDN connection number and/or a bearer context number control policy;

s803: the MME sends a CreateSessionrequest message to the SGW on the target network side;

the CreateSessionRequest message carries a default bearer identifier of a bearer that can be created or reserved by the target network side, and in addition, the step S803 triggers execution of the step S804;

s804: the target network side SGW sends a ModiodBererRequest message to the PGW;

wherein the step is of PDN granularity;

s805: a target network side SGW receives a ModiodBererResponse message sent by a PGW;

s806: the MME receives a CreateSessionResponse message sent by the SGW at the target network side;

s807: the MME sends a first session deletion request message to the SGW at the source network side;

for a bearer that cannot be created or reserved by the target network side, the MME may be triggered to send a first delete session request message carrying an operation identifier OI to the source network side SGW, where in a specific embodiment, the OI identifier is set to 1, and the OI identifier is used to instruct the source network side SGW to send a second delete session request message to the PGW;

s808: the source network side SGW sends a second session deletion request message to the PGW according to the received first session deletion request message carrying the operation identifier;

s809: after receiving a second session deletion request message sent by the SGW of the source network side, the PGW deletes the information of the bearers that cannot be created or retained by the target network side according to the information of the bearers that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response message to the SGW of the source network side;

s810: the MME receives a first session deletion response message sent by the SGW at the source network side;

s811: the MME sends a third session deletion request message to the SGW at the source network side;

after the information of the bearers which can not be created or reserved by the target network side is deleted, the MME initiates a deletion process of the remaining bearer contexts of the UE in the SGW of the source network side;

wherein, the step is of UE granularity, at this time, the third delete session request message carries an SI identifier, and the SI identifier is set to 1, which indicates the source network side SGW to release all PDN connection contexts of the UE, and at this time, the OI identifier is set to 0, so that the source network side SGW does not need to send the delete session request message to the PGW;

s812: and the MME receives a third delete session response message sent by the SGW at the source network side.

In the sixth embodiment of the method provided in the present invention, when a tracking area location update procedure occurs, a second session deletion request message is sent to the PGW by indicating the source network side serving gateway, the PGW can be triggered to delete the information of the bearing which can not be created or reserved by the target network side, so that redundant bearing information is not reserved in the PGW any more, the bearing context resource of the network side is saved, in addition, the source network side MME and the target network side MME are the same MME, thereby reducing the communication overhead between network elements, secondly, the operation of deleting the session request is classified, the source network side and the packet data gateway delete the bearer information which cannot be created or reserved by the target network side first, and then delete the bearer information which can be created or reserved by the remaining target network side of the user equipment on the source network side, so that the operability and flexibility of deleting the created bearer context information of the UE by the source network side are enhanced.

As shown in fig. 9, a flowchart is an implementation flowchart of a seventh embodiment of the method according to an embodiment of the present invention, where, for an application scenario in which an MME changes and an SGW does not change when a TAU procedure occurs, that is, a target network side MME and a source network side MME are not the same MME, and a target network side SGW and a source network side SGW are the same SGW, the embodiment includes:

s901: UE sends TAURequest message carrying EPS bearing state information element to target network side MME;

s902: a target network side MME sends a ContextRequest message to a source network side MME;

s903: after receiving the ContextRequest message sent by the target network side MME, the source network side MME sends a ContextResponse message to the target network side MME;

wherein, the ContextResponse message contains the bearer context information of the UE, and the bearer context information of the UE is described by an epspdn connections cell;

s904: the target network side MME determines the information of the load bearing which can not be created or reserved by the target network side;

(3) when UE (user equipment) establishing LIPAPDN connection on a source network side moves, a target network side MME (mobility management entity) judges that the established LIPAPDN connection cannot be reserved on the target network side; for example, the bearer context information transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPAPDN connection, the default bearer 5 is conventional PDN connection, the source network side HeNB and the target network side HeNB are not in the same home base station network, and at this time, after the target network side MME is determined, it may be determined that the target network side cannot create or retain the default bearer 6;

s905: the target network side MME sends a notification message to the source network side MME, wherein in the embodiment, the notification message can adopt a ContextAck message;

(1) the ContextAck message carries a default bearer identifier or access point name information, where the default bearer identifier or access point name may directly correspond to an identifier of a bearer that cannot be created or reserved by the target network side, for example, the default bearer identifier or access point name may be included in a context to be deleted "contextended" cell, and directly indicate an identifier of a bearer that cannot be created or reserved by the target network side; or, the default bearer identifier or the access point name corresponds to an identifier of a bearer that can be created or reserved by the target network side, implicitly indicates information of a bearer that cannot be created or reserved by the target network side, and the source network side MME learns information of a bearer that cannot be created or reserved by the remaining target network side through locally stored bearer context information of the user equipment and the learned information of a bearer that can be created or reserved by the target network side; or,

(3) the context tag message carries the LPCNSI identity to indicate that the LIPAPDN connection cannot be created or reserved on the target network side;

in addition, the ContextAck message will not carry the SGWCI id to indicate that the SGW in the TAU flow has not changed;

s906: the target network side MME sends a ModifyBearerRequest message to the SGW;

the ModifyBearerRequest message carries a default bearer identifier of a bearer that can be created or reserved by the target network side, and in addition, the step S906 triggers execution of the step S907;

the step is of PDN granularity, and if multiple PDN connections (bearers) can be created or reserved on the target network side, multiple ModifyBearerRequest messages are correspondingly triggered, where each ModifyBearerRequest message corresponds to a relevant PDN connection, and the step is not triggered for a PDN connection that cannot be created or reserved on the target network side;

s907: the SGW sends a ModifyBearerRequest message to the PGW;

wherein, the bearer modification request message sent by the SGW to the PGW is implemented by a bearer modification request message sent by a target network side MME to the SGW;

s908: the SGW receives a ModifyBearerResponse message sent by the PGW;

s909: a target network side MME receives a ModifyBearerResponse message sent by an SGW;

s910: the source network side MME learns the information of the bearers that the target network side cannot create or retain according to the ContextAck message sent by the target network side MME received in the aforementioned step S905;

it should be noted that, in this step S910, it may occur before, after, or concurrently with step S906, and there is no precedence order, and after receiving the ContextAck message sent by the target network side MME, the source network side MME may execute this step;

s911: a source network side MME sends a first session deletion request message to an SGW;

for a bearer that cannot be created or reserved by the target network side, the source network side MME may be triggered to send a first delete session request message carrying an operation identifier OI to the SGW, where in a specific embodiment, the OI identifier is set to 1, and the OI identifier is used to instruct the SGW to send a second delete session request message to the PGW;

s912: the SGW sends a second session deletion request message to the PGW according to the received first session deletion request message carrying the operation identifier;

s913: after receiving a second session deletion request message sent by the SGW, the PGW deletes the information of the bearers that cannot be created or retained by the target network side according to the information of the bearers that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response message to the SGW;

s914: and the source network side MME receives a first session deletion response message sent by the SGW.

Seventh, in an embodiment of the method provided in the present invention, when a tracking area location update procedure occurs, the source network side MME instructs the serving gateway to send a second delete session request message to the PGW, which can trigger the PGW to delete information of bearers that cannot be created or reserved by the target network side, so that redundant bearer information is not retained in the PGW any more, and thus context resources of bearers on the network side are saved The operability and flexibility of deleting the bearer context information of the UE created by the source network side are enhanced.

As shown in fig. 10, a flowchart is an implementation flowchart of an eighth embodiment of the method according to the present invention, where the embodiment is directed to an application scenario in which an MME and an SGW change simultaneously when a Handover procedure occurs, and the embodiment includes:

s1001: a HeNB at a source network side triggers a Handover flow;

s1002: a source network side HeNB sends a handover request (Handoverrequired) message to a source network side MME;

s1003: after receiving a Handover required message sent by a HeNB (home evolved node B) of a source network side, an MME (mobility management entity) of the source network side sends a forward redirection request (ForwardRecoverRelocationRequest) message to an MME of a target network side;

the ForwardRecoverationRequest message contains the bearing context information of the UE, and the bearing context information of the UE is described by an EPSPDNConnections cell;

s1004: the target network side MME determines the information of the load bearing which can not be created or reserved by the target network side;

(1) the target network side MME determines the information of the bearers which can not be created or reserved by the target network side according to a local policy, wherein the local policy can comprise an access PDN connection quantity and/or a bearer context quantity control policy, and at the moment, the target network side MME can not successfully create all the bearers of the UE due to the control policy, so that part of the bearers can not be created or reserved on the target network side; for example, the bearer context transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, but the target network side MME can only create the default bearer 5 because the number of the bearer contexts that have already been created on the target network side MME has reached the upper limit of the number of the bearer contexts that are allowed to be created, and at this time, after the target network side MME is determined, it can be determined that the target network side cannot create or retain the default bearer 6;

(2) when UE (user equipment) establishing LIPAPDN connection on a source network side moves, a target network side MME (mobility management entity) judges that the established LIPAPDN connection cannot be reserved on the target network side; for example, the bearer context information transferred by the source network side MME includes the contexts of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPAPDN connection, the default bearer 5 is conventional PDN connection, the source network side HeNB and the target network side HeNB are not in the same home base station network, and at this time, after the target network side MME is determined, it may be determined that the target network side cannot create or retain the default bearer 6;

s1005: the target network side MME sends notification information to the source network side MME, and in this embodiment, the notification information may adopt a forward redirection response (forwardrelocation response) message;

the forwardrelocation response message may explicitly (directly) indicate information of a bearer that cannot be created or reserved by the target network side, or may implicitly (indirectly) indicate information of a bearer that cannot be created or reserved by the target network side, and a specific implementation manner of the forwardrelocation response message may be implemented by one of the following manners or a combination thereof:

(1) the forwardrelocation response message carries a default bearer identifier or access point name information, where the default bearer identifier or access point name may directly correspond to an identifier of a bearer that cannot be created or reserved by the target network side, for example, the default bearer identifier or access point name may be included in a context to be deleted "contextended" cell, and directly indicate an identifier of a bearer that cannot be created or reserved by the target network side; or, the default bearer identifier or the access point name corresponds to an identifier of a bearer that can be created or reserved by the target network side, implicitly indicates information of a bearer that cannot be created or reserved by the target network side, and the source network side MME learns information of a bearer that cannot be created or reserved by the remaining target network side through locally stored bearer context information of the user equipment and the learned information of a bearer that can be created or reserved by the target network side; or,

(2) the forwardrelocation response message carries an epsbedirerstatus cell, different values (e.g., 1 or 0) in corresponding bits in the epsbedirerstatus cell respectively indicate bearers that the target network side can create or reserve and bearers that the target network side cannot create or reserve, and the source network side MME learns information of the bearers that the target network side cannot create or reserve according to the EPS bearer state cell; or,

(3) the forwardrelocation response message carries an LPCNSI identifier to indicate that the target network side cannot create or reserve LIPAPDN connection;

in addition, the forwardrelocation response message also carries an SGWCI identifier to indicate that the Handover procedure has selected a new SGW;

s1006: a target network side MME sends a CreateSessionRequest message to a target network side SGW;

the CreateSessionRequest message carries a default bearer identifier of a bearer that can be created or reserved by the target network side, which is different from the fifth method embodiment and the sixth method embodiment, in step S1006, the target network side SGW is not triggered to send a modifybearerrrequest message to the PGW, and in a subsequent operation of the process, the target network side MME sends the modifybearerrrequest message to the target network side SGW to trigger the target network side SGW to send the modifybearerrrequest message to the PGW;

s1007: a target network side MME receives a CreateSession response message sent by a target network side SGW;

s1008: the source network side MME acquires, according to the forward redirection response message sent by the target network side MME received in the foregoing step S1005, information of a bearer that the target network side cannot create or reserve;

it should be noted that, in step S1008, it may occur before, after, or simultaneously with step S1006, and there is no precedence order, and after receiving the forwarding redirection response message sent by the target network side MME, the source network side MME may execute this step;

s1009: a source network side MME sends a first delete session request (DeleteSessionRequest) message to a source network side SGW;

s1010: a source network side SGW sends a second delete session request (DeleteSessionrequest) message to a PGW according to the received first delete session request message carrying an operation identifier;

s1011: after receiving a second session deletion request message sent by a source network side SGW, a PGW deletes bearer information that cannot be created or retained by a target network side according to the bearer information that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response (deletessessionresponse) message to the source network side SGW;

s1012: a source network side MME receives a first delete session response (DeleteSessionResponse) message sent by a source network side SGW;

s1013: the source network side MME sends a third delete session request (DeleteSessionRequest) message to the source network side SGW;

s1014: the source network side MME receives a third delete session response (deletessessionresponse) message sent by the source network side SGW.

In this embodiment, in addition to obtaining the information of the bearers that cannot be created or reserved by the target network side through the notification message, the source network side MME may determine the information of the bearers that cannot be created or reserved by the target network side by receiving the information of the bearers that are created or reserved by the target network side and sent by the target network side MME. Specifically, the local policy of the target network side and the information of whether the target network side supports the establishment of LIPAPDN connection may be forwarded to the source network side MME through a forward redirection response message, and after the source network side MME receives the forward redirection response message carrying the information of the target network side establishment or reservation bearer, the source network side MME determines the information of the bearer that the target network side cannot establish or reserve.

Eighth of the method provided in this embodiment of the present invention, when a handover procedure occurs, the source network MME instructs the source network serving gateway to send a second delete session request message to the PGW, which may trigger the PGW to delete information of bearers that cannot be created or reserved by the target network side, so that redundant bearer information is not retained in the PGW any more, and thus saving bearer context resources of the network side, in addition, the source network MME may learn, through a notification message or bearer establishment or reservation basis information of the target network side, bearer information that cannot be created or reserved by the target network side, so that the way in which the source network MME learns the bearer information that cannot be created or reserved by the target network side is more flexible, and then, the delete session request operations are classified, and the source network side and the packet data gateway delete the bearer information that cannot be created or reserved by the target network side before deleting the remaining bearer information that can be created or reserved by the target network side of the user equipment at the source network side, the operability and flexibility of deleting the bearer context information of the UE created by the source network side are enhanced.

As shown in fig. 11, a flowchart of a ninth implementation of the method according to the embodiment of the present invention is shown, where the embodiment is directed to an application scenario in which an MME does not change and an SGW changes when a Handover procedure occurs, and the embodiment includes:

s1101: a HeNB at a source network side triggers a Handover flow;

s1102: a HeNB on a source network side sends a HandoverRequired message to an MME;

s1103: the MME determines the information of the load which can not be created or reserved by the target network side;

the MME determines, according to the information of the bearer created or reserved by the target network side, information of the bearer that cannot be created or reserved by the target network side, where the case that the target network side cannot create or reserve the bearer includes:

when the UE establishing the LIPAPDN connection on the source network side moves, the MME judges that the established LIPAPDN connection cannot be reserved on the target network side; for example, the bearer context information of the UE stored by the MME itself includes the contexts of the default bearer 5 and the default bearer 6, where the default bearer 6 is LIPAPDN connection, the default bearer 5 is conventional PDN connection, the source network side HeNB and the target network side HeNB are not in the same home base station network, and at this time, the MME determines that the target network side cannot create or retain the default bearer 6 after the MME determines;

s1104: the MME sends a CreateSessionRequest message to a target network side SGW;

the CreateSessionRequest message carries a default bearer identifier of a bearer that can be created or reserved by the target network side, and the step S1104 does not trigger the target network side SGW to send a ModifyBearerRequest message to the PGW, and in a subsequent operation of the process, the MME sends the ModifyBearerRequest message to the target network side SGW to trigger the target network side SGW to send the ModifyBearerRequest message to the PGW;

if a plurality of PDN connections (bearers) can be created or reserved on the target network side, a plurality of CreateSessionRequest messages are correspondingly triggered, each CreateSessionRequest message corresponds to a related PDN connection, and the step is not triggered for PDN connections which cannot be created or reserved on the target network side;

s1105: the MME receives a CreateSessionResponse message sent by the SGW at the target network side;

s1106: the MME sends a first session deletion request message to the SGW at the source network side;

for a bearer that cannot be created or reserved by the target network side, the MME may be triggered to send a first delete session request message carrying an operation identifier OI to the source network side SGW, where in a specific embodiment, the OI identifier is set to 1;

s1107: the source network side SGW sends a second session deletion request message to the PGW according to the received first session deletion request message carrying the operation identifier;

wherein, the second delete session request message carries information of bearers that the target network side cannot create or retain;

s1108: after receiving a second session deletion request message sent by the SGW of the source network side, the PGW deletes the information of the bearers that cannot be created or retained by the target network side according to the information of the bearers that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response message to the SGW of the source network side;

s1109: the MME receives a first session deletion response message sent by the SGW at the source network side;

s1110: the MME sends a third session deletion request message to the SGW at the source network side;

s1111: and the MME receives a third delete session response message sent by the SGW at the source network side.

Ninth, in the method provided in the embodiment of the present invention, when a handover procedure occurs, a second delete session request message is sent to the PGW by indicating the source network side serving gateway, triggering the PGW to delete the information of the bearer which can not be created or reserved by the target network side can be triggered, so that the PGW can not reserve redundant bearer information any more, thereby saving the bearer context resources of the network side, in addition, the source network side MME and the target network side MME are the same MME, thereby reducing the communication overhead between network elements, secondly, the operation of deleting the session request is classified, the source network side and the packet data gateway delete the bearer information which cannot be created or reserved by the target network side first, and then delete the bearer information which can be created or reserved by the remaining target network side of the user equipment on the source network side, so that the operability and flexibility of deleting the created bearer context information of the UE by the source network side are enhanced.

As shown in fig. 12, a flowchart of a tenth implementation of a method embodiment according to an embodiment of the present invention is shown, where the embodiment is directed to an application scenario in which an MME changes and an SGW does not change when a Handover procedure occurs, and the embodiment includes:

s1201: a HeNB at a source network side triggers a Handover flow;

s1202: a HeNB (home evolved node B) at a source network side sends a HandoverRequired message to an MME (mobility management entity) at the source network side;

s1203: after receiving a Handover required message sent by a HeNB (home evolved node B) of a source network side, an MME (mobility management entity) of the source network side sends a ForwardRelocationRequest message to an MME of a target network side, wherein the ForwardRelocationRequest message carries an EPSPDNConnections cell for describing bearing context information of UE (user equipment);

s1204: the target network side MME determines the information of the load bearing which can not be created or reserved by the target network side;

s1205: the target network side MME sends a notification message to the source network side MME, in this embodiment, the notification message may adopt a forwardrelocation response message;

(2) the forwardrelocation response message carries an epsbedirerstatus cell, different values (for example, 1 or 0) in corresponding bits in the epsbedirerstatus cell respectively indicate a bearer which can be created or reserved by the target network side and a bearer which cannot be created or reserved by the target network side, and the source network side MME learns information of the bearer which cannot be created or reserved by the target network side according to the epsbedirerstatus cell; or,

in the subsequent operation of the process, the target network side MME sends a ModifyBearerRequest message to the SGW to instruct the SGW to send the ModifyBearerRequest message to the PGW;

in addition, the forwardrelocation response message will not carry the SGWCI identifier to indicate that the SGW in the Handover procedure has not changed;

s1206: the source network side MME acquires the information of the load which can not be created or reserved by the target network side according to the received ForwardRecovericationResponse message sent by the target network side MME;

s1207: a source network side MME sends a first session deletion request message to an SGW;

for a bearer that cannot be created or reserved by the target network side, the source network side MME may be triggered to send a first delete session request message carrying an operation identifier OI to the SGW, where in a specific implementation, the OI identifier is set to 1, and the OI identifier is used to instruct the SGW to send a second delete session request message to the PGW;

s1208: the SGW sends a second session deletion request message to the PGW according to the received first session deletion request message carrying the operation identifier;

s1209: after receiving a second session deletion request message sent by the SGW, the PGW deletes the information of the bearers that cannot be created or retained by the target network side according to the information of the bearers that cannot be created or retained by the target network side and is carried in the second session deletion request message, and then sends a second session deletion response message to the SGW;

s1210: and the source network side MME receives a first session deletion response message sent by the SGW.

In the tenth embodiment of the method provided in the present invention, when a handover procedure occurs, the source network MME instructs the serving gateway to send a second delete session request message to the PGW, which may trigger the PGW to delete information of bearers that cannot be created or reserved by the target network side, so that redundant bearer information is no longer reserved in the PGW, thereby saving bearer context resources of the network side, in addition, the source network MME may learn, through a notification message or information according to bearers created or reserved by the target network side, information of bearers that cannot be created or reserved by the target network side, so that the way in which the source network MME learns information of bearers that cannot be created or reserved by the target network side is more flexible, and then, the delete session request operations are classified, the source network side and the packet data gateway delete bearer information that cannot be created or reserved by the target network side first, and then delete the bearer information that can be created or reserved by the remaining target network side of the user equipment on the source network side, the operability and flexibility of deleting the bearing context information of the UE created by the source network side are enhanced.

As shown in fig. 13, a mobility management network element provided for an embodiment of the present invention includes:

a learning unit 1301, configured to learn information of a bearer that cannot be created or reserved by a target network side;

a sending unit 1302, configured to trigger a source network side serving gateway to send a second delete session request message to a packet domain data network gateway after the obtaining unit 1301 obtains information of a bearer that cannot be created or reserved by a target network side, where the second delete session request message carries information of the bearer that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearer that cannot be created or reserved by the target network side.

Further, the learning unit 1301 may be implemented in the following two manners:

the first forming method is as follows: the learning unit 1301 includes:

a first receiving unit, configured to receive a notification message sent by a mobile management network element at a target network side, where the notification message carries an identifier or an access point name of a bearer that cannot be created or reserved at the target network side;

a first determining unit, configured to, after the first receiving unit receives a notification message carrying an identifier or an access point name of a bearer that cannot be created or reserved by a target network side, directly acquire, according to the notification message, information of the bearer that cannot be created or reserved by the target network side; or

A second receiving unit, configured to receive a notification message sent by a mobile management network element at a target network side, where the notification message carries an identifier or an access point name of a bearer that can be created or reserved at the target network side;

a second determining unit, configured to determine, after the second receiving unit receives the notification message carrying the identifier or the access point name of the bearer that can be created or reserved by the target network side, information of the bearer that cannot be created or reserved by the target network side according to locally stored bearer context information of the user equipment and the identifier or the access point name of the bearer that can be created or reserved by the target network side; or

A third receiving unit, configured to receive a notification message sent by a mobile management network element at a target network side, where the notification message carries an EPS bearer status information element, and the EPS bearer status information element indicates a bearer that can be created or reserved at the target network side and a bearer that cannot be created or reserved at the target network side respectively;

a third determining unit, configured to learn, according to the EPS bearer status cell, bearer information that cannot be created or reserved by the target network side after the third receiving unit receives the notification message carrying the EPS bearer status cell; or

A fourth receiving unit, configured to receive a notification message sent by a mobile management network element on the target network side, where the notification message carries an LIPAPDN connection unsupported identifier;

a fourth determining unit, configured to learn, according to the LIPAPDN connection non-support identifier, a LIPAPDN connection that cannot be created or reserved on the target network side after the fourth receiving unit receives the notification message carrying the LIPAPDN connection non-support identifier.

The second structure is as follows: the learning unit 1301 is specifically configured to determine, according to the basis information of the bearer created or reserved by the target network side, information of the bearer that cannot be created or reserved by the target network side, where the basis information of the bearer created or reserved by the target network side includes one of the following information or any combination thereof: the method comprises the following steps that the bearing context information of the user equipment, an EPS bearing state cell, a local strategy of a target network side and information whether the target network side supports the establishment of LIPAPDN connection or not are obtained;

the learning unit 1301 specifically includes:

a fifth determining unit, configured to determine, according to whether the bearer context information of the ue is consistent with the EPS bearer status information element, bearer information that cannot be created or reserved by the target network side; or

A sixth determining unit, configured to determine, according to the local policy of the target network side, information of bearers that cannot be created or reserved by the target network side, where the local policy of the target network side includes a control policy for controlling the number of connections to a PDN and/or the number of contexts in bearer; or

And a seventh determining unit, configured to determine, according to the information about whether the target network side supports creating the LIPAPDN connection, a LIPAPDN connection that the target network side cannot create or reserve.

The sending unit 1302 is specifically configured to send, to a source network side serving gateway, a first delete session request message carrying an operation identifier after the obtaining unit 1301 obtains information of a bearer that cannot be created or reserved by a target network side, where the first delete session request message carries information of a bearer that cannot be created or reserved by the target network side, and the operation identifier triggers the source network side serving gateway to send a second delete session request message to a packet domain data network gateway.

The sending unit 1302 is further configured to send a third delete session request message to the source network side serving gateway after deleting information of bearers that cannot be created or reserved by the target network side, where the third delete session request message indicates that the source network side serving gateway deletes information of bearers that can be created or reserved by the remaining target network side of the user equipment.

In the mobility management element provided in the embodiment of the present invention, the obtaining unit may obtain, through the notification message or the information according to which the target network side creates or retains the bearer, information of the bearer that cannot be created or retained by the target network side, so that the manner of obtaining the information of the bearer that cannot be created or retained by the target network side is more flexible.

As shown in fig. 14, another mobility management network element provided for the embodiment of the present invention includes:

a determining unit 1401, configured to determine information of a bearer that cannot be created or reserved by a target network side;

a sending unit 1402, configured to send, after the determining unit 1401 determines the information of the bearer that cannot be created or reserved by the target network side, a notification message to the source network side mobility management element, and instruct the source network side mobility management element to acquire the information of the bearer that cannot be created or reserved by the target network side.

In addition to making the source network side mobility management element know information of bearers that cannot be created or reserved by the target network side through the notification message, an embodiment of the present invention further provides a mobility management element, so that the target network side mobility management element sends, to the source network side mobility management element, information of bearers that the target network side creates or reserves, and the source network side mobility management element determines, according to the information of the bearers that the target network side creates or reserves, information of bearers that the target network side cannot create or reserve, specifically, the mobility management element includes:

a determining unit 1401' configured to determine basis information for creating or reserving a bearer on a target network side;

a sending unit 1402 'is configured to send, after the determining unit 1401' determines the basis information of the bearer created or reserved by the target network side, the basis information of the bearer created or reserved by the target network side to the source network side mobility management element, and instruct the source network side mobility management element to determine the information of the bearer that cannot be created or reserved by the target network side.

The information according to which the target network side creates or reserves the bearer includes one of the following information or any combination thereof: the UE carries the context information, EPS carries the status cell, the local tactics and target network side of the target network side support and establish LIPAPDN information of connecting.

In the mobility management network element provided in the above two embodiments, the sending unit sends the notification message or the basis information of the bearer created or reserved by the target network side to the mobility management network element on the source network side, so that the mobility management network element on the source network side obtains the information of the bearer that cannot be created or reserved by the target network side.

As shown in fig. 15, a serving gateway SGW provided in an embodiment of the present invention includes:

a receiving unit 1501, configured to receive a trigger instruction sent by a mobile management network element on a source network side, where the trigger instruction is sent after the mobile management network element on the source network side learns information of a bearer that cannot be created or reserved on a target network side;

a sending unit 1502, configured to send a second delete session request message to the packet domain data network gateway according to the trigger indication received by the receiving unit, where the second delete session request message carries information of a bearer that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearer that cannot be created or reserved by the target network side.

The receiving unit 1501 is specifically configured to receive a first delete session request message which is sent by a source network side mobility management element and carries an operation identifier; the sending unit 1502 is specifically configured to send a second delete session request message to the packet domain data network gateway according to the operation identifier in the first delete session request message.

According to the service gateway provided by the embodiment of the present invention, according to the operation identifier received by the receiving unit, the sending unit is triggered to send the second deletion session request message to the PGW, and the PGW is instructed to delete the information of the bearer that cannot be created or reserved on the target network side, so that redundant bearer information is no longer reserved in the PGW, and thus, the network side bearer context resource is saved.

As shown in fig. 16, a processing system for a bearer according to an embodiment of the present invention includes: a source network side mobility management network element 1601, a source network side serving gateway 1602, a packet domain data network gateway 1603, wherein,

the source network side mobility management network element 1601 is configured to trigger the source network side service gateway 1602 to send a second delete session request message to the packet domain data network gateway 1603 after acquiring information of a bearer that cannot be created or reserved by the target network side;

the source network side service gateway 1602 is configured to receive a trigger instruction sent by the source network side mobility management network element 1601, and send a second delete session request message to the packet domain data network gateway 1603 according to the trigger instruction, where the second delete session request message carries information of a bearer that cannot be created or reserved by the target network side;

after receiving the second delete session request message sent by the source network side service gateway 1602, the packet domain data network gateway 1603 is configured to delete the information of the bearer that cannot be created or reserved by the target network side according to the information of the bearer that cannot be created or reserved by the target network side and carried in the second delete session request message.

The source network side mobility management network element 1601 includes:

a sending unit, configured to trigger the source network side serving gateway to send a second delete session request message to the packet domain data network gateway after the obtaining unit obtains information of a bearer that cannot be created or reserved by the target network side;

the source network side service gateway 1602 includes:

the mobile management system comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a trigger instruction sent by a source network side mobile management network element, and the trigger instruction is sent after the source network side mobile management network element acquires information of a bearer which cannot be created or reserved by a target network side;

and the sending unit is used for sending a second session deletion request message to the packet domain data network gateway according to the triggering indication received by the receiving unit.

In addition, the system further includes a target network side mobility management network element, where the target network side mobility management network element is configured to send a notification message to the source network side mobility management network element 1601, so that the source network side mobility management network element 1601 acquires, according to the notification message, information of bearers that cannot be created or reserved by the target network side; or,

the target network side mobility management element is configured to send, to the source network side mobility management element 1601, basis information of a target network side created or reserved bearer, so that the source network side mobility management element 1601 determines, according to the basis information of the target network side created or reserved bearer, information of a bearer that cannot be created or reserved by the target network side, where the basis information of the target network side created or reserved bearer includes one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection.

The source network side mobility management element 1601 and the target network side mobility management element may be the same mobility management element, and at this time, the target network side mobility management element may send a first delete session request message to the source network side service gateway after determining information of a bearer that cannot be created or reserved by the target network side.

In the method and system for processing a bearer, the mobility management element and the serving gateway provided in the embodiments of the present invention, when a mobility management procedure occurs, the source network side mobility management element indicates the source network side serving gateway to send a second delete session request message to the PGW, which may trigger the PGW to delete information of a bearer that cannot be created or retained on the target network side, so that redundant bearer information is no longer retained in the PGW, and thus context resources of the network side bearer are saved And secondly, classifying the operation of deleting the session request, deleting the bearer information which cannot be created or reserved by the target network side by the source network side and the packet data gateway, and then deleting the bearer information which can be created or reserved by the remaining target network side of the user equipment on the source network side, so that the operability and flexibility of deleting the created bearer context information of the UE by the source network side are enhanced.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the scope of the present invention, and it is understood that various changes and modifications can be made by those skilled in the art, and any modifications, equivalents or improvements made under the spirit and principle of the present invention are included in the scope of the appended claims.

Claims

1. A bearer processing method is characterized by comprising the following steps:

the source network side mobile management network element triggers a source network side service gateway to send a second deletion session request message to a packet domain data network gateway, wherein the second deletion session request message carries information of the bearer which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearer which cannot be created or reserved by the target network side;

wherein, the obtaining of the information of the bearer that cannot be created or reserved by the target network side by the source network side mobility management network element includes: the source network side mobile management network element determines the information of the bearer which can not be created or reserved by the target network side according to the information of the bearer created or reserved by the target network side, wherein the information of the bearer created or reserved by the target network side comprises one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection.

2. The method of claim 1, wherein the triggering, by the source network-side mobility management element, the source network-side serving gateway to send the second delete session request message to the packet domain data network gateway comprises:

the source network side mobile management network element sends a first session deletion request message carrying an operation identifier to a source network side service gateway, wherein the first session deletion request message carries information of a bearer which cannot be created or reserved by the target network side;

and the source network side service gateway sends a second session deletion request message to the packet domain data network gateway according to the first session deletion request message carrying the operation identifier.

3. The method of claim 2, wherein the operation identifier takes a specific value.

4. The method according to claim 1 or 2, wherein the obtaining, by the source network side mobility management element, information of bearers that cannot be created or reserved by the target network side includes:

and the source network side mobile management network element receives a notification message sent by the target network side mobile management network element, and acquires the information of the load which cannot be created or reserved by the target network side according to the notification message.

5. The method of claim 4, wherein the source network side mobility management element receives a notification message sent by a target network side mobility management element, and learns the information of the bearers that cannot be created or reserved by the target network side according to the notification message, comprising:

if the notification message carries an identifier or an access point name of a bearer which cannot be created or reserved by a target network side, the source network side mobile management network element directly acquires information of the bearer which cannot be created or reserved by the target network side; or

If the notification message carries the identifier or the access point name of the bearer which can be created or reserved by the target network side, the source network side mobile management network element determines the information of the bearer which cannot be created or reserved by the target network side according to locally stored bearer context information of the User Equipment (UE) and the identifier or the access point name of the bearer which can be created or reserved by the target network side; or

If the notification message carries an EPS bearer status cell, the EPS bearer status cell indicates a bearer that can be created or reserved by the target network side and a bearer that cannot be created or reserved by the target network side, respectively, and the source network side mobility management network element obtains information of the bearer that cannot be created or reserved by the target network side according to the EPS bearer status cell; or

And if the notification message carries a Local Internet Protocol Access (LIPA) Packet Data Network (PDN) connection non-support identifier, the source network side mobility management network element learns the LIPAPDN connection which cannot be created or reserved by the target network side according to the LIPAPDN connection non-support identifier.

6. The method of claim 4, wherein the receiving, by the source network-side mobility management element, the notification message sent by the target network-side mobility management element comprises: and receiving a context response message or forwarding a redirection response message sent by the target network side mobile management network element.

7. The method of claim 4, wherein before the receiving the notification message sent by the target network-side mobility management element, the method further comprises:

the target network side mobile management network element determines the information of the bearer which cannot be created or reserved by the target network side according to the information of the basis of the creation or reservation of the bearer by the target network side, wherein the information of the basis of the creation or reservation of the bearer by the target network side comprises one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection.

8. The method of claim 1, further comprising:

if the source network side mobile management network element and the target network side mobile management network element are the same mobile management network element, the source network side mobile management network element obtains the self-stored bearing context information of the user equipment, the local strategy of the target network side and the information whether the target network side supports the establishment of the LIPAPDN connection, and obtains an EPS bearing state cell sent by the user equipment; or,

if the source network side mobility management network element and the target network side mobility management network element are different mobility management network elements, the source network side mobility management network element obtains the bearing context information of the user equipment stored by the source network side mobility management network element, and obtains information of whether the target network side mobility management network element forwards the EPS bearing state information, the local policy of the target network side and the target network side support the establishment of the LIPAPDN connection.

9. The method according to claim 8, wherein the determining information of bearers that cannot be created or reserved by the target network side according to the information of the bearers created or reserved by the target network side includes:

determining the information of the bearer which can not be created or reserved by the target network side according to whether the bearer context information of the user equipment is inconsistent with the EPS bearer state information element; or

Determining the information of the load bearing which can not be created or reserved by the target network side according to the local strategy of the target network side, wherein the local strategy of the target network side comprises the control strategy of the access PDN connection quantity and/or the load bearing context quantity; or

And determining the LIPAPDN connection which cannot be created or reserved by the target network side according to the information whether the target network side supports the establishment of the LIPAPDN connection.

10. The method according to claim 1 or 2, wherein after the source network-side serving gateway sends the second delete session request message to the packet domain data network gateway, the method further comprises:

and the source network side mobile management network element sends a third session deletion request message to the source network side service gateway, wherein the third session deletion request message indicates that the source network side service gateway deletes the information of the bearers which can be created or reserved by the remaining target network side of the user equipment.

11. A bearer processing method is characterized by comprising the following steps:

a source network side service gateway receives a trigger instruction sent by a source network side mobile management network element, wherein the trigger instruction is sent after the source network side mobile management network element learns the information of the bearers which cannot be created or reserved by a target network side, the source network side mobile management network element determines the information of the bearers which cannot be created or reserved by the target network side according to the information of the bearers which are created or reserved by the target network side, and the information of the bearers which are created or reserved by the target network side comprises one or any combination of the following information: the method comprises the following steps that the bearing context information of the user equipment, an EPS bearing state cell, a local strategy of a target network side and information whether the target network side supports the establishment of LIPAPDN connection or not are obtained;

and the source network side service gateway sends a second session deletion request message to the packet domain data network gateway according to the trigger indication, wherein the second session deletion request message carries the information of the bearers which cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes the information of the bearers which cannot be created or reserved by the target network side.

12. The method of claim 11, wherein the receiving, by the source network-side serving gateway, the trigger indication sent by the source network-side mobility management element comprises: receiving a first delete session request message carrying an operation identifier and sent by a mobile management network element at a source network side, wherein the first delete session request message carries information of a bearer which cannot be created or reserved at a target network side;

then, the source network side service gateway sends a second request message for deleting the session to the packet domain data network gateway according to the first request message for deleting the session carrying the operation identifier.

13. The method according to claim 11 or 12, wherein after the source network-side serving gateway sends the second delete session request message to the packet domain data network gateway, the method further comprises:

and the source network side service gateway receives a third session deletion request message sent by the source network side mobile management network element, wherein the third session deletion request message indicates that the source network side service gateway deletes the information of the bearers which can be created or reserved by the remaining target network side of the user equipment.

14. A mobility management network element, comprising:

a sending unit, configured to trigger a source network side serving gateway to send a second delete session request message to a packet domain data network gateway after the obtaining unit obtains information of a bearer that cannot be created or reserved by a target network side, where the second delete session request message carries information of a bearer that cannot be created or reserved by the target network side, so that the packet domain data network gateway deletes information of a bearer that cannot be created or reserved by the target network side;

wherein the learning unit is specifically configured to: determining the information of the load bearing which can not be created or reserved by the target network side according to the information of the created or reserved load bearing of the target network side; the information according to which the target network side creates or reserves the bearer includes one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection.

15. The mobility management element according to claim 14, wherein the learning unit comprises:

16. The mobility management element according to claim 14, wherein the learning unit comprises:

A sixth determining unit, configured to determine, according to the local policy of the target network side, information of bearers that cannot be created or reserved by the target network side, where the local policy of the target network side includes a control policy for accessing the number of PDN connections and/or the number of bearer contexts; or

17. The mobility management element according to any of claims 14 to 16, wherein the sending unit is specifically configured to:

after the learning unit learns the information of the bearer which cannot be created or reserved by the target network side, a first session deletion request message carrying an operation identifier is sent to a source network side service gateway, the first session deletion request message carries the information of the bearer which cannot be created or reserved by the target network side, and the operation identifier triggers the source network side service gateway to send a second session deletion request message to the packet domain data network gateway.

18. The mobility management element according to claim 17, wherein the sending unit is further configured to:

after deleting the information of the bearers which can not be created or reserved by the target network side, sending a third delete session request message to the source network side service gateway, where the third delete session request message indicates that the source network side service gateway deletes the information of the bearers which can be created or reserved by the remaining target network side of the user equipment.

19. A serving gateway, comprising:

20. The serving gateway of claim 19, wherein the receiving unit is specifically configured to receive a first session deletion request message carrying an operation identifier and sent by a source network side mobility management element; the sending unit is specifically configured to send a second delete session request message to the packet domain data network gateway according to the operation identifier in the first delete session request message.

21. A supported processing system, comprising: a source network side mobility management network element, a source network side serving gateway, and a packet domain data network gateway, wherein,

the packet domain data network gateway is used for deleting the information of the bearer which cannot be created or reserved by the target network side according to the information of the bearer which cannot be created or reserved by the target network side and is carried in the second session deletion request message after receiving the second session deletion request message sent by the source network side service gateway;

the system also comprises a target network side mobile management network element;

the target network side mobility management element is configured to send basis information of a target network side created or reserved bearer to the source network side mobility management element, so that the source network side mobility management element determines, according to the basis information of the target network side created or reserved bearer, information of a bearer that cannot be created or reserved by the target network side, where the basis information of the target network side created or reserved bearer includes one of the following information or any combination thereof: the method comprises the following steps of carrying context information of the user equipment, an EPS carrying state cell, a local policy of a target network side and information whether the target network side supports the establishment of the LIPAPDN connection.

22. The system of claim 21, wherein the source network side mobility management element comprises:

and the sending unit is used for triggering the service gateway at the source network side to send a second session deletion request message to the packet domain data network gateway after the acquiring unit acquires the information of the bearer which cannot be created or reserved at the target network side.

23. The system according to claim 21 or 22, wherein the source network side service gateway comprises:

24. The system according to claim 23, wherein said source network side mobility management element and said target network side mobility management element are the same mobility management element.