CN113489626A

CN113489626A - Method and device for detecting and notifying path fault

Info

Publication number: CN113489626A
Application number: CN202111035990.9A
Authority: CN
Inventors: 陈娟娟; 沈洋; 叶勇; 汪硕; 黄韬
Original assignee: Network Communication and Security Zijinshan Laboratory
Current assignee: Network Communication and Security Zijinshan Laboratory
Priority date: 2021-09-06
Filing date: 2021-09-06
Publication date: 2021-10-08
Anticipated expiration: 2041-09-06
Also published as: CN113489626B

Abstract

The invention provides a method and a device for detecting and notifying path faults, wherein the method is applied to a head end of SR policy and comprises the following steps: based on a one-way detection protocol, periodically sending a detection message to an MEP detection point configured at the tail end of the SR Policy through an MEP detection point configured at the head end of the SR Policy, and detecting the SR Policy candidate path; and if a fault notification sent by an MEP detection point at the tail end of the SR policy is received, determining that the SR policy candidate path has a fault. The method for detecting and notifying the path fault provided by the invention detects the SR policy candidate path by periodically sending the detection message to the MEP detection point at the tail end in a one-way through the MEP detection point at the head end, and determines that the SR policy candidate path has the fault under the condition that the head end receives the fault notification, thereby strictly ensuring the correctness of the candidate path detection.

Description

Method and device for detecting and notifying path fault

Technical Field

The present invention relates to the field of network transmission technologies, and in particular, to a method and an apparatus for detecting and notifying a path fault.

Background

SR Policy (traffic engineering system) is a new generation of traffic engineering system based on the Segment Routing technology. SR Policy encodes the forwarding path of the data packet in the network to form a Segment list based on the user intention, issues the result to the network edge node, guides the data packet to be forwarded to the destination node based on the network path corresponding to the Segment list after entering the network, and accordingly achieves the traffic engineering intentions of high bandwidth, low time delay, non-intersecting paths and the like.

The method is a common method for detecting the effectiveness of the SR Policy candidate path, and the method uses SBFD (Seamless Bidirectional Forwarding Detection) to initiate the Segment list Forwarding path Detection at the SR Policy head end. The SBFD is a bidirectional path detection mechanism, and the link detection result is normal only if the outbound path and the return path are both normal, but the SR Policy candidate path itself is a unidirectional path. When the SBFD is applied to the SR Policy candidate path, the outbound detection message is forwarded to the tail end from the SR Policy head end routing Segment list, the return detection message is forwarded through IP, and is not actually related to the SR Policy path.

Disclosure of Invention

Aiming at the problems in the prior art, the invention provides a method and a device for detecting and notifying a path fault.

In a first aspect, the present invention provides a method for detecting and notifying a path fault, which is applied to a head end of SR policy, and includes:

based on a unidirectional detection protocol, periodically sending a detection message to an MEP (Maintenance Entity Group End) detection Point configured at the tail End of the SR Policy through an MEP (Maintenance Entity Group End) detection Point configured at the head End of the SR Policy, and detecting the SR Policy candidate path;

if a fault notification sent by an MEP detection point at the tail end of the SR policy is received, determining that the SR policy candidate path has a fault;

binding an MEP detection point at the head end with an SR Policy candidate path, and determining the corresponding MEP detection point at the tail end as a peer MEP; and binding the MEP detection point of the tail end with the IP address on the SR Policy head-end equipment, and determining that the corresponding MEP of the head end is a peer MEP.

According to the method for detecting and notifying the path fault provided by the invention, if the fault notification sent by the MEP detection point at the tail end of the SR policy is received, the method comprises the following steps:

under the condition that the interval of sending detection messages of MEP detection points at the head end of the SR Policy is a first interval, receiving a first fault notification sent by the MEP detection points at the tail end of the SR Policy through a data plane and/or sent by an SDN controller;

under the condition that the interval of sending the detection message of the MEP detection point at the head end of the SR Policy is a second interval, receiving a second fault notification sent by the MEP detection point at the tail end of the SR Policy through a control plane;

wherein the first interval is less than the second interval.

According to the method for detecting and notifying the path fault, after receiving the first fault notification sent by the MEP detection point of the SR Policy tail end through the data plane and/or sent by the SDN controller, the method further includes:

determining an MEP detection point Identification (ID) of the tail end of the SR Policy based on the first fault notification;

and matching in the SR Policy candidate paths to obtain a first fault candidate path based on the MEP detection point identification ID of the tail end, and setting the first fault candidate path to be invalid.

According to the method for detecting and notifying the path fault provided by the invention, the method further comprises the following steps:

triggering SR Policy to switch to other candidate paths if the first failed candidate path deploys Hotstandy protection.

According to the method for detecting and notifying the path fault provided by the invention, after receiving the second fault notification sent by the MEP detection point at the SR Policy tail end through the control plane, the method further comprises the following steps:

determining an MEP detection point Identification (ID) of the tail end of the SR policy based on the second fault notification;

and matching in the SR Policy candidate path to obtain a second fault candidate path based on the MEP detection point identification ID of the tail end, and setting the second fault candidate path to be invalid.

and under the condition that the SDN controller judges that the second failure candidate path deploys the Hotstandy protection, triggering SR Policy to switch to other candidate paths.

According to the method for detecting and notifying the path fault, provided by the invention, the period of the detection message which is sent periodically is the packet sending interval of the detection message which is configured on the MEP detection point at the head end of the SR Policy and the MEP detection point at the tail end of the SR Policy, and the configuration parameters at the two ends are consistent.

According to the method for detecting and notifying the path fault, provided by the invention, the detection Message is a CCM (Continuity Check Message) detection frame, and the label forwarding information of the detection Message is encapsulated by label stack information corresponding to an SR Policy candidate path.

In a second aspect, the present invention further provides a method for detecting and notifying a path failure, which is applied to a tail end of SR policy, and includes:

based on a one-way detection protocol, receiving a detection message periodically sent by an MEP detection point configured at the head end of the SR policy;

if the detection message is not received within a preset number of periods, determining that the SR policy candidate path has a fault, and sending a fault notification to an MEP detection point at the head end of the SR policy;

According to the method for detecting and notifying the path fault, provided by the invention, if the packet sending interval is a first interval, the rapid detection is determined;

