WO2017166126A1

WO2017166126A1 - Method, device, and system for identifying invalid bearer context

Info

Publication number: WO2017166126A1
Application number: PCT/CN2016/077875
Authority: WO
Inventors: 何钢杰; 陈中平
Original assignee: 华为技术有限公司
Priority date: 2016-03-30
Filing date: 2016-03-30
Publication date: 2017-10-05

Abstract

Embodiments of the present invention relate to the field of communications and provide a method, device, and system for identifying an invalid bearer context. The method for identifying an invalid bearer context comprises: an MME receives, from an SGW-C, a notification message carrying anomaly indicating information; and the MME determines an invalid bearer context according to the anomaly indicating information. By receiving, from the SGW-C, a notification message carrying anomaly indicating information, and determining an invalid bearer context according to the anomaly indicating information, the MME can learn about an abnormal bearer in a timely manner to avoid a data transmission failure caused by invalid bearer information, thereby improving user experience.

Description

Method, device and system for identifying invalid bearer context

Technical field

The present invention relates to a mobile communication system, and in particular, to a method, device and system for identifying an invalid bearer context.

Background technique

With the development of mobile communication, the functions of the traditional gateway, namely the Serving Gateway (SGW) and the Packet Data Network Gateway (PGW), based on the evolved packet system (EPS) network architecture. The functions, for example, the control function and the message processing function, are decomposed into two independent network elements, namely Control Plane Gateway (GW-C) and User Plane Gateway (GW-U). A new network architecture is called a Distributed Gateway (DGW) architecture. As shown in FIG. 1 , the control plane gateway includes a Control Plane Serving Gateway (SGW-C) and a Control Plane Packet Data Network Gateway (PGW-C), which are specifically used to implement a traditional gateway. Control functions and logic for implementing functions such as session management and/or data path configuration. The user plane gateway includes a User Plane Serving Gateway (SGW-U) and a User Plane Packet Data Network Gateway (PGW-U), which is specifically configured to implement user plane data forwarding on the network side. It is pure data forwarding or just simple control logic.

Based on the above-mentioned distributed gateway architecture, it can be seen that the user plane gateway and the Mobility Management Entity (MME) no longer have direct interaction with data or signaling, and therefore, when the user plane service gateway (SGW) -U) When restarting or down, the MME cannot sense the SGW_U exception in time, causing data transmission to be interrupted.

Summary of the invention

Embodiments of the present invention provide a method, apparatus, and system for identifying an invalid bearer context, which can enable The MME quickly senses the abnormality of the SGW-U and improves system reliability.

The first aspect provides a method for identifying an invalid bearer context, including: the mobility management entity MME receiving a notification message sent by the control plane serving gateway SGW-C, where the notification message carries abnormal indication information; Indicates the information to determine the invalid bearer context.

With reference to the first aspect, in the first implementation manner of the first aspect, the abnormality indication information includes at least one of the following: a first bearer identifier, an identifier of the user equipment UE, and a first user plane serving gateway SGW-U identifier. The first SGW-U identifier is used to indicate that the first SGW-U is abnormal. The abnormality may be restarted or down, or the device caused by a serious alarm or the like may not work normally.

With reference to the first aspect, or the first implementation manner of the first aspect, in the second implementation manner of the first aspect, the first SGW-U identifier is a device identifier or a location of the first SGW-U The IP address of the first SGW-U.

With reference to the first implementable manner of the first aspect or the second implementable manner of the first aspect, in a third implementable manner of the first aspect, the abnormality indication information includes the first SGW-U identifier Determining, by the MME, the invalid bearer context according to the abnormality indication information, the MME obtaining the bearer context of the related bearer of the first SGW-U according to the first SGW-U identifier; the MME The obtained bearer context is determined to be the invalid bearer context.

With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the MME obtains a bearer related to the first SGW-U according to the first SGW-U identifier The bearer context includes: the MME searching for the first SGW-U identifier in a locally stored bearer context, obtaining a bearer context including the first SGW-U identifier; or the MME according to a preset The corresponding relationship between the SGW-U and the bearer is determined, and the related bearer of the first SGW-U is determined, and the bearer context of the related bearer is obtained. The related bearer of the first SGW-U is a bearer corresponding to the first SGW-U identifier.

With the first aspect or the foregoing implementation manners of the first aspect, in a fifth implementation manner of the first aspect, the method further includes: the MME sending a modify bearer request message to the SGW-C, where The modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormality. The bearer, the abnormal bearer is one of the bearers corresponding to the invalid bearer context; the MME receives the modify bearer response message sent by the SGW-C, and the modified bearer response message carries the second bearer identifier and the whole a tunnel endpoint identifier F-TEID, the F-TEID including an IP address of the second SGW-U and a reassigned tunnel endpoint identifier TEID; the MME is updated according to the second bearer identifier and the F-TEID The invalid bearer context.

With reference to the first aspect, or any one of the foregoing first to fourth implementation manners of the first aspect, in a sixth implementation manner of the first aspect, the method further includes: the MME receiving the first UE The sent tracking area update TAU message or service request service request message, the TAU message or service request message carries the identifier of the first UE; if there is an invalid bearer context of the first UE, the SGW-C is sent to the SGW-C Sending a modify bearer request message, where the modify bearer request message carries a third bearer identifier, where the third bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is a bearer corresponding to the invalid bearer context of the first UE; The MME receives the modified bearer response message sent by the SGW-C, where the modified bearer response message carries the third bearer identifier and the F-TEID, where the F-TEID includes the IP address of the second SGW-U and the reassigned The MME updates the invalid bearer context of the first UE according to the third bearer identifier and the F-TEID.

With reference to the sixth implementation manner of the first aspect, in a seventh implementation manner of the first aspect, before the MME receives the TAU or service request message sent by the first UE, the method further includes: the MME receiving The downlink data sent by the SGW-C is notified to the DDN message, where the DDN message carries the third bearer identifier, and the MME sends a paging message to the first UE according to the DDN message, where the paging message is sent. Used to page the first UE.

A second aspect provides a method for identifying an invalid bearer context, the method comprising: the control plane serving gateway SGW-C monitoring a state of the first user plane serving gateway SGW-U; if the first SGW-U is abnormal And the SGW-C sends a notification message to the mobility management entity MME, where the notification message carries abnormal indication information, where the abnormality indication information is used by the MME to determine an invalid bearer context. The abnormality may be restarted or down, or the device caused by a serious alarm or the like may not work normally.

With reference to the second aspect, in the first implementation manner of the second aspect, the abnormality indication information includes at least one of the following: a first bearer identifier, an identifier of the user equipment, and a first SGW-U identifier.

With reference to the first implementation manner of the second aspect, in a second implementation manner of the second aspect, the first SGW-U identifier is a device identifier of the first SGW or the first SGW-U IP address.

With reference to the second aspect or the first or second implementation manner of the second aspect, in a third implementation manner of the second aspect, the method further includes: the SGW-C receiving the sending by the MME The first modified bearer request message, where the first modified bearer request message carries a second bearer identifier, the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is one of the bearers corresponding to the invalid bearer context. The SGW-C sends a recovery bearer request message to the second SGW-U according to the first modified bearer request message, where the resume bearer request message carries the second bearer identifier; the SGW-C receiving station a recovery bearer response message sent by the second SGW-U, the recovery bearer response message carrying the second bearer identifier and the reassigned tunnel endpoint identifier TEID; the SGW-C sending the first modified bearer to the MME And responding to the message, the first modified bearer response message carries the second bearer identifier and a full tunnel endpoint identifier F-TEID, where the F-TEID includes the reassigned TEID and the IP of the second SGW-U address.

