WO2020200136A1

WO2020200136A1 - Gateway selection system and method

Info

Publication number: WO2020200136A1
Application number: PCT/CN2020/081939
Authority: WO
Inventors: 龙思锐
Original assignee: 华为技术有限公司
Priority date: 2019-03-29
Filing date: 2020-03-28
Publication date: 2020-10-08
Also published as: CN111757401B; CN111757401A

Abstract

Disclosed in embodiments of the present application are a gateway selection system and method. The gateway selection system comprises an MME, a plurality of SGW-Cs and a plurality of SGW-Us. A first SGW-C is configured to send an identifier of a first SGW-U to the MME when detecting that an anomaly occurs in the first SGW-U, the first SGW-C being one of the plurality of SGW-Cs and the first SGW-U being one of the plurality of SGW-Us docked with the first SGW-C. The MME is configured to receive the identifier of the first SGW-U from the first SGW-C, to determine, according to the identifier of the first SGW-U, a first session affected by the first SGW-U, and to reselect a non-faulted second SGW-C for the first session. The second SGW-C is configured to reselect a non-faulted second SGW-U for the first session. On the basis of the system, a non-faulted second SGW-U can be reselected for the first session.

Description

A gateway selection system and method

Technical field

This application relates to the field of communication technology, and in particular to a gateway selection system and method.

Background technique

The 3rd generation partnership project (3rd generation partnership project, 3GPP) standard working group began research on EPS (evolved packet system, evolved packet system) from R8. The entire EPS system can be divided into two parts: the wireless access network and the core network. In the core network, it includes a mobility management entity (MME), a serving gateway (serving gateway, S-GW), a packet data gateway (PDN gateway, P-GW), etc. With the emergence of software-defined network (SDN) technology, the separation of CU (control plane and user plane) has gradually become the development direction of mobile networks. 3GPP proposed the LTE architecture study of CU separation in the Release 13 stage. As shown in Figure 1, under the CU separation architecture, the original PGW is split into a packet data gateway control plane function entity (PDN gateway control plane function, PGW-C) and a packet data gateway user plane function entity (PDN gateway user plane function) , PGW-U) two functional entities, the original SGW is split into a Serving Gateway Control plane function entity (Serving Gateway Control plane function, SGW-C) and a Serving Gateway User plane function entity (Serving Gateway User plane function, SGW-U) ) Two functional entities. During deployment, SGW-C and SGW-U may have a one-to-many relationship, and one SGW-C device may correspond to one or more SGW-U devices. Similarly, PGW-C and PGW-U can have a one-to-many relationship, and one PGW-C device may correspond to one or more PGW-U devices.

In actual applications, the SGW-U in the core network may fail or restart. After the SGW-U in the core network fails or restarts, services will be interrupted. Therefore, after the functional entity in the core network fails or restarts, the SGW-U needs to be reselected. How to reselect SGW-U is a problem that needs to be solved urgently.

Summary of the invention

The embodiment of the application provides a gateway selection system and method, which can reselect the SGW-U.

In the first aspect, an embodiment of the present application provides a gateway selection system. The gateway selection system includes a mobility management entity MME, multiple serving gateway control plane function entities SGW-C, and multiple serving gateway user plane function entities SGW-U, Wherein: the first SGW-C is used to send the identifier of the first SGW-U to the MME when it is detected that the first SGW-U is abnormal, and the first SGW-C is one of the multiple SGW-Cs -C, the first SGW-U is the SGW-U docked with the first SGW-C among the multiple SGW-Us; the MME is used to receive the identity of the first SGW-U from the first SGW-C; MME, It is also used to determine the first session affected by the first SGW-U according to the identifier of the first SGW-U, and to reselect the second SGW-C that has not failed for the first session; the second SGW-C is used to One session reselects the second SGW-U that has not failed. Based on the system described in the first aspect, the MME can reselect a second SGW-C that has not failed for the first session, and the second SGW-C can reselect a second SGW-U that has not failed for the first session. In this way, the second SGW-C and the second SGW-U can subsequently provide services for the first session.

In a specific design, the MME is also used to record the identity of the SGW-U used in the session; the MME determines the identity of the first session affected by the first SGW-U according to the identity of the first SGW-U The specific implementation is as follows: the MME determines that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U. Based on this specific design, the MME can accurately determine the first session affected by the first SGW-U.

In a specific design, the specific implementation manner for the MME to reselect the second SGW-C that has not failed for the first session is: when the MME receives the uplink signaling of the first session, the MME reselects the failed SGW-C for the first session. The second SGW-C that failed. In this specific design, when the MME receives the uplink signaling of the first session, it can trigger the reselection of the SGW-C for the corresponding session, and this specific design is beneficial for timely restoration of emergency services.

In a specific design, the gateway selection system also includes multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user plane functional entities PGW-U. Among them: the first PGW-C uses After receiving the identifier of the abnormal first SGW-U from the first PGW-U or the first SGW-C, the first PGW-C is the PGW-C that is docked with the first SGW-C among the plurality of PGW-Cs , The first PGW-U is the PGW-U that is docked with the first SGW-U and the first PGW-C among the plurality of PGW-Us; the first PGW-C is also used to identify the first SGW-U Determine the second session affected by the first SGW-U; the first PGW-C is also used to send a first message to the MME when the downlink signaling of the second session is received, and the first message is used to trigger the MME to be the first The second session reselects a non-faulty SGW-C; the MME is also used to receive the first message from the first PGW-C, and reselect a non-failed third SGW-C for the second session according to the first message; The third SGW-C is used to reselect a third SGW-U that has not failed for the second session. Through this specific design, the downlink signaling sent by the network side can trigger the reselection of the SGW-U for the session affected by the abnormal SGW-U in a timely manner, which is conducive to timely restoration of the affected services.

In a specific design, the first SGW-C is also used to send the identification of the SGW-U used in the session to the first PGW-C; the first PGW-C is also used to receive from the first SGW-C The ID of the SGW-U used in the session, and the ID of the SGW-U corresponding to the session is recorded in the session; the first PGW-C determines the ID of the second session affected by the first SGW-U according to the ID of the first SGW-U The specific implementation is as follows: the first PGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U. Based on this specific design, the first PGW-C can accurately determine the first session affected by the first SGW-U.

In a specific design, the gateway selection system also includes multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user plane functional entities PGW-U. Among them: the first SGW-C, and It is used to determine the second session affected by the first SGW-U when the abnormality of the first SGW-U is detected; the first PGW-C is used to receive the first signaling corresponding to the second session, and according to the first The signaling sends the second signaling corresponding to the second session to the first SGW-C. The first PGW-C is the PGW-C that is connected to the first SGW-C among the multiple PGW-Cs; the first SGW-C also Used to receive the second signaling from the first PGW-C and send a response to the second signaling to the first PGW-C. The response of the second signaling carries the reason for indicating that the context of the second session is not found Value; the first PGW-C is also used to receive the response of the second signaling from the first SGW-C, and send a first message to the MME, the first message is used to trigger the MME to reselect a non-faulty for the second session SGW-C; MME, also used to receive the first message from the first PGW-C, and according to the first message for the second session to re-select a third SGW-C that has not failed; the third SGW-C, used Reselect the third SGW-U that has not failed for the second session. Through this specific design, it is possible to trigger the reselection of the SGW-U for the session affected by the abnormal SGW-U in a timely manner through the signaling sent by the network side, which is conducive to timely restoration of the affected services.

In a specific design, the first SGW-C is also used to record the identification of the SGW-U used in the session; the first SGW-C determines the specific details of the second session affected by the first SGW-U The implementation manner is: the first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U. Based on this specific design, the first SGW-C can accurately determine the first session affected by the first SGW-U.

In a specific design, the first SGW-C is also used to delete the second session after receiving the dedicated bearer creation request corresponding to the second session. Since the SGW-C needs to be re-selected for the second session, the retention of the second session in the first SGW-C has no effect, and the first SGW-C needs to delete the second session.

In a specific design, the gateway selection system also includes multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user plane functional entities PGW-U, where: the first PGW-U uses When the abnormality of the first SGW-U is detected, the third session affected by the first SGW-U is determined, and the first PGW-U is the PGW-U docking with the first SGW-U among the plurality of PGW-Us. U; The first PGW-U is also used to send a notification message to the first PGW-C when receiving a downlink data packet of the third session, and the notification message is used to notify the third session that the downlink data packet is received. One PGW-C is the PGW-C that is docked with the first PGW-U among the multiple PGW-Cs; the first PGW-C is also used to receive notification messages from the first PGW-U and send a second message to the MME , The second message is used to trigger the MME to reselect a non-faulty SGW-C for the third session; the MME is also used to receive the second message from the PGW-C, and reselect a non-failed SGW-C for the third session according to the second message The failed fourth SGW-C; the fourth SGW-C is used to reselect the unfailed fourth SGW-U for the third session. Through this specific design, the downlink data message sent by the network side can trigger the reselection of the SGW-U for the session affected by the abnormal SGW-U in a timely manner, which is beneficial to timely restoration of the affected services.

In a specific design, the first PGW-U is also used to record the identification of the SGW-U used in the session; the first PGW-U determines the specific details of the third session affected by the first SGW-U The implementation manner is: the first PGW-U determines that the session with the identifier of the first SGW-U in the session is the third session affected by the first SGW-U. Based on this specific design, the first PGW-U can accurately determine the first session affected by the first SGW-U.

In the second aspect, an embodiment of the present application provides a gateway selection method, the method includes: the first serving gateway control plane function entity SGW-C detects that the first serving gateway user plane function entity docked with the first SGW-C When the SGW-U is abnormal, it sends the identity of the first SGW-U to the mobility management entity MME; the MME receives the identity of the first SGW-U from the first SGW-C, and determines the identity of the first SGW-U according to the identity of the first SGW-U. The first session affected by the SGW-U; the MME re-selects the second SGW-C that has not failed for the first session; the second SGW-C re-selects the second SGW-U that has not failed for the first session.

In a specific design, the MME records the identification of the SGW-U used by the session in the session; the specific implementation manner for the MME to determine the first session affected by the first SGW-U according to the identification of the first SGW-U is: The MME determines that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U.

In a specific design, the specific implementation manner for the MME to reselect the second SGW-C that is not failed for the first session is: when the MME receives the service request of the first session, the MME reselects the non-failed second SGW-C for the first session The second SGW-C.

In a specific design, the method further includes the following steps: the first PGW-C receives the identifier of the abnormal first SGW-U from the first PGW-U or the first SGW-C, and the first PGW-C Is a PGW-C docked with the first SGW-C, the first PGW-U is a PGW-U docked with the first SGW-U and the first PGW-C; the first PGW-C is based on the first SGW-U Identify the second session affected by the first SGW-U; when the first PGW-C receives the downlink signaling of the second session, it sends a first message to the MME, and the first message is used to trigger the MME to be the second session Reselect a non-faulty SGW-C; MME receives the first message from the first PGW-C, and selects a non-failed third SGW-C for the second session according to the first message; the third SGW-C is the first The second session reselects the third SGW-U that has not failed.

In a specific design, the method further includes the following steps: the first SGW-C sends to the first PGW-C the identifier of the SGW-U used in the session; the first PGW-C receives the session from the first SGW-C The identifier of the SGW-U used, and the identifier of the SGW-U corresponding to the session is recorded in the session; the first PGW-C determines the specific details of the second session affected by the first SGW-U according to the identifier of the first SGW-U The implementation manner is: the first PGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.

In a specific design, the method further includes the following steps: when the first SGW-C detects that the first SGW-U is abnormal, it determines the second session affected by the first SGW-U; the first PGW-C Receive the first signaling corresponding to the second session, and send the second signaling corresponding to the second session to the first SGW-C according to the first signaling. The first PGW-C is the PGW that interfaces with the first SGW-C -C; the first SGW-C receives the second signaling from the first PGW-C, and sends a response to the second signaling to the first PGW-C, and the response of the second signaling carries a response to indicate that the second signaling is not found The reason value of the context of the second session; the first PGW-C receives the response of the second signaling from the first SGW-C, and sends a first message to the MME, which is used to trigger the MME to reselect one for the second session The non-faulty SGW-C; the MME receives the first message from the first PGW-C, and re-selects a third SGW-C for the second session based on the first message; the third SGW-C is the second session Reselect the third SGW-U that has not failed.

In a specific design, the first SGW-C records the identification of the SGW-U used by the session in the session; the specific implementation manner for the first SGW-C to determine the second session affected by the first SGW-U is: The first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.

In a specific design, the first SGW-C deletes the second session after receiving the dedicated bearer creation request corresponding to the second session.

In a specific design, the method further includes the following steps: when the first PGW-U detects that the first SGW-U is abnormal, it determines the third session affected by the first SGW-U, and the first PGW-U U is the PGW-U docked with the first SGW-U; when the first PGW-U receives the downlink data message of the third session, it sends a notification message to the first PGW-C, and the notification message is used to notify the third session Receiving a downlink data message, the first PGW-C is the PGW-C docking with the first PGW-U; the first PGW-C receives the notification message from the first PGW-U and sends a second message to the MME, The second message is used to trigger the MME to reselect a non-faulty SGW-C for the third session; the MME receives the second message from the PGW-C, and selects a non-failed fourth SGW for the third session according to the second message -C; the fourth SGW-C re-selects the unfaulted fourth SGW-U for the third session.

In a specific design, the first PGW-U may also record the identification of the SGW-U used by the session in the session; the first PGW-U determines the specific implementation of the third session affected by the first SGW-U It is: the first PGW-U determines that the session with the identity of the first SGW-U in the session is the third session affected by the first SGW-U.

Based on the same inventive concept, the beneficial effects of the second aspect or the specific design of the second aspect can be referred to the beneficial effects of the above-mentioned first aspect or the specific design of the first aspect, and the repetition will not be repeated.

In a third aspect, an embodiment of the present application provides a gateway selection method, the method includes: a mobility management entity MME receives an abnormal first serving gateway user plane function entity SGW-C from a first serving gateway control plane function entity SGW-C The identifier of U, the first SGW-C is docked with the first SGW-U; the MME determines the first session affected by the first SGW-U according to the identifier of the first SGW-U; the MME re-selects no failure for the first session The second SGW-C.

In a specific design, the MME may also record the identification of the SGW-U corresponding to the session in the session; the specific implementation manner of the MME determining the first session affected by the first SGW-U according to the identification of the first SGW-U is as follows: : The MME determines that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U.

In a specific design, the specific implementation manner for the MME to reselect the second SGW-C that has not failed for the first session is: when the MME receives the uplink signaling of the first session, the MME reselects the failed SGW-C for the first session. The second SGW-C that failed.

Based on the same inventive concept, the beneficial effects of the third aspect or the specific design of the third aspect can be referred to the beneficial effects of the above-mentioned first aspect or the specific design of the first aspect, and the repetition will not be repeated.

In a fourth aspect, an embodiment of the present application provides a gateway selection method. The method includes: a first packet data network gateway control plane function entity PGW-C from the first packet data network gateway user plane function entity PGW-U or the first The serving gateway control plane functional entity SGW-C receives the identifier of the abnormal first serving gateway user plane functional entity SGW-U, the first PGW-C is docked with the first PGW-U, and the first PGW-C is connected to The first SGW-C is docked, the first SGW-U is docked with the first PGW-U, and the first SGW-U is docked with the first SGW-C; the first PGW-C is based on the first SGW-U The identifier determines the second session affected by the first SGW-U; when the first PGW-C receives the downlink signaling of the second session, it sends a first message to the mobility management entity MME, which is used to trigger the MME to be The second session selects a non-faulty SGW-C again.

In a specific design, the first PGW-C may also receive the identification of the SGW-U used in the session from the first SGW-C; the first PGW-C may also record the SGW-U used in the session in the session The first PGW-C determines the second session affected by the first SGW-U according to the identity of the first SGW-U: The first PGW-C determines that the session has the identity of the first SGW-U The session at is the second session affected by the first SGW-U.