if the packet sending interval is a second interval, determining the packet sending interval is slow detection;

wherein the first interval is less than the second interval.

According to the method for detecting and notifying the path fault provided by the present invention, if the packet sending interval is the first interval, after the packet sending interval is determined to be the fast detection, the method further includes:

determining a period for sending a first fault notification based on a period for sending a detection message configured by peer-to-peer MEP detection points of a head end of SR Policy;

sending a first fault notification to an MEP detection point of the SR Policy head-end through a data plane and/or via an SDN controller;

the first fault notification comprises an MEP detection point identification ID and a target address of the SR Policy tail end, and the target address is an IP address of equipment of the SR Policy head end.

if the data plane fails, sending the first failure report to an SR Policy head end through an SDN controller;

and switching to other SR Policy candidate paths through the SDN controller, and sending the latest state of the SR Policy candidate paths to the head end of the SR Policy.

According to the method for detecting and notifying the path fault provided by the present invention, if the packet sending interval is the second interval, after the packet sending interval is determined to be slow detection, the method further includes:

determining a period for sending a second fault notification based on a period for sending a detection message configured by peer-to-peer MEP detection points of a head end of SR Policy, and reporting the second fault notification to an SDN controller;

the second fault notification comprises an MEP detection point identification ID and a target address of the SR Policy tail end, and the target address is an IP address of the SR Policy head end.

According to the method for detecting the path fault, the method further comprises the following steps:

and if the SDN controller deploys hotspot protection, switching to other SR Policy candidate paths through the SDN controller, and sending the effectiveness of the SR Policy candidate paths and path switching information to equipment where an SR Policy head end is located.

if the periodic detection message is received again, determining that the fault is relieved;

determining whether the interval for sending the messages is a first interval or a second interval according to the period for detecting the messages;

and determining the period for sending the fault release notice according to the interval type, and sending the fault release notice in the period.

In a third aspect, the present invention further provides a head-end electronic device for SR policy, including a memory, a transceiver, and a processor;

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and implementing the steps of the method of path failure detection and notification as described above in relation to the first aspect.

In a fourth aspect, the present invention further provides a tail end electronic device for SR policy, comprising a memory, a transceiver, and a processor;

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and implementing the steps of the method of path failure detection and notification as described above in relation to the second aspect.

In a fifth aspect, the present invention further provides an apparatus for detecting and notifying a path failure, where the apparatus includes:

the first sending module is used for periodically sending a detection message to an MEP detection point configured at the tail end of the SR Policy through the MEP detection point configured at the head end of the SR Policy based on a one-way detection protocol to detect the SR Policy candidate path;

the first determining module is used for determining that the SR policy candidate path has a fault if a fault notification sent by an MEP detection point at the tail end of the SR policy is received;

In a sixth aspect, the present invention further provides an apparatus for detecting and notifying a path failure, where the apparatus includes:

a second receiving module, configured to receive, based on a unidirectional detection protocol, a detection packet periodically sent through an MEP detection point configured at a head end of the SR policy;

a second sending module, configured to determine that the SR policy candidate path has a fault if the detection packet is not received within a preset number of cycles, and send a fault notification to an MEP detection point at a head end of the SR policy;

In a seventh aspect, the present invention also provides a non-transitory computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for path failure detection and notification according to the first aspect, or implements the steps of the method for path failure detection and notification according to the second aspect.

In an eighth aspect, the present invention also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method for path failure detection and notification according to the first aspect described above, or implements the steps of the method for path failure detection and notification according to the second aspect described above.

The method and the device for detecting and notifying the path fault provided by the invention detect the SR Policy candidate path by periodically sending the detection message to the MEP detection point arranged at the tail end of the SR Policy in a one-way through the MEP detection point arranged at the head end of the SR Policy, determine that the SR Policy candidate path has the fault under the condition that the head end of the SR Policy receives the fault notification, and strictly ensure the correctness of the SR Policy candidate path detection.

Drawings

In order to more clearly illustrate the technical solutions of the present invention or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.

FIG. 1 is a flow chart of a method for detecting and notifying a path fault according to the present invention;

FIG. 2 is a schematic diagram of an RDI tag bit format;

fig. 3 is a schematic diagram of a CCM frame structure;

FIG. 4 is a second flowchart of the method for detecting and notifying a path fault according to the present invention;

FIG. 5 is a schematic diagram of SR Policy candidate path failure detection and notification provided by the present invention;

FIG. 6 is a schematic diagram of the SR Policy candidate path failure detection and notification provided by the present invention with a failure;

FIG. 7 is a schematic structural diagram of a head-end electronic device of SR policy provided in the present invention;

FIG. 8 is a schematic structural diagram of a tail-end electronic device of SR policy according to the present invention;

FIG. 9 is a schematic diagram of a path failure detection and notification apparatus according to the present invention;

fig. 10 is a second schematic structural diagram of the apparatus for detecting and notifying a path fault according to the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The method and apparatus for path failure detection and notification of the present invention are described below in conjunction with fig. 1-10.

SR Policy encodes the forwarding path of the data packet in the network to form a Segment list based on the user intention, issues the result to the network edge node, guides the data packet to be forwarded to the destination node based on the network path corresponding to the Segment list after entering the network, and accordingly achieves the traffic engineering intentions of high bandwidth, low time delay, non-intersecting paths and the like. The technology is easy to obtain an application-driven network architecture, and meets the requirements of large-scale, fine-grained and end-to-end SLA (Service Level Agreement) network transmission capability.

SR Policy is identified by the following three attributes (triplets):

head end (head): SR Policy generated nodes;

color (Color): is a 32-bit digital value that associates SR Policy with intent (e.g., low latency);

tail End (End Point): the destination address of SR Policy.

The forwarding path corresponding to SR Policy appears as a set of weighted sets of Segment list. Each Segment list represents a candidate forwarding path, and by combining the path validity, the candidate path preference value, the Segment list weight and the like, the active-standby protection or load balance of the SR Policy based on multiple forwarding paths can be realized.