With reference to the second aspect or the first or second implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the method further includes: the SGW-C receiving the sending by the MME The first modified bearer request message, where the first modified bearer request message carries a second bearer identifier, the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is one of the bearers corresponding to the invalid bearer context. The SGW-C re-allocates the TEID according to the first modified bearer request message; the SGW-C notifies the second SGW-U of the re-allocated TEID; the SGW-C sends the first to the MME And modifying the bearer response message, where the first modified bearer response message carries the second bearer identifier and the F-TEID, where the F-TEID includes the reassigned TEID and the IP address of the second SGW-U.

A third aspect provides an apparatus for identifying an invalid bearer context, the apparatus being a mobility management entity MME, the apparatus comprising: a receiving unit, configured to receive, by a control plane serving gateway SGW-C The notification message carries the abnormality indication information, and the determining unit is configured to determine the invalid bearer context according to the abnormality indication information received by the receiving unit.

With reference to the third aspect, in a first implementation manner of the third aspect, the abnormality indication information includes at least one of the following: a first bearer identifier, an identifier of the user equipment UE, and a first user plane serving gateway SGW-U identifier. The first SGW-U identifier is used to indicate that the first SGW-U is abnormal. The abnormality may be restarted or down, or the device caused by a serious alarm or the like may not work normally.

With reference to the first implementation manner of the third aspect, in a second implementation manner of the third aspect, the first SGW-U identifier is a device identifier of the first SGW-U or the first SGW -U's IP address.

With reference to the first or second implementation manner of the third aspect, in a third implementation manner of the third aspect, the abnormality indication information includes the first SGW-U identifier, and the determining unit is specifically used Obtaining, according to the first SGW-U identifier, a bearer context of the related bearer of the first SGW-U; determining the obtained bearer context as the invalid bearer context. The related bearer may include a bearer whose one end is the first SGW-U.

With reference to the third implementation manner of the third aspect, in a fourth implementation manner of the third aspect, the determining unit is further configured to: search for the first SGW-U identifier in a locally stored bearer context, Obtaining a bearer context that includes the first SGW-U identifier; or determining a related bearer of the first SGW-U according to a correspondence between the preset SGW-U identifier and the bearer, and obtaining the related bearer Hosting context. The related bearer may be a bearer corresponding to the first SGW-U identifier.

The fourth aspect provides an apparatus for identifying an invalid bearer context, where the apparatus is a control plane serving gateway SGW-C, and the apparatus includes: a monitoring unit, configured to monitor a state of the first user plane serving gateway SGW-U; a sending unit, configured to: if the monitoring unit detects that the first SGW-U is abnormal, send a notification message to the mobility management entity MME, where the notification message carries abnormal indication information, where the abnormality indication information is used by the The MME determines the invalid bearer context. The abnormality may be restarted or down, or the device caused by a serious alarm or the like may not work normally.

With reference to the fourth aspect, in a first implementation manner of the fourth aspect, the abnormality indication information packet At least one of the following: a first bearer identifier, an identifier of the user equipment, and the first SGW-U identifier.

With reference to the first implementation manner of the fourth aspect, in a second implementation manner of the fourth aspect, the first SGW-U identifier is a device identifier of the first SGW or the first SGW-U IP address.

With reference to the fourth aspect or the first or second implementation manner of the fourth aspect, in a third implementation manner of the fourth aspect, the device further includes a receiving unit, and the receiving unit is configured to receive the a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is corresponding to the invalid bearer context. And a sending unit, configured to send a recovery bearer request message to the second SGW-U according to the first modified bearer request message received by the receiving unit, where the resume bearer request message carries The receiving unit is further configured to receive a recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and a reassigned tunnel endpoint identifier The sending unit is further configured to send a first modified bearer response message to the MME, where the first modified bearer response message carries the second bearer identifier and Tunnel Endpoint Identifier F-TEID, the F-TEID including the IP address and TEID of the re-allocation of the second of the SGW-U.

With reference to the fourth aspect or the first or second implementation manner of the fourth aspect, in a fourth implementation manner of the fourth aspect, the device further includes: a receiving unit and a processing unit; And the first modified bearer request message is sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is invalid. a processing unit, configured to: re-allocate the TEID according to the first modified bearer request message; and notify the second SGW-U of the re-allocated TEID; the sending unit further And sending, by the MME, a first modified bearer response message, where the first modified bearer response message carries the second bearer identifier and an F-TEID, where the F-TEID includes the reassigned TEID and the first The IP address of the second SGW-U.

In view of the above drawbacks, the method or apparatus provided by the embodiment of the present invention, the MME receives the SGW-C The notification message is sent, and the notification message carries the abnormality indication information, and the invalid bearer context is determined according to the abnormality indication information, so that the MME can know the abnormal bearer in time, avoid the data transmission failure caused by the invalid bearer information, and improve the user experience. .

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying for creative labor.

1 is a schematic diagram of a distributed gateway architecture;

2 is a flowchart of a method for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 3 is a flowchart of another method for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 4 is a flowchart of another method for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 5 is a flowchart of still another method for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an apparatus for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of another apparatus for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of another apparatus for identifying an invalid bearer context according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another apparatus for identifying an invalid bearer context according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

As shown in FIG. 2, an embodiment of the present invention provides a method for identifying an invalid bearer context, where the method includes:

Step 201: The MME receives a notification message sent by the SGW-C, where the notification message carries an abnormality indication letter. interest.

The abnormality indication information may be used to indicate a bearer or device in which an abnormality occurs, for example, an abnormal bearer or an abnormal SGW-U, or a user equipment (UE) for indicating an abnormal device. Specifically, the abnormality indication information may include at least one of the following: a first bearer identifier, an identifier of the UE, and a first SGW-U identifier. The first SGW-U is a restart or downtime SGW-U, and the first SGW-U identifier is used to indicate the first SGW-U. In other words, the first SGW-U identifier is used to indicate the first abnormality. SGW-U; the identifier of the first SGW-U may be a device identifier or an IP address of the first SGW-U.

In addition, the first bearer identifier is used to indicate an abnormal bearer, and the first bearer identifier may be a Tunnel Endpoint Identifier (TEID) or a bearer ID. The identifier of the UE is used to indicate that the bearer has an abnormality, for example, an international International Mobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity (TMSI) or other identifier.

The notification message may be an error notification message, and the structure of the error notification message may include multiple IMSIs and multiple bearer IDs, which may be in the form of a list, as shown in Table 1:

Table 1

信元Cell	说明Description
IMSI ListIMSI List	IMSI列表IMSI list
Bearer ID ListBearer ID List	承载ID列表Bearer ID list

Step 202: The MME determines an invalid bearer context according to the abnormality indication information.

Specifically, the bearer context may further include an invalid indication bit, and the step 202 may include setting a value of the invalid indication bit to a first specific value, where the first specific value is used to indicate that the bearer context is invalid, for example, the first specific value may be 1, there is no limit here.

It should be noted that, in various embodiments of the present invention, the invalid bearer context refers to a bearer context packet. The invalid bearer information is included, and the invalid bearer information causes the data to be unsuccessfully transmitted. For example, due to the restart or downtime of the SGW-U, the Fully Tunnel Endpoint Identifier (F-) of the SGW-U end in the bearer context is caused. The TEID is invalid. The F-TEID contains the tunnel IP address and TEID, which are not mentioned here.

The method provided by the foregoing embodiment, by receiving the notification message sent by the SGW-C, the notification message carries the abnormal indication information, and determines the invalid bearer context according to the abnormality indication information, so that the MME can know the abnormal bearer in time, and the MME is invalid. The bearer information is provided to other network elements, thereby avoiding data transmission failure due to invalid bearer information, thereby improving user experience.