Based on the same inventive concept, the beneficial effects of the specific design of the fourth aspect or the fourth aspect can be referred to the beneficial effects of the specific design of the above-mentioned first aspect, and the repetition will not be repeated.

In a fifth aspect, an embodiment of the present application provides a gateway selection method. The method includes: when the first serving gateway control plane function entity SGW-C detects that the connected first serving gateway user plane function entity SGW-U is abnormal, The first SGW-C determines the second session affected by the first SGW-U; the first SGW-C receives the second signaling corresponding to the second session from the first packet data network gateway control plane function entity PGW-C; first The SGW-C sends a response of the second signaling to the first PGW-C, and the response of the second signaling carries a cause value indicating that the context of the second session is not found.

In a specific design, the first SGW-C may also record the identification of the SGW-U used by the session in the session; the first SGW-C determines the specific implementation of the second session affected by the first SGW-U This is: the first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.

In a specific design, after receiving the dedicated bearer creation request corresponding to the second session, the first SGW-C deletes the second session.

Based on the same inventive concept, the beneficial effects of the specific design of the fifth aspect or the fifth aspect can be referred to the beneficial effects of the specific design of the above-mentioned first aspect, and the repetition will not be repeated.

In a sixth aspect, an embodiment of the present application provides a gateway selection method. The method includes: a first packet data network gateway control plane function entity PGW-C receives first signaling; and the first PGW-C receives first signaling according to the first signaling Send the second signaling to the first serving gateway control plane functional entity SGW-C; the first PGW-C receives the response of the second signaling from the first SGW-C, and the response of the second signaling carries the indication The reason value of the second session context is not found. The second session is a session in the first SGW-C that is affected by the abnormal first serving gateway user plane function entity SGW-U; the first PGW-C sends to the mobility management entity MME The first message, which is used to trigger the MME to re-select a third SGW-C that is not faulty for the second session.

Based on the same inventive concept, the beneficial effects of the sixth aspect can be referred to the beneficial effects of the specific design of the first aspect described above, and the repetition will not be repeated.

In a seventh aspect, an embodiment of the present application provides a gateway selection method. The method includes: the first packet data network gateway user plane function entity PGW-U detects that the connected first serving gateway user plane function entity SGW-U is abnormal When the first PGW-U determines the third session that is affected by the first SGW-U; when the first PGW-U receives the downlink data packet of the third session, it reports to the control plane function entity of the first packet data network gateway that is connected The PGW-C sends a notification message, which is used to notify the third session that the downlink data packet is received.

Based on the same inventive concept, the beneficial effects of the specific design of the seventh aspect or the seventh aspect may refer to the beneficial effects of the specific design of the above-mentioned first aspect, and the repetition will not be repeated.

In an eighth aspect, an embodiment of the present application provides a gateway selection method. The method includes: the first packet data network gateway control plane function entity PGW-C receives a notification message from the first packet data network gateway user plane function entity PGW-U , The notification message is used to notify that the downlink data packet of the third session is received, and the third session is the session in the first PGW-U that is affected by the abnormal first serving gateway user plane function entity SGW-U; the first PGW -C sends a first message to the mobility management entity MME, where the first message is used to trigger the MME to reselect a non-faulty SGW-C for the third session.

Based on the same inventive concept, the beneficial effects of the eighth aspect can be referred to the specific design of the above-mentioned first aspect, and the repetition will not be repeated.

In a ninth aspect, an embodiment of the present application provides a gateway selection system, which includes a mobility management entity MME, multiple serving gateway control plane function entities SGW-C, multiple serving gateway user plane function entities SGW-U, Multiple packet data network gateway control plane function entities PGW-C and multiple packet data network gateway user plane function entities PGW-U, among which: the first PGW-U is used to slave the first PGW-C or the first SGW-U Receive the identifier of the abnormal first SGW-C, where the first PGW-U is one of the multiple PGW-Us, and the first PGW-C and the first SGW-U are respectively the same as the first PGW-U For docking, the first PGW-C and the first SGW-U are respectively docked with the first SGW-C; the first PGW-U is used to determine the first SGW-C affected by the first SGW-C according to the identifier of the first SGW-C The first session; the first PGW-U is also used to send a notification message to the first PGW-C when the downlink data message of the first session is received, the notification message is used to notify that the downlink data of the first session is received Message; the first PGW-C is used to receive the notification message from the first PGW-U and send the first message to the MME, the first message is used to trigger the MME to reselect a non-faulty SGW-C for the first session ; MME is also used to receive the first message from the first PGW-C, and reselect a second SGW-C that is not faulty for the first session according to the first message. Based on the method described in the ninth aspect, the downlink data message sent by the network side can trigger the reselection of the SGW-C for the session affected by the abnormal SGW-C in a timely manner, which is conducive to timely restoration of the affected services.

In a specific design, the first PGW-C is also used to send the identification of the SGW-C used in the session to the first PGW-U; the first PGW-U is also used to receive from the first PGW-C The identification of the SGW-C used in the session, and the identification of the SGW-C used in the session is recorded in the session; the first PGW-U determines the first session affected by the first SGW-C according to the identification of the first SGW-C The specific implementation manner is: the first PGW-U determines that the session with the identifier of the first SGW-C in the session is the first session affected by the first SGW-C. Based on this specific design, the first PGW-U can accurately determine the first session affected by the first SGW-C.

In a tenth aspect, an embodiment of the present application provides a gateway selection method. The method includes: a first packet data network gateway user plane function entity PGW-U from the first packet data network gateway control plane function entity PGW-C or the first The serving gateway user plane function entity SGW-U receives the identifier of the first serving gateway control plane function entity SGW-C that is abnormal, and the first PGW-C and the first SGW-U are respectively connected to the first PGW-U, and the first PGW -C and the first SGW-U are respectively connected to the first SGW-C; the first PGW-U determines the first session affected by the first SGW-C according to the identification of the first SGW-C; the first PGW-U is receiving When the downlink data message of the first session is reached, a notification message is sent to the first PGW-C, and the notification message is used to notify the reception of the downlink data message of the first session; the first PGW-C receives the first PGW-U Notify the message and send a first message to the MME. The first message is used to trigger the MME to re-select a non-faulty SGW-C for the first session; the MME receives the first message from the first PGW-C, and then according to the first message Reselect a second SGW-C that has not failed for the first session.

In a specific design, the method may further include the following steps: the first PGW-C sends to the first PGW-U the identification of the SGW-C used in the session; the first PGW-U receives from the first PGW-C The identifier of the SGW-C used in the session; the identifier of the SGW-C used by the first PGW-U to record the session in the session; the first PGW-U determines that it is affected by the first SGW-C according to the identifier of the first SGW-C The specific implementation of the first session is: the first PGW-U determines that the session with the identifier of the first SGW-C in the session is the first session affected by the first SGW-C.

Based on the same inventive concept, the beneficial effects of the specific design of the tenth aspect or the tenth aspect may refer to the beneficial effects of the specific design of the ninth aspect or the ninth aspect, and the repetition will not be repeated.

In an eleventh aspect, an embodiment of the present application provides a gateway selection method. The method includes: a first packet data network gateway user plane function entity PGW-U obtains from the first packet data network gateway control plane function entity PGW-C or A serving gateway user plane function entity SGW-U receives the identifier of the abnormal first serving gateway control plane function entity SGW-C, and the first PGW-C and the first SGW-U are connected to the first PGW-U respectively, The first PGW-C and the first SGW-U are respectively docked with the first SGW-C; the first PGW-U determines the first session affected by the first SGW-C according to the identifier of the first SGW-C; When a PGW-U receives the downlink data message of the first session, it sends a notification message to the first PGW-C, where the notification message is used to notify the reception of the downlink data message of the first session.

In a specific design, the first PGW-U may also receive the identification of the SGW-C used in the session from the first PGW-C; the first PGW-U may also record the SGW-C used in the session in the session. The identification of C; the first PGW-U determines the first session affected by the first SGW-C according to the identification of the first SGW-C: the first PGW-U determines that the session has the first SGW-C The identified session is the first session affected by the first SGW-C.

In a twelfth aspect, an embodiment of the present application provides a gateway selection method. The method includes: the first packet data network gateway control plane function entity PGW-C receives a notification from the first packet data network gateway user plane function entity PGW-U Message, the notification message is used to notify that the downlink data packet of the first session is received, the first session is the session in the first PGW-U that is affected by the abnormal first serving gateway control plane function entity SGW-C; the first PGW -C sends a first message to the mobility management entity MME, where the first message is used to trigger the MME to reselect a non-faulty SGW-C for the first session.

In a specific design, when the first PGW-C determines that the first SGW-C is abnormal, it sends the first SGW-C identifier to the first PGW-U.

In a specific design, the first PGW-C sends the identification of the SGW-C corresponding to the session to the first PGW-U.

Based on the same inventive concept, the beneficial effects of the specific design of the eleventh aspect or the eleventh aspect may refer to the beneficial effects of the specific design of the ninth aspect or the ninth aspect, and the repetition will not be repeated.

In the thirteenth aspect, the embodiments of the present application provide a service recovery system. The service recovery system includes a mobility management entity MME, multiple serving gateway control plane function entities SGW-C, multiple serving gateway user plane function entities SGW-U, Multiple packet data network gateway control plane function entities PGW-C and multiple packet data network gateway user plane function entities PGW-U, among which: the first SGW-C is used to slave the first PGW-C or the first SGW-U Receive the identifier of the first PGW-U that is abnormal, the first SGW-C is one of the plurality of SGW-Cs, and the first PGW-C is the PGW of the plurality of PGW-Cs that is connected to the first SGW-C -C, the first SGW-U is the SGW-U docked with the first SGW-C among the plurality of SGW-Us, and the first PGW-U is docked with the first PGW-C and the first SGW-C respectively; SGW-C is used to send the identifier of the abnormal first PGW-U to the MME; MME is used to receive the identifier of the first PGW-U from the first SGW-C, and determine the recipient according to the identifier of the first PGW-U The first session affected by the first PGW-U; the MME is also used to delete the first session and instruct the user equipment corresponding to the first session to re-establish a packet data network PDN connection. Based on the system described in the thirteenth aspect, the affected business can be restored.

In a specific design, the MME is also used to record the identity of the PGW-U used in the session; the MME determines the specific identity of the first session affected by the first PGW-U according to the identity of the first PGW-U The implementation manner is: the MME determines that the session with the identifier of the first PGW-U in the session is the first session affected by the first PGW-U. Based on this specific design, the MME can accurately determine the first session affected by the first PGW-U.

In a specific design, the MME deletes the first session and instructs the user equipment corresponding to the first session to re-establish a packet data network PDN connection. The specific implementation is: when the MME receives the uplink signaling of the first session To delete the first session, and instruct the user equipment corresponding to the first session to re-establish a PDN connection. In this specific design, when the MME receives the signaling sent by the user equipment side, it can trigger the restoration of the service corresponding to the signaling. Therefore, this design facilitates the timely restoration of emergency services.

In a specific design, the first SGW-U is used to determine the second session affected by the first PGW-U when it is determined that the first PGW-U is abnormal; the first SGW-U is used to When the uplink data message of the second session arrives, a notification message is sent to the first SGW-C, and the notification message is used to notify the second session that the uplink data message is received; the first SGW-C is used to send the message from the first SGW-C. U receives the notification message; the first SGW-C is also used to delete the second session and instruct the user equipment corresponding to the second session to re-establish a PDN connection. Based on this design, when the first SGW-U receives the uplink data message of the second session, it can trigger the service recovery of the second session in time.

In a specific design, the first SGW-U is also used to record the identification of the PGW-U used in the session; the first SGW-U determines the specific details of the second session affected by the first PGW-U The implementation manner is: the first SGW-U determines that the session with the identity of the first PGW-U in the session is the second session affected by the first PGW-U. Based on this specific design, the first SGW-U can accurately determine the second session affected by the first PGW-U.

In a specific design, the first PGW-C is used to determine the third session affected by the first PGW-U when an abnormality of the first PGW-U is detected; the first PGW-C is also used for When the downlink signaling of the third session is received, the third session is deleted, and the user equipment corresponding to the third session is instructed to re-establish the PDN connection. Based on this design, the first PGW-C can trigger the service recovery of the third session in time when receiving the signaling of the third session.

In a specific design, the first PGW-C is also used to record the identification of the PGW-U used in the session; the first PGW-C determines the specific details of the third session affected by the first PGW-U The implementation manner is: the first PGW-C determines that the session with the identifier of the first PGW-U in the session is the third session affected by the first PGW-U. Based on this specific design, the first PGW-C can accurately determine the third session affected by the first PGW-U.

In a specific design, the first PGW-C is also used to send a message to the second PGW-U used in the fourth session according to the signaling of the fourth session when the signaling of the fourth session is received; The first PGW-C is also used to, after retransmitting the message to the second PGW-U, if the first PGW-C does not receive a response message for the message within a preset time period, delete the fourth session and indicate the first The user equipment corresponding to the fourth session re-establishes the PDN connection. Based on this specific design, when the first PGW-C does not sense the abnormality of the second PGW-U in time, the services affected by the second PGW-U can be restored in time.

In a fourteenth aspect, an embodiment of the present application provides a service recovery method. The method includes: the first serving gateway control plane function realizing SGW-C from the first packet data network gateway control plane function entity PGW-C or the first service The gateway user plane function entity SGW-U receives the identifier of the abnormal first packet data network gateway user plane function entity PGW-U. The first PGW-C is connected to the first SGW-C, and the first SGW-U is connected to the first SGW-U docked with SGW-C, the first PGW-U is docked with the first PGW-C, and the first PGW-U is docked with the first SGW-U; the first SGW-C sends the abnormal first to the mobility management entity MME A PGW-U identifier; the MME receives the identifier of the first PGW-U from the first SGW-C; the MME determines the first session affected by the first PGW-U according to the identifier of the first PGW-U; the MME responds to the first session Delete, and instruct the user equipment corresponding to the first session to re-establish a packet data network PDN connection.

In a specific design, the MME records the identification of the PGW-U used by the session in the session; the specific implementation manner for the MME to determine the first session affected by the first PGW-U according to the identification of the first PGW-U is: The MME determines that the session with the identifier of the first PGW-U in the session is the first session affected by the first PGW-U.

In a specific design, the MME deletes the first session and instructs the user equipment corresponding to the first session to re-establish a packet data network PDN connection. The specific implementation is: when the MME receives the uplink signaling of the first session To delete the first session, and instruct the user equipment corresponding to the first session to re-establish a PDN connection.

In a specific design, the method further includes the following steps: when the first SGW-U determines that the first PGW-U is abnormal, it determines the second session affected by the first PGW-U; When receiving the uplink data packet of the second session, send a notification message to the first SGW-C, the notification message is used to notify the second session that the uplink data packet is received; the first SGW-C receives the uplink data packet from the first SGW-U Notification message; the first SGW-C deletes the second session and instructs the user equipment corresponding to the second session to re-establish a PDN connection.

In a specific design, the first SGW-U can also record the identification of the PGW-U used by the session in the session; the first SGW-U determines the specific implementation of the second session affected by the first PGW-U It is: the first SGW-U determines that the session with the identity of the first PGW-U in the session is the second session affected by the first PGW-U.

In a specific design, the method further includes the following steps: when the first PGW-C detects that the first PGW-U is abnormal, it determines the third session affected by the first PGW-U; the first PGW-C When the downlink signaling of the third session is received, the third session is deleted, and the user equipment corresponding to the third session is instructed to re-establish the PDN connection.

In a specific design, the first PGW-C records the identification of the PGW-U used by the session in the session; the specific implementation manner for the first PGW-C to determine the third session affected by the first PGW-U is: The first PGW-C determines that the session with the identifier of the first PGW-U in the session is the third session affected by the first PGW-U.

In a specific design, when the first PGW-C receives the signaling of the fourth session, it sends a message to the second PGW-U used in the fourth session according to the signaling of the fourth session; the first PGW-C After C retransmits the message to the second PGW-U, if the first PGW-C does not receive the response message of the message within the preset time period, delete the fourth session and instruct the user equipment corresponding to the fourth session to re-establish PDN connection.