Different from the traditional RSVP-TE (Resource Reservation Protocol-Traffic Engineering, based on Traffic Engineering extension) that senses the tunnel state through signaling link establishment, SR Policy does not have a signaling link, nor a tunnel interface, and as long as a network edge node (path head end) issues a Segment list (label stack), a candidate path corresponding to SR Policy is considered to be successfully created, and the true validity of the path needs to be verified by an additional mechanism, for example, by checking the candidate path corresponding to the Segment list in combination with a fast detection mechanism, when a fault is found, the SR Policy head end node is immediately notified, the candidate path is set to invalid, and the Traffic is switched to a standby protection path.

The SBFD is used for initiating Segment list forwarding path detection at the SR Policy head end, and the method is a common SR Policy candidate path validity detection means. The SBFD is a bidirectional path detection mechanism, and the link detection result is normal only if the outbound path and the return path are both normal, but the SR Policy candidate path itself is a unidirectional path. When the SR Policy itself is forwarded normally and the return IP path fails, the SR Policy head end will also receive the path failure notification of the SBFD, which further causes the Segment list forwarding path corresponding to the SR Policy to be set invalid, triggers the path switching, and triggers the flow error switching when the detection result is inconsistent with the Segment list validity corresponding to the SR Policy.

Based on the above problems, the technical scheme of the present invention is provided, and the core idea of the present invention is to periodically send a detection message to the tail end through the MEP detection point at the SR Policy head end, determine that the candidate path has a fault if the MEP detection point at the SR Policy tail end does not receive the detection message within a preset number of message periods, send a fault notification to the SR Policy head end through the data plane or the control plane, ensure that the SR Policy knows the candidate path fault, and take corresponding operations.

The invention provides a concept of combining SR Policy Path with unidirectional Detection, carries out certain transformation on a unidirectional Detection protocol, and applies a Y1731 unidirectional link Detection protocol which is originally applied to a two-layer direct link, a PW (pseudo wire) link and an LSP (Label Switched Path) link to the SR Policy link for operation, so that the fault Detection result is consistent with the connectivity condition of the SR Policy candidate Path, the problem of SR Policy Path fault false report caused by the fault of a return IP Path when BFD (Bidirectional Forwarding Detection) is used for SR Policy Path Detection is solved, the difficulty of judgment of operation and maintenance personnel on the real condition of the fault is improved, and the occurrence of Path false switch is reduced.

FIG. 1 is a flow chart of a method for detecting and notifying a path fault according to the present invention; as shown in fig. 1, the method for detecting and notifying a path fault is applied to an SR Policy head end, and includes:

step 101, based on a unidirectional detection protocol, periodically sending a detection message to an MEP detection point configured at the tail end of SR Policy through an MEP detection point configured at the head end of SR Policy, and detecting the SR Policy candidate path;

step 102, if a fault notification sent by an MEP detection point at the tail end of the SR policy is received, determining that a fault exists in the SR policy candidate path;

Specifically, according to the traffic transmission intention of the user, label stack forwarding information between the head end and the tail end is calculated, and an SR Policy candidate path is established, so that SR Policy triple and label stack information can be obtained. The unidirectional detection protocol refers to that an SR Policy head end sends a detection message to an SR Policy tail end or the SR Policy tail end sends the detection message to the SR Policy head end, wherein the head end and the tail end are relative. And configuring detection point information on the head end and the tail end of the SR Policy, and setting MEG (Maintenance Entity Group) and MEP (Maintenance Entity Group) detection points. The head end and the tail end of each SR Policy candidate path are respectively provided with an MEP detection point, an MEP ID identifies a specific detection end point, and the MEP detection point can send out and terminate detection messages. The MEG ID identifies the group of detection endpoints within the same administrative domain. The MEG ID identifies a management domain in all SR Policy candidate paths, each management domain comprises a plurality of pairs of MEP detection points, namely the head end and the tail end of each candidate path are respectively provided with one MEP detection point. The management domain identified by the MEG ID includes MEP detection points (a 1, a 2) in the candidate path a, MEP detection points (B1, B2) in the candidate path B, and MEP detection points (C1, C2) in the candidate path C, where a1, a2, B1, B2, C1, and C2 represent identifications of MEP detection points respectively, and represent MEP detection points located at the head end or the tail end of SR Policy.

And binding the MEP detection point at the head end of the SR Policy with one SR Policy candidate path, and configuring the MEP detection point at the tail end of the corresponding SR Policy as a peer MEP according to the SR Policy candidate path. And binding the MEP detection point at the SR Policy tail end with the IP address of the equipment at the SR Policy head end, and configuring the MEP at the corresponding head end as a peer MEP according to the SR Policy candidate path. If multiple SR Policy candidate paths to the same destination address need to be detected, the tail end of the SR Policy needs to be configured with multiple MEP detection points.

The MEP detection point at the head end of the SR Policy periodically sends a detection message to the MEP detection point at the tail end of the SR Policy, because the MEP detection point at the head end of the SR Policy is bound with the SR Policy candidate path, a forwarding path of the detection message is encapsulated by adopting label stack information corresponding to the SR Policy candidate path, and the forwarding path of the detection message is completely consistent with the forwarding path of the data message forwarded by using the SR Policy, namely, the path of the SR Policy head end MEP detection point for sending the detection message corresponds to the SR Policy candidate path bound with the head end MEP detection point.

When the forwarding path of the detection message fails, the MEP detection point at the tail end of the SR Policy cannot receive the corresponding detection message, and at the moment, the MEP detection point at the tail end of the SR Policy sends a failure notice to the MEP detection point at the head end of the SR Policy. Once the SR Policy head end receives the fault notification sent by the MEP detection point at the SR Policy tail end, the fault notification indicates that the corresponding SR Policy candidate path has a fault.

The method for detecting and notifying the path fault provided by the invention is characterized in that MEP detection points are respectively configured at the head end and the tail end of the SR Policy, an SR Policy path is bound at the head end MEP detection point, the IP address of the head end equipment is bound at the MEP detection point at the tail end, the detection message is ensured to be periodically sent to the tail end of the SR Policy according to the corresponding candidate path based on a one-way detection protocol, and the fault notification sent by the MEP detection point at the tail end according to the bound IP address of the head end equipment can be received under the condition that the candidate path has the fault, so that the corresponding candidate path information with the fault is obtained.

Optionally, the receiving the fault notification sent by the MEP detection point at the tail end of the SR policy includes:

wherein the first interval is less than the second interval.

Specifically, the interval of sending detection messages by MEP detection points at the SR Policy head end mainly includes two types:

