WO2016008322A1

WO2016008322A1 - Path connectivity test method and device

Info

Publication number: WO2016008322A1
Application number: PCT/CN2015/077377
Authority: WO
Inventors: 徐小虎; 尤建洁
Original assignee: 华为技术有限公司
Priority date: 2014-07-18
Filing date: 2015-04-24
Publication date: 2016-01-21
Also published as: CN105337785B; CN105337785A

Abstract

Provided in an embodiment of the present invention are a path connectivity test method and device. The method comprises: a receiving node receives an echo request transmitted by a transmitting node, the echo request comprising an identifier of a service function (SF), the packet header of the echo request comprising information on a path to the SF, the path information comprising a segment identifier (SID) of the SF; when the receiving node determines, on the basis of the SID of the SF, that the SF is associated with the receiving node, determining whether the SID corresponding to an SF stored by the receiving node is consistent with the SID of the SF contained in the path information; if so, then determining that the path to the SF has connectivity, and the receiving node transmits a first echo reply to the transmitting node, the value of a return code carried in the echo reply indicating that the path to the SF has connectivity. The invention realizes an effective test of path connectivity.

Description

Path connectivity detection method and device

This application claims the priority of the Chinese Patent Application filed on July 18, 2014, the Chinese Patent Application No. CN 201410344976.0, entitled "A Path Connectivity Test Method and Apparatus", the entire contents of which are incorporated by reference. In this application.

Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a path connectivity detection method and apparatus.

Background technique

As the types of services of operators increase, in order to provide a better service experience, a service routing network needs to be deployed, so Service Funcition Chaning (SFC) technology has been developed. Service chain technology can link multiple business functions and provide the foundation for flexible business processing. As shown in Figure 1, the service classifier classifies the data flows entering the service routing domain, and then forwards the selected data flows along the service function path (SFP) corresponding to the SFC. In this process, the service function (SF) that the SFP passes through performs corresponding service processing on the data stream. The SF may be a module inside a Service Node (SN) system.

