WO2022057779A1 - 一种实现业务路径检测的方法、设备和系统 - Google Patents

一种实现业务路径检测的方法、设备和系统 Download PDF

Info

Publication number
WO2022057779A1
WO2022057779A1 PCT/CN2021/118135 CN2021118135W WO2022057779A1 WO 2022057779 A1 WO2022057779 A1 WO 2022057779A1 CN 2021118135 W CN2021118135 W CN 2021118135W WO 2022057779 A1 WO2022057779 A1 WO 2022057779A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
packet
network device
service
header
Prior art date
Application number
PCT/CN2021/118135
Other languages
English (en)
French (fr)
Inventor
李祖庆
范萍伟
胡珣
杨平安
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202011375770.6A external-priority patent/CN114257494A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21868602.0A priority Critical patent/EP4210286A4/en
Priority to JP2023518238A priority patent/JP2023541706A/ja
Publication of WO2022057779A1 publication Critical patent/WO2022057779A1/zh
Priority to US18/186,631 priority patent/US20230261979A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/26—Route discovery packet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method, device and system for implementing service path detection.
  • tunnel-level fault detection can currently be implemented.
  • the user-side PE device detects that the user-side operator edge ( If the tunnel between the provider edge, PE) device and the network-side PE device fails, the user-side PE device implements tunnel-level switching to ensure the normal operation of the services originally carried through the tunnel.
  • the granularity of fault detection at the tunnel level is relatively coarse. Once the fault is caused by a service and other services carried on the tunnel can run normally, this fault detection method cannot accurately detect the fault at the service level.
  • the PE device on the user side will switch all the services carried on the tunnel, that is, the services running normally on the tunnel will also be switched by mistake, thereby wasting network resources.
  • Embodiments of the present application provide a method, device, and system for implementing service path detection.
  • the network device sends a detection packet carrying an indication, so that the network device at the receiver of the packet can accurately distinguish the detection packet from the detection packet through the indication.
  • the service message ensures that the network device of the receiver can effectively implement service-level fault detection, thus providing a guarantee for the normal operation of the service in the network.
  • an embodiment of the present application provides a method for implementing service path detection.
  • the method is applied to a first network device.
  • the method may include: the first network device is based on the sixth version of the Internet Protocol (internet protocol version 6, IPv6) generate and send a first packet to the second network device, where the first packet includes a first indication and service identification information, wherein the first indication is used to indicate that the first packet is a detection packet; the The first network device sends the first message to the second network device to instruct the second network device receiving the first message to send the first message to the second network device according to the first instruction and the identification information of the service.
  • IPv6 Internet Protocol version 6
  • the detection performed by the second network device on the path carrying the service may be detection of a path status, such as path failure detection or path quality detection. It can be seen that through this method, the sender's network device adds the first indication and the identification information of the service to the sent detection message, so that the receiver's network device can accurately determine that the received message is a detection message and perceive the corresponding service.
  • the connectivity or quality of the path to be detected carrying the service to be detected is detected, which overcomes the fact that currently only coarse-grained tunnel-level detection between network devices can be completed, resulting in the inability to meet the requirements. It realizes finer-grained and more accurate service-level detection, provides an accurate basis for service-level path switching, and thus guarantees the normal and efficient operation of services in the network.
  • the path to be detected may be at least one of a path between the first network device and the second network device for carrying the service and a path between the second network device and the access-side network device for carrying the service.
  • the specific path to be detected and the specific content of the detection can be determined according to the detection information carried in the detection packet.
  • the path to be detected includes both the path between the first network device and the second network device for carrying the service and the path between the second network device and the access-side network device for carrying the service, it can also be considered that the The path to be detected is the path range between the first network device and the access-side network device.
  • the detection content of the path to be detected may include the status of objects such as interfaces, links or devices on the path, such as the fault status, and may also include the quality status of the data transmitted on the path, such as packet loss, delay, bit error, etc. Or statistics or analysis of jitter, etc.
  • the second network device may send the detection content to the first network device so that the first network device determines the detection result, or may locally obtain the detection result according to the detection content.
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the identification information of the service may be, for example, a virtual private network segment identifier (virtual private network segment identifier, VPN SID) corresponding to the second network device.
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • Various possible implementation manners in which the first packet carries the first indication are exemplarily described below.
  • the first packet may include a first IPv6 header, then, the first indication is carried in a next header field in the first IPv6 header.
  • This implementation manner may be applicable to The best effort (BE) scenario of SRv6.
  • the first packet may also include the first IPv6 extension header, then, the first indication is carried in the next header field in the first segment routing header (segment routing header, SRH) of the first IPv6 extension header, the The implementation can be applied to SRv6 policy scenarios.
  • the value of the next header field carrying the first indication in the first packet is 137, indicating that the first packet is a detection packet.
  • the first IPv6 extension header in the first packet may further include a reserved label (alert label) and a control word (control word), and the reserved label and control word are used to indicate the payload ( payload), the detection information is used to instruct the second network device to detect the service path according to the detection information.
  • the alert label and the control word are used to indicate the detection information, which can be determined based on the value of the alert label and the control word to determine the content carried later as detection information, or can also be based on the value of the alert label and the control word.
  • BFD bidirectional forwarding detection
  • the first packet may include the first IPv6 header, then the first indication is carried in the variable (args) in the first destination address (DA) field of the first IPv6 header field, this implementation can be applied to SRv6 BE scenarios.
  • the first packet may include a first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header, and this implementation manner may be applicable to an SRv6 policy scenario.
  • the value of args of the DA field carrying the first indication in the first packet is not equal to 0 (eg, the value of args is equal to 3), indicating that the first packet is a detection packet.
  • the first packet may include a first IPv6 extension header, and the first indication may be carried in a flags (flags) field in the SRH of the first IPv6 extension header.
  • flags the value of the flags field carrying the first indication in the first packet is not equal to 0 (eg, the value is equal to 1), indicating that the first packet is a detection packet.
  • the first packet may include a first IPv6 extension header
  • the first indication may be carried in a hop by hop (HBH) option header of the first IPv6 extension header
  • HBH hop by hop
  • TLV type length Value
  • DOH destination option header
  • the HBH option header field in the first packet includes a TLV field carrying the first indication, indicating that the first packet is a detection packet; for another example, the DOH field in the first packet includes a TLV field carrying the first indication The TLV field indicates that the first packet is a detection packet.
  • the method may further include: the first network device sends a second packet to the second network device, where the second packet is a service packet used to carry the service, and the second packet is The text does not include the first instruction.
  • the second network device can determine whether the packet is a detection packet or a service packet based on the indication carried in the packet, so as to execute the corresponding operation based on the specific packet type. deal with.
  • the second packet does not include the first indication, which may mean that the second packet does not include a field for carrying the first indication.
  • the HBH option header field in the first packet includes the first an indicated TLV field
  • the HBH option header of the second packet does not include the TLV field used to carry the first indication; for another example, suppose that the DOH field in the first packet includes the TLV that bears the first indication field, then, the DOH field of the second packet does not include the TLV field for carrying the first indication.
  • the second packet does not include the first indication. It may also mean that the second packet includes a field that carries the first indication. However, the value of this field is different in the first packet and the second packet. Used to carry different indications, the value of this field in the first packet is used to carry the first indication, the first indication is used to indicate that the first packet is a detection packet, and the value of this field in the second packet is used. The value is used to carry the second indication, and the second indication is used to indicate that the second packet is a service packet. In one case, it is assumed that the second packet includes a second IPv6 header, the second indication is carried in the next header field in the second IPv6 header, and the first indication is the first indication of the next header field in the first IPv6 header.
  • the second indication may be the second value of the next header field in the second IPv6 header (the first value is not equal to the second value).
  • the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is the next in the first SRH of the first IPv6 extension header
  • the first value of the header field, then the second indication may be the second value of the next header field in the second SRH.
  • the value of the next header field carrying the first indication in the first packet is 137, indicating that the first packet is a detection packet; the value of the next header field carrying the second indication in the second packet is 143 , indicating that the second packet is a service packet.
  • the second packet includes the second IPv6 header, the second indication is carried in the args field in the second DA field of the second IPv6 header, and the first indication is in the first DA field of the first IPv6 header the third value of the args field, then the second indication may be the fourth value of the args field in the second DA field (the third value is not equal to the fourth value).
  • the second indication is the args field of the second DA field carried in the second SRH of the second IPv6 extension header
  • the first indication is the first indication of the first IPv6 extension header.
  • the third value of the args field of the first DA field in the SRH then the second indication may be the fourth value of the args field of the second DA field in the second SRH.
  • the value of the args field in the DA field carrying the first indication in the first message is 3, indicating that the first message is a detection message; the second message carries the args field in the DA field carrying the second indication
  • the value of the field is 0, indicating that the second packet is a service packet.
  • the second packet includes a second IPv6 extension header
  • the second indication is carried in the flags field in the SRH of the second IPv6 extension header
  • the first indication is the flag flags in the SRH of the first IPv6 extension header.
  • the fifth value of the field then the second indication may be the sixth value of the flags field in the SRH of the second IPv6 extension header (the fifth value is not equal to the sixth value).
  • the first indication and the identification information of the service carried in the first packet sent by the first network device to the second network device, in the first packet sending stage, the purpose is to enable the second network device to The identification information of the second network device detects the path carrying the service, but does not limit whether the second network device actually receives the first packet.
  • the second network device may not be able to receive the first packet. Therefore, the first network device may fail to receive the first packet. If the response message sent by the second network device cannot be received within the preset time period, it may be determined that the path carrying the service is faulty. In this example, due to the unpredictability of the forwarding path state between the first network device and the second network device in the first packet sending stage, in some possible situations including the failure scenarios listed in this example, The second network device cannot actually receive the first packet normally, but this does not affect the purpose of the first network device in the first packet sending stage, which is to enable the second network device to pair the The path carrying the service is detected.
  • the content that can be sensed and detected by the second network device may include: a link used by the second network device to connect the access-side network device on the path or if the interface is faulty.
  • the second network device can also determine whether the access-side network connected to it is faulty in some ways, for example, the access-side network device directly or indirectly connected to it, the chain link in the access-side network Check whether the channel or port is faulty.
  • the access side mentioned here may also be referred to as the user side in some cases.
  • the second network device may choose not to respond to the first packet when it is determined that the interface or link connecting the second network device to the access-side network device is faulty.
  • the first network device may choose not to respond to the first packet. If the device cannot receive the response message sent by the second network device within a preset time period, it may determine that the path between the first network device and the access-side network device carrying the service is faulty. In another case, the second network device may choose to generate and send a response corresponding to the first packet to the first network device. Then, when the first network device receives the response packet sent by the second network device, the response may be based on the response.
  • the link state information or interface state information carried in the message determines whether the path carrying the service is faulty, for example, it is determined that the path between the second network device and the access-side network device for carrying the service is faulty.
  • the second network device may also detect the path quality of the path used to carry the service, for example, the first network device and the second network device Quality data such as packet loss and delay on the path between them are detected.
  • the response packet sent by the second network device to the first network device carries corresponding quality feedback data, where the quality feedback data may include quality data fed back by the second network device and/or sent by the second network device
  • the device sends the quality feedback data added in the response message by multiple intermediate devices on the path of the response message to the first network device, so that the first network device determines the unidirectional or bidirectional path quality detection result.
  • the second network device may also directly determine the unidirectional path quality detection result according to the quality data obtained by detection.
  • the method may further include: the first network device uses the path for carrying the service
  • the switching includes a path from the first network device to the third network device, and the third network device carries the service after the switching.
  • an embodiment of the present application further provides a method for implementing service path detection, and the method is applied to a second network device.
  • the method may include: the second network device receives a first packet sent by the first network device. , the first message includes the first indication and the identification information of the service, and the first indication is used to indicate that the first message is a detection message; then, the second network device can be based on the first indication and the identification of the service The information detects at least one of the path between the first network device and the second network device that carries the service and the path between the second network device and the access-side network device that carries the service.
  • the sender's network device adds the first indication and the identification information of the service to the sent detection message, so that the receiver's network device can accurately determine that the received message is a detection message and perceive the corresponding services, so as to detect the connectivity or quality of the paths carrying services based on detection packets, overcoming the problems of the current related technologies that only support tunnel-level detection between network devices, cannot meet the requirements and waste network resources due to coarse granularity , to achieve more fine-grained and more accurate business-level detection, provide an accurate basis for business-level handover, and thus ensure the normal operation of services in the network.
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the identification information of the service may be, for example, the VPN SID corresponding to the second network device.
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • Various possible implementation manners in which the first packet carries the first indication are exemplarily described below.
  • the first packet may include the first IPv6 header, then the first indication is carried in the next header field in the first IPv6 header, and this implementation manner may be applicable to the SRv6 BE scenario.
  • the first packet may also include the first IPv6 extension header, then the first indication is carried in the next header field in the first SRH of the first IPv6 extension header, and this implementation manner may be applicable to the SRv6 policy scenario.
  • the first IPv6 extension header in the first packet may also include an alert label and a control word, and the reserved label and the control word are used to indicate detection information in the payload of the first packet. for instructing the second network device to detect the service path according to the detection information.
  • the alert label and the control word are used to indicate the detection information, which can be determined based on the value of the alert label and the control word to determine the content carried later as detection information, or can also be based on the value of the alert label and the control word.
  • the first packet may include the first IPv6 header, then the first indication is carried in the args field in the first DA field of the first IPv6 header, and this implementation manner may be applicable to SRv6 BE Scenes.
  • the first message may include a first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header, and this implementation may be applicable to an SRv6 policy scenario.
  • the first packet may include a first IPv6 extension header, and the first indication may be carried in a flags field in the SRH of the first IPv6 extension header.
  • the first packet may include a first IPv6 extension header
  • the first indication may be carried in a TLV field in the HBH option header of the first IPv6 extension header, or may also be The TLV field carried in the DOH of the first IPv6 extension header.
  • the method may further include: the second network device receives a second packet sent by the first network device, where the second packet is a service packet for carrying the service, and the second packet is a service packet for carrying the service.
  • the message does not include the first indication.
  • the second network device can determine whether the packet is a detection packet or a service packet based on the indication carried in the packet, so as to execute the corresponding operation based on the specific packet type. processing, making it possible to achieve business-level detection.
  • the second packet does not include the first indication, which may mean that the second packet does not include a field for carrying the first indication, or it may also mean that the second packet includes a field for carrying the first indication, However, the value of this field in the second packet is different from the value in the first packet, and they are used to carry different indications. The value of this field in the first packet is used to carry the first indication.
  • An indication is used to indicate that the first packet is a detection packet
  • the value of the field in the second packet is used to carry a second indication
  • the second indication is used to indicate that the second packet is a service packet.
  • the second indication is carried in the next header field in the second IPv6 header, and the first indication is the first indication of the next header field in the first IPv6 header.
  • the second indication may be the second value of the next header field in the second IPv6 header (the first value is not equal to the second value).
  • the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is the next in the first SRH of the first IPv6 extension header
  • the first value of the header field, then the second indication may be the second value of the next header field in the second SRH.
  • the second indication is carried in the args field in the second DA field of the second IPv6 header, and the first indication is in the first DA field of the first IPv6 header the third value of the args field, then the second indication may be the fourth value of the args field in the second DA field (the third value is not equal to the fourth value).
  • the second indication is carried in the args field of the second DA field in the second SRH of the second IPv6 extension header, and the first indication is the first indication of the first IPv6 extension header.
  • the second indication may be the fourth value of the args field of the second DA field in the second SRH.
  • the second packet includes a second IPv6 extension header
  • the second indication is carried in the flags field in the SRH of the second IPv6 extension header
  • the first indication is the flag flags in the SRH of the first IPv6 extension header.
  • the fifth value of the field then the second indication may be the sixth value of the flags field in the SRH of the second IPv6 extension header (the fifth value is not equal to the sixth value).
  • the second network device may detect the path status of the path used to carry the service according to the reception of the first packet, and the path status may be, for example, a path failure status or a path quality status, etc.
  • the second network device may, according to the first indication and the identification information of the service, send a message to the second network device and the access-side network device. Detect the path used to carry the service between them, or detect the path in the access-side network in some way, such as the link connected to the network device in the access-side network, or the included interface, etc. test. In this example, in one case, the second network device may choose not to respond to the first packet.
  • the first network device cannot receive the response packet sent by the second network device within a preset period of time, it can be determined that The path carrying the service is faulty, for example, the first network device determines that the path between the first network device and the access-side network device for carrying the service is faulty.
  • the second network device may choose to generate and send a response corresponding to the first packet to the first network device. Then, when the first network device receives the response packet sent by the second network device, the response may be based on the response.
  • the link state information or interface state information carried in the packet determines whether the path carrying the service is faulty. For example, the first network device may determine, according to the response message, that the path between the second network device and the access-side network device for carrying the service is faulty.
  • the second network device may also detect the path quality of the path used to carry the service according to the received first packet, for example, detect the path quality between the first network device and the second network device The quality data such as packet loss and delay on the network are detected.
  • the second network device may carry corresponding quality feedback data in the response packet sent to the first network device, so that the first network device determines the bidirectional path quality detection result.
  • the second network device may also directly determine the unidirectional path quality detection result according to the quality data obtained by detection.
  • the second network device detects the path carrying the service according to the first indication and the identification information of the service, for example, it may include: the second network device determines the first report If the message is a detection message, and it is determined that detection according to the first indication is supported locally, detection is performed on the path carrying the service according to the local detection policy.
  • the local fault detection policy it may refer to sending the first packet to the corresponding detection process, and performing fault detection in the corresponding detection process.
  • the local support for detection according to the first indication may mean that the local configuration of the network device enables the detection function indicated by the first indication.
  • sending the first packet to the corresponding detection process may be, for example, sending the remaining service-related content and detection information after removing the tunnel information (such as the SRH in the first packet) in the first packet. to the corresponding detection process.
  • the first network device may be an ingress PE device bearing the service
  • the second network device may be an egress PE device bearing the service.
  • the first network device may also be other types of network devices capable of initiating the detection methods described in the first and second aspects in the network, and the second network device may be capable of responding to the received detection report.
  • Other possible types of devices that perform corresponding path detection may be used.
  • the service carried between the first network device and the second network device may be a layer 2 virtual private network (layer 2 virtual private network, L2VPN) service.
  • L2VPN may Including services carried by traditional VPN technology or Ethernet virtual private network (ethernet virtual private network, EVPN) technology. Whether it is a traditional VPN service or an EVPN service, a virtual leased line (VLL) service model or a virtual private LAN service (VPLS) service model can be used for network deployment.
  • VLL virtual leased line
  • VPLS virtual private LAN service
  • the first packet may be a BFD packet, or may also be an operation administration and maintenance (operation administration and maintenance, OAM) packet.
  • OAM operation administration and maintenance
  • Different service path detection functions can be implemented according to different types of the first packets, for example, service path failure detection or service path quality detection, wherein the service path quality detection can detect indicators such as delay, packet loss or jitter.
  • the above method can not only detect the connectivity of the path carrying the service between the first network device and the second network device, but also realize the detection of the connection between the second network device and the second network device. Detection of the connectivity of the path carrying the service between the access-side network devices, so that the first network device can know the connectivity of the path from the first network device to the access-side network device for carrying the service , not only the tunnel path connectivity between the first network device and the second network device, thereby achieving the effect of service-level connectivity detection.
  • the path status detected according to the above method may include the connectivity of the path and the quality of the path.
  • implementing the path quality detection by the OAM packet may include: the first network device sends an OAM packet to the second network device, informing the first network device of statistical information (such as the number of data packets sent) , timestamp, etc.), the second network device can determine the service to be detected according to the service identification information carried in the OAM message, and obtain the received statistical result of the corresponding received data for the to-be-detected service, and pass the statistical information to obtain the path quality detection result corresponding to the path carrying the service to be detected.
  • the second network device may also generate and send an OAM packet carrying the detection result to the first network device, so as to notify the first network device of the path quality of the service to be detected.
  • implementing the path quality detection in the OAM packet may include: the first network device sends an OAM packet to the second network device, informing the first network device of statistics of data sent, and the second network device sends an OAM packet to the second network device The device can determine the service to be detected according to the service identification information carried in the OAM packet, obtain the statistical result of the received data corresponding to the service to be detected, and carry the statistical result in the generated OAM packet and send it to the first device.
  • the network device instructs the first network device to process the statistical result in the received OAM packet and obtain the detection result of the path carrying the service to be detected, thereby determining the quality of the path bearing the service to be detected.
  • the OAM packet is used as a detection packet. On the one hand, it can detect the path quality of the path carrying the service between the first network device and the second network device, and on the other hand, it can also realize the detection of the path carrying the service. Connectivity check.
  • an embodiment of the present application further provides an apparatus for implementing service path detection, where the apparatus is applied to a first network device, and the apparatus is applied in a network supporting SRv6.
  • the apparatus may include: a generating unit and a sending unit.
  • the generating unit is configured to generate a first packet based on the sixth version of the Internet Protocol IPv6, where the first packet includes a first indication and service identification information, and the first indication is used to indicate the first packet for detection packets.
  • a sending unit configured to send the first message to a second network device, to instruct the second network device receiving the first message to At least one of the path between the network device and the second network device that bears the service and the path between the second network device and the access-side network device that bears the service is detected.
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the first packet includes the first IPv6 header, and the first indication is carried in a next header field in the first IPv6 header; or, the first packet includes all the first IPv6 extension header, and the first indication is carried in the next header field in the first segment routing extension header SRH of the first IPv6 extension header.
  • the first IPv6 extension header of the first packet further includes a reserved label and a control word, and the reserved label and the control word are used to indicate the detection information in the payload of the first packet, the The detection information is used to instruct the second network device to detect the path of the service according to the detection information.
  • the first packet includes the first IPv6 header, and the first indication is carried in the variable args field in the first destination address DA field of the first IPv6 header; or, the first A packet includes the first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header, and the first indication is carried in a flags field in the SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header
  • the first indication is carried in the Type Length Value TLV field in the hop-by-hop HBH option header of the first IPv6 extension header, or carries in the TLV field in the destination address option header DOH of the first IPv6 extension header.
  • the sending unit is further configured to send a second packet to the second network device, where the second packet is a service packet used to carry the service, and the first The second packet does not include the first indication.
  • the second message may further include a second indication, where the second indication is used to indicate that the second message is a service message, and the second indication is different from the first indication.
  • the second indication is different from the first indication, and may include: the second packet includes a second IPv6 header, and the second indication is carried in the next header field in the second IPv6 header, so The first indication is the first value of the next header field in the first IPv6 header, and the second indication is the second value of the next header field in the second IPv6 header; or, the second message
  • the file includes a second IPv6 extension header, the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is in the first SRH of the first IPv6 extension header
  • the first value of the next header field, the second indication is the second value of the next header field in the second SRH; or, the second packet includes a second IPv6 header, and the second indication carries In the args field in the second DA field of the second IPv6 header, the first indication is the third value of the args field in the first DA field of the first IPv6 header, and the second indication is the The
  • the first indication is the third value of the args field of the first DA field in the first SRH of the first IPv6 extension header
  • the second indication is the second SRH
  • the first indication is the fifth value of the flags field in the SRH of the first IPv6 extension header
  • the second indication is the sixth value of the flags field in the SRH of the second IPv6 extension header value.
  • the apparatus may further include a determination unit.
  • the determining unit is configured to, if a response message from the second network device to the first message is not received within a preset time period, determine the relationship between the first network device and the access-side network device The path used to carry the service is faulty.
  • the apparatus may further include a receiving unit and a determining unit.
  • the receiving unit is configured to receive a response message from the second network device to the first message; the determining unit is configured to determine the second network device and the access-side network according to the response message. The path status of the path between devices for carrying the service.
  • the apparatus may further include a switching unit.
  • the switching unit is configured to determine that the path used to carry the service is faulty according to the failure to receive a response message from the second network device to the first message within a preset time period, or, according to the when the path status determines that the path used to carry the service is faulty or does not meet the path quality requirements, switching the path used to carry the service to a path including the first network device to the third network device, After the handover, the third network device carries the service.
  • the device for implementing service path detection provided by the third aspect is used to perform the relevant operations mentioned in the first aspect.
  • the relevant description of the first aspect which will not be repeated here. .
  • an embodiment of the present application further provides an apparatus for implementing service path detection, where the apparatus is applied to a second network device, and the apparatus is applied in a network supporting SRv6.
  • the apparatus may include: a receiving unit and a detecting unit.
  • the receiving unit is configured to receive a first packet sent by a first network device, where the first packet includes a first indication and service identification information, and the first indication is used to indicate the first packet for detection packets.
  • a detection unit configured to detect, according to the first indication and the identification information of the service, the path between the first network device and the second network device that bears the service and the bearer between the second network device and the access-side network device At least one of the paths of the traffic is detected.
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the first packet includes a first IPv6 header, and the first indication is carried in a next header field in the first IPv6 header; or, the first packet includes a first IPv6 header An extension header, where the first indication is carried in the next header field in the first segment routing extension header SRH of the first IPv6 extension header.
  • the first IPv6 extension header of the first packet further includes a reserved label and a control word, and the reserved label and the control word are used to indicate the detection information in the payload payload of the first message, so The detection information is used to instruct the second network device to detect the path carrying the service according to the detection information.
  • the first packet includes the first IPv6 header, and the first indication is carried in the variable args field in the first destination address DA field of the first IPv6 header; or, the first A packet includes the first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header, and the first indication is carried in a flags field in the SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header
  • the first indication is carried in the Type Length Value TLV field in the hop-by-hop HBH option header of the first IPv6 extension header, or carries in the TLV field in the destination address option header DOH of the first IPv6 extension header.
  • the receiving unit is further configured to receive a second packet sent by the first network device, where the second packet is a service packet used to carry the service, and the The second packet does not include the first indication.
  • the second message may further include a second indication, where the second indication is used to indicate that the second message is a service message, and the second indication is different from the first indication.
  • the second indication is different from the first indication, and may include: the second packet includes a second IPv6 header, and the second indication is carried in the next header field in the second IPv6 header, so The first indication is the first value of the next header field in the first IPv6 header, and the second indication is the second value of the next header field in the second IPv6 header; or, the second message
  • the file includes a second IPv6 extension header, the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is in the first SRH of the first IPv6 extension header
  • the first value of the next header field, the second indication is the second value of the next header field in the second SRH; or, the second packet includes a second IPv6 header, and the second indication carries In the args field in the second DA field of the second IPv6 header, the first indication is the third value of the args field in the first DA field of the first IPv6 header, and the second indication is the The
  • the first indication is the third value of the args field of the first DA field in the first SRH of the first IPv6 extension header
  • the second indication is the second SRH
  • the first indication is the fifth value of the flags field in the SRH of the first IPv6 extension header
  • the second indication is the sixth value of the flags field in the SRH of the second IPv6 extension header value.
  • the apparatus may further include a sending unit.
  • the sending unit is configured to send a response message to the first network device, so that the first network device determines, according to the response message, that the second network device and the access-side network device are carrying the The service path is faulty.
  • the response packet sent by the second network device may include interface status information of the second network device, where the interface status information is used to instruct the first network device to determine the second network device and The path carrying the service between the access-side network devices is faulty.
  • the detection unit may be specifically configured to: determine that the first packet is a detection packet, and determine that detection according to the first indication is locally supported, then, according to the local detection policy The path carrying the service is detected.
  • the device for implementing service path detection provided in the fourth aspect is used to perform the relevant operations mentioned in the second aspect above.
  • relevant descriptions of the second aspect which will not be repeated here. .
  • the device for implementing service path detection applied to the first network device may be an ingress PE device that carries the service
  • the device for implementing service path detection applied to the second network device may be an egress PE device that bears the service.
  • the service carried between the apparatuses implementing the service path detection may be an L2VPN service
  • the L2VPN may include, for example, a service carried by a traditional VPN technology or an EVPN technology. Whether it is a traditional VPN service or an EVPN service, the VLL service model or the VPLS service model can be used for network deployment.
  • the first packet may be a BFD packet, or may also be an OAM packet.
  • the present application further provides a network device, where the network device includes: a processor configured to enable the network device to implement the method provided in the first aspect or the second aspect.
  • the network device may further include a memory, the memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the network device can be made to implement the method provided in the first aspect or the second aspect.
  • the network device may also include a communication interface for the network device to communicate with other devices, for example, the communication interface may be a transceiver, circuit, bus, module or other type of communication interface.
  • the instructions in the memory in this application may be stored in advance, or may be downloaded from the Internet and then stored when the network device is used. This application does not specifically limit the source of the instructions in the memory.
  • the present application further provides a network system, the network system includes a first network device and a second network device, wherein: the first network device is configured to execute the method provided in the first aspect above ; the second network device, configured to execute the method provided by the second aspect.
  • the present application provides a chip, including a processor and an interface circuit; the interface circuit is used to receive instructions and transmit them to the processor; the processor is used to execute the instructions provided in the first aspect or the second aspect method corresponding to the instruction.
  • the present application provides a computer-readable storage medium, the computer-readable storage medium stores program codes or instructions that, when run on a computer, cause the computer to execute the above first aspect or the second The method provided by the aspect.
  • the present application provides a computer program product, including a computer program, which implements the method provided in the first aspect or the second aspect when the computer program is executed by a processor.
  • FIG. 1 is a schematic structural diagram of a network system 10 in an embodiment of the application
  • FIG. 2 is a flowchart of a method 100 for implementing service path detection in an embodiment of the present application
  • 3a is a schematic diagram of the format of a message 1 in an embodiment of the present application.
  • FIG. 3b is a schematic diagram of the format of another message 1 in the embodiment of the present application.
  • Fig. 3c is a schematic diagram of the format of the message 2 corresponding to Fig. 3a in an embodiment of the present application;
  • FIG. 3d is a schematic diagram of the format of the message 2 corresponding to FIG. 3b in an embodiment of the present application;
  • 4a is a schematic diagram of the format of a message 1 in an embodiment of the present application.
  • FIG. 4b is a schematic diagram of the format of another message 1 in the embodiment of the present application.
  • Fig. 4c is a schematic diagram of the format of the message 2 corresponding to Fig. 4a in the embodiment of the present application;
  • FIG. 4d is a schematic diagram of the format of the message 2 corresponding to FIG. 4b in an embodiment of the present application;
  • 5a is a schematic diagram of a format of a message 1 in an embodiment of the present application.
  • Fig. 5b is a schematic diagram of the format of the message 2 corresponding to Fig. 5a in an embodiment of the present application;
  • 6a is a schematic diagram of the format of a message 1 in an embodiment of the present application.
  • FIG. 6b is a schematic diagram of the format of another message 1 in the embodiment of the present application.
  • FIG. 6c is a schematic diagram of the format of the message 2 corresponding to FIG. 6a in an embodiment of the present application;
  • FIG. 6d is a schematic diagram of the format of the message 2 corresponding to FIG. 6b in an embodiment of the present application;
  • FIG. 7 is a schematic structural diagram of an apparatus 700 for implementing service path detection in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an apparatus 800 for implementing service path detection in an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network device 900 in an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device 1000 in an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network system 1100 in an embodiment of the present application.
  • the network system 10 shown in FIG. 1 may include a PE device 11, a PE device 12, a PE device 13, a customer edge (CE) device 21, a CE device 22, a provider (provider, P) Device 31, P device 32 and P device 33, wherein PE device 11 is connected to CE device 21, PE device 11 is connected to PE device 12 through P device 31, PE device 11 is connected to PE device 13 through P device 32 and P device 33 respectively, The PE device 12 and the PE device 13 are connected to the CE device 22 .
  • PE device 11 can detect packets through the tunnel and detect Tunnel 1 is faulty, so both service 1 and service 2 carried on tunnel 1 are switched to tunnel 2, that is, the traffic of service 1 and service 2 are both sent to CE equipment 22 through PE equipment 13 after switching.
  • the granularity of fault detection at the tunnel level is too coarse. Once the fault is caused by a certain service and other services carried on the tunnel can run normally, this fault detection method cannot accurately detect the service with path failure. , the forwarding path of the faulty service cannot be switched accurately, but only the tunnel-level path switching can be performed. As a result, the user-side PE device will perform path switching for all services carried on the tunnel, that is, the The bearer paths of services running normally on the tunnel will also be switched, wasting network resources. Moreover, in other path detection scenarios, it is also necessary to perform service-level detection on the path quality to know the path quality of the path carrying the service, so as to provide better service services.
  • an embodiment of the present application provides a method for implementing service path detection, where the first network device can generate and send to the second network device a first indication and The first packet of identification information of the service, the first indication is used to indicate that the first packet is a detection packet, and the identification information of the service is used to indicate the service; in this way, the second network receiving the first packet The device can then determine that the first packet is a detection packet according to the first indication in the first packet, and determine to detect the path carrying the service according to the identification information of the service in the first packet.
  • Paths carrying services are subject to fault detection and/or quality detection.
  • the sender's network device adds the indication and service identification information to the sent detection message, so that the receiver's network device can accurately determine that the received message is a detection message and perceive it.
  • the path carrying the service is detected based on the detection packet, which overcomes the problem that currently only tunnel-level detection between network devices can be implemented, the coarse granularity cannot meet the demand and the network resources are wasted.
  • the service-level detection requirements for path quality enable finer-grained and more accurate service-level path detection, provide an accurate basis for service-level path switching, and thus ensure the normal operation of services in the network.
  • the path detection process provided in this embodiment of the present application may include, for example: S11, the PE device 11 generates a packet 41 based on IPv6, and the packet 41 includes the indication 51 and the identifier of the service 1 information, the indication 51 is used to indicate that the message 41 is a detection message, and the identification information of the service 1 can be used to identify the service 1, then the message 41 is used to instruct the receiver device to detect the path carrying the service 1; S12 , the PE device 11 sends the message 41 to the PE device 12 via the P device 31; S13, after the PE device 12 receives the message 41, it can determine that the received message is a detection message based on the indication 51, and according to the message 41 In this case, in one case, the following S14a-S15a may be performed, and in another case, the following S14b-S15b may be performed.
  • the PE device 12 determines that the path carrying the service 1 is faulty, and does not respond to the message 41; S15a, the PE device 11 does not receive a response message for the message 41 within a preset time period (eg 1 second), Then, it is determined that the path between the PE device 11 and the CE device 22 carrying the service 1 is faulty.
  • a preset time period eg 1 second
  • the PE device 12 determines the state of the path carrying the service 1, and sends a response message of the message 41 to the PE device 11, where the response message may include the determined state of the path carrying the service 1, wherein the path
  • the state may include the path quality and/or path connectivity of the path carrying service 1 between the PE device 12 and the access-side network device (such as the CE device 22 ), and the path state may also include the path between the PE device 11 and the PE device 12 Path quality and/or path connectivity of the path carrying service 1;
  • S15b PE device 11 determines the path status of the path carrying service 1 between PE device 11 and CE device 22 according to the response message.
  • the following S16 may also be performed, that is, when the PE device 11 determines that the path carrying the service 1 between the PE device 11 and the CE device 22 is faulty according to S15a, or determines that the path status indicates the PE device 11 to the CE device according to S51b
  • switch service 1 to the path including PE equipment 13. After switching, service 1 passes through The PE equipment 13 is borne, and the service 2 is still borne by the PE equipment 12 . In this way, more refined path detection and switching are realized, which makes the utilization of resources more reasonable.
  • the service-bearing path between PE device 11 and PE device 12 is reachable and PE device 12 can receive the detection packet sent by PE device 11, then PE device 12 can transfer the obtained bearer
  • the path status of the path of service 1 is carried in the response packet and sent to the PE device 11 .
  • the path status carried in the response packet may include the path quality or path connectivity related information between the PE device 12 and the access-side network device (such as the CE device 22 ) obtained by the PE device 12 .
  • the PE device 11 That is, based on the response message, it can be sensed whether there is a fault in the path range carrying the service 1 from the PE device 12 to the access-side network device or whether the path quality meets the requirements.
  • the PE device 12 may not be able to receive the packet 41. Therefore, the PE device 11 may fail to receive the packet 41 according to the If the response packet sent by the PE device 12 cannot be received within the set time period, it can be determined that the path between the PE device 11 and the CE device 22 carrying service 1 is faulty.
  • PE device 12 determines that the path between PE device 11 and PE device 12 carrying service 1 is faulty, it can also actively send a packet to PE device 11 through a backup path to notify PE device 11
  • the path carrying service 1 is faulty, or inform PE device 11 that the quality of the path carrying service 1 does not meet the requirements, or inform PE device 11 about the status of the interface, device or link on the path carrying service 1, so that PE device 11 Whether the path carrying the service is faulty or does not meet the path quality requirement is determined according to the status information received from the PE device 12 .
  • PE devices may be directly connected; PE devices may also be indirectly connected through one or more forwarding devices, wherein the forwarding devices include but are not limited to P devices.
  • the network device in the embodiments of the present application may refer to devices such as routers, switches, repeaters, and firewalls that can bear services.
  • the methods provided by the embodiments of the present application may be applied to an SRv6 network, or other required application scenarios, such as other derivative networks that support the operation of the IPv6 protocol.
  • L2VPN layer 2 virtual private network
  • L2VPN may include, for example, traditional VPN technology or ethernet virtual private network (ethernet virtual private network) services.
  • L2VPN whether it is a traditional VPN service or an EVPN service, a virtual leased line (VLL) service model or a virtual private LAN service (VPLS) service model can be used for network deployment.
  • VLL is used to support point-to-point services
  • VPLS is used to support point-to-multipoint services or multipoint-to-multipoint services.
  • the network system 10 shown in FIG. 1 is a traditional VPN network, then, regardless of whether it is a VLL service model or a VPLS service model, the connection between PE equipment 11 and PE equipment 12, And the connection between PE equipment 11 and PE equipment 13 can be called pseudo wire (pseudo wire, PW); If the network system 10 shown in FIG. 1 is an EVPN network, then, for the VLL service model, PE equipment 11 and PE The connection between the devices 12 and the connection between the PE device 11 and the PE device 13 may be referred to as virtual private wire service (virtual private wire service, VPWS) neighbors.
  • the traditional VPN and EVPN networks can carry the same types of services.
  • the EVPN network can be implemented through the border gateway protocol (BGP), while the traditional VPN network can be implemented through the label distribution protocol (label distribution protocol, LDP), BGP, etc. implementation of at least one of the protocols.
  • the detection packets mentioned in the various embodiments of this application can be used to check the connectivity of the service-bearing path or the quality of the service-bearing path (such as indicators such as delay and packet loss on the path) test.
  • the detection message may be, for example, a bidirectional forwarding detection (BFD) message or an operation administration and maintenance (operation administration and maintenance, OAM) message.
  • BFD bidirectional forwarding detection
  • OAM operation administration and maintenance
  • the detection packet is a BFD packet
  • the method provided by the embodiment of the present application may support static BFD detection, dynamic BFD detection, or seamless bidirectional forwarding detection (seamless bidirectional forwarding detection, SBFD) detection, for example.
  • SBFD seamless bidirectional forwarding detection
  • the state of the path carrying the service is detected, which may refer to the connectivity or path quality of the path.
  • the method provided by the embodiment of the present application can support, for example, connectivity fault management (connectivity fault management, CFM) detection and Y.1731 detection.
  • connectivity fault management connectivity fault management, CFM
  • Y.1731 detection The specific type of the detection packet and the supported detection type do not affect the implementation of this embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method 100 for implementing service path detection provided by an embodiment of the present application.
  • the method 100 may be applied in a network scenario including a first network device and a second network device.
  • the first network device may be a tunnel ingress PE device bearing the target service to be detected
  • the second network device may be a tunnel egress PE device bearing the target service.
  • the target service to be detected is the service carried on the PE device 11 and the PE device 12. 1.
  • the method 100 may, for example, include the following S101 to S104:
  • the PE device 11 generates a packet 41 based on IPv6, where the packet 41 includes an indication 51 and identification information of service 1, where the indication 51 is used to indicate that the packet 41 is a detection packet.
  • the PE device 11 may encapsulate the detection packet through IPv6 to obtain a packet 41, which may also be referred to as a detection packet based on IPv6 encapsulation.
  • a detection packet based on IPv6 encapsulation.
  • the packet 41 in S101 may be called a BFD packet based on IPv6 encapsulation, and the BFD packet before encapsulation corresponds to the detection information in the packet 41 after encapsulation.
  • the identification information of the service 1 may be carried in the IPv6 header 1 of the packet 41, or may be carried in the IPv6 extension header 1', for identifying the service 1.
  • the identification information of the service 1 may be the VPN SID allocated by the PE device 12 to identify the service.
  • the indication 51 may be carried in the IPv6 header 1 of the packet 41, or the indication 51 may also be carried in the IPv6 extension header 1'.
  • the following is an exemplary description of the location where the indication 51 is carried in the message 41 in various situations.
  • the packet 41 may further include an IPv6 extension header 1', and the IPv6 extension header 1' may include a reserved label (alert label) and a control word, wherein the alert label and the control word are used to indicate that the packet 41 is valid
  • the payload part carries detection information, and the detection information is used to instruct the PE device 12 to perform fault detection or quality detection on the path carrying the service 1 according to the detection information.
  • the alert label and the control word are used to indicate the detection information, which can be determined based on the value of the alert label and the control word to determine that the content carried behind is the detection information, or it can also be determined based on the value of the alert label and the control word.
  • the indication 51 can also be considered to be carried in the next header field of IPv6 header 1 and the alert label and control word in IPv6 extension header 1', the next header field of IPv6 header 1, the alert label in IPv6 extension header 1' and the The three control words in the IPv6 extension header 1' together indicate that the packet 41 is a detection packet.
  • the format diagram of the packet 41 is shown in FIG. 3a.
  • the packet 41 may include an IPv6 header 1 and an IPv6 extension header 1', wherein the IPv6 header 1 may include a source address (source address, SA) field, a destination address (destination address).
  • the value of the SA field is the address of the PE device 11, for example, it is equal to the loopback address 1::1 of the PE device 11, and the value of the DA field is the VPN of the PE device 12
  • the segment identifier (SID) for example, is equal to End.DX2 A3::1500:0 of the PE device 12, and the value of the next header field can be 137; the IPv6 extension header 1' can include the alert label and the control word, the
  • IP internet protocol
  • UDP user datagram protocol
  • the indication 51 can be carried in the next header field in the segment routing header (SRH) of the IPv6 extension header 1, for example, in the IPv6 packet 41
  • the IPv6 extension header 1' may also include an alert label, a control word, and detection information, where the alert label and the control word are used to indicate detection information in the payload of the packet 41, and the detection information is used to indicate the PE
  • the device 12 performs fault detection on the path carrying the service 1 according to the detection information.
  • the indication 51 can also be considered to be carried in the next header field, the alert label and the control word in the SRH in the IPv6 extension header 1', and the three together indicate that the message 41 is a detection message.
  • the indication 51 can be carried in the DA field of the IPv6 header 1, for example, it can be carried in the variable (args) of the DA field of the IPv6 header 1, for example, in the packet 41 of the IPv6 header 1
  • the payload of the packet 41 may include detection information.
  • a schematic diagram of the format of the packet 41 is shown in Figure 4a.
  • the packet 41 may include an IPv6 header 1 and a payload, wherein the IPv6 header 1 may include an SA field and a DA field, and the value of the SA field is the address of the PE device 11.
  • the args in the VPN SID can also be set to other values, such as other non-zero positive integers.
  • the indication 51 can be carried in the DA field in the SRH of the IPv6 extension header 1', for example, in the args of the DA field of the IPv6 extension header 1', for example, in the packet 41
  • the payload of the packet 41 may include detection information.
  • a schematic diagram of the format of the packet 41 is shown in Figure 4b.
  • the packet 41 may include an IPv6 header 1, an IPv6 extension header 1' and a payload, wherein the IPv6 header 1 may include an SA field and a DA field, and the value of the SA field is
  • the address of PE device 11, for example, is equal to the loopback address 1::1 of PE device 11, and the value of the DA field is the VPN SID of PE device 12, for example, equal to End.DX2 A3::1500:3 of PE device 12; IPv6 extension
  • the payload of the packet 41 may include detection information. A schematic diagram of the format of the message 41 is shown in FIG. 5a.
  • the message 41 may include an IPv6 header 1, an IPv6 extension header 1' and a payload, wherein the IPv6 header 1 may include the SA field and the DA field; the IPv6 extension header 1' It may include SRH, and the payload may include IP, UDP and detection information, wherein the value of a certain bit in the flags of SRH may be 1, and the detection information may be BFD information.
  • the indication 51 may be carried in the type length value (TLV) field in the hop by hop (HBH) option header of the IPv6 extension header 1'.
  • TLV type length value
  • HBH option header in 1' includes the TLV field, which is used to indicate that the message 41 is a detection message.
  • the payload of the packet 41 may include detection information.
  • the message 41 may include an IPv6 header 1, an IPv6 extension header 1' and a payload, wherein the IPv6 header 1 may include the SA field and the DA field; the IPv6 extension header 1' may include the SA field and the DA field; Including the HBH option header, the payload may include IP, UDP and detection information, wherein the HBH option header includes a TLV field, and the detection information may be BFD information.
  • the indication 51 may also be carried in the TLV field in the destination address option header (destination option header, DOH) of the IPv6 extension header 1', and the DOH in the IPv6 extension header 1' includes the TLV field, using to indicate that the message 41 is a detection message.
  • the payload of the packet 41 may include detection information.
  • the packet 41 may include an IPv6 header 1, an IPv6 extension header 1' and a payload, wherein the IPv6 header 1 may include the SA field and the DA field; the IPv6 extension header 1' may include the SA field and the DA field; Including DOH, the payload may include IP, UDP and detection information, wherein the DOH includes a TLV field, and the detection information may be BFD information.
  • the packet 41 is a BFD packet as an example for description. If the packet 41 is an OAM packet, the manner of carrying the indication 51 and the identification information of the service 1 may refer to the implementation of the above examples.
  • the detection information in the payload of the packet 41 may be OAM information.
  • the OAM information may be Including the number of data packets sent by the PE device 11 to the PE device 12, time stamps, and the like.
  • the PE device 11 sends a packet 41 to the PE device 12 .
  • the link or the equipment passing through which the PE device 11 sends the packet 41 to the PE device 12 fails, the packet 41 cannot be successfully sent to the PE device 12, then the PE device 12 cannot receive the packet 41.
  • the fault content corresponding to the failure of PE device 12 to successfully receive the packet 41 may include: link failure between PE device 11 and P device 31, link failure between P device 31 and PE device 12, P device 31 Failure or PE equipment 12 failure.
  • the PE device 12 can successfully receive the packet 41 , that is, the method 100 further includes S103 to S104 after S102 , then the detection can be implemented based on the method 100 . Refer to the following descriptions for related implementations.
  • the PE device 12 receives the packet 41 sent by the PE device 11 .
  • S102 and S103 may be executed to implement corresponding detection; or, the path carrying the service may also be periodically detected, that is, each cycle is executed.
  • S102-S103 are used to implement corresponding detection, wherein the detection period can be flexibly set according to actual requirements.
  • the PE device 12 detects at least one of the path between the PE device 11 and the PE device 12 carrying the service 1 and the path between the PE device 12 and the CE device 22 carrying the service 1 according to the indication 51 and the identification information of the service 1 .
  • the PE device 12 can detect the path carrying the service 1 according to the indication 51 in the message 41 and the identification information of the service 1.
  • the PE device 12 can detect the PE device 11 Detect the path between PE device 12 for carrying service 1, for example, to detect whether the link between PE device 12 and P device 31 is faulty, or, for example, to detect the interface on PE device 12 used to connect P device 31
  • the PE device 12 can also detect the path between the PE device 12 and the access-side network device (such as the CE device 22) for carrying the service 1, for example, detect the PE device 12 and the CE device Whether the link between the 22 is faulty, for another example, it is detected whether the interface on the PE device 12 for connecting the CE device 22 is faulty.
  • the PE device 12 If the PE device 12 detects that the path carrying the service 1 is not faulty or the path quality meets the requirements, it can reply to the PE device 11 with a response message, which is used to inform the PE device 11 that the path carrying the service 1 is normal.
  • the PE device 12 may not respond to the packet 41, or the PE device 12 may also send a notification to the PE device 11 for the failure or a response packet whose path quality does not meet the requirements.
  • the PE device 12 determines that the path carrying the service 1 is faulty or the path quality does not meet the requirements, for example, the PE device 12 perceives that the local interface used to connect the CE device 22 is faulty, and the PE device 12 is connected to the CE device 22.
  • the method may further include: the PE device 12 sends a response to the PE device 11 After receiving the response message, PE device 11 can determine the path carrying service 1 between PE device 11 and PE device 12 and the path carrying service 1 between PE device 12 and CE device 22 according to the response message The path status of at least one path in the path status, where the path status includes the connectivity and/or the path quality of the corresponding path.
  • the response message may include, but is not limited to: local state information of the PE device 12, state information of the link between the PE device 12 and the access-side network device, and the interface of the PE device 12 connecting to the access-side network device status information.
  • the response message may further include: state information of the path between the PE device 12 and the PE device 11 and state information of the interface of the PE device 12 connected to the network device on the network side.
  • the PE device 11 may determine the path quality and path connectivity of the service 1 based on the response message.
  • the PE device 11 can also more accurately determine the status of each path segment on the path carrying the service 1 according to the response message, such as the link quality or the specific fault location. For example, it can determine: Link state, link state between PE device 12 and CE device 22 , interface state used by PE device 12 to connect P device 31 , or interface state used by PE device 12 to connect CE device 22 .
  • PE equipment 11 can still be notified of the existence of the fault through a response message. For example, if the fault exists on the path between PE equipment 11 and PE equipment 12 that carries the service 1, then PE equipment 12 can choose another reachable path. The path that corresponds to the path sends the response message to the PE device 11 to inform the PE device 11 of the failure of the path used to carry the service 1.
  • the PE device 12 may not send a response packet, which may specifically include but is not limited to: not sending a response packet when the detection mechanism determines that there is a fault
  • the response message, or the response message cannot be sent due to the failure of the link between the PE device 12 and the P device 31 or the failure of the interface used by the PE device 12 to connect the P device 31 or the like.
  • a preset duration (eg, 1 second) may be set in the PE device 11, and the preset duration may be a preset maximum allowable time for the PE device 11 to wait for receiving a response packet after sending a detection packet.
  • the PE device 11 can determine whether the PE device 11 and the CE device 22 have The path carrying service 1 is faulty or the path quality does not meet the requirements.
  • the situations in which the path carrying service 1 is faulty may include but are not limited to: PE device 12 failure, P device 31 failure, CE device 22 failure, link failure between PE device 11 and P device 31, P device 31 to P device 31
  • the link between PE device 12, the link between PE device 12 and CE device 22 is faulty, the interface between PE device 11 and P device 31 is faulty, the interface between P device 31 and PE device 12 is faulty, PE
  • the interface between the device 12 and the CE device 22 is faulty, and there is a device, link or interface fault in the user-side network connected to the PE device 12 .
  • the PE device 11 sends the BFD packet to the PE device 12, and not only can perceive that the service 1 is carried between the PE device 11 and the PE device 12 Whether there is a fault on the path of the service 1, and based on the identification information of the service 1 in the BFD packet, it can also perceive whether the path between the PE device 12 and the access-side network device (such as the CE device 22) carrying the service 1 is faulty. In this way, The PE device 11 can sense the connectivity of the entire path carrying the service 1 through the BFD message, thereby achieving the effect of service-level connectivity detection.
  • the PE device 11 sends the OAM packet to the PE device 12, so as to detect the connectivity and path quality of the path carrying the service 1 .
  • the process of implementing path quality detection by an OAM packet may include, for example: PE device 11 sends an OAM packet to PE device 12, informing PE device 11 of the statistical information (such as the number of data packets sent, time stamps and other information), the PE device 12 can determine the service 1 corresponding to the VPN to be detected according to the VPN SID carried in the OAM packet, so as to determine the service 1 to be detected in the device obtained by itself and the service 1 to be detected.
  • the statistical results of the corresponding received data packets and the statistical information in the received OAM packets are processed to obtain the quality inspection results corresponding to the path carrying the service to be detected 1;
  • the OAM response message of the detection result instructs the PE device 11 to obtain the quality detection result of the path carrying the service to be detected 1 from the received OAM response message, and to determine the quality of the path carrying the service to be detected.
  • the process of implementing path quality detection by the OAM packet may also include, for example: PE device 11 sends an OAM packet to PE device 12 to notify PE device 12 of statistics of service data packets sent by PE device 12.
  • PE device 12 may The service 1 corresponding to the VPN to be detected is determined according to the VPN SID carried in the OAM packet, and the statistical result of the received data packets corresponding to the service 1 to be detected obtained by the PE device 12 is carried in the OAM packet for response It is sent to the PE device 11, so that the PE device 11 processes the received response OAM message, obtains the quality detection result of the path carrying the service 1 to be detected, and determines the quality of the path carrying the service 1 to be detected.
  • the above two situations take unidirectional detection as an example. In other possible situations, PE device 11 and PE device 12 can also perform bidirectional detection on paths carrying services. For example, PE device 11 sends an OAM packet to PE device 12.
  • the PE device 11 may determine the bidirectional path quality detection result for the data packet of the service according to the response message.
  • the OAM packet is used as a detection packet
  • the response packet received by the PE device 11 may include at least one of the following three: the connectivity detection result of the path carrying the service 1 (that is, the PE device 11 and the PE device Whether at least one of the path carrying service 1 between 12 and the path carrying service 1 between PE equipment 12 and CE equipment 22 is faulty), the path quality detection results of the path carrying service 1 (that is, PE equipment 11 and PE equipment Whether the path quality of at least one of the path carrying Service 1 between devices 12 and the path carrying Service 1 between PE device 12 and CE device 22 meets the requirements), and the statistical results of the path quality of the path carrying Service 1 (i.e.
  • the path quality parameter of at least one of the path between PE device 11 and PE device 12 that carries service 1 and the path between PE device 12 and CE device 22 that carries service 1 can be processed by PE device 11 Obtain the path quality detection result of whether the path quality meets the requirements), wherein the path quality detection may refer to performing quality detection on a unidirectional path, or it may refer to performing quality detection on a bidirectional path.
  • S104 may, for example, include: the PE device 12 determines that the packet 41 is a detection packet, and determines that the detection according to the indication 51 is supported locally, then the path carrying the service 1 is faulted according to the local fault detection policy detection.
  • the local fault detection strategy it may refer to sending the message 41 to a corresponding detection process, and to perform fault detection in the corresponding detection process. For example, assuming that the packet 41 is a BFD detection packet, then, when the PE device 12 determines that the local BFD detection is supported, it sends the service-related content and detection information in the BFD detection packet to the local BFD process, so that the corresponding BFD process can be performed. fault detection.
  • the PE device 12 determines that the local OAM detection is supported, it sends the service-related content and detection information in the OAM detection packet to the local OAM instance, so as to perform the OAM detection in the OAM instance. corresponding detection.
  • the local support for detection according to the indication 51 may mean that the local configuration of the PE device enables the corresponding detection function of the detection indicated by the indication 51.
  • the service 1 may be, for example, a traditional VPN service 1 or an EVPN service 1.
  • the detection packet includes an SRH indicating tunnel information
  • the content sent to the detection process may be the content after the detection packet has stripped the SRH.
  • the PE device 12 may determine that the packet 41 is a detection packet according to the indication 51 of the packet 41 after determining that the DA field of the packet 41 matches the local VPN SID. If it is determined that the PE device 12 locally supports detection according to the instruction 51, and the PE device 12 is a device capable of sensing service 1 (for example, the PE device 12 is an egress PE device), the service-related content in the packet 41 and the The detection information is sent to the corresponding detection process, and fault detection is performed in the corresponding detection process.
  • the PE device 12 may determine that the TLV field carrying the indication 51 exists in the HBH option header of the IPv6 extension header 1' of the packet 41.
  • the instruction 51 determines that the packet 41 is a detection packet
  • the service-related content and detection information in the packet 41 are sent to the corresponding detection During the process, fault detection is performed in the corresponding detection process.
  • the PE device 12 may determine the DOH of the IPv6 extension header 1' of the packet 41 after determining that the DA field of the packet 41 matches the local VPN SID.
  • There is a TLV field carrying the indication 51 according to the indication 51 of the message 41, it is determined that the message 41 is a detection message, it is determined that the local support for detection according to the indication 51, and the PE device 12 is a device capable of sensing service 1, then the message is used.
  • the service-related content and detection information in document 41 are sent to the corresponding detection process, and fault detection is performed in the corresponding detection process.
  • the PE device 11 may also send a service packet corresponding to the service 1 to the PE device 12.
  • the method 100 may further include: S105, the PE device 11 sends a packet 42 to the PE device 12, the The message 42 is a service message for carrying the service 1, and the message 42 does not include the indication 51.
  • the packet 2 does not include the field carrying the indication 51.
  • the packet 41 carries the indication 51 through the TLV field in the HBH option header of the IPv6 extension header 1', then the corresponding packet 42 is shown in Figure 6b.
  • the corresponding TLV field is not included in the HBH option header.
  • the message 41 carries the indication 51 through the TLV field in the DOH of the IPv6 extension header 1', then the corresponding message 42 is shown in Figure 6d, and the DOH does not include the corresponding TLV field.
  • the message 42 includes a field carrying the indication 51 , and the field carries the indication 52 in the message 42 , the indication 52 is used to indicate that the message 42 is a service message, and the indication 52 is different from the indication 51 .
  • the packet 42 includes the IPv6 header 2, the indication 52 is carried in the next header field in the IPv6 header 2, the indication 51 is the first value of the next header field in the IPv6 header 1, then the indication 52 is in the IPv6 header 2
  • the second value of the next header field, the first value and the second value are not the same.
  • the packet 42 includes the IPv6 extension header 2'
  • the indication 52 is carried in the next header field in the SRH of the IPv6 extension header 2'
  • the indication 51 is the first of the next header field in the SRH of the IPv6 extension header 1' value
  • indicates that 52 is the second value of the next header field in the SRH of the IPv6 extension header 2', and the first value and the second value are different.
  • the value of the next header field in the message 42 is 143 as an example.
  • the value of the next header field of the message 42 in Fig. 3c and Fig. 3d is used as an example. Can also be different.
  • the packet 42 includes the IPv6 header 2, the indication 52 carries the args field in the DA field of the IPv6 header 2, the indication 51 is the third value of the args of the DA field in the IPv6 header 1, then the indication 52 is The fourth value of the args of the DA field in IPv6 header 2, the third value and the fourth value are not the same.
  • the args field of the DA field in the IPv6 header 1 in the packet 41 3
  • the corresponding packet 42 is shown in FIG. 4c
  • the args field of the DA field in the IPv6 header 2 in the packet 42 is 0.
  • the packet 42 includes the IPv6 extension header 2'
  • the indication 52 is carried in the args field of the DA field in the SRH of the IPv6 extension header 2'
  • the indication 51 is the args of the DA field in the SRH of the IPv6 extension header 1'
  • the third value of the field indicates that 52 is the fourth value of the args field of the DA field in the SRH of the IPv6 extension header 2', and the third value and the fourth value are different.
  • the args field of the DA field of the SRH in the IPv6 extension header 1' in the packet 41 3
  • the corresponding packet 42 is shown in Figure 4d
  • the args field of the DA field of the SRH in the IPv6 extension header 2' of the packet 42 0.
  • the value of the DA field in the message 42 is 0 as an example. In practical applications, the value of the args field of the message 42 in FIG. 4c and FIG. 4d can also be different.
  • the packet 42 includes the IPv6 extension header 2'
  • the indication 52 is carried in the flag field in the SRH of the IPv6 extension header 2'
  • the indication 51 is the fifth value of the flag field in the SRH of the IPv6 extension header 1'
  • the indication 52 is the sixth value of the flag field in the SRH of the IPv6 extension header 2'
  • the fifth value and the sixth value are different.
  • the flag field of the SRH in the IPv6 extension header 1' in the message 41 1
  • the corresponding message 42 is shown in Figure 5b
  • the flag field of the SRH in the IPv6 extension header 2' in the message 42 0.
  • the PE device 12 on the receiving side can identify whether the received packet is a detection packet or a service packet by analyzing the received packet, so as to perform corresponding processing. For example, the PE device 12 obtains the indication 51 by parsing the received packet 41, and determines that the packet 41 is a detection packet based on the indication 51, so as to execute the above S104; for another example, the PE device 12 parses the packet 42 to determine The packet 42 that does not include the indication 51 is a service packet, so corresponding operations such as forwarding the service packet are performed according to the processing rules of the service packet.
  • the PE device 11 may also switch the path used for carrying the service 1 to a path including the PE device 11 to the PE device 13 , and the PE device 13 carries the service 1 after switching.
  • the service packets corresponding to service 1 pass through PE equipment 11, P equipment 31, and PE equipment 12 to reach CE equipment 22.
  • the service packets corresponding to service 1 pass through PE equipment 11, P equipment 32, and P equipment according to 33.
  • the PE device 13 reaches the CE device 22.
  • the service packets corresponding to the service 2 pass through the PE device 11, the P device 31, and the PE device 12 to reach the CE device 22 in sequence.
  • all services including service 1 and service 2 on the tunnel are switched after the fault is found. After the switch, service 1 and service 2 reach CE equipment through PE equipment 11, P equipment 31, and PE equipment 12. 22. The problem of wasting network resources improves the accuracy of business control.
  • the sender's network device adds indication and service identification information to the sent detection message, so that the receiver's network device can accurately distinguish whether the received message is a detection message or a service.
  • the recipient network device determines that the received packet is a detection packet, it can determine the service to be detected based on the identification information of the service in the detection packet, and then detect the path carrying the service to be detected.
  • it provides an accurate basis for the switching of the service level, thus providing a guarantee for the normal operation of the service in the network.
  • the embodiments of the present application provide an apparatus for implementing service path detection, which will be described below with reference to the accompanying drawings.
  • FIG. 7 is a schematic structural diagram of an apparatus 700 for implementing service path detection according to an embodiment of the present application.
  • the apparatus 700 is applied to a first network device, for example, can perform the function of the PE device 11 in the embodiment shown in FIG. 1 .
  • the apparatus 700 may include: a generating unit 701 and a sending unit 702 .
  • the generating unit 701 is configured to generate a first packet based on the sixth version of the Internet Protocol IPv6, where the first packet includes a first indication and service identification information, and the first indication is used to indicate the first packet
  • the message is a detection message.
  • the specific implementation of generating the first packet by the generating unit 701 may refer to S101 in the embodiment described in FIG. 2 .
  • a sending unit 702 configured to send the first packet to a second network device, so that the second network device that receives the first packet sends the first packet to the second network device according to the first indication and the identification information of the service. At least one of the path between a network device and the second network device that bears the service and the path between the second network device and the access-side network device that bears the service is detected.
  • the specific implementation of sending the first packet by the sending unit 702 may refer to S102 in the embodiment described in FIG. 2 .
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the first packet includes the first IPv6 header, and the first indication is carried in a next header field in the first IPv6 header; or, the first packet includes all the first IPv6 extension header, and the first indication is carried in the next header field in the first segment routing extension header SRH of the first IPv6 extension header.
  • the first IPv6 extension header of the first packet further includes a reserved label and a control word, and the reserved label and the control word are used to indicate the detection information in the payload payload of the first message, so The detection information is used to instruct the second network device to detect the path of the service according to the detection information.
  • the first packet includes the first IPv6 header, and the first indication is carried in the variable args field in the first destination address DA field of the first IPv6 header; or, the first A packet includes the first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header, and the first indication is carried in a flags field in the SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header
  • the first indication is carried in the Type Length Value TLV field in the hop-by-hop HBH option header of the first IPv6 extension header, or carries in the TLV field in the destination address option header DOH of the first IPv6 extension header.
  • the sending unit 702 is further configured to send a second packet to the second network device, where the second packet is a service packet used to carry the service, and the second packet is a service packet used to carry the service.
  • the second packet does not include the first indication.
  • the specific implementation of the sending unit 702 sending the second packet may refer to S105 in the embodiment described in FIG. 2 .
  • the second message may further include a second indication, where the second indication is used to indicate that the second message is a service message, and the second indication is different from the first indication.
  • the second indication is different from the first indication, and may include: the second packet includes a second IPv6 header, and the second indication is carried in the next header field in the second IPv6 header, so The first indication is the first value of the next header field in the first IPv6 header, and the second indication is the second value of the next header field in the second IPv6 header; or, the second message
  • the file includes a second IPv6 extension header, the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is in the first SRH of the first IPv6 extension header
  • the first value of the next header field, the second indication is the second value of the next header field in the second SRH; or, the second packet includes a second IPv6 header, and the second indication carries In the args field in the second DA field of the second IPv6 header, the first indication is the third value of the args field in the first DA field of the first IPv6 header, and the second indication is the The
  • the first indication is the third value of the args field of the first DA field in the first SRH of the first IPv6 extension header
  • the second indication is the second SRH
  • the first indication is the fifth value of the flags field in the SRH of the first IPv6 extension header
  • the second indication is the sixth value of the flags field in the SRH of the second IPv6 extension header value.
  • the apparatus 700 may further include a determination unit.
  • the determining unit is configured to, if a response message from the second network device to the first message is not received within a preset time period, determine the relationship between the first network device and the access-side network device The path used to carry the service is faulty.
  • the apparatus 700 may further include a receiving unit and a determining unit.
  • the receiving unit is configured to receive a response message from the second network device to the first message; the determining unit is configured to determine the first network device and the second network device according to the response message.
  • the path status includes at least one of path connectivity and path quality
  • the apparatus 700 may further include a switching unit.
  • the switching unit is configured to determine that the path for carrying the service is faulty according to not receiving a response message from the second network device to the first message within a preset time period, or, according to the When the path status determines that the path used to carry the service is faulty or does not meet the path quality requirements, switch the path used to carry the service to a path including the first network device to the third network device, and switch Afterwards, the third network device carries the service.
  • an embodiment of the present application also provides an apparatus 800 for implementing service path detection.
  • the apparatus 800 is applied to a second network device, for example, the function of the PE device 12 in the embodiment shown in FIG. 1 can be performed.
  • the apparatus 800 may include: a receiving unit 801 and a detecting unit 802 .
  • the receiving unit 801 is configured to receive a first packet sent by a first network device, where the first packet includes a first indication and service identification information, and the first indication is used to indicate the first packet
  • the message is a detection message.
  • the detection unit 802 is configured to detect, according to the first indication and the identification information of the service, the path between the first network device and the second network device that carries the service and the path between the second network device and the access-side network device At least one of the paths carrying the traffic is detected.
  • the identification information of the service may be carried in the first IPv6 header or the first IPv6 extension header of the first packet
  • the first indication may be carried in the first IPv6 header or the first IPv6 extension header of the first packet.
  • the first packet includes a first IPv6 header, and the first indication is carried in a next header field in the first IPv6 header; or, the first packet includes a first IPv6 header An extension header, where the first indication is carried in the next header field in the first segment routing extension header SRH of the first IPv6 extension header.
  • the first IPv6 extension header of the first packet further includes a reserved label and a control word, and the reserved label and the control word are used to indicate the detection information in the payload payload of the first message, so The detection information is used to instruct the second network device to detect the path carrying the service according to the detection information.
  • the first packet includes the first IPv6 header, and the first indication is carried in the variable args field in the first destination address DA field of the first IPv6 header; or, the first A packet includes the first IPv6 extension header, and the first indication is carried in the args field in the first DA field of the first SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header, and the first indication is carried in a flags field in the SRH of the first IPv6 extension header.
  • the first packet includes the first IPv6 extension header
  • the first indication is carried in the Type Length Value TLV field in the hop-by-hop HBH option header of the first IPv6 extension header, or carries in the TLV field in the destination address option header DOH of the first IPv6 extension header.
  • the receiving unit 801 is further configured to receive a second packet sent by the first network device, where the second packet is a service packet used to carry the service, so The second packet does not include the first indication.
  • the apparatus 800 is applied to the PE device 12 shown in FIG. 1 , for the specific implementation of the receiving unit 801 receiving the second packet, reference may be made to S105 in the embodiment described in FIG. 2 .
  • the second message may further include a second indication, where the second indication is used to indicate that the second message is a service message, and the second indication is different from the first indication.
  • the second indication is different from the first indication, and may include: the second packet includes a second IPv6 header, and the second indication is carried in the next header field in the second IPv6 header, so The first indication is the first value of the next header field in the first IPv6 header, and the second indication is the second value of the next header field in the second IPv6 header; or, the second message
  • the file includes a second IPv6 extension header, the second indication is carried in the next header field in the second SRH of the second IPv6 extension header, and the first indication is in the first SRH of the first IPv6 extension header
  • the first value of the next header field, the second indication is the second value of the next header field in the second SRH; or, the second packet includes a second IPv6 header, and the second indication carries In the args field in the second DA field of the second IPv6 header, the first indication is the third value of the args field in the first DA field of the first IPv6 header, and the second indication is the The
  • the first indication is the third value of the args field of the first DA field in the first SRH of the first IPv6 extension header
  • the second indication is the second SRH
  • the first indication is the fifth value of the flags field in the SRH of the first IPv6 extension header
  • the second indication is the sixth value of the flags field in the SRH of the second IPv6 extension header value.
  • the apparatus 800 may further include a sending unit.
  • the sending unit is configured to send a response message to the first network device, so as to instruct the first network device to determine, according to the response message, all bearers between the first network device and the second network device. the service path, and at least one path state in the path between the second network device and the access side network device carrying the service, where the path state includes at least one of path connectivity and path quality.
  • the response packet sent by the second network device includes interface status information of the second network device, and the interface status information is used to instruct the first network device to determine the second network device and the interface. Check whether the path carrying the service between the ingress-side network devices is faulty or whether the path quality is good or bad.
  • the detection unit 802 may be specifically configured to: determine that the first packet is a detection packet, and determine that detection according to the first indication is locally supported, then, according to a local detection policy The path carrying the service is detected.
  • the above apparatus 700 for implementing service path detection may be an ingress PE device carrying the service, and the apparatus 800 for implementing service path detection may be an egress PE device carrying the service.
  • L2VPN L2VPN services
  • L2VPN may include, for example, services borne by traditional VPN technology or EVPN technology. Whether it is a traditional VPN service or an EVPN service, the VLL service model or the VPLS service model can be used.
  • the first packet may be a BFD packet, or may also be an OAM packet.
  • FIG. 9 is a schematic structural diagram of a network device 900 according to an embodiment of the present application.
  • the network device 900 may be any PE device in the embodiment shown in FIG. 1 , or may be the implementation shown in FIG. 7 or FIG. 8 .
  • the network device 900 includes: a processor 910 , a communication interface 920 and a memory 930 .
  • the number of processors 910 in the network device 900 may be one or more, and one processor is taken as an example in FIG. 9 .
  • the processor 910, the communication interface 920, and the memory 930 may be connected through a bus system or other manners, and FIG. 9 takes the connection through the bus system 940 as an example.
  • Processor 910 may be a CPU, NP, or a combination of CPU and NP.
  • the processor 910 may further include hardware chips.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (generic array logic, GAL) or any combination thereof.
  • the processor 910 may execute the above method embodiments to generate the first packet including the first indication and the identification information of the service, and send the first packet to the second network device. Function.
  • the processor 910 may perform the above method embodiments to receive the first packet including the first indication and the identification information of the service from the first network device, according to the first indication and the identification of the service Information related functions such as detection of paths carrying services.
  • the communication interface 920 is used for receiving and sending messages.
  • the communication interface 920 may include a receiving interface and a sending interface.
  • the receiving interface may be used to receive packets, and the sending interface may be used to send packets.
  • the number of communication interfaces 920 may be one or more.
  • the communication interface 920 may be used to implement the functions of the sending unit 702 shown in FIG. 7 or the receiving unit 801 shown in FIG. 8 .
  • the memory 930 may include volatile memory (English: volatile memory), such as random-access memory (random-access memory, RAM); the memory 930 may also include non-volatile memory (English: non-volatile memory), such as fast Flash memory (English: flash memory), hard disk drive (HDD) or solid-state drive (solid-state drive, SSD); the memory 930 may also include a combination of the above-mentioned types of memory.
  • volatile memory such as random-access memory (random-access memory, RAM
  • non-volatile memory such as fast Flash memory (English: flash memory), hard disk drive (HDD) or solid-state drive (solid-state drive, SSD)
  • the memory 930 may also include a combination of the above-mentioned types of memory.
  • the memory 930 can store, for example, the identification information of the aforementioned services.
  • the memory 930 stores an operating system and programs, executable modules or data structures, or their subsets, or their extended sets, wherein the programs may include various operation instructions for implementing various operations.
  • the operating system may include various system programs for implementing various basic services and handling hardware-based tasks.
  • the processor 910 may read the program in the memory 930 to implement the method for implementing service path detection provided by the embodiments of the present application.
  • the memory 930 may store program codes such as program codes for implementing the functions of the generation unit 701 shown in FIG. 7 or the detection unit 802 shown in FIG. 8 .
  • the memory 930 may be a storage device in the network device 900 , or may be a storage device independent of the network device 900 .
  • the bus system 940 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus system 940 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10 is a schematic structural diagram of another network device 1000 provided by an embodiment of the present application.
  • the network device 1000 may be configured as any PE device in the foregoing embodiment shown in FIG. 1 , or may be the one shown in FIG. 7 or FIG. 8 .
  • the network device 1000 includes: a main control board 1010 and an interface board 1030 .
  • the main control board 1010 is also called a main processing unit (MPU) or a route processing card (route processor card).
  • the main control board 1010 controls and manages various components in the network device 1000, including route calculation, Equipment maintenance, protocol processing functions.
  • the main control board 1010 includes: a central processing unit 1011 and a memory 1012 .
  • the interface board 1030 is also called a line processing unit (LPU), a line card (line card) or a service board.
  • the interface board 1030 is used to provide various service interfaces and realize data packet forwarding.
  • the service interface includes, but is not limited to, an Ethernet interface, a POS (Packet over SONET/SDH) interface, etc.
  • the Ethernet interface is, for example, a flexible Ethernet service interface (Flexible Ethernet Clients, FlexE Clients).
  • the interface board 1030 includes: a central processing unit 1031 , a network processor 1032 , a forwarding table entry memory 1034 and a physical interface card (ph8sical interface card, PIC) 1033 .
  • the central processing unit 1031 on the interface board 1030 is used to control and manage the interface board 1030 and communicate with the central processing unit 1011 on the main control board 1010 .
  • the network processor 1032 is used to implement packet forwarding processing.
  • the network processor 832 may be in the form of a forwarding chip.
  • the processing of the uplink packet includes: processing of the incoming interface of the packet, and searching of the forwarding table; processing of the downlink packet: searching of the forwarding table, and so on.
  • the physical interface card 1033 is used to realize the interconnection function of the physical layer, the original traffic enters the interface board 1030 through this, and the processed packets are sent from the physical interface card 1033 .
  • the physical interface card 1033 includes at least one physical interface, which is also called a physical port.
  • the physical interface card 1033 may also be referred to as a daughter card, which can be installed on the interface board 1030, and is responsible for converting the optoelectronic signal into a message, and after checking the validity of the message, the message is forwarded to the network processor 1032 for processing.
  • the central processing unit 831 of the interface board 1030 can also perform the functions of the network processor 1032 , such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1032 is not required in the physical interface card 1033 .
  • the network device 1000 includes multiple interface boards, for example, the network device 1000 further includes an interface board 1040 , and the interface board 1040 includes a central processing unit 1041 , a network processor 1042 , a forwarding table entry storage 1044 and a physical interface card 1043 .
  • the network device 1000 further includes a switch fabric board 1020 .
  • the switch fabric unit 1020 may also be referred to as a switch fabric unit (switch fabric unit, SFU).
  • SFU switch fabric unit
  • the switching network board 1020 is used to complete data exchange between the interface boards.
  • the interface board 1030 and the interface board 1040 may communicate through the switch fabric board 820 .
  • the main control board 1010 and the interface board 1030 are coupled.
  • the main control board 1010 , the interface board 1030 , the interface board 1040 , and the switch fabric board 1020 are connected to the system backplane through a system bus to implement intercommunication.
  • an inter-process communication (inter-process communication, IPC) channel is established between the main control board 1010 and the interface board 1030, and the main control board 1010 and the interface board 1030 communicate through the IPC channel.
  • IPC inter-process communication
  • the network device 1000 includes a control plane and a forwarding plane
  • the control plane includes the main control board 1010 and the central processing unit 1031
  • the forwarding plane includes various components that perform forwarding, such as the forwarding entry storage 1034, the physical interface card 1033 and the network processing device 1032.
  • the control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol packets, configuring and maintaining device status, etc.
  • the control plane delivers the generated forwarding tables to the forwarding plane.
  • the network processor 1032 is based on the control plane.
  • the delivered forwarding table forwards the packets received by the physical interface card 1033 by looking up the table.
  • the forwarding table issued by the control plane may be stored in the forwarding table entry storage 1034 .
  • the control plane and forwarding plane may be completely separate and not on the same device.
  • the central processor 1011 may generate a first packet including the first indication and the identification information of the service.
  • the network processor 1032 may trigger the physical interface card 1033 to send the first packet to the second network device.
  • the central processor 1011 may receive the first packet including the first indication and the service identification information from the first network device, and carry out the identification of the bearer service according to the first indication and the service identification information. path is detected.
  • the network processor 1032 may trigger the physical interface card 1033 to send a response packet to the first network device.
  • the sending unit 702 and the like in the apparatus 700 for implementing service path detection may be equivalent to the physical interface card 1033 or the physical interface card 1043 in the network device 1000; the generating unit 701 and the like in the apparatus 700 for implementing service path detection may be equivalent to The central processing unit 1011 or the central processing unit 1031 in the network device 1000 .
  • the receiving unit 801 and the like in the apparatus 800 for implementing service path detection may be equivalent to the physical interface card 1033 or the physical interface card 1043 in the network device 1000; the detection unit 802 and the like in the apparatus 800 for implementing service path detection may be equivalent to the network device 1000
  • the operations on the interface board 1040 in this embodiment of the present application are the same as the operations on the interface board 1030, and for brevity, details are not repeated here.
  • the network device 1000 in this embodiment may correspond to any node in the foregoing method embodiments, and the main control board 1010 , the interface board 1030 , and/or the interface board 1040 in the network device 1000 may implement the foregoing methods.
  • the functions possessed by any node in the example and/or the various steps performed are not repeated here.
  • main control boards there may be one or more main control boards, and when there are more than one main control board, it may include an active main control board and a backup main control board.
  • a network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices in a distributed architecture are greater than those in a centralized architecture.
  • the form of the network device can also be that there is only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board.
  • the central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed, the data exchange and processing capacity of this form of equipment is low (for example, low-end switches or routers and other networks. equipment).
  • the specific architecture used depends on the specific networking deployment scenario.
  • the above nodes may be implemented as virtualized devices.
  • the virtualization device may be a virtual machine (English: Virtual Machine, VM) running a program for sending a message, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • a virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.
  • Virtual machines can be configured as nodes.
  • each node may be implemented based on a general physical server combined with a Network Functions Virtualization (NFV) technology.
  • NFV Network Functions Virtualization
  • Each node is a virtual host, virtual router or virtual switch.
  • the network system 1100 may include a first network device 1101 and a second network device 1102 .
  • the first network device 1101 may be the PE device 11 shown in FIG. 1 , the apparatus 700 for implementing service path detection shown in FIG. 7 , the network device 900 configured as the first network device shown in FIG. 9 , or the device shown in FIG. 10 .
  • the shown network device 1000 is configured as the first network device; the second network device 1102 may be the PE device 12 shown in FIG. 1 , the apparatus 800 for implementing service path detection shown in FIG.
  • the embodiment of the present application also provides a chip, including a processor and an interface circuit, the interface circuit is used to receive instructions and transmit them to the processor; the processor, for example, may be the device 700 for implementing service path detection shown in FIG. 7 .
  • the processor for example, may be the device 700 for implementing service path detection shown in FIG. 7 .
  • a specific implementation form can be used to execute the above method; another example can be a specific implementation form of the apparatus 800 for implementing service path detection shown in FIG. 8 , which can be used to implement the above method.
  • the processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the chip system enables the method in any of the foregoing method embodiments.
  • the number of processors in the chip system may be one or more.
  • the processor can be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips.
  • the setting method of the processor is not particularly limited.
  • the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller).
  • controller unit, MCU it can also be a programmable logic device (PLD) or other integrated chips.
  • Embodiments of the present application also provide a computer-readable storage medium, including instructions or computer programs, which, when run on a computer, cause the computer to execute the method for implementing service path detection provided by the above embodiments.
  • the embodiments of the present application also provide a computer program product including instructions or computer programs, which, when running on a computer, cause the computer to execute the method for implementing service path detection provided by the above embodiments.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of units is only a logical business division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each service unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of a software business unit.
  • the integrated unit if implemented as a software business unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .
  • the services described in the present invention may be implemented by hardware, software, firmware or any combination thereof.
  • the services may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Abstract

