WO2018058618A1

WO2018058618A1 - Fault processing method and device

Info

Publication number: WO2018058618A1
Application number: PCT/CN2016/101284
Authority: WO
Inventors: 刘会勇; 曾侃
Original assignee: 华为技术有限公司
Priority date: 2016-09-30
Filing date: 2016-09-30
Publication date: 2018-04-05

Abstract

A fault processing method and device for reducing the possibility of service interruption of a UP (user plane). In the embodiments of the present invention, since a signalling processing network element may receive information sent by multi-party network elements, a fault determination task is handed over to the signalling processing network element. The signalling processing network element may comprehensively determine whether a user plane network element fails, a control plane network element fails, or a link between the control plane network element and the user plane network element fails by combining received first detection information and second detection information. Since information about multiple aspects may be comprehensively considered during fault determination, instead of only taking information about a single network element into consideration, the accuracy rate of a determination result is improved, so that subsequently, if a network element fails, processing may be performed according to the network element fault, and if the link fails, processing may be performed according to the link fault, thereby preventing service interruption of a fault-free UP as far as possible and guaranteeing the continuity of a service.

Description

Fault processing method and device

Technical field

The present invention relates to the field of communications technologies, and in particular, to a fault processing method and device.

Background technique

Currently, Serving GateWay (S-GW) and Packet Data Network GateWay (P-GW) are deployed centrally in the regional/provincial center, which is unable to meet the continuous growth of capacity performance, and given the future fifth-generation mobile The communication system (5G) needs for multiple service slicing. Therefore, the S-GW/P-GW gateway sinking distributed deployment becomes the future deployment trend. Under the trend of S-GW/P-GW gateway sinking distributed deployment, the 3rd Generation Partnership Project (3GPP) project initiated the control plane for S-GW/P-GW gateway nodes (Control) Plane, CP) / User Plane (UP) separation study.

Under the existing System Architecture Evolution (SAE) architecture, the S-GW and P-GW are split into Control Plane S-GW (SGW-C) according to the concept of CP/UP separation. User Plane S-GW (SGW-U), Control Plane Packet Network Gateway (Control Plane P-GW, PGW-C) and User Plane Packet Network Gateway (User Plane P-GW, PGW-U) ). The Gateway General Packet Radio Service Support Node (GGSN) function is included in the P-GW, and the PGW is also split into a Control Plane Gateway General Packet Radio Service Support Node (Control Plane GGSN, GGSN- C) and User Plane Gateway General Packet Radio Service Support Node (User Plane GGSN, GGSN-U), which will not be described separately.

The separation of the CP/UP causes the link between the CP and the UP inside the conventional S-GW/P-GW gateway to become a standard external 3GPP Sx interface. The Sx interface includes an Sxa interface between the SGW-C and the SGW-U, and an Sxb interface between the PGW-C and the PGW-U. After the CP/UP is separated, the CP is deployed centrally with the Control Plane Gateway (CGW), and the UP is distributed with the distributed gateway (DGW). The link between the CP and the UP is faulty. The probability will increase. The CGW can be regarded as including the functions of the SGW-C and the functions of the PGW-C. The DGW can be regarded as including the functions of the SGW-U and the functions of the PGW-U, and the GGSN-C can be regarded as being combined with the PGW-C. GGSN-U is considered to be in one set with PGW-U.

If the CP and the UP are normal, only the link between the CP and the UP is faulty, which does not actually affect the UP to continue to provide user service access services. Now CP and UP can detect each other. For the CP, whether it is an UP fault or a link fault between the CP and the UP, the CP considers it to be an UP fault and directly processes it according to the UP fault. For example, the CP will reselect UP for user reactivation. For UP, whether it is a CP fault or a link failure between the CP and the UP, the UP is considered to be a CP fault, and thus directly processes the fault according to the UP fault, for example, the UP releases the local service. If the link between the CP and the UP is faulty, the CP processes the fault according to the UP fault or the fault is processed according to the fault of the CP. This causes the service of the UP that is not faulty to be interrupted and the service experience of the user. It can be seen that the current test results are not accurate enough, which may cause the UP business to be interrupted.

Summary of the invention

The embodiment of the invention provides a fault processing method and device for reducing the possibility of service interruption of the UP.

In a first aspect, a fault processing method is provided, which is performed by a signaling processing network element, such as implemented by an MME. The method includes: the signaling processing network element receives the first detection information sent by the first control plane network element, where the first detection information is used to indicate the state of the first user plane network element obtained by the first control plane network element. The signaling processing network element receives the second detection information sent by the second user plane network element, where the second detection information is used to indicate the status of the first user plane network element obtained by the second user plane network element. The signaling processing network element determines the fault type according to the first probe information and the second probe information, where the fault type includes the first user plane network element fault, or a link fault between the first control plane network element and the first user plane network element. .

In the embodiment of the present invention, the signaling processing network element can receive the information sent by the multi-party network element, and therefore the task of performing the fault determination is handed over to the signaling processing network element. The signaling processing network element can comprehensively determine whether the user plane network element fault and the control plane network element are combined with the received first probe information and the second probe information. The fault is also a link fault between the control plane network element and the user plane network element. Because multiple aspects of information are comprehensively considered in the fault judgment, not only the information of a single network element is considered, but the accuracy of the judgment result is improved. Therefore, if the network element fails, the network element can be processed according to the network element failure. If the link is faulty, the link fault can be processed. The service interruption of the faultless UP can be avoided to ensure the continuity of the service or the fault in the UP. In this case, you can also restore the UP service as quickly as possible, and try not to affect the user's business experience.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the signaling processing network element determines the fault type according to the first probe information and the second probe information, by implementing the following manner: The second detection information indicates that the first user plane network element is faulty, and the signaling processing network element determines that the fault type is the first user plane network element fault; or, if the first detection information indicates that the first user plane network element fails, and the second The detection information indicates that the first user plane network element is normal, and the signaling processing network element determines that the fault type is normal for the first user plane network element, and the link between the first control plane network element and the first user plane network element is faulty.

That is to say, the signaling processing network element determines the fault type by comprehensively considering the first probe information and the second probe information. In this way, it can effectively determine whether the first user plane network element fault or the first A link fault between the control plane network element and the first user plane network element can effectively distinguish the network element fault and the link fault, so that different faults can be handled differently, and the link fault is avoided as much as possible. A bad experience such as business interruption caused by network element failure processing.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the signaling processing network element determines that the fault type is the first control plane network element and the first user plane network element. After the link failure occurs, the signaling processing network element can perform fault recovery processing. The fault recovery process includes, but is not limited to, the following two methods: the signaling processing network element re-selects the control plane network element for the first user plane network element, and sends the identifier of the first user plane network element to the reselected control plane network element. The re-selected control plane network element manages the first user plane network element; or the signaling processing network element instructs the first control plane network element to wait for link recovery.

The signaling processing network element can reselect the control plane network element and send it to the reselected control plane network element. Sending the identifier of the first user plane network element. Optionally, the signaling processing network element may send the re-selected control plane network element in addition to the identifier of the first user plane network element to the reselected control plane network element. Sending a fault indication, that is, indicating exactly where the fault occurred, the reselected control plane network element receives the information sent by the signaling processing network element, and then can know exactly where the fault occurs, and can be based on the first user plane network element. The identifier establishes a link with the first user plane network element in time, so that the network returns to normal as soon as possible. Alternatively, the signaling processing network element may also indicate that the first control plane network element is waiting for the link to be restored, and no other processing is required. Therefore, the restored first control plane network element can continue to be used, thereby improving the utilization rate of the network element.

With reference to the first aspect or the first possible implementation manner or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the first control plane network element is a control plane serving gateway The second user plane network element is a base station, the first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity; or, the first control plane network element is a control plane packet data network gateway, and the second The user plane network element is a user plane service gateway, the first user plane network element is a user plane packet data network gateway, and the signaling processing network element is a mobility management entity; or, the first control plane network element is a control plane serving gateway, and the second The user plane network element is a user plane packet data network gateway, the first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity.

Depending on the factors to be processed, the network elements may have different selection modes. The application scenarios supported by the embodiments of the present invention are applicable to the embodiments of the present invention.

In a second aspect, a fault processing method is provided, which is performed by a signaling processing network element, such as implemented by an MME. The method includes: the signaling processing network element obtains the first detection information, where the first detection information is used to indicate the state of the first control plane network element. The signaling processing network element receives the second detection information sent by the first user plane network element, where the second detection information is used to indicate the status of the second user plane network element obtained by the first user plane network element. The signaling processing network element determines the fault type according to the first probe information and the second probe information, where the fault type includes only the first control plane network element fault, or only the second user plane network element fault, or the first control plane network element and the first control plane Both user plane network elements are faulty. Then, if the first control plane network element and the second user plane network element both fail, and the first control plane network element manages the second user plane network element, The signaling processing network element releases the service associated with the first control plane network element and/or the second user plane network element.

In the embodiment of the present invention, if the signaling processing network element determines that both the first control plane network element and the second user plane network element are faulty, and the first control plane network element manages the second user plane network element, that is, the first fault The control plane network element and the second user plane network element are interconnected network elements, and the signaling processing network element can locally release the service associated with the first control plane network element and/or the second user plane network element, so that the part The service can be restored on other network elements to minimize the length of business interruption.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the signaling processing network element determines, according to the first detection information and the second detection information, a fault type, by: if the first detection information indicates If the control plane network element fails, the signaling processing network element determines that the first control plane network element is faulty; or, if the second detection information indicates that the second user plane network element fails, the signaling processing network element determines the second user plane network. Meta failure.

That is, the signaling processing network element determines whether the first control plane network element and the second user plane network element are faulty according to the first probe information and the second probe information, and the determining manner is relatively straightforward, and the faulty network element can be locked relatively quickly.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, after the signaling processing network element determines the fault type, if only the first control plane network element fails, signaling The processing network element re-selects the control plane network element for the second user plane network element, and sends the identifier of the second user plane network element to the reselected control plane network element, so that the reselected control plane network element manages the second user plane network. yuan.

If only the first control plane network element fails, the signaling processing network element may reselect the control plane network element, and send the identifier of the second user plane network element to the reselected control plane network element, optionally, the signaling processing network In addition to sending the identifier of the second user plane network element to the reselected control plane network element, the element may also send a fault indication to the reselected control plane network element, that is, indicating exactly where the fault occurred, and then reselecting the control. After receiving the information sent by the network element, the network element can learn exactly where the fault occurs, and can establish a link with the second user plane network element according to the identifier of the second user plane network element, so that the network Return to normal as soon as possible. In addition, in this process, since the second user plane network element has no fault, the service of the second user plane network element can continue, and the possibility of service interruption is minimized.

With reference to the second aspect or the first possible implementation manner or the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the signaling processing network element obtains the first detection information, The method is as follows: the signaling processing network element receives the first detection information sent by the second control plane network element, where the first detection information is used to indicate the state of the first control plane network element obtained by the second control plane network element; or The signaling processing network element detects the first control plane network element, and generates first detection information according to the detection result.

That is, the signaling processing network element may directly detect the first control plane network element to obtain the first detection information, or may also be the second control plane network element to detect the first control plane network element, and send the first detection information. For the signaling processing network element, the signaling processing network element obtains the first detection information in a flexible manner. In practical applications, an appropriate manner can be selected according to the difference of the network elements that need to be detected.

With reference to the second aspect or the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the signaling processing network element is a mobile management entity, and the first control plane network element is a control plane The serving gateway, the first user plane network element is a base station, and the second user plane network element is a user plane serving gateway; or the signaling processing network element is a mobility management entity, and the second control plane network element is a control plane serving gateway, first The control plane network element is a control plane packet data network gateway, the first user plane network element is a user plane service gateway, and the second user plane network element is a user plane packet data network gateway.

In a third aspect, a fault processing method is provided, which is implemented by an SDN controller. The method includes: the SDN controller detects the first switch, and obtains the first probe information. The SDN controller receives the second probe information sent by the second switch, where the second probe information is used to indicate the status of the first switch obtained by the second switch. The SDN controller determines the fault type according to the first probe information and the second probe information, where the fault type includes a first switch fault or a link fault between the SDN controller and the first switch.