one type is rapid detection, namely, the packet sending interval for sending the detection message is a first interval;

the other type is slow detection, namely the packet sending interval for sending the detection message is a second interval;

and the packet sending interval of the rapid detection is smaller than that of the slow detection, the rapid detection sends a detection message through a data plane, and the slow detection sends the detection message through a control plane.

When the MEP detection point at the head end of the SR Policy is rapid detection, that is, when the packet sending interval of a detection message sent by the MEP detection point at the head end of the SR Policy is a first interval, and when a fault exists in the SR Policy candidate path, the MEP detection point at the tail end of the SR Policy can send a detection result to the SR Policy head end through the data plane, the SDN controller, or the data plane and the SDN controller. The SDN controller is mainly configured to send a detection result through the SDN controller, that is, the detection result is reported to the device control plane through the data plane, and the device control plane continues to report the detection result to the SDN controller, so that when a fault exists in the data plane, the SR Policy's head end MEP detection point can still receive the detection result sent through the SDN controller, that is, the detection result is reported to the SR Policy's head end MEP detection point in the form of a fault notification, the fault notification is a detection packet carrying an RDI (Remote Defect Indication) flag, and a format of an RDI flag bit is shown in fig. 2. And the time consumption of the fault notification sent through the data plane is shorter, and the notification is more timely.

When the MEP detection point at the head end of the SR policy is slow detection, that is, when the packet transmission interval for transmitting the detection message by the MEP detection point at the head end of the SR policy is a second interval, the slow detection is longer than the packet transmission interval for fast detection. In the case of a failure of the SR Policy candidate path, the MEP detection point at the tail end of the SR Policy may be logged to the SR Policy head end through the control plane sending detection. The control plane is mainly sent by the SDN controller, the detection result is directly reported to the SDN controller for processing, and finally the detection result is sent to a head end MEP detection point of SR Policy in the form of fault notification, wherein the fault notification is a detection message carrying an RDI mark.

The method for detecting and notifying the path fault provided by the invention ensures that the fault message sent by the MEP detection point at the tail end of the SR Policy can also be sent to the head end of the SR Policy through the control plane, namely the SDN controller, under the condition that the data plane has a fault by adopting a fault notification sending mode comprising a data plane and a control plane.

Optionally, after receiving the first fault notification sent by the MEP detection point of the SR Policy tail end through the data plane and/or sent via the SDN controller, the method further includes:

Specifically, an MEP detection point at the SR Policy head end receives a first fault notification sent by the SR Policy tail end, the first fault notification is a detection message carrying an RDI mark, then candidate path information associated with the MEP detection point at the SR Policy head end is inquired through MEP ID information in the detection message, the MEP ID information in the detection message is matched with an MEP ID corresponding to the MEP detection point at the SR Policy tail end, a corresponding candidate path is obtained, and therefore the first fault candidate path with the fault is determined. And setting the first failure candidate path to invalid.

The method for detecting and notifying the path fault provided by the invention comprises the steps that by sending a detection message comprising RDI, SR Policy inquires a matched candidate path according to the detection message carrying the RDI, determines a candidate path with the fault, and sets the candidate path with the fault as invalid. Under the condition of quick detection, the candidate path of the fault can be quickly positioned and processed in time.

Optionally, the method further includes:

Specifically, the SR Policy head end directly determines or determines that hotspot protection is deployed on the first failure candidate path through a determination result forwarded by the SDN controller, and performs path switching to switch to other candidate paths. And for the condition that a plurality of candidate paths exist, selecting the path with higher preference value or lower preference value as the candidate path after switching based on the preference value of each candidate path.

The preference value of each candidate path may be set in advance by the SDN controller, or may be configured by a pre-configuration file.

According to the path fault detection and notification method provided by the invention, the hotspot protection is deployed on the SR Policy candidate path, so that under the condition that a fault exists in a certain candidate path, the path can be switched to other effective candidate paths in time, the data transmission is continued, and the continuity of the data transmission is ensured.

Optionally, after the receiving the second fault notification sent by the MEP detection point at the SR Policy tail end through the control plane, the method further includes:

Specifically, under the condition of slow detection, the SR Policy head end receives a second fault notification sent by the SR Policy tail end through the control plane, where the second fault notification is a detection message carrying RDI, and once the SR Policy head end receives the detection message carrying RDI, it determines that a fault exists in the candidate path, and determines an MEP detection point at the SR Policy tail end according to an MEP IP identifier included in the detection message, where the MEP detection point at the SR Policy head end matches the candidate path bound by the MEP detection point at the SR Policy head end according to the MEP ID at the SR Policy tail end, and determines a specific candidate path with the fault, that is, a second fault candidate path, and the second fault candidate path is set as invalid by the SR Policy head end.

In the method for detecting and notifying the path fault, under the condition of slow detection, an MEP detection point at the head end of the SR Policy receives a detection message which is sent by an MEP detection point at the tail end of the SR Policy and carries RDI, inquires the information of SR Policy candidate paths according to MEP ID included in the detection message, matches and determines the MEP detection point identification at the tail end of the SR Policy, determines the candidate paths with the fault, and sets the candidate paths with the fault as invalid, thereby avoiding invalid transmission and wasting network resources.

Optionally, the method further includes:

Specifically, when the SR Policy head end performs slow detection, the SDN controller determines that the hotspot protection is deployed in the second failure candidate path, and the SR Policy head end performs path switching to another candidate path. And for the condition that a plurality of candidate paths exist, selecting the path with higher preference value or lower preference value as the candidate path after switching based on the preference value of each candidate path.

According to the path fault detection and notification method provided by the invention, the existence of a fault path is determined under the condition of slow detection through the MEP detection point of the SR Policy head end, the SDN controller judges that the SR Policy candidate path deploys hotspot protection, and the MEP detection point of the SR Policy head end or the SDN controller sends an instruction to be switched to other candidate paths, so that the SR Policy head end can be switched to an effective candidate path to continue data transmission, and the continuity of data transmission is ensured.

Optionally, the period of the detection packet sent periodically is a packet sending interval of the detection packet configured at the MEP detection point at the head end of the SR Policy and the MEP detection point at the tail end of the SR Policy, and configuration parameters at both ends are consistent.