Based on the same inventive concept, the beneficial effects of the specific design of the fourteenth aspect or the fourteenth aspect can be referred to the beneficial effects of the specific design of the above-mentioned thirteenth aspect or the thirteenth aspect, and the repetition will not be omitted. Repeat.

In a fifteenth aspect, an embodiment of the present application provides a service recovery method. The method includes: a mobility management entity MME receives an abnormal first packet data network gateway user plane function from a first serving gateway control plane function entity SGW-C The identity of the entity PGW-U; the MME determines the first session affected by the first PGW-U according to the identity of the first PGW-U; the MME deletes the first session and instructs the user equipment corresponding to the first session to re-establish packet data Network PDN connection.

In a specific design, the MME may also record the identification of the PGW-U used in the session; the MME determines the specific implementation of the first session affected by the first PGW-U according to the identification of the first PGW-U It is: the MME determines that the session with the identifier of the first PGW-U in the session is the first session affected by the first PGW-U.

Based on the same inventive concept, the beneficial effects of the specific design of the fifteenth aspect or the fifteenth aspect may refer to the beneficial effects of the specific design of the thirteenth aspect or the specific design of the thirteenth aspect. Repeat.

In a sixteenth aspect, an embodiment of the present application provides a service recovery method, which includes: when the first serving gateway user plane function entity SGW-U determines that the first packet data network gateway user plane function entity PGW-U is abnormal , Determine the second session affected by the first PGW-U; when the first SGW-U receives the uplink data message of the second session, it sends a notification message to the first serving gateway control plane function entity SGW-C. The message is used to notify the second session that the uplink data packet is received.

Based on the same inventive concept, the beneficial effects of the specific design of the sixteenth aspect or the sixteenth aspect may refer to the beneficial effects of the specific design of the above-mentioned thirteenth aspect, and the repetition will not be repeated.

In a seventeenth aspect, an embodiment of the present application provides a service recovery method. The method includes: the first serving gateway control plane function entity SGW-C receives a notification message from the first serving gateway user plane function entity SGW-U, and the notification message Used to notify the second session that the uplink data packet is received. The second session is the session affected by the abnormal first packet data network gateway user plane function entity PGW-U; the first SGW-C deletes the second session and instructs the second session The user equipment corresponding to the session re-establishes the PDN connection.

Based on the same inventive concept, the beneficial effects of the seventeenth aspect may refer to the specific design of the above-mentioned thirteenth aspect, and the repetition will not be repeated.

In an eighteenth aspect, an embodiment of the present application provides a service recovery method. The method includes: the first packet data network gateway control plane function entity PGW-C detects that the first packet data network gateway user plane function entity PGW-U When an exception occurs, determine the third session affected by the first PGW-U; when the first PGW-C receives the downlink signaling of the third session, delete the third session and instruct the user equipment corresponding to the third session to re-establish PDN connection.

In a specific design, the first PGW-C may also record the identification of the PGW-U used by the session in the session; the first PGW-C determines the specific implementation of the third session affected by the first PGW-U It is: the first PGW-C determines that the session with the identifier of the first PGW-U in the session is the third session affected by the first PGW-U.

Based on the same inventive concept, the beneficial effects of the specific design of the eighteenth aspect or the eighteenth aspect may refer to the beneficial effects of the specific design of the above-mentioned thirteenth aspect, and the repetition will not be repeated.

In a nineteenth aspect, a network device is provided that can execute the above-mentioned third aspect to the eighth aspect, the specific design of the third aspect to the specific design of the eighth aspect, the eleventh aspect, the twelfth aspect, and the third aspect. The specific design of the eleventh aspect, the specific design of the twelfth aspect, the specific design of the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the specific design of the eighteenth aspect. . This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-mentioned functions. The unit can be software and/or hardware. Based on the same inventive concept, the principle and beneficial effects of the root node to solve the problem can be found in the third aspect to the eighth aspect, the specific design of the third aspect to the specific design of the eighth aspect, the eleventh aspect, and the twelfth aspect. Aspect, the specific design of the eleventh aspect, the specific design of the twelfth aspect, the specific design of the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the specific design of the eighteenth aspect The methods and beneficial effects of the items will not be repeated here.

In a twentieth aspect, a network device is provided. The network device includes a processor, a memory, and a communication interface; the processor, the communication interface and the memory are connected; wherein the communication interface may be a transceiver. The communication interface is used to realize communication with other network elements. Wherein, one or more programs are stored in the memory, and the processor calls the programs stored in the memory to implement the third aspect to the eighth aspect, the specific design of the third aspect to the specific design of the eighth aspect , The eleventh aspect, the twelfth aspect, the specific design of the eleventh aspect, the specific design of the twelfth aspect, the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the tenth For the method of any one of the eight aspects of the specific design, the implementation of the network device to solve the problem and the beneficial effects can be referred to the third aspect to the eighth aspect, and the specific design of the third aspect to the eighth aspect. , The eleventh aspect, the twelfth aspect, the specific design of the eleventh aspect, the specific design of the twelfth aspect, the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the tenth The method and beneficial effects of any one of the eight aspects of the specific design will not be repeated here.

In the twenty-first aspect, a computer program product is provided, which when it runs on a computer, causes the computer to execute the above-mentioned third aspect to the eighth aspect, the specific design of the third aspect to the eighth aspect, The eleventh aspect, the twelfth aspect, the specific design of the eleventh aspect, the specific design of the twelfth aspect, the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the eighteenth aspect Any one of the specific design methods.

The twenty-second aspect provides a chip product that implements the above-mentioned third aspect to the eighth aspect, the specific design of the third aspect to the specific design of the eighth aspect, the eleventh aspect, the twelfth aspect, and the The specific design of the eleventh aspect, the specific design of the twelfth aspect, the specific design of the fifteenth aspect to the eighteenth aspect, the specific design of the fifteenth aspect to the specific design of the eighteenth aspect. .

In a twenty-third aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute the aforementioned third to eighth aspects, and Three specific designs ~ eighth specific design, eleventh, twelfth, eleventh specific design, twelfth specific design, fifteenth to tenth Eighth aspect, fifteenth aspect specific design ~ eighteenth aspect specific design method.

Description of the drawings

Fig. 1 is a schematic diagram of an existing communication system;

Figure 2 is a schematic diagram of a communication system provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of a gateway selection method provided by an embodiment of the present application;

4 is a schematic flowchart of another gateway selection method provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of yet another gateway selection method provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart of yet another gateway selection method provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of yet another gateway selection method provided by an embodiment of the present application;

FIG. 8 is a schematic flowchart of a service recovery method provided by an embodiment of the present application;

FIG. 9 is a schematic flowchart of another service recovery method provided by an embodiment of the present application;

FIG. 10 is a schematic flowchart of another service recovery method provided by an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of another terminal device provided by an embodiment of the present application.

detailed description

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the technical solutions of the embodiments of the present invention will be described below with reference to the accompanying drawings.

In order to better understand the embodiments of this application, the following describes the applicable system architecture of the embodiments of this application:

Please refer to FIG. 2, which is a schematic diagram of a communication system provided by an embodiment of the present application. As shown in Figure 2, the communication system includes at least a mobility management entity (MME), multiple serving gateway control plane function entities (serving gateway control plane functions, SGW-C), and multiple serving gateway user plane functions Entity (serving gateway user plane function, SGW-U), multiple packet data network gateway control plane function entities (PDN gateway control plane function, PGW-C), and multiple packet data network gateway user plane function entities (PDN gateway user plane) function, PGW-U). Among them, Figure 2 takes the communication system including 2 SGW-C, 4 SGW-U, 2 PGW-C and 4 PGW-U as an example. Of course, the communication system can also include more SGW-C and SGW -U, PGW-C and PGW-U. Alternatively, the communication system may include less than 4 SGW-Us and less than 4 PGW-Us, which is not limited in the embodiment of the present application.

Among them, one SGW-C can be connected to one or more SGW-Us, and one SGW-U can also be connected to one or more SGW-Cs, and the SGW-C and SGW-U communicate through the Sxa interface. One SGW-C can be connected to one or more PGW-Cs, and one PGW-C can also be connected to one or more SGW-Cs. SGW-C and PGW-C communicate through the S5/8-C interface. A PGW-C can be connected to one or more PGW-Us, and a PGW-U can be connected to one or more PGW-Cs. PGW-C and PGW-U communicate through the Sxb interface. One SGW-U can be connected to one or more PGW-Us, and one PGW-U can also be connected to one or more SGW-Us. The SGW-U and PGW-U communicate through the S5/8-U interface.

Among them, MME can be used for access control, mobility management, attach and detach, session management functions, selection of SGW-C and PGW-C, etc. For other functions and descriptions of the MME, please refer to the descriptions in the relevant 3GPP TS 23.401 and other standards, which will not be repeated here.

Among them, SGW-C is used to manage or select SGW-U, or to implement other non-session-level management functions. PGW-C is used to manage or select PGW-U, or to implement other non-session-level management functions. SGW-U and PGW-U are used for IP packet forwarding, bearer/APN traffic attention, service detection, etc. For other functions and descriptions of SGW-C, PGW-C, SGW-U and PGW-U, please refer to the descriptions in 3GPP TS 23.214 and other standards, which will not be repeated here.

As shown in Figure 2, the communication system may also include an evolved universal mobile telecommunications system territorial radio access network (E-UTRAN) and user equipment (UE). FIG. 2 takes one UE as an example. Of course, the communication system may also include multiple UEs, which is not limited in the embodiment of the present application. Among them, SGW-U and E-UTRAN communicate through the S1-U interface. E-UTRAN communicates with UE through LTE-Uu interface.

Wherein, the above-mentioned E-UTRAN includes access network equipment. The access network device can provide communication coverage for a specific geographic area, and can communicate with user equipment located in the coverage area. The access network device can support communication protocols of different standards or can support different communication modes. For example, the access network equipment may be an evolved base station (evolutional node B, eNB or eNodeB) in an LTE system, or a radio network controller in a cloud radio access network (cloud radio access network, CRAN), or may be The access network equipment in the 5G network, such as gNB, may be a small station, a micro station, or a transmission reception point (TRP), or a relay station, an access point, or a public land mobile network that will evolve in the future. Land mobile network (PLMN) access network equipment, etc.

Among them, the aforementioned UE may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a terminal device, a mobile terminal, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the Internet of Things, virtual reality devices, terminal devices in the fifth generation (5G) network, or Terminal equipment in the future evolving public land mobile network (PLMN).

Among them, the aforementioned MME, SGW-C, SGW-U, PGW-C, and PGW-U are devices in the core network. UE, E-UTRAN, and core network form an evolved packet system (Evolved Packet System, EPS). As shown in Figure 2, the communication system may also include a Packet Data Network (PDN). Among them, PDN and PGW-U communicate through the SGi interface.

In the LTE network, the UE must be connected to at least one PDN to perform data communication. The PDN connection established between the UE and the PDN may also be called a session. In a session, the UE can receive data from the PDN and can also send data to the PDN. The session is carried by EPS to transmit data between the UE and the PDN. The EPS bearer can bear the data of services such as videophone, network video, and VoLTE. If the SGW-U is abnormal, the channel between the UE and the PDN will be interrupted, causing the conversation service to not be able to proceed normally. Therefore, SGW-U needs to be reselected for the affected session.

To this end, embodiments of the present application provide a gateway selection system and method, which can reselect SGW-U for sessions affected by abnormal SGW-U when SGW-U fails. Wherein, the gateway selection system may include the network elements in the aforementioned communication system.

Based on the above communication system, please refer to FIG. 3, which is a schematic flowchart of a gateway selection method provided by an embodiment of the present application. The method described in FIG. 3 is used to reselect the SGW-U in time for the session affected by the abnormal SGW-U when the SGW-U is abnormal. In the method described in FIG. 3, the first session affected by the failed SGW-U is recorded through the MME. The MME can actively reselect the SGW-U for the first session. Alternatively, the MME may initiate the process of reselecting the SGW-U for the first session when receiving the signaling of the first session from the user equipment side. As shown in Figure 3, the gateway selection method includes the following parts 301 to 304, among which:

301. The first SGW-C sends an identification of the first SGW-U to the MME when detecting that the first SGW-U docked with the first SGW-C is abnormal.

In the embodiment of the present application, the first SGW-C is any one SGW-C among the multiple SGW-Cs in the aforementioned gateway selection system. The first SGW-U is any SGW-U among the SGW-Us docked with the first SGW-C. For example, the first SGW-C may be SGW-C1 or SGW-C2 in FIG. 2. When the first SGW-C is SGW-C1, the first SGW-U is SGW-U1 or SGW-U2 in FIG. 2. When the first SGW-C is SGW-C2, the first SGW-U is SGW-U3 or SGW-U4 in FIG. 2.

The identifier of the first SGW-U may be the IP address of the first SGW-U.

The abnormality of the first SGW-U may mean that the first SGW-U fails or the first SGW-U restarts.

The first SGW-C can determine whether the first SGW-U is abnormal through the HeatBeat message of the Sx interface. For example, the first SGW-C may send a HeatBeat request message to the first SGW-U at a preset time period. After receiving the HeatBeat request message, the first SGW-U returns a HeatBeat response message to the first SGW-C. If the first SGW-C does not receive the HeatBeat response message sent by the first SGW-U within the preset time period, the first SGW-C determines that the first SGW-U is faulty. If the first SGW-C receives the HeatBeat response message, but the value of the recovery counter in the HeatBeat response message is different from the value of the recovery counter in the HeatBeat response message received last time, the first SGW-C It is determined that the first SGW-U restarts. If the first SGW-U restarts, the value of the recovery counter in the HeatBeat response message will increase by 1. Therefore, when the first SGW-C detects that the value of the restoration counter in the HeatBeat response message is different from the value of the restoration counter in the HeatBeat response message received last time, the first SGW-C can determine that the first SGW-U A restart occurred.

Of course, the first SGW-C may also determine whether the first SGW-U is abnormal in other ways, which is not limited in the embodiment of the present application.

Wherein, the first SGW-C may send the identity of the first SGW-U to the MME through the existing Node-level Echo message of the agreement. Alternatively, the first SGW-C may send the identification of the first SGW-U to the MME through an existing session-level session management/mobility management message in the agreement. Alternatively, the first SGW-C may also send the identity of the first SGW-U to the MME through a private Node-level message defined outside the protocol.

302. The MME determines the first session affected by the first SGW-U according to the identity of the first SGW-U.

In the embodiment of this application, after the MME receives the identity of the first SGW-U from the first SGW-C, the MME determines the first session affected by the first SGW-U from the sessions included in the MME according to the identity of the first SGW-U . Due to the failure of the first SGW-U, the services using the session in the first SGW-U will be affected. Therefore, the first session affected by the first SGW-U refers to a session using the MME and the first SGW-U.

In a specific design, the MME may record the SGW-U identifier used in the session in the session. The specific implementation manner for the MME to determine the first session affected by the first SGW-U according to the identifier of the first SGW-U is: the MME determines that the session with the identifier of the first SGW-U in the session is affected by the first SGW-U The first conversation. Based on this specific design, the MME can accurately determine the first session affected by the first SGW-U.

For example, session 1, session 2, and session 3 use MME, so there are session 1, session 2, and session 3 in the MME. Session 1 and Session 2 also use SGW-C1, SGW-U1, PGW-C1, and PGW-U1. Session 3 also uses SGW-C2, SGW-U3, PGW-C2, and PGW-U3. Then, the MME will record the identification of SGW-U1 in Session 1 and Session 2, and the identification of SGW-U3 in Session 3. If the first SGW-U is SGW-U1, after receiving the identifier of SGW-U1, the MME searches for the identifier of SGW-U1 in the MME session. The MME finds the identity of SGW-U1 in Session 1 and Session 2. Therefore, the MME determines Session 1 and Session 2 as the first session determined to be affected by SGW-U1.