In the embodiment of the present invention, the SDN controller can receive the second detection information sent by the second switch, and the SDN controller can combine the received information. The first detection information and the second detection information comprehensively determine the type of the fault, because comprehensive information is considered in the judgment of the fault, and not only the information of the single network element is considered, and the accuracy of the judgment result is improved, thereby If the fault is faulty, the fault can be processed according to the fault of the NE. If the link is faulty, the fault can be processed according to the link fault. The service interruption of the faultless switch can be avoided to ensure the continuity of the service. You can also restore the services of the switch as quickly as possible without affecting the user's service experience.

In a fourth aspect, a fault processing method is provided, the method being performed by a first network element. The method includes: the first network element detects that the state of the second network element is a fault, and the first network element generates the detection information according to the detection of the second network element, and sends the detection information to the signaling processing network element, and the detection information The identifier of the second network element is carried in, and the detection information is used to determine the type of the fault.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first network element is a control plane network element or a user plane network element, and the second network element is a control plane network element or a user plane network element.

That is, the first network element that is the control plane network element or the user plane network element can detect the state of the second network element. If the state of the second network element is known to be faulty, the first network element can temporarily not perform fault processing, for example, The service information associated with the second network element is not released locally, but the detection information (the detection information may include the first detection information or the second detection information as described in the foregoing aspects) is sent to the signaling processing network element, and the detection is performed. The information may carry the identifier of the second network element. After receiving the detection information, the signaling processing network element may determine, according to the identifier of the second network element carried in the detection information, that the status of the second network element is faulty. Therefore, the signaling processing network element can comprehensively determine the fault type according to the probe information sent by the multi-party network element, improve the fault judgment accuracy, and can distinguish whether the network element fault or the link fault is as far as possible. If the fault occurs on the NE, the fault can be processed according to the fault of the NE. If the link is faulty, the fault can be processed according to the link fault. You can avoid service interruption of the faultless UP and ensure the continuity of the service or the fault in the UP. Under the same time, you can also restore the UP service as quickly as possible, and try not to affect the user's business experience.

In a fifth aspect, a signaling processing network element is provided, where the signaling processing network element includes a receiver and a processor. The receiver is configured to receive the first probe information sent by the first control plane network element, and receive the second probe information sent by the second user plane network element. The first probe information is used to indicate the first control plane network The state of the first user plane network element obtained by the element, and the second probe information is used to indicate the state of the first user plane network element obtained by the second user plane network element. The processor is configured to determine a fault type according to the first probe information and the second probe information, where the fault type includes a first user plane network element fault, or a link fault between the first control plane network element and the first user plane network element.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the processor is configured to determine a fault type according to the first probe information and the second probe information, including: if the first probe information and the second probe information are both indicated If the first user plane network element is faulty, the fault type is determined to be the first user plane network element fault; or, if the first probe information indicates that the first user plane network element is faulty, and the second probe information indicates that the first user plane network element is normal, Then, the fault type is determined to be that the first user plane network element is normal, and the link between the first control plane network element and the first user plane network element is faulty.

With reference to the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the signaling processing network element further includes a transmitter. The processor is further configured to: after determining that the fault type is a link fault between the first control plane network element and the first user plane network element, reselect the control plane network element for the first user plane network element, and pass the transmitter. Sending, to the reselected control plane network element, the identifier of the first user plane network element, so that the reselected control plane network element manages the first user plane network element; or determining the fault type as the first control plane network element and the first After the link between the user plane network elements fails, the first control plane network element is instructed to wait for link recovery.

With reference to the fifth aspect or the first possible implementation manner or the second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the first control plane network element is a control plane serving gateway The second user plane network element is a base station, the first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity; or, the first control plane network element is a control plane packet data network gateway, and the second The user plane network element is a user plane service gateway, the first user plane network element is a user plane packet data network gateway, and the signaling processing network element is a mobility management entity; or, the first control plane network element is a control plane serving gateway, and the second The user plane network element is a user plane packet data network gateway, the first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity.

In a sixth aspect, a signaling processing network element is provided, the signaling processing network element including a processor and a receiver. The processor is configured to obtain first probe information, where the first probe information is used to indicate the first control The state of the face network element. The receiver is configured to receive the second probe information that is sent by the first user plane network element, where the second probe information is used to indicate the state of the second user plane network element obtained by the first user plane network element. The processor is further configured to determine a fault type according to the first probe information and the second probe information, where the fault type includes only the first control plane network element fault, or only the second user plane network element fault, or the first control plane network element and the first control plane Both user plane network elements are faulty. If the fault type is that the first control plane network element and the second user plane network element are both faulty, and the first control plane network element manages the second user plane network element, the processor releases the first control plane network element and/or the second The service associated with the user plane network element.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the processor is configured to determine a fault type according to the first probe information and the second probe information, including: if the first probe information indicates the first control plane network element If the second probe information indicates that the second user plane network element is faulty, the second user plane network element fault is determined.

With reference to the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the signaling processing network element further includes a transmitter. The processor is further configured to: after determining the fault type, if the fault type is only the first control plane network element fault, reselect the control plane network element for the second user plane network element, and use the transmitter to reselect the control plane. The network element sends the identifier of the second user plane network element, so that the reselected control plane network element manages the second user plane network element.

With reference to the sixth aspect, or the first possible implementation manner of the sixth aspect, or the second possible implementation manner, in a third possible implementation manner of the sixth aspect, the processor is configured to obtain the first detection information, including: Acquiring the first detection information sent by the second control plane network element received by the receiving unit, where the first detection information is used to indicate the state of the first control plane network element obtained by the second control plane network element; or, for the first control plane The network element performs detection, and generates first detection information according to the detection result.

With reference to the third possible implementation manner of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the signaling processing network element is a mobility management entity, and the first control plane network element is a control plane serving gateway, A user plane network element is a base station, and a second user plane network element is a user plane serving gateway; or, the signaling processing network element is a mobility management entity, and the second control plane network element is a control plane serving gateway, and the first control plane network element For the control plane packet data network gateway, the first user plane network element is a user plane service gateway, and the second user plane network element is a user plane packet data network gateway.

In a seventh aspect, an SDN controller is provided, the SDN controller comprising a processor and a receiver. The processor is configured to detect the first switch to obtain the first probe information. The receiver is configured to receive the second probe information sent by the second switch, where the second probe information is used to indicate the status of the first switch obtained by the second switch. The processor is further configured to determine a fault type according to the first probe information and the second probe information, where the fault type includes a first switch fault, or a link fault between the SDN controller and the first switch.

In an eighth aspect, a network element is provided, the network element including a processor and a transmitter. The processor is configured to detect, by detecting, that the state of the second network element is a fault, and generate the probe information according to the detection of the second network element. The transmitter is configured to send the probe information to the signaling processing network element, where the probe information carries the identifier of the second network element, and the probe information is used to determine the fault type.

With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, the network element is a control plane network element or a user plane network element, and the second network element is a control plane network element or a user plane network element.

In a ninth aspect, a signaling processing network element is provided, the signaling processing network element comprising a functional unit for performing the method provided by the first aspect or any one of the possible implementations of the first aspect.

In a tenth aspect, a signaling processing network element is provided, the signaling processing network element comprising a functional unit for performing the method provided by the second aspect or any one of the possible implementations of the second aspect.

In an eleventh aspect, an SDN controller is provided, the SDN controller comprising functional units for performing the method provided by the third aspect or any of the possible implementations of the third aspect.

In a twelfth aspect, a network element is provided, the network element being a first network element, the network element comprising a functional unit for performing the method provided by the fourth aspect or any one of the possible implementation manners of the fourth aspect.

A thirteenth aspect, a computer storage medium for storing computer software instructions for use in the above-described signaling processing network element, comprising any of the possible implementations for performing the first aspect or the first aspect Let the program designed by the network element be processed.

A fourteenth aspect, a computer storage medium for storing computer software instructions for use in the signaling processing network element, comprising any of the possible implementations for performing the second aspect or the second aspect Let the program designed by the network element be processed.

In a fifteenth aspect, a computer storage medium is provided for storage as the SDN controller Computer software instructions for use, comprising a program designed to perform the SDN controller in any one of the possible implementations of the third aspect or the third aspect.

In a sixteenth aspect, a computer storage medium is provided for storing computer software instructions for use in the first network element, and includes any possible implementation manner for performing the fourth aspect or the fourth aspect. The program designed by the network element.

In the embodiment of the present invention, the signaling processing network element comprehensively considers multiple aspects of information when performing fault diagnosis, and not only considers the information of a single network element, but also improves the accuracy of the judgment result, so that if the network element fails, If the link is faulty, you can perform the fault according to the link fault. You can avoid service interruption of the faultless UP and ensure the continuity of the service. In the case of the UP fault, you can also recover the fault as quickly as possible. UP business, try not to affect the user's business experience.

DRAWINGS

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

FIG. 1 is a schematic diagram of a network architecture applied to an embodiment of the present invention; FIG.

2 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 3 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 4 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 5 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 6 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 8 is a flowchart of a fault processing method according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a computer device according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a signaling processing network element according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention;

FIG. 13 is a schematic structural diagram of a first network element according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the embodiments of the present invention.

The techniques described herein may be used in various communication systems, such as Long Term Evolution (LTE) systems, 4.5G systems, or 5G systems, as well as other such communication systems or evolved systems that will emerge in the future. Moreover, the technical solution provided in this paper is not only applicable to the 3rd Generation Partnership Project (3GPP) access method, but also applicable to the control plane and user plane in the non-3GPP (Non-3GPP) access mode. Separation situation.

Hereinafter, some of the terms in the embodiments of the present invention will be explained to facilitate understanding by those skilled in the art.

1) User Equipment (UE), which is a device that provides voice and/or data connectivity to a user, for example, may include a handheld device with wireless connectivity, or a processing device connected to a wireless modem. The user equipment can communicate with the core network via a Radio Access Network (RAN) to exchange voice and/or data with the RAN. The user equipment may also be referred to as a wireless terminal device, a mobile terminal device, a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile Station, a Remote Station, and a Pickup Station. Access Point (AP), Remote Terminal, Access Terminal, User Terminal, User Agent, User Device, etc. For example, the user equipment may include a mobile telephone (or "cellular" telephone), a computer with a mobile terminal device, a dedicated terminal device in the NB-IoT, portable, pocket, handheld, computer built-in or vehicle-mounted Moving device. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), etc. .

2) Network devices, also known as network elements. For example, the network device includes a control plane network element, a user plane network element, or a signaling processing network element. The network elements in the embodiment of the present invention may be physical devices or logical devices.

In a network architecture where the control plane (or signaling plane) is separated from the user plane (or the forwarding plane), the S-GW is split into SGW-C and SGW-U, and the PGW is split into PGW-C and PGW. -U. Among them, the SGW-C and the PGW-C as the control plane may be components of the CGW. Similarly, the SGW-U and the PGW-U as the user plane may also be components of the DGW. One CGW can manage multiple DGWs, and one DGW can belong to multiple CGWs. Among them, CGW and CP can be understood as the same concept, and DGW and UP can be understood as the same concept.

The control plane network element in the embodiment of the present invention may include a CGW, or in a future communication system (for example, a 5G system), the current Mobility Management Entity (MME) and the CGW may be (or It also includes other devices) to merge to form a new control plane network element, or the new control plane network element may also include other possible network devices for implementing the functions of the control plane.

The user plane network element in the embodiment of the present invention may include a DGW, or may also include other possible network devices for implementing functions of the user plane.

In addition, in the embodiment of the present invention, the user plane network element may further include an access network element, such as a base station (for example, an access point). A base station may specifically refer to a device in an access network that communicates with a wireless terminal over one or more sectors over an air interface. The base station can be used to convert the received air frame with an Internet Protocol (IP) packet as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network can include an IP network. . The base station can also coordinate attribute management of the air interface. For example, the base station may be an evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in a system such as Long Term Evolution (LTE) or Long Term Evolution (LTE-A). The embodiment of the invention is not limited.

In the embodiment of the present invention, the signaling processing network element mainly performs the fault determination work, and the signaling processing network element may be implemented by using the MME, or may also be implemented by other network devices.

Alternatively, the signaling processing network element in the embodiment of the present invention may also be implemented by a controller (Controller) in a Software Defined Network (SDN), which is hereinafter referred to as an SDN controller. In this case, the user plane network element may include a switch (Switch) in the SDN.

3) In the embodiment of the present invention, the concept of "User Bearer Context" may be a subordinate concept of the concept of "business". For example, if the service is interrupted, the user session context of the service may be interrupted or lost.