Optionally, in the first implementation scenario of the foregoing embodiment, if the abnormality indication information includes the first bearer identifier, step 202 specifically includes:

Step 2021a: The MME searches for a locally stored bearer context according to the first bearer identifier.

Step 2022: The MME determines, as the invalid bearer context, the bearer context of the bearer indicated by the first bearer identifier.

The foregoing finding the local storage context by using the bearer identifier can find the invalid bearer context in a timely and accurate manner, that is, finding an abnormal bearer and improving the working efficiency of the system.

Optionally, in the second implementation scenario of the foregoing embodiment, the abnormality indication information includes the identifier of the UE, and the step 202 specifically includes:

Step 2021b: The MME searches for a locally stored bearer context according to the identifier of the UE.

Step 2022b: The MME determines, as the invalid bearer context, the bearer context of the bearer of the UE indicated by the identifier of the UE.

Optionally, in the third implementation scenario of the foregoing embodiment, the abnormality indication information includes the first SGW-U identifier, and the step 202 specifically includes:

Step 2021c: The MME obtains a bearer context of the related bearer of the first SGW-U according to the first SGW-U identifier.

Step 2022c: The MME determines the obtained bearer context as an invalid bearer context.

The related bearer may include a bearer whose first end is the first SGW-U.

Further, step 2021c may specifically include:

The MME searches for the first SGW-U identifier in the locally stored bearer context, and obtains the bearer context that includes the first SGW-U identifier; or

The MME determines the related bearer of the first SGW-U according to the preset correspondence between the SGW-U identifier and the bearer, and obtains the bearer context of the related bearer.

The related bearer is a bearer corresponding to the first SGW identifier.

Optionally, in the fourth implementation scenario of the foregoing embodiment, after step 202, steps 203-205 are further included, as follows:

Step 203: The MME sends a modify bearer request message to the SGW-C.

The modify bearer request message may carry a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is one of the bearers corresponding to the invalid bearer context, in other words, the abnormal bearer belongs to the invalid The bearer corresponding to the bearer context, and the bearer context of the abnormal bearer is an invalid bearer context. Specifically, when the bearer corresponding to the invalid bearer context includes only one bearer, the abnormal bearer is the bearer corresponding to the invalid bearer context; when the bearer corresponding to the invalid bearer context includes two or more bearers, the abnormal bearer is One of the bearers corresponding to the invalid bearer context described above.

It should be noted that, in the embodiments of the present invention, the bearer corresponding to the invalid bearer context refers to the bearer to which the invalid bearer context belongs.

Step 204: The MME receives the modify bearer response message sent by the SGW-C.

The modified bearer response message carries a second bearer identifier and an F-TEID, and the F-TEID may include an IP address of the second SGW-U and a re-allocated TEID; in addition, the re-allocated TEID may be allocated by the SGW-C. It may also be allocated by the second SGW-U, and the second SGW-U may be the reselected SGW-U or the first SGW-U after the restart, which is not limited.

Step 205: The MME updates the invalid bearer context according to the second bearer identifier and the F-TEID.

It should be noted that updating the invalid bearer context in the embodiments of the present invention may specifically include updating the invalid F-TEID in the invalid bearer context indicated by the second bearer identifier, and is not limited.

Optionally, in the fifth implementation scenario of the foregoing embodiment, after step 202, steps 206-209 are further included, as follows:

Step 206: The MME receives a track area update (TAU) message or a service request (service request) message sent by the first UE.

The TAU message or the service request message may carry the identifier of the first UE.

Step 207: If there is an invalid bearer context of the first UE, the MME sends a modify bearer request message to the SGW-C.

The modify bearer request message may carry a third bearer identifier, where the third bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is a bearer corresponding to the invalid bearer context of the first UE.

Specifically, the MME may determine, according to the identifier of the first UE, whether an invalid bearer context of the first UE exists. For example, the bearer context of the first UE stored locally is searched according to the identifier of the first UE. If the setting value indicating that the invalid indicator bit in the at least one bearer context is invalid, it is determined that the invalid bearer context of the first UE exists.

Step 208: The MME receives the modify bearer response message sent by the SGW-C.

The modified bearer response message carries a third bearer identifier and an F-TEID, and the F-TEID may include an IP address of the second SGW-U and a re-allocated TEID; in addition, the second SGW-U may be a reselected SGW- U or the first SGW-U after restart is not limited.

Step 209: The MME updates the invalid bearer context of the first UE according to the third bearer identifier and the F-TEID in the modify bearer response message.

Further, before step 206, the foregoing method further includes:

Step 205: The MME receives a downlink data notification (DDN) message sent by the SGW-C, where the DDN message carries a third bearer identifier.

Step 206b: The MME sends a paging message to the first UE according to the DDN message, where the paging message is used to page the first UE.

In the foregoing implementation scenario, the invalid bearer context of the UE is updated by the service, so that the update of the bearer information is more targeted, and the recovery or establishment of a large number of bearers is avoided at the same time, and the system is added. The load, in addition, avoids allocating new resources to user equipment that has left the communication network, resulting in wasted system resources.

It should be noted that, in the embodiments of the present invention, the abnormal bearer refers to that the bearer cannot transmit service data normally, and the abnormal device refers to the device that cannot be caused by restarting or downtime or serious alarm. normal work.

As shown in FIG. 3, an embodiment of the present invention provides another method for identifying an invalid bearer context, where the method includes:

Step 301: The SGW-C monitors the status of the first SGW-U.

Step 302: If the first SGW-U is restarted or down, the SGW-C sends a notification message to the MME.

The notification message carries the abnormality indication information, which is used to indicate the bearer or device in which the abnormality occurs, and is also used by the MME to determine the invalid bearer context. In addition, the abnormality indication information may include at least one of the following: a first bearer identifier, an identifier of the UE, and a first SGW-U identifier.

It should be noted that the first bearer identifier is used to identify the bearer, which may be a TEID; the identifier of the UE is used to identify the UE; the first SGW-U identifier is used to indicate the first SGW-U, and specifically may be the first SGW- The device ID of the U or the IP address of the first SGW-U is not limited.

For the identifier of the UE, the first bearer identifier, and the identifier of the first SGW-U, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein.

Specifically, step 302 may use a timing transmission request or response message to determine the status of the SGW-U. For example, if the SGW-C sends a request message to the first SGW-U and does not receive the response message of the first SGW-U within a preset time, it is determined that the first SGW-U is restarted or down. Among them, restart refers to restart, and the downtime refers to the first SGW-U not working properly.

Alternatively, the step 302 may be that if the first SGW-U is abnormal, the SGW-C sends the foregoing notification message to the MME, where the abnormality may be a restart or a downtime, or the device caused by a serious alarm or the like fails to work normally. No longer.

The method provided by the foregoing embodiment, the SGW-C monitors the state of the SGW-U, and is in the first When the SGW-U is restarted or down, the SGW sends a notification message to the MME, so that the MME can know the abnormal bearer in time, and prevent the MME from providing invalid bearer information to other network elements, thereby avoiding data transmission failure due to invalid bearer information. , to enhance the user's feelings.

Optionally, in the first implementation scenario of the foregoing embodiment, after the step 302, the foregoing method further includes the steps 303-306, as follows:

Step 303: The SGW-C receives the first modified bearer request message sent by the MME.

The first modified bearer request message may carry a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is one of the bearers corresponding to the invalid bearer context. For details, refer to the embodiment shown in FIG. 2 . The relevant description in the description will not be repeated.

Step 304: The SGW-C sends a recovery bearer request message to the second SGW-U according to the first modified bearer request message.

The recovery bearer request message may carry the second bearer identifier. In addition, the second SGW-U may be the SGW-U reselected by the SGW-C. For example, the second SGW-U is randomly selected by the SGW-C or according to the location. The SGW-U may also be the first SGW-U after the restart, and is not limited.