In the full text of the embodiments of this application, the SGW-U used in the session may also be referred to as the SGW-U where the session is located or the SGW-U corresponding to the session.

In a specific design, after the MME determines the first session affected by the first SGW-U according to the identifier of the first SGW-U, the MME needs to record the first session affected by the first SGW-U so that it can be the first session subsequently. One session reselects the second SGW-C that has not failed. For example, the MME may record the first session affected by the first SGW-U in the following manner: the MME marks the first session. Or, the MME sets a flag bit for the first session. Or, the MME creates a list of sessions affected by the first SGW-U, and adds the first session to the list. For example, after determining that Session 1 and Session 2 are the first sessions affected by SGW-U1, the MME marks Session 1 and Session 2. Or, the MME sets flag bits for session 1 and session 2. Or, the MME adds Session 1 and Session 2 to the list of sessions affected by the first SGW-U.

In a specific design, after the MME reselects the second SGW-C that has not failed for the first session, the MME cancels the recording of the first session. In this way, the MME can subsequently process the service of the first session normally. For example, after the MME re-selects the second SGW-C that has not failed for the first session, the MME cancels the marking of the first session. Or, the MME cancels the flag bit set for the first session. Or, the MME removes the first session from the list of sessions affected by the first SGW-U.

303. The MME reselects a second SGW-C that has not failed for the first session.

In the embodiment of the present application, after determining the first session, the MME re-selects the second SGW-C that has not failed for the first session, so that the subsequent second SGW-C can provide services for the services of the first session. The second SGW-C may be the same as or different from the first SGW-C, which is not limited in the embodiment of the present application.

For example, the first SGW-C is SGW-C1. Session 1 and Session 2 are the first sessions affected by SGW-U1. Then, the MME re-selects the second SGW-C that has not failed for session 1, and reselects the second SGW-C that has not failed for session 2. The second SGW-C may be SGW-C1 or SGW-C2, that is, the MME can select the original SGW-C1 to continue to provide services for the first session or select other unfaulted SGW-C2 to continue to provide services for the first session. The second SGW-C reselected by the MME for session 1 may be the same or different from the second SGW-C reselected for session 2, which is not limited in the embodiment of the present application.

The MME can reselect the second SGW-C that is not faulty for the first session in the following two ways.

Manner 1: There are multiple first sessions that are affected. Even if the MME does not receive the signaling of the first session, the MME can actively reselect the non-failed second SGW-C for the multiple first sessions at a preset rate.

Manner 2: When the MME receives the uplink signaling of the first session, the MME preferentially reselects the second SGW-C that is not faulty for the first session. For example, the uplink signaling may be a service request. For example, the first affected session includes session 1 to session 100, and the MME re-selects the second SGW-C that is not faulty for session 1 to session 100 at a preset rate. When receiving the service request of the session 100 from the user equipment, the MME preferentially selects the second SGW-C that is not faulty for the session 100. Due to the large number of first sessions affected, it will take a long time for the MME to re-select the unfaulted second SGW-C for these 100 sessions in batches, which may cause some emergency services to fail to recover in time. In this specific design, when the MME receives the signaling sent by the user equipment side, it can trigger the reselection of the SGW-C for the corresponding session. Through this specific design, it is beneficial to restore emergency services in time.

304. The second SGW-C reselects a second SGW-U that has not failed for the first session.

In the embodiment of the present application, after the MME reselects the unfaulted second SGW-C for the first session to provide services, the second SGW-C reselects the unfailed second SGW-U for the first session, so that the subsequent second SGW-U -U can provide services for the business of the first session. For example, as shown in Figure 2, SGW-U1 is abnormal, and session 1 in the MME is a session affected by SGW-U1. The MME re-selects the surviving SGW-C2 for session 1. The SGW-C2 reselects the unfaulted SGW-U3 or SGW-U4 to provide services for the first session.

After the MME re-selects the unfaulted second SGW-C for the first session, and after the second SGW-C re-selects the unfaulted second SGW-U for the first session, some related operations are needed to restore the service. For example, after the MME reselects the second SGW-C that has not failed for the first session, the MME may send a create session request to the second SGW-C that has not failed to modify the bearer of the first session. After receiving the session creation request, the second SGW-C sends a modify bearer request to the first PGW-C. Among them, the first PGW-C is the PGW-C docked with the first SGW-C. Specifically, after receiving the bearer modification request, the first PGW-C sends a session modification request (session modification request) to the first PGW-U. Among them, the first PGW-U is the PGW-U docked with the first PGW-C. Specifically, after receiving the session modification request, the first PGW-U updates the tunnel of the S5S8 interface, and sends a session modification response to the first PGW-C. For example, the tunnel may be a user plane general packet radio service tunneling protocol (general packet radio service tunnelling protocol for the user plane, GTPU) tunnel. After receiving the session modification response, the first PGW-C sends a modification bearer response to the second SGW-C. After the second SGW-C receives the modify bearer response, the second SGW-C sends a create session response to the MME.

For another example, after the second SGW-C reselects the unfaulted second SGW-U for the first session, the second SGW-C may also send a packet forwarding control protocol (packet forwarding control protocol, PFCP) Session establishment request to establish a session between the second SGW-C and the second SGW-U. Correspondingly, after receiving the PFCP Session establishment request, the second SGW-U may send a PFCP Session establishment response to the second SGW-C.

After the MME re-selects the unfaulted second SGW-C for the first session, and after the second SGW-C re-selects the unfaulted second SGW-U for the first session, how to restore services can be found in 3GPP TS 23.007, The procedures in 3GPP TS 23.214, 3GPP TS 29.244 and other standards will not be repeated here.

It can be seen that, by implementing the method described in FIG. 3, the MME can reselect the second SGW-C that has not failed for the first session, and the second SGW-C can reselect the second SGW-U that has not failed for the first session. In this way, the second SGW-C and the second SGW-U can subsequently provide services for the first session.

Based on the above communication system, please refer to FIG. 4, which is a schematic flowchart of another gateway selection method provided by an embodiment of the present application. The method described in Figure 4 is used to reselect SGW-U in time for the session affected by the abnormal SGW-U when the SGW-U is abnormal. In the method described in FIG. 4, the second session affected by the failed SGW-U is recorded through the PGW-C. When the PGW-C receives the downlink signaling of the second session, it initiates the process of reselecting the SGW-U for the second session. As shown in Figure 4, the gateway selection method includes the following parts 401 to 405, in which:

401. The first PGW-C receives an identifier of the first SGW-U that is abnormal from the first PGW-U or the first SGW-C.

Wherein, the first SGW-C is any one in the gateway selection system. The first PGW-C is connected to the first PGW-U and the first SGW-C respectively. The first SGW-U is connected to the first PGW-U and the first SGW-C respectively.

For example, as shown in Figure 2, the first SGW-C is SGW-C1, and the first PGW-C is PGW-C1. The first SGW-U is SGW-U1, and the first PGW-U is PGW-U1. The PGW-U1 can detect whether the SGW-U1 is abnormal, and when the SGW-U1 is detected to be abnormal, the SGW-U1 identifier is sent to the PGW-C1 to notify the PGW-C1 of the abnormal SGW-U1. The SGW-C1 may also detect whether the SGW-U1 is abnormal, and when the SGW-U1 is detected to be abnormal, the SGW-U1 identifier is sent to the PGW-C1 to notify the PGW-C1 of the abnormal SGW-U1.

Among them, the first PGW-U can detect whether the first SGW-U is abnormal through the Echo request message. For example, the first PGW-U may send an Echo request message to the first SGW-U at a preset time period. After receiving the Echo request message, the first SGW-U will return an Echo response message to the first PGW-U. If the first PGW-U does not receive the Echo response message sent by the first SGW-U within the preset time period, the first PGW-U determines that the first SGW-U is faulty. If the first PGW-U receives the Echo response message, but the value of the recovery counter in the Echo response message is different from the value of the recovery counter in the last received Echo response message, then the first PGW-U It is determined that the first SGW-U restarts. If the first SGW-U restarts, the value of the recovery counter in the Echo response message will increase by 1. Therefore, when the first PGW-U detects that the value of the restoration counter in the Echo response message is different from the value of the restoration counter in the last received Echo response message, the first PGW-U can determine the first SGW-U A restart occurred.

Of course, the first PGW-U may also determine whether the first SGW-U is abnormal in other ways, which is not limited in the embodiment of the application.

Wherein, the first PGW-U may send the identification of the first SGW-U to the first PGW-C through a Node-level message. For example, the Node-level message may be a node report request message. Alternatively, the first PGW-U may also send the identification of the first SGW-U to the first PGW-C through a private Node-level message defined outside the protocol.

For the specific implementation of how the first SGW-C detects whether the first SGW-U is abnormal, refer to the description corresponding to the above step 301, which will not be repeated here.

Wherein, the first SGW-C may send the identification of the first SGW-U to the first PGW-C through an Echo message at the Node level that is already in the agreement. Alternatively, the first SGW-C may send the identifier of the first SGW-U to the first PGW-C through an existing session-level session management/mobility management message in the protocol. Alternatively, the first SGW-C may also send the identity of the first SGW-U to the first PGW-C through a private Node-level message defined outside the protocol.

402. The first PGW-C determines the second session affected by the first SGW-U according to the identifier of the first SGW-U.

In the embodiment of the present application, after receiving the identifier of the first SGW-U, the first PGW-C determines the second session affected by the first SGW-U according to the identifier of the first SGW-U. The second session affected by the first SGW-U refers to a session using the first PGW-C and the first SGW-U.

In a specific design, the first SGW-C may also send the identification of the SGW-U used in the session to the first PGW-C; the first PGW-C receives the SGW-U used in the session from the first SGW-C. After the identification of U, the identification of the SGW-U corresponding to the session is recorded in the session; the first PGW-C determines the second session affected by the first SGW-U according to the identification of the first SGW-U. The specific implementation manner is: A PGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U. Based on this specific design, the first PGW-C can accurately determine the second session affected by the first SGW-U.

For example, take the first PGW-C as PGW-C1 and the first SGW-U as SGW-U1 as an example. Session 1, Session 2, and Session 3 use PGW-C1. Session 1 and Session 2 also use SGW-U1. Session 3 also uses SGW-U2. SGW-C1 can send SGW-U1 used in session 1, SGW-U1 used in session 2, and SGW-U2 used in session 3 to PGW-C1. After PGW-C1 receives SGW-U1 used in session 1, SGW-U1 used in session 2, and SGW-U2 used in session 2, PGW-C1 records the identification of SGW-U1 in session 1 and session 2, and Record the identification of SGW-U2 in session 3. After PGW-C1 receives the identifier of SGW-U1, it searches for the identifier of SGW-U1 in Session 1 to Session 3 of PGW-C1. PGW-C1 finds the identity of SGW-U1 in Session 1 and Session 2. Therefore, PGW-C1 determines Session 1 and Session 2 as the second session determined to be affected by SGW-U1.

In a specific design, after the first PGW-C determines the second session affected by the first SGW-U according to the identifier of the first SGW-U, the first PGW-C needs to record the second session affected by the first SGW-U The second session, so as to subsequently trigger the process of reselecting a non-failed SGW-U for the second session. For example, the first PGW-C may record the second session affected by the first SGW-U in the following manner: the first PGW-C marks the second session. Or, the first PGW-C sets a flag bit for the second session. Alternatively, the first PGW-C creates a list of sessions affected by the first SGW-U, and adds the second session to the list.

In a specific design, after the first PGW-C receives the bearer modification request corresponding to the second session from the third SGW-C, the PGW-C cancels the recording of the second session. For example, after the first PGW-C receives the bearer modification request corresponding to the second session from the third SGW-C, the first PGW-C cancels the marking of the second session. Or, the first PGW-C cancels the flag bit set for the second session. Or, the first PGW-C removes the second session from the list of sessions affected by the first SGW-U. In this way, the first PGW-C can subsequently process the services of the second session normally.

403. The first PGW-C sends the first message to the MME when receiving the downlink signaling of the second session.

For example, the first PGW-C may send the first message to the MME when receiving the downlink signaling of the second session from the policy and charging rules function (PCRF). Alternatively, the first PGW-C may send the first message to the MME when receiving the downlink signaling of the second session from other devices on the network side.

Specifically, when receiving the downlink signaling of the second session, the first PGW-C sends the first message to the MME through the SGW-C. The first PGW-C may send the first message to the MME through the SGW-C where the second session is located or send the first message to the MME through other SGW-Cs that have not failed.

Wherein, the first message is used to trigger the MME to reselect a non-faulty SGW-C for the second session. For example, the first message may be a packet data network gateway downlink triggering notification (P-GW downlink triggering notification, PDTN) message. Correspondingly, after receiving the PDTN message, the MME may send a packet data network gateway downlink triggering acknowledgement (P-GW downlink triggering ack, PDTA) message to the first PGW-C. Alternatively, the first message may also be another message, which is not limited in the embodiment of the present application.

For example, the second session includes session 1 and session 2. When the first PGW-C receives the session 1 signaling, it sends a first message to the MME. The first information is used to trigger the MME to reselect a third SGW-C that is not faulty for the session 1. When the first PGW-C receives the session 2 signaling, it sends a first message to the MME. The first information is used to trigger the MME to reselect a third SGW-C that is not faulty for the session 2.

404. The MME reselects a third SGW-C that has not failed for the second session according to the first message.

In the embodiment of this application, after the MME receives the first message from the first PGW-C, the MME re-selects a third SGW-C that is not faulty for the second session according to the first message. The third SGW-C may be the same as or different from the first SGW-C, which is not limited in the embodiment of the present application.

The principle of the MME reselecting a non-faulty third SGW-C for the second session is the same as the principle of the MME reselecting a non-failed second SGW-C for the first session in FIG. 3, and will not be repeated here.

405. The third SGW-C reselects a third SGW-U that has not failed for the second session.

Among them, the principle of the third SGW-C re-selecting a non-faulty third SGW-U for the second session is the same as the principle of the second SGW-C re-selecting a non-failed second SGW-U for the first session in FIG. 3 The same, so I won’t repeat them here.

In a specific design, steps 403 to 405 may not be executed. When the first PGW-C receives the downlink signaling of the second session, the first PGW-C can directly send a target message to the SGW-C used in the second session, and the target message is used to trigger the The SGW-C re-selects an unfaulted SGW-U message for the second session. After receiving the target message, the SGW-C used in the second session re-selects a third SGW-U that has not failed for the second session. In this specific design, there is no need to reselect a non-faulty third SGW-C, and a non-failed SGW-U can be selected for the second session by the original SGW-C used for the second session.

By implementing the method described in FIG. 4, the first PGW-C can send the first message to the MME when receiving the signaling of the affected second session, so that the MME can reselect a third SGW that has not failed for the second session -C, the third SGW-C re-selects a third SGW-U that has not failed for the second session. It can be seen that by implementing the method described in FIG. 4, the reselection of the SGW-U for the session affected by the abnormal SGW-U can be triggered in time through the signaling sent by the network side, which is beneficial to timely restoration of the affected services.

Based on the foregoing communication system, please refer to FIG. 5, which is another gateway selection method provided by an embodiment of the present application. The method described in FIG. 5 is used to reselect the SGW-U in time for the sessions affected by the abnormal SGW-U when the SGW-U is abnormal. In the method described in FIG. 5, the second session affected by the failed SGW-U is recorded through the SGW-C. When the SGW-C receives the downlink signaling of the second session, it initiates a process of reselecting the SGW-U for the second session. As shown in Figure 5, the gateway selection method includes the following parts 501 to 507, in which:

501. When detecting that the first SGW-U is abnormal, the first SGW-C determines the second session affected by the first SGW-U.

The first SGW-C will detect whether the first SGW-U is abnormal, and when the first SGW-U is detected to be abnormal, the second session affected by the first SGW-U is determined. The second session affected by the first SGW-U refers to a session using the first SGW-C and the first SGW-U. For the specific implementation manner for the first SGW-C to detect whether the first SGW-U is abnormal, please refer to the description of the specific implementation manner for the first SGW-C to detect whether the first SGW-U is abnormal in the embodiment corresponding to FIG. 3 , I won’t go into details here.