4) The terms "system" and "network" in the embodiments of the present invention may be used interchangeably. "Multiple" means two or more. "and/or", describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. In addition, the character "/", unless otherwise specified, generally indicates that the contextual object is an "or" relationship.

The network architecture applied in the embodiment of the present invention is an architecture in which the control plane and the user plane are separated, and is described below with reference to the accompanying drawings.

FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention. In FIG. 1, the signaling processing network element is implemented by using an MME as an example. In Figure 1, the user equipment is connected to the base station through the Uu interface, and the base station is connected to the SGW-U in the DGW through the S1-U interface. The SGW-U is connected to the PGW-U in the same DGW through the S5/S8-U interface, and the PGW-U passes. The SGi interface is connected to the Internet. The relationship between the PGW-U and the Internet connection is not shown in Figure 1. In addition, the base station is connected to the MME through the S1-MME interface, and the MME is connected to the SGW-C in the CGW through the S11 interface, and the SGW-C is connected to the PGW-C in the same CGW through the S5/S8-C interface. Of course, the SGW-C can also The PGW-C in the different CGWs is connected, which is not shown in FIG. The SGW-C connects to the SGW-U through the Sxa interface, and the PGW-C connects to the PGW-U through the Sxb interface. It can be understood that the CGW in FIG. 1 manages the DGW, specifically, the SGW-C manages the SGW-U, and the PGW-C manages the PGW-U.

The name of the interface and the name of the network element introduced in the embodiment of the present invention do not constitute a pair. The limitations of the device itself may also have other names in the application, interfaces and network elements.

Currently, heartbeat messages are generally exchanged between the CP and the UP. For example, the CP periodically sends a heartbeat message to the UP. After receiving the heartbeat message, the UP sends a response message to the CP. Alternatively, the UP periodically sends a heartbeat message to the CP. After receiving the heartbeat message, the CP sends a response message to the UP. Then, if the CP does not receive the heartbeat message or the response message sent by the UP for a long time, the CP determines that the UP is faulty, then the CP enters the fault processing flow of the UP. For example, the CP will reselect the UP for user reactivation.

Similarly, if the UP does not receive the heartbeat message or the response message sent by the CP for a long time, the UP determines that the CP is faulty, then the UP enters the fault handling process of the CP, for example, the UP releases the local service.

The CP has not received the heartbeat message or the response message sent by the UP for a long time, or the heartbeat message or the response message sent by the CP that has not been received by the CP for a long time may be an UP fault or a CP fault, or may be a CP and an UP. The link between the faults. It can be seen that whether the UP is faulty or the link between the CP and the UP is faulty, the CP is currently considered to be an UP fault, and is directly processed according to the UP fault. Regardless of whether the CP is faulty or the link between the CP and the UP is faulty, the UP is uniformly considered to be a CP fault, and thus is directly processed according to the CP fault. If the link between the CP and the UP is faulty, the CP processes the fault according to the UP fault, or the UP processes the fault according to the CP fault, which causes the service of the UP that is not faulty to be interrupted or lost. It will be longer and greatly affect the user's business experience. It can be seen that the accuracy of the detection result of the CP or the UP is not high, which may cause the service of the UP to be interrupted or lost.

In the embodiment of the present invention, the signaling processing network element can receive the information sent by the multi-party network element, and therefore the task of performing the fault determination is handed over to the signaling processing network element. The signaling processing network element can comprehensively determine whether the user plane network element fault, the control plane network element fault, or the link fault between the control plane network element and the user plane network element is combined with the received first probe information and the second probe information. Because the multi-faceted information will be comprehensively considered in the judgment of the fault, not just the information of the single network element, the accuracy of the judgment result is improved. If the fault occurs on the user plane network element, the fault can be processed according to the fault of the network element on the control plane. If the fault occurs on the control plane network element, the link fault can be processed. In the case of a link fault, the service interruption of the fault-free UP can be avoided as much as possible, and the service continuity can be ensured. In the case of an UP fault, the UP service can be restored as quickly as possible without affecting the user experience.

The network architecture and the device provided by the embodiment of the present invention are described above. The method provided by the embodiment of the present invention is described below with reference to the accompanying drawings. In the embodiment shown in FIG. 2 to FIG. 7 to be described later, the network architecture shown in FIG. 1 is taken as an example. According to the above description, those skilled in the art naturally know that the application scenario of the embodiment of the present invention is not limited to this. .

An embodiment of the invention provides a fault processing method. In the embodiment of the present invention, the first control plane network element is configured to detect that the state of the first user plane network element is a fault, and the first control plane network element generates the first probe information according to the detection of the first user plane network element, and Sending the first probe information to the signaling processing network element. In addition, the second user plane network element learns that the state of the first user plane network element is faulty, and the second user plane network element generates second detection information according to the detection of the first user plane network element, and the second detection information is also Send to the signaling processing network element. The signaling processing network element determines the fault type according to the first probe information and the second probe information. The technical solution provided by the embodiment of the present invention can effectively determine whether the user plane network element fault or the link fault. In the following description, the first control plane network element is SGW-C, the first user plane network element is SGW-U, the second user plane network element is a base station, and the signaling processing network element is an MME. ,as shown in picture 2.

S21 and SGW-C know that the state of the SGW-U is a fault.

The SGW-C can detect the state of the SGW-U through the heartbeat message or other signaling messages on the Sx interface. For example, the SGW-C periodically sends a heartbeat message to the SGW-U, and the SGW-U sends a response message to the SGW-C after receiving the heartbeat message, or the SGW-U periodically sends a heartbeat message to the SGW-C, and the SGW-C receives the heartbeat. The message will be sent to the SGW-U after the message. If the SGW-C does not receive the response message or the heartbeat message sent by the SGW-U for a long time, the SGW-C determines that the SGW-U is faulty.

In the embodiment of the present invention, after the SGW-C learns that the status of the SGW-U is faulty, the SGW-C keeps the service associated with the SGW-U locally and continues to perform normally.

The SGW-C can identify the SGW-U fault after determining that the SGW-U is faulty, but can still keep the service associated with the SGW-U from continuing normally. In this way, users can be prevented from going offline. The volume keeps the business going.

S22. The SGW-C sends the first probe information to the MME, where the first probe information is generated by the SGW-C according to the detection result, that is, the first probe information is used to indicate the status of the SGW-U obtained by the SGW-C. .

If the SGW-C determines that the SGW-U is faulty, the identifier of the faulty SGW-U may be carried in the first probe information. For example, the identifier of the SGW-U may be the IP address of the forwarding plane of the SGW-U, or other identifiers used to identify the identity of the SGW-U. If the SGW-C determines that the SGW-U is fault-free, the SGW-C may not carry the identifier of the faulty SGW-U in the first probe information, and may set a detection period for the MME, according to receiving in the detection period. The identifier of the faulty SGW-U carried by the first probe information sent by the SGW-C determines which SGW-Us are faulty. Alternatively, the SGW-C may not send the first probe information to the MME, and if the MME does not receive the first probe information sent by the SGW-C in the detection period, the default SGW-C detection result to the SGW-U is normal. Therefore, the MME can learn the detection result of the SGW-C accordingly.

For example, the SGW-C sends the first probe information to the MME through the extended S11 interface message. For example, the extended S11 interface message is an Echo Request message, or may be a newly added fault processing message or the like.

As described above, the SGW-C learns that the state of the SGW-U is faulty. Since the SGW-C and the SGW-U are mutually detected, the SGW-C can know that the state of the SGW-U is faulty, and the same. SGW-U can also know that the status of SGW-C is faulty.

After the SGW-U learns that the status of the SGW-C is faulty, the SGW-C can still maintain the normal service of the SGW-C.

The SGW-U can identify the SGW-C fault after determining that the SGW-C is faulty, but can still keep the service associated with the SGW-C from proceeding normally. In this way, users can be prevented from going offline and the service can be continued.

S23. The base station learns that the state of the SGW-U is a fault.

The base station may detect the state of the sensing SGW-U based on the data transmission channel of the user plane, thereby determining whether the SGW-U is faulty.

S24. The base station sends the second probe information to the MME, where the second probe information is generated by the base station according to the detection result, that is, the second probe information is used to indicate the status of the SGW-U obtained by the base station.

If the base station determines that the SGW-U is faulty, the second probe information may carry the identifier of the faulty SGW-U. If the base station determines that the SGW-U is faultless, the base station may not carry the faulty SGW in the second probe information. The identifier of the -U, for the MME, may set a detection period, and determine which SGW-Us are faulty according to the identifier of the fault SGW-U carried by the second probe information sent by the base station received in the detection period. Or the base station may not send the second probe information to the MME, if the MME does not receive the second probe information sent by the base station in the detection period, the default base station detects the SGW-U as normal, that is, the user plane data. The transmission channel is normal, so that the MME can learn the detection result of the base station accordingly.

After the base station learns that the status of the SGW-U is faulty, the local device may have different processing manners for the local service associated with the SGW-U. Correspondingly, the base station sends the second detection information to the MME in different manners. The following is a brief introduction.

method one:

In the first mode, if the UP (for example, the base station) learns that the state of the other UP (for example, the SGW-U) is a fault, the UP locally releases the service associated with another UP, and the UP may be in the MME due to the release of the service. The triggered message carries the second probe information.

For example, the UE Context Release Request message sent by the base station to the MME may carry the second probe information. If the base station learns that the status of the SGW-U is a fault, the base station may send an S1UE Context Release Request message to the MME for all services associated with the SGW-U, that is, send an S1UE Context Release Request message to the MME, where the S1UE Context Release Request message is The Cause Indicates can be identified as S1-U Failure. Optionally, the S1UE Context Release Request message may also carry the identifier of the faulty SGW-U. In this way, after receiving the S1UE Context Release Request message, the MME can know the detection result of the base station. In addition, the MME may further send an S1 User Equipment Context Release Command (UE Context Release Command) message to the base station to instruct the base station to release the air interface and the local Local business.

Method 2:

In the second mode, if the UP (for example, the base station) learns that the status of the other UP (for example, the SGW-U) is faulty, the UP can continue to maintain the normal association with the other UP. The user goes offline, allowing the business to continue. The UP may send the second probe information to the MME by using an existing message or a newly added fault processing message or the like. For example, if the base station learns that the state of the SGW-U is a fault, the base station continues to maintain the SGW-U-related service locally, and the base station sends the second probe information to the MME through the extended S1-MME interface message.

Among them, S21-S22 and S23-S24 can be regarded as two parts, and the execution order of these two parts can be arbitrary.

S25. The MME determines a fault type according to the first probe information and the second probe information, where the fault type includes an SGW-U fault, or a link fault between the SGW-C and the SGW-U.

For example, the MME combines the identifier of the faulty SGW-U carried in the first probe information, and the identifier of the faulty SGW-U carried in the second probe information or the SGW-U associated with the user whose indication indicates the S1-U Failure. The identifier identifies whether it is a SGW-U failure or a link failure between SGW-C and SGW-U.

In a possible implementation, if the identifier of the faulty SGW-U carried in the second probe information includes the identifier of the faulty SGW-U carried in the first probe information, or the Cause Indicates identifier in the second probe information is S1 The identifier of the SGW-U associated with the user of the -U Failure includes the identifier of the faulty SGW-U carried in the first probe information, that is, the first probe information and the second probe information both indicate that the SGW-U is faulty, and the MME determines the SGW. -U failure.

In a possible implementation, if the identifier of the faulty SGW-U carried in the second probe information does not include the identifier of the faulty SGW-U carried in the first probe information, or the Cause Indicates identifier in the second probe information is The identifier of the SGW-U that is associated with the user-initiated SGW-U of the S1-U Failure does not include the identifier of the faulty SGW-U carried in the first probe information, or the MME does not receive the second probe information in the detection period, that is, the first probe information. Instructing the SGW-U to fail, and the second probe information indicates that the SGW-U is normal, the MME determines that the SGW-U is normal, and the link between the SGW-C and the SGW-U is faulty.

S26. The MME performs fault recovery processing.

In the embodiment of the present invention, the MME may perform link failure recovery processing in combination with a predefined link failure processing policy. The link fault handling policy may be predefined by the operator or may be predefined by a protocol or a standard. The link fault handling strategy in the embodiment of the present invention includes but is not limited to the following:

1. UP fault handling strategy.