Specifically, the head end and the tail end of the SR Policy are relatively speaking, and both can send the detection message, and the packet sending intervals for sending the detection message are the same, so that it can be ensured that both ends synchronously receive and send the corresponding detection message.

Optionally, the detection packet is a CCM detection frame, and the label forwarding information of the detection packet is encapsulated by label stack information corresponding to the SR Policy candidate path.

Specifically, the detection messages are all CCM detection frames, a CCM frame format in a Y1731 protocol is used, a specific frame structure is shown in fig. 3, the Y1731 protocol specifies a unidirectional CCM detection protocol, and unidirectional detection of the SR Policy candidate path is realized, that is, the detection messages are sent from a head end MEP detection point of the SR Policy to a tail end MEP detection point of the SR Policy in a unidirectional manner, or sent from the tail end MEP detection point of the SR Policy to the head end MEP detection point of the SR Policy. The head end and the tail end are relative, two end points are determined according to the SR Policy candidate path, one end is the head end, and the opposite receiving end is the tail end.

The forwarding path of the detection message is determined according to the SR Policy candidate path, the specific SR Policy candidate path is represented as label stack information, and the label stack information is encapsulated in the detection message, namely the forwarding path of the detection message is determined.

The path fault detection and notification method provided by the invention realizes single detection of multiple SR Policy candidate paths by adopting CCM frames specified by Y1731 protocol as detection messages, and strictly ensures the accuracy of one-way detection.

Fig. 4 is a second flowchart of the method for detecting and notifying a path fault according to the present invention, and as shown in fig. 4, the method is applied to the tail end of SR Policy, and includes:

step 401, receiving a detection message periodically sent through an MEP detection point configured at the head end of SR policy based on a unidirectional detection protocol;

step 402, if the detection message is not received within a preset number of cycles, determining that the SR policy candidate path has a fault, and sending a fault notification to an MEP detection point at the head end of the SR policy;

Specifically, the unidirectional detection protocol refers to that the SR Policy head end sends a detection message to the SR Policy tail end, or the SR Policy tail end sends a detection message to the SR Policy head end, where the head end and the tail end are relatively speaking. After the SR Policy candidate path is established, detecting point information is configured on the head end and the tail end of the SR Policy, and MEG (Maintenance Entity Group) and MEP (Maintenance Entity Group) detecting points are set. The head end and the tail end of each SR Policy candidate path are respectively provided with an MEP detection point, an MEP ID identifies a specific detection end point, and the MEP detection point can send out and terminate detection messages. The MEG ID identifies the group of detection endpoints within the same administrative domain. The MEG ID identifies a management domain in all SR Policy candidate paths, each management domain comprises a plurality of pairs of MEP detection points, namely the head end and the tail end of each candidate path are respectively provided with one MEP detection point. The management domain identified by the MEG ID includes MEP detection points (a 1, a 2) in the candidate path a, MEP detection points (B1, B2) in the candidate path B, and MEP detection points (C1, C2) in the candidate path C, where a1, a2, B1, B2, C1, and C2 represent identifications of MEP detection points respectively, and represent MEP detection points located at the head end or the tail end of SR Policy.

And the MEP detection point at the tail end of the SR Policy receives the MEP detection point at the head end of the SR Policy and periodically sends a detection message, and because the MEP detection point at the head end of the SR Policy is bound with the SR Policy candidate path, the forwarding path of the detection message is the SR Policy candidate path bound with the MEP detection point at the head end of the SR Policy for sending the detection message.

And if the MEP detection point at the tail end of the SR Policy does not receive the detection message within a preset number of periods, determining that the corresponding SR Policy candidate path has a fault, and at the moment, sending a fault notice to the MEP detection point at the head end of the SR Policy by the MEP detection point at the tail end of the SR Policy to inform that the corresponding SR Policy candidate path has the fault.

Specifically, MEP detection points are respectively configured at the head end or the tail end of the SR Policy, the MEP detection points at the head end of the SR Policy periodically send detection messages to the MEP detection points at the tail end of the SR Policy, the sending period is the packet sending interval, and the packet sending interval parameters configured at the EMP detection points at the two ends are consistent. The method can ensure that EMP detection points at the head end and the tail end of the SR Policy synchronously transmit or receive detection messages.

Optionally, if the sending packet interval is a first interval, determining that the sending packet interval is rapid detection;

wherein the first interval is less than the second interval.

Specifically, an MEP detection point at the tail end of the SR Policy may send packet intervals according to received detection packets, that is, the interval time between every two data packets may be 3.33ms, 10ms, 100ms, 1s, 10s, 1min, 10min, and the like, for example, the packet sending intervals of 3.33ms, 10ms, and 100ms are used as first intervals, and the detection packets sent at the first intervals are fast detection; and correspondingly, packet sending intervals 1s, 10s, 1min and 10min are used as second intervals, the detection message sent in the second intervals is slow detection, and the packet sending intervals of the fast detection are smaller than the packet sending intervals of the slow detection.

The above is merely an exemplary illustration, and the specific division of the first interval or the second interval may be artificially determined or configured in advance according to the actual application scenario.

Optionally, if the packet sending interval is the first interval, after determining that the packet sending interval is the fast detection, the method further includes:

Specifically, under the condition of fast detection, in a candidate path of the SR Policy, MEP detection points at the head end and the tail end of the SR Policy are matched in pairs, and are mutually called peer MEPs; when an MEP detection point at the SR Policy tail end determines that a candidate path has a fault, determining a period for the SR Policy tail end to send a first fault notification according to a period for sending a detection message by the MEP detection point at the SR Policy head end; the method for sending the first fault notification to the IP address of the SR Policy head-end device bound to the SR Policy tail-end MEP detection point mainly includes: by the data plane, via an SDN controller, or both; that is, the first fault notification may be sent to the MEP detection point of the SR Policy head-end through both data plane and SDN controller. The sending of the first fault notification to the SR Policy head end through the SDN controller means that the MEP detection point at the SR Policy tail end reports the detection result to the control plane of the device through the data plane, reports the detection result to the SDN controller on the control plane of the device, and forwards the detection result to the MEP detection point at the SR Policy head end through the SDN controller. And the first fault notification also comprises an MEP detection point identification ID at the SR Policy tail end, and the MEP detection point used for the SR Policy head end matches the tail end MEP detection point in the locally stored SR Policy path according to the MEP detection point identification ID at the SR Policy tail end, so as to find out a candidate path with a fault.