In a specific design, the first SGW-C may record the identification of the SGW-U used in the session in the session; the specific implementation manner for the first SGW-C to determine the second session affected by the first SGW-U is : The first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U. Based on this specific design, the first SGW-C can accurately determine the second session affected by the first SGW-U.

For example, take the first SGW-C as SGW-C1 and the first SGW-U as SGW-U1 as an example. Session 1, Session 2, and Session 3 use SGW-C1. Session 1 and Session 2 also use SGW-U1. Session 3 also uses SGW-U2. Then, SGW-C1 will record the identification of SGW-U1 in Session 1 and Session 2, and the identification of SGW-U2 in Session 3. If SGW-C1 detects that SGW-U1 is abnormal, it searches the SGW-C1 session for the identification of SGW-U1. SGW-C1 finds the identity of SGW-U1 in Session 1 and Session 2. Therefore, SGW-C1 determines Session 1 and Session 2 as the second session determined to be affected by SGW-U1.

In a specific design, after the first SGW-C determines the second session affected by the first SGW-U, the first SGW-C needs to record the second session affected by the first SGW-U in order to subsequently detect whether The signaling of the session affected by the first SGW-U is received. For example, the first SGW-C may record the second session affected by the first SGW-U in the following manner: the first SGW-C marks the second session. Or, the first SGW-C sets a flag bit for the second session. Alternatively, the first SGW-C creates a list of sessions affected by the first SGW-U, and adds the second session to the list.

502. The first PGW-C receives the first signaling corresponding to the second session.

Wherein, the first PGW-C is a PGW-C docked with the first SGW-C, and the first PGW-C has a second session. The first signaling may be sent by the PCRF to the first PGW-C, or sent by other devices to the first PGW-C, which is not limited in this embodiment of the application.

503. The first PGW-C sends second signaling corresponding to the second session to the first SGW-C according to the first signaling.

In the embodiment of the present application, after the first PGW-C receives the first signaling corresponding to the second session, the first PGW-C sends the second signaling corresponding to the second session to the first SGW-C.

504. The first SGW-C sends a response of the second signaling to the first PGW-C.

In the embodiment of the present application, after receiving the second signaling from the first PGW-C, the first SGW-C determines that the second signaling is the second signaling corresponding to the second session. Therefore, the first SGW-C sends a response of the second signaling to the first PGW-C. The response of the second signaling carries a cause value indicating that the context of the second session is not found.

Wherein, the first signaling may be a re-auth-request (re-auth-request, RAR), and the second signaling may be a create bearer request (create bearer request) or an update bearer request (update bearer request). Wherein, the bearer creation request corresponding to the second session is used to create a dedicated bearer of the second session. The update bearer request corresponding to the second session is used to update the bearer of the second session. Alternatively, the first signaling and the second signaling may also be other signaling, which is not limited in the embodiment of the present application.

In a specific design, after receiving the dedicated bearer creation request from the first PGW-C, the first SGW-C may also delete the second session. The first SGW-C may delete the second session while sending the dedicated bearer creation response to the first PGW-C, or delete the second session after sending the dedicated bearer creation response to the first PGW-C. The application examples are not limited. Since the SGW-C needs to be re-selected for the second session, the retention of the second session in the first SGW-C has no effect, and the first SGW-C needs to delete the second session.

505. The first PGW-C sends a first message to the MME.

In the embodiment of the present application, after receiving the response of the second signaling from the first SGW-C, the first PGW-C sends the first message to the MME. The first message is used to trigger the MME to reselect a non-faulty SGW-C for the second session. For example, the first message may be a packet data network gateway downlink triggering notification (P-GW downlink triggering notification, PDTN) message. Correspondingly, after receiving the PDTN message, the MME may send a packet data network gateway downlink triggering acknowledgement (P-GW downlink triggering ack, PDTA) message to the first PGW-C. Alternatively, the first message may also be another message, which is not limited in the embodiment of the present application.

Specifically, the first PGW-C sends the first message to the MME through the SGW-C. The first PGW-C may send the first message to the MME through the first SGW-C or send the first message to the MME through other non-faulty SGW-Cs.

506. The MME re-selects a third SGW-C that has not failed for the second session according to the first message.

In the embodiment of this application, after receiving the first message from the first PGW-C, the MME re-selects a third SGW-C that is not faulty for the second session according to the first message. The third SGW-C may be the same as or different from the first SGW-C, which is not limited in the embodiment of the present application. The principle of the MME reselecting a non-faulty third SGW-C for the second session is the same as the principle of the MME reselecting a non-failed second SGW-C for the first session in FIG. 3, and will not be repeated here.

507. The third SGW-C reselects a third SGW-U that has not failed for the second session.

In a specific design, steps 504 to 507 may not be executed. After the first SGW-C receives the second signaling corresponding to the second session from the first PGW-C, the first SGW-C directly reselects a non-faulty SGW-U for the second session. That is to say, in this specific design, there is no need to reselect a non-failed third SGW-C, and a non-failed SGW-U can be selected for the second session by the first SGW-C used in the second session. .

By implementing the method described in Figure 5, the first SGW-C can send a response of the second signaling to the first PGW-C when receiving the second signaling of the affected second session. The response of contains a reason value indicating that the context of the second session is not found. After the first PGW-C receives the response of the second signaling, the first PGW-C sends a first message to the MME to trigger the MME to re-select a third SGW-C that has not failed for the second session, and the third SGW-C -C re-selects the third SGW-U that has not failed for the second session. It can be seen that by implementing the method described in FIG. 5, the reselection of the SGW-U for the session affected by the abnormal SGW-U can be triggered in time through the signaling sent by the network side, which is beneficial to timely restoration of the affected services.

Based on the foregoing communication system, please refer to FIG. 6, which is another gateway selection method provided by an embodiment of the present application. The method described in FIG. 6 is used to reselect the SGW-U in time for the session affected by the abnormal SGW-U when the SGW-U is abnormal. In the method described in FIG. 6, the third session affected by the failed SGW-U is recorded through the PGW-U. When the PGW-U receives the downlink data message of the third session, it initiates a process of reselecting the SGW-U for the third session. As shown in Figure 6, the gateway selection method includes the following parts 601-605, in which:

601. When detecting that the first SGW-U is abnormal, the first PGW-U determines the third session affected by the first SGW-U.

Among them, the first PGW-U is any PGW-U of the gateway selection system. The first SGW-U is any SGW-U docked with the first PGW-U in the gateway selection system. For example, the first PGW-U is PGW-U1, and the first SGW-U is SGW-U1. The first PGW-U is PGW-U3, and the first SGW-U is SGW-U3.

For the specific implementation manner for the first PGW-U to detect the abnormality of the first SGW-U, refer to the description in the embodiment corresponding to FIG. 4, which is not repeated here.

The third session affected by the first SGW-U refers to a session using the first PGW-U and the first SGW-U.

In a specific design, the first PGW-U may record the identification of the SGW-U used by the session in the session; the specific implementation manner for the first PGW-U to determine the third session affected by the first SGW-U is : The first PGW-U determines that the session with the identifier of the first SGW-U in the session is the third session affected by the first SGW-U. Based on this specific design, the first PGW-U can accurately determine the third session affected by the first SGW-U.

For example, take the first PGW-U as PGW-U1 and the first SGW-U as SGW-U1 as an example. Session 1, Session 2, and Session 3 use PGW-U1. Session 1 and Session 2 also use SGW-U1. Session 3 also uses SGW-U2. Then, PGW-U1 will record the identification of SGW-U1 in Session 1 and Session 2, and the identification of SGW-U2 in Session 3. If PGW-U1 detects that SGW-U1 is abnormal, it searches for the SGW-U1 identifier in the session of PGW-U1. PGW-U1 finds the identity of SGW-U1 in Session 1 and Session 2. Therefore, PGW-U1 determines Session 1 and Session 2 as the third session determined to be affected by SGW-U1.

In a specific design, after the first PGW-U determines the second session affected by the first SGW-U, the first PGW-U needs to record the third session affected by the first SGW-U in order to subsequently detect whether Receive a downlink data message of the session affected by the first SGW-U. For example, the first PGW-U may record the third session affected by the first SGW-U in the following manner: the first PGW-U marks the third session. Or, the first PGW-U sets a flag bit for the third session. Or, the first PGW-U creates a list of sessions affected by the first SGW-U, and adds the third session to the list.

In a specific design, the first PGW-U receives the session modification request from the first PGW-C; the first PGW-U cancels the recording of the third session. For example, the first PGW-U unmarks session 1. Or, the first PGW-U cancels the flag bit set for session 1. Or, the first PGW-U removes Session 1 from the list of sessions affected by the first SGW-U. Based on this design, the first PGW-U receives the session modification request from the first PGW-C, indicating that the fourth SGW-U that has not failed has been re-selected for the third session, and the service of the subsequent third session can be restored. Therefore, at this time, the first PGW-U needs to cancel the recording of the third session, and subsequently the first PGW-U can process the service of the third session normally.

602. When receiving the downlink data message of the third session, the first PGW-U sends a notification message to the first PGW-C.

In the embodiment of this application, after the first PGW-U determines the third session affected by the first SGW-U, if a downlink data packet of the third session is received, the first PGW-U sends to the first PGW-C Notification message. The notification message is used to notify the third session that the downlink data packet is received, and the first PGW-C is the PGW-C that is docked with the first PGW-U. Wherein, the notification message may be session-level information, for example, it may be a session report request (session report request).

603. The first PGW-C sends a second message to the MME.

In the embodiment of the present application, after receiving the notification message from the first PGW-U, the first PGW-C sends a second message to the MME. The second message is used to trigger the MME to reselect a non-faulty SGW-C for the third session. For example, the second message may be a packet data network gateway downlink triggering notification (P-GW downlink triggering notification, PDTN) message. Correspondingly, after receiving the PDTN message, the MME may send a packet data network gateway downlink triggering acknowledgement (P-GW downlink triggering ack, PDTA) message to the first PGW-C. Alternatively, the second message may also be another message, which is not limited in the embodiment of the present application.

Specifically, after receiving the notification message from the first PGW-U, the first PGW-C sends the second message to the MME through the SGW-C. The first PGW-C may send the first message to the MME through the SGW-C used in the third session or send the first message to the MME through other SGW-Cs that have not failed.

604. The MME reselects a fourth SGW-C that has not failed for the third session according to the second message.

In this embodiment of the application, after receiving the second message from the PGW-C, the MME re-selects a fourth SGW-C that is not faulty for the third session according to the second message. The principle of the MME re-selecting a non-faulty fourth SGW-C for the third session is the same as the principle of the MME re-selecting a non-failed second SGW-C for the first session in FIG. 3, and will not be repeated here.

605. The fourth SGW-C reselects a fourth SGW-U that has not failed for the third session.

Among them, the principle of the fourth SGW-C re-selecting a non-faulty fourth SGW-U for the third session is the same as the principle of the second SGW-C re-selecting a non-failed second SGW-U for the first session in FIG. 3 The same, so I won’t repeat them here.

In a specific design, step 603 to step 605 may not be executed. When the first PGW-C receives from the first PGW-U a notification message for notifying that the third session has received a downlink data message, it can directly send a target message to the SGW-C used by the third session. The target message is The SGW-C used to trigger the third session reselects a non-faulty SGW-U for the third session. After receiving the target message, the SGW-C used in the third session reselects a non-faulty SGW-U for the third session. In this specific design, there is no need to reselect a non-faulty third SGW-C, and a non-failed SGW-U can be reselected for the third session by the SGW-C originally used for the third session.

By implementing the method described in FIG. 6, the first PGW-U can send a second message to the MME when receiving the downlink data message of the affected third session, so as to trigger the MME to reselect the unfailed one for the third session The fourth SGW-C, and the fourth SGW-C reselects the unfaulted fourth SGW-U for the third session. It can be seen that by implementing the method described in FIG. 6, the downlink data message sent by the network side can trigger the reselection of the SGW-U for the session affected by the abnormal SGW-U in a timely manner, which is conducive to timely restoration of the affected services.

It is worth mentioning that an abnormal SGW-U will affect all sessions using the SGW-U. Each session can receive signaling from the user equipment side, can also receive signaling from the network side, and can also receive downlink data packets. Therefore, the methods described in Figure 3, Figure 4, and Figure 6 can be combined with each other. Or, the methods described in FIG. 3, FIG. 5, and FIG. 6 are combined with each other. In this way, when the uplink signaling of the affected session is received, the process of reselecting the SGW-U for the affected session can be initiated through the method described in FIG. 3. When the downlink signaling of the affected session is received, the process of reselecting the SGW-U for the affected session can be initiated by the method described in FIG. 4 or FIG. 5. When receiving the downlink data message of the affected session, the process of reselecting the SGW-U for the affected session can be initiated through the method described in FIG. 6. By combining the methods described in Figure 3, Figure 4, and Figure 6 with each other, or combining the methods described in Figure 3, Figure 5, and Figure 6 with each other, it is possible to initiate a restart for the affected session in multiple scenarios. Select the process of SGW-U.

For example, the methods described in FIG. 3, FIG. 4, and FIG. 6 are combined with each other. The MME may determine the first session affected by the first SGW-U, and the MME actively reselects the SGW-U for the first session. Alternatively, the MME may initiate the process of reselecting SGW-U for the first session when receiving the signaling of the first session from the user equipment side. The first PGW-C may also determine the second session affected by the first SGW-U, and upon receiving the signaling of the second session from the network side, initiate the process of reselecting the SGW-U for the first session. The first PGW-U may also determine the third session affected by the first SGW-U, and when receiving the downlink data packet of the third session, initiate a process of reselecting the SGW-U for the third session.

For another example, the methods described in FIG. 3, FIG. 5, and FIG. 6 are combined with each other. The MME may determine the first session affected by the first SGW-U, and the MME actively reselects the SGW-U for the first session. Alternatively, the MME may initiate the process of reselecting SGW-U for the first session when receiving the signaling of the first session from the user equipment side. The first SGW-C may also determine the second session affected by the first SGW-U, and upon receiving the signaling of the second session from the network side, initiate the process of reselecting the SGW-U for the first session. The first PGW-U may also determine the third session affected by the first SGW-U, and when receiving the downlink data packet of the third session, initiate a process of reselecting the SGW-U for the third session.

In the communication system described above, not only SGW-U may be abnormal, but SGW-C may also be abnormal in some cases. If the SGW-C is abnormal, the channel between the UE and the PDN will be interrupted, resulting in the inability of the conversation service to proceed normally. Therefore, it is also necessary to reselect SGW-C for the affected session. For this reason, the embodiment of the present application also provides a gateway selection system and method for reselecting the SGW-C for the sessions affected by the abnormal SGW-C. The gateway selection system includes the network elements in the aforementioned communication system.

Based on the foregoing communication system, please refer to FIG. 7, which is another gateway selection method provided by an embodiment of the present application. The method described in FIG. 7 is used to reselect the SGW-C for the session affected by the abnormal SGW-C in time when the SGW-C is abnormal. In the method described in FIG. 7, the first session affected by the failed SGW-C is recorded through the PGW-U. When the PGW-U receives the downlink data message of the first session, it initiates a process of reselecting the SGW-C for the first session. As shown in Figure 7, the gateway selection method includes the following parts 701 to 705, in which:

701. The first PGW-U receives an identifier of the abnormal first SGW-C from the first PGW-C or the first SGW-U.

Among them, the first PGW-U can select any PGW-U in the system for the gateway. The first PGW-C is any PGW-C docked with the first PGW-U. The first SGW-U is any SGW-U docked with the first PGW-U. The first SGW-C is any SGW-C docked with the first PGW-C or the first SGW-U.