The MME may acquire the SGW-C of the failed SGW-U home association based on the user session context, ie, the SGW-C of the SGW-U for managing the fault. The MME sends an extended S11 interface message to the SGW-C, instructing the SGW-C to initiate fault processing of the SGW-U. The extended S11 interface message sent by the MME to the SGW-C may carry the identifier of the faulty SGW-U, the fault service processing indication, and the like. Specifically, the fault handling mode of the user plane network element is related to the deployment mode of the user plane network element. The embodiments of the present invention provide several types of UP deployment modes. The following describes how to implement the fault processing of the UP in different deployment modes.

Deployment mode 1: A CP manages multiple UPs, and a load balancing deployment between multiple UPs managed by one CP. Then, if the UP fails, the CP can release the service corresponding to the failed UP, and the user equipment served by the failed UP needs to reactivate the selection to other UPs. In this deployment mode, the faulty UP is handled in a simple manner. However, the service corresponding to the fault UP may be lost. The service recovery time is long and the user experience may not be very good.

Deployment mode 2: N+1 backup deployment between multiple UPs managed by one CP, that is, multiple UPs managed by one CP include N primary UPs and one standby UP. If a primary UP fails, the CP loads the user's session context of the failed primary UP to the standby UP based on the user session context of the primary UP saved locally by the CP, thereby restoring the user's service. In this deployment mode, most services corresponding to the fault UP can be recovered. However, since the backup of the user session context of the fault UP to the CP is performed periodically, the user service context that is not backed up in time during the backup period may still be lost, and the time required for the entire service recovery is long. There may still be a business interruption, and the user experience is general.

Deployment mode 3: Multiple UP (N-way) mode redundancy between multiple UPs managed by one CP. UP is used for main purposes, but certain redundant resources are reserved between UPs. If a certain UP is faulty, the CP scatters the user session context of the failed UP to other UPs based on the user session context of the UP saved locally by the CP, thereby restoring the user's service. In this deployment mode, the service recovery time and service integrity required for the fault UP are similar to those of the deployment mode 2.

Deployment mode 4: A multiple-upup between multiple UPs managed by a CP is a 1+1 backup mode. That is, one primary UP corresponds to one standby UP. In this deployment mode, the primary UP and the standby UP can detect each other. If a primary UP is faulty, the standby UP corresponding to the primary UP can be switched to the primary UP to continue to provide services. In this deployment mode, user service recovery time is shorter, service interruption time is shorter, and user experience is better.

2. Reselect the control plane network element strategy.

That is, the MME can reselect the CP, re-establish the link between the reselected CP and the UP, and do not need to continue to perform service processing through the faulty link, so that the service can continue as soon as possible.

In this link failure handling strategy, if the MME determines that the link between the CP and the UP is faulty, the MME may reselect the CP. After the CP is reselected, the MME may send a Modify Bearer Request message to the reselected CP. The Modify Bearer Request message may be extended to carry the Sx link recovery indication and may carry the UP identifier. In addition, in order to enable the service to be restored as soon as possible, the Modify Bearer Request message may also carry the address of the original CP, so that the reselected CP can obtain the service information of the UP from the original CP.

After receiving the Modify Bearer Request message, the reselected CP may trigger an Sx Session Modification message according to the Sx link recovery indication carried therein to restore the link between the UP and the UP.

After the link between the reselected CP and the UP is restored, the CP may send a Modify Bearer Response message to the MME, where the Modify Bearer Response message may be extended to indicate that the Sx link has returned to normal.

For example, in the embodiment of the present invention, the MME may reselect the SGW-C, and re-establish the link between the reselected SGW-C and the SGW-U, without continuing to perform service processing through the faulty link. Enable the business to continue as soon as possible. Wherein, the MME determines the link between the SGW-C and the SGW-U. In case of failure, the MME can reselect SGW-C. After the SGW-C is reselected, the MME may send a Modify Bearer Request message to the reselected SGW-C. The Modify Bearer Request message may be extended to carry the Sx link recovery indication and may carry the identifier of the SGW-U. In addition, in order to enable the service to be restored as soon as possible, the original SGW-C address may be carried in the Modify Bearer Request message, so that the reselected SGW-C can obtain the service information of the SGW-U from the original SGW-C. .

After receiving the Modify Bearer Request message, the reselected SGW-C may trigger the Sx Session Modification message according to the Sx link recovery indication carried therein to restore the link with the SGW-U.

After the link between the reselected SGW-C and the SGW-U is restored, the SGW-C may send a Modify Bearer Response message to the MME, where the indication of the Sx link may be extended in the Modify Bearer Response message. Back to normal.

3. Wait for the link recovery strategy.

That is, the MME may indicate that the original CP does not perform processing and wait for link recovery between the CP and the UP.

In this link fault handling policy, the MME does not reselect the CP, but can send an extended S11 interface message, such as an Echo Request message or a newly added fault handling message, to the original CP. The extended S11 interface message may carry the identifier of the failed UP, and may carry an indication of waiting for the Sx link to recover. After receiving the extended S11 interface message, the CP waits for the Sx link recovery indication carried in the process, and does not process, waiting for the link between the CP and the UP to resume.

4. Release the business strategy.

That is, the MME can locally release all services associated with the faulty network element.

5. Wait for the NE recovery policy.

That is, the MME may wait for the fault recovery of the faulty network element without processing. In this way, after the faulty network element is restored, the faulty network element becomes a normal network element again, and can continue to be utilized, and the original service can be continued, without replacing other network element processing in the middle, thereby reducing the possibility of user session information loss. Sexuality also improves the utilization of network elements.

For example, in the embodiment of the present invention, the MME may indicate that the original SGW-C does not process, and waits for link recovery between the SGW-C and the SGW-U. Where MME determines SGW-C and If the link between the SGW and the U is faulty, the MME does not reselect the SGW-C, but sends an extended S11 interface message, such as an Echo Request message or a newly added fault handling message, to the original SGW-C. The extended S11 interface message may carry the identifier of the faulty SGW-U, and may carry an indication of waiting for the Sx link to recover. After receiving the extended S11 interface message, the SGW-C waits for the link recovery between the SGW-C and the SGW-U according to the waiting Sx link recovery indication carried in the SGW-C.

The foregoing link fault handling strategies are only examples, and other link fault handling strategies may be implemented in the actual application, which are all within the protection scope of the embodiments of the present invention.

In a possible implementation manner, if the MME determines that the SGW-U is faulty, and the link between the SGW-C and the SGW-U is normal, the MME may adopt the first type of link fault handling policy as described above, that is, the UP fault. Process the policy for link failure recovery. In the first link fault handling policy, link fault recovery can be performed in different ways for different deployment modes of the UP. It is flexible and conforms to the actual network.

In a possible implementation manner, if the MME determines that the SGW-U is normal, and the link between the SGW-C and the SGW-U is faulty, the MME may adopt the second type of link fault handling policy or the third type as described above. The link fault handling policy is to reselect the control plane network element policy or wait for the link recovery policy to perform link fault recovery. If the second link fault handling strategy is used for link recovery, the recovery speed is faster and the service can continue as soon as possible. If the third link fault handling strategy is used for link recovery, after the link between the SGW-C and the SGW-U is restored, the original SGW-C can continue to be utilized, and the original service can be continued. There is no need to replace other network element processing in the middle, which reduces the possibility of user session context loss and improves the utilization of network elements.

With the technical solution provided by the embodiment of the present invention, after detecting the fault of the opposite end of the Sx link, the SGW-C and the SGW-U may not initiate the faulty service processing, and send the fault state of the peer end obtained by the probe to the probe information. In the MME, the MME can determine whether the SGW-U fault or the Sx link fault is relatively accurately determined by combining the probe information of the user plane sent by the base station and the probe information of the control plane sent by the SGW-C.

The probability of link failure caused by the network is higher than that of the SGW-U failure, and the cost of the SGW-U fault service processing is high. By distinguishing between Sx link faults and avoiding Sx link faults The SGW-U fault is processed to greatly improve the service experience of the network.

An embodiment of the present invention provides a fault processing method. In the example of FIG. 3, the first control plane network element is PGW-C, the first user plane network element is PGW-U, the second user plane network element is SGW-U, and the signaling processing network element is MME. Describe.

S31 and PGW-C know that the state of the PGW-U is a fault.

The PGW-C can determine whether the status of the PGW-U is a fault through a mechanism such as heartbeat detection, and no further description is provided.

In the embodiment of the present invention, after the PGW-C learns that the state of the PGW-U is a fault, the service that the PGW-C still keeps the PGW-U locally continues to perform normally.

After the PGW-C knows that the status of the PGW-U is faulty, the PGW-U fault can be identified, but the service associated with the PGW-U can still be maintained normally. In this way, users can be prevented from going offline and the business can be continued as much as possible.

S32. The PGW-C sends the first probe information to the MME, where the first probe information is generated by the PGW-C according to the detection result, that is, the first probe information is used to indicate the status of the PGW-U obtained by the PGW-C.

If the PGW-C determines that the PGW-U is faulty, the identifier of the faulty PGW-U may be carried in the first probe information, and the identifier of the PGW-U is, for example, the IP address of the forwarding plane of the PGW-U, and may of course be other An identifier used to identify the identity of the PGW-U. In addition, the identifier of the PGW-C may also be carried in the first probe information. If the PGW-C determines that the PGW-U is fault-free, the PGW-C may not carry the identifier of the faulty PGW-U in the first probe information. For the MME, the detection period may be set, according to receiving in the detection period. The identifier of the fault PGW-U carried by the first probe information sent by the PGW-C determines which PGW-Us are faulty. Alternatively, the PGW-C may not send the first probe information to the MME, so that if the MME does not receive the first probe information sent by the PGW-C within the detection period, the default PGW-C detection result of the PGW-U is normal. Therefore, the MME can learn the detection result of the PGW-C accordingly.

For example, the PGW-C sends the first probe information to the SGW-C through the extended S5/S8 interface message, and the SGW-C forwards the first probe information to the MME through the S11 interface message, for example, the first probe information is carried in the extended Echo. In the Request message or in the newly added fault handling message.

As described above, the PGW-C knows that the state of the PGW-U is faulty. Since the PGW-C and the PGW-U are mutually detected, the PGW-C can know that the state of the PGW-U is faulty, the same. , PGW-U can also know that the status of PGW-C is faulty.

After the PGW-U learns that the status of the PGW-C is faulty, the PGW-C can still maintain the normal business of the PGW-C.

The PGW-U can identify the PGW-C failure after determining the PGW-C failure, but can still maintain the PGW-C-related service to continue normal. In this way, users can be prevented from going offline and the service can be continued.

S33 and SGW-U know that the state of the PGW-U is a fault.

The SGW-U can detect the state of the PGW-U based on the data transmission channel of the user plane, thereby determining whether the PGW-U is faulty.

S34. The SGW-U sends the second probe information to the MME, where the second probe information is generated by the SGW-U according to the detection result, that is, the second probe information is used to indicate the status of the PGW-U obtained by the SGW-U.

If the SGW-U determines that the PGW-U is faulty, the second probe information may carry the identifier of the faulty PGW-U. If the SGW-U determines that the PGW-U has no fault, the SGW-U may be in the second probe information. The identifier of the PGW-U that does not carry the fault, for the MME, may set a detection period, and determine which ones are based on the identifier of the fault PGW-U carried by the second probe information sent by the SGW-U received in the detection period. PGW-U failure. Alternatively, the SGW-U may not send the second probe information to the MME, and if the MME does not receive the second probe information sent by the SGW-U in the detection period, the default SGW-U detection result to the PGW-U is normal. Therefore, the MME can learn the detection result of the SGW-U accordingly.

The SGW-U may have different processing modes for the local service associated with the PGW-U after the status of the PGW-U is known to be faulty. Correspondingly, the SGW-U sends the second detection information to the MME. different way. The following is a brief introduction.

method one:

In mode 1, if UP (for example, SGW-U) knows the state of another UP (for example, PGW-U) If the fault is the fault, the UP will release the service associated with the other UP. The UP may carry the second probe information in the message triggered by the MME.

For example, if the SGW-U learns that the status of the PGW-U is faulty, the SGW-U can trigger the release process of the user service bearer associated with the PGW-U. For example, the SGW-U sends a message for performing fault processing to the SGW-C through the Sx-interface, for example, a UPlane Session Delete Request message, and the SGW-C sends the S11 interface to the MME for troubleshooting. A message, such as a Delete Bearer Request message, and a message for performing fault processing, such as a Delete Bearer Command message, is sent to the PGW-C through the S5/S8 interface, thereby releasing the faulty PGW-U association. User traffic is hosted. The SGW-U can extend the identifier of the PGW-U carrying the fault in the UPlane Session Delete Request message. Correspondingly, the identifier of the PGW-U carrying the fault can be extended in the Delete Bearer Request message. SGW-C is not shown in FIG.