Step 305: The SGW-C receives the recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and the re-allocated TEID.

The redistributed TEID may be allocated by the second SGW-U.

Step 306: The SGW-C sends a first modified bearer response message to the MME.

The first modified bearer response message carries a second bearer identifier and an F-TEID, and the F-TEID may include a reassigned TEID and an IP address of the second SGW-U.

Optionally, in the first implementation scenario of the foregoing embodiment, after the step 302, the foregoing method further includes the steps 307-310, as follows:

Step 307: The SGW-C receives the first modified bearer request message sent by the MME.

The first modified bearer request message may carry a second bearer identifier, where the second bearer identifier is used to indicate a bearer corresponding to the invalid bearer context.

Step 308: The SGW-C re-allocates the TEID according to the first modified bearer request message.

Step 309: The SGW-C notifies the second SGW-U of the re-allocated TEID.

The second SGW-U may be the SGW-U reselected by the SGW-C. For example, the second SGW-U is randomly selected by the SGW-C or selected according to the location, or may be restarted. The first SGW-U is not limited. In addition, the reassigned TEID may be sent to the second SGW-U by a recovery bearer request message.

Step 310: The SGW-C sends a first modified bearer response message to the MME.

The first modified bearer response message may carry a second bearer identifier and an F-TEID, where the F-TEID includes a reassigned TEID and an IP address of the second SGW-U.

Further, the above method may further include:

The SGW-C sends a second modified bearer request message to the PGW-C, where the second modified bearer request message carries the second bearer identifier and the F-TEID;

The SGW-C receives the second modified bearer response message sent by the PGW-C.

Optionally, before step 303 or 307, the foregoing method further includes:

The SGW-C receives the notification message sent by the PGW-C, where the notification message carries a second bearer identifier, where the notification message is used to indicate that downlink data arrives on the bearer indicated by the second bearer identifier.

The SGW-C sends a DDN message to the MME, where the DDN message carries the second bearer identifier.

Optionally, before step 303 or 307, the foregoing method further includes:

The SGW-C receives and buffers the downlink data packet sent by the PGW-C, where the downlink data packet carries the second bearer identifier;

Optionally, before step 303 or 307, the foregoing method further includes:

The SGW-C receives and buffers the downlink data packet sent by the second SGW-U, where the downlink data packet carries the second bearer identifier, and the second SGW-U is the first SGW-U after the restart;

It should be noted that the terminology mentioned in the embodiment shown in FIG. 3 may be specifically referred to the related description in the embodiment shown in FIG. 2, and details are not described herein again.

As shown in FIG. 4, an embodiment of the present invention provides another method for identifying an invalid bearer context, where the method includes:

Step 401: The SGW-C monitors the status of the first SGW-U.

Step 402: If the first SGW-U is restarted or down, the SGW-C sends a notification message to the MME, where the notification message carries abnormal indication information.

For details of the notification message and the abnormality indication information, refer to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein.

The first SGW-U restart or downtime in step 402 may be determined by message interaction between the first SGW-U and the SGW-C. For example, the SGW-C sends a request message to the first SGW-U, if If the response message sent by the first SGW-U is not received within the set time, it is determined that the first SGW-U is restarted or down.

Step 403: The MME receives the notification message sent by the SGW-C.

Step 404: The MME determines an invalid bearer context according to the abnormality indication information in the notification message.

For the invalid bearer context, refer to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein. For details, refer to the implementation scenario related to step 202 in the embodiment shown in FIG. 2, and details are not described herein.

Step 405: The MME sends a modify bearer request message to the SGW-C.

The modify bearer request message carries a bearer identifier, where the bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is one of the bearers corresponding to the invalid bearer context. Specifically, when the bearer corresponding to the invalid bearer context includes only one bearer, the abnormal bearer is the bearer corresponding to the invalid bearer context; when the bearer corresponding to the invalid bearer context includes two or more bearers, the abnormal bearer is For one of the bearers corresponding to the invalid bearer context, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein.

Step 406: The SGW-C sends a recovery bearer request message to the second SGW-U according to the modify bearer request message, where the resume bearer request message carries the bearer identifier.

The second SGW-U may be the reselected SGW-U, or the first after the restart. SGW-U.

Step 407: The second SGW-U re-allocates the TEID according to the recovery bearer request message, and sends a recovery bearer response message to the SGW-C.

The recovery bearer response message carries the bearer identifier and the re-allocated TEID.

It should be noted that, if the TEID is re-allocated by the SGW-C, the recovery bearer response message may not carry the re-allocated TEID, but the SGW-C carries the re-allocated TEID to the second SGW-U through the recovery bearer request message. .

Step 408: The SGW-C receives the recovery bearer response message sent by the second SGW-U.

Step 409: The SGW-C sends a modify bearer response message to the MME, where the modify bearer response message carries the bearer identifier and the F-TEID.

The F-TEID may include an IP address of the second SGW-U and a re-allocated TEID.

Step 410: The MME updates the invalid bearer context according to the second bearer identifier and the F-TEID.

For details about updating the invalid bearer context, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein.

The method provided by the foregoing embodiment is to monitor the state of the SGW-U by using the SGW-C, and send an abnormality indication information to the MME when the SGW-U is confirmed to be abnormal, to indicate that the abnormal bearer occurs; and the MME determines the invalid bearer context according to the abnormality indication information. And triggering the recovery of the completed bearer and the update of the invalid bearer context, not only avoiding the data transmission failure caused by the invalid bearer information, but also realizing the timely recovery of the bearer, thereby quickly recovering the data transmission and ensuring network reliability.

It should be noted that the specific implementation of the term or the steps mentioned in FIG. 4 can be referred to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein again.

As shown in FIG. 5, the embodiment of the present invention provides another method for identifying an invalid bearer context, where the method includes:

Step 501: The SGW-C monitors the status of the first SGW-U.

Step 502: If the first SGW-U is restarted or down, the SGW-C sends a notification message to the MME. The notification message carries abnormal indication information.

For details of the abnormality indication information, the restart or the downtime, refer to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein.

Step 503: The MME receives the notification message sent by the SGW-C.

Step 504: The MME determines an invalid bearer context according to the abnormality indication information.

It should be noted that the related descriptions of the steps 401-404 in the embodiment shown in FIG. 4 may be omitted, and details are not described herein again.

Step 505: The MME receives a TAU message or a service request message sent by the first UE.

The TAU message or the service request message carries the identifier of the first UE, and the identifier of the first UE is used to identify the first UE, which may be IMSI or TMSI, and is not limited.

Step 506: If it is determined that the invalid bearer context of the first UE exists according to the identifier of the first UE, the MME sends a modify bearer request message to the SGW-C, where the modify bearer request message carries the bearer identifier.

The bearer identifier is used to indicate the abnormal bearer, and the abnormal bearer is the bearer corresponding to the invalid bearer context of the first UE. In addition, the implementation manner of determining the invalid bearer context of the first UE according to the identifier of the first UE is determined in step 506. For details, refer to the related description in step 207, and details are not described herein.

Step 507: The SGW-C sends a recovery bearer request message to the second SGW-U according to the modify bearer request message, where the resume bearer request message carries the bearer identifier.

The second SGW-U may be a reselected SGW-U or a first SGW-U after the restart, and is not limited.

Step 508: The second SGW-U re-allocates the TEID according to the recovery bearer request message, and sends a recovery bearer response message to the SGW-C.

Step 509: The SGW-C receives the recovery bearer response message sent by the second SGW-U.

The redistributed TEID may be allocated by the second SGW-U.

Step 510: The SGW-C sends a modify bearer response message to the MME, where the modify bearer response message carries the bearer identifier and the F-TEID.