For example, as shown in FIG. 2, the first PGW-U is PGW-U1, the first PGW-C is PGW-C1, the first SGW-U is SGW-U1, and the first SGW-C is SGW-C1. The PGW-U1 can receive the identifier of the abnormal SGW-C1 from the PGW-C1 or SGW-U1. In other words, PGW-C1 or SGW-U1 will detect whether SGW-C1 is abnormal. If it is detected that the SGW-C1 is abnormal, the SGW-C1 identifier is sent to PGW-U1.

Among them, the first PGW-C can detect whether the first SGW-C is abnormal through the Echo request message. For example, the first PGW-C may send an Echo request message to the first SGW-C at a preset time period. After receiving the Echo request message, the first SGW-C returns an Echo response message to the first PGW-C. If the first PGW-C does not receive the Echo response message sent by the first SGW-C within the preset time period, the first PGW-C determines that the first SGW-C is faulty. If the first PGW-C receives the Echo response message, but the value of the recovery counter in the Echo response message is different from the value of the recovery counter in the last received Echo response message, then the first PGW-C It is determined that the first SGW-C restarts. If the first SGW-C restarts, the value of the recovery counter in the Echo response message will increase by 1. Therefore, when the first PGW-C detects that the value of the restoration counter in the Echo response message is different from the value of the restoration counter in the last received Echo response message, the first PGW-C can determine the first SGW-C A restart occurred.

Of course, the first PGW-C can also detect whether the first SGW-C is abnormal in other ways, which is not limited in the embodiment of the present application.

Among them, the first PGW-C may send the identifier of the abnormal first SGW-C to the first PGW-U through a message defined by an existing protocol, for example, an Sx Association Update Request message. Alternatively, the first PGW-C may send the identifier of the abnormal first SGW-C to the first PGW-U through another message.

Among them, the first SGW-U can detect whether the first SGW-C is abnormal through the HeatBeat message. For example, the first SGW-U may send a HeatBeat request message to the first SGW-C at a preset time period. After the first SGW-C receives the HeatBeat request message, it returns a HeatBeat response message to the first SGW-U. If the first SGW-U does not receive the HeatBeat response message sent by the first SGW-C within the preset time period, the first SGW-U determines that the first SGW-C is faulty. If the first SGW-U receives the HeatBeat response message, but the value of the recovery counter in the HeatBeat response message is different from the value of the recovery counter in the HeatBeat response message received last time, the first SGW-U It is determined that the first SGW-C restarts. If the first SGW-C restarts, the value of the restoration counter in the HeatBeat response message will increase by 1. Therefore, when the first SGW-U detects that the value of the restoration counter in the HeatBeat response message is different from the value of the restoration counter in the HeatBeat response message received last time, the first SGW-U can determine the first SGW-C A restart occurred.

Of course, the first SGW-U may also detect whether the first SGW-C is abnormal in other ways, which is not limited in the embodiment of the present application.

Wherein, the first SGW-U may send the identification of the first SGW-C to the first PGW-U through the existing Node-level Echo message of the agreement. Alternatively, the identification of the first SGW-C may be sent to the first PGW-U through an existing session-level session management/mobility management message of the protocol. Alternatively, the identification of the first SGW-C may also be sent to the first PGW-U through a private Node-level message defined outside the protocol.

702. The first PGW-U determines the first session affected by the first SGW-C according to the identifier of the first SGW-C.

In the embodiment of the present application, after the first PGW-U receives the identifier of the abnormal first SGW-C from the first PGW-C or the first SGW-U, it determines that the first SGW-C is affected by the identifier of the first SGW-C. The first session affected by C. The first session affected by the first SGW-C refers to a session using the first PGW-U and the first SGW-C.

In a specific design, the first PGW-U receives the identifier of the SGW-C used by the session from the first PGW-C; the first PGW-U records the SGW-C corresponding to the session in the session Identification; the first PGW-U determines the first session affected by the first SGW-C according to the identification of the first SGW-C: the first PGW-U determines that the session has the first session The session identified by the SGW-C is the first session affected by the first SGW-C. Based on this specific design, the first PGW-U can accurately determine the first session affected by the first SGW-C.

For example, take the first PGW-U as PGW-U1 and the first SGW-C as SGW-C1 as an example. Session 1, Session 2, and Session 3 use PGW-U1. Session 1 and Session 2 also use SGW-C1. Session 3 also uses SGW-C2. Then, PGW-U1 will record the identification of SGW-C1 in Session 1 and Session 2, and the identification of SGW-C2 in Session 3. If the first SGW-C is SGW-C1, after receiving the identifier of SGW-C1, the MME searches for the identifier of SGW-C1 in the MME session. The MME finds the identity of SGW-C1 in Session 1 and Session 2. Therefore, the MME determines Session 1 and Session 2 as the first session determined to be affected by SGW-C1.

In the full text of the embodiments of this application, the SGW-C used in the session may also be referred to as the SGW-C where the session is located or the SGW-C corresponding to the session.

In a specific design, after the first PGW-U determines the affected first session, it records the first session. For example, the first PGW-U may record the first session affected by the first SGW-C in the following manner: the first PGW-U marks the first session. Or, the first PGW-U sets a flag bit for the first session. Alternatively, the first PGW-U creates a list of sessions affected by the first SGW-C, and adds the first session to the list. In a specific design, after the first PGW-U receives the session modification request from the second SGW-C, the first PGW-U cancels the recording of the first session. For example, the first PGW-U unmarks the first session. Or, the first PGW-U cancels the flag bit set for the first session. Or, the first PGW-U removes the first session from the list of sessions affected by the first SGW-U. In this way, the first PGW-U can subsequently process the services of the first session normally.

703. When receiving the downlink data packet of the first session, the first PGW-U sends a notification message to the first PGW-C.

The notification message is used to notify that the downlink data packet of the first session is received. The notification message may be a session-level message, for example, a session report request (session report request), or other messages.

704. The first PGW-C sends a first message to the MME.

Specifically, after receiving the notification message from the first PGW-U, the first PGW-C sends the first message to the MME. The first message is used to trigger the MME to reselect a non-faulty SGW-C for the first session. For example, the first message may be a packet data network gateway downlink triggering notification (P-GW downlink triggering notification, PDTN) message. Correspondingly, after receiving the PDTN message, the MME may send a packet data network gateway downlink triggering acknowledgement (P-GW downlink triggering ack, PDTA) message to the first PGW-C. Alternatively, the first message may also be another message, which is not limited in the embodiment of the present application.

Specifically, the first PGW-C sends the first message to the MME through the non-faulty SGW-C.

705. The MME reselects a second SGW-C that has not failed for the first session according to the first message.

In this embodiment of the application, after receiving the first message, the MME re-selects a second SGW-C that is not faulty for the first session according to the first message. The principle of the MME reselecting a non-faulty second SGW-C for the first session is the same as the principle of the MME reselecting a non-failed second SGW-C for the first session in FIG. 3, which will not be repeated here.

By implementing the method described in FIG. 7, the first PGW-U can send the first message to the MME when receiving the downlink data message of the affected first session, so that the MME can re-select the first session that is not faulty for the first session. Two SGW-C. It can be seen that by implementing the method described in FIG. 7, the downlink data message sent by the network side can trigger the reselection of the SGW-C for the session affected by the abnormal SGW-C in a timely manner, which is beneficial to timely restoration of the affected services.

In the communication system described above, not only SGW-U and SGW-C may be abnormal, but PGW-U may also be abnormal in some cases. If the PGW-U is abnormal, the channel between the UE and the PDN will be interrupted, causing the conversation service to not be performed normally. To this end, the embodiments of the present application also provide a service restoration system and method, which are used to restore the service affected by the abnormal PGW-U. Wherein, the service recovery system may include the network elements in the aforementioned communication system.

Based on the foregoing communication system, please refer to FIG. 8, which is a service restoration method provided by an embodiment of the present application. The method described in Fig. 8 is used to recover the services affected by the abnormal PGW-U when the PGW-U is abnormal. In the method described in FIG. 8, the MME records the first session affected by the failed PGW-U, and the MME can actively initiate a process of restoring the service of the first session. Alternatively, the MME may also initiate a process of restoring the service of the first session when receiving the uplink signaling of the first session. As shown in Figure 8, the service recovery method includes the following parts 801 to 804, in which:

801. The first SGW-C receives an identifier of the first PGW-U that is abnormal from the first PGW-C or the first SGW-U.

Among them, the first SGW-C is any one of the service recovery system, the first PGW-C is the PGW-C that is connected to the first SGW-C in the service recovery system, and the first SGW-U is the first SGW-C in the service recovery system. An SGW-U docked with an SGW-C, the first PGW-U is docked with the first PGW-C and the first SGW-C respectively. For example, as shown in Fig. 2, the first SGW-C is GW-C1, the first SGW-U is SGW-U1, the first PGW-C is PGW-C1, and the first PGW-U is PGW-U1.

The first SGW-C can receive the identifier of the abnormal first PGW-U in the following two ways.

Manner 1: The first SGW-C receives the identifier of the abnormal first PGW-U from the first SGW-U. For example, the first SGW-U may detect whether the first PGW-U fails. If the first SGW-U detects that the first PGW-U fails, the first SGW-U sends the identification of the first PGW-U to the first SGW-C. The first SGW-U may send the identifier of the first PGW-U to the first SGW-C through a Node-level message or a session-level session management/mobility management message. For example, the Node-level message may be a node report request message. Alternatively, the first SGW-U may send the identity of the first PGW-U to the first SGW-C by defining a private Node-level message outside the protocol.

Wherein, the first SGW-U can detect whether the first PGW-U is abnormal through the Echo request message. For example, the first SGW-U may send an Echo request message to the first PGW-U at a preset time period. After receiving the Echo request message, the first PGW-U will return an Echo response message to the first SGW-U. If the first SGW-U does not receive the Echo response message sent by the first PGW-U within the preset time period, the first SGW-U determines that the first PGW-U is faulty. If the first SGW-U receives the Echo response message, but the value of the recovery counter in the Echo response message is different from the value of the recovery counter in the last received Echo response message, the first SGW-U It is determined that the first PGW-U restarts. If the first PGW-U restarts, the value of the recovery counter in the Echo response message will increase by 1. Therefore, when the first SGW-U detects that the value of the restoration counter in the Echo response message is different from the value of the restoration counter in the last received Echo response message, the first SGW-U can determine the first PGW-U A restart occurred.

Of course, the first SGW-U may also detect whether the first PGW-U is abnormal in other ways, which is not limited in the embodiment of the present application.

Manner 2: The first SGW-C receives the identifier of the abnormal first PGW-U from the first PGW-C. For example, the first PGW-C may detect whether the first PGW-U fails. If the first PGW-C detects that the first PGW-U has failed, the first PGW-C sends the identifier of the first PGW-U to the first SGW-C. The first PGW-C may send the identity of the first PGW-U to the first SGW-C through a Node-level message or a session-level session management/mobility management message. For example, the Node-level message may be a node report request message. Alternatively, the first PGW-C may send the identity of the first PGW-U to the first SGW-C by defining a private Node-level message outside the protocol.

Wherein, the first PGW-C can determine whether the first PGW-U is abnormal through the HeatBeat message of the Sx interface. For example, the first PGW-C may send a HeatBeat request message to the first PGW-U at a preset time period. After receiving the HeatBeat request message, the first PGW-U returns a HeatBeat response message to the first PGW-C. If the first PGW-C does not receive the HeatBeat response message sent by the first PGW-U within the preset time period, the first PGW-C determines that the first PGW-U is faulty. If the first PGW-C receives the HeatBeat response message, but the value of the recovery counter in the HeatBeat response message is different from the value of the recovery counter in the HeatBeat response message received last time, then the first PGW-C It is determined that the first PGW-U restarts. If the first PGW-U restarts, the value of the recovery counter in the HeatBeat response message will increase by 1. Therefore, when the first PGW-C detects that the value of the restoration counter in the HeatBeat response message is different from the value of the restoration counter in the HeatBeat response message received last time, the first PGW-C can determine the first PGW-U A restart occurred.

Of course, the first PGW-C may also determine whether the first PGW-U is abnormal in other ways, which is not limited in the embodiment of the present application.

802. The first SGW-C sends to the MME the identifier of the first PGW-U where the abnormality occurs.

In the embodiment of the present application, specifically, after receiving the identifier of the abnormal first PGW-U, the first SGW-C sends the identifier of the abnormal first PGW-U to the MME.

803. The MME determines the first session affected by the first PGW-U according to the identifier of the first PGW-U.

In the embodiment of the present application, after receiving the identifier of the first PGW-U from the first SGW-C, the MME determines the first session affected by the first PGW-U according to the identifier of the first PGW-U. The first session affected by the first PGW-U refers to a session using the MME and the first PGW-U.

In a specific design, the MME records the identification of the PGW-U used by the session in the session; the specific implementation manner for the MME to determine the first session affected by the first PGW-U according to the identification of the first PGW-U is: The MME determines that the session with the identifier of the first PGW-U in the session is the first session affected by the first PGW-U. Based on this specific design, the MME can accurately determine the first session affected by the first PGW-U.

For example, Session 1, Session 2, and Session 3 use MME. Session 1 and Session 2 also use SGW-C1, SGW-U1, PGW-C1, and PGW-U1. Session 3 also uses SGW-C2, SGW-U3, PGW-C2, and PGW-U3. Then, the MME will record the identification of PGW-U1 in Session 1 and Session 2, and the identification of PGW-U3 in Session 3. If the first PGW-U is PGW-U1, after receiving the identification of PGW-U1, the MME searches for the identification of PGW-U1 in the MME session. The MME finds the identity of PGW-U1 in Session 1 and Session 2. Therefore, the MME determines Session 1 and Session 2 as the first session determined to be affected by PGW-U1.

In the full text of the embodiments of this application, the PGW-U used in the session may also be referred to as the PGW-U where the session is located or the PGW-U corresponding to the session.

In a specific design, the MME may record the first session after determining the first session affected by the first PGW-U according to the identifier of the first PGW-U. For example, the MME may record the first session affected by the first PGW-U in the following manner: the MME marks the first session. Or, the MME sets a flag bit for the first session. Alternatively, the MME creates a list of sessions affected by the first PGW-U, and adds the first session to the list.

804. The MME deletes the first session, and instructs the user equipment corresponding to the first session to re-establish a PDN connection.

In this embodiment of the present application, after determining the first session affected by the first PGW-U according to the identifier of the first PGW-U, the MME deletes the first session, and instructs the user equipment corresponding to the first session to re-establish a PDN connection. In other words, the MME will delete the first session and instruct the user equipment to re-establish a session with the PDN. After the user equipment re-establishes the session with the PDN, the service of the user equipment can be restored to normal.

In a specific design, the MME will also instruct the first SGW-C to delete the first session. After receiving the instruction for deleting the first session from the MME, the first SGW-C deletes the first session. And the first SGW-C sends an instruction for deleting the first session to the first SGW-U and the first PGW-C. After receiving the instruction for deleting the first session, the first SGW-U and the first PGW-C also delete the first session.

The MME can delete the first session in the following two ways, and instruct the user equipment corresponding to the first session to re-establish the PDN connection.

Manner 1: There are multiple first sessions affected, and the MME deletes the multiple first sessions at a preset rate, and instructs the user equipment corresponding to the first session to re-establish a PDN connection.

Manner 2: When the MME receives the uplink signaling of the first session, it deletes the first session and instructs the user equipment corresponding to the first session to re-establish the PDN connection. The uplink signaling may be a service request or other uplink signaling. For example, the first affected session includes session 1 to session 100, the MME deletes session 1 to session 100 at a preset rate, and instructs the user equipment corresponding to the session to re-establish a PDN connection. When the MME receives the service request of the session 100 from the user equipment, it preferentially deletes the session 100 and instructs the user equipment corresponding to the session 100 to re-establish the PDN connection. Due to the large number of first sessions affected, it will take a long time for all services of these 100 sessions to be restored, which may cause some emergency services to fail to be restored in time. In this specific design, when the MME receives the signaling sent by the user equipment side, it can trigger the restoration of the service corresponding to the signaling. Therefore, this design facilitates the timely restoration of emergency services.