Method 2:

In the second mode, if the UP (for example, the SGW-U) learns that the status of the other UP (for example, the PGW-U) is a fault, the UP can continue to maintain the service associated with the other UP. Users can be prevented from going offline, so that the business can continue. The UP may send the second probe information to the MME by using an existing message or a newly added fault processing message or the like. For example, if the SGW-U knows that the status of the PGW-U is a fault, the SGW-U continues to maintain the PGW-U-related service locally, and the SGW-U can send the second probe information through the extended S1-MME interface message. To the MME.

Among them, S31-S32 and S33-S34 can be regarded as two parts, and the execution order of these two parts can be arbitrary.

S35. The MME determines a fault type according to the first probe information and the second probe information, where the fault type includes a PGW-U fault, or a link fault between the PGW-C and the PGW-U.

For example, the MME determines whether the PGW-U fault or the PGW-C and the PGW-U are combined with the identifier of the faulty PGW-U carried in the first probe information and the identifier of the faulty PGW-U carried in the second probe information. The link between the faults.

In a possible implementation, if the identifier of the faulty PGW-U carried in the second probe information includes the identifier of the faulty PGW-U carried in the first probe information, that is, the first probe information and the second probe The information indicates that the SGW-U is faulty, and the MME determines that the PGW-U is faulty.

In a possible implementation, if the identifier of the faulty PGW-U carried in the second probe information does not include the identifier of the faulty PGW-U carried in the first probe information, that is, the first probe information indicates that the SGW-U is faulty. While the second probe information indicates that the SGW-U is normal, the MME determines that the PGW-U is normal, and the link between the PGW-C and the PGW-U is faulty.

S36. The MME performs fault recovery processing.

In a possible implementation manner, if the MME determines that the PGW-U is faulty and the link between the PGW-C and the PGW-U is normal, the MME may adopt the first type introduced in S26 in the embodiment shown in FIG. 2 . The link fault handling policy performs link fault recovery.

In a possible implementation manner, if the MME determines that the PGW-U is normal and the link between the PGW-C and the PGW-U is faulty, the MME may adopt the second type introduced in S26 in the embodiment shown in FIG. 2. The link fault handling policy or the third link fault handling policy performs link fault recovery.

With the technical solution of the embodiment of the present invention, after detecting the fault of the opposite end of the Sx link, the PGW-C and the PGW-U may not initiate the fault service processing, and send the peer fault status obtained by the probe to the MME by using the probe information. Then, the MME combines the detection information of the user plane sent by the SGW-U and the detection information of the control plane sent by the PGW-C to determine whether the PGW-U fault or the Sx link fault is relatively accurate.

The probability of link failure caused by the network is relatively high relative to the PGW-U failure, and the cost of the PGW-U fault service processing is high. By distinguishing between Sx link faults and avoiding Sx link faults according to PGW-U faults, the service experience of the network can be greatly improved.

An embodiment of the invention provides a fault processing method. In FIG. 4, the first control plane network element is SGW-C, the first user plane network element is SGW-U, the second user plane network element is a base station and/or a PGW-U, and the signaling processing network element is an MME. For an example, describe it.

S41. The SGW-C learns that the state of the SGW-U is a fault.

The SGW-C can determine whether the state of the SGW-U is a fault through a mechanism such as heartbeat detection, and no further description is provided.

The SGW-C can identify the SGW-U fault after determining that the SGW-U is faulty, but can still keep the service associated with the SGW-U from continuing normally. In this way, users can be prevented from going offline and the business can be continued as much as possible.

S42. The SGW-C sends the first probe information to the MME, where the first probe information is generated by the SGW-C according to the detection result, that is, the first probe information is used to indicate the status of the SGW-U obtained by the SGW-C.

If the SGW-C determines that the SGW-U is faulty, the identifier of the faulty SGW-U may be carried in the first probe information, and the identifier of the SGW-U is, for example, the IP address of the forwarding plane of the SGW-U, and may of course be other An identifier used to identify the identity of the SGW-U. If the SGW-C determines that the SGW-U is not faulty, the SGW-C may not carry the identifier of the faulty SGW-U in the first probe information, or the SGW-C may not send the first probe information to the MME, so that the MME The detection result of SGW-C can be known from this.

For example, the SGW-C sends the first probe information to the MME through the extended S11 interface message.

S43. The PGW-U knows that the state of the SGW-U is a fault.

The PGW-U can determine whether the state of the SGW-U is a fault through a mechanism such as heartbeat detection, and no further description is provided.

In the embodiment of the present invention, after the PGW-U learns that the state of the SGW-U is a fault, the PGW-U still keeps the service associated with the SGW-U and continues to perform normally.

After the PGW-U learns that the SGW-U is faulty, it can identify the SGW-U fault, but the service associated with the SGW-U can still be maintained normally. In this way, users can be prevented from going offline and the business can be continued as much as possible.

S44. The PGW-U sends the second detection information to the MME, where the second detection information is generated by the PGW-U according to the detection result, that is, the second detection information is used to indicate the status of the SGW-U obtained by the PGW-U.

If the PGW-U determines that the SGW-U is faulty, the identifier of the faulty SGW-U may be carried in the second probe information. If the PGW-U determines that the SGW-U is fault-free, the PGW-U may not carry the identifier of the faulty SGW-U in the second probe information. For the MME, the detection period may be set. The SGW-U faults are determined according to the identifier of the fault SGW-U carried by the first probe information sent by the PGW-U received during the detection period. Alternatively, the PGW-U may not send the second probe information to the MME, and if the MM E does not receive the first probe information sent by the PGW-U within the detection period, the default PGW-U detection result of the SGW-U is Normal, so that the MME default PGW-U detects the SGW-U as normal, so that the MME can learn the detection result of the PGW-U accordingly.

For example, the PGW-U sends the second probe information to the PGW-C, and the PGW-C sends the second probe information to the SGW-C by extending the S5/S8 interface message, and the SGW-C further transmits the second probe by extending the S11 interface message. The information is sent to the MME. PGW-C is not shown in FIG.

Among them, S41-S42 and S43-S44 can be regarded as two parts, and the execution order of these two parts can be arbitrary.

S45. The MME determines a fault type according to the first probe information and the second probe information, where the fault type includes an SGW-U fault, or a link fault between the SGW-C and the SGW-U.

For example, the MME determines whether the SGW-U fault or the SGW-C and the SGW are combined with the identifier of the faulty SGW-U carried in the first probe information and the identifier of the faulty SGW-U carried in the two second probe information. The link between -U is faulty.

In a possible implementation, the identifier of the faulty SGW-U carried in the second probe information that is sent by the base station to the MME includes the identifier of the faulty SGW-U carried in the first probe information, and the PGW-U is sent to the MME. The identifier of the faulty SGW-U carried in the second probe information also includes the identifier of the faulty SGW-U carried in the first probe information, that is, the first probe information and the second probe information indicate that the SGW-U is faulty. The MME determines that the SGW-U fails, and the link between the SGW-C and the SGW-U is normal.

In a possible implementation manner, if the identifier of the faulty SGW-U carried in the second probe information that is sent by the base station to the MME does not include the identifier of the faulty SGW-U carried in the first probe information, and the PGW-U sends the identifier to the PGW-U. The identifier of the faulty SGW-U carried in the second probe information of the MME does not include the identifier of the faulty SGW-U carried in the first probe information, that is, the first probe information indicates that the SGW-U is faulty, and the second probe is detected. The information indicates that the SGW-U is normal, and the MME determines that the SGW-U is normal, and the link between the SGW-C and the SGW-U is faulty.

S46. The MME performs fault recovery processing.

In a possible implementation manner, if the MME determines that the SGW-U is faulty, and the link between the SGW-C and the SGW-U is normal, the MME may adopt the first type introduced in S26 in the embodiment shown in FIG. 2 . The link fault handling policy performs link fault recovery.

In a possible implementation manner, if the MME determines that the SGW-U is normal and the link between the SGW-C and the SGW-U is faulty, the MME may adopt the second type introduced in S26 in the embodiment shown in FIG. 2 . The link fault handling policy or the third link fault handling policy performs link fault recovery.

With the solution provided by the embodiment of the present invention, after detecting the SGW-U fault, the base station where the user forwarding plane is located may not initiate the user service bearer release processing associated with the SGW-U, so that the MME and the SGW-C have an opportunity to be based on the predefined The link fault handling strategy and the redundancy mechanism provided in the current UP deployment mode restore the user service associated with the faulty SGW-U. The MME can determine whether the SGW-U fault or the Sx chain is relatively accurately determined by the probe information acquired by the base station through the user forwarding plane and/or the probe information acquired by the PGW-U and the detection fault information acquired by the SGW-C through the control plane. Road failure.

If the SGW-U fails, the associated user service is deactivated, and the user's service recovery time is longer. The redundant resources provided by the SGW-U-based deployment can quickly recover the services of the faulty SGW-U. The service recovery time of the users is shorter and the service experience of the users is better.

Based on the technical solution provided by the embodiment of the present invention, the user service release and reactivation of the heavyweight process after the SGW-U failure can be avoided to perform the recovery process of the user service, and the redundancy provided by the lightweight SGW-U deployment is selected. The remaining resources recover the faulty user service, the user service recovery time is short, the user service experience is good, and the impact of the signaling storm of a large number of users carrying the deactivation/reactivation on the network is avoided.

An embodiment of the invention further provides a fault processing method. In the embodiment of the present invention, the signaling processing network element detects the first control plane network element, and obtains the first detection information. If the signaling processing network element determines that the first control plane network element is faulty, the first detection information indicates that the first control plane network element is faulty. In addition, the first user plane network element learns that the state of the second user plane network element is fault by detecting. The first user plane network element generates second detection information according to the detection of the second user plane network element, and the second detection signal The information is sent to the signaling processing network element. The signaling processing network element determines the fault type according to the first probe information and the second probe information. In the following description, the first control plane network element is SGW-C, the first user plane network element is the base station, the second user plane network element is the SGW-U, and the signaling processing network element is the MME. As shown in Figure 5.

S51: The MME determines that the SGW-C is faulty, and generates the first probe information, that is, the first probe information is used to indicate the state of the SGW-C obtained by the MME.

The MME detects the SGW-C, and generates first detection information according to the detection result, where the first detection information may indicate whether the SGW-C is faulty.

In the embodiment of the present invention, after the MME determines that the SGW-C is faulty, the MME still maintains the service associated with the SGW-C to continue normal.

The MME may identify the SGW-C failure after determining that the SGW-C is faulty, but may still keep the service associated with the SGW-C from proceeding normally. Because the SGW-C fault or the link fault can be determined in combination with other information, the MME can continue to keep the SGW-C-associated service continuing normally, so that the service can continue and avoid the service. Sudden interruptions to improve the user experience.

S52. The SGW-U learns that the state of the SGW-C is a fault.

The SGW-U can learn whether the status of the SGW-C is faulty through a mechanism such as heartbeat detection.

In the embodiment of the present invention, after the SGW-U determines that the SGW-C is faulty, the SGW-U still maintains the service associated with the SGW-U to continue normal.

The SGW-U can identify the SGW-C fault after determining that the SGW-C is faulty, but can still keep the service associated with the SGW-U from continuing normally. Since the SGW-C failure or the link failure is determined by the MME, as the SGW-U, the service associated with the SGW-U can continue to be performed normally when it is uncertain what is the fault, so if If the link is faulty, it will not affect the SGW-U to continue processing the service, so that the service can continue, avoid sudden interruption of the service, and improve the user experience.

S53. The base station learns that the state of the SGW-U is a fault.

The base station can detect the state of the perceived SGW-U based on the forwarding channel of the user plane, and the SGW-U detects Perceive the state of PGW-U. If the PGW-U is faulty, the SGW-U may directly detect and release the user service bearer associated with the SGW-U. The SGW-U may send the fault information of the PGW-U to the MME through the SGW-C. Similarly, if the SGW is used. The -U fault may also cause the base station or PGW-U to detect and release the locally associated user traffic bearer.

S54. The base station sends the second probe information to the MME, where the second probe information is generated by the base station according to the detection result, that is, the second probe information is used to indicate the status of the SGW-U obtained by the base station.