In the method for detecting and notifying the path fault, when the candidate path fault is determined under the condition of rapid detection, the corresponding first fault notification is sent to the MEP detection point of the SR Policy head end through the data plane and/or the SDN controller, so that the MEP detection point of the SR Policy head end is ensured to receive the first fault notification, and the MEP detection point of the SR Policy head end determines the corresponding candidate path of the fault according to the first fault notification.

Optionally, the method further includes:

Specifically, when the MEP detection point at the SR Policy tail end determines that the data plane sending the first fault notification has a fault, the MEP detection point at the SR Policy tail end reports a detection result to the control plane through the data plane, and then the control plane reports the detection result to the SDN controller, and finally the SDN controller sends the detection result to the MEP detection point at the SR Policy head end in the form of fault notification, where the fault notification is the first fault notification.

After receiving the first fault notification, an MEP detection point of the SR Policy head end can acquire a candidate path of the fault and switch to other SR Policy candidate paths; or after the SDN controller sends the first fault notification, sending instructions to enable the SR Policy to execute switching of SR Policy candidate paths and enable the data transmission path to be switched to other SR Policy candidate paths.

In addition, the MEP detection point at the tail end of SR Policy sends the latest state of SR Policy candidate path to the head end of SR Policy.

The path fault detection and notification method provided by the invention has the advantages that under the condition of rapid detection, the first fault notification is sent through the data plane and/or through the SDN controller, so that the first fault notification sent through the SDN controller can be received by the MEP detection point of the head end of the SR Policy under the condition that the data plane has a fault, and the SR Policy is switched to other SR Policy candidate paths.

Optionally, if the packet sending interval is the second interval, after determining that the packet sending interval is the slow detection, the method further includes:

Specifically, in the candidate path of SR Policy, the MEP detection point at the head end and the MEP detection point at the tail end of SR Policy are matched in pairs, and are mutually called peer MEPs; the MEP detection point at the tail end of the SR Policy and the MEP detection point at the head end of the SR Policy are configured with the same period for sending the detection message, and the corresponding one-way detection is slow detection when the packet sending interval is determined to be the second interval.

Under the condition of slow detection, an MEP detection point at the tail end of the SR Policy determines a period for sending a second fault notification according to the period for sending a detection message by the MEP detection point at the head end of the SR Policy, and directly sends a detection result to the MEP detection point at the head end of the SR Policy through an SDN controller, wherein the sent target address is the IP address of SR Policy head-end equipment bound with the MEP detection point at the tail end of the SR Policy. And the detection result is sent in a fault notification mode, and during slow detection, the fault notification is the second fault notification which is a detection message carrying RDI. And the second fault notification also comprises an MEP detection point identification ID at the tail end of the SR Policy, so that after the MEP detection point at the head end of the SR Policy receives the second fault notification, according to the MEP detection point identification ID at the tail end of the SR Policy, the locally stored SR Policy candidate path is inquired, the MEP detection point identification ID at the tail end of the SR Policy corresponding to the SR Policy candidate path is matched, and the candidate path with the fault is determined.

Optionally, the method further includes:

and under the condition that the SDN controller determines that the Hotstandy protection is deployed, the SR Policy candidate path validity and the path switching information are sent to the equipment where the SR Policy head end is located.

Specifically, when a data plane has a fault, the SDN controller determines that the SR Policy candidate path deploys hotspot protection, and after the SDN controller sends a second fault notification, sends an instruction to an MEP detection point of the SR Policy head end to switch to another SR Policy candidate path, so that data is transmitted on the switched SR Policy candidate path. And the MEP detection point at the tail end of the SR Policy sends the validity of the SR Policy candidate path and the switching information of the path to the equipment where the SR Policy head end is located, wherein the equipment where the SR Policy head end is located mainly refers to a network communication switch. That is, the network communication switch obtains the validity of the SR Policy candidate path and the switching information of the path sent by the MEP detection point at the tail end of each SR Policy, and updates the information of all local SR Policy candidate paths.

According to the path fault detection and notification method provided by the invention, the hotspot protection is deployed on the SR Policy candidate path, so that the path can be switched to other candidate paths in time under the condition that the candidate path fault exists. Meanwhile, the MEP detection point at the tail end of the SR Policy sends the effectiveness of the SR Policy candidate path and the path switching information to the equipment where the SR Policy head end is located, and all SR Policy path information is updated.

Optionally, the method further includes:

Specifically, if the MEP detection point at the tail end of the SR Policy receives the periodic detection message of the MEP detection point at the head end of the SR Policy again, it is determined that the fault of the candidate path has been resolved.

Determining a period for sending a failure release notice according to the period for sending the detection message by the MEP detection point of the head end of the SR Policy, and determining whether a packet sending interval is a first interval or a second interval according to the period for sending the detection message by the MEP detection point of the head end of the SR Policy, namely determining whether the unidirectional detection is fast detection or slow detection.

If the detection is fast, sending a failure release notification to an MEP detection point of the SR Policy head end through the data plane and/or via the SDN controller.

And if the detection is slow, sending a fault release notice to an MEP detection point of the SR Policy head end through the control plane.

The method for detecting and notifying the path fault provided by the invention ensures that a detection message is periodically sent to the tail end of the SR Policy according to a corresponding candidate path through configuring MEP detection points at the head end and the tail end of the SR Policy respectively, binding an SR Policy path at the head end MEP detection point and binding the IP address of head end equipment at the tail end MEP detection point based on a one-way detection protocol, and can receive a fault release notification sent by the MEP detection point at the tail end of the SR Policy through a data plane and/or a control main and update the information of the SR Policy candidate path under the condition that the fault release exists in the candidate path.

Fig. 5 is a schematic diagram of SR Policy candidate path failure detection and notification provided by the present invention, as shown in fig. 5, the specific steps include:

1. SR Policy is created on PE3, a user intention and a tail end destination address corresponding to the SR Policy are configured on a head end node PE3, two candidate paths are explicitly issued after calculation by a controller, a path with a higher preference value becomes a main candidate path, the other path becomes a standby candidate path, and data traffic is forwarded by the main candidate path.