It can be seen that by implementing the method described in Figure 8, the affected business can be restored.

Please refer to FIG. 9, which is another service recovery method provided by an embodiment of the present application. The method described in Fig. 9 is used to recover the services affected by the abnormal PGW-U in time when an abnormality occurs in the PGW-U. In the method described in FIG. 9, the SGW-U records the second session affected by the failed PGW-U. When the SGW-U receives the uplink data message of the second session, it initiates a process of restoring the service of the second session. As shown in Figure 9, the service recovery method includes the following parts 901 to 903, of which:

901. When determining that the first PGW-U is abnormal, the first SGW-U determines the second session affected by the first PGW-U.

Among them, the first SGW-U is any SGW-U, and the first PGW-U is any PGW-U docked with the SGW-U. For example, as shown in FIG. 2, when the first SGW-U is SGW-U1, the first PGW-U is PGW-U1. When the first SGW-U is SGW-U3, the first PGW-U is PGW-U3.

For a specific implementation manner of how the first SGW-U determines that the first PGW-U is abnormal, refer to the description in the embodiment corresponding to FIG. 8, which is not repeated here.

The second session affected by the first PGW-U refers to a session using the first SGW-U and the first PGW-U.

In a specific design, the first SGW-U records the identity of the PGW-U used by the session in the session; the first SGW-U determines the first PGW-U affected by the identity of the first PGW-U according to the identity of the first PGW-U The specific implementation of the second session is: the first SGW-U determines that the session with the identifier of the first PGW-U in the session is the second session affected by the first PGW-U. Based on this specific design, the first SGW-UE can accurately determine the second session affected by the first PGW-U.

For example, session 1, session 2, session use SGW-U1. Session 1 and Session 2 also use PGW-U1. Session 3 also uses PGW-U2. Then, SGW-U1 will record the identification of PGW-U1 in Session 1 and Session 2, and the identification of PGW-U2 in Session 3. If the first PGW-U is PGW-U1, after receiving the identification of PGW-U1, SGW-U1 searches for the identification of PGW-U1 in the session of SGW-U1. SGW-U1 finds the identity of PGW-U1 in Session 1 and Session 2. Therefore, SGW-U1 determines Session 1 and Session 2 as the second session determined to be affected by PGW-U1.

In a specific design, after the first SGW-U determines the second session affected by the first PGW-U according to the identifier of the first PGW-U, the second session may be recorded. For example, the first SGW-U may record the second session affected by the first PGW-U in the following manner: the first SGW-U marks the second session. Or, the first SGW-U sets a flag bit for the second session. Alternatively, the first SGW-U creates a list of sessions affected by the first PGW-U, and adds the second session to the list.

902. The first SGW-U sends a notification message to the first SGW-C when receiving the uplink data packet of the second session.

In the embodiment of the present application, after determining the second session affected by the first PGW-U, the first SGW-U sends a notification message to the first SGW-C when receiving the uplink data packet of the second session. The notification message is used to notify the second session that the uplink data packet is received. Among them, the uplink data message refers to the data message from the user side. The notification message may be a message defined by an existing protocol. For example, the notification message may be a session report request message. The notification message can also be a private message defined outside the protocol.

903. The first SGW-C deletes the second session, and instructs the user equipment corresponding to the second session to re-establish a PDN connection.

Specifically, after receiving the notification message from the first SGW-U, the first SGW-C deletes the second session, and instructs the user equipment corresponding to the second session to re-establish the PDN connection. In other words, the first SGW-C will delete the second session and instruct the user equipment to re-establish a session with the PDN. After the user equipment re-establishes the session with the PDN, the service of the user equipment can be restored to normal.

In a specific design, the first SGW-C will also instruct the MME, the first SGW-U, and the first PGW-C to delete the second session. After receiving the instruction for deleting the second session, the MME deletes the second session. After receiving the instruction for deleting the second session, the first SGW-U deletes the second session. After receiving the instruction for deleting the second session, the first PGW-C deletes the second session.

Through the method described in FIG. 9, the first SGW-U can trigger the service recovery of the second session in time when receiving the uplink data message of the second session.

Please refer to FIG. 10, which is another service recovery method provided by an embodiment of the present application. The method described in Fig. 10 is used to recover the services affected by the abnormal PGW-U in time when an abnormality occurs in the PGW-U. In the method described in FIG. 10, PGW-C records the third session affected by the failed PGW-U. When the PGW-C receives the uplink data message of the third session, it initiates a process of restoring the service of the third session. As shown in Figure 10, the service recovery method includes the following parts 1001 to 1002, among which:

1001. The first PGW-C determines the third session affected by the first PGW-U when detecting that the first PGW-U is abnormal.

In the embodiment of this application, the first PGW-C is any PGW-C in service restoration. The first PGW-U is any PGW-U docked with the first PGW-C. For example, as shown in FIG. 2, the first PGW-C is PGW-C1, and the first PGW-U is PGW-U1 or PGW-U2. The first PGW-C is PGW-C2, and the first PGW-U is PGW-U3 or PGW-U4.

Among them, the third session affected by the first PGW-U refers to a session existing in the first PGW-C and existing in the first PGW-U.

For the specific implementation manner for the first PGW-C to detect the abnormality of the first PGW-U, refer to the description in the embodiment corresponding to FIG. 7, which is not repeated here.

In a specific design, the first PGW-C records the identity of the PGW-U used by the session in the session; the first PGW-C determines the first PGW-U affected by the identity of the first PGW-U according to the identity of the first PGW-U The specific implementation of the third session is: the first PGW-C determines that the session with the identifier of the first PGW-U in the session is the third session affected by the first PGW-U. Based on this specific design, the first PGW-C can accurately determine the third session affected by the first PGW-U.

For example, the first PGW-C includes session 1, session 2, and session 3. Session 1 and Session 2 use PGW-U1. Session 3 also uses PGW-U2. Then, the first PGW-C will record the identification of PGW-U1 in Session 1 and Session 2, and the identification of PGW-U2 in Session 3. If the first PGW-U is PGW-U1, after receiving the identification of PGW-U1, the first PGW-C searches for the identification of PGW-U1 in the session of the first PGW-C. The first PGW-C finds the identity of PGW-U1 in Session 1 and Session 2. Therefore, the first PGW-C determines Session 1 and Session 2 as the third session determined to be affected by PGW-U1.

In a specific design, after the first PGW-C determines the third session affected by the first PGW-U according to the identifier of the first PGW-U, the third session may be recorded. For example, the first PGW-C may record the third session affected by the first PGW-U in the following manner: the first PGW-C marks the third session. Or, the first PGW-C sets a flag bit for the third session. Alternatively, the first PGW-C creates a list of sessions affected by the first PGW-U, and adds the third session to the list.

1002. When receiving the downlink signaling of the third session, the first PGW-C deletes the third session, and instructs the user equipment corresponding to the third session to re-establish a PDN connection.

Specifically, after the first PGW-C determines the third session affected by the first PGW-U, if the downlink signaling of the third session is received, the third session is deleted, and the user equipment corresponding to the third session is instructed to re-establish PDN connection. In other words, the first PGW-C will delete the third session and instruct the user equipment to re-establish a session with the PDN. After the user equipment re-establishes the session with the PDN, the service of the user equipment can proceed normally.

Wherein, the signaling may be signaling from PCRF, for example, a re-authentication request message. Alternatively, the signaling may also be signaling from other network elements on the network side, which is not limited in the embodiment of the present application.

In a specific design, the first PGW-C will also instruct the first SGW-C to delete the third session. After receiving the instruction for deleting the third session, the first SGW-C deletes the third session. After receiving the instruction for deleting the third session, the first SGW-C also instructs the first SGW-U and the MME to delete the third session. After receiving the instruction for deleting the third session, the MME deletes the third session. After receiving the instruction for deleting the third session, the first SGW-U deletes the third session.

In a specific design, when the first PGW-C receives the signaling of the fourth session, the first PGW-C sends a message to the second PGW-U according to the signaling of the fourth session; the first PGW-C After the message is retransmitted to the second PGW-U, if the first PGW-C does not receive the response message of the message within the preset time period, the fourth session is deleted, and the user equipment corresponding to the fourth session is instructed to re-establish the PDN connection. Wherein, the second PGW-U is any PGW-U connected to the first PGW-C except the first PGW-U. The fourth session is a session existing in the first PGW-C and in the second PGW-U. For example, as shown in FIG. 2, the first PGW-C is PGW-C1, the first PGW-U is PGW-U1, and the second PGW-U is PGW-U2. PGW-C1 detects that PGW-U1 is abnormal, and determines that the session affected by PGW-U1 is session 1. PGW-C1 deletes session 1 and instructs the user equipment of session 1 to re-establish a PDN connection to restore the service of session 1. If PGW-U2 is also abnormal but PGW-C1 has not yet sensed it, at this time, if PGW-C1 receives session 2 signaling, such as a re-authentication request message, PGW-C1 sends to PGW-U2 according to session 2 signaling information. If PGW-C1 does not receive PGW-U2's response to the information, PGW-C1 resends the information to PGW-U2. If after PGW-C1 retransmits the message to PGW-U2, PGW-C1 still does not receive a response message for the message within the preset time period, PGW-C1 deletes session 2 and instructs the user equipment corresponding to session 2 to restart Establish a PDN connection. Based on this specific design, even when PGW-C1 does not detect the abnormality of PGW-U2 in time, it can also restore services affected by PGW-U2 in time.

It can be seen that through the method described in FIG. 10, the first PGW-C can trigger the service recovery of the third session in time when receiving the signaling of the third session.

It is worth mentioning that an abnormality of a PGW-U will affect all sessions using the PGW-U. Each session can receive uplink signaling, uplink data packets, and downlink signaling. Therefore, the methods described in Figure 8, Figure 9, and Figure 10 can be combined with each other. In this way, the uplink session is received, and the service affected by the abnormal PGW-U can be restored by the method described in Figure 8. After receiving the session of the uplink data message, the service affected by the abnormal PGW-U can be restored by the method described in FIG. 9. After receiving the downlink signaling session, the service affected by the abnormal PGW-U can be restored by the method described in Figure 10. By combining the methods described in Figure 8, Figure 9 and Figure 10 with each other, services affected by abnormal PGW-U can be restored in multiple scenarios.

For example, the methods described in FIG. 8, FIG. 9, and FIG. 10 are combined. The MME may determine the first session affected by the abnormal first PGW-U, and the MME actively initiates a process of recovering the service of the first session. Alternatively, the MME may initiate a process of recovering the service of the first session when receiving the uplink signaling of the first session. The first SGW-U may also determine the second session affected by the abnormal first PGW-U. When receiving the uplink data packet of the second session, the first SGW-U initiates a process of recovering the service of the second session. The first PGW-C may also determine the third session affected by the abnormal first PGW-U, and upon receiving the downlink signaling of the third session, initiate a process of recovering the service of the third session.

The embodiment of the present invention may divide the device into functional modules according to the foregoing method examples. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiment of the present invention is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the MME in the method embodiment described in FIG. 3. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The communication module 1102 is configured to receive the identifier of the abnormal first serving gateway user plane function entity SGW-U from the first serving gateway control plane function entity SGW-C, and the first SGW-C is connected to the first SGW-U; processing; The module 1101 is configured to determine the first session affected by the first SGW-U according to the identifier of the first SGW-U; the processing module 1101 is also configured to reselect a second SGW-C that has not failed for the first session.

In a specific design, the processing module 1101 is also used to record the identity of the SGW-U used in the session; the processing module 1101 determines the first SGW-U affected by the identity of the first SGW-U according to the identity of the first SGW-U The method of a session is specifically: determining that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U.

In a specific design, the method for the processing module 1101 to reselect the second SGW-C that has not failed for the first session is specifically as follows: when the communication module 1102 receives the uplink signaling of the first session, the processing module 1101 is the first session. One session reselects the second SGW-C that has not failed.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first PGW-C in the method embodiment described in FIG. 4. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The communication module 1102 is configured to receive the identifier of the abnormal first serving gateway user plane function entity SGW-U from the first packet data network gateway user plane function entity PGW-U or the first serving gateway control plane function entity SGW-C, The network device is docked with the first PGW-U, and the network device is docked with the first SGW-C, the first SGW-U is docked with the first PGW-U, and the first SGW-U is docked with the first SGW-C; processing module 1101, configured to determine the second session affected by the first SGW-U according to the identity of the first SGW-U; the communication module 1102 is also configured to send the second session to the mobility management entity MME when receiving downlink signaling of the second session A message, the first message is used to trigger the MME to reselect a non-faulty SGW-C for the second session.

In a specific design, the communication module 1102 is also used to receive the SGW-U identifier used in the session from the first SGW-C; the processing module 1101 is also used to record the SGW-U corresponding to the session in the session Identification; the processing module 1101 determines the second session affected by the first SGW-U according to the identification of the first SGW-U specifically: determining that the session with the identification of the first SGW-U in the session is affected by the first SGW-U The second session affected.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first SGW-C in the method embodiment described in FIG. 5. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The processing module 1101 is configured to determine the second session affected by the first SGW-U when an abnormality occurs in the user plane function entity SGW-U of the first serving gateway that is connected; the communication module 1102 is configured to receive data from the first packet The network gateway control plane function entity PGW-C receives the second signaling corresponding to the second session; the communication module 1102 is also used to send a response of the second signaling to the first PGW-C, and the response of the second signaling carries The reason value used to indicate that the context of the second session was not found.

In a specific design, the processing module 1101 is also used to record the identification of the SGW-U used by the session in the session; the method for the processing module 1101 to determine the second session affected by the first SGW-U is specifically: determine The session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.

In a specific design, the processing module 1101 is further configured to delete the second session after the communication module 1102 receives the dedicated bearer creation request corresponding to the second session.

The embodiment of the present application provides a network device. The network device may be used to perform part or all of the functions of the first PGW-C in the method embodiment described in FIG. 5. The network device may include a communication module. among them:

The communication module is configured to receive the first signaling; the communication module is also configured to send the second signaling corresponding to the second session to the first serving gateway control plane functional entity SGW-C according to the first signaling; the communication module, further It is used to receive a response of the second signaling from the first SGW-C, and the response of the second signaling carries a reason value for indicating that the second session context is not found. The second session is the recipient of the first SGW-C. The session affected by the abnormal first serving gateway user plane function entity SGW-U; the communication module is also used to send a first message to the mobility management entity MME, and the first message is used to trigger the MME to reselect a non-faulty session for the second session The third SGW-C.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first PGW-U in the method embodiment described in FIG. 6. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The processing module 1101 is configured to determine the third session affected by the first SGW-U when an abnormality of the user plane function entity SGW-U of the connected first serving gateway is detected; the communication module 1102 is configured to In the case of a downlink data message of the session, a notification message is sent to the first packet data network gateway control plane function entity PGW-C that is connected, and the notification message informs the third session that the downlink data message is received.

In a specific design, the processing module 1101 is also used to record the identification of the SGW-U used by the session in the session; the method for the processing module 1101 to determine the third session affected by the first SGW-U is specifically: determine The session with the identifier of the first SGW-U in the session is the third session affected by the first SGW-U.

The embodiment of the present application provides a network device. The network device may be used to perform part or all of the functions of the first PGW-C in the method embodiment described in FIG. 6. The network device may include a communication module. among them:

The communication module is used to receive a notification message from the first packet data network gateway user plane function entity PGW-U, where the notification message is used to notify the reception of a downlink data packet of a third session, which is the first PGW-U The communication module is also used to send a first message to the mobility management entity MME. The first message is used by the MME to select a new session for the third session. The faulty SGW-C.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first PGW-U in the method embodiment described in FIG. 7. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The communication module 1102 is configured to receive the identifier of the abnormal first serving gateway control plane function entity SGW-C from the first packet data network gateway control plane function entity PGW-C or the first serving gateway user plane function entity SGW-U, The first PGW-C and the first SGW-U are respectively docked with the network equipment, and the first PGW-C and the first SGW-U are respectively docked with the first SGW-C; the processing module 1101 is configured to connect with the first SGW-C Identifies the first session affected by the first SGW-C; the communication module 1102 is also configured to send a notification message to the first PGW-C when receiving a downlink data message of the first session, and the notification message is used to notify The downlink data packet of the first session is received.