Step 511: The MME updates the invalid bearer context according to the second bearer identifier and the F-TEID.

The method provided by the foregoing embodiment is to monitor the state of the SGW-U by using the SGW-C, and send an abnormality indication information to the MME when the SGW-U is confirmed to be abnormal, to indicate that the abnormal bearer occurs; and the MME determines the invalid bearer context according to the abnormality indication information. The recovery of the bearer and the update of the invalid bearer context are triggered by the service flow of the UE, which not only avoids data transmission failure caused by invalid bearer information, but also implements bearer recovery and ensures network reliability. In addition, the recovery of the bearer and the update of the invalid bearer context are triggered by the service flow of the UE, which avoids the waste of the bearer resources and reduces the system load caused by the simultaneous recovery of a large number of bearers.

It should be noted that the specific implementation of the term or the steps mentioned in FIG. 5 can be referred to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein again.

As shown in FIG. 6, the embodiment of the present invention provides an apparatus for identifying an invalid bearer context, where the apparatus is an MME, and is used to perform the operation steps of the MME in the embodiment shown in FIG. 2, 4 or 5. The apparatus includes:

The receiving unit 601 is configured to receive a notification message sent by the SGW-C, where the notification message carries abnormal indication information;

The determining unit 602 is configured to determine an invalid bearer context according to the abnormality indication information received by the receiving unit 601.

The abnormal indication information may include at least one of the following: a first bearer identifier, an identifier of the UE, and a first SGW-U identifier; and the first SGW-U identifier is used to indicate a first SGW-U that is restarted or down. Specifically, the first SGW-U identifier may be a device identifier of the first SGW-U or an IP address of the first SGW-U.

It should be noted that the first bearer identifier, the identifier of the UE, the abnormality indication information, and the invalid bearer context can be referred to the related description in the embodiment shown in FIG. 2, and details are not described herein.

The apparatus provided by the foregoing embodiment receives the notification message sent by the SGW-C, and the notification message The abnormal indication information is carried, and the invalid bearer context is determined according to the abnormality indication information, so that the abnormal bearer can be known in time, and the invalid bearer information is prevented from being provided to other network elements, thereby avoiding the data transmission failure caused by the invalid bearer information, thereby improving the data transmission failure. User's feelings.

Optionally, the foregoing abnormality indication information includes a first bearer identifier, and the determining unit 602 is specifically configured to:

Finding a locally stored bearer context according to the first bearer identifier;

The bearer context of the bearer indicated by the first bearer identifier is determined as an invalid bearer context.

Optionally, the foregoing abnormality indication information includes an identifier of the UE, and the determining unit 602 is specifically configured to:

Finding a locally stored bearer context according to the identifier of the UE;

The bearer context of the bearer of the UE indicated by the identifier of the UE is determined as an invalid bearer context.

Optionally, the abnormality indication information includes a first SGW-U identifier, and the determining unit 602 is specifically configured to:

Obtaining, according to the first SGW-U identifier, a bearer context of the related bearer of the first SGW-U;

The obtained bearer context is determined to be an invalid bearer context.

The related bearer may include a bearer whose first end is the first SGW-U.

Optionally, the determining unit 602 is further configured to:

Finding a first SGW-U identifier in a locally stored bearer context, and obtaining a bearer context that includes the first SGW-U identifier; or

And determining, according to the preset correspondence between the SGW-U identifier and the bearer, the related bearer of the first SGW-U, and obtaining the bearer context of the related bearer.

The related bearer may be a bearer corresponding to the first SGW identifier.

Optionally, the foregoing apparatus further includes a first sending unit 603 and a first updating unit 604;

The first sending unit 603 is configured to send, to the SGW-C, a modify bearer request message, where the modify bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is the invalid bearer context corresponding to For details, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein again.

The receiving unit 601 is further configured to receive a modified bearer response message sent by the SGW-C, where the modified bearer response message carries a second bearer identifier and a full F-TEID.

The F-TEID includes an IP address of the second SGW-U and a re-allocated TEID.

The first update unit 604 is configured to update the invalid bearer context according to the second bearer identifier and the F-TEID received by the receiving unit 601.

Optionally, the foregoing apparatus further includes: a second sending unit 605 and a second updating unit 606;

The receiving unit 605 is further configured to receive a tracking area update TAU message or a service request service request message sent by the first UE, where the TAU message or the service request message carries the identifier of the first UE;

The second sending unit 606 is further configured to: if the invalid bearer context of the first UE exists, send a modify bearer request message to the SGW-C, where the modify bearer request message carries a third bearer identifier, where the third bearer identifier is used to indicate an abnormality a bearer, where the abnormal bearer is a bearer corresponding to an invalid bearer context of the first UE;

The receiving unit 601 is further configured to receive a modified bearer response message sent by the SGW-C, where the modified bearer response message carries a third bearer identifier and an F-TEID, where the F-TEID includes the IP address of the second SGW-U and the reassigned TEID;

The second update unit 606 is configured to update the invalid bearer context of the first UE according to the third bearer identifier and the F-TEID received by the receiving unit 601.

Further, the receiving unit 601 is further configured to: before receiving the TAU or service request message sent by the first UE, receive a DDN message sent by the SGW-C, where the DDN message carries a third bearer identifier;

The second sending unit 606 is further configured to send, according to the DDN message received by the receiving unit 601, a paging message to the first UE, where the paging message is used to page the first UE.

As shown in FIG. 7, an embodiment of the present invention provides an apparatus for identifying an invalid bearer context, where the apparatus is SGW-C, and may be used to perform related operations of SGW-C in the embodiment shown in FIG. 3, 4 or 5. , the device includes:

The monitoring unit 701 is configured to monitor a state of the first SGW-U.

The sending unit 702 is configured to send a notification message to the MME if the monitoring unit 701 detects that the first SGW-U is restarted or down.

The notification message carries abnormal indication information, and the abnormality indication information may be used by the MME to determine that there is no Effect bearer context. The abnormality indication information includes at least one of the following: a first bearer identifier, an identifier of the UE, and a first SGW-U identifier.

It should be noted that the abnormality indication information, the first bearer identifier, the identifier of the UE, the first SGW-U identifier, and the restart or the downtime can be referred to the related description in the embodiment shown in FIG.

Specifically, the first SGW-U identifier may be a device identifier of the first SGW or an IP address of the first SGW-U.

Alternatively, the sending unit 702 is configured to: if the monitoring unit 701 detects that the first SGW-U is abnormal, send a notification message to the MME, where the abnormality may be a restart or a downtime, or the device caused by a serious alarm or the like may not be normal. Work, no longer repeat them.

The device provided by the foregoing embodiment, by monitoring the state of the SGW-U, and sending a notification message to the MME when the first SGW-U is restarted or down, so that the MME can know the abnormal bearer in time, and avoid the MME will invalidate the bearer. The information is provided to other network elements, thereby avoiding the data transmission failure caused by the invalid bearer information, thereby improving the user's feelings.

Optionally, the above apparatus further includes a receiving unit 703;

The receiving unit 703 is configured to receive a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is the invalid bearer context. One of the corresponding bearers;

The sending unit 702 is further configured to send, according to the first modified bearer request message received by the receiving unit 703, a resume bearer request message to the second SGW-U, where the resume bearer request message carries the second bearer identifier;

The receiving unit 703 is further configured to receive a recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and the re-allocated TEID;

The sending unit 702 is further configured to send a first modified bearer response message to the MME, where the first modified bearer response message carries a second bearer identifier and an F-TEID, where the F-TEID includes the reassigned TEID and the second SGW-U IP address.

Alternatively, the above apparatus further includes: a receiving unit 703 and a processing unit 704;