一种实现业务路径检测的方法、设备和系统，该方法应用于SRv6网络，包括：第一网络设备基于IPv6生成并向第二网络设备发送第一报文，第一报文包括第一指示和业务的标识信息，第一指示用于指示该第一报文为检测报文；第二网络设备在接收到该第一报文后，根据该第一指示和业务的标识信息对承载该业务的路径进行检测。发送方通过在检测报文中添加第一指示和业务的标识信息，使得接收方能够确定出所接收的是检测报文并感知到相应的运行业务，从而基于检测报文对承载该业务的路径的连通性或质量等进行检测，以实现细粒度的业务级路径检测，并为业务级的路径切换提供了判断依据。

Description

一种实现业务路径检测的方法、设备和系统
本申请要求于2020年09月21日提交中国国家知识产权局、申请号为202010992436.9、申请名称为“一种在SRv6场景下实现故障检测的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；本申请要求于2020年11月30日提交中国国家知识产权局、申请号为202011375770.6、申请名称为“一种实现业务路径检测的方法、设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种实现业务路径检测的方法、设备和系统。
背景技术
在基于第六版互联网协议的分段路由(segment routing over internet protocol version 6，SRv6)的网络中，目前能够实现隧道级的故障检测，例如，用户侧PE设备检测到该用户侧运营商边缘(provider edge，PE)设备到网络侧PE设备之间的隧道故障，则，由用户侧PE设备实现隧道级的切换以确保经过该隧道上原来承载的业务的正常运行。但是，该隧道级的故障检测粒度较粗，一旦该故障是由某个业务导致的，而该隧道上承载的其他业务能够正常运行，那么，该故障检测方式无法精确检测出业务级的故障，导致用户侧PE设备会对该隧道上承载的所有业务均进行切换，即，该隧道上正常运行的业务也会被误切换，由此浪费了网络资源。
基于此，亟待在该场景下提供一种业务级的路径检测方法，实现更细粒度、更精确的路径检测，从而保证对业务实现准确的切换。
发明内容
本申请实施例提供了一种实现业务路径检测的方法、设备和系统，网络设备通过发出携带指示的检测报文，使得该报文的接收方网络设备通过该指示能够准确的区分检测报文和业务报文，确保接收方网络设备能够有效的实现业务级的故障检测，从而为网络中业务的正常运行提供了保障。
本申请中所提供的下述方法、装置、设备和系统，能够应用于SRv6网络中。
第一方面，本申请实施例提供了一种实现业务路径检测的方法，该方法应用于第一网络设备，该方法例如可以包括：第一网络设备基于第六版互联网协议(internet protocol version 6，IPv6)生成并向第二网络设备发送第一报文，该第一报文包括第一指示和业务的标识信息，其中，第一指示用于指示该第一报文为检测报文；所述第一网络设备向第二网络设备发送所述第一报文，以指示接收所述第一报文的所述第二网络设备根据所述第一指示和所述业务的标识信息对所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个路径进行检测。其中，第二网络设备对承载所述业务的路径进行的检测可以是针对路径状态的检测，如路径故障检测或路径质量检测等。可见，通过该方法，发送方网络设备在 发送的检测报文中添加第一指示和业务的标识信息，使得接收方网络设备能够精确的确定出所接收的报文是检测报文并感知相应的业务信息，从而基于检测报文对承载待该业务的待检测路径进行连通性或质量等方面的检测，克服了目前只能完成网络设备之间较粗粒度的隧道级的检测，从而导致无法满足需求和浪费网络资源的问题，实现了更细粒度、更精确的业务级的检测，为业务级的路径切换提供了准确的依据，从而为网络中业务的正常和高效运行提供了保障。
其中，待检测路径可以是第一网络设备和第二网络设备之间用于承载业务的路径以及第二网络设备和接入侧网络设备之间用于承载该业务的路径中的至少一个。具体检测哪段路径以及检测的具体内容可以根据检测报文中携带的检测信息确定。当待检测的路径同时包括第一网络设备和第二网络设备之间用于承载业务的路径以及第二网络设备和接入侧网络设备之间用于承载该业务的路径时，也可以认为该待检测的路径为第一网络设备和接入侧网络设备之间的路径范围。针对所述待检测的路径的检测内容可以包括路径上的接口、链路或设备等对象的状态，如故障状态，也可以包括路径传输数据的质量状态，如从丢包、时延、误码或抖动等方面进行的统计或分析等。第二网络设备可以将上述检测内容发送至第一网络设备以使得第一网络设备确定检测结果，也可以在本地根据上述检测内容获取检测结果。
其中，业务的标识信息可以携带在第一报文的第一IPv6头或第一IPv6扩展头中。业务的标识信息例如可以是第二网络设备对应的虚拟专用网段标识(virtual private network segment identifier，VPN SID)。
其中，第一指示可以携带于第一报文的第一IPv6头或第一IPv6扩展头中。下面对第一报文携带第一指示的各种可能的实现方式进行示例性说明。
在一种可能的实现方式中，该第一报文可以包括第一IPv6头，那么，该第一指示携带于第一IPv6头中的下一个头(next header)字段，该实现方式可以适用于SRv6的尽力而为(best effort，BE)场景。或者，第一报文也可以包括第一IPv6扩展头，那么，该第一指示携带于第一IPv6扩展头的第一分段路由扩展头(segment routing header，SRH)中的next header字段，该实现方式可以适用于SRv6策略(policy)场景。例如，第一报文中承载第一指示的next header字段的取值为137，指示该第一报文为检测报文。
该实现方式下，第一报文中的第一IPv6扩展头还可以包括保留标签(alert label)和控制字(control word)，该保留标签和控制字用于指示该第一报文的载荷(payload)中的检测信息，该检测信息用于指示第二网络设备根据检测信息对业务的路径进行检测。其中，alert label和控制字用于指示检测信息，可以是基于alert label和控制字的取值确定后面携带的内容为检测信息，或者，也可以基于alert label和控制字的取值确定后面携带的内容为检测信息且能够确定检测信息的类型，例如，alert label＝13和控制字，可以确定后面携带的内容为检测信息且检测信息的类型为双向转发检测(bidirectional forwarding detection，BFD)信息。
在另一种可能的实现方式中，第一报文可以包括第一IPv6头，那么，第一指示携带于第一IPv6头的第一目的地址(destination address，DA)字段中的变量(args)字段，该实 现方式可以适用于SRv6 BE场景。或者，该第一报文可以包括第一IPv6扩展头，该第一指示携带于第一IPv6扩展头的第一SRH的第一DA字段中的args字段，该实现方式可以适用于SRv6 policy场景。例如，第一报文中承载第一指示的DA字段的args的取值不等于0(如args取值等于3)，指示该第一报文为检测报文。
在又一种可能的实现方式中，该第一报文可以包括第一IPv6扩展头，该第一指示可以携带于第一IPv6扩展头的SRH中的标志(flags)字段。例如，第一报文中承载第一指示的flags字段的取值不等于0(如取值等于1)，指示该第一报文为检测报文。
在再一种可能的实现方式中，该第一报文可以包括第一IPv6扩展头，该第一指示可以携带于所述第一IPv6扩展头的逐跳(hop by hop，HBH)选项头中的类型长度值(type length Value，TLV)字段，或者，也可以携带于第一IPv6扩展头的目的地址选项头(destination option header，DOH)中的TLV字段。例如，第一报文中的HBH选项头字段中包括承载第一指示的TLV字段，指示该第一报文为检测报文；又例如，第一报文中的DOH字段中包括承载第一指示的TLV字段，指示该第一报文为检测报文。
在一些可能的实现方式中，该方法还可以包括：第一网络设备向第二网络设备发送第二报文，该第二报文为用于承载所述业务的业务报文，该第二报文不包括第一指示。这样，第二网络设备接收到第一报文和第二报文后，能够基于报文中携带的指示，确定报文是检测报文还是业务报文，从而基于具体的报文类型执行相应的处理。
作为一个示例，第二报文不包括第一指示，可以是指第二报文中不包括用于承载第一指示的字段，例如，假设第一报文中的HBH选项头字段中包括承载第一指示的TLV字段，那么，第二报文的HBH选项头中不包括该用于承载第一指示的TLV字段；又例如，假设第一报文中的DOH字段中包括承载第一指示的TLV字段，那么，第二报文的DOH字段中不包括该用于承载第一指示的TLV字段。
作为另一个示例，第二报文不包括第一指示，也可以指第二报文包括承载第一指示的字段，但是，该字段在第一报文和第二报文中的取值不同，用于承载不同的指示，该字段在第一报文中的取值用于承载第一指示，第一指示用于指示第一报文为检测报文，该字段在第二报文中的取值用于承载第二指示，第二指示用于指示第二报文为业务报文。一种情况下，假设第二报文包括第二IPv6头，第二指示携带于所述第二IPv6头中的next header字段，第一指示为所述第一IPv6头中的next header字段的第一值，那么，第二指示可以为第二IPv6头中的next header字段的第二值(第一值不等于第二值)。或者，假设第二报文包括第二IPv6扩展头，第二指示携带于第二IPv6扩展头的第二SRH中的next header字段，第一指示为第一IPv6扩展头的第一SRH中的next header字段的第一值，那么，第二指示可以为第二SRH中的next header字段的第二值。例如，第一报文中承载第一指示的next header字段的取值为137，指示该第一报文为检测报文；第二报文中承载第二指示的next header字段的取值为143，指示该第二报文为业务报文。另一种情况下，假设第二报文包括第二IPv6头，第二指示携带于第二IPv6头的第二DA字段中的args字段，第一指示为第一IPv6头的第一DA字段中的args字段的第三值，那么，第二指示可以为第二DA字段中的args字段的第四值(第三值不等于第四值)。或者，假设第二报文包括第二IPv6扩展头， 第二指示携带于第二IPv6扩展头的第二SRH中的第二DA字段的args字段，第一指示为第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，那么，第二指示可以为第二SRH中的第二DA字段中的args字段的第四值。例如，第一报文中承载第一指示的DA字段中的args字段的取值为3，指示该第一报文为检测报文；第二报文中承载第二指示的DA字段中的args字段的取值为0，指示该第二报文为业务报文。又一种情况下，假设第二报文包括第二IPv6扩展头，第二指示携带于第二IPv6扩展头的SRH中的flags字段，第一指示为第一IPv6扩展头的SRH中的标志flags字段的第五值，那么，第二指示可以为所述第二IPv6扩展头的SRH中的标志flags字段的第六值(第五值不等于第六值)。
第一网络设备向第二网络设备发送的第一报文中携带的第一指示和业务的标识信息，在第一报文发送阶段的目的在于使得第二网络设备能够根据该第一指示和业务的标识信息对承载所述业务的路径进行检测，但并不对第二网络设备是否确实接收到第一报文进行限制。
作为一个示例，当第一网络设备到第二网络设备之间的链路或设备存在故障以及第二网络设备故障时，第二网络设备可能无法接收到第一报文，从而，第一网络设备在预设时长内接收不到第二网络设备发送的响应报文，可以确定承载该业务的路径故障。在该示例中，由于第一网络设备和第二网络设备之间的转发路径状态在第一报文发送阶段的不可预期性，导致在包括本示例列举的故障场景在内的一些可能情形下，第二网络设备实际无法正常接收到第一报文，但这并不影响第一网络设备在第一报文发送阶段的目的在于，使得第二网络设备能够根据第一指示和业务的标识信息对承载该业务的路径进行检测。
作为另一个示例，假设第二网络设备接收到第一报文，那么，第二网络设备能够感知并检测的内容可以包括：第二网络设备用于连接路径上的接入侧网络设备的链路或接口是否存在故障。在其他可能的情形中，第二网络设备还能够通过某些方式确定与其连接的接入侧网络是否存在故障，例如，与其直接或间接连接的接入侧网络设备、接入侧网络中的链路或端口是否存在故障。这里提及的接入侧在一些情形下也可称为用户侧。该示例下，一种情况下，第二网络设备可以在确定第二网络设备连接接入侧网络设备的接口或链路故障的情形下，选择不对第一报文进行响应，那么，第一网络设备在预设时长内接收不到第二网络设备发送的响应报文，可以确定第一网络设备和接入侧网络设备之间承载所述业务的路径故障。另一种情况下，第二网络设备可以选择生成并向第一网络设备发送第一报文对应的响应，那么，第一网络设备接收到第二网络设备发送的响应报文时，可以基于响应报文中携带的链路状态信息或接口状态信息确定承载业务的路径是否存在故障，例如，确定第二网络设备和接入侧网络设备之间用于承载所述业务的路径存在故障。
作为再一个示例，假设第二网络设备接收到第一报文，第二网络设备还可以对用于承载所述业务的路径的路径质量进行检测，例如，对第一网络设备和第二网络设备之间的路径上的丢包、时延等质量数据进行检测。在一种情形中，在第二网络设备发送至第一网络设备的响应报文中携带相应的质量反馈数据，该质量反馈数据可以包括第二网络设备反馈的质量数据和/或由第二网络设备向第一网络设备发送响应报文的路径上由多个中间设备在该响应报文中添加的质量反馈数据，以使得第一网络设备确定单向或双向路径质量检测 结果。在另一种情形中，第二网络设备也可以直接根据检测获得的质量数据确定单向路径质量检测结果。
在一些可能的实现方式中，如果第一网络设备确定承载所述业务的路径存在故障或路径质量不满足要求，则，该方法还可以包括：第一网络设备将用于承载所述业务的路径切换为包括第一网络设备到第三网络设备的路径，切换后第三网络设备承载所述业务。这样，通过业务级的故障检测，能够精确的检测到出现故障的是承载哪个业务的路径，从而对承载该业务的路径进行切换，而无需由于执行隧道级切换而将隧道上承载的所有业务的转发路径均进行切换，一定程度上节约了网络资源。
第二方面，本申请实施例还提供了一种实现业务路径检测的方法，该方法应用于第二网络设备，该方法例如可以包括：第二网络设备接收第一网络设备发送的第一报文，该第一报文中包括第一指示和业务的标识信息，该第一指示用于指示该第一报文为检测报文；那么，第二网络设备即可根据第一指示和业务的标识信息对第一网络设备和第二网络设备之间承载所述业务的路径以及第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个进行检测。可见，通过该方法，发送方网络设备在发送的检测报文中添加第一指示和业务的标识信息，使得接收方网络设备能够精确的确定出所接收的报文是检测报文并感知到对应的业务，从而基于检测报文对承载业务的路径进行连通性或质量的检测，克服了目前相关技术中由于只支持网络设备之间隧道级的检测，粒度较粗无法满足需求和浪费网络资源的问题，实现了更细粒度、更精确的业务级的检测，为业务级的切换提供了准确的依据，从而为网络中业务的正常运行提供了保障。
其中，业务的标识信息可以携带在第一报文的第一IPv6头或第一IPv6扩展头中。业务的标识信息例如可以是第二网络设备对应的VPN SID。
其中，第一指示可以携带于第一报文的第一IPv6头或第一IPv6扩展头中。下面对第一报文携带第一指示的各种可能的实现方式进行示例性说明。
在一种可能的实现方式中，该第一报文可以包括第一IPv6头，那么，该第一指示携带于第一IPv6头中的next header字段，该实现方式可以适用于SRv6 BE场景。或者，第一报文也可以包括第一IPv6扩展头，那么，该第一指示携带于第一IPv6扩展头的第一SRH中的next header字段，该实现方式可以适用于SRv6 policy场景。
该实现方式下，第一报文中的第一IPv6扩展头还可以包括alert label和控制字，该保留标签和控制字用于指示该第一报文的payload中的检测信息，该检测信息用于指示第二网络设备根据检测信息对业务的路径进行检测。其中，alert label和控制字用于指示检测信息，可以是基于alert label和控制字的取值确定后面携带的内容为检测信息，或者，也可以基于alert label和控制字的取值确定后面携带的内容为检测信息且能够确定检测信息的类型，例如，alert label＝13和控制字，可以确定后面携带的内容为检测信息且检测信息的类型为BFD信息。
在另一种可能的实现方式中，第一报文可以包括第一IPv6头，那么，第一指示携带于第一IPv6头的第一DA字段中的args字段，该实现方式可以适用于SRv6 BE场景。或者，该第一报文可以包括第一IPv6扩展头，该第一指示携带于第一IPv6扩展头的第一SRH的 第一DA字段中的args字段，该实现方式可以适用于SRv6 policy场景。
在又一种可能的实现方式中，该第一报文可以包括第一IPv6扩展头，该第一指示可以携带于第一IPv6扩展头的SRH中的flags字段。
在再一种可能的实现方式中，该第一报文可以包括第一IPv6扩展头，该第一指示可以携带于所述第一IPv6扩展头的HBH选项头中的TLV字段，或者，也可以携带于第一IPv6扩展头的DOH中的TLV字段。
在一些可能的实现方式中，该方法还可以包括：第二网络设备接收第一网络设备发送的第二报文，该第二报文为用于承载所述业务的业务报文，该第二报文不包括第一指示。这样，第二网络设备接收到第一报文和第二报文后，能够基于报文中携带的指示，确定报文是检测报文还是业务报文，从而基于具体的报文类型执行相应的处理，使得实现业务级的检测成为可能。
其中，第二报文不包括第一指示，可以指第二报文中不包括用于承载第一指示的字段，或者，也可以指第二报文中包括用于承载第一指示的字段，但是该字段在第二报文中的取值和第一报文中的取值不同，分别用于承载不同的指示，该字段在第一报文中的取值用于承载第一指示，第一指示用于指示第一报文为检测报文，该字段在第二报文中的取值用于承载第二指示，第二指示用于指示第二报文为业务报文。一种情况下，假设第二报文包括第二IPv6头，第二指示携带于所述第二IPv6头中的next header字段，第一指示为所述第一IPv6头中的next header字段的第一值，那么，第二指示可以为第二IPv6头中的next header字段的第二值(第一值不等于第二值)。或者，假设第二报文包括第二IPv6扩展头，第二指示携带于第二IPv6扩展头的第二SRH中的next header字段，第一指示为第一IPv6扩展头的第一SRH中的next header字段的第一值，那么，第二指示可以为第二SRH中的next header字段的第二值。另一种情况下，假设第二报文包括第二IPv6头，第二指示携带于第二IPv6头的第二DA字段中的args字段，第一指示为第一IPv6头的第一DA字段中的args字段的第三值，那么，第二指示可以为第二DA字段中的args字段的第四值(第三值不等于第四值)。或者，假设第二报文包括第二IPv6扩展头，第二指示携带于第二IPv6扩展头的第二SRH中的第二DA字段的args字段，第一指示为第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，那么，第二指示可以为第二SRH中的第二DA字段中的args字段的第四值。又一种情况下，假设第二报文包括第二IPv6扩展头，第二指示携带于第二IPv6扩展头的SRH中的flags字段，第一指示为第一IPv6扩展头的SRH中的标志flags字段的第五值，那么，第二指示可以为所述第二IPv6扩展头的SRH中的标志flags字段的第六值(第五值不等于第六值)。
在一种可能的实现方式中，第二网络设备可以根据接收到第一报文，对用于承载所述业务的路径的路径状态进行检测，所述路径状态例如可以是路径故障状态或路径质量状态等。作为一个示例，假设第二网络设备接收到第一报文，那么，第二网络设备可以根据所述第一指示和所述业务的标识信息，对所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径进行检测，或者通过某种方式对接入侧网络中的路径进行检测，如对接入侧网络中的网络设备所连接的链路，或者包括的接口等进行检测。在该示例下，一种情况 下，第二网络设备可以选择不对第一报文进行响应，那么，第一网络设备在预设时长内接收不到第二网络设备发送的响应报文，可以确定承载业务的路径故障，例如，第一网络设备确定第一网络设备和接入侧网络设备之间用于承载所述业务的路径存在故障。另一种情况下，第二网络设备可以选择生成并向第一网络设备发送第一报文对应的响应，那么，第一网络设备接收到第二网络设备发送的响应报文时，可以基于响应报文中携带的链路状态信息或接口状态信息确定承载业务的路径是否存在故障。例如，第一网络设备可以根据该响应报文，确定第二网络设备和接入侧网络设备之间用于承载所述业务的路径存在故障。
作为另一个示例，第二网络设备还可以根据接收到第一报文，对用于承载所述业务的路径的路径质量进行检测，例如，对第一网络设备和第二网络设备之间的路径上的丢包、时延等质量数据进行检测。在一种情形中，第二网络设备可以在发送至第一网络设备的响应报文中携带相应的质量反馈数据，以使得第一网络设备确定双向路径质量检测结果。在另一种情形中，第二网络设备也可以直接根据检测获得的质量数据确定单向路径质量检测结果。
在一些可能的实现方式中，该方法中第二网络设备根据所述第一指示和所述业务的标识信息对承载所述业务的路径进行检测，例如可以包括：第二网络设备确定第一报文为检测报文，且确定本地支持根据第一指示进行检测，则，按照本地检测策略对承载所述业务的路径进行检测。其中，按照本地故障检测策略，可以指将该第一报文发送到对应的检测进程中，在对应的检测进程进行故障检测，例如，假设第一报文为BFD检测报文，那么，第二网络设备确定本地支持该BFD检测报文时，将该BFD检测报文中业务相关内容和检测信息发送到本地BFD进程中，从而利用该BFD进程进行对应的故障检测。其中，本地支持根据第一指示进行检测，可以指网络设备本地配置使能了该第一指示所指示的检测功能。需要说明的是，将第一报文发送到对应的检测进程中，例如可以是将第一报文中隧道信息(如第一报文中的SRH)去除之后剩余的业务相关内容和检测信息发送到对应的检测进程。
在上述第一方面和第二方面提供的方法中，第一网络设备可以为承载所述业务的入口PE设备，第二网络设备可以为承载所述业务的出口PE设备。或者，第一网络设备也可以是其他能够在网络中发起上述第一方面和第二方面所描述的检测方法的其他类型的网络设备，而第二网络设备则可以是能够响应于接收的检测报文并执行相应路径检测的其他可能类型的设备。
在上述第一方面和第二方面提供的方法中，第一网络设备和第二网络设备之间承载的业务，可以是二层虚拟专用网(layer 2 virtual private network，L2VPN)业务，L2VPN例如可以包括传统VPN技术或以太虚拟专用网(ethernet virtual private network，EVPN)技术承载的业务。无论是传统VPN业务还是EVPN业务，均可以采用虚拟租用线路(virtual leased line，VLL)业务模型或虚拟专用局域网业务(virtual private LAN service，VPLS)业务模型进行网络布署。
在上述第一方面和第二方面提供的方法中，第一报文可以为BFD报文，或者，也可以为操作管理和维护(operation administration and maintenance，OAM)报文。根据第一报文 类型的不同能够实现不同的业务路径检测功能，例如，业务路径故障检测或业务路径质量检测，其中业务路径质量检测可以针对时延、丢包或抖动等指标进行检测。
对于第一报文是BFD报文的情况，根据上述方法不仅可以实现对第一网络设备和第二网络设备之间承载该业务的路径的连通性的检测，还能够实现对第二网络设备和接入侧网络设备之间承载该业务的路径的连通性的检测，从而让第一网络设备能够获知用于承载该业务的、从第一网络设备直至接入侧网络设备之间路径的连通性，而不仅是第一网络设备和第二网络设备之间的隧道路径连通性，由此达到业务级连通性检测的效果。
对于第一报文是OAM报文的情况，根据上述方法检测的路径状态，可以包括路径的连通性以及路径的质量。在一种可能的情形中，OAM报文实现路径质量检测可以包括：第一网络设备向第二网络设备发送OAM报文，告知第一网络设备已发送数据的统计信息(如发送的数据包数量、时间戳等)，第二网络设备可以根据OAM报文中携带的业务标识信息确定待检测的业务，并针对该待检测业务获取接收到的对应接收数据的统计结果，并通过对该统计信息的处理，得到承载该待检测业务的路径对应的路径质量检测结果。可选地，第二网络设备还可以生成并向第一网络设备发送携带该检测结果的OAM报文，以向第一网络设备通告该待检测业务的路径质量。或者，在另一种可能的情形中，OAM报文实现路径质量检测可以包括：第一网络设备向第二网络设备发送OAM报文，告知第一网络设备已发送数据的统计信息，第二网络设备可以根据OAM报文中携带的业务标识信息确定待检测的业务，并获取对应于该待检测业务的接收数据的统计结果，并将该统计结果携带在生成的OAM报文中发送给第一网络设备，以指示第一网络设备对所接收OAM报文中的统计结果进行处理并获得承载该待检测业务的路径的检测结果，从而确定承载该待检测业务的路径质量。此外，OAM报文作为检测报文，一方面能够实现对第一网络设备和第二网络设备之间承载该业务的路径的路径质量的检测，另一方面也能够实现对承载该业务的路径的连通性检测。
第三方面，本申请实施例还提供了一种实现业务路径检测的装置，该装置应用于第一网络设备，该装置应用于支持基于SRv6的网络中。该装置可以包括：生成单元和发送单元。其中，生成单元，用于基于第六版互联网协议IPv6生成第一报文，所述第一报文包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文。发送单元，用于向第二网络设备发送所述第一报文，以指示接收所述第一报文的所述第二网络设备根据所述第一指示和所述业务的标识信息对第一网络设备和第二网络设备之间承载所述业务的路径以及第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个进行检测。
其中，业务的标识信息可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中
其中，第一指示可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
作为一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。其中，所述第一报文的所述第一IPv6扩展头还包括保留标签和控制字，所述保留标签和控制 字用于指示所述第一报文的载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对所述业务的路径进行检测。
作为另一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
作为又一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
作为再一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
在一些可能的实现方式中，所述发送单元，还用于向所述第二网络设备发送第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。其中，所述第二报文还可以包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
其中，所述第二指示与所述第一指示不同，可以包括：所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的第二值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第二值；或者，所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
在一些可能的实现方式中，该装置还可以包括确定单元。该确定单元，用于在预设时长未接收到所述第二网络设备对所述第一报文的响应报文，则，确定所述第一网络设备和所述接入侧网络设备之间用于承载所述业务的路径存在故障。
在一些可能的实现方式中，该装置还可以包括接收单元和确定单元。其中，接收单元，用于接收所述第二网络设备对所述第一报文的响应报文；确定单元，用于根据所述响应报文，确定所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径的路径状态。
在一些可能的实现方式中，该装置还可以包括切换单元。该切换单元，用于根据在预 设时长未接收到所述第二网络设备对所述第一报文的响应报文确定所述用于承载所述业务的路径存在故障时，或，根据所述路径状态确定所述用于承载所述业务的路径存在故障或不满足路径质量要求时，将用于承载所述业务的路径切换为包括所述第一网络设备到第三网络设备的路径，切换后所述第三网络设备承载所述业务。
该第三方面提供的实现业务路径检测的装置用于执行上述第一方面提及的相关操作，其具体实现方式以及达到的效果，均可以参见上述第一方面的相关描述，在此不再赘述。
第四方面，本申请实施例还提供了一种实现业务路径检测的装置，该装置应用于第二网络设备，该装置应用于支持基于SRv6的网络中。该装置可以包括：接收单元和检测单元。其中，接收单元，用于接收第一网络设备发送的第一报文，所述第一报文中包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文。检测单元，用于根据所述第一指示和所述业务的标识信息对第一网络设备和第二网络设备之间承载所述业务的路径以及第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个进行检测。
其中，业务的标识信息可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中
其中，第一指示可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
作为一个示例，所述第一报文包括第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，所述第一报文包括第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。其中，所述第一报文的所述第一IPv6扩展头还包括保留标签、控制字，所述保留标签和控制字用于指示所述第一报文的有效载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对承载所述业务的路径进行检测。
作为另一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
作为又一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
作为再一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
在一些可能的实现方式中，所述接收单元，还用于接收所述第一网络设备发送的第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。其中，所述第二报文还可以包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
其中，所述第二指示与所述第一指示不同，可以包括：所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的 第二值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第二值；或者，所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
在一些可能的实现方式中，该装置还可以包括发送单元。该发送单元，用于向所述第一网络设备发送响应报文，以使得所述第一网络设备根据所述响应报文确定所述第二网络设备和接入侧网络设备之间承载所述业务的路径存在故障。其中，所述第二网络设备发送的所述响应报文可以包括所述第二网络设备的接口状态信息，所述接口状态信息用于指示所述第一网络设备确定所述第二网络设备和接入侧网络设备之间承载所述业务的路径存在故障。
在一些可能的实现方式中，所述检测单元，具体可以用于：确定所述第一报文为检测报文，且确定本地支持根据所述第一指示进行检测，则，按照本地检测策略对承载所述业务的路径进行检测。
该第四方面提供的实现业务路径检测的装置用于执行上述第二方面提及的相关操作，其具体实现方式以及达到的效果，均可以参见上述第二面的相关描述，在此不再赘述。
在上述第三方面和第四方面提供的装置中，应用于第一网络设备的实现业务路径检测的装置可以为承载所述业务的入口PE设备，应用于第二网络设备的实现业务路径检测的装置可以为承载所述业务的出口PE设备。
在上述第三方面和第四方面提供的装置中，实现业务路径检测的装置之间承载的业务，可以是L2VPN业务，L2VPN例如可以包括传统VPN技术或EVPN技术承载的业务。无论是传统VPN业务还是EVPN业务，均可以采用VLL业务模型或VPLS业务模型进行网络布署。
在上述第三方面和第四方面提供的装置中，第一报文可以为BFD报文，或者，也可以为OAM报文。
第五方面，本申请还提供了一种网络设备，所述网络设备包括：处理器，用于使得该网络设备实现上述第一方面或第二方面提供的所述方法。该网络设备还可以包括存储器，存储器与处理器耦合，处理器执行存储器中存储的指令时，可以使得该网络设备实现上述第一方面或第二方面提供的方法。该网络设备还可以包括通信接口，通信接口用于该网络设备与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它 类型的通信接口。本申请中存储器中的指令可以预先存储，也可以使用该网络设备时从互联网下载后存储，本申请对于存储器中指令的来源不进行具体限定。
第六方面，本申请还提供了一种网络系统，所述网络系统包括第一网络设备和第二网络设备，其中：所述第一网络设备，用于执行上述第一方面提供的所述方法；所述第二网络设备，用于执行上述第二方面提供的所述方法。
第七方面，本申请提供了一种芯片，包括处理器和接口电路；接口电路，用于接收指令并传输至处理器；处理器，用于执行如第一方面或第二方面提供的所述方法对应的指令。
第八方面，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质存储有程序代码或指令，当其在计算机上运行时，使得所述计算机执行以上第一方面或第二方面提供的所述方法。
第九方面，本申请提供了一种计算机程序产品，包括计算机程序，所述计算机程序被处理器执行时实现以上第一方面或第二方面提供的所述方法。
附图说明
图1为本申请实施例中一种网络系统10的结构示意图；
图2为本申请实施例中一种实现业务路径检测的方法100的流程图；
图3a为本申请实施例中一种报文1的格式示意图；
图3b为本申请实施例中另一种报文1的格式示意图；
图3c为本申请实施例中与图3a对应的报文2的格式示意图；
图3d为本申请实施例中与图3b对应的报文2的格式示意图；
图4a为本申请实施例中一种报文1的格式示意图；
图4b为本申请实施例中另一种报文1的格式示意图；
图4c为本申请实施例中与图4a对应的报文2的格式示意图；
图4d为本申请实施例中与图4b对应的报文2的格式示意图；
图5a为本申请实施例中一种报文1的格式示意图；
图5b为本申请实施例中与图5a对应的报文2的格式示意图；
图6a为本申请实施例中一种报文1的格式示意图；
图6b为本申请实施例中另一种报文1的格式示意图；
图6c为本申请实施例中与图6a对应的报文2的格式示意图；
图6d为本申请实施例中与图6b对应的报文2的格式示意图；
图7为本申请实施例中一种实现业务路径检测的装置700的结构示意图；
图8为本申请实施例中一种实现业务路径检测的装置800的结构示意图；
图9为本申请实施例中一种网络设备900的结构示意图；
图10为本申请实施例中一种网络设备1000的结构示意图；
图11为本申请实施例中一种网络系统1100的结构示意图。
具体实施方式
目前，在SRv6的网络中，仅能够进行隧道级的故障检测，从而，也仅能够在检测到隧道存在故障时进行隧道级的切换。例如，在图1所示的网络系统10中，可以包括PE设备11、PE设备12、PE设备13、用户侧边缘(customer edge，CE)设备21、CE设备22、运营商(provider，P)设备31、P设备32和P设备33，其中，PE设备11连接CE设备21，PE设备11通过P设备31连接PE设备12，PE设备11分别通过P设备32和P设备33连接PE设备13，PE设备12和PE设备13连接CE设备22。假设PE设备11和PE设备12之间具有隧道1，PE设备11和PE设备13之间具有隧道2，隧道1上承载有业务1和业务2，PE设备11能够通过隧道检测报文，检测到隧道1发生故障，从而，将隧道1上承载的业务1和业务2都切换到隧道2上，即，切换后业务1和业务2的流量均通过PE设备13发送到CE设备22。
但是，该隧道级的故障检测粒度太粗，一旦该故障是由某个业务导致的，而该隧道上承载的其他业务能够正常运行，那么，该故障检测方式无法精确检测出发生路径故障的业务，也无法针对发生故障的业务的转发路径进行精确的切换，而只能进行隧道级的路径切换，由此导致用户侧PE设备会对该隧道上承载的所有业务均进行路径切换，即，该隧道上正常运行的业务的承载路径也会被切换，浪费网络资源。而且，在其他路径检测的场景下，也需要对路径质量进行业务级的检测，以了解承载业务的路径的路径质量，从而提供更加优质的业务服务。
基于此，本申请实施例提供了一种实现业务路径检测的方法，第一网络设备能够基于第六版互联网协议(internet protocol version 6，IPv6)生成并向第二网络设备发送包括第一指示和业务的标识信息的第一报文，该第一指示用于指示第一报文为检测报文，业务的标识信息用于指示所述业务；这样，接收到该第一报文的第二网络设备即可根据第一报文中的第一指示确定第一报文为检测报文，并根据第一报文中所述业务的标识信息确定对承载所述业务的路径进行检测，例如，对承载业务的路径进行故障检测和/或质量检测。可见，通过本申请实施例提供的方法，发送方网络设备在发送的检测报文中添加指示和业务的标识信息，使得接收方网络设备能够精确的确定出所接收的报文是检测报文并感知到对应的业务，从而基于检测报文对承载该业务的路径进行检测，克服了目前只能实现网络设备之间隧道级的检测，粒度较粗无法满足需求和浪费网络资源的问题，也满足了对路径质量进行业务级的检测需求，实现了更细粒度、更精确的业务级的路径检测，为业务级的路径切换提供了准确的依据，从而为网络中业务的正常运行提供了保障。
仍然以图1所示的网络系统10为例，本申请实施例提供的路径检测过程例如可以包括：S11，PE设备11基于IPv6生成报文41，该报文41包括指示51和业务1的标识信息，指示51用于指示该报文41为检测报文，业务1的标识信息可以用于识别业务1，那么，该报文41用于指示接收方设备对承载业务1的路径进行检测；S12，PE设备11经过P设备31向PE设备12发送该报文41；S13，PE设备12接收到报文41后，可以基于指示51确定所接收的是检测报文，并且，根据报文41中的业务1的标识信息对承载该业务1的路径进行检测；此时，一种情况下，可以执行下述S14a～S15a，另一种情况下，可以执行下述S14b～S15b。S14a，PE设备12确定承载该业务1的路径存在故障，则，不对该报文41作 出响应；S15a，PE设备11在预设时长(如1秒)未接收到报文41的响应报文，则，确定PE设备11到CE设备22之间承载业务1的路径存在故障。S14b，PE设备12确定承载该业务1的路径状态，并向PE设备11发送报文41的响应报文，该响应报文中可以包括所确定的承载该业务1的路径状态，其中，该路径状态可以包括PE设备12和接入侧网络设备(如CE设备22)之间承载业务1的路径的路径质量和/或路径连通性，该路径状态还可以包括PE设备11和PE设备12之间承载业务1的路径的路径质量和/或路径连通性；S15b，PE设备11根据响应报文，则，确定PE设备11到CE设备22之间承载业务1的路径的路径状态。接着，还可以执行下述S16，即，PE设备11在根据S15a确定PE设备11到CE设备22之间承载业务1的路径存在故障时，或在根据S51b确定路径状态指示PE设备11到CE设备22之间承载业务1的路径存在故障或PE设备11到CE设备22之间承载业务1的路径不满足路径质量要求时，将业务1切换到包括PE设备13的路径上，切换后业务1通过PE设备13承载，业务2仍然通过PE设备12承载。这样，实现了更加精细化的路径检测和切换，使得资源的利用更加合理。
在一种情形下，如果PE设备11和PE设备12之间承载业务的路径可达，PE设备12可以接收到PE设备11发送的检测报文，则，PE设备12即可将获取到的承载业务1的路径的路径状态携带在响应报文中发送给PE设备11。其中，响应报文中携带的路径状态，可以包括PE设备12获得的PE设备12和接入侧网络设备(如CE设备22)之间的路径质量或路径连通性相关信息，这样，PE设备11即可基于该响应报文感知到从PE设备12到接入侧网络设备之间承载业务1的路径范围是否存在故障或路径质量是否满足要求。在另一种情形下，当PE设备11到PE设备12之间的链路或设备存在故障以及PE设备12故障时，PE设备12可能无法接收到报文41，从而，PE设备11根据在预设时长内接收不到PE设备12发送的响应报文，可以确定PE设备11和CE设备22之间承载业务1的路径故障。在另一种情形下，PE设备12在确定PE设备11和PE设备12之间承载业务1的路径存在故障时，也可以通过某条备用路径主动向PE设备11发送报文，告知PE设备11承载业务1的路径存在故障，或告知PE设备11承载业务1的路径质量不满足要求，或告知PE设备11承载业务1的路径上的有关接口、设备或链路的状态，以使得PE设备11根据从PE设备12接收的状态信息确定承载业务的路径是否存在故障或不满足路径质量要求。
在图1所示的网络系统10中，PE设备之间可以直接连接；PE设备之间也可以通过一个或多个转发设备间接连接，其中，转发设备包括但不限于P设备。
需要说明的是，本申请实施例中的网络设备可以指能够承载业务的路由器、交换机、转发器、防火墙等设备。
需要说明的是，本申请各实施例提供的方法，可以应用于SRv6的网络中，或者其他需要的应用场景，如支持IPv6协议运行的其他衍生网络。
需要说明的是，本申请中各实施例中提及的业务，可以是二层虚拟专用网(layer 2 virtual private network，L2VPN)业务，L2VPN例如可以包括传统VPN技术或以太虚拟专用网(ethernet virtual private network，EVPN)技术承载的业务。L2VPN中，无论是传统VPN业务还是EVPN业务，均可以采用虚拟租用线路(virtual leased line，VLL)业务模型或虚 拟专用局域网业务(virtual private LAN service，VPLS)业务模型进行网络布署。其中，VLL用于支持点到点的业务，VPLS用于支持点到多点的业务或多点到多点的业务。以图1所示的网络系统10为例，如果图1所示的网络系统10为传统VPN网络，那么，无论是VLL业务模型还是VPLS业务模型，PE设备11和PE设备12之间的连接、以及PE设备11和PE设备13之间的连接均可以称为伪线(pseudo wire，PW)；如果图1所示的网络系统10为EVPN网络，那么，对于VLL业务模型，PE设备11和PE设备12之间的连接、以及PE设备11和PE设备13之间的连接均可以称为虚拟专用线路业务(virtual private wire service，VPWS)邻居。传统VPN和EVPN网络承载的业务类型可以相同，其中，EVPN网络能够通过边界网关协议(border gateway protocol，BGP)实现，而传统VPN网络能够通过标签分发协议(label distribution protocol，LDP)、BGP等多种协议中的至少一种协议实现。
需要说明的是，本申请各实施例中提及的检测报文，可以用于对承载业务的路径的连通性或承载业务的路径的质量(如该路径上的时延、丢包等指标)进行检测。检测报文例如可以是双向转发检测(bidirectional forwarding detection，BFD)报文或者操作管理和维护(operation administration and maintenance，OAM)报文。对于检测报文为BFD报文的情况，本申请实施例提供的方法例如可以支持静态BFD检测、动态BFD检测或无缝双向转发检测(seamless bidirectional forwarding detection，SBFD)检测。检测到承载业务的路径状态，可以指该路径的连通性或路径质量。对于检测报文为OAM报文的情况，本申请实施例提供的方法例如可以支持连通性故障管理(connectivity fault management，CFM)检测、Y.1731检测。检测报文的具体类型以及支持的检测类型不影响本申请实施例的实施。
为便于理解本申请实施例提供的网络故障检测方法，下面将结合附图对该方法进行说明。
图2为本申请实施例提供的一种实现业务路径检测的方法100的流程示意图。该方法100可以应用于包括第一网络设备和第二网络设备的网络场景中。作为一种示例，第一网络设备可以为承载待检测的目标业务的隧道入口PE设备，第二网络设备可以是承载该目标业务的隧道出口PE设备。为了方便理解，以图1示出的网络系统10的结构为例，通过PE设备11和PE设备12之间的交互进行描述，待检测的目标业务为PE设备11和PE设备12上承载的业务1。具体实现时，该方法100例如可以包括下述S101～S104：
S101，PE设备11基于IPv6生成报文41，该报文41包括指示51和业务1的标识信息，所述指示51用于指示报文41为检测报文。
具体实现时，在SRv6网络中，PE设备11可以通过IPv6封装检测报文，得到报文41，该报文41也可以称为基于IPv6封装的检测报文。例如，假设检测报文为BFD报文，那么，S101中的报文41可以称为基于IPv6封装的BFD报文，封装之前的BFD报文对应封装之后报文41中的检测信息。
其中，业务1的标识信息，可以携带在报文41的IPv6头1中，也可以携带在IPv6扩展头1’中，用于标识该业务1。例如，业务1的标识信息可以是PE设备12为标识业务而分配的VPN SID。
其中，指示51可以携带在报文41的IPv6头1中，或者，指示51也可以携带在IPv6扩展头1’中。下面对指示51在各种情况下携带在报文41中的位置进行示例性说明。
作为一个示例，对于SRv6的尽力而为(best effort，BE)场景，指示51可以携带在IPv6头1的下一个头(next header)字段中，例如，报文41中IPv6头1的next header字段＝137，用于指示该报文41为检测报文。该示例下，报文41还可以包括IPv6扩展头1’，该IPv6扩展头1’中可以包括保留标签(alert label)和控制字，其中，alert label和控制字用于指示报文41的有效载荷(payload)部分携带有检测信息，该检测信息用于指示PE设备12根据该检测信息对承载业务1的路径进行故障检测或质量检测。其中，alert label和控制字用于指示检测信息，可以是基于alert label和控制字的取值确定后面携带的内容为检测信息，或者，也可以基于alert label和控制字的取值确定后面携带的内容为检测信息且能够确定检测信息的类型，例如，alert label＝13和控制字，可以确定后面携带的内容为检测信息且检测信息的类型为BFD信息。此外，指示51也可以认为携带在IPv6头1的next header字段以及IPv6扩展头1’中的alert label和控制字中，IPv6头1的next header字段、IPv6扩展头1’中的alert label和该IPv6扩展头1’中的控制字三者共同指示该报文41为检测报文。报文41的格式示意图参见图3a所示，该报文41可以包括IPv6头1和IPv6扩展头1’，其中，IPv6头1中可以包括源地址(source address，SA)字段、目的地址(destination address，DA)字段和next header字段，SA字段的取值为PE设备11的地址，例如等于PE设备11的环回(loopback)地址1::1，DA字段的取值为PE设备12的VPN段标识(segment identifier，SID)，例如等于PE设备12的End.DX2 A3::1500:0，next header字段的取值可以为137；IPv6扩展头1’中可以包括alert label和控制字，该报文41的payload中可以包括互联网协议(internet protocol，IP)、用户数据报协议(user datagram protocol，UDP)和检测信息，其中，alert label＝13，检测信息为BFD信息。
作为另一个示例，对于SRv6的策略(policy)场景，指示51可以携带在IPv6扩展头1的分段路由扩展头(segment routing header，SRH)中的next header字段中，例如，报文41中IPv6扩展头1’的next header字段＝137，用于指示该报文41为检测报文。该示例下，该IPv6扩展头1’中还可以包括alert label和控制字和检测信息，其中，alert label和控制字用于指示报文41的payload中的检测信息，该检测信息用于指示PE设备12根据该检测信息对承载业务1的路径进行故障检测。此外，指示51也可以认为携带在IPv6扩展头1’中SRH中的next header字段、alert label和控制字中，三者共同指示该报文41为检测报文。报文41的格式示意图参见图3b所示，该报文41可以包括IPv6头1和IPv6扩展头1’，其中，IPv6头1中可以包括SA字段和DA字段；IPv6扩展头1’可以包括next header字段、alert label和控制字，该报文41的payload中可以包括IP、UDP和检测信息，其中，next header字段的＝137，alert label＝13，检测信息为BFD信息。
作为又一个示例，对于SRv6 BE场景，指示51可以携带在IPv6头1的DA字段中，例如可以携带在IPv6头1的DA字段的变量(args)中，如，报文41中IPv6头1的DA字段的args＝3，用于指示该报文41为检测报文。该示例下，报文41的payload中可以包括检测信息。报文41的格式示意图参见图4a所示，该报文41可以包括IPv6头1和payload， 其中，IPv6头1中可以包括SA字段和DA字段，SA字段的取值为PE设备11的地址，例如等于PE设备11的loopback地址1::1，DA字段的取值为PE设备12的VPN SID，示例性地为End.DX2 A3::1500:3(即DA字段中args＝3)；payload中包括检测信息，其中，检测信息可以为BFD信息。在其他可能的方式中，该VPN SID中args也可以设置为其他取值，如其他非0的正整数。
作为另一个示例，对于SRv6 policy场景，指示51可以携带在IPv6扩展头1’的SRH中的DA字段中，例如可以携带在IPv6扩展头1’的DA字段的args中，例如，报文41中IPv6扩展头1’的DA字段中args＝3，用于指示该报文41为检测报文。该示例下，报文41的payload中可以包括检测信息。报文41的格式示意图参见图4b所示，该报文41可以包括IPv6头1、IPv6扩展头1’和payload，其中，IPv6头1中可以包括SA字段和DA字段，SA字段的取值为PE设备11的地址，例如等于PE设备11的loopback地址1::1，DA字段的取值为PE设备12的VPN SID，例如等于PE设备12的End.DX2 A3::1500:3；IPv6扩展头1’可以包括SRH，payload中可以包括IP、UDP和检测信息，其中，SRH中DA字段的args＝3，检测信息可以为BFD信息。
作为再一个示例，指示51可以携带在IPv6扩展头1’的SRH中的标志(flags)字段中，例如，报文41中IPv6扩展头1’的的SRH中的某个flag＝1，用于指示该报文41为检测报文，承载指示51的flag可以是未被定义的flags字段中的任意一个比特位，或者，也可以复用flags中已被占用的O-flag标志位。该示例下，报文41的payload中可以包括检测信息。报文41的格式示意图参见图5a所示，该报文41可以包括IPv6头1、IPv6扩展头1’和payload，其中，IPv6头1中可以包括SA字段和DA字段；IPv6扩展头1’中可以包括SRH，payload中可以包括IP、UDP和检测信息，其中，SRH的flags中的某个比特位的取值可以为1，检测信息可以为BFD信息。
作为又一个示例，一种情况下，指示51可以携带在IPv6扩展头1’的逐跳(hop by hop，HBH)选项头中的类型长度值(type length value，TLV)字段中，IPv6扩展头1’中的HBH选项头中包括该TLV字段，用于指示该报文41为检测报文。该报文41的payload中可以包括检测信息。报文41的格式示意图参见图6a所示，该报文41可以包括IPv6头1、IPv6扩展头1’和payload，其中，IPv6头1中可以包括SA字段和DA字段；IPv6扩展头1’可以包括HBH选项头，payload中可以包括IP、UDP和检测信息，其中，HBH选项头中包括TLV字段，检测信息可以为BFD信息。另一种情况下，指示51也可以携带在IPv6扩展头1’的目的地址选项头(destination option header，DOH)中的TLV字段中，IPv6扩展头1’中的DOH中包括该TLV字段，用于指示该报文41为检测报文。该报文41的payload中可以包括检测信息。报文41的格式示意图参见图6b所示，该报文41可以包括IPv6头1、IPv6扩展头1’和payload，其中，IPv6头1中可以包括SA字段和DA字段；IPv6扩展头1’可以包括DOH，payload中可以包括IP、UDP和检测信息，其中，DOH中包括TLV字段，检测信息可以为BFD信息。
上述各示例中，以报文41为BFD报文为例进行说明。如果报文41为OAM报文，则，携带指示51以及业务1的标识信息的方式可以参见上述各示例的实现，此时报文41的 payload中的检测信息可以是OAM信息，该OAM信息例如可以包括PE设备11向PE设备12发送数据包的数量、时间戳等。
需要说明的是，上述各种报文41中携带指示51的方式，均是示例性的，也可以采用其他可能的任何方式在报文41中携带指示51。
S102，PE设备11向PE设备12发送报文41。
在一些可能的实现方式中，如果PE设备11向PE设备12发送报文41的链路或经过的设备故障导致无法成功将该报文41发送给PE设备12，则，PE设备12不能接收到PE设备11发送的报文41，从而，PE设备11在预设时长内接收不到PE设备12发送的响应报文，可以确定PE设备11和CE设备22之间承载业务1的路径故障。其中，PE设备12不能成功接收到报文41对应的故障内容可以包括：PE设备11和P设备31之间的链路故障、P设备31和PE设备12之间的链路故障、P设备31故障或PE设备12故障。
在另一些可能的实现方式中，PE设备12能够成功接收到报文41，即，该方法100中在S102之后还包括S103～S104，则，可以基于该方法100实现检测。相关实现方式参见下述描述。
S103，PE设备12接收PE设备11发送的报文41。
具体实现时，在存在对承载业务1的路径进行检测的需求时，可以执行S102和S103以实施对应的检测；或者，也可以周期性的对承载业务的路径进行检测，即，每个周期执行S102～S103以实施对应的检测，其中，检测周期可以根据实际需求进行灵活设置。
S104，PE设备12根据指示51和业务1的标识信息对PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个进行检测。
具体实现时，PE设备12接收到报文41后，可以根据该报文41中的指示51和业务1的标识信息对承载业务1的路径进行检测，一方面，PE设备12可以对PE设备11和PE设备12之间用于承载业务1的路径进行检测，例如，检测PE设备12和P设备31之间的链路是否故障，又例如，检测PE设备12上用于连接P设备31的接口是否故障；另一方面，PE设备12也可以对该PE设备12和接入侧网络设备(如CE设备22)之间用于承载业务1的路径进行检测，例如，检测PE设备12和CE设备22之间的链路是否故障，又例如，检测PE设备12上用于连接CE设备22的接口是否故障。
如果PE设备12检测到承载业务1的路径不存在故障或路径质量满足要求，则，可以向PE设备11回复响应报文，该响应报文用于告知PE设备11承载业务1的路径正常。
如果PE设备12检测到承载业务1的路径存在故障或路径质量不满足要求，则，PE设备12可以不对该报文41作出响应，或者，PE设备12也可以向PE设备11发送用于通告故障或路径质量不满足要求的响应报文。
作为一个示例，PE设备12在确定承载业务1的路径存在故障或路径质量不满足要求时，例如，PE设备12感知到本地用于连接CE设备22的接口故障、PE设备12连接CE设备22的链路故障、PE设备12连接PE设备11的路径质量不满足要求(如时延超过预设的时延阈值)时，在S104之后，该方法还可以包括：PE设备12向PE设备11发送响应报 文；PE设备11接收到该响应报文后，即可根据响应报文确定PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个路径的路径状态，该路径状态包括对应路径的连通性和/或路径质量。其中，该响应报文中可以包括但不限于：PE设备12的本地的状态信息、PE设备12和接入侧网络设备之间链路的状态信息以及PE设备12连接接入侧网络设备的接口的状态信息。此外，该响应报文中还可以包括：PE设备12和PE设备11之间路径的状态信息以及PE设备12连接网络侧网络设备的接口的状态信息。PE设备11可以基于响应报文确定承载业务1的路径质量以及路径连通性此外。PE设备11也可以根据响应报文更精确的确定承载业务1的路径上各路径段的状态，如链路质量或者具体故障位置等，例如，可以确定：PE设备12和P设备31之间的链路状态、PE设备12和CE设备22之间的链路状态、PE设备12用于连接P设备31的接口状态或者PE设备12用于连接CE设备22的接口状态。
需要说明的是，在一种可能的情形中，如果PE设备12整机故障，则，无法再向PE设备11发送响应报文；在其他可能的情形中，即使PE设备12确定存在与其关联的路径故障，仍可以通过响应报文告知PE设备11故障的存在，例如，假设故障存在于PE设备11和PE设备12之间承载该业务1的路径上，那么，PE设备12可以选择其他可达的路径向PE设备11发送该响应报文，以告知PE设备11用于承载业务1的路径故障。
作为另一个示例，PE设备12在确定承载业务1的路径存在故障或路径质量不满足要求时，PE设备12可以不发送响应报文，具体可以包括但不限于：检测机制确定存在故障时不发送响应报文，或者，由于PE设备12和P设备31之间的链路故障或PE设备12用于连接P设备31的接口故障等原因导致无法发送响应报文。PE设备11中可以设置预设时长(如1秒)，该预设时长可以是PE设备11预先设置的发出检测报文后等待接收响应报文的最长允许时间。那么，当PE设备11从发送报文41开始经过预设时长，仍然未接收到PE设备12发来的针对报文41的响应报文，则PE设备11可以确定PE设备11和CE设备22之间承载业务1的路径存在故障或路径质量不满足要求。其中，承载业务1的路径存在故障的情况可以包括但不限于：PE设备12故障、P设备31故障、CE设备22故障、PE设备11到P设备31之间的链路故障、P设备31到PE设备12之间的链路、PE设备12到CE设备22之间的链路故障、PE设备11到P设备31之间的接口故障、P设备31到PE设备12之间的接口故障、PE设备12到CE设备22之间的接口故障、与PE设备12连接的用户侧网络中存在设备、链路或接口故障。
在一种可能的实现方式中，如果报文41为BFD报文，则，PE设备11向PE设备12发送该BFD报文，不仅可以感知到PE设备11和PE设备12之间承载该业务1的路径是否存故障，还能够基于BFD报文中的业务1的标识信息感知到PE设备12和接入侧网络设备(如CE设备22)之间承载该业务1的路径是否存在故障，这样，PE设备11即可通过该BFD报文，感知到承载该业务1的整个路径的连通性，达到业务级连通性检测的效果。
在另一种可能的实现方式中，如果报文41为OAM报文，则，PE设备11向PE设备12发送该OAM报文，可以实现对承载业务1的路径的连通性以及路径质量的检测。以检测路径质量为例，一种情况下，OAM报文实现路径质量检测的过程例如可以包括：PE设 备11向PE设备12发送OAM报文，告知PE设备11已发送业务数据包的统计信息(如发送的数据包数量、时间戳等信息)，PE设备12可以根据OAM报文中携带的VPN SID确定待检测的VPN对应的业务1，从而对自身获取的本设备中与该待检测业务1对应的接收数据包的统计结果和所接收OAM报文中的统计信息进行处理，得到承载该待检测业务1的路径对应的质量检测结果；接着，PE设备12可以生成并向PE设备11发送携带该检测结果的OAM响应报文，以指示PE设备11从所接收的该OAM响应报文中获得承载该待检测业务1的路径的质量检测结果，确定承载该待检测业务的路径质量。另一种情况下，OAM报文实现路径质量检测的过程例如也可以包括：PE设备11向PE设备12发送OAM报文，告知PE设备12已发送的业务数据包的统计信息，PE设备12可以根据OAM报文中携带的VPN SID确定待检测的VPN对应的业务1，并将PE设备12获取的与该待检测业务1对应的已接收数据包的统计结果携带在用于响应的OAM报文中发送给PE设备11，以使得PE设备11根据接收的响应OAM报文进行处理，获得承载该待检测业务1的路径的质量检测结果，从而确定承载该待检测业务1的路径质量。以上的两种情形以单向检测为例，在其他可能的情形中，PE设备11和PE设备12也可以对承载业务的路径进行双向检测，如PE设备11向PE设备12发送OAM报文，告知PE设备11已发送业务数据包的统计信息，并接收PE设备12发送的响应报文，该响应报文可以用于指示PE设备11对该业务的双向路径数据包进行统计，该响应报文还可以携带返程路径上针对该业务的数据包进行统计的统计信息。PE设备11可以根据该响应报文确定针对该业务的数据包的双向路径质量检测结果。如此，OAM报文作为检测报文，PE设备11接收到的响应报文中可以包括下述三者中的至少一个：承载业务1的路径的连通性检测结果(即，PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个是否存在故障)，承载业务1的路径的路径质量检测结果(即，PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个的路径质量是否满足要求)，以及承载业务1的路径的路径质量的统计结果(即，PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个的路径质量参数，可以由PE设备11对路径质量参数进行处理获得路径质量是否满足要求的路径质量检测结果)，其中对于路径质量检测可以指针对单向路径进行质量检测，也可以是指针对双向路径进行质量检测。
在一些可能的实现方式中，S104例如可以包括：PE设备12确定报文41为检测报文，且确定本地支持根据指示51进行检测，则，按照本地故障检测策略对承载业务1的路径进行故障检测。其中，按照本地故障检测策略，可以指将该报文41发送到对应的检测进程中，在对应的检测进程进行故障检测。例如，假设报文41为BFD检测报文，那么，PE设备12确定本地支持BFD检测时，将该BFD检测报文中业务相关内容和检测信息发送到本地BFD进程中，以在BFD进程进行对应的故障检测。又例如，假设报文41为OAM检测报文，那么，PE设备12确定本地支持OAM检测时，将该OAM检测报文中业务相关内容和检测信息发送到本地OAM实例中，以在OAM实例进行对应的检测。
其中，本地支持根据指示51进行检测，可以指PE设备本地配置使能了该指示51所指 示检测的相应检测功能。其中，该业务1例如可以是传统VPN业务1或EVPN业务1。在一种可能的情形中，如果检测报文中包括指示隧道信息的SRH，则，发送到检测进程中的内容可以为检测报文剥掉SRH之后的内容。
作为一个示例，如果报文41如上图5a所示，则，PE设备12可以在确定报文41的DA字段与本地的VPN SID匹配之后，根据报文41的指示51确定报文41为检测报文，确定PE设备12本地支持根据指示51进行检测，且该PE设备12为能够感知业务1的设备(如：PE设备12是出口PE设备)，则，将该报文41中业务相关内容和检测信息发送到对应的检测进程中，在对应的检测进程进行故障检测。
作为另一个示例，如果报文41如上图6a所示，则，PE设备12可以在确定报文41的IPv6扩展头1’的HBH选项头中存在承载指示51的TLV字段，根据报文41的指示51确定报文41为检测报文，确定本地支持根据指示51进行检测，且PE设备12为能够感知业务1的设备时，将该报文41中业务相关内容和检测信息发送到对应的检测进程中，在对应的检测进程进行故障检测。
作为又一个示例，如果报文41如上图6b所示，则，PE设备12可以在确定报文41的DA字段与本地的VPN SID匹配之后，确定报文41的IPv6扩展头1’的DOH中存在承载指示51的TLV字段，根据报文41的指示51确定报文41为检测报文，确定本地支持根据指示51进行检测，且PE设备12为能够感知业务1的设备，则，将该报文41中业务相关内容和检测信息发送到对应的检测进程中，在对应的检测进程进行故障检测。
在一些可能的实现方式中，PE设备11还可以向PE设备12发送业务1对应的业务报文，例如，该方法100还可以包括：S105，PE设备11向PE设备12发送报文42，该报文42为用于承载业务1的业务报文，该报文42不包括指示51。
一种情况下，报文2不包括承载指示51的字段，例如，报文41通过IPv6扩展头1’的HBH选项头中的TLV字段承载指示51，则，对应的报文42如图6b所示，HBH选项头中不包括对应的TLV字段。又例如，报文41通过IPv6扩展头1’的DOH中的TLV字段承载指示51，则，对应的报文42如图6d所示，DOH中不包括对应的TLV字段。
另一种情况下，报文42包括承载指示51的字段，该字段在报文42中承载指示52，该指示52用于指示报文42为业务报文，指示52与指示51不同。作为一个示例，报文42包括IPv6头2，指示52携带于IPv6头2中的next header字段，指示51为IPv6头1中的next header字段的第一值，那么，指示52为IPv6头2中的next header字段的第二值，第一值和第二值不相同。例如，报文41中IPv6头1中next header字段＝137，对应报文42如图3c所示，报文42中IPv6头2中next header字段＝143。作为另一个示例，报文42包括IPv6扩展头2’，指示52携带于IPv6扩展头2’的SRH中的next header字段，指示51为IPv6扩展头1’的SRH中的next header字段的第一值，那么，指示52为IPv6扩展头2’的SRH中的next header字段的第二值，第一值和第二值不相同。例如，报文41中IPv6扩展头1’中SRH的next header字段＝137，对应报文42如图3d所示，报文42中IPv6扩展头2’中SRH的next header字段＝143。在以上图3c和图3d的示例中，以next header字段在报文42中的取值均为143作为举例，在实际应用中，图3c和图3d中报文42的next header 字段的取值也可以不同。作为又一个示例，报文42包括IPv6头2，指示52携带于IPv6头2的DA字段中的args字段，指示51为IPv6头1中的DA字段的args的第三值，那么，指示52为IPv6头2中的DA字段的args的第四值，第三值和第四值不相同。例如，报文41中IPv6头1中DA字段的args字段＝3，对应报文42如图4c所示，报文42中IPv6头2中DA字段的args字段＝0。作为再一个示例，报文42包括IPv6扩展头2’，指示52携带于IPv6扩展头2’的SRH中的DA字段的args字段，指示51为IPv6扩展头1’的SRH中的DA字段的args字段的第三值，那么，指示52为IPv6扩展头2’的SRH中的DA字段的args字段的第四值，第三值和第四值不相同。例如，报文41中IPv6扩展头1’中SRH的DA字段的args字段＝3，对应报文42如图4d所示，报文42中IPv6扩展头2’中SRH的DA字段的args字段＝0。在以上图4c和图4d的示例中，以DA字段在报文42中的取值均为0作为举例，在实际应用中，图4c和图4d中报文42的args字段的取值也可以不同。作为又一个示例，报文42包括IPv6扩展头2’，指示52携带于IPv6扩展头2’的SRH中的flag字段，指示51为IPv6扩展头1’的SRH中的flag字段的第五值，那么，指示52为IPv6扩展头2’的SRH中的flag字段的第六值，第五值和第六值不相同。例如，报文41中IPv6扩展头1’中SRH的flag字段＝1，对应报文42如图5b所示，报文42中IPv6扩展头2’中SRH的flag字段＝0。
如此，对于接收方PE设备12，能够通过对所接收报文的解析，识别到所接收的报文是检测报文还是业务报文，从而执行相应的处理。例如，PE设备12通过对所接收报文41的解析获得指示51，基于指示51确定报文41为检测报文，从而执行上述S104；又例如，PE设备12通过对报文42的解析，确定不包括指示51的报文42为业务报文，从而按照业务报文的处理规则对该业务报文进行转发等相应的操作。
在一些可能的实现方式中，在PE设备11确定PE设备11和PE设备12之间承载业务1的路径以及PE设备12和CE设备22之间承载业务1的路径中的至少一个路径存在故障之后，为了保证业务的正常运行，PE设备11还可以将用于承载所述业务1的路径切换为包括PE设备11到PE设备13的路径，切换后PE设备13承载该业务1。切换之前，业务1对应的业务报文依据经过PE设备11、P设备31、PE设备12到达CE设备22，切换之后，业务1对应的业务报文依据经过PE设备11、P设备32、P设备33、PE设备13到达CE设备22，但是，无论是切换之前还是切换之后，业务2对应的业务报文均依次经过PE设备11、P设备31、PE设备12到达CE设备22，这样，克服了隧道级故障检测中，发现故障之后将隧道上所有的业务(包括业务1和业务2)均进行切换，切换后业务1和业务2均经过PE设备11、P设备31、PE设备12到达CE设备22，浪费网络资源的问题，提高了业务控制的精度。
可见，通过本申请实施例提供的方法100，发送方网络设备在发送的检测报文中添加指示和业务的标识信息，使得接收方网络设备能够精确的区分出所接收的报文是检测报文还是业务报文，当接收方网络设备确定接收到的报文是检测报文时，即可基于检测报文中的业务的标识信息确定待检测业务，进而对承载该待检测业务的路径进行检测，以实现更细粒度、更精确的业务级的故障检测，为业务级的切换提供了准确的依据，从而为网络中 业务的正常运行提供了保障。
基于上述方法实施例，本申请实施例提供了一种实现业务路径检测的装置，下面将结合附图对该装置进行说明。
图7为本申请实施例提供的一种实现业务路径检测的装置700的结构示意图，该装置700应用于第一网络设备，例如可以执行图1所示实施例中PE设备11的功能。该装置700可以包括：生成单元701和发送单元702。
其中，生成单元701，用于基于第六版互联网协议IPv6生成第一报文，所述第一报文包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文。
当装置700应用于图1所示的PE设备11时，生成单元701生成第一报文的具体实现可以参见图2所述实施例中S101。
发送单元702，用于向第二网络设备发送所述第一报文，以使得接收所述第一报文的所述第二网络设备根据所述第一指示和所述业务的标识信息对第一网络设备和第二网络设备之间承载所述业务的路径以及第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个进行检测。
当装置700应用于图1所示的PE设备11时，发送单元702发送第一报文的具体实现可以参见图2所述实施例中S102。
其中，业务的标识信息可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中
其中，第一指示可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
作为一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。其中，所述第一报文的所述第一IPv6扩展头还包括保留标签、控制字，所述保留标签和控制字用于指示所述第一报文的有效载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对所述业务的路径进行检测。
作为另一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
作为又一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
作为再一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
在一些可能的实现方式中，所述发送单元702，还用于向所述第二网络设备发送第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。
当装置700应用于图1所示的PE设备11时，发送单元702发送第二报文的具体实现 可以参见图2所述实施例中S105。
其中，所述第二报文还可以包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
其中，所述第二指示与所述第一指示不同，可以包括：所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的第二值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第二值；或者，所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
在一些可能的实现方式中，该装置700还可以包括确定单元。该确定单元，用于在预设时长未接收到所述第二网络设备对所述第一报文的响应报文，则，确定所述第一网络设备和所述接入侧网络设备之间用于承载所述业务的路径存在故障。
在一些可能的实现方式中，该装置700还可以包括接收单元和确定单元。其中，接收单元，用于接收所述第二网络设备对所述第一报文的响应报文；确定单元，用于根据所述响应报文，确定所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个路径的路径状态。其中，路径状态包括路径连通性和路径质量中的至少一个
在一些可能的实现方式中，该装置700还可以包括切换单元。该切换单元，用于根据在预设时长未接收到所述第二网络设备对所述第一报文的响应报文确定所述用于承载所述业务的路径存在故障，或，根据所述路径状态确定所述用于承载所述业务的路径存在故障或不满足路径质量要求时，将用于承载所述业务的路径切换为包括所述第一网络设备到第三网络设备的路径，切换后所述第三网络设备承载所述业务。
关于实现业务路径检测的装置700具体可执行的功能和实现，可以参见图2所示实施例中关于PE设备11的相应描述，此处不再赘述。
此外，本申请实施例还提供了一种实现业务路径检测的装置800，如图8所示，该装置800应用于第二网络设备，例如可以执行图1所示实施例中PE设备12的功能。该装置800可以包括：接收单元801和检测单元802。
其中，接收单元801，用于接收第一网络设备发送的第一报文，所述第一报文中包括 第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文。
当装置800应用于图1所示的PE设备12时，接收单元801接收第一报文的具体实现可以参见图2所述实施例中S103。
检测单元802，用于根据所述第一指示和所述业务的标识信息对第一网络设备和第二网络设备之间承载所述业务的路径以及第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个进行检测。
当装置800应用于图1所示的PE设备12时，检测单元802对承载业务的路径的检测的具体实现可以参见图2所述实施例中S104。
其中，业务的标识信息可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中
其中，第一指示可以携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
作为一个示例，所述第一报文包括第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，所述第一报文包括第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。其中，所述第一报文的所述第一IPv6扩展头还包括保留标签、控制字，所述保留标签和控制字用于指示所述第一报文的有效载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对承载所述业务的路径进行检测。
作为另一个示例，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
作为又一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
作为再一个示例，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
在一些可能的实现方式中，所述接收单元801，还用于接收所述第一网络设备发送的第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。当装置800应用于图1所示的PE设备12时，接收单元801接收第二报文的具体实现可以参见图2所述实施例中S105。
其中，所述第二报文还可以包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
其中，所述第二指示与所述第一指示不同，可以包括：所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的第二值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第 二值；或者，所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA字段中的args字段的第四值；或者，所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
在一些可能的实现方式中，该装置800还可以包括发送单元。该发送单元，用于向所述第一网络设备发送响应报文，以指示所述第一网络设备根据所述响应报文确定所述第一网络设备和所述第二网络设备之间承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间承载所述业务的路径中的至少一个路径状态，其中，路径状态包括路径连通性和路径质量中的至少一个。其中，所述第二网络设备发送的所述响应报文包括所述第二网络设备的接口状态信息，所述接口状态信息用于指示所述第一网络设备确定所述第二网络设备和接入侧网络设备之间承载所述业务的路径是否存在故障或路径质量好坏。
在一些可能的实现方式中，所述检测单元802，具体可以用于：确定所述第一报文为检测报文，且确定本地支持根据所述第一指示进行检测，则，按照本地检测策略对承载所述业务的路径进行检测。
关于实现业务路径检测的装置800具体可执行的功能和实现，可以参见图2所示实施例中关于PE设备12的相应描述，此处不再赘述。
上述实现业务路径检测的装置700可以为承载所述业务的入口PE设备，实现业务路径检测的装置800可以为承载所述业务的出口PE设备。
上述实现业务路径检测的装置700和实现业务路径检测的装置800之间承载的业务，可以是L2VPN业务，L2VPN例如可以包括传统VPN技术或EVPN技术承载的业务。无论是传统VPN业务还是EVPN业务，均可以采用VLL业务模型或VPLS业务模型。
上述实现业务路径检测的装置700和实现业务路径检测的装置800中，第一报文可以为BFD报文，或者，也可以为OAM报文。
图9为本申请实施例提供的一种网络设备900的结构示意图，该网络设备900例如可以是图1所示实施例中的任意一个PE设备，或者也可以是图7或图8所示实施例中的实现业务路径检测的装置的设备实现。
请参阅图9所示，网络设备900包括：处理器910、通信接口920和存储器930。其中网络设备900中的处理器910的数量可以一个或多个，图9中以一个处理器为例。本申请实施例中，处理器910、通信接口920和存储器930可通过总线系统或其它方式连接，其中，图9中以通过总线系统940连接为例。
处理器910可以是CPU、NP、或者CPU和NP的组合。处理器910还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)， 可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
当网络设备900包括第一网络设备时，处理器910可以执行上述方法实施例中生成包括第一指示和业务的标识信息的第一报文，向第二网络设备发送第一报文等的相关功能。当网络设备900为第二网络设备时，处理器910可以执行上述方法实施例中从第一网络设备接收包括第一指示和业务的标识信息的第一报文，根据第一指示和业务的标识信息对承载业务的路径进行检测等的相关功能。
通信接口920用于接收和发送报文，具体地，通信接口920可以包括接收接口和发送接口。其中，接收接口可以用于接收报文，发送接口可以用于发送报文。通信接口920的个数可以为一个或多个。作为一种可能的实现，通信接口920可以用于实现图7示出的发送单元702或图8示出的接收单元801的功能。
存储器930可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器930也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器930还可以包括上述种类的存储器的组合。存储器930例如可以存储前文提及的业务的标识信息。
可选地，存储器930存储有操作系统和程序、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，程序可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。处理器910可以读取存储器930中的程序，实现本申请实施例提供的实现业务路径检测的方法。作为一种可能的实现，存储器930中可以存储诸如用于实现图7示出的生成单元701或图8示出的检测单元802功能的程序代码。
其中，存储器930可以为网络设备900中的存储器件，也可以为独立于网络设备900的存储装置。
总线系统940可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线系统940可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图10是本申请实施例提供的另一种网络设备1000的结构示意图，网络设备1000可以配置为前述图1所示实施例中的任意一个PE设备，或者也可以是图7或图8所示实施例中的实现业务路径检测的装置的设备实现。
网络设备1000包括：主控板1010和接口板1030。
主控板1010也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板1010对网络设备1000中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板1010包括：中央处理器1011和存储器1012。
接口板1030也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板1030用于提供各种业务接口并实现数据包的转发。业务接口包括而不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(Flexible Ethernet Clients，FlexE Clients)。接口板1030包括：中央处理器1031、网络处理器1032、转发表项存储器1034和物理接口卡(ph8sical interface card，PIC)1033。
接口板1030上的中央处理器1031用于对接口板1030进行控制管理并与主控板1010上的中央处理器1011进行通信。
网络处理器1032用于实现报文的转发处理。网络处理器832的形态可以是转发芯片。具体而言，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理：转发表查找等等。
物理接口卡1033用于实现物理层的对接功能，原始的流量由此进入接口板1030，以及处理后的报文从该物理接口卡1033发出。物理接口卡1033包括至少一个物理接口，物理接口也称物理口。物理接口卡1033也可称为子卡，可安装在接口板1030上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器1032处理。在一些实施例中，接口板1030的中央处理器831也可执行网络处理器1032的功能，比如基于通用CPU实现软件转发，从而物理接口卡1033中不需要网络处理器1032。
可选地，网络设备1000包括多个接口板，例如网络设备1000还包括接口板1040，接口板1040包括：中央处理器1041、网络处理器1042、转发表项存储器1044和物理接口卡1043。
可选地，网络设备1000还包括交换网板1020。交换网板1020也可以称为交换网板单元(switch fabric unit，SFU)。在网络设备有多个接口板1030的情况下，交换网板1020用于完成各接口板之间的数据交换。例如，接口板1030和接口板1040之间可以通过交换网板820通信。
主控板1010和接口板1030耦合。例如。主控板1010、接口板1030和接口板1040，以及交换网板1020之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板1010和接口板1030之间建立进程间通信协议(inter-process communication，IPC)通道，主控板1010和接口板1030之间通过IPC通道进行通信。
在逻辑上，网络设备1000包括控制面和转发面，控制面包括主控板1010和中央处理器1031，转发面包括执行转发的各个组件，比如转发表项存储器1034、物理接口卡1033和网络处理器1032。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器1032基于控制面下发的转发表对物理接口卡1033收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器1034中。在一些实施例中，控制面和转发面可以完全分离，不在同一设备上。
如果网络设备1000被配置为第一网络设备时，中央处理器1011可以生成包括第一指示和业务的标识信息的第一报文。网络处理器1032可以触发物理接口卡1033向第二网络设备发送所述第一报文。
如果网络设备1000被配置为第二网络设备，中央处理器1011可以从第一网络设备接收包括第一指示和业务的标识信息的第一报文，根据第一指示和业务的标识信息对承载业务的路径进行检测。网络处理器1032可以触发物理接口卡1033向第一网络设备发送响应报文。
应理解，实现业务路径检测的装置700中的发送单元702等可以相当于网络设备1000中的物理接口卡1033或物理接口卡1043；实现业务路径检测的装置700中的生成单元701等可以相当于网络设备1000中的中央处理器1011或中央处理器1031。实现业务路径检测的装置800中的接收单元801等可以相当于网络设备1000中的物理接口卡1033或物理接口卡1043；实现业务路径检测的装置800中的检测单元802等可以相当于网络设备1000中的中央处理器1011或中央处理器1031。
应理解，本申请实施例中接口板1040上的操作与接口板1030的操作一致，为了简洁，不再赘述。应理解，本实施例的网络设备1000可对应于上述各个方法实施例中的任意一个节点，该网络设备1000中的主控板1010、接口板1030和/或接口板1040可以实现上述各个方法实施例中的任意一个节点所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
应理解，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。可选地，网络设备的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等网络设备)。具体采用哪种架构，取决于具体的组网部署场景。
在一些可能的实施例中，上述各节点可以实现为虚拟化设备。例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(英文：Virtual Machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。可以将虚拟机配置为各节点。例如，可以基于通用的物理服务器结合网络功能虚拟化(Network Functions Virtualization，NFV)技术来实现各节点。各节点为虚拟主机、虚拟路由器或虚拟交换机。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的各节点，此处不再赘述。
应理解，上述各种产品形态的网络设备，分别具有上述方法实施例中各节点的任意功能，此处不再赘述。
本申请实施例还提供了一种网络系统1100，如图11所示。该网络系统1100可以包括第一网络设备1101和第二网络设备1102。其中，第一网络设备1101可以是图1所示的PE设备11、图7所示的实现业务路径检测的装置700、图9所示的被配置为第一网络设备的网络设备900或者图10所示的被配置为第一网络设备的网络设备1000；第二网络设备1102可以是图1所示的PE设备12、图8所示的实现业务路径检测的装置800、图9所示的被配置为第二网络设备的网络设备900或者图10所示的被配置为第二网络设备的网络设备1000。
本申请实施例还提供了一种芯片，包括处理器和接口电路，接口电路，用于接收指令并传输至处理器；处理器，例如可以是图7示出的实现业务路径检测的装置700的一种具体实现形式，可以用于执行上述方法；又例如可以是图8示出的实现业务路径检测的装置800的一种具体实现形式，可以用于执行上述方法。其中，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例还提供了一种计算机可读存储介质，包括指令或计算机程序，当其在计算机上运行时，使得计算机执行以上实施例提供的实现业务路径检测的方法。
本申请实施例还提供了一种包含指令或计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行以上实施例提供的实现业务路径检测的方法。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑业务划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各业务单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件业务单元的形式实现。
集成的单元如果以软件业务单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的业务可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些业务存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明的具体实施方式而已。
以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (39)

  1. 一种实现业务路径检测的方法，其特征在于，所述方法应用于支持基于第六版互联网协议的分段路由SRv6的网络中，所述方法包括：
    第一网络设备基于第六版互联网协议IPv6生成第一报文，所述第一报文包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文；
    所述第一网络设备向第二网络设备发送所述第一报文，以指示接收所述第一报文的所述第二网络设备根据所述第一指示和所述业务的标识信息对所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个进行检测。
  2. 根据权利要求1所述的方法，其特征在于，所述第一指示携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
  3. 根据权利要求2所述的方法，其特征在于，
    所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，
    所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。
  4. 根据权利要求3所述的方法，其特征在于，所述第一报文的所述第一IPv6扩展头还包括保留标签和控制字，所述保留标签和控制字用于指示所述第一报文的载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对所述业务的路径进行检测。
  5. 根据权利要求2所述的方法，其特征在于，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，
    所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
  6. 根据权利要求2所述的方法，其特征在于，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
  7. 根据权利要求2所述的方法，其特征在于，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
  8. 根据权利要求2-7任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述第二网络设备发送第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。
  9. 根据权利要求8所述的方法，其特征在于，所述第二报文还包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
  10. 根据权利要求9所述的方法，其特征在于，所述第二指示与所述第一指示不同，包括：
    所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header 字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的第二值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第二值；或者，
    所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA字段中的args字段的第四值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备在预设时长未接收到所述第二网络设备对所述第一报文的响应报文，则，所述第一网络设备确定所述第一网络设备和所述接入侧网络设备之间用于承载所述业务的路径存在故障。
  12. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收所述第二网络设备对所述第一报文的响应报文；
    所述第一网络设备根据所述响应报文，确定所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径的路径状态。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备根据在预设时长未接收到所述第二网络设备对所述第一报文的响应报文确定所述用于承载所述业务的路径存在故障，或，根据所述路径状态确定所述用于承载所述业务的路径存在故障或不满足路径质量要求时，将用于承载所述业务的路径切换为包括所述第一网络设备到第三网络设备的路径，切换后所述第三网络设备承载所述业务。
  14. 一种实现业务路径检测的方法，其特征在于，所述方法应用于支持基于第六版互联网协议的分段路由SRv6的网络中，所述方法包括：
    第二网络设备接收第一网络设备发送的第一报文，所述第一报文中包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文；
    所述第二网络设备根据所述第一指示和所述业务的标识信息对所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个进行检测。
  15. 根据权利要求14所述的方法，其特征在于，所述第一指示携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
  16. 根据权利要求15所述的方法，其特征在于，
    所述第一报文包括第一IPv6头，所述第一指示携带于所述第一IPv6头中的下一个头next header字段；或者，
    所述第一报文包括第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一分段路由扩展头SRH中的next header字段。
  17. 根据权利要求16所述的方法，其特征在于，所述第一报文的所述第一IPv6扩展头还包括保留标签和控制字，所述保留标签和控制字用于指示所述第一报文的载荷payload中的检测信息，所述检测信息用于指示所述第二网络设备根据所述检测信息对承载所述业务的路径进行检测。
  18. 根据权利要求15所述的方法，其特征在于，所述第一报文包括所述第一IPv6头，所述第一指示携带于所述第一IPv6头的第一目的地址DA字段中的变量args字段；或者，
    所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的第一SRH的第一DA字段中的args字段。
  19. 根据权利要求15所述的方法，其特征在于，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的SRH中的标志flags字段。
  20. 根据权利要求15所述的方法，其特征在于，所述第一报文包括所述第一IPv6扩展头，所述第一指示携带于所述第一IPv6扩展头的逐跳HBH选项头中的类型长度值TLV字段，或者携带于所述第一IPv6扩展头的目的地址选项头DOH中的TLV字段。
  21. 根据权利要求15-20任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第一网络设备发送的第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。
  22. 根据权利要求21所述的方法，其特征在于，所述第二报文还包括第二指示，所述第二指示用于指示所述第二报文为业务报文，所述第二指示与所述第一指示不同。
  23. 根据权利要求22所述的方法，其特征在于，所述第二指示与所述第一指示不同，包括：
    所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头中的next header字段，所述第一指示为所述第一IPv6头中的next header字段的第一值，所述第二指示为所述第二IPv6头中的next header字段的第二值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的next header字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的next header字段的第一值，所述第二指示为所述第二SRH中的next header字段的第二值；或者，
    所述第二报文包括第二IPv6头，所述第二指示携带于所述第二IPv6头的第二DA字段中的args字段，所述第一指示为所述第一IPv6头的第一DA字段中的args字段的第三值，所述第二指示为所述第二DA字段中的args字段的第四值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的第二SRH中的第二DA字段的args字段，所述第一指示为所述第一IPv6扩展头的第一SRH中的第一DA字段的args字段的第三值，所述第二指示为所述第二SRH中的所述第二DA 字段中的args字段的第四值；或者，
    所述第二报文包括第二IPv6扩展头，所述第二指示携带于所述第二IPv6扩展头的SRH中的flags字段，所述第一指示为所述第一IPv6扩展头的SRH中的标志flags字段的第五值，所述第二指示为所述第二IPv6扩展头的SRH中的标志flags字段的第六值。
  24. 根据权利要求14-23任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送响应报文，以指示所述第一网络设备根据所述响应报文确定所述第一网络设备和第二网络设备之间用于承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个的路径状态。
  25. 根据权利要求24所述的方法，其特征在于，所述路径状态包括路径连通性和路径质量中的至少一个。
  26. 根据权利要求14-25任一项所述的方法，其特征在于，所述第二网络设备根据所述第一指示和所述业务的标识信息对所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个进行检测，包括：
    所述第二网络设备确定所述第一报文为检测报文，且确定本地支持根据所述第一指示进行检测，则，按照本地检测策略对承载所述业务的路径进行检测。
  27. 根据权利要求1-26任一项所述的方法，其特征在于，所述第一网络设备为承载所述业务的入口运营商边缘PE设备，所述第二网络设备为承载所述业务的出口PE设备。
  28. 根据权利要求1-27任一项所述的方法，其特征在于，所述第一网络设备和所述第二网络设备之间布署虚拟租用线路VLL或虚拟专用局域网业务VPLS。
  29. 根据权利要求1-28任一项所述的方法，其特征在于，所述第一报文为双向转发检测BFD报文，或者，所述第一报文为操作管理和维护OAM报文。
  30. 根据权利要求1-29任一项所述的方法，其特征在于，所述业务的标识信息为虚拟专用网段标识VPN SID，所述业务的类型为传统虚拟专用网VPN业务或以太虚拟专用网EVPN业务。
  31. 一种网络系统，其特征在于，所述网络系统应用于支持基于第六版互联网协议的分段路由SRv6的网络中，所述网络系统包括第一网络设备和第二网络设备，其中：
    所述第一网络设备，用于基于第六版互联网协议IPv6生成第一报文，并向所述第二网络设备发送所述第一报文，所述第一报文包括第一指示和业务的标识信息，所述第一指示用于指示所述第一报文为检测报文；
    所述第二网络设备，用于接收所述第一网络设备发送的第一报文，并根据所述第一指示和所述业务的标识信息对所述第一网络设备和所述第二网络设备之间用于承载所述业务的路径，以及所述第二网络设备和接入侧网络设备之间用于承载所述业务的路径中的至少一个进行检测。
  32. 根据权利要求31所述的网络系统，其特征在于，所述第一指示携带于所述第一报文的第一IPv6头或第一IPv6扩展头中。
  33. 根据权利要求31或32所述的网络系统，其特征在于，
    所述第一网络设备，还用于向所述第二网络设备发送第二报文，所述第二报文为用于承载所述业务的业务报文，所述第二报文不包括所述第一指示。
  34. 根据权利要求31-33任一项所述的网络系统，其特征在于，所述第一网络设备和所述第二网络设备之间布署虚拟租用线路VLL或虚拟专用局域网业务VPLS。
  35. 根据权利要求31-34任一项所述的网络系统，其特征在于，所述第一报文为双向转发检测BFD报文，或者，所述第一报文为操作管理和维护OAM报文。
  36. 一种网络设备，其特征在于，包括：
    存储器，所述存储器包括计算机可读指令；
    与所述存储器通信的处理器，所述处理器用于执行所述计算机可读指令，使得所述网络设备执行权利要求1-13、27-30任一项所述的方法。
  37. 一种网络设备，其特征在于，包括：
    存储器，所述存储器包括计算机可读指令；
    与所述存储器通信的处理器，所述处理器用于执行所述计算机可读指令，使得所述网络设备执行权利要求14-30任一项所述的方法。
  38. 一种计算机可读存储介质，其特征在于，包括程序或指令，当其被处理器执行时实现如权利要求1-30任一项所述的方法。
  39. 一种计算机程序产品，其特征在于，包括计算机程序，所述计算机程序被处理器执行时实现权利要求1-30任一项所述的方法。
PCT/CN2021/118135 2020-09-21 2021-09-14 一种实现业务路径检测的方法、设备和系统 WO2022057779A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21868602.0A EP4210286A4 (en) 2020-09-21 2021-09-14 METHOD, DEVICE AND SYSTEM FOR IMPLEMENTING SERVICE PATH DETECTION
JP2023518238A JP2023541706A (ja) 2020-09-21 2021-09-14 サービスパス検出を実施する方法、デバイス、及びシステム
US18/186,631 US20230261979A1 (en) 2020-09-21 2023-03-20 Method, Device, and System for Implementing Service Path Detection

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202010992436 2020-09-21
CN202010992436.9 2020-09-21
CN202011375770.6A CN114257494A (zh) 2020-09-21 2020-11-30 一种实现业务路径检测的方法、设备和系统
CN202011375770.6 2020-11-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/186,631 Continuation US20230261979A1 (en) 2020-09-21 2023-03-20 Method, Device, and System for Implementing Service Path Detection

Publications (1)

Publication Number Publication Date
WO2022057779A1 true WO2022057779A1 (zh) 2022-03-24

Family

ID=80776475

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/118135 WO2022057779A1 (zh) 2020-09-21 2021-09-14 一种实现业务路径检测的方法、设备和系统

Country Status (4)

Country Link
US (1) US20230261979A1 (zh)
EP (1) EP4210286A4 (zh)
JP (1) JP2023541706A (zh)
WO (1) WO2022057779A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102282805A (zh) * 2011-05-26 2011-12-14 华为技术有限公司 一种业务保护方法及接入设备
CN102468977A (zh) * 2010-11-19 2012-05-23 中兴通讯股份有限公司 分组传送网的保护方法和装置
CN107872356A (zh) * 2016-09-26 2018-04-03 中兴通讯股份有限公司 业务功能链检测路径的方法和装置
WO2019128950A1 (zh) * 2017-12-27 2019-07-04 华为技术有限公司 一种报文处理的方法、网络节点和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8976680B2 (en) * 2010-03-15 2015-03-10 Juniper Networks, Inc. Operations, administration, and management fields for packet transport
US9525622B2 (en) * 2014-03-17 2016-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Label stack encoding and processing to enable OAM procedures for service segments in segment routed (SR) networks
CN113364610B (zh) * 2018-03-30 2022-08-09 华为技术有限公司 网络设备的管理方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102468977A (zh) * 2010-11-19 2012-05-23 中兴通讯股份有限公司 分组传送网的保护方法和装置
CN102282805A (zh) * 2011-05-26 2011-12-14 华为技术有限公司 一种业务保护方法及接入设备
CN107872356A (zh) * 2016-09-26 2018-04-03 中兴通讯股份有限公司 业务功能链检测路径的方法和装置
WO2019128950A1 (zh) * 2017-12-27 2019-07-04 华为技术有限公司 一种报文处理的方法、网络节点和系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on User Plane Protocol in 5GC. (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 29.892, vol. CT WG4, no. V1.3.0, 8 September 2019 (2019-09-08), pages 1 - 51, XP051784486 *
See also references of EP4210286A4

Also Published As

Publication number Publication date
JP2023541706A (ja) 2023-10-03
EP4210286A4 (en) 2024-02-28
US20230261979A1 (en) 2023-08-17
EP4210286A1 (en) 2023-07-12

Similar Documents

Publication Publication Date Title
US20220407802A1 (en) Packet processing method and apparatus, network device, and storage medium
CN108574616B (zh) 一种处理路由的方法、设备及系统
CN113411834B (zh) 报文处理方法、装置、设备及存储介质
CN112565046B (zh) 同步多播路由器能力
CN113395735B (zh) 一种报文传输方法、装置和网络设备
US20120134365A1 (en) Method and network device for associated channel capability negotiation
WO2022105927A1 (zh) 一种通告网络设备处理能力的方法、设备和系统
JP2021534669A (ja) パケット処理方法およびゲートウェイ・デバイス
KR20220093155A (ko) 패킷 전달 방법, 제1 네트워크 디바이스 및 제1 디바이스 그룹
CN114257494A (zh) 一种实现业务路径检测的方法、设备和系统
WO2022057779A1 (zh) 一种实现业务路径检测的方法、设备和系统
CN114760244B (zh) 一种传输绑定段标识bsid的方法、装置和网络设备
CN114205221B (zh) 一种故障查询方法及装置
CN110545240B (zh) 基于分布式聚合系统的标签转发表的建立及报文转发方法
US20230388177A1 (en) Fault detection method, network device, and system
WO2023213216A1 (zh) 一种报文处理的方法及相关设备
WO2022166464A1 (zh) 一种报文传输方法、系统及设备
CN114629834B (zh) 通信方法及装置
WO2023125774A1 (zh) 一种vxlan报文传输方法、网络设备及系统
WO2022037330A1 (zh) 传输虚拟专用网的段标识vpn sid的方法、装置和网络设备
WO2024021976A1 (zh) 一种报文处理的方法及相关设备
WO2023284547A1 (zh) 一种故障检测的方法、装置和系统
WO2022228533A1 (zh) 处理报文的方法、装置、系统及存储介质
WO2023040783A1 (zh) 获取能力、发送能力信息的方法、装置、系统及存储介质
JP2024500907A (ja) ルート伝送方法および装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2023518238

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021868602

Country of ref document: EP

Effective date: 20230404