If the base station determines that the SGW-U is faulty, the second probe information may carry the identifier of the faulty SGW-U. If the base station determines that the SGW-U is faultless, the base station may not carry the faulty SGW in the second probe information. The identifier of the -U, or the base station may not send the second probe information to the MME, so that the MME can learn the detection result of the base station accordingly.

In the embodiment of the present invention, if the UP (for example, the base station) learns that the status of the other UP (for example, the SGW-U) is a fault, the UP locally releases the service associated with another UP, and the UP may be released due to the release of the service. The message triggered by the MME carries the second probe information. For example, the base station determines that the SGW-U is faulty, and sends an S1UE Context Release Request message to the MME to release the air interface and the local service related to the SGW-U, that is, the second probe information can be implemented by using the S1UE Context Release Request message. In the S1UE Context Release Request message, the indication that the Cause Indicates identifier is S1-U Failure and the faulty SGW-U can be carried. Therefore, the MME can know the detection result of the base station. In addition, after receiving the S1UE Context Release Request message, the MME may send an S1UE Context Release Command message to the base station to instruct the base station to release the air interface and the local service.

Among them, S51, S52 and S53-S54 can be regarded as three parts, and the order of execution of these three parts can be arbitrary.

S55. The MME determines a fault type according to the first probe information and the second probe information, where the fault type includes an SGW-C fault, or both the SGW-C and the SGW-U fault, that is, when the SGW-C fails, the SGW-U Is it normal or faulty?

For example, the MME determines whether only the SGW-C is faulty, only the SGW-C identifier of the faulty SGW-C carried in the first probe information, and the identifier of the faulty SGW-U carried in the second probe information. The SGW-U failure is still faulty for both SGW-C and SGW-U.

In a possible implementation manner, the MME determines that the SGW-C corresponding to the identifier of the faulty SGW-C carried in the first probe information is a fault.

In a possible implementation manner, the MME determines that the SGW-U corresponding to the identifier of the faulty SGW-U carried in the second probe information is a fault.

S56. The MME performs fault recovery processing.

In a possible implementation manner, if the MME determines that only the SGW-C is faulty, the MME may adopt the second fault handling policy or the fifth fault handling policy introduced in S26 in the embodiment shown in FIG. 2 to perform fault recovery. deal with.

In a possible implementation manner, if the MME determines that only the SGW-U is faulty, the MME may adopt the first fault handling policy or the fifth fault handling policy introduced in S26 in the embodiment shown in FIG. 2 to perform fault recovery. deal with.

In a possible implementation manner, if the MME determines that both the SGW-C and the SGW-U are faulty, and the faulty SGW-C and the SGW-U are not associated, that is, the faulty SGW-C and the SGW-U are not associated with each other. SGW-C and SGW-U, the MME can be handled as a SGW-C fault and an SGW-U fault, respectively, and the processing manner is as described above.

In a possible implementation manner, if the MME determines that there is an existing SGW-C and an SGW-U fault, and the faulty SGW-C and the SGW-U have mutually associated SGW-C and SGW-U, then the associated SGW- C and SGW-U, the MME may adopt the fourth fault handling policy described in S26 in the embodiment shown in FIG. 2, that is, release the service policy to perform fault recovery processing. For example, the MME may locally release all services associated with the faulty SGW-C and/or SGW-U of the associated relationship.

The SGW-U associated with the SGW-C may include the SGW-U managed by the SGW-C.

With the technical solution provided by the embodiment of the present invention, after detecting the fault of the PGW-C, the MME may not start the fault service processing temporarily, and the MME combines the second probe information sent by the base station to cause the SGW-C fault, the SGW-U fault, and the fault. Several cases of associated SGW-C and SGW-U failures, associated SGW-C and SGW-U failures are handled in different ways, thereby minimizing the cost of service processing, such as reducing deactivation of network element associations. The possibility of business to enhance the business experience of the network.

An embodiment of the invention further provides a fault processing method. In the embodiment of the present invention, the second control plane network element is configured to detect that the state of the first control plane network element is a fault, and the second control plane network element generates the first probe information according to the detection of the first control plane network element, and Sending the first probe information to the signaling processing network element. In addition, the first user plane network element learns that the state of the second user plane network element is faulty, and the first user plane network element generates second detection information according to the detection of the second user plane network element, and the second detection information is also Send to the signaling processing network element. The signaling processing network element determines the fault type based on the first probe information and the second probe information. With the technical solution provided by the embodiment of the present invention, it can be determined that only the first control plane network element is faulty, only the second user plane network element is faulty, or the first control plane network element and the second user plane network element are both faulty. In the following description, the first control plane network element is PGW-C, the first user plane network element is SGW-U, the second user plane network element is PGW-U, and the second control plane network element is SGW-U. C. The signaling processing network element is an MME as an example, as shown in FIG. 6.

S61 and SGW-C know that the state of the PGW-C is a failure.

The SGW-C can learn whether the status of the PGW-C is fault through a mechanism such as heartbeat detection.

In the embodiment of the present invention, after the SGW-C determines that the PGW-C is faulty, the SGW-C still maintains the PGW-C-associated service to continue normal.

After the SGW-C determines that the PGW-C is faulty, the PGW-C fault can be identified, but the service associated with the PGW-C can still be maintained normally. Because whether the PGW-C fault or the link fault is determined by the MME, as the SGW-C, the service associated with the PGW-C can continue to be performed normally when it is uncertain what is the fault, so if It is indeed a link failure, so it generally does not affect the PGW-C to continue to process the business, so that the business can continue, avoid sudden interruption of business, and improve the user experience.

S62. The SGW-C sends the first probe information to the MME, where the first probe information is generated by the SGW-C according to the detection result, that is, the first probe information is used to indicate the status of the PGW-C obtained by the SGW-C.

If the SGW-C learns that the status of the PGW-C is faulty, the identifier of the faulty PGW-C may be carried in the first probe information. If the SGW-C determines that the PGW-C is faultless, the SGW-C is in the first probe. The information may not carry the identifier of the faulty PGW-C, and for the MME, the detection week may be set. And determining which PGW-Cs are faulty according to the identifier of the fault PGW-C carried by the first probe information sent by the SGW-C received in the detection period. Alternatively, the SGW-C may not send the first probe information to the MME, so that if the MME does not receive the first probe information sent by the SGW-C within the detection period, the default SGW-C detection result for the PGW-C is normal. Therefore, the MME can learn the detection result of the SGW-C accordingly.

For example, the SGW-C sends the first probe information to the MME through the extended S11 interface message. The extended S11 interface message is, for example, an Echo Request message or a newly added fault handling message.

S63 and PGW-U know that the state of the PGW-C is a failure.

The PGW-U can know whether the status of the PGW-C is fault through a mechanism such as heartbeat detection, and no further description is provided.

In the embodiment of the present invention, after the PGW-U determines that the PGW-C is faulty, the PGW-U locally keeps the service associated with the PGW-U from continuing normally.

The PGW-U can identify the PGW-C failure after determining the PGW-C failure, but can still maintain the PGW-U-related service to continue normal. Since the PGW-C failure or the link failure is determined by the MME, as the PGW-U, the service associated with the PGW-U can continue to be performed normally when it is uncertain what is the fault, so if It is indeed a link failure, so it generally does not affect the PGW-U to continue to process the business, so that the business can continue, avoid sudden interruption of the business, and improve the user experience.

S64 and SGW-U know that the state of the PGW-U is a fault.

The SGW-U can learn whether the status of the PGW-U is faulty through a mechanism such as heartbeat detection.

S65. The SGW-U sends the second probe information to the MME, where the second probe information is generated by the SGW-U according to the detection result, that is, the second probe information is used to indicate the status of the PGW-U obtained by the SGW-U.

If the SGW-U determines that the PGW-U is faulty, the second probe information may carry the identifier of the faulty PGW-U, and may also carry the identifier of the PGW-C associated with the faulty PGW-U, if the SGW -U determines that the PGW-U is not faulty, then the SGW-U may not carry the identifier of the faulty PGW-U and the identifier of the PGW-C associated with the faulty PGW-U in the second probe information, for the MME It can be said that the detection period can be set to determine which PGW-Us are faulty according to the identifier of the fault PGW-U carried by the second probe information sent by the SGW-U received during the detection period. Alternatively, the SGW-U may not send the second probe information to the MME, and if the MME does not receive the second probe information sent by the SGW-U within the detection period, the default SGW-U detection result for the PGW-U is normal. Therefore, the MME can learn the detection result of the SGW-U accordingly.

The SGW-C determines the identity of the PGW-C associated with the faulty PGW-U based on the association relationship between the locally constructed PGW-C and the PGW-U. For example, the SGW-C may construct an association relationship between the PGW-C and the PGW-U based on the PGW-U information exchanged between the SGW-C and the PGW-C when creating the user plane channels of the SGW-U and the PGW-U, or PGW -C may transmit the association relationship between the PGW-C and the PGW-U to the SGW-C, and the SGW-C may also send the association relationship to the MME.

method one:

In the first mode, if the UP (for example, the SGW-U) learns that the state of the other UP (for example, the PGW-U) is a fault, the UP locally releases the service associated with another UP, and the UP may be due to the release of the service. The message triggered to the MME carries the second probe information.

For example, if the SGW-U learns that the status of the PGW-U is faulty, the SGW-U can trigger the release process of the user service bearer associated with the PGW-U. For example, the SGW-U sends a message for performing fault processing to the SGW-C through the Sxa interface, for example, a UPlane Session Delete Request message, and the SGW-C sends a message for performing fault processing to the MME through the S11 interface, for example, a Delete Bearer Request message. And sending a message for performing fault processing, such as a Delete Bearer Request message, to the PGW-C through the S5/S8 interface, thereby releasing the user service bearer associated with the faulty PGW-U. The SGW-U can extend the identifier of the PGW-U carrying the fault in the UPlane Session Delete Request message. Correspondingly, the identifier of the PGW-U carrying the fault can be extended in the Delete Bearer Request message.

Method 2:

In mode 2, if UP (for example, SGW-U) knows the state of another UP (for example, PGW-U) In the case of a fault, the UP can continue to maintain the normal association with another UP. In this way, the user can be prevented from going offline, so that the service can continue. The UP may send the second probe information to the MME by using an existing message or a newly added fault processing message or the like. For example, if the SGW-U knows that the status of the PGW-U is a fault, the SGW-U continues to maintain the PGW-U-related service locally, and the SGW-U sends the second probe information to the MME through the SGW-C.

Among them, S61-S62, S63, S64-S65 can be regarded as three parts, and the order of execution of these three parts can be arbitrary.

S66. The MME determines a fault type according to the first probe information and the second probe information, where the fault type includes only a PGW-C fault, only a PGW-U fault, or both the PGW-C and the PGW-U fault.

For example, the MME determines whether the PGW-C fault, the PGW-U fault, or the PGW- is combined with the identifier of the faulty PGW-C carried in the first probe information and the identifier of the faulty PGW-U carried in the second probe information. Both C and PGW-U fail.

In a possible implementation manner, the MME determines that the PGW-C corresponding to the identifier of the faulty PGW-C carried in the first probe information is a fault.

In a possible implementation manner, the MME determines that the PGW-U corresponding to the identifier of the faulty PGW-U carried in the second probe information is a fault.

S67. The MME performs fault recovery processing.

In a possible implementation manner, if the MME determines that the PGW-C is faulty, the MME may adopt the second fault handling policy or the fifth fault handling policy introduced in S26 in the embodiment shown in FIG. 2 to perform fault recovery processing. .

In a possible implementation manner, if the MME determines that the PGW-U is faulty, the MME may adopt the first fault handling policy or the fifth fault handling policy introduced in S26 in the embodiment shown in FIG. 2 to perform fault recovery processing. .

In a possible implementation manner, if the MME determines that there is both a PGW-C and a PGW-U fault, and the faulty PGW-C and the PGW-U are not associated, that is, the faulty PGW-C and the PGW-U are not associated with each other. For PGW-C and PGW-U, the MME can be handled as a PGW-C fault and a PGW-U fault, respectively, and the processing manner is as described above.

In a possible implementation manner, if the MME determines that there is both a PGW-C and a PGW-U fault, and the faulty PGW-C and the PGW-U have mutually associated PGW-C and PGW-U, then the associated PGW- C and PGW-U, the MME may adopt the fourth fault handling policy described in S26 in the embodiment shown in FIG. 2, that is, release the service policy to perform fault recovery processing. For example, the MME may locally release all services associated with the faulty PGW-C and/or PGW-U of the associated relationship.