The processing unit 704 is configured to re-allocate the TEID according to the first modified bearer request message received by the receiving unit 703, and notify the second SGW-U of the re-allocated TEID;

The sending unit 703 is further configured to send a first modified bearer response message to the MME, where the first modified bearer response message carries a second bearer identifier and an F-TEID, where the F-TEID includes the reassigned TEID and the second SGW-U IP address.

For details of the abnormal bearer, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein again.

Further, optionally, the sending unit 702 is further configured to send a second modified bearer request message to the PGW-C, where the second modified bearer request message carries the second bearer identifier and the F-TEID;

The receiving unit 703 is further configured to receive a second modified bearer response message sent by the PGW-C.

Further, the receiving unit 703 is further configured to: before receiving the first modified bearer request message sent by the MME, receive the notification message sent by the PGW-C, where the notification message carries the second bearer identifier, the notification message;

The sending unit 702 is further configured to send a DDN message to the MME, where the DDN message carries the second bearer identifier.

Further, the receiving unit 703 is further configured to: before receiving the first modified bearer request message sent by the MME, receive and buffer a downlink data packet sent by the PGW-C, where the downlink data packet carries the second bearer identifier;

Further, the receiving unit 703 is further configured to: before receiving the first modified bearer request message sent by the MME, receive and cache the downlink data packet sent by the second SGW-U, where the downlink data packet carries the second bearer The identifier, wherein the second SGW-U is the first SGW-U after restarting;

The sending unit 702 is further configured to send a DDN message to the MME, where the DDN message carries the second bearer Logo.

As shown in FIG. 8, the embodiment of the present invention provides another apparatus for identifying an invalid bearer context, where the apparatus is an MME, the apparatus includes: a processor 801, a communication interface 802, and a memory 803; and the processor 801 is configured to execute the memory 803. The stored program, which may specifically include the relevant operational steps of the MME in the embodiment shown in FIG. 2, 4 or 5.

The communication interface 802 is configured to receive a notification message sent by the SGW-C, where the notification message carries abnormal indication information.

a memory 803, configured to store a bearer context;

The processor 801 is configured to determine, according to the abnormality indication information received by the communication interface 802, the invalid bearer context stored by the memory 803.

The device provided by the foregoing embodiment receives the notification message sent by the SGW-C, and the notification message carries the abnormal indication information, and determines the invalid bearer context according to the abnormality indication information, so that the abnormal bearer can be known in time, and the invalid bearer information is avoided. Give other network elements, and thus avoid data transmission failure due to invalid bearer information, and improve the user's feelings.

Optionally, the foregoing abnormality indication information includes a first bearer identifier, and the processor 801 is specifically configured to:

Searching for a bearer context stored in the memory 803 according to the first bearer identifier;

Optionally, the foregoing abnormality indication information includes an identifier of the UE, and the processor 801 is specifically configured to:

Searching for a bearer context stored in the memory 803 according to the identifier of the UE;

Optionally, the foregoing abnormality indication information includes a first SGW-U identifier, and the processor 801 is specifically configured to:

The obtained bearer context is determined to be an invalid bearer context.

The related bearer may include a bearer whose first end is the first SGW-U.

Optionally, the processor 801 is further configured to:

Searching for the first SGW-U identifier in the bearer context stored in the memory 803, and obtaining the bearer context including the first SGW-U identifier; or

The related bearer may be a bearer corresponding to the first SGW-U identifier.

Optionally, the communication interface 802 is further configured to send, to the SGW-C, a modify bearer request message, where the modify bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is invalid. One of the bearers corresponding to the bearer context. For details about the abnormal bearer, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein again.

The communication interface 802 is further configured to receive a modify bearer response message sent by the SGW-C, where the modify bearer response message carries the second bearer identifier and the full F-TEID.

The F-TEID includes an IP address of the second SGW-U and a re-allocated TEID.

The processor 801 is further configured to update the invalid bearer context according to the second bearer identifier and the F-TEID received by the communication interface 802.

Optionally, the communication interface 802 is further configured to: receive a TAU message or a service request service request message sent by the first UE, where the TAU message or service request message carries an identifier of the first UE;

The processor 801 is further configured to: if the invalid bearer context of the first UE exists, send a modify bearer request message to the SGW-C through the communication interface 801, where the modify bearer request message carries a third bearer identifier, where the third bearer identifier is used for Indicates an abnormal bearer, where the abnormal bearer is a bearer corresponding to the invalid bearer context of the first UE;

The communication interface 802 is further configured to receive a modified bearer response message sent by the SGW-C, where the modified bearer The response message carries a third bearer identifier and an F-TEID, where the F-TEID includes an IP address of the second SGW-U and a re-allocated TEID;

The processor 801 is further configured to update the invalid bearer context of the first UE stored by the memory 803 according to the third bearer identifier and the F-TEID received by the communication interface 802.

Further, the communication interface 802 is further configured to: before receiving the TAU or service request message sent by the first UE, receive a DDN message sent by the SGW-C, where the DDN message carries a third bearer identifier;

The processor 801 is further configured to send, according to the DDN message, a paging message to the first UE, where the paging message is used to page the first UE.

As shown in FIG. 9, the embodiment of the present invention provides another apparatus for identifying an invalid bearer context, where the apparatus is SGW-C, and the apparatus includes: a processor 901, a communication interface 902, and a memory 903; This executes the program stored in the memory 903. The program may specifically include the relevant operational steps of the SGW-C in the embodiment shown in FIG. 3, 4 or 5.

The processor 901 is configured to monitor a state of the first SGW-U.

The processor 901 is further configured to send a notification message to the MME through the communication interface 902 if the first SGW-U is restarted or down.

The notification message carries abnormal indication information, and the abnormality indication information may be used by the MME to determine an invalid bearer context. The abnormality indication information includes at least one of the following: a first bearer identifier, an identifier of the UE, and a first SGW-U identifier.

Alternatively, the processor 901 is configured to send a notification message to the MME through the communication interface 902 if the first SGW-U is abnormal, the abnormality may be a restart or a downtime, or the device caused by a serious alarm or the like may not work normally. ,No longer.

Optionally, the communication interface 902 is configured to receive a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is One of the bearers corresponding to the invalid bearer context;

The processor 901 is further configured to send, by using the communication interface 902, a recovery bearer request message to the second SGW-U according to the first modified bearer request message received by the communication interface 902, where the resume bearer request message carries the second bearer identifier;

The communication interface 902 is further configured to receive a recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and the re-allocated TEID;

The processor 901 is further configured to send, by using the communication interface 902, a first modified bearer response message, where the first modified bearer response message carries a second bearer identifier and a F-TEID, where the F-TEID includes a reassigned TEID and a second IP address of the SGW-U.

or,

The communication interface 902 is configured to receive a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is the invalid bearer context. One of the corresponding bearers;

The processor 901 is further configured to:

Re-allocating the TEID according to the first modified bearer request message received by the communication interface 902; and notifying the second SGW-U of the re-allocated TEID;

The first modified bearer response message is sent to the MME through the communication interface 902. The first modified bearer response message carries a second bearer identifier and an F-TEID, where the F-TEID includes the reassigned TEID and the IP address of the second SGW-U.

Further, the processor 901 is further configured to send, by using the communication interface 902, a second modified bearer request message to the PGW-C, where the second modified bearer request message carries the second bearer identifier and the F-TEID;

The communication interface 902 is further configured to receive a second modified bearer response message sent by the PGW-C.

Further, optionally, the communication interface 902 is further configured to: before receiving the first modified bearer request message sent by the MME, receive a notification message sent by the PGW-C, where the notification message carries a second bearer identifier, the notification message;