2. Configuring MEG group ID on PE1 and PE3 for creating a detection domain; both PE1 and PE3 have created and joined the same MEG group.

3. Configuring MEP detection points on PE1 and PE3 for creating detection points based on the main candidate path; an MEP1 is created on PE3 to serve as a detection starting point, main candidate path information is bound, a peer MEP is set to be an MEP2, PE1 serves as a detection terminal point, the peer MEP is configured to be an MEP1, and an IP address of an opposite end PE3 is set to be a fault notification destination address.

4. Creating detection points based on the candidate paths on PE1 and PE 3; an MEP3 is created on PE3 to serve as a detection starting point, standby candidate path information is bound, a peer MEP is set to be an MEP4, PE1 serves as a detection terminal point, the peer MEP is configured to be an MEP3, and an IP address of an opposite end PE3 is set to be a fault notification destination address.

5. Configuring a packet transmission interval of 3.33ms based on all MEPs, enabling detection of packets at head-end MEP1 and MEP3, and enabling connectivity detection at MEP2 and MEP 4; and the detection examples of the main and standby paths are issued to a data plane, a periodic packet sending logic is generated on the data plane of the head-end node, and an encapsulated detection message format is issued, so that the data plane can send packets quickly, a connectivity detection logic is generated on the data plane of the tail-end node, and an encapsulated detection message format carrying an RDI (remote data interface) label is issued, so that an announcement packet can be sent quickly after the data is checked to be in a fault.

6. The detection message of the main candidate path is periodically sent from the MEP1 to the MEP2, and the message forwarding path is consistent with the main candidate path; the detection message of the standby candidate path is periodically sent from the MEP1 to the MEP2, and the message forwarding path is consistent with the standby candidate path.

7. As shown in fig. 6, when the PE3 through P1 traversed by the primary candidate path has a fiber failure, the PE1 data plane does not receive any CCM frames from peer MEPs within a time interval 3.5 times the packet sending interval, and considers that a connectivity failure from the head end MEP to the tail end MEP is detected, and immediately sends the CCM frames carrying RDI flags, which are already stored in the data plane, to a destination address set under the MEP2 to notify the path head end of the failure. And reporting the detected connectivity problem to a device control plane, and informing the SDN controller of the fault by the device control plane.

8. The head-end device PE3 data plane receives a CCM frame carrying an RDI tag sent from the opposite end, proves that the remote end detects a fault, extracts MEP ID information in the CCM frame to match with remote MEP information, finds a local MEP according to the remote MEP information, and finds that the local MEP is a detection example of a main candidate path under the corresponding SR Policy. Therefore, the primary candidate path is invalid and triggers SR Policy to switch to the backup candidate path for traffic transmission. After the path switching is successful, the flow is transmitted through the standby candidate path, and the forwarding is recovered to be normal.

And 9, the SDN receives a fault notification sent by a PE1 device control plane, finds a corresponding head-end MEP according to the PE1 MEP ID, finds that the SR Policy main candidate path detects the fault, immediately sets the SR Policy main candidate path invalid, and performs path switching.

And 10, the SDN notifies the PE3 of the updated information, the PE3 updates the control plane information and issues a data plane switching action at the same time, and because the switching of the data plane is completed before, the processing is not performed, and the final path forwarding states of the control plane and the data plane are consistent.

FIG. 7 is a schematic structural diagram of a head-end electronic device of SR policy provided in the present invention; as shown in fig. 7, the SR policy headend electronics includes a memory 720, a transceiver 710, and a processor 700; wherein the processor 700 and the memory 720 may also be physically separated.

A memory 720 for storing a computer program; a transceiver 710 for transceiving data under the control of the processor 700.

In particular, the transceiver 710 is used to receive and transmit data under the control of the processor 700.

Where in fig. 7, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 700 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 710 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like.

The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 in performing operations.

The processor 700 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

The processor 700, by calling the computer program stored in the memory 720, is configured to execute any of the methods provided by the embodiments of the present application according to the obtained executable instructions, for example:

based on a unidirectional detection protocol, periodically sending a detection message to an MEP detection point configured at the tail end of the SR Policy through an MEP detection point configured at the head end of the SR Policy, and detecting the SR Policy candidate path;

under the condition that the interval of sending detection messages of the MEP detection points at the head end of the SR Policy is a first interval, receiving a first fault notification sent by the MEP detection points at the tail end of the SR Policy through a data plane;

and under the condition that the interval of sending the detection message of the MEP detection point at the head end of the SR Policy is a second interval, receiving a second fault notification sent by the MEP detection point at the tail end of the SR Policy through the control plane.

Optionally, after receiving the first fault notification sent by the MEP detection point at the SR Policy tail end through the data plane, the method further includes:

Optionally, the steps further include:

Optionally, after the receiving the second fault notification sent by the MEP detection point at the SR Policy tail end through the control plane, the step further includes:

Optionally, the steps further include:

It should be noted that, the head-end electronic device of SR Policy provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and details of the same parts and beneficial effects as those of the method embodiment in this embodiment are not described herein again.

FIG. 8 is a schematic structural diagram of a tail-end electronic device of SR policy according to the present invention; as shown in fig. 8, the tail end electronics of the SR policy includes a memory 820, a transceiver 810, and a processor 800; wherein the processor 800 and the memory 820 may also be physically separated.

A memory 820 for storing a computer program; a transceiver 810 for transceiving data under the control of the processor 800.

In particular, transceiver 810 is used to receive and transmit data under the control of processor 800.

Where in fig. 8, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 800 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 810 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like.

The processor 800 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 800 in performing operations.

The processor 800 may be a CPU, ASIC, FPGA or CPLD, and the processor may also employ a multi-core architecture.

The processor 800 is configured to execute any of the methods provided by the embodiments of the present application by calling the computer program stored in the memory 820, according to the obtained executable instructions, for example:

wherein the first interval is less than the second interval.

Optionally, the steps further include:

It should be noted that, the SR policy tail end electronic device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

FIG. 9 is a schematic diagram of a path failure detection and notification apparatus according to the present invention; as shown in fig. 9, the apparatus includes:

a first sending module 901, configured to send, based on a unidirectional detection protocol, a detection packet to an MEP detection point configured at the tail end of SR Policy periodically through an MEP detection point configured at the head end of SR Policy, so as to detect an SR Policy candidate path;