When implementing SFC in a Segament Routing (SR) network, a Segment List is usually used to represent an SFP. Taking the service processing scenario shown in Figure 1 as an example, describe an SFP, namely {SN1, SF A, SF B, SN2, SF C}. The corresponding segment list is: {SID(SN1), SID(SF A) SID (SF B), SID (SN2), SID (SF C), where the Segment Identifier (SID) is an identifier assigned by the SR network to the SN or the Service Function SF for guiding forwarding. In the prior art, the SID can be represented by a Multi-Protocol Label Switching (MPLS) label or an Internet Protocol Version 6, IPv6 address. When the SID is represented by an MPLS label, the SID of the SN is a global or local MPLS label, and the SID of the SF is a global or local MPLS label; when the SID is represented by an IPv6 address, the SID of the SN is an IPv6 global address, and the SID of the SF is Link-local address (LLA).

However, when SFC is implemented in an SR network, the operation, management, and maintenance of the SF cannot be realized. (Operation Administration Maintenance, OAM) functions, for example, failing to implement connectivity and availability detection for SF. This is because the detection of SF connectivity or availability is not supported in existing MPLS OAM technologies. In addition, in the existing IPv6 protocol, the IPv6 ping command is generally used to detect the connectivity of the path. When the IPv6 ping command is used to detect the LLA address, the IPv6 ping command usually requires the sender of the command to be directly connected to the receiver. However, for the SFC scenario, the sender of the detection command (eg, the classifier) is not directly connected to the receiver SF. Therefore, when the IPv6 address is used to indicate the segment identifier SID of the SN or SF, the path cannot be detected using the IPv6 Ping command. Connectivity.

Therefore, there is no method and device in the prior art, which can detect the path connectivity in the SR network, so as to implement the OAM function in the SR-SFC network.

Summary of the invention

The embodiment of the invention provides a path connectivity detection method and device, which can implement path connectivity detection in an SR network, and is beneficial to implementing OAM functions in an SR-SFC network.

To this end, the embodiments of the present invention provide the following technical solutions:

According to a first aspect of the embodiments of the present invention, a path connectivity detection method is provided, where the method is applicable to an SR network, and the method includes:

The receiving node receives an Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF, where the path information includes The SID of the SF;

When the receiving node determines that the SF is associated with the receiving node according to the identifier of the SF, determining whether the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information ;

When the receiving node determines that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, determining that the path to the SF is connected, the receiving node is The sending node sends a first echo response (Echo Reply) message, and the value of the return code carried in the first Echo Reply message is used to indicate that the path to the SF is connected.

In a first possible implementation manner of the first aspect, the method further includes:

When the receiving node determines the SID corresponding to the SF stored by the receiving node and the path When the SIDs of the SFs included in the information are inconsistent, the path to the SF is determined to be disconnected, and the receiving node sends a second Echo Reply message to the sending node, where the second Echo Reply message carries the value of the return code. The value of the return code is used to indicate that the path to the SF is not connected.

In a second possible implementation manner of the first aspect, the method further includes:

When the receiving node determines that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state;

The detecting whether the SF is in an available state includes:

The receiving node sends a status detection request to the SF, receives a status response message sent by the SF, and determines, according to the status response message, whether the SF is in an available state; or

And receiving, by the receiving node, a status report message that is sent by the SF, and determining, according to the status report message, whether the SF is in an available state.

With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, when the determining that the SF is in an unavailable state, the return that is carried by the first Echo Reply message The value of the code is used to indicate that the SF is in an unavailable state.

According to a second aspect of the embodiments of the present invention, a method for path connectivity detection is provided, where the method is applicable to an SR network, and the method includes:

The sending node constructs an Echo Request message, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF;

Sending, by the sending node, the Echo Request message to the receiving node according to the path information, where the receiving node is a destination SN corresponding to the SF;

The sending node receives an Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message;

The sending node determines, according to the Echo Reply message, whether a path to the SF is connected.

In a first possible implementation manner of the second aspect, the path information includes shortest path information or explicit path information, where:

The shortest path information includes a SID of the destination SN and an SID of the SF;

The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF.

With reference to the first possible implementation of the second aspect, in a second possible implementation manner of the second aspect, the SID of the destination SN and the SN is an MPLS label, and the SID of the SF is MPLS label; or,

The SID of the destination SN is an IPv6 global address, and the SID of the SF is an LLA.

With reference to the foregoing second aspect or any one of the foregoing possible implementations of the foregoing aspect, in a third possible implementation manner of the second aspect, the Echo Request message is an MPLS Echo Request message, and correspondingly, the Echo The reply message is an MPLS Echo Reply message, and the Echo Request message includes the identifier of the SF, which is specifically:

A service SF Equivalence Class (FEC) field is added to the MPLS Echo Request message, and the SF identifier is carried in the SF FEC field.

In combination with the foregoing second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect, the fourth possible implementation manner of the second aspect The Echo Request message is an Internet Control Message Protocol (VIP) 6th Echo Request message. The Echo Request message is an ICMPv6Echo Reply message, and the Echo Request message includes an SF identifier. for:

A service function identifier (SF ID) field is added to the ICMPv6 Echo Request message, and the identifier of the SF is carried by the SF ID field.

With reference to the foregoing second aspect or any one of the foregoing possible implementation manners of the foregoing aspect, in a fifth possible implementation manner of the second aspect, the sending node determines, according to the Echo Reply message, the arrival of the SF Whether the path is connected includes:

The sending node determines, according to the value of the return code carried in the Echo Reply message, whether the path to the SF is connected.

With reference to the foregoing second aspect or any one of the foregoing possible implementation manners of the foregoing aspect, in the sixth possible implementation manner of the second aspect, the Echo Request message is configured to detect whether the SF is available. And detecting the identifier, where the detection identifier is used to indicate that the destination SN detects whether the SF is in an available state.

According to a third aspect of the embodiments of the present invention, there is provided a path connectivity detecting apparatus, the apparatus being applicable to an SR network, the apparatus comprising:

a receiving unit, configured to receive an Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the SF, where a packet header of the Echo Request message includes path information that reaches the SF, where the path information includes SID of SF;

a determining unit, configured to determine, when the SF is associated with the device according to the identifier of the SF, Determining whether the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information; and sending, by the determining unit, determining, by the determining unit, an SID corresponding to the SF stored by the device When the SIDs of the SFs in the path information are consistent, the path to the SF is determined to be connected, and the first Echo Reply message is sent to the sending node, and the value of the return code carried in the first Echo Reply message is Used to indicate the path connectivity to the SF.

In a first possible implementation manner of the third aspect, the sending unit is further configured to:

When the determining unit determines that the SID corresponding to the SF stored by the device does not match the SID of the SF included in the path information, determining that the path to the SF is not connected, and sending the first to the sending node And a second Echo Reply message, where the second Echo Reply message carries a value of a return code, where the value of the return code is used to indicate that the path to the SF is disconnected.

In a second possible implementation manner of the third aspect, the device further includes:

a detecting unit, configured to: when the determining unit determines that the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state;

The detecting unit is specifically configured to:

Sending a status detection request to the SF, receiving a status response message sent by the SF, determining, according to the status response message, whether the SF is in an available state; or receiving a status report message sent by the SF, according to the The status report message determines if the SF is in an available state.

In conjunction with the second possible implementation of the third aspect, in a third possible implementation manner of the third aspect, the sending unit is further configured to:

And when the detecting unit determines that the SF is in an unavailable state, the value of the return code carried by the first Echo Reply message sent to the sending node is used to indicate that the SF is in an unavailable state.

According to a fourth aspect of the present invention, there is provided a path connectivity detecting apparatus, the apparatus being applicable to an SR network, the apparatus comprising:

a constructing unit, configured to construct an Echo Request message, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF;

a sending unit, configured to send the Echo Request message to the receiving node according to the path information, where the receiving node is a destination service node SN corresponding to the SF;

a receiving unit, configured to receive an echo response Echo Reply message sent by the receiving node, where The Echo Reply message is a response message for the Echo Request message;

And a determining unit, configured to determine, according to the Echo Reply message, whether a path to the SF is connected.

In a first possible implementation manner of the fourth aspect, the path information included in the packet header of the Echo Request message constructed by the constructing unit includes shortest path information or explicit path information, where:

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the SID of the destination SN and each SN is an MPLS label, and the SID of the SF is MPLS. The SID of the destination SN is an IPv6 global address, and the SID of the SF is an LLA.

With reference to the fourth aspect, or any one of the foregoing possible implementation manners of the fourth aspect, in the third possible implementation manner of the fourth aspect, the Echo Request message configured by the constructing unit is an MPLS Echo Request message, corresponding to The Echo Reply message received by the receiving unit is an MPLS Echo Reply message, and the constructing unit is specifically configured to:

An SF FEC field is added to the MPLS Echo Request message, and the identifier of the SF is carried in the SF FEC field.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, to any one of the second possible implementation manner of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, The Echo Request message constructed by the structuring unit is an ICMPv6Echo Request message, and the Echo Reply received by the receiving unit is an ICMPv6Echo Reply message, where the constructing unit is specifically configured to:

A service function identifier SF ID field is added to the ICMPv6 Echo Request message, and the identifier of the SF is carried by the SF ID field.

With reference to the fourth aspect, or any one of the foregoing possible implementation manners of the fourth aspect, in the fifth possible implementation manner of the fourth aspect, the determining unit is specifically configured to:

Determining whether the path to the SF is connected according to the value of the return code carried in the Echo Reply message.

With the fourth aspect or any one of the possible implementation manners of the fourth aspect, in the sixth possible implementation manner of the fourth aspect, the Echo Request message configured by the constructing unit is configured to detect the SF Whether the detection identifier is available, and the detection identifier is used to indicate that the destination SN detects whether the SF is in an available state.

The path connectivity detection method and device provided by the embodiment of the present invention determines the SF according to the identifier of the SF carried in the Echo Request message and the path information included in the packet header of the Echo Request message, by receiving the Echo Request message. When it is associated with the receiving node, it is determined whether the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, and the SID corresponding to the SF and the path information stored by the receiving node are determined. If the SIDs of the SFs are consistent, the path to the SF is determined to be connected, and the Echo Reply message is sent to the sending node, so that the sending node determines the path to the SF according to the value of the return code carried in the Echo Reply message. Connected. The method provided by the embodiment of the invention implements the detection of the connectivity of the service chain SFC path in the SR network, and is beneficial to implementing the OAM function in the SR-SFC network.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only These are some of the embodiments described in this application, and other figures can be obtained from those of ordinary skill in the art in view of these drawings.

1 is a schematic diagram of a service chain technology in the prior art;

2 is a schematic flowchart of a path connectivity detecting method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an implementation manner of an Echo Request message according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart diagram of a method for detecting path connectivity according to an embodiment of the present disclosure;

5 is a schematic structural diagram of an MPLS Echo Request message in the prior art;

FIG. 6 is a schematic diagram of an implementation form of a TLV field of an SF FEC according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of an implementation form of adding an SF ID field to an ICMPv6 Echo Request message according to an embodiment of the present disclosure;

FIG. 8 is a schematic flowchart of a path connectivity detection method according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of an implementation manner of an MPLS Echo Request message according to an embodiment of the present disclosure;

FIG. 10 is a schematic flowchart of a path connectivity detection method according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of an implementation manner of an ICMPv6 Echo Request message according to an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of a path connectivity detecting apparatus according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of a path connectivity detecting apparatus according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of a path connectivity detecting apparatus according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a path connectivity detecting apparatus according to an embodiment of the present invention.

detailed description

In the prior art, when SFC is implemented in an SR network, the OAM function for the SF cannot be implemented. For example, path connectivity and availability detection for the SF cannot be implemented. This is because the detection of SF connectivity or availability is not supported in the existing MPLS OAM technology. In addition, in the existing IPv6 protocol, the IPv6 Ping command is generally used to detect the connectivity of the path. When the IPv6 Ping is used to detect the LLA address, the IPv6 Ping command usually requires the sender of the command to be directly connected to the receiver. However, for the SFC scenario, the sender of the detection command (eg, the classifier) is not directly connected to the receiver SF. Therefore, when the IPv6 address is used to indicate the segment identifier SID of the SN or SF, the path cannot be detected using the IPv6 Ping command. Connectivity.

However, in the SR-SFC network, when the SID of the SF is sent by the control plane of the service node SN, the SID allocated by the control plane of the SN and the SID of the SF saved in the forwarding plane may be caused by a fault or an error. There are inconsistencies. Therefore, there is a need for a path connectivity detection method and apparatus for detecting path connectivity when an error occurs in a data plane (forward plane) to implement OAM functions in an SR-SFC network.

Based on this, the embodiment of the present invention provides a path connectivity detection method and device, which can implement path connectivity detection in an SR network, and is beneficial to implementing OAM functions in an SR-SFC network.

In order to make those skilled in the art better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. The embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of the present invention.

The terms used in the embodiments of the present invention are for the purpose of describing particular embodiments only and are not intended to limit the invention. The singular form "a" used in the embodiments of the invention and the appended claims The terms "and" and "the" are also intended to include the plural unless the context clearly indicates otherwise. It is also understood that the term "and/or" as used herein means and includes one or more List any or all possible combinations of items.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a method for detecting a path connectivity according to an embodiment of the present invention, which is applicable to an SR network, and may include the following steps:

S201: The receiving node receives an Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF, where the path information includes the SF. SID.

The identifier SF ID of the SF is used to identify an SF in a SFC-enabled domain or a Service Chain Domain. The service chain domain includes nodes on the service chain, and usually includes at least one service classifier and one or more service nodes SN, and each service node SN is associated with one or more SFs. The SF and the SN associated with it can be implemented in the same system. For example, the SF can be a module inside the SN system, and the communication between the SN and the SF is a private implementation. Of course, the SF can also exist independently of the SN, for example, by using a separate server, a virtual machine (VM) on the server, a proprietary hardware device, and the like, and connecting to the SN. The SR network may include one or more service chain domains. Taking the service chain diagram shown in Figure 1 as an example, the service chain domain includes an ingress SN, which can be a Service Classifier and two service nodes SN1 and SN2 and an egress SN. SN1 associates SF A and SF. B, SN2 is associated with SF C. SF A, SF B, and SF C have their corresponding SF IDs, which are used to uniquely identify the corresponding SFs in the service chain domain.

Depending on the implementation, the Echo Request message may contain different implementations of the SF ID. In a possible implementation, the Echo Request message is an MPLS Echo Request message, and the Echo Request message includes the SF ID, and the SF FEC field may be added to the MPLS Echo Request message. The SF ID is carried in the SF FEC field. In another possible implementation manner, the Echo Request message is an ICMPv6Echo Request message, and the Echo Request message includes an SF ID, which may be: adding a service function identifier SF ID field in the ICMPv6 Echo Request message, by using the SF The ID field carries the SF ID. The specific form of the SF ID may be very flexible, for example, by using a string or by using address information, as long as the service function SF can be uniquely identified in the service chain domain, which is not limited by the embodiment of the present invention.

The path information of the SF is included in the packet header of the Echo Request. The sending The node sends the Echo Request message to the receiving node according to the path information. Specifically, the receiving node is a destination SN corresponding to the SF. The path information includes an SID of the SF. As shown in FIG. 3, it is a representation form of an Echo Request message received by a receiving node. The path information is encapsulated in the header of the Echo Request message, and the path information is expressed in the form of an SR (Segment Routing) header. The path information may be expressed in different forms, for example, may include shortest path information or explicit path information, where: the shortest path information includes a SID of a destination SN and an SID of the SF. The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF. As shown in Figure 1, the Echo Request message sent by the sending node carries the SF ID of the SF C. The path information contained in the header of the Echo Request message is represented by the shortest path information: {SID(SN2) , SID (SF C)}. It is assumed that the Echo Request message sent by the sending node carries the SF ID of the SF C, and the path information included in the header of the Echo Request message is represented by the display path information: {SID(SN1), SID(SN2), SID( SF C)}.

S202, when the receiving node determines that the SF is associated with the receiving node according to the identifier of the SF, determining whether the SID corresponding to the SF stored by the receiving node is related to the SF included in the path information. The SID is consistent.

The receiving node determines that the SF is associated with the receiving node according to the SF ID included in the Echo Request message. The associating the SF with the receiving node includes: connecting, in the receiving node of the SF, or the receiving node, outside the receiving node. When the SF is in the receiving node, the SF may be a module inside the receiving node; when the SF is outside the receiving node, the SF is independent of the receiving node, and may be at the server, The VM, the proprietary hardware device is implemented and connected to the receiving node. The receiving node determines whether the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information. In a specific implementation, the SID of the SF corresponding to the SF ID saved in the receiving node is obtained, and the SID of the obtained SF is compared with the SID of the SF included in the path information. In a specific implementation, the receiving node obtains the SID of the SF corresponding to the SF ID saved in the forwarding plane according to the SF ID. The present invention does not limit the form in which the service node saves the SID of the SF. The service node may also store a correspondence between the SF ID and the SID of the SF, and determine the SID corresponding to the SF ID according to the correspondence.

S203, when it is determined that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, determining that the path to the SF is connected, and the receiving node is sent to the sending node. Sending a first Echo Reply message, where the first Echo Reply message carries a return The value of the code, the value of the return code is used to indicate the path connectivity to the SF.

When it is determined that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, it is determined that the message can be forwarded to the correct SF according to the SFC path indicated by the SID, so , determine the path connectivity to the SF. At this time, the receiving node sends the first Echo Reply message to the sending node, the value of the return code carried in the first Echo Reply message, and the value of the return code is used to indicate that the path to the SF is connected. In a specific implementation, when the Echo Request message is an MPLS Echo Request message, the first Echo Reply message is an MPLS Echo Reply message. When the first Echo Request message is an ICMPv6Echo Request message, the Echo Reply is an ICMPv6Echo Reply message. In a specific implementation, when it is determined that the path to the SF is connected, the return code of the MPLS Echo Reply message sent by the receiving node to the sending node is zero, that is, return code=0.

Determining, by the receiving node, that the SF is not associated with the receiving node according to the identifier of the SF, or determining that the SID corresponding to the SF stored by the receiving node is inconsistent with the SID of the SF included in the path information. Determining that the path to the SF is not connected, the receiving node sends a second Echo Reply message to the sending node, and the value of the return code carried by the second Echo Reply message is used to indicate the path to the SF. Not connected. In a specific implementation, when the second Echo Request message is an MPLS Echo Request message, the second Echo Reply message is an MPLS Echo Reply message, and the value of the return code is carried in the MPLS Echo Reply message, for example, return When code=10, the indicator tag is not a specific tag in the tag path. When the Echo Request message is an ICMPv6Echo Request message, the response message is a destination address unreachable Destination Unreachable Message. The value of the return code of the response is carried in the Destination Unreachable Message to indicate that the path to the SF is disconnected.

It should be noted that when the receiving node determines, according to the SF ID, that the SID of the SF does not exist in the forwarding plane, or determines that there is no SID in the forwarding plane that is consistent with the SID of the SF included in the path information, It is also determined that the path to the SF is not connected. When the SF and its associated SN are implemented within the same system, for example, the SF may be a module internal to the SN system, and the SN may implement private communication with the SF. When the SF is independent of the SN, the SN can determine whether the physical link between the SN and the SF is in a normal connection state by checking a port or a VLAN (Virtual Local Area Network) interface. When the SN determines that the physical link between the SN and the SF is not normally connected, the corresponding information of the SF saved in the forwarding plane, such as the SID of the SF, is deleted. Therefore, when receiving The node determines, according to the SF ID, that there is no SID corresponding to the SF in the forwarding plane, and also determines that the path to the SF is disconnected.

In a possible implementation, when it is determined that the SID corresponding to the SF saved by the receiving node is consistent with the SID of the SF included in the path information, whether the SF is in an available state is further detected. In a possible implementation, the Echo Request message may carry a detection identifier for detecting whether the SF is available, and the detection identifier is used to indicate that the destination SN detects whether the SF is in an available state. When the receiving node determines that the received Echo Request message carries the detection identifier, it further detects whether the SF is in an available state. Of course, in another possible implementation manner, the receiving node may decide whether to perform the SF availability detection. For example, the receiving node determines whether to detect whether the SF is in an available state according to its own policy. The embodiment of the present invention does not limit the conditions for triggering the SN node to detect the available state of the SF.

The detecting whether the SF is in an available state includes: the receiving node sending a status detection request to the SF, receiving a status response message sent by the SF, and determining, according to the status response message, whether the SF is available. a state; or, the receiving node receives a status report message that is sent by the SF, and determines, according to the status report message, whether the SF is in an available state. . Whether the SF is in an available state may include detecting whether the SF is faulty or detecting whether the SF supports the corresponding service function. When the SF fails and the load is too high, the SF can be in an unavailable state. When determining, according to the status response message or the status report message, that the SF is in an unavailable state, the receiving node sends an Echo Reply message to the sending node, where a value of a return code carried in the Echo Reply message is used to indicate the SF is in an unavailable state. For example, the receiving node adds a return code in the MPLS Echo Reply message to indicate that the SF is in an unavailable state. For another example, the receiving node adds a return code in the Destination Unreachable Message to indicate that the SF is in an unavailable state.

Optionally, the SF ID may be carried in the response message sent by the receiving node.

In a possible implementation manner, the Echo Request message further includes an FEC of the destination service node SN, and the FEC information of the destination SN is used to detect whether the path to the destination service node is connected. In specific implementation, the value of the FEC of the SN may be the IP address of the SN. The SN determines whether there is a SID of the SN corresponding to the FEC of the SN according to the FEC of the SN; if yes, it determines whether the SID of the SN is consistent with the SID of the SN included in the path information. If consistent, it is determined that the path to the SN is connected. If there is no SID corresponding to the SN or the SID corresponding to the SN does not match the SID of the SN included in the path information, it is determined that the path to the SN is not connected. When it is implemented, when When the value of the FEC of the SN is the IP address of the SN, the SN determines whether the SID of the SN corresponding to the IP address is stored; if so, whether the SID of the SN corresponding to the IP address stored in the self is compared with the Echo Request message. The SIDs included in the SN are the same. If they are the same, the path to the SN is determined to be connected. If the SID of the SN corresponding to the IP address is different or does not exist, it indicates that the wrong SN or the path information error may have been reached, that is, the path to the SN indicated in the path information is not connected.

The path connectivity detection method provided by the embodiment of the present invention determines the SF and the receiving by receiving the Echo Request message according to the identifier of the SF carried in the Echo Request message and the path information included in the packet header of the Echo Request message. When the node is associated, it is determined whether the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, and the SID corresponding to the SF stored in the receiving node and the path information included in the path information are determined. If the SIDs of the SFs are consistent, the Echo Reply message is sent to the sending node, so that the sending node determines the path connectivity to the SF according to the value of the return code carried in the Echo Reply message. The method provided by the embodiment of the invention implements the detection of the connectivity of the service chain SFC path in the SR network, and is beneficial to implementing the OAM function in the SR-SFC network.

Referring to FIG. 4, FIG. 4 is a schematic flowchart of a path connectivity detection method according to an embodiment of the present invention. The method is applicable to an SR network, and the method may include:

S401: The sending node constructs an Echo Request message, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF.

In a specific implementation of the embodiment of the present invention, the sending node may be a classifier or other network element, for example, a policy decision point (PDP), which is not limited by the present invention.

The sending node constructs an Echo Request message. As shown in FIG. 3, it is a representation form of an Echo Request message received by a receiving node. The Echo Request message includes an identifier SF ID of the SF, where the SF ID is used to identify an SF in a service routing domain or a service chain domain.

Depending on the implementation, the Echo Request message may have different implementations including the SF ID. In a possible implementation, the Echo Request message is an MPLS Echo Request message, and the MPLS Echo Request message includes an SF ID, and the SF FEC field may be added to the MPLS Echo Request message. The SF ID is carried in the SF FEC field. 5 is a schematic structural diagram of an MPLS Echo Request message, where the MPLS Echo Request message includes a Version Number, a Global Flag, and a message. Message Type, Reply Mode, Return Code, RReturn Subcode, Sender's Handle, Sequence Number, Transmit Timestamp/sec (TimeStamp) Sent (seconds), TimeStamp Sent (microseconds), TimeStamp Received (seconds), TimeStamp Received (microseconds), and multiple types, lengths The Type Length Value (TLV) field. The SF FEC may be carried in the TLVs portion of FIG. 5 in a TLV manner. In specific implementation, the SF FEC may be as shown in FIG. 6: the Sub Type may be 17, the Length may be 4 bytes, and the Value Field may be the SF ID. The above is only an illustrative example and is not to be construed as limiting the embodiments of the present invention.

In another possible implementation manner, the Echo Request message is an ICMPv6Echo Request message, and the Echo Request message includes an SF ID, which may be: adding an SF ID field in the ICMPv6Echo Request message, and carrying the SF ID field by using the SF ID field. The SF ID. As shown in FIG. 7, an implementation form of adding an SF ID field (or parameter) to an ICMPv6 Echo Request message is shown. The type type may be equal to 128, which is used to indicate that it is an Echo Request message; the code value Code may be equal to 1 for indicating a service function check (Service Function Check); and the SF ID is data carried in the Echo Request message (The data From the invoking Echo Request message), used to uniquely identify the SF ID. The ICMPv6Echo Request message may further include a checksum, an identifier, and a sequence number field.

In the above implementation manners, the specific form of the SF ID may be very flexible, for example, using a string or using address information, as long as the SF can be uniquely identified in the service chain domain, the embodiment of the present invention Not limited.

As shown in FIG. 3, the path information of the SF is included in the packet header of the Echo Request. The sending node sends the Echo Request message to the receiving node according to the path information. Specifically, the receiving node is a destination service node SN corresponding to the SF. The path information includes an SID of the SF. Path information is encapsulated in a packet header of the Echo Request message, and the path information is expressed in the form of an SR header. The path information may be expressed in different forms, for example, may include shortest path information or explicit path information, where: the shortest path information includes a SID of a destination SN and an SID of the SF. The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF. Take the example shown in Figure 1, suppose the Echo sent by the sending node. The request message carries the SF ID of the SF C, and the path information included in the packet header of the Echo Request message is represented by the shortest path information: {SID(SN2), SID(SF C)}. It is assumed that the Echo Request message sent by the sending node carries the SF ID of the SF C, and the path information included in the header of the Echo Request message is represented by the display path information: {SID(SN1), SID(SN2), SID( SF C)}.

The SID of the destination SN and the SN is an MPLS label, and the SID of the SF is a local MPLS label allocated by the destination SN to the SF; or the SID of the destination SN is the SR An IPv6 global address in the network, and the SID of the SF is an LLA assigned to the SF by the destination SN.

In a possible implementation, the Echo Request message carries a detection identifier for detecting whether the SF is available, and the detection identifier is used to indicate that the destination SN detects whether the SF is in an available state.

S402. The sending node sends the Echo Request message to the receiving node according to the path information, where the receiving node is a destination service node SN corresponding to the SF.

The sending node sends the Echo Request message to the receiving node according to the path information in the Echo Request message. The receiving node is a destination service node SN corresponding to the SF. In a specific implementation, the Echo Request message is forwarded by the shortest path or the explicit path to the destination service function SF. The shortest path refers to the SID forwarding by using the SN that reaches the destination SF. The explicit path forwarding refers to the SN passing through some SNs before reaching the destination SN. That is, the shortest path information includes the SID of the destination SN and the SID of the SF. The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF.

S403. The sending node receives an Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message.

After receiving the Echo Request message, the receiving node performs corresponding processing and echoes the Echo Reply message to the sending node. The processing performed by the receiving node is as shown in the embodiment shown in FIG. 2, and can be implemented by referring to the embodiment shown in FIG. 2, and details are not described herein again.

S404. The sending node determines, according to the Echo Reply message, whether a path to the SF is connected.

In a specific implementation, the sending node determines, according to the value of the return code carried in the response message, whether the path to the SF is connected. The value of the return code carried in the response message is used to indicate the destination The path of the service function SF is not connected, and the destination service function SF is connected to the destination service function SF, but the destination service function SF is in an unavailable state or the path to the destination service function SF is connected and the destination service function SF is in an available state.

In this embodiment of the present invention, the sending node constructs an Echo Request message, the identifier of the SF carried in the Echo Request message, and includes path information in the packet header of the Echo Request message, and sends the path information according to the path information. The Echo Request message, so that the receiving node determines, according to the SF and the SID information included in the path information, whether the path to the SF is connected, and the sending node carries the return code carried in the Echo Reply message according to the response message sent by the receiving node. The value determines whether the path to the SF is connected. The method provided by the embodiment of the invention implements the detection of the connectivity of the SFC path in the SR network, and the method is simple to implement.

Referring to FIG. 8, FIG. 8 is a schematic flowchart of a path connectivity detection method according to an embodiment of the present invention. The embodiment shown in FIG. 8 is applicable to, for example, an MPLS label as an application scenario of the SID of the SN and the SID of the SF.

S801. The sending node constructs an MPLS Echo Request message, and sends the MPLS Echo Request message to the destination SN corresponding to the destination SF.

The SF FEC field in the MPLS Echo Request message carries the SF ID, and the packet header of the MPLS Echo Request message includes path information to the destination SF.

The MPLS Echo Request message constructed by the sending node may be as shown in FIG. 9. The SR header encapsulates the path information of the SF, and the MPLS Echo Request message is presented in the form of an MPLS ping packet. The path information of the SF may be represented by an MPLS Lable Stack. That is, the packet header of the MPLS Echo Request message includes at least the SID (MPLS Lable) of the destination SN and the SID (MPLS Lable) of the destination SF. Assume that the SFP includes n SFs. For example, to check the connectivity and availability of the nth SF in the SFP, you only need to carry the SID of the SN corresponding to the first n SFs and the SF SID of the nth SF to ensure Echo. The Request is forwarded along the SFP, except that the first n-1 SFs are not executed. By analogy, the

classifier classifier checks

1, 2, ... n SFs in turn, and finally checks the connectivity of the entire SFP. Of course, the SID of the SN corresponding to the nth SF (ie, the destination SF) and the SF SID of the nth SF may be directly carried.

S802. The destination SN receives an MPLS Echo Request message sent by the sending node.

S803. Determine, by the destination SN, the SF and the destination SN according to the SF ID in the SF FEC. When the association is performed, the destination SN determines whether the SID corresponding to the SF stored in the forwarding plane of the destination SN is consistent with the SID of the SF included in the path information.

In a specific implementation, the receiving node determines, according to the SF ID in the SF FEC carried in the MPLS Echo Request message, whether the SF corresponding to the SF ID is associated with the destination SN, and the SF corresponding to the SF ID in the association check forwarding plane. Whether the MPLS Lable (SID) is consistent with the SF MPLS Lable carried in the packet header of the MPLS Echo Request. If they are consistent, it is determined that the path of the SF is reached. If the SID of the SF that is stored in the forwarding plane is inconsistent with the SF MPLS Lable carried in the packet header of the MPLS Echo Request, the path to the SF is determined. Not connected.

S804: When it is determined that the SID corresponding to the SF identified by the SF ID stored in the forwarding plane of the destination SN is consistent with the SID of the SF included in the path information, the destination SN detects whether the SF is in an available state.

S805. The destination SN sends a response message to the sending node.

When the path to the SF is not connected, the return code is carried in the MPLS Echo Reply, and the value of the return code is used to indicate that the path to the SF is disconnected.

When the path to the SF is reached but the SF is in an unavailable state, a new return code return code is defined in the MPLS Echo Reply, the value of the return code is used to indicate that the path to the SF is reached but the SF is in an unavailable state. For example, when the value of return code is 14, it indicates that the SF is in an unavailable state (Unavaililable).

When the path to the SF is connected and the SF is in the available state, the return code is carried in the MPLS Echo Reply, and the value of the return code may be equal to zero, indicating that the path to the SF is connected and the SF is in an available state.

S806. The sending node receives the MPLS Echo Reply message sent by the destination SN.

Optionally, the MPLS Echo Reply message carries the SF ID. The sending node may determine, according to the SF ID, which SF detection result is returned by the returned MPLS Echo Reply message.

Optionally, the MPLS Echo Request message may further include the FEC information of the destination SN, where the FEC information of the destination SN is used to detect whether the path to the destination service node is connected. In a specific implementation, the value of the FEC of the SN may be the IP address of the SN, and the SN determines whether the MPLS label of the SN corresponding to the IP address is saved; if yes, compares whether the MPLS label stored in the MPLS label corresponding to the IP address is MPLS label corresponding to the SN FEC contained in the MPLS Echo Request message The same, if the same, it is determined that the path to the SN is connected. If the MPLS label corresponding to the IP address does not exist at the same time or not, the SN or the path information representation error may be reached, that is, the path to the SN indicated in the path information is not connected.

Referring to FIG. 10, FIG. 10 is a schematic flowchart of a path connectivity detection method according to an embodiment of the present invention. The embodiment shown in FIG. 10 is applicable to, for example, an application scenario of an SID of an IPv6 address identifier SN and an SID of an SF.

S1001: The sending node constructs an ICMPv6Echo Request message, and sends the ICMPv6Echo Request message to the destination SN corresponding to the destination SF.

The SF ID field in the ICMPv6 Echo Request message carries the SF ID, and the packet header of the ICMPv6 Echo Request message includes path information to the destination SF.

The ICMPv6Echo Request message constructed by the sending node may be as shown in FIG. 11. The SR header encapsulates the path information of the SF, and the ICMPv6Echo Request message is presented in the form of an ICMPv6Ping packet. The path information of the SF may be represented by an IPv6 address list. That is, the header of the ICMPv6 Echo Request message includes at least the SID of the destination SN and the SID of the destination SF. The SID of each SN is an IPv6 global address, and the SID of the SF is an LLA allocated to the SF by the destination SN. Similar to the embodiment shown in FIG. 8, for example, to check the connectivity and availability of the nth SF in the SFP, it is only necessary to carry the SID of the SN corresponding to the first n SFs and the SF SID of the nth SF to ensure Echo. The Request is forwarded along the SFP, except that the first n-1 SFs are not executed. By analogy, the

classifier classifier checks

1, 2, ... n SFs in turn, and finally checks the connectivity of the entire SFP (if the SFP contains n SFs). Of course, the SID of the SN corresponding to the nth SF (ie, the destination SF) and the SF SID of the nth SF may be directly carried.

S1002: The destination SN receives an ICMPv6Echo Request message sent by the sending node.

S1003: When the destination SN determines that the SF corresponding to the SF ID is associated with the destination SN according to the SF ID, it is determined whether the SID corresponding to the SF stored in the forwarding plane of the destination SN is included in the path information. The SID of the SF is consistent.

In a specific implementation, the receiving node determines, according to the SF ID carried in the ICMPv6Echo Request message, that the SF corresponding to the SF ID is associated with the destination SN, and checks whether the SID corresponding to the SF and the ICMPv6Echo Request packet are stored in the forwarding plane. The SF SIDs carried in the header are the same, that is, whether there is an LLA that is consistent with the LLA carried in the packet header. If there is a consistent SID, then determine The path to the SF is connected. If the SID corresponding to the SF stored in the forwarding plane does not match the SID carried in the header of the ICMPv6Echo Request, the path to the SF is determined to be disconnected.

S1004: When the destination SN determines that the SID corresponding to the SF stored in the forwarding plane of the destination SN is consistent with the SID of the SF included in the path information, the destination SN detects whether the SF is in an available state.

S1005: The destination SN sends a response message to the sending node.

When the path to the SF is not connected, the return code is carried in the Destination Unreachable Message, and the value of the return code is used to indicate that the path to the SF is disconnected.

When the path to the SF is reached but the SF is in an unavailable state, a new return code return code is defined in the Destination Unreachable Message, the value of the return code is used to indicate that the path to the SF is reached but the SF is in an unavailable state. For example, when the value of the return code is 8, it indicates that the SF is in an unavailable state (Unavaililable).

When the path to the SF is reached and the SF is in the available state, the ICMPv6Echo Reply carries a return code return code indicating that the path to the SF is connected and the SF is in an available state.

S1006: The sending node receives the response message sent by the destination SN.

Optionally, the response message carries the SF ID. The sending node may determine, according to the SF ID, which of the SF detection results the returned response message corresponds to.

Referring to FIG. 12, FIG. 12 is a schematic diagram of a path connectivity detecting apparatus 1200 according to an embodiment of the present invention. The apparatus 1200 may be in the path connectivity detecting method shown in FIG. 2 or FIG. 4 or FIG. 8 or FIG. Receive node. The device 1200 is applicable to an SR network, and the device 1200 includes:

The receiving unit 1201 is configured to receive an Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the SF, where the packet header of the Echo Request message includes path information that reaches the SF, where the path information includes Describe the SID of the SF.

The determining unit 1202 is configured to determine, when the SF is associated with the device 1200 according to the identifier of the SF, whether the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information.

The sending unit 1203 is configured to determine, when the determining unit determines that the SID corresponding to the SF stored by the device 1200 is consistent with the SID of the SF included in the path information, determining that the SF is reached. The path is connected, and the first Echo Reply message is sent to the sending node, where the value of the return code carried in the first Echo Reply message is used to indicate that the path to the SF is connected.

Optionally, the sending unit is further configured to:

When the determining unit determines that the SID corresponding to the SF stored by the device 1200 is inconsistent with the SID of the SF included in the path information, determining that the path to the SF is disconnected, and sending the second to the sending node An Echo Reply message, the value of the return code carried by the second Echo Reply message is used to indicate that the path to the SF is disconnected.

Optionally, the device further includes:

a detecting unit, configured to: when the determining unit determines that the SID corresponding to the SF stored by the device 1200 is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state;

The detecting unit is specifically configured to:

Optionally, the sending unit is further configured to:

When the detecting unit determines that the SF is in an unavailable state, the value of the return code carried by the first Echo Reply message sent to the sending node is used to indicate that the SF is in an unavailable state.

Referring to FIG. 13, FIG. 13 is an SN1300 used for path connectivity detection according to an embodiment of the present invention. The SN 1300 may be a receiving node in the path connectivity detection method shown in FIG. 2 or FIG. 4 or FIG. 8 or FIG. Referring to the schematic diagram of FIG. 13, the SN 1300 can include at least one processor 1301, at least one network interface 1302 or other communication interface, memory 1303, and at least one communication bus 1304 for enabling connection communication between these devices. The processor 1301 is configured to execute an executable module, such as a computer program, stored in the memory 1303. The processor 1301 may be a CPU, and the memory 1303 may include a high speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage. The communication connection between the system gateway and at least one other network element is implemented by using at least one network interface, and an Internet, a wide area network, a local network, a metropolitan area network, or the like can be used.

The memory 1303 is configured to store a set of program instructions, and the processor 1301 is configured to invoke the program instructions stored by the memory 1303 to perform the following operations:

Receiving an Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the SF, and the packet header of the Echo Request message includes path information that reaches the SF, where the path information includes the SID of the SF;

When it is determined that the SF is associated with the SN 1300 according to the identifier of the SF, it is determined whether the SID corresponding to the SF stored by the SN 1300 is consistent with the SID of the SF included in the path information;

When it is determined that the SID corresponding to the SF stored by the SN 1300 is consistent with the SID of the SF included in the path information, determining that the path to the SF is connected, the receiving node sends a message to the sending node. An Echo Reply message, the value of the return code carried in the first Echo Reply message is used to indicate that the path to the SF is connected.

The processor 1301 is further configured to: when it is determined that the SID corresponding to the SF stored by the device is inconsistent with the SID of the SF included in the path information, determine that the path to the SF is disconnected, Sending a second Echo Reply message to the sending node, where the value of the return code carried by the second Echo Reply message is used to indicate that the path to the SF is disconnected.

The processor 1301 is further configured to: when it is determined that the SID of the SF that is stored by the SN 1300 is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state. The detecting whether the SF is in an available state comprises: sending a status detection request to the SF, receiving a status response message sent by the SF, determining, according to the status response message, whether the SF is in an available state; or And receiving a status report message that is sent by the SF, and determining, according to the status report message, whether the SF is in an available state.

The processor 1301 is further configured to: when determining that the SF is in an unavailable state, the value of the return code carried by the first Echo Reply message sent to the sending node is used to indicate the SF Is not available.

The SN 1300 for path connectivity detection provided by the embodiment of the present invention, when receiving the Echo Request message, determines that the SF is associated with the device according to the identifier of the SF, and determines that the SID corresponding to the SF stored by the device is determined. And determining, when the SID of the SF is consistent with the path information, determining that the path to the SF is connected, sending an Echo Reply message to the sending node, so that the sending node determines, according to the value of the return code carried in the Echo Reply message. The path to the SF is connected. The device provided by the embodiment of the invention implements the detection of the connectivity of the service chain SFC path in the SR network, and is beneficial to implementing the OAM function in the SR-SFC network.

Referring to FIG. 14, FIG. 14 is a path connectivity detecting apparatus 1400 according to an embodiment of the present invention. It is intended that the apparatus 1400 can be a transmitting node in the path connectivity detection method shown in FIG. 2 or FIG. 4 or FIG. 8 or FIG. The apparatus 1400 is applicable to an SR network, and the apparatus 1400 includes:

The constructing unit 1401 is configured to construct an Echo Request message, where the Echo Request message includes an identifier of the service function SF, and the packet header of the Echo Request message includes path information that reaches the SF.

The sending unit 1402 is configured to send the Echo Request message to the receiving node according to the path information, where the receiving node is a destination service node SN corresponding to the SF.

The receiving unit 1403 is configured to receive an Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message.

The determining unit 1404 is configured to determine, according to the Echo Reply message, whether a path to the SF is connected.

Optionally, the path information included in the packet header of the Echo Request message constructed by the constructing unit includes shortest path information or explicit path information, where:

Optionally, the SID of the destination SN and the SN is an MPLS label, and the SID of the SF is an MPLS label allocated by the destination SN to the SF; or the SID of the destination SN is an IPv6 global Address, the SID of the SF is LLA.

Optionally, the Echo Request message configured by the constructing unit is an MPLS Echo Request message, and the Echo Reply message received by the receiving unit is an MPLS Echo Reply message, where the constructing unit is specifically configured to:

Optionally, the Echo Request message configured by the constructing unit is an ICMPv6Echo Request message, and the Echo Reply received by the receiving unit is an ICMPv6Echo Reply message, where the constructing unit is specifically configured to:

An SF ID field is added to the ICMPv6 Echo Request message, and the identifier of the SF is carried by the SF ID field.

Optionally, the determining unit is specifically configured to:

Optionally, the Echo Request message configured by the constructing unit further carries a detection identifier for detecting whether the SF is available, and the detection identifier is used to indicate that the destination SN detects whether the SF is in an available state.

Optionally, the determining unit is further configured to:

Determining whether the SF is in an available state according to a value of a return code carried in the Echo Reply message.

Referring to FIG. 15, FIG. 15 is a schematic diagram of an SN 1500 for path connectivity detection according to an embodiment of the present invention. The SN 1500 may be a transmitting node in the path connectivity detection method shown in FIG. 2 or FIG. 4 or FIG. 8 or FIG. The SN 1500 can include at least one processor 1501, at least one network interface 1502 or other communication interface, a memory 1503, and at least one communication bus 1504 for enabling connection communication between the devices. The processor 1501 is configured to execute an executable module, such as a computer program, stored in the memory 1503. The memory 1503 may include RAM, and may also include non-volatile memory, such as at least one disk storage. The communication connection between the system gateway and at least one other network element is implemented by using at least one network interface, and an Internet, a wide area network, a local network, a metropolitan area network, or the like can be used.

The memory 1503 is configured to store a set of program instructions, and the processor 1501 is configured to invoke the program instructions stored by the memory 1503 to perform the following operations:

The processor 1501 is configured to: construct an Echo Request message, where the Echo Request message includes an identifier of the SF, where a packet header of the Echo Request message includes path information that reaches the SF; and according to the path information, The receiving node sends the Echo Request message, the receiving node is a destination service node SN corresponding to the SF, and receives an Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message. Determining whether the path to the SF is connected according to the Echo Reply message.

The processor 1501 is further configured to: the path information included in the packet header of the Echo Request message includes the shortest path information or the explicit path information, where the shortest path information includes the SID of the destination SN and the The SID of the SF; the explicit path information includes an SID of each SN passing through the destination SN and an SID of the SF.

The processor 1501 is further configured to: package the packet in the header of the constructed Echo Request message. The SID of the destination SN and the SID of the SN are MPLS labels, and the SID of the SF is an MPLS label; or the SID of the destination SN is an IPv6 global address, and the SID of the SF For LLA.

The processor 1501 is further configured to: construct an MPLS Echo Request message, add an SF FEC field in the MPLS Echo Request message, and carry the identifier of the SF in the SF FEC field.

The processor 1501 is further configured to: construct an ICMPv6Echo Request message, add an SF ID field in the ICMPv6Echo Request message, and carry the identifier of the SF by using the SF ID field.

The processor 1501 is further configured to: determine, according to a value of a return code carried in the Echo Reply message, whether a path to the SF is connected.

The processor 1501 is further configured to: in the configured Echo Request message, a detection identifier that is used to detect whether the SF is available, where the detection identifier is used to indicate that the target SN detects whether the SF is in an available state. .

The processor 1501 is further configured to: determine, according to a value of a return code carried in the Echo Reply message, whether the SF is in an available state.

The SN 1500 for the path connectivity detection provided by the embodiment of the present invention includes the Echo Request message, the identifier of the SF carried in the Echo Request message, and includes the path information in the packet header of the Echo Request message, and according to The path information is sent by the Echo Request message, so that the receiving node determines whether the path to the SF is connected according to the SF and the SID information included in the path information, and the device sends a response message Echo Reply according to the receiving node. The value of the return code carried in the message determines whether the path to the SF is connected. The device provided by the embodiment of the invention implements the detection of the connectivity of the service chain SFC path in the SR network, and is beneficial to implementing the OAM function in the SR-SFC network.

The above description of the device embodiment is relatively simple, and embodiments of the device of the present invention can be implemented by referring to the method embodiments.

The inventive arrangements may be described in the general context of computer-executable instructions executed by a computer, such as a program element. Generally, program units include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The inventive arrangements can also be practiced in distributed computing environments where remotes are connected through a communication network Process the device to perform the task. In a distributed computing environment, program units can be located in both local and remote computer storage media including storage devices.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

The embodiments of the present invention have been described in detail above, and the present invention has been described with reference to the specific embodiments. The description of the above embodiments is only for facilitating understanding of the method and device of the present invention. Meanwhile, for those skilled in the art, The present invention is not limited by the scope of the present invention.

Claims

A method for detecting path connectivity, wherein the method is applicable to a segment route SR network, and the method includes:

The receiving node receives an echo request Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the service function SF, and the packet header of the Echo Request message includes path information that reaches the SF, where the path information includes The segment identifier SID of the SF;

When the receiving node determines that the SF is associated with the receiving node according to the identifier of the SF, determining whether the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information ;

When the receiving node determines that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, determining that the path to the SF is connected, the receiving node is The sending node sends a first echo response Echo Reply message, and the value of the return code carried in the first Echo Reply message is used to indicate that the path to the SF is connected.
The method of claim 1 further comprising:

When the receiving node determines that the SID corresponding to the SF stored by the receiving node is inconsistent with the SID of the SF included in the path information, determining that the path to the SF is disconnected, the receiving node is The sending node sends a second Echo Reply message, where the second Echo Reply message carries a value of a return code, and the value of the return code is used to indicate that the path to the SF is disconnected.
The method of claim 1 further comprising:

When the receiving node determines that the SID corresponding to the SF stored by the receiving node is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state;

The detecting whether the SF is in an available state includes:

The receiving node sends a status detection request to the SF, receives a status response message sent by the SF, and determines, according to the status response message, whether the SF is in an available state; or

And receiving, by the receiving node, a status report message that is sent by the SF, and determining, according to the status report message, whether the SF is in an available state.
The method according to claim 3, wherein the value of the return code carried by the first Echo Reply message is used to indicate that the SF is in an unavailable state when it is determined that the SF is in an unavailable state.
A method for path connectivity detection, characterized in that the method is applicable to segment routing SR Network, the method includes:

The sending node constructs an echo request Echo Request message, where the Echo Request message includes an identifier of the service function SF, and the packet header of the Echo Request message includes path information that reaches the SF;

The sending node sends the Echo Request message to the receiving node according to the path information, where the receiving node is a destination service node SN corresponding to the SF;

The sending node receives an echo response Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message;

The sending node determines, according to the Echo Reply message, whether a path to the SF is connected.
The method according to claim 5, wherein the path information comprises shortest path information or explicit path information, wherein:

The shortest path information includes a segment identifier SID of the destination SN and a SID of the SF;

The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF.
The method according to claim 6, wherein the SID of the destination SN and the SN is a multi-protocol label switching MPLS label, and the SID of the SF is an MPLS label; or

The SID of the destination SN is the Internet Protocol 6th Edition IPv6 global address, and the SID of the SF is the link local address LLC.
The method according to any one of claims 5 to 7, wherein the Echo Request message is an MPLS Echo Request message, and correspondingly, the Echo Reply message is an MPLS Echo Reply message, and the Echo Request message includes The identification of the service function SF is specifically as follows:

Adding a service function forwarding equivalence class SF FEC field in the MPLS Echo Request message, and carrying the identifier of the SF in the SF FEC field.
The method according to any one of claims 5 to 7, wherein the Echo Request message is an Internet Control Information Protocol version 6 ICMPv6Echo Request message, and correspondingly, the Echo Reply is an ICMPv6Echo Reply message, The Echo Request message contains the identifier of the service function SF, which is specifically as follows:

A service function identifier SF ID field is added to the ICMPv6 Echo Request message, and the identifier of the SF is carried by the SF ID field.
A method according to any one of claims 5 to 9, wherein said hair is Determining, by the sending node, whether the path to the SF is connected according to the Echo Reply message includes:

The sending node determines, according to the value of the return code carried in the Echo Reply message, whether the path to the SF is connected.
The method according to any one of claims 5 to 10, wherein the Echo Request message further carries a detection identifier for detecting whether the SF is available, and the detection identifier is used to indicate the destination SN. It is detected whether the SF is in an available state.
A path connectivity detecting apparatus, wherein the apparatus is applicable to a segment routing SR network, and the apparatus includes:

a receiving unit, configured to receive an echo request Echo Request message sent by the sending node, where the Echo Request message includes an identifier of the service function SF, and the packet header of the Echo Request message includes path information that reaches the SF, where The path information includes a segment identifier SID of the SF;

a determining unit, configured to determine, when the SF is associated with the device according to the identifier of the SF, whether the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information;

a sending unit, configured to: when the determining unit determines that the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information, determine a path connectivity to the SF, to the The sending node sends a first echo response Echo Reply message, and the value of the return code carried in the first Echo Reply message is used to indicate that the path to the SF is connected.
The device according to claim 12, wherein the sending unit is further configured to:

When the determining unit determines that the SID corresponding to the SF stored by the device does not match the SID of the SF included in the path information, determining that the path to the SF is not connected, and sending the first to the sending node And a second Echo Reply message, where the second Echo Reply message carries a value of a return code, where the value of the return code is used to indicate that the path to the SF is disconnected.
The device of claim 12, wherein the device further comprises:

a detecting unit, configured to: when the determining unit determines that the SID corresponding to the SF stored by the device is consistent with the SID of the SF included in the path information, further detecting whether the SF is in an available state;

The detecting unit is specifically configured to:

Sending a status detection request to the SF, receiving a status response message sent by the SF, determining, according to the status response message, whether the SF is in an available state; or receiving the SF to send an active message. The status report message determines whether the SF is in an available state according to the status report message.
The device according to claim 14, wherein the sending unit is further configured to:

And when the detecting unit determines that the SF is in an unavailable state, the value of the return code carried by the first Echo Reply message sent to the sending node is used to indicate that the SF is in an unavailable state.
A path connectivity detecting apparatus, wherein the apparatus is applicable to a segment routing SR network, and the apparatus includes:

a constructing unit, configured to construct an echo request Echo Request message, where the Echo Request message includes an identifier of the service function SF, and the packet header of the Echo Request message includes path information that reaches the SF;

a sending unit, configured to send the Echo Request message to the receiving node according to the path information, where the receiving node is a destination service node SN corresponding to the SF;

a receiving unit, configured to receive an echo response Echo Reply message sent by the receiving node, where the Echo Reply message is a response message for the Echo Request message;

And a determining unit, configured to determine, according to the Echo Reply message, whether a path to the SF is connected.
The device according to claim 16, wherein the path information included in the header of the Echo Request message constructed by the constructing unit includes shortest path information or explicit path information, where:

The shortest path information includes a segment identifier SID of the destination SN and a SID of the SF;

The explicit path information includes an SID of each SN through which the destination SN passes and an SID of the SF.
The device according to claim 17, wherein the destination SN and the SID of each SN are multi-protocol label switching MPLS labels, and the SID of the SF is an MPLS label; or the destination SN and the The SID of each SN is the Internet Protocol 6th Edition IPv6 global address, and the SID of the SF is the link local address LLA.
The device according to any one of claims 16 to 18, wherein the Echo Request message constructed by the constructing unit is an MPLS Echo Request message, and correspondingly, the Echo Reply message received by the receiving unit For the MPLS Echo Reply message, the constructing unit is specifically configured to:

Adding a service function forwarding equivalence class SF FEC field in the MPLS Echo Request message, and carrying the identifier of the SF in the SF FEC field.
The device according to any one of claims 16 to 18, wherein the Echo Request message constructed by the constructing unit is an Internet Control Information Protocol version 6 ICMPv6Echo Request message, and correspondingly, the receiving unit receives The Echo Reply is an ICMPv6Echo Reply message, and the constructing unit is specifically configured to:

A service function identifier SF ID field is added to the ICMPv6 Echo Request message, and the identifier of the SF is carried by the SF ID field.
The device according to any one of claims 16 to 20, wherein the determining unit is specifically configured to:

Determining whether the path to the SF is connected according to the value of the return code carried in the Echo Reply message.
The device according to any one of claims 16 to 21, wherein the Echo Request message constructed by the constructing unit carries a detection identifier for detecting whether the SF is available, and the detection identifier is used for The destination SN is instructed to detect whether the SF is in an available state.