The PGW-U associated with the PGW-C may include the PGW-U managed by the PGW-C.

With the technical solution provided by the embodiment of the present invention, after detecting the PGW-C failure, the SGW-C may not start the fault service processing temporarily. After detecting the PGW-C fault, the PGW-U may not start the fault service processing temporarily. The MME combines the detection information sent by the SGW-C and the PGW-U to fault the PGW-C, the PGW-U failure, the unrelated PGW-C and PGW-U failures, the associated PGW-C and PGW-U failures. Several situations are handled in different ways, so that the cost of service processing can be minimized, for example, the possibility of deactivating the service associated with the network element is reduced, and the service experience of the network is improved.

The foregoing various embodiments are exemplified by the network architecture shown in FIG. 1. In practical applications, the solution of the embodiment of the present invention may also be applied to other network architectures. It can be considered that the network architecture that is separate from the control plane and the user plane can be applied to the technical solution provided by the embodiment of the present invention. The following example shows another network architecture.

FIG. 7 is a schematic diagram of a network architecture according to an embodiment of the present invention. It can be seen that FIG. 7 shows the network architecture of the SDN, including the SDN controller and multiple switches. In FIG. 7, three switches are taken as an example. In practical applications, the number of switches can be set according to the situation. In FIG. 7, the signaling processing network element is implemented by using an SDN controller as an example.

For a better understanding, how to apply the technical solution provided by the embodiment of the present invention to the network architecture shown in FIG. 8 is described below.

An embodiment of the invention provides a fault determination and processing method. In the embodiment of the present invention, the signaling processing network element determines the first user plane network element fault by the probe, and the signaling processing network element generates the first probe information according to the detection of the first user plane network element. In addition, the second user plane network element learns that the state of the first user plane network element is faulty, and the second user plane network element generates second detection information according to the detection of the first user plane network element, and the second detection information is also Send to the signaling processing network element. Signaling processing network element The fault type is determined according to the first probe information and the second probe information. In the following description, the first user plane network element and the second user plane network element are both switches and the signaling processing network element is an SDN controller as an example. Since the two user plane network elements are both switches, in order to facilitate the following description, three switches are respectively given different reference numerals in FIG. 7, namely, switch 71, switch 72 and switch 73 in FIG. 7, for example, The switch 71 is the first user plane network element in the embodiment of the present invention, and the switch 72 is the second user plane network element in the embodiment of the present invention. Therefore, it should be clear that the same type of device is given different reference numerals in FIG. 7 for the convenience of description, and does not mean that the types of these devices are different. See Figure 8.

S81. The SDN controller determines that the switch 71 is faulty, and generates first probe information, that is, the first probe information is used to indicate the status of the switch 71 obtained by the SDN controller.

The SDN controller detects the switch 71 and can determine whether the switch 71 is faulty. The SDN controller may generate the first probe information according to the detection result of the switch 71. The first probe information may indicate whether the switch 71 is normal or faulty. In the embodiment of the present invention, the fault of the switch 71 is taken as an example. It can be understood that the SDN controller detects the switch 71, and detects the control plane connection state between the SDN controller and the switch 71, that is, detects the link state between the SDN controller and the switch 71. It can be understood that the first probe information can indicate whether the signaling connection status between the SDN controller and the switch 71 is normal or faulty.

In the embodiment of the present invention, after the SDN controller determines that the switch 71 is faulty, the SDN controller locally keeps the service associated with the switch 71 from continuing normally.

After determining that the switch 71 is faulty, the SDN controller can identify that the switch 71 is faulty, but can still keep the services associated with the switch 71 continue to operate normally. Because the switch 71 is faulty or the link fault can be determined in combination with other information, the SDN controller can continue to keep the services associated with the switch 71 continue to operate normally, so that the service can continue and avoid the service. Sudden interruptions to improve the user experience.

S82. The switch 72 learns that the state of the switch 71 is a fault.

The switch 72 detects the switch 71 and can determine whether the switch 71 is faulty. It can be understood that the switch 72 detects the switch 71 and detects the user between the switch 72 and the switch 71. Face connection status.

S83, the switch 72 sends the second probe information to the SDN controller, where the second probe information is generated by the switch 72 according to the detection result, that is, the second probe information is used to indicate the status of the switch 71 obtained by the switch 72.

The switch 72 can generate the second probe information according to the detection result of the switch 71. The second probe information can indicate whether the switch 71 is normal or faulty. In the embodiment of the present invention, the fault of the switch 71 is taken as an example. It can be understood that the second probe information can indicate whether the user plane connection status between the switch 71 and the switch 72 is normal or faulty. Of course, the switch 72 can detect other switches in addition to the switch 71. For example, the switch 73 can detect the switch 73. Therefore, the second probe information can indicate that the switch 71 is normal or faulty, and can also indicate the switch. 73 is normal or faulty, and is not limited in the embodiment of the present invention.

Among them, S81, and S82-S83 can be regarded as two parts, and the execution order of these two parts can be arbitrary.

S84. The SDN controller determines the fault type according to the first probe information and the second probe information, where the fault type includes a fault of the switch 71, or a link fault between the SDN controller and the switch 71.

For example, the SDN controller determines whether the switch 71 is faulty or the link between the switch 71 and the SDN controller, in combination with the identifier of the faulty switch carried by the first probe information and the identifier of the faulty switch carried in the second probe information. malfunction.

In a possible implementation, if the identifier of the faulty switch carried in the second probe information includes the identifier of the faulty switch carried by the first probe information, that is, the identifier of the switch 71 carrying the fault in the first probe information, and the second The probe information also carries the identity of the failed switch 71, and the SDN controller can determine that the switch 71 is faulty.

In a possible implementation, if the identifier of the faulty switch carried in the second probe information does not include the identifier of the faulty switch carried by the first probe information, the first probe information carries the identifier of the faulty switch 71. The second probe information does not carry the identifier of the switch 71, and the SDN controller can determine that the switch 71 is normal, and the link between the switch 71 and the SDN controller is faulty.

S85, SDN controller performs fault recovery processing.

In a possible implementation manner, if the SDN controller determines that the switch 71 is faulty and the link between the switch 71 and the SDN controller fails, the SDN controller may reselect the new switch to replace the original faulty switch 71, for example, selecting The switch 73 replaces the switch 71, and needs to update the forwarding table of the failed switch 71 to the switch 73, and modify the forwarding table of the upstream and downstream switches of the switch 71 so that its upstream and downstream switches are forwarded through the reselected switch 73.

In a possible implementation manner, if the SDN controller can determine that the switch 71 is normal, and the link between the switch 71 and the SDN controller is faulty, the SDN controller can wait for the SDN control connection interface to resume, and continue to let the user plane data flow through the switch. 71 for transmission.

The technical solution provided by the embodiment of the present invention can effectively identify whether the network element is faulty or the link is faulty, so that different measures can be taken respectively to ensure that the service of the user plane can be continued, and the possibility of sudden interruption of the service is reduced, and the possibility is improved. Network performance.

The device provided by the embodiment of the present invention is described below with reference to the accompanying drawings.

FIG. 9 is a schematic diagram of a computer device 100 according to an embodiment of the present invention. The computer device 100 includes at least one processor 101, a communication bus 102, a memory 103, and at least one communication interface 104. In the embodiment of the present invention, the signaling processing network element or the first network element and the like can be implemented by the computer device 100 shown in FIG. The first network element may be a control plane network element (such as a first control plane network element or a second control plane network element), or a user plane network element (such as a first user plane network element or a second user plane network element) The second network element may also be a control plane network element or a user plane network element. The first network element obtains the detection information according to the detection of the second network element by detecting the state of the second network element, and the detection information may be The first probe information or the second probe information is included, and the first network element sends the generated probe information to the signaling processing network element. As to what kind of network element the first network element and the second network element are, reference may be made to the method provided by any one of FIG. 2 to FIG. 6 or FIG.

The processor 101 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.

Communication bus 102 can include a path for communicating information between the components described above. Communication interface 104, using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.

The memory 103 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory 103 can be independently present and connected to the processor 101 via a bus. The memory 103 can also be integrated with the processor 101.

The memory 103 is used to store application code for executing the solution of the present invention, and is controlled by the processor 101 for execution. The processor 101 is configured to execute application code stored in the memory 103. If the signaling processing network element, the control plane network element, or the user plane network element is implemented by the computer device 100, one or more of the signaling processing network element, the control plane network element, or the user plane network element memory 103 may be stored. The software module, the signaling processing network element, the control plane network element, or the user plane network element may implement the stored software module through the processor 101 and the program code in the memory 103 to implement the determination or processing of the fault.

In a particular implementation, as an embodiment, processor 101 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a specific implementation, as an embodiment, the computer device 100 may include a plurality of processors 101, such as the first processor 1011 and the second processor 1012 in FIG. 9, wherein the first processor 1011 and the second process The names of the devices 1012 are different and the reference numerals are different, just to distinguish the plurality of processors 101. Each of these processors 101 may be a single-CPU processor 101 or a multi-CPU processor 101. Processor 101 herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

The computer device 100 described above may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 100 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure. Embodiments of the invention do not limit the type of computer device 100.

Referring to FIG. 10, an embodiment of the present invention provides a signaling processing network element, where the signaling processing network element includes a receiving unit 1001 and a processing unit 1002.

Optionally, the signaling processing network element may further include a sending unit 1003, which is shown together in FIG. The sending unit 1003 is an optional functional unit. In order to distinguish it from the required functional unit, it is drawn in the form of a dotted line in FIG.

In a practical application, the physical device corresponding to the receiving unit 1001 and the sending unit 1003 may include the communication interface 104 in FIG. 9, and the physical device corresponding to the processing unit 1002 may be the processor 101 in FIG. It can be considered that in the communication interface 104 in FIG. 9, some communication interfaces 104 implement the functions of the receiving unit 1001, and some communication interfaces 104 can implement the functions of the transmitting unit 1003, or can be considered as being in the communication interface 104 in FIG. It is possible that each communication interface 104 can implement both the function of the receiving unit 1001 and the function of the transmitting unit 1003.

The signaling processing network element may be used to perform the method provided by the embodiment shown in any one of the above Figures 2 to 4, for example, may be a signaling processing network element as described above. Therefore, for the functions and the like implemented by the units in the signaling processing network element, reference may be made to the description of the previous method part, and details are not described herein.

Referring to FIG. 11, an embodiment of the present invention provides a signaling processing network element, where the signaling processing network element includes a receiving unit 1101 and a processing unit 1102.

Optionally, the signaling processing network element may further include a sending unit 1103, which is shown together in FIG. The sending unit 1103 is an optional functional unit, which is drawn in the form of a broken line in FIG. 11 in order to distinguish it from the required functional unit.

In a practical application, the physical device corresponding to the receiving unit 1101 and the sending unit 1103 may include the communication interface 104 in FIG. 9, and the physical device corresponding to the processing unit 1102 may be the processor in FIG. 101. It can be considered that in the communication interface 104 in FIG. 9, some communication interfaces 104 implement the functions of the receiving unit 1101, and some communication interfaces 104 can implement the functions of the transmitting unit 1103, or can be considered as being in the communication interface 104 in FIG. It is possible that each communication interface 104 can implement both the function of the receiving unit 1101 and the function of the transmitting unit 1103.

The signaling processing network element may be used to perform the method provided by the embodiment shown in any of the above-mentioned Figures 5-6, and may be, for example, a signaling processing network element as described above. Therefore, for the functions and the like implemented by the units in the signaling processing network element, reference may be made to the description of the previous method part, and details are not described herein.

Referring to FIG. 12, an embodiment of the present invention provides an SDN controller, where the SDN controller includes a receiving unit 1201 and a processing unit 1202.

In a practical application, the physical device corresponding to the receiving unit 1201 may be the communication interface 104 in FIG. 9, and the physical device corresponding to the processing unit 1202 may be the processor 101 in FIG. It can be considered that in the communication interface 104 in FIG. 9, some communication interfaces 104 implement the function of the receiving unit 1201, and some communication interfaces 104 can implement the function of transmitting data, or can be considered that in the communication interface 104 in FIG. It is possible that each communication interface 104 can implement both the function of the receiving unit 1201 and the function of transmitting data.