a first determining module 902, configured to determine that a fault exists in the SR policy candidate path if a fault notification sent by an MEP detection point at a tail end of the SR policy is received;

Optionally, the apparatus further includes a first receiving module 903, configured to receive, when an interval of sending the detection packet at the MEP detection point at the head end of the SR Policy is a first interval, a first fault notification sent by the MEP detection point at the tail end of the SR Policy over the data plane and/or sent via the SDN controller;

wherein the first interval is less than the second interval.

Optionally, the first determining module 902 is further configured to determine, based on the first fault notification, an MEP detection point identifier ID at the tail end of the SR Policy;

Optionally, the first receiving module 903 is further configured to trigger SR Policy to switch to another candidate path when the first failure candidate path deploys hotspot protection.

Optionally, the first determining module 902 is further configured to determine, based on the second fault notification, an MEP detection point identifier ID of the tail end of the SR policy;

Optionally, the first receiving module 903 is further configured to trigger SR Policy to switch to another candidate path when the SDN controller determines that the hotspot protection is deployed in the second failure candidate path.

FIG. 10 is a second schematic structural diagram of a path failure detection and notification apparatus provided in the present invention; as shown in fig. 10, the apparatus includes:

a second receiving module 1001, configured to receive, based on a unidirectional detection protocol, a detection packet periodically sent through an MEP detection point configured at a head end of the SR policy;

a second sending module 1002, configured to determine that the SR policy candidate path has a fault if the detection packet is not received within a preset number of cycles, and send a fault notification to an MEP detection point at a head end of the SR policy;

wherein the first interval is less than the second interval.

Optionally, the apparatus further includes a second determining module 1003, configured to determine, based on a period configured by peer MEP detection points of a head end of SR Policy, a period for sending a first fault notification;

a second sending module 1002, further configured to send a first fault notification to an MEP detection point of the SR Policy head end through a data plane and/or via an SDN controller;

Optionally, the second sending module 1002 is further configured to send, if the data plane fails, the first failure notification to an SR Policy head end through an SDN controller;

Optionally, the second determining module 1003 is further configured to determine, based on a period configured by peer MEP detection points of the SR Policy head end, a period for sending a second fault notification, send the second fault notification to the SR Policy head end through a control plane, and report the second fault notification to the SDN controller;

Optionally, the second sending module 1002 is further configured to send the SR Policy candidate path validity and the path switching information to a device where the SR Policy head end is located, when the SDN controller determines that hotspot protection is deployed.

Optionally, the second determining module 1003 is further configured to determine that the fault is resolved if the periodic detection message is received again;

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

It should be noted that the apparatus provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

In another aspect, the present invention also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the steps of the method for detecting and notifying a path failure provided by the above methods, applied to a head end of SR policy, for example, including:

In another aspect, the present invention also provides a computer program product, which includes a computer program stored on a non-transitory computer readable storage medium, the computer program including program instructions, when the program instructions are executed by a computer, the computer being capable of executing the steps of the method for detecting and notifying a path fault provided by the above methods, applied to the tail end of SR policy, for example, including:

On the other hand, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable the processor to execute the method for detecting and notifying a path failure provided in the foregoing embodiments, and the method is applied to a head end of SR policy, and includes:

On the other hand, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable the processor to execute the method for detecting and notifying a path failure provided in the foregoing embodiments, and apply to a tail end of SR policy, and for example, the method includes:

The processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A method for detecting and notifying a path fault is applied to a head end of SR policy, and comprises the following steps:

2. The method of claim 1, wherein the step of receiving the fault notification sent by the MEP detection point at the tail end of SR policy comprises:

wherein the first interval is less than the second interval.

3. The method for path fault detection and notification according to claim 2, wherein after receiving the first fault notification sent by the MEP detection point of the SR Policy tail-end through the data plane and/or sent via the SDN controller, the method further comprises:

4. The method of path failure detection and notification according to claim 3, further comprising:

5. The method for path fault detection and notification according to claim 2, wherein after receiving a second fault notification sent by an MEP detection point at an SR Policy tail end through a control plane, the method further comprises:

6. The method of path failure detection and notification according to claim 5, further comprising:

7. The method of path failure detection and notification according to any of claims 1 to 6, wherein:

the period of the detection messages sent periodically is the packet sending interval of the detection messages configured on the MEP detection point at the head end of the SR Policy and the MEP detection point at the tail end of the SR Policy, and the configuration parameters at the two ends are consistent.

8. The method of path failure detection and notification according to any of claims 1 to 6, wherein:

the detection message is a CCM detection frame, and the label forwarding information of the detection message is encapsulated by label stack information corresponding to the SR Policy candidate path.

9. A method for path fault detection and notification is applied to a tail end of SR policy, and comprises the following steps:

10. The method of path failure detection and notification according to claim 9, wherein:

11. The method of path failure detection and notification according to claim 10, wherein:

if the packet sending interval is a first interval, determining the packet sending interval as fast detection;

wherein the first interval is less than the second interval.

12. The method of claim 11, wherein after determining to be a fast detection if the packet sending interval is a first interval, the method further comprises:

13. The method of path failure detection and notification according to claim 12, further comprising:

14. The method of claim 11, wherein after determining to be slow detection if the packet transmission interval is the second interval, the method further comprises:

determining a period for sending a second fault notification based on a period for sending a detection message configured by a peer-to-peer MEP (message exchange protocol) of a head end of SR Policy, and reporting the second fault notification to an SDN (software defined network) controller;

15. The method of path failure detection and notification according to claim 14, further comprising:

16. The method of path failure detection and notification according to claim 11, further comprising:

17. A head-end electronic device of SR policy comprises a memory, a transceiver and a processor;

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for executing a computer program in said memory and implementing the steps of the method of path failure detection and notification according to any of claims 1 to 8.

18. The terminal electronic equipment of SR policy comprises a memory, a transceiver and a processor;

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for executing a computer program in said memory and implementing the steps of the method of path failure detection and notification according to any of claims 9 to 16.

19. An apparatus for path failure detection and notification, the apparatus comprising:

20. An apparatus for path failure detection and notification, the apparatus comprising:

21. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to perform the method of path failure detection and notification of any of claims 1 to 8, or the method of path failure detection and notification of any of claims 9 to 16.