In a specific design, the communication module 1102 is also used to receive the identification of the SGW-C used in the session from the first PGW-C; the processing module 1101 is also used to record the SGW-C used in the session in the session The method for the processing module 1101 to determine the first session affected by the first SGW-C according to the identifier of the first SGW-C is specifically: determining that the session with the identifier of the first SGW-C in the session is affected by the first SGW-C The first session affected by C.

The embodiment of the present application provides a network device. The network device may be used to perform part or all of the functions of the first PGW-C in the method embodiment described in FIG. 7. The network device may include a communication module. among them:

The communication module is used to receive a notification message from the first packet data network gateway user plane function entity PGW-U, where the notification message is used to notify that a downlink data message indicating the reception of the first session is received, and the first session is the first PGW- A session affected by the abnormal first serving gateway control plane function entity SGW-C in U; the communication module is also used to send a first message to the mobility management entity MME, which is used to trigger the MME to reselect for the first session A surviving SGW-C.

In a specific design, the communication module is also used to send the identification of the first SGW-C to the first PGW-U when it is determined that the first SGW-C is abnormal.

In a specific design, the communication module is also used to send the SGW-C identifier corresponding to the session to the first PGW-U.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the MME in the method embodiment described in FIG. 8. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The communication module 1102 is configured to receive the identifier of the abnormal first packet data network gateway user plane functional entity PGW-U from the first serving gateway control plane functional entity SGW-C; the processing module 1101 is configured to The identifier of determines the first session affected by the first PGW-U; the processing module 1101 is further configured to delete the first session and instruct the user equipment corresponding to the first session to re-establish a packet data network PDN connection.

In a specific design, the processing module 1101 is also used to record the identification of the PGW-U used in the session; the processing module 1101 determines the first PGW-U affected by the identification of the first PGW-U according to the identification of the first PGW-U The method of a session is specifically: determining that the session with the identifier of the first PGW-U in the session is the first session affected by the first PGW-U.

In a specific design, the processing module 1101 deletes the first session, and instructs the user equipment corresponding to the first session to re-establish a packet data network PDN connection: when the communication module 1102 receives the uplink of the first session During signaling, the first session is deleted, and the user equipment corresponding to the first session is instructed to re-establish the PDN connection.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first SGW-U in the method embodiment described in FIG. 9. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The processing module 1101 is used to determine the second session affected by the first PGW-U when it is determined that the first packet data network gateway user plane function entity PGW-U is abnormal; the communication module 1102 is used to determine the second session when the second session is received Sending a notification message to the first serving gateway control plane functional entity SGW-C when the uplink data message is received, and the notification message is used to notify the second session that the uplink data message is received.

In a specific design, the processing module 1101 is also used to record the identification of the PGW-U used in the session; the processing module 1101 determines the second session affected by the first PGW-U specifically as follows: The session with the identifier of the first PGW-U in the session is the second session affected by the first PGW-U.

Please refer to FIG. 11, which shows a schematic structural diagram of a network device according to an embodiment of the present application. The network device shown in FIG. 11 may be used to perform part or all of the functions of the first SGW-C in the method embodiment described in FIG. 9. The network device shown in FIG. 11 may include a processing module 1101 and a communication module 1102. among them:

The communication module 1102 is configured to receive a notification message from the user plane function entity SGW-U of the first serving gateway, and the notification message is used to notify the second session that the uplink data packet is received, and the second session is the abnormal first packet data network gateway The session affected by the user plane function entity PGW-U; the processing module 1101 is configured to delete the second session and instruct the user equipment corresponding to the second session to re-establish a PDN connection.

The embodiment of the present application provides a network device. The network device may be used to perform part or all of the functions of the first PGW-C in the method embodiment described in FIG. 10. The network device may include a processing module. among them:

The processing module is used for determining the third session affected by the first PGW-U when the first packet data network gateway user plane function entity PGW-U is detected to be abnormal; the processing module is also used for receiving the third session When the downlink signaling is performed, the third session is deleted, and the user equipment corresponding to the third session is instructed to re-establish the PDN connection.

In a specific design, the processing module is also used to record the identity of the PGW-U used in the session; the processing module determines the third session affected by the first PGW-U specifically as follows: The session with the identifier of the first PGW-U is the third session affected by the first PGW-U.

In a specific design, the network device also includes a communication module. When the communication module receives the signaling of the fourth session, it sends a message to the second PGW-U used in the fourth session according to the signaling of the fourth session; after the communication module retransmits the message to the second PGW-U, if If the first network device does not receive the response message of the message within the preset time period, the processing module deletes the fourth session and instructs the user equipment corresponding to the fourth session to re-establish the PDN connection.

Please refer to FIG. 12, which is a schematic structural diagram of a network device disclosed in an embodiment of the present application. As shown in FIG. 12, the network device includes a processor 1201, a memory 1202, and a communication interface 1203. Among them, the processor 1201, the memory 1202 and the communication interface 1203 are connected.

The processor 1201 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (digital signal processor, DSP), or an application-specific integrated circuit (ASIC). , Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The processor 1201 may also be a combination for realizing computing functions, for example, including one or more microprocessor combinations, DSP and microprocessor combinations, and so on.

Among them, the communication interface 1203 is used to implement communication with the access network device.

Wherein, the processor 1201 calls the program code stored in the memory 1202 to execute the steps performed by the MME, SGW-C, SGW-U, PGW-C, or SGW-U in the foregoing method embodiment.

Based on the same inventive concept, the principle of solving the problem by the network device provided in the embodiment of this application is similar to the principle of solving the problem by the MME, SGW-C, SGW-U, PGW-C, or SGW-U in the method embodiment of this application. For the implementation of the device, refer to the implementation of the method. For a concise description, it will not be repeated here.

In the above-mentioned embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in an embodiment, reference may be made to related descriptions of other embodiments.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: It is still possible to modify the technical solutions described in the foregoing embodiments, or equivalently replace some or all of the technical features; these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the application range.

Claims

A gateway selection system, characterized in that the gateway selection system includes a mobility management entity MME, multiple serving gateway control plane function entities SGW-C, and multiple serving gateway user plane function entities SGW-U, wherein:

The first SGW-C is configured to send the identifier of the first SGW-U to the MME when it is detected that the first SGW-U is abnormal, where the first SGW-C is the multiple SGW-Cs One of the SGW-C in the SGW-C, the first SGW-U is the SGW-U that is docked with the first SGW-C among the multiple SGW-Us;

The MME is configured to receive the identity of the first SGW-U from the first SGW-C;

The MME is further configured to determine a first session affected by the first SGW-U according to the identifier of the first SGW-U, and reselect a second SGW-C that has not failed for the first session;

The second SGW-C is used to reselect a second SGW-U that has not failed for the first session.
The gateway selection system according to claim 1, wherein:

The MME is also used to record the identification of the SGW-U used in the session in the session;

The MME determining the first session affected by the first SGW-U according to the identifier of the first SGW-U includes:

The MME determines that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U.
The gateway selection system according to claim 1 or 2, wherein the MME reselecting a second SGW-C that has not failed for the first session comprises:

When the MME receives the uplink signaling of the first session, the MME reselects a second SGW-C that is not faulty for the first session.
The gateway selection system according to any one of claims 1 to 3, wherein the gateway selection system further comprises multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user planes Functional entity PGW-U, where:

The first PGW-C is used to receive the identifier of the first SGW-U that is abnormal from the first PGW-U or the first SGW-C, and the first PGW-C is the multiple PGW- PGW-C docked with the first SGW-C in C, and the first PGW-U is the PGW-U docked with the first SGW-U and the first PGW-C among the plurality of PGW-Us PGW-U;

The first PGW-C is also used to determine the second session affected by the first SGW-U according to the identity of the first SGW-U, and is used to determine the second session affected by the first SGW-U when the downlink signaling of the second session is received When, sending a first message to the MME, where the first message is used to trigger the MME to reselect a non-faulty SGW-C for the second session;

The MME is further configured to receive the first message from the first PGW-C, and reselect a third SGW-C that has not failed for the second session according to the first message;

The third SGW-C is used to reselect a third SGW-U that has not failed for the second session.
The gateway selection system according to claim 4, wherein:

The first SGW-C is also used to send the identification of the SGW-U used in the session to the first PGW-C;

The first PGW-C is further configured to receive the identifier of the SGW-U used in the session from the first SGW-C, and record the identifier of the SGW-U corresponding to the session in the session;

The determining, by the first PGW-C, according to the identifier of the first SGW-U, the second session affected by the first SGW-U includes:

The first PGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.
The gateway selection system according to any one of claims 1 to 3, wherein the gateway selection system further comprises multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user planes Functional entity PGW-U, where:

The first SGW-C is further configured to determine a second session affected by the first SGW-U when an abnormality of the first SGW-U is detected;

The first PGW-C is configured to receive the first signaling corresponding to the second session, and send the second signaling corresponding to the second session to the first SGW-C according to the first signaling, The first PGW-C is the PGW-C that is docked with the first SGW-C among the plurality of PGW-Cs;

The first SGW-C is further configured to receive the second signaling from the first PGW-C, and send a response to the second signaling to the first PGW-C, the The response of the second signaling carries a cause value used to indicate that the context of the second session is not found;

The first PGW-C is further configured to receive a response of the second signaling from the first SGW-C, and send a first message to the MME, where the first message is used to trigger the MME Reselect a non-faulty SGW-C for the second session;

The MME is further configured to receive the first message from the first PGW-C, and reselect a third SGW-C that has not failed for the second session according to the first message;

The third SGW-C is used to reselect a third SGW-U that has not failed for the second session.
The gateway selection system according to claim 6, wherein:

The first SGW-C is also used to record the identifier of the SGW-U used in the session in the session;

The first SGW-C determining the second session affected by the first SGW-U includes:

The first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.
The gateway selection system according to any one of claims 1 to 7, wherein the gateway selection system further comprises multiple packet data network gateway control plane functional entities PGW-C and multiple packet data network gateway user planes Functional entity PGW-U, where:

The first PGW-U is used to determine a third session affected by the first SGW-U when an abnormality of the first SGW-U is detected, and the first PGW-U is the multiple PGWs -PGW-U docked with the first SGW-U in U;

The first PGW-U is also used to send a notification message to the first PGW-C when receiving a downlink data message of the third session, where the notification message is used to notify the third session that the downlink data message is received In a data message, the first PGW-C is the PGW-C that is docked with the first PGW-U among the plurality of PGW-Cs;

The first PGW-C is also used to receive the notification message from the first PGW-U and send a second message to the MME, where the second message is used to trigger the MME to become the first Three sessions re-select a non-faulty SGW-C;

The MME is further configured to receive the second message from the PGW-C, and reselect a fourth SGW-C that has not failed for the third session according to the second message;

The fourth SGW-C is used to reselect a fourth SGW-U that has not failed for the third session.
The gateway selection system according to claim 8, wherein:

The first PGW-U is also used to record the identification of the SGW-U used in the session in the session;

The determining, by the first PGW-U, of the third session affected by the first SGW-U includes:

The first PGW-U determines that the session with the identifier of the first SGW-U in the session is the third session affected by the first SGW-U.
A gateway selection method, characterized in that the method further includes:

When the first serving gateway control plane function entity SGW-C detects that the first serving gateway user plane function entity SGW-U docked with the first SGW-C is abnormal, it sends the first SGW-U to the mobility management entity MME The logo;

Receiving, by the MME, the identifier of the first SGW-U from the first SGW-C;

The MME determines the first session affected by the first SGW-U according to the identifier of the first SGW-U, and reselects a second SGW-C that has not failed for the first session;

The second SGW-C reselects a second SGW-U that has not failed for the first session.
The method according to claim 10, wherein the method further comprises:

The MME records the SGW-U identifier used by the session in the session;

The MME determining the first session affected by the first SGW-U according to the identifier of the first SGW-U includes:

The MME determines that the session with the identifier of the first SGW-U in the session is the first session affected by the first SGW-U.
The method according to claim 10 or 11, wherein the MME reselecting a second SGW-C that has not failed for the first session comprises:

When the MME receives the uplink signaling of the first session, the MME reselects a second SGW-C that is not faulty for the first session.
The method according to any one of claims 10 to 12, wherein the method further comprises:

The first PGW-C receives the identifier of the abnormal first SGW-U from the first PGW-U or the first SGW-C, where the first PGW-C is docked with the first SGW-C , The first PGW-U is a PGW-U docked with the first SGW-U and the first PGW-C;

Determining, by the first PGW-C, the second session affected by the first SGW-U according to the identifier of the first SGW-U;

When receiving the downlink signaling of the second session, the first PGW-C sends a first message to the MME, and the first message is used to trigger the MME to reselect one for the second session SGW-C without failure;

The MME receives the first message from the first PGW-C, and reselects a third SGW-C that is not faulty for the second session according to the first message;

The third SGW-C reselects a third SGW-U that has not failed for the second session.
The method of claim 13, wherein the method further comprises:

Sending, by the first SGW-C, an identifier of the SGW-U used in the session to the first PGW-C;

The first PGW-C receives the identifier of the SGW-U used in the session from the first SGW-C, and records the identifier of the SGW-U corresponding to the session in the session;

The determining, by the first PGW-C, according to the identifier of the first SGW-U, the second session affected by the first SGW-U includes:

The first PGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.
The method according to any one of claims 10 to 12, wherein the method further comprises:

When the first SGW-C detects that the first SGW-U is abnormal, determining the second session affected by the first SGW-U;

The first PGW-C receives the first signaling corresponding to the second session, and sends the second signaling corresponding to the second session to the first SGW-C according to the first signaling. One PGW-C is the PGW-C docked with the first SGW-C;

The first SGW-C receives the second signaling from the first PGW-C, and sends a response to the second signaling to the first PGW-C, the second signaling The response of contains a reason value indicating that the context of the second session is not found;

The first PGW-C receives the response of the second signaling from the first SGW-C, and sends a first message to the MME, where the first message is used to trigger the MME to become the first Second, the session selects a non-faulty SGW-C again;

The MME receives the first message from the first PGW-C, and reselects a third SGW-C that is not faulty for the second session according to the first message;

The third SGW-C reselects a third SGW-U that has not failed for the second session.
The method according to claim 15, wherein the method further comprises:

The first SGW-C records in the session the identifier of the SGW-U used in the session;

The first SGW-C determining the second session affected by the first SGW-U includes:

The first SGW-C determines that the session with the identifier of the first SGW-U in the session is the second session affected by the first SGW-U.
The method according to any one of claims 10 to 16, wherein the method further comprises:

When the first PGW-U detects that the first SGW-U is abnormal, it determines the third session affected by the first SGW-U, and the first PGW-U is connected to the first SGW-U. PGW-U docked;

When the first PGW-U receives the downlink data packet of the third session, it sends a notification message to the first PGW-C, where the notification message is used to notify the third session that the downlink data packet is received, The first PGW-C is a PGW-C docked with the first PGW-U;

The first PGW-C receives the notification message from the first PGW-U and sends a second message to the MME, where the second message is used to trigger the MME to reselect for the third session A non-faulty SGW-C;

The MME receives the second message from the PGW-C, and reselects a non-faulty fourth SGW-C for the third session according to the second message;

The fourth SGW-C reselects a fourth SGW-U that has not failed for the third session.
The method of claim 17, wherein the method further comprises:

The first PGW-U records the SGW-U identifier used by the session in the session;

The determining, by the first PGW-U, of the third session affected by the first SGW-U includes:

The first PGW-U determines that the session with the identifier of the first SGW-U in the session is the third session affected by the first SGW-U.