The signaling processing network element may be used to perform the method provided by the embodiment shown in FIG. 8 above, and may be, for example, the SDN controller as described in the embodiment shown in FIG. 7 or FIG. 8. Therefore, for the functions and the like implemented by the units in the signaling processing network element, reference may be made to the description of the previous method part, and details are not described herein.

Referring to FIG. 13, an embodiment of the present invention provides a network element, where the network element is a first network element, where the network element includes a sending unit 1301 and a processing unit 1302.

In a practical application, the physical device corresponding to the sending unit 1301 may be the communication interface 104 in FIG. 9, and the physical device corresponding to the processing unit 1302 may be the processor 101 in FIG. It can be considered that, in the communication interface 104 in FIG. 9, some communication interfaces 104 implement the functions of the transmitting unit 1301, and some communication interfaces 104 can implement the function of receiving data, or it can be considered that in the communication interface 104 in FIG. It is possible that each communication interface 104 can implement both the function of the transmitting unit 1301 and the function of receiving data.

The network element may be used to perform the method provided by the embodiment shown in any one of the above FIG. 2-6 and FIG. 8, for example, the first control plane network element and the second may be as described above. The control plane network element, the first user plane network element, or the second user plane network element. Therefore, for the functions and the like implemented by the units in the network element, reference may be made to the description of the previous method part, and details are not described herein.

In the embodiment of the present invention, the signaling processing network element can receive the information sent by the multi-party network element, and therefore the task of performing the fault determination is handed over to the signaling processing network element. The signaling processing network element can comprehensively determine whether the user plane network element fault, the control plane network element fault, or the link fault between the control plane network element and the user plane network element is combined with the received first probe information and the second probe information. Because the multi-faceted information is comprehensively considered in the judgment of the fault, not only the information of the single network element is considered, but the accuracy of the judgment result is improved, so that if the network element fails, it can be processed according to the network element failure, if A link fault can be processed according to the link fault. You can avoid service interruption of the faultless UP and ensure the continuity of the service. In the case of an UP fault, you can also restore the UP service as quickly as possible. Business experience.

In the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit or unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.

The embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium may store a program, where the program includes some or all of the bandwidth adjustment method in any one of the video communication processes described in the foregoing method embodiments. step.

The functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may also be an independent physical module.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on this understanding, this All or part of the technical solution of the invention may be embodied in the form of a software product stored in a storage medium, including instructions for causing a computer device, such as a personal computer, a server, or a network device. Etc., or a processor, performs all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a universal serial bus flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

The above embodiments are only used to describe the technical solutions of the present invention in detail, but the description of the above embodiments is only for the purpose of facilitating the understanding of the embodiments of the present invention, and should not be construed as limiting the embodiments of the present invention. Variations or substitutions that may be readily conceived by those skilled in the art are intended to be included within the scope of the present invention.

Claims

A fault processing method, comprising:

The signaling processing network element receives the first probe information sent by the first control plane network element, where the first probe information is used to indicate the state of the first user plane network element obtained by the first control plane network element;

The signaling processing network element receives the second probe information sent by the second user plane network element, where the second probe information is used to indicate the status of the first user plane network element obtained by the second user plane network element ;

Determining, by the signaling processing network element, the fault type according to the first probe information and the second probe information, where the fault type includes the first user plane network element fault, or the first control plane network element and The link between the first user plane network elements is faulty.
The method according to claim 1, wherein the signaling processing network element determines a fault type according to the first probe information and the second probe information, including:

If the first probe information and the second probe information both indicate that the first user plane network element is faulty, the signaling processing network element determines that the fault type is the first user plane network element fault; or

If the first probe information indicates that the first user plane network element is faulty, and the second probe information indicates that the first user plane network element is normal, the signaling processing network element determines that the fault type is the The first user plane network element is normal, and the link between the first control plane network element and the first user plane network element is faulty.
The method according to claim 2, after the signaling processing network element determines that the fault type is a link fault between the first control plane network element and the first user plane network element, Also includes:

The signaling processing network element re-selects the control plane network element for the first user plane network element, and sends the identifier of the first user plane network element to the reselected control plane network element, so that the reselected control plane The network element manages the first user plane network element; or

The signaling processing network element instructs the first control plane network element to wait for link recovery.
A method according to any of claims 1-3, wherein

The first control plane network element is a control plane serving gateway, and the second user plane network element is a base station. The first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity; or

The first control plane network element is a control plane packet data network gateway, the second user plane network element is a user plane serving gateway, and the first user plane network element is a user plane packet data network gateway, and the signaling Processing the network element as a mobility management entity; or

The first control plane network element is a control plane serving gateway, the second user plane network element is a user plane packet data network gateway, and the first user plane network element is a user plane serving gateway, and the signaling processing network The yuan is a mobile management entity.
A fault processing method, comprising:

The signaling processing network element obtains the first detection information; the first detection information is used to indicate the state of the first control plane network element;

The signaling processing network element receives the second probe information sent by the first user plane network element, where the second probe information is used to indicate the state of the second user plane network element obtained by the first user plane network element ;

The signaling processing network element determines a fault type according to the first probe information and the second probe information, where the fault type includes only the first control plane network element fault, or only the second user plane network a failure of the element, or the first control plane network element and the second user plane network element are both faulty;

If the first control plane network element and the second user plane network element both fail, and the first control plane network element manages the second user plane network element, the signaling processing network element is released. The service associated with the first control plane network element and/or the second user plane network element.
The method according to claim 5, wherein the signaling processing network element determines the fault type according to the first probe information and the second probe information, including:

If the first probe information indicates that the first control plane network element is faulty, the signaling processing network element determines that the first control plane network element is faulty; or

And if the second probe information indicates that the second user plane network element is faulty, the signaling processing network element determines that the second user plane network element is faulty.
The method of claim 6 wherein said signaling processing network element is determined After the type of barrier, it also includes:

If only the first control plane network element fails, the signaling processing network element reselects the control plane network element for the second user plane network element, and sends the second user to the reselected control plane network element. The identifier of the surface network element is such that the reselected control plane network element manages the second user plane network element.
The method according to any one of claims 5-7, wherein the signaling processing network element obtains the first detection information, including:

The signaling processing network element receives the first detection information that is sent by the second control plane network element, where the first detection information is used to indicate the first control plane network element obtained by the second control plane network element State; or

The signaling processing network element detects the first control plane network element, and generates the first probe information according to the detection result.
The method of claim 8 wherein:

The signaling processing network element is a mobility management entity, the first control plane network element is a control plane serving gateway, the first user plane network element is a base station, and the second user plane network element is a user plane serving gateway. ;or

The signaling processing network element is a mobility management entity, the second control plane network element is a control plane serving gateway, and the first control plane network element is a control plane packet data network gateway, and the first user plane network element Serving the gateway for the user plane, the second user plane network element is a user plane packet data network gateway.
A fault processing method, comprising:

The software-defined network SDN controller detects the first switch to obtain the first probe information;

The SDN controller receives the second probe information sent by the second switch, where the second probe information is used to indicate the state of the first switch obtained by the second switch;

Determining, by the SDN controller, a fault type according to the first probe information and the second probe information, where the fault type includes the first switch fault, or between the SDN controller and the first switch The link is faulty.
A fault processing method, comprising:

The first network element learns that the state of the second network element is faulty by detecting;

The first network element generates the probe information according to the detection of the second network element, and sends the probe information to the signaling processing network element; the probe information carries the identifier of the second network element, where The probe information is used to determine the type of fault.
The method according to claim 11, wherein the first network element is a control plane network element or a user plane network element; and the second network element is a control plane network element or a user plane network element.
A signaling processing network element, comprising:

a receiving unit, configured to receive first probe information sent by the first control plane network element, and receive second probe information sent by the second user plane network element; the first probe information is used to indicate the first control plane a state of the first user plane network element obtained by the network element, where the second probe information is used to indicate a state of the first user plane network element obtained by the second user plane network element;

a processing unit, configured to determine a fault type according to the first probe information and the second probe information, where the fault type includes the first user plane network element fault, or the first control plane network element and the The link between the first user plane network elements is faulty.
The signaling processing network element according to claim 13, wherein the processing unit is configured to:

If the first probe information and the second probe information both indicate that the first user plane network element is faulty, determining that the fault type is the first user plane network element fault; or

If the first probe information indicates that the first user plane network element is faulty, and the second probe information indicates that the first user plane network element is normal, determining that the fault type is the first user plane network element is normal. The link between the first control plane network element and the first user plane network element is faulty.
The signaling processing network element according to claim 14, wherein the signaling processing network element further comprises a sending unit; the processing unit is further configured to:

After determining that the fault type is a link fault between the first control plane network element and the first user plane network element, reselecting the control plane network element for the first user plane network element, and by using the Sending, by the sending unit, the identifier of the first user plane network element to the reselected control plane network element, so that the reselected control plane network element manages the first user plane network element; or

Determining a fault type as a chain between the first control plane network element and the first user plane network element After the road failure, the first control plane network element is instructed to wait for link recovery.
A signaling processing network element according to any of claims 13-15, characterized in that

The first control plane network element is a control plane serving gateway, the second user plane network element is a base station, the first user plane network element is a user plane serving gateway, and the signaling processing network element is a mobility management entity. ;or

The first control plane network element is a control plane packet data network gateway, the second user plane network element is a user plane serving gateway, and the first user plane network element is a user plane packet data network gateway, and the signaling Processing the network element as a mobility management entity; or

The first control plane network element is a control plane serving gateway, the second user plane network element is a user plane packet data network gateway, and the first user plane network element is a user plane serving gateway, and the signaling processing network The yuan is a mobile management entity.
A signaling processing network element, comprising:

a processing unit, configured to obtain first probe information, where the first probe information is used to indicate a state of the first control plane network element;

a receiving unit, configured to receive second probe information that is sent by the first user plane network element, where the second probe information is used to indicate a state of the second user plane network element obtained by the first user plane network element;

The processing unit is further configured to: determine a fault type according to the first probe information and the second probe information, where the fault type includes only the first control plane network element fault, or only the second user plane The network element is faulty, or the first control plane network element and the second user plane network element are both faulty; and, if the first control plane network element and the second user plane network element are both faulty, and The first control plane network element manages the second user plane network element, and releases the service associated with the first control plane network element and/or the second user plane network element.
The signaling processing network element according to claim 17, wherein the processing unit is configured to determine a fault type according to the first probe information and the second probe information, including:

Determining that the first control plane network element is faulty if the first probe information indicates that the first control plane network element is faulty; or

Determining the second use if the second probe information indicates that the second user plane network element is faulty The user network element is faulty.
The signaling processing network element according to claim 18, wherein the signaling processing network element further comprises a sending unit; the processing unit is further configured to:

After determining the fault type, if only the first control plane network element fails, the control plane network element is newly selected for the second user plane network element, and is sent to the reselected control plane network element by using the sending unit. The identifier of the second user plane network element is configured, so that the reselected control plane network element manages the second user plane network element.
The signaling processing network element according to any one of claims 17 to 19, wherein the processing unit is configured to obtain the first detection information, including:

Obtaining the first detection information that is sent by the second control plane network element that is received by the receiving unit, where the first detection information is used to indicate the first control plane network element obtained by the second control plane network element State; or

The first control plane network element is detected, and the first probe information is generated according to the detection result.
The signaling processing network element of claim 20, wherein

The signaling processing network element is a mobility management entity, the first control plane network element is a control plane serving gateway, the first user plane network element is a base station, and the second user plane network element is a user plane serving gateway. ;or

The signaling processing network element is a mobility management entity, the second control plane network element is a control plane serving gateway, and the first control plane network element is a control plane packet data network gateway, and the first user plane network element Serving the gateway for the user plane, the second user plane network element is a user plane packet data network gateway.
A software defined network SDN controller, comprising:

a processing unit, configured to detect the first switch, to obtain first detection information;

a receiving unit, configured to receive second detection information sent by the second switch, where the second detection information is used to indicate a status of the first switch obtained by the second switch;

The processing unit is further configured to determine a fault type according to the first probe information and the second probe information, where the fault type includes the first switch fault, or the SDN controller and the first switch The link between the faults.
A network element, comprising:

a processing unit, configured to learn, by detecting, that the state of the second network element is a fault, and generate detection information according to the detection of the second network element;

And a sending unit, configured to send the detection information to the signaling processing network element, where the detection information carries an identifier of the second network element, where the detection information is used to determine a fault type.
The network element according to claim 23, wherein the network element is a control plane network element or a user plane network element; and the second network element is a control plane network element or a user plane network element.