The processor 901 is further configured to send, by using the communication interface 902, a DDN message to the MME, where the DDN message carries a second bearer identifier.

Further, optionally, the communication interface 902 is further configured to: before receiving the first modified bearer request message sent by the MME, receive and buffer the downlink data packet sent by the PGW-C to the memory 903, where the downlink data packet carries the second bearer identifier;

Further, optionally, the communication interface 902 is further configured to: before receiving the first modified bearer request message sent by the MME, receive and cache the downlink data packet sent by the second SGW-U, where the downlink data packet carries the second bearer The identifier, wherein the second SGW-U is the first SGW-U after restarting;

The embodiment of the present invention provides a system for identifying an invalid bearer context, and the system may specifically include the apparatus shown in FIG. 6 and FIG. 7, or the system includes the apparatus shown in FIG. 8 and 9, and details are not described herein.

It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The steps of the foregoing method embodiments; and the foregoing memory includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions described in the foregoing embodiments may be modified or equivalently substituted for some of the technical features. The modifications and substitutions do not depart from the scope of the technical solutions of the embodiments of the present invention.

Claims

A method for identifying an invalid bearer context, the method comprising:

The mobility management entity MME receives the notification message sent by the control plane serving gateway SGW-C, where the notification message carries abnormal indication information;

The MME determines an invalid bearer context according to the abnormality indication information.
The method according to claim 1, wherein the abnormality indication information comprises at least one of: a first bearer identifier, an identifier of a user equipment UE, and a first user plane serving gateway SGW-U identifier, the first The SGW-U identifies the first SGW-U that is used to indicate a restart or downtime.
The method according to claim 2, wherein the first SGW-U is identified as a device identifier of the first SGW-U or an IP address of the first SGW-U.
The method according to claim 2, wherein the abnormality indication information includes the first bearer identifier, and the MME determines an invalid bearer context according to the abnormality indication information, including:

The MME searches for a locally stored bearer context according to the first bearer identifier.

And determining, by the MME, a bearer context of the bearer indicated by the first bearer identifier as the invalid bearer context.
The method according to claim 2, wherein the abnormality indication information includes an identifier of the UE, and the MME determines an invalid bearer context according to the abnormality indication information, including:

The MME searches for a locally stored bearer context according to the identifier of the UE;

The MME determines, as the invalid bearer context, a bearer context of a bearer of the UE indicated by the identifier of the UE.
The method according to claim 2 or 3, wherein the abnormality indication information includes the first SGW-U identifier, and the MME determines an invalid bearer context according to the abnormality indication information, including:

Obtaining, according to the first SGW-U identifier, the bearer context of the related bearer of the first SGW-U;

The MME determines the obtained bearer context as the invalid bearer context.
The method according to claim 6, wherein the MME obtains a bearer context of a bearer associated with the first SGW-U according to the first SGW-U identifier, including:

The MME searches for the first SGW-U identifier in a locally stored bearer context, and obtains a bearer context that includes the first SGW-U identifier; or

The MME determines the related bearer of the first SGW-U according to the preset correspondence between the SGW-U identifier and the bearer, and obtains the bearer context of the related bearer.
The method of any of claims 1-7, wherein the method further comprises:

Sending, by the MME, a modify bearer request message to the SGW-C, where the modify bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer is the invalid bearer context. One of the corresponding bearers;

Receiving, by the MME, a modify bearer response message sent by the SGW-C, where the modify bearer response message carries the second bearer identifier and a full tunnel endpoint identifier F-TEID, where the F-TEID includes a second SGW-U IP address and reassigned tunnel endpoint identifier TEID;

The MME updates the invalid bearer context according to the second bearer identifier and the F-TEID.
The method of any of claims 1-7, wherein the method further comprises:

Receiving, by the MME, a tracking area update TAU message or a service request service request message sent by the first UE, where the TAU message or the service request message carries the identifier of the first UE;

If the invalid bearer context of the first UE is present, send a modify bearer request message to the SGW-C, where the modify bearer request message carries a third bearer identifier, where the third bearer identifier is used to indicate an abnormal bearer. The abnormal bearer is a bearer corresponding to the invalid bearer context of the first UE;

The MME receives the modified bearer response message sent by the SGW-C, where the modified bearer response message carries the third bearer identifier and the F-TEID, and the F-TEID includes the IP address of the second SGW-U and the re- Assigned TEID;

And the MME updates the invalid bearer context of the first UE according to the third bearer identifier and the F-TEID.
The method according to claim 9, wherein before the MME receives the TAU or service request message sent by the first UE, the method further includes:

Receiving, by the MME, a downlink data notification DDN message sent by the SGW-C, where the DDN message carries the third bearer identifier;

And sending, by the MME, a paging message to the first UE according to the DDN message, where the paging message is used to page the first UE.
A method for identifying an invalid bearer context, the method comprising:

The control plane serving gateway SGW-C monitors the state of the first user plane serving gateway SGW-U;

If the first SGW-U is restarted or down, the SGW-C sends a notification message to the mobility management entity MME, where the notification message carries abnormal indication information, and the abnormality indication information is used by the MME to determine that the MME is invalid. Hosting context.
The method according to claim 11, wherein the abnormality indication information comprises at least one of the following: a first bearer identifier, an identifier of the user equipment, and a first SGW-U identifier.
The method according to claim 12, wherein the first SGW-U is identified as a device identifier of the first SGW or an IP address of the first SGW-U.
The method of any of claims 11-13, wherein the method further comprises:

The SGW-C receives the first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, and the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is One of the bearers corresponding to the invalid bearer context;

The SGW-C sends a recovery bearer request message to the second SGW-U according to the first modified bearer request message, where the resume bearer request message carries the second bearer identifier;

The SGW-C receives the recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and the reassigned tunnel endpoint identifier TEID;

The SGW-C sends a first modified bearer response message to the MME, where the first modified bearer response message carries the second bearer identifier and a full tunnel endpoint identifier F-TEID, where the F-TEID includes Reassigning the TEID and the IP address of the second SGW-U.
The method of any of claims 11-13, wherein the method further comprises:

The SGW-C receives the first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, and the second bearer identifier is used to indicate an abnormal bearer, where the abnormal bearer is One of the bearers corresponding to the invalid bearer context;

The SGW-C re-allocates the TEID according to the first modified bearer request message;

The SGW-C notifies the second SGW-U of the reassigned TEID;

The SGW-C sends a first modified bearer response message to the MME, where the first modified bearer response message carries the second bearer identifier and an F-TEID, where the F-TEID includes the reassigned TEID and The IP address of the second SGW-U.
The method according to claim 14 or 15, wherein the method further comprises:

The SGW-C sends a second modified bearer request message to the control plane packet data gateway PGW-C, where the second modified bearer request message carries the second bearer identifier and the F-TEID;

The SGW-C receives the second modified bearer response message sent by the PGW-C.
The method according to any one of claims 14-16, wherein before the SGW-C receives the first modified bearer request message sent by the MME, the method further includes:

The SGW-C receives the notification message sent by the PGW-C, where the notification message carries the second bearer identifier, where the notification message is used to indicate that downlink data arrives on the bearer indicated by the second bearer identifier;

The SGW-C sends a downlink data notification DDN message to the MME, where the DDN message carries the second bearer identifier.
The method according to any one of claims 14-16, wherein before the SGW-C receives the first modified bearer request message sent by the MME, the method further includes:

The SGW-C receives and buffers a downlink data packet sent by the PGW-C, where the downlink data packet carries the second bearer identifier;

The SGW-C sends a DDN message to the MME, where the DDN message carries the second bearer identifier.
The method according to any one of claims 14-16, wherein before the SGW-C receives the first modified bearer request message sent by the MME, the method further includes:

The SGW-C receives and buffers the downlink data packet sent by the second SGW-U, where the downlink data packet carries the second bearer identifier, and the second SGW-U is the first a SGW-U;

The SGW-C sends a DDN message to the MME, where the DDN message carries the second bearer identifier.
An apparatus for identifying an invalid bearer context, wherein the apparatus is a mobility management entity MME, and the apparatus includes:

a receiving unit, configured to receive a notification message sent by the control plane serving gateway SGW-C, where the notification message carries abnormal indication information;

And a determining unit, configured to determine an invalid bearer context according to the abnormality indication information received by the receiving unit.
The apparatus according to claim 20, wherein the abnormality indication information comprises at least one of: a first bearer identifier, an identifier of a user equipment UE, and a first user plane serving gateway SGW-U identifier, the first The SGW-U identifies the first SGW-U that is used to indicate a restart or downtime.
The apparatus according to claim 21, wherein the first SGW-U is identified as a device identifier of the first SGW-U or an IP address of the first SGW-U.
The device according to claim 21, wherein the abnormality indication information comprises the first bearer identifier, and the determining unit is specifically configured to:

Searching for a locally stored bearer context according to the first bearer identifier;

And determining, by the bearer context of the bearer indicated by the first bearer identifier, the invalid bearer context.
The device according to claim 21, wherein said abnormality indication information comprises The identifier of the UE, the determining unit is specifically configured to:

Finding a locally stored bearer context according to the identifier of the UE;

The bearer context of the bearer of the UE indicated by the identifier of the UE is determined as the invalid bearer context.
The device according to claim 21 or 22, wherein the abnormality indication information comprises the first SGW-U identifier, and the determining unit is specifically configured to:

Obtaining, according to the first SGW-U identifier, a bearer context of the related bearer of the first SGW-U;

Determining the obtained bearer context as the invalid bearer context.
The device according to claim 25, wherein the determining unit is further configured to:

Locating the first SGW-U identifier in a locally stored bearer context, and obtaining a bearer context including the first SGW-U identifier; or

Determining, according to a preset correspondence between the SGW-U identifier and the bearer, the related bearer of the first SGW-U, and obtaining a bearer context of the related bearer.
The device according to any one of claims 20 to 26, wherein the device further comprises a first transmitting unit and a first updating unit;

The first sending unit is configured to send a modify bearer request message to the SGW-C, where the modify bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormal bearer One of the bearers corresponding to the invalid bearer context;

The receiving unit is further configured to receive a modified bearer response message sent by the SGW-C, where the modified bearer response message carries the second bearer identifier and a full tunnel endpoint identifier F-TEID, where the F-TEID includes a second SGW-U IP address and reassigned tunnel endpoint identifier TEID;

The first update unit is configured to update the invalid bearer context according to the second bearer identifier and the F-TEID received by the receiving unit.
The device according to any one of claims 20 to 26, wherein the device further comprises: a second sending unit and a second updating unit;

The receiving unit is further configured to receive a tracking area update TAU message or a service request service request message sent by the first UE, where the TAU message or the service request message carries the identifier of the first UE;

The second sending unit is further configured to: if the invalid bearer context of the first UE exists, send a modify bearer request message to the SGW-C, where the modify bearer request message carries a third bearer identifier, where the The three bearer identifiers are used to indicate an abnormal bearer, where the abnormal bearer is a bearer corresponding to the invalid bearer context of the first UE;

The receiving unit is further configured to receive a modify bearer response message sent by the SGW-C, where the modify bearer response message carries the third bearer identifier and an F-TEID, where the F-TEID includes a second SGW-U IP address and reassigned TEID;

The second update unit is configured to update the invalid bearer context of the first UE according to the third bearer identifier and the F-TEID received by the receiving unit.
The device of claim 28, wherein

The receiving unit is further configured to: before receiving the TAU or service request message sent by the first UE, receive a downlink data notification DDN message sent by the SGW-C, where the DDN message carries the third bearer identifier;

The second sending unit is further configured to send, according to the DDN message received by the receiving unit, a paging message to the first UE, where the paging message is used to page the first UE.
An apparatus for identifying an invalid bearer context, wherein the apparatus is a control plane serving gateway SGW-C, and the apparatus includes:

a monitoring unit, configured to monitor a state of the first user plane serving gateway SGW-U;

a sending unit, configured to send a notification message to the mobility management entity MME, if the monitoring unit detects that the first SGW-U is restarted or down, the notification message carries abnormal indication information, where the abnormality indication information is used by The invalid bearer context is determined by the MME.
The apparatus according to claim 30, wherein the abnormality indication information comprises at least one of the following: a first bearer identifier, an identifier of the user equipment, and the first SGW-U identifier.
The apparatus according to claim 31, wherein the first SGW-U is identified as a device identifier of the first SGW or an IP address of the first SGW-U.
Apparatus according to any one of claims 30 to 32, wherein the apparatus further comprises a receiving unit;

The receiving unit is configured to receive a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormality is Carrying one of the bearers corresponding to the invalid bearer context;

The sending unit is further configured to send, according to the first modified bearer request message received by the receiving unit, a recovery bearer request message to the second SGW-U, where the resume bearer request message carries the second bearer identifier ;

The receiving unit is further configured to receive a recovery bearer response message sent by the second SGW-U, where the recovery bearer response message carries the second bearer identifier and a reassigned tunnel endpoint identifier TEID;

The sending unit is further configured to send a first modified bearer response message to the MME, where the first modified bearer response message carries the second bearer identifier and a full tunnel endpoint identifier F-TEID, the F-TEID The redistributed TEID and the IP address of the second SGW-U are included.
The device according to any one of claims 30 to 32, further comprising: a receiving unit and a processing unit;

The receiving unit is configured to receive a first modified bearer request message sent by the MME, where the first modified bearer request message carries a second bearer identifier, where the second bearer identifier is used to indicate an abnormal bearer, and the abnormality is Carrying one of the bearers corresponding to the invalid bearer context;

The processing unit is configured to re-allocate the TEID according to the first modified bearer request message, and notify the second SGW-U of the re-allocated TEID;

The sending unit is further configured to send a first modified bearer response message to the MME, where the first modified bearer response message carries the second bearer identifier and an F-TEID, where the F-TEID includes the reallocation TEID and the IP address of the second SGW-U.
A device according to claim 33 or 34, wherein

The sending unit is further configured to send a second modified bearer request message to the control plane packet data gateway PGW-C, where the second modified bearer request message carries the second bearer identifier and the F-TEID;

The receiving unit is further configured to receive a second modified bearer response message sent by the PGW-C.
Apparatus according to any one of claims 33 to 35, wherein

The receiving unit is further configured to: before receiving the first modified bearer request message sent by the MME, receive a notification message sent by the PGW-C, where the notification message carries the second bearer identifier, where the notification message is used by the And indicating that downlink data arrives on the bearer indicated by the second bearer identifier;

The sending unit is further configured to send a downlink data notification DDN message to the MME, where the DDN message carries the second bearer identifier.
Apparatus according to any one of claims 33 to 35, wherein

The receiving unit is further configured to: before receiving the first modified bearer request message sent by the MME, receive and cache a downlink data packet sent by the PGW-C, where the downlink data packet carries the second bearer identifier;

The sending unit is further configured to send a DDN message to the MME, where the DDN message carries the second bearer identifier.
Apparatus according to any one of claims 33 to 35, wherein

The receiving unit is further configured to: before receiving the first modified bearer request message sent by the MME, receive and cache a downlink data packet sent by the second SGW-U, where the downlink data packet carries the second Carrying the identifier, the second SGW-U is the first SGW-U after restarting;

The sending unit is further configured to send a DDN message to the MME, where the DDN message carries the second bearer identifier.