WO2017148139A1 - 故障检测方法及装置 - Google Patents

故障检测方法及装置 Download PDF

Info

Publication number
WO2017148139A1
WO2017148139A1 PCT/CN2016/100111 CN2016100111W WO2017148139A1 WO 2017148139 A1 WO2017148139 A1 WO 2017148139A1 CN 2016100111 W CN2016100111 W CN 2016100111W WO 2017148139 A1 WO2017148139 A1 WO 2017148139A1
Authority
WO
WIPO (PCT)
Prior art keywords
bier
tlv
bfir
detection message
bfer
Prior art date
Application number
PCT/CN2016/100111
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
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017148139A1 publication Critical patent/WO2017148139A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • 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

Definitions

  • This document relates to, but is not limited to, the field of communications, and more particularly to a fault detection method and apparatus.
  • BIER Bit Indexed Explicit Replication
  • BIER-TE Bit Index Explicit Replication-Traffic Enginering
  • Each bit position in a BitString represents one or more adjacencies, rather than a BFER.
  • the embodiment of the invention provides a fault detection method and device, which can implement path detection in BIER-TE.
  • An embodiment of the present invention provides a fault detection method, including: receiving an operation management and maintenance OAM detection message from a controller for requesting detection of a bit index display based on a traffic engineering extension to copy a BIER-TE path; and detecting the OAM according to the OAM detection The message performs fault detection on the BIER-TE path.
  • receiving the OAM detection message from the controller for requesting to detect the BIER-TE path comprises: receiving the OAM detection message by using a path for receiving a BIER-TE data message.
  • performing fault detection on the BIER-TE path according to the OAM detection message includes: the BFIR or BFR according to The bit forwarding egress router BFER information carried in the OAM detection message forwards the OAM detection message to the BFER corresponding to the BFER information, where the OAM detection message is used to indicate that the BFER performs the BIER-TE The path performs verification of the fault detection, and feeds back the verification result to the controller; or the BFIR or BFR performs fault detection on the BIER-TE path according to the lifetime TTL of the OAM detection message, where: When the value of the TTL is 1, the BFIR or the BFR performs the check of the fault detection on the BIER-TE path by using the OAM detection message, and feeds back the check result to the controller; when the value of the TTL is When the M value is greater than 1, the BFIR or BFR forwards the
  • receiving the OAM detection message from the controller includes: the BFER receiving bit forwarding ingress router BFIR or a bit forwarding router BFR forwarding
  • the OAM detection message from the controller includes: the BFER performing fault detection on the BIER-TE path according to the OAM detection message by using the OAM detection message Verification and feedback of the verification result to the controller.
  • the BFER performs the check of the fault detection on the BIER-TE path by using the OAM detection message, and feeds back the check result to the controller, where the BFER is: And the bit string BitString in the BIER-TE header header carried in the OAM detection message and the BIER-TE local decapsulation type length value local_decap TLV in the BIER-TE response request echo request carried in the OAM detection message a BFER address is filled in the advertising node identifier of the advertising node identifier carried in the BIER-TE local_decap TLV, and the adjacency id of the BFER identifies the adjacency id and the BitString When the index represented by the corresponding bit is consistent, the verification succeeds, and a BIER-TE response echo reply carrying the verification success information is sent to the controller;
  • the controller sends a BIER-TE response with an authentication failure message to answer the echo reply.
  • the BFER uses OAM detection.
  • the BFER will be a bit string in the header of the BIER-TE data header carried in the OAM detection message.
  • the BFIR or BFR when performing the verify operation as BFIR or BFR, performs verification of fault detection on the BIER-TE path by using an OAM detection message, and feeds back the verification result to the controller.
  • the BFIR or the BFR is configured according to the bit string BitString in the BIER-TE header header carried in the OAM detection message and the destination forwarding equivalence class in the BIER-TE response request echo request carried in the OAM detection message.
  • the stack type length value is verified in the corresponding adjacency FEC in the Target FEC Stack TLV, and is The controller feeds back the verification result.
  • the corresponding adjacency FEC in the Target FEC Stack TLV includes a forward connection forward_connected TLV and/or a forward route forward_routed TLV, where the corresponding adjacency FEC in the Target FEC Stack TLV includes the forward_connected In the TLV, the BFIR or the BFR is verified according to the BitString in the BIER-TE header carried in the OAM detection message and the corresponding adjacency FEC in the Target FEC Stack TLV in the BIER-TE echo request carried in the OAM detection message.
  • feeding back the verification result to the controller includes: when the BFIR or BFR checks out that the BIER-TE forward_connected TLV is filled in, is a direct link of the BFIR or BFR, and the BFIR or BFR When the adjacency id allocated to the direct link is consistent with the index indicated by the corresponding bit in the BitString, the verification succeeds, and a BIER-TE response echo reply carrying the verification success information is sent to the controller; When BFIR or BFR verifies that a BIER-TE forward_connected TLV is filled in a direct link that is not BFIR or BFR, or BFIR or BFR is the direct link If the assigned adjacency id is inconsistent with the index indicated by the corresponding bit in the BitString, the verification fails, and the BIER-TE response echo reply carrying the verification failure information is sent to the controller; when the Target FEC Stack TLV is corresponding When the adjacency FEC includes the forward_routed TLV, the BFIR or the BFR is based
  • the adjacency FEC performs verification, and feeding back the verification result to the controller includes: when the BFIR or BFR check out the BIER-TE forward_routed TLV, the prefix prefix information is filled in, and the BFIR or BFR is When the adjacency id of the prefix is consistent with the index represented by the corresponding bit in the BitString, the verification succeeds, and the BIER-TE response echo reply carrying the verification success information is sent to the controller; when the BFIR or BFR school Check out the BIER-TE forward_routed TLV is not the prefix prefix information, or the BFIR or BFR prefix assigned adjacency id and BitString When the index indicated by the bit is inconsistent, the verification fails, and a BIER-TE response echo reply carrying the verification failure information is sent to the controller.
  • the BIER-TE echo reply when the BFIR or the BFR sends a BIER-TE response response echo reply carrying the verification success information to the controller, the BIER-TE echo reply further carries: a downstream mapping downstream mapping TLV information, And the FEC Stack Change TLV, where the downstream mapping TLV information carries the downstream node address and the downstream interface address; the FEC Stack Change TLV is used to notify the controller to pop up the corresponding in the Target FEC Stack TLV. Adjacency FEC.
  • the embodiment of the present invention further provides a fault detection method, including: sending, to a bit forwarding ingress router BFIR, an operation management and maintenance OAM detection message for requesting detection of a bit index display replication BIER-TE path based on a traffic engineering extension, where The OAM detection message is used to indicate the location
  • the BFIE performs fault detection on the BIER-TE path according to the OAM detection message.
  • sending, by the BFIR, the OAM detection message for requesting to detect the BIER-TE path includes: sending, to the BFIR, the OAM detection message for requesting detection of the BIER-TE path, where The OAM detection message carries a bit forwarding egress router BFER information, where the BFER information is used to instruct the BFIR to forward the OAM detection message to the BFER corresponding to the BFER information according to the BFER information, where the OAM detection is performed.
  • the message is used to indicate that the BFER performs verification of fault detection on the BIER-TE path, and feeds back a verification result; or sends a survival time to the BFIR for requesting detection of the BIER-TE path
  • the OAM detection message of the TTL wherein: when the value of the TTL is 1, the OAM detection message is used to indicate that the BFIR performs a fault detection on the BIER-TE path according to the OAM detection message. When the value of the TTL is greater than 1, the OAM detection message is used to instruct the BFIR to forward the OAM detection message to the (M-1)th hop node after the BFIR.
  • the OAM detection message is used to indicate the first after the BFIR ( M-1)
  • the hopping node performs verification of fault detection on the BIER-TE path according to the OAM detection message, and feeds back the verification result.
  • the method further includes: after sending the OAM detection message for requesting detection of the BIER-TE path to the BFIR, receiving the BFIR or the bit forwarding after the BFIR on the path to be detected
  • the BIER-TE response carrying the verification success information of the router BFR responds to the echo reply message, where the BIER-TE echo reply message carries the downstream mapping downstream mapping TLV information and the forwarding equivalence class stack change type length value FEC Stack
  • the TTL of the to-be-transmitted OAM detection message is set according to the downlink mapping TLV information, and the target FEC in the echo request carried in the BIER-TE response request carried in the to-be-transmitted OAM detection message is popped according to the FEC Stack Change TLV. Corresponding AFECency corresponding FEC in the Stack TLV; sending the to-be-transmitted OAM detection message to the BFIR.
  • An embodiment of the present invention provides a fault detection apparatus, including:
  • a receiving module configured to receive an operation management and maintenance OAM detection message from the controller for requesting detection of a traffic index extension based bit index display copy BIER-TE path;
  • An embodiment of the present invention provides a fault detection apparatus, including:
  • a sending module configured to send, to the bit forwarding ingress router BFIR, an operation management and maintenance OAM detection message for requesting detection of a traffic index extension based bit index display copy BIER-TE path, wherein the OAM detection message is used to indicate the The BFIE performs fault detection on the BIER-TE path according to the OAM detection message.
  • an operation management and maintenance OAM detection message for receiving a BIER-TE path is displayed by using a bit index for requesting detection of a traffic engineering extension based on a traffic engineering extension; and the BIER-TE is performed according to the OAM detection message.
  • the path is fault detected.
  • Path detection in BIER-TE is implemented to ensure reliable transmission of packets in BIER-TE.
  • FIG. 1 is a network diagram of a BIER-TE in the related art
  • FIG. 2 is a flowchart of a first fault detection method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a second fault detection method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a format of an OAM message for detecting a BIER-TE path according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of an Echo Request or a Reply header format according to an embodiment of the present invention.
  • FIG. 6 is a format diagram of an Original bitstring TLV according to an embodiment of the present invention.
  • Target bitstring TLV is a format diagram of a Target bitstring TLV according to an embodiment of the present invention.
  • FIG. 8 is a format diagram of a Downstream Mapping TLV according to an embodiment of the present invention.
  • FIG. 9 is a format diagram of a BIER-TE forward_connected TLV according to an embodiment of the present invention.
  • FIG. 10 is a format diagram of a BIER-TE local_decap TLV according to an embodiment of the present invention.
  • FIG. 11 is a format diagram of a BIER-TE forward_routed TLV according to an embodiment of the present invention.
  • FIG. 12 is another format diagram of a BIER-TE forward_routed TLV according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of fault detection according to a first embodiment of the present invention.
  • FIG. 14 is a schematic diagram 1 of fault detection according to a second embodiment of the present invention.
  • 15 is a second schematic diagram of fault detection according to a second embodiment of the present invention.
  • 16 is a schematic diagram 3 of fault detection according to a second embodiment of the present invention.
  • 17 is a schematic diagram 4 of fault detection according to a second embodiment of the present invention.
  • FIG. 18 is a schematic diagram 1 of fault detection according to a third embodiment of the present invention.
  • FIG. 19 is a second schematic diagram of fault detection according to a third embodiment of the present invention.
  • 21 is a structural block diagram of a first fault detecting apparatus according to an embodiment of the present invention.
  • Figure 22 is a block diagram showing the structure of a second type of fault detecting apparatus according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a first fault detection method according to an embodiment of the present invention. As shown in FIG. 2, the flow includes the following steps:
  • Step S202 receiving an operation management and maintenance (OAM) detection message from the controller for requesting detection of the BIER-TE path;
  • OAM operation management and maintenance
  • Step S204 Perform fault detection on the BIER-TE path according to the foregoing OAM detection message.
  • the above steps may be a bit forwarding router (Bit-Forwarding Ingress) Router, referred to as BFIR), can also be BFER, or it can be other BFR.
  • BFIR Bit Forwarding Router
  • the method for detecting the OAM detection message sent by the controller for detecting the BIER-TE path may be received, and then the detection of the BIER-TE path may be completed according to the OAM detection message, and the path detection in the BIER-TE is implemented. To ensure reliable transmission of messages in BIER-TE.
  • receiving the OAM detection message from the controller for requesting detection of the BIER-TE path comprises receiving the OAM detection message by using a path for receiving the BIER-TE data message. That is, in this embodiment, the OAM detection message and the BIER data plane can go the same path without adding other paths for transmitting the OAM detection message, thereby saving resources.
  • performing fault detection on the BIER-TE path according to the OAM detection message includes :
  • the BFIR or the BFR forwards the OAM detection message to the BFER corresponding to the BFER information according to the bit forwarding egress router BFER information carried in the OAM detection message, where the OAM detection message is used to instruct the BFER to perform the verification of the BIER-TE path fault detection. And feed back the verification result to the controller.
  • the BIER-TE path transmission request message is mainly verified by the initiating node (corresponding to the above-mentioned controller), and the uplink processing is performed at the egress node (corresponding to the above-mentioned BFER).
  • the outbound node verification needs to verify the forwarding equivalence class (FEC), and responds to the initiating node with a response response message, thereby implementing fault detection of the BIER-TE path.
  • FEC forwarding equivalence class
  • BFER exit information (corresponding to the BFER information described above) may be formulated in the BIER request message to control which BFER nodes reply.
  • the BFIR or the BFR detects the BIER-TE path according to the Time To Live (TTL) of the OAM detection message, where:
  • BFIR or BFR uses OAM to detect messages to BIER-TE.
  • the path performs verification of the fault detection and feeds back the verification result to the controller;
  • the BFIR or BFR forwards the OAM detection message to the (M-1) hop node after the BFIR or BFR, and the OAM detection message is used to indicate the BFIR or the BFR (M) -1)
  • the hop node uses the OAM detection message to verify the fault detection of the BIER-TE path and feed back the verification result to the controller.
  • the TTL may be carried in a BIER-MPLS (Multi-Protocol Label Switching) tag (Lable) in the OAM detection message sent by the controller, and the OAM detection message sent by the controller is The TTL can be incremented from 1 to achieve accurate location of the fault.
  • the return code is "Replying router is the only BFER in BIER header Bitstring" (the reply router is the only BFER in the BIER header string) "You can stop sending an echo request.”
  • the controller may include an exit BFER information in the echo request to control which BFERs are to be traced.
  • the condition that the receiving device ie, the above-mentioned BFIR, BFER or BFR) sends the detection result to the controller includes at least one of the following: the receiving device is a BFER, and the TTL in the BIER-MPLS Lable times out.
  • receiving the OAM detection message from the controller includes: the BFER receiving bit forwarding ingress router BFIR or the bit forwarding router BFR forwarding from The OAM detection message of the controller; performing fault detection on the BIER-TE path according to the OAM detection message includes: the BFER uses the OAM detection message to perform verification of the fault detection on the BIER-TE path, and feeds back the verification result to the controller.
  • the OAM detection message that the BFER receives the BFIR or BFR forwarding may also be received under the PING technique or the traceroute technology described above.
  • the BFER uses the OAM detection message to verify the fault detection of the BIER-TE path
  • Feedback verification results to the controller include:
  • the BFER will use the bit string (BitString) in the BIER-TE header carried in the OAM detection message and the BIER-TE local decapsulation type length value in the BIER-TE response request (echo request) carried in the OAM detection message.
  • BitString bit string
  • BIER-TE local decapsulation type length value in the BIER-TE response request (echo request) carried in the OAM detection message.
  • the verification fails, and the portable school is sent to the controller.
  • the BIER-TE response of the failure message responds to the echo reply.
  • the BFER when the BIER-TE path is detected by the traceroute technology, when the BFER is performed by the check operation, the BFER performs the check of the fault detection of the BIER-TE path by using the OAM detection message.
  • feedback verification results to the controller include:
  • the BFER compares the bit string BitString in the BIER-TE header header carried in the OAM detection message with the destination bit string type length value Target SI-BitString TLV in the BIER-TE response request echo request carried in the OAM detection message;
  • the bearer When it is determined that the BitString in the BIER-TE header does not match the egress bit string-type length value Egress BitString Sub-TLV in the downstream mapping downstream mappingTLV carried in the BIER-TE echo request, the bearer carries the egress bit string-type Length value Egress BitString Sub-TLV mismatch information BIER-TE response response echo reply;
  • the BIER-TE response echo echo carrying the mismatch entry is sent to the controller;
  • the controller is sent with a "Replying router is one of the BFER in BIER header Bitstring".
  • a BFER) message BIER-TE response echo reply if there is no other BFER local_decap adjacency index in the Target SI-BitString TLV, send the message "Replying router is the only BFER in BIER header Bitstring" to the controller. Is the only BFER in the BIER header string.”
  • the BIER-TE response of the message responds to the echo reply;
  • the BFER sends a BIER-TE response echo reply carrying the "Replying BFR is not in the path to any target BFER" message to the controller.
  • the BFIR or the BFR performs the fault detection on the BIER-TE path by using the OAM detection message.
  • Checking and feeding back the check result to the controller includes: BFIR or BFR according to the bit string BitString in the BIER-TE header of the OAM detection message and the BIER-TE response request in the OAM detection message in the echo request.
  • the destination forwarding equivalence class stack type length value is verified by the corresponding adjacency FEC in the Target FEC Stack TLV, and the verification result is fed back to the controller.
  • the order of each adjacency index in the BitString is consistent with the order of the corresponding FEC in the FEC stack.
  • the corresponding adjacency FEC in the Target FEC Stack TLV includes a forward connection forward_connected TLV and/or a forward route forward_routed TLV;
  • the BFIR or the BFR is based on the BitString in the BIER-TE header carried in the OAM detection message and the BIER-TE echo request carried in the OAM detection message.
  • the corresponding adjacency FEC in the Target FEC Stack TLV is verified, and the verification result is fed back to the controller, including:
  • the BFIR or the BFR is based on the BitString in the BIER-TE header carried in the OAM detection message and the Target FEC in the BIER-TE echo request carried in the OAM detection message.
  • the corresponding adjacency FEC in the Stack TLV is verified, and the verification result is fed back to the controller, including:
  • the verification succeeds and is sent to the controller.
  • the BIER-TE response carrying the verification success message responds to the echo reply; when the BFIR or BFR check out the BIER-TE forward_routed TLV, the prefix information is not prefixed, or the BFIR or BFR is the adjacency id assigned to the prefix and the corresponding bit in the BitString. If the indicated indexes are inconsistent, the verification fails, and the BIER-TE response with the verification failure information is sent to the controller to respond to the echo reply.
  • the BIER-TE echo reply when the BFIR or the BFR sends a BIER-TE response echo reply carrying the verification success information to the controller, the BIER-TE echo reply carries: downstream mapping downstream mapping TLV information, and , FEC Stack Change TLV;
  • the downstream mapping TLV information carries the downstream node address and the downstream interface address; the FEC Stack Change TLV is used to inform the controller to pop up the corresponding adjacency FEC in the Target FEC Stack TLV.
  • the adjacency FEC includes a corresponding forward_connected TLV or forward_routed TLV.
  • the BFIR or the BFR when the BIER-TE path is detected by the traceroute technology, when the check operation is performed as BFIR or BFR, the BFIR or the BFR performs the fault detection on the BIER-TE path by using the OAM detection message.
  • the checksum and the feedback result to the controller include: BFIR or BFR will be the bit in the BIER-TE header of the OAM detection message.
  • the string BitString is associated with the Target SI-BitString TLV in the BIER-TE response request echo request carried in the OAM detection message; when the phase and result are not 0, the BFIR or BFR performs the following operations: when determining the BIER-TE header outer package
  • the BIER-Label-L in the BIER-Multiprotocol Label Switching MPLS Label Lable is inconsistent with the label assigned by ⁇ sub-domain, BitStringLen, SI ⁇ given in the Original SI-BitString TLV in the BIER-TE echo request.
  • the controller sends a BIER-TE response echo check with the mismatch entry; when it is determined that there is no question Sending a BIER-TE response echo reply carrying packet forwarding success Packet-Forward-Success information to the controller; when the phase and result are 0, BFIR or BFR sends the message to the controller carrying "Replying BFR is not in the The BIER-TE response of the path to any target BFER message responds to the echo reply.
  • FIG. 3 is a flowchart of a second fault detection method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 sending, to the bit forwarding ingress router BFIR, an operation management and maintenance OAM detection message for requesting detection of the bit index display replication BIER-TE path based on the traffic engineering extension, wherein the OAM detection message is used to instruct the BFIE to use the OAM detection message. Fault detection of the BIER-TE path.
  • the above steps may be performed by the controller.
  • the method for detecting the OAM detection message of the BIER-TE path may be sent to the BFIR, and the BFIE is instructed to complete the detection of the BIER-TE path according to the OAM detection message, and the path detection in the BIER-TE is implemented, which ensures Reliable transmission of messages in BIER-TE.
  • sending an OAM detection message for requesting detection of the BIER-TE path to the BFIR includes: transmitting an OAM detection message for requesting detection of the BIER-TE path to the BFIR, where the OAM detection
  • the message carries a bit forwarding egress router BFER information, which is used to instruct the BFIR to forward the OAM detection message to the BFER corresponding to the BFER information according to the BFER information, where the OAM detection message is used to instruct the BFER to perform fault detection on the BIER-TE path. Verify and feedback the verification result;
  • the OAM detection message carrying the time-to-live TTL for requesting detection of the BIER-TE path is sent to the BFIR, where: when the value of the TTL is 1, the OAM detection message is used. Instructing the BFIR to perform the check for the fault detection of the BIER-TE path by using the OAM detection message; when the value of the TTL is greater than the value of M, the OAM detection message is used to indicate that the BFIR forwards the OAM detection message to the BFIR.
  • the OAM detection message is used to indicate that the (M-1) hop node after the BFIR performs the check of the fault detection of the BIER-TE path by using the OAM detection message, and feeds back the verification result.
  • the BIER-TE response request in the OAM detection message is in the echo request.
  • the purpose of forwarding the equivalence class stack type length value Target FEC Stack TLV is the forwarding equivalence class FEC corresponding to all adjacency adjacency in the bit string BitString, wherein the BitString is located in the BIER-TE header of the OAM detection message. in.
  • the method further includes: after transmitting the OAM detection message for requesting detection of the BIER-TE path to the BFIR, receiving the BFIR or the carrier forwarding of the BFR feedback after the BFIR on the path to be detected
  • the BIER-TE response of the success message is responsive to the echo reply message, wherein the BIER-TE echo reply message carries the downstream mapping downstream mapping TLV information and the forwarding equivalence class stack change type length value FEC Stack Change TLV; according to the downstream mapping TLV
  • the information sets the TTL of the OAM detection message to be sent, and the EAC detection message to be sent according to the FEC Stack Change TLV.
  • the BIER-TE responds to the corresponding adjacency corresponding FEC in the Target FEC Stack TLV in the echo request; and sends the above-mentioned OAM detection message to be sent to the BFIR.
  • FIG. 4 is a schematic diagram of an OAM message format for detecting a BIER-TE path according to an embodiment of the present invention.
  • the message type Message Type includes the following two types:
  • FIG. 5 is a schematic diagram of an Echo Request or a Reply header format according to an embodiment of the present invention, where
  • the TLV introduced in the embodiment of the present invention has a specific format as shown in FIG. 6 to FIG. 12.
  • the TLVs used in the specific embodiment 1 to the third embodiment include FIGS. 6 to 12, and the TLV used in the fourth embodiment only includes FIGS. 6 to 8.
  • a fault detection method based on traffic engineering extension bit index explicit replication is specifically introduced from a specific embodiment.
  • FIG. 1 depicts a BIER-TE networking diagram in the related art, in which all nodes in the BIER-TE domain are connected to a controller.
  • FIG. 13 is a schematic diagram of fault detection according to a first embodiment of the present invention, The embodiment will be described with reference to FIG. 13:
  • a fault detection method for bit index explicit replication based on traffic engineering extension which mainly utilizes PING technology, and the BIER-TE PING technology mainly passes the initiator node (ie, the controller in FIG. 13).
  • the BIER-TE path transmission request message is verified, and the uplink processing is performed at the out node (i.e., BFER1 and/or BFER2 in Fig. 13).
  • the outbound node verification needs to check the FEC and respond to the initiating node with a response response message to implement BIER-TE fault detection.
  • BIER-TE fault detection is initiated from the controller.
  • the message goes to the BFER1 and BFER2 nodes.
  • the specific process is as follows:
  • step S1301 the BIER-TE controller initiates a fault detection message to BFIR1.
  • the BIER-TE header and the BIER-TE echo request message are included, wherein the BIER-TE echo request is followed by the BIER-TE header, and the proto field in the BIER header is 5 to indicate that the BIER-TE OAM message is sent.
  • the outer layer of the BIER-TE header continues to encapsulate the BIER-MPLS Label.
  • the PIER mode of the BIER-MPLS Label is set to 255 in PING mode.
  • the BIER-TE local_decap TLV proposed in the embodiment of the present invention is encapsulated in the BIER-TE echo request. You can also include the Target SI-BitString TLV to control which BFERs are going to reply to reply.
  • BFIR1 receives the fault detection message initiated by the controller, and forwards the fault detection message according to the BIER-TE header, that is, forwards to the BFER1 and BFER2 nodes through BFR1 and BFR2.
  • step S1303 after receiving the fault detection message, the BFER1 and BFER2 nodes perform FEC check.
  • the format of the FEC is shown in the BIER-TE local_decap TLV format shown in FIG. 6, and the BFER (ie, the above BFER1 and/or BFER2) nodes check the BitString in the BIER-TE header and the BIER-TE local_decap TLV.
  • the verification is successful as follows:
  • the BFER1 node address is filled in the advertising node identifier received by the BFER1 node (the advertising node identifier is carried in the BIER-TE local_decap TLV), and the BFER1adjacency id is consistent with the index represented by the corresponding bit in the BitString.
  • the BFER2 node receives the advertising node identifier and fills in the BFER2 node address, and the BFER2adjacency id is consistent with the index represented by the corresponding bit in the BitString.
  • Step S1304 if the verification is successful, the BFER1 and BFER2 nodes respectively respond to a BIER-TE echo reply message to the controller.
  • step S1305 if the verification fails, the BFER1 and BFER2 nodes respectively respond to an echo reply message carrying the FEC check failure to the controller.
  • FIGS. 14-17 are schematic diagrams of fault detection according to a second embodiment of the present invention.
  • the traceroute mode in a pure BIER-TE network is mainly introduced.
  • the Return code is "Replying router is the only BFER in BIER header Bitstring”
  • the echo request is stopped.
  • the process includes the following steps:
  • the fault detection message includes a BIER-TE header and a BIER-TE echo request message, wherein the BIER-TE echo request is after the BIER-TE header, and the proto field in the BIER header is 5, indicating that the fault detection message is a BIER OAM message. .
  • the outer layer of the BIER header continues to encapsulate the BIER-MPLS Label.
  • the TTL of the BIER-MPLS Label is incremented during traceroute.
  • the BIER-TE echo request pushes the corresponding FEC of all adjacency in the BitString in the Target FEC Stack TLV.
  • the order of each adjacency index in the BitString is consistent with the order of the corresponding FEC in the FEC stack.
  • the verification success is as follows: the BIER-TE forward_connected TLV received by the BFIR1 node is filled in a direct link of BFIR1, and the adjacency id allocated by the BFIR1 for the direct link is the same as the index represented by the corresponding bit in the BitString. .
  • step S1403 if the verification is successful, BFIR1 responds to the BIER-TE echo reply message carrying the verification success information to the controller.
  • the BIER-TE echo reply message carries the downstream mapping TLV to the controller.
  • the downstream mapping TLV carries the downstream node address and the downstream interface address.
  • the FEC Stack Change TLV can also be included to notify the controller to pop the BIER-TE Target FEC Stack.
  • the corresponding forward_connected TLV in the TLV is the TLV.
  • step S1404 if the verification fails, BFIR1 responds to an echo reply message carrying the FEC check failure to the controller.
  • the verification success is as follows: the BIER-TE forward_connected TLV received by the BIR1 node is filled with a direct link of BFR1, and BFIR1 is the index of the adjacency id assigned to the directly connected link and the corresponding bit in the BitString. Consistent.
  • Step S1408 If the verification is successful, the BFR1 responds to the BIER-TE echo reply message carrying the verification success information to the controller.
  • the Echo Reply message carries the FEC Stack Change TLV, and the controller sends the corresponding forward_connected TLV in the BIER-TE Target FEC Stack TLV.
  • the BIER-TE Echo Reply message carries the downstream mapping TLV to the controller.
  • the downstream mapping TLV carries the downstream node. Address, and downstream interface address.
  • step S1409 if the verification fails, BFR2 responds to an echo reply message carrying the FEC check failure to the controller.
  • Step S1411 When the message passes through the BFIR1 and BFR1 nodes, the TTL is decremented by 1, and the message is forwarded to BFR2 according to the BIER header.
  • the verification success is as follows: the BIER-TE forward_connected TLV received by the BFR2 node is filled with a direct link of BFR2, and BFIR1 is the index of the adjacency id assigned to the directly connected link and the corresponding bit in the BitString. Consistent.
  • step S1413 if the verification is successful, the BFR2 responds to the BIER-TE echo reply message carrying the verification success information to the controller.
  • the Echo Reply message carries the FEC Stack Change TLV, and the controller forwards the corresponding forward_connected TLV in the BIER-TE Target FEC Stack TLV.
  • the BIER-TE Echo Reply message carries the downstream mapping TLV to the controller, and the downstream mapping TLV carries the downstream. Node address, and downstream interface address.
  • Step S1416 When the message passes the BFIR1, BFR1, and BFR2 nodes, the TTL is decremented by 1, and the message is forwarded to the BFER according to the BIER header.
  • the verification success is as follows: the BFER node receives the advertising node identifier and fills in the BFER node address, and the assigned adjacency id of the BFER node address is consistent with the index represented by the corresponding bit in the BitString.
  • step S1419 if the verification fails, the BFER responds to an echo reply message carrying the FEC check failure to the controller.
  • FIGS. 18-20 are schematic diagrams of fault detection according to a third embodiment of the present invention.
  • the traceroute mode in a pure BIER-TE network is mainly introduced.
  • the Return code is "Replying router is the only BFER in BIER header Bitstring”
  • the echo request is stopped.
  • the process includes the following steps:
  • Steps S1501-S1509 are the same as steps S1401-1409, and are not described here.
  • Step S1511 When the message passes through the BFIR1 and BFR1 nodes, the TTL is decremented by 1, and the message is forwarded to BFR2 according to the BIER header.
  • step S1512 when the packet arrives at the BFR2 node, the BFR2 node will not reply to the BIER-TE echo reply message due to the failure of the BFR2 node. After the controller waits for a specific time, the response message is not received, and the BFR1 and BFR2 are considered. The link between the links or the BFR2 node has failed.
  • the traceroute mode in a pure BIER-TE network is introduced.
  • an Original SI-BitString TLV and a Target SI-BitString TLV are introduced. As shown in FIG. 13, the process includes the following steps:
  • the fault detection message may include a BIER-TE header and a BIER-TE echo request message, where the BIER-TE echo request is after the BIER-TE header, and the proto field in the BIER-TE header is 5 to indicate that the BIER-TE OAM packet is .
  • the outer layer of the BIER-TE header continues to encapsulate the BIER-MPLS Label.
  • the TTL of the BIER-MPLS Label is incremented during traceroute.
  • the BIER-TE echo request can contain the Target SI-BitString TLV, which path to which BFER to trace, or some information about the downstream node and interface.
  • the reply message carries: Set-Identifier Mismatch.
  • the reply does not match the entry.
  • reply code5 Packet-Forward-Success to the controller.
  • step S1607 if the phase and the result are not 0, the BFR1 node needs to perform other checks.
  • the BIER-TE echo reply message carries the downstream mapping TLV to the controller.
  • the downstream mapping TLV carries the downstream node address and the downstream interface address.
  • the reply message carries: Set-Identifier Mismatch.
  • the reply does not match the entry.
  • reply code5 Packet-Forward-Success to the controller.
  • Step S1609 When the message passes through the BFIR1 and BFR1 nodes, the TTL is decremented by 1, and the message is forwarded to BFR2 according to the BIER header.
  • step S1611 if the phase and the result are not 0, the BFR2 node needs to perform other checks.
  • the reply message carries: Set-Identifier Mismatch.
  • the reply does not match the entry.
  • the message forwarding success message is sent to the controller.
  • Step S1613 When the message passes the BFIR1, BFR1, and BFR2 nodes, the TTL is decremented by 1, and the message is forwarded to the BFER according to the BIER header.
  • step S1615 if the phase and the result are not 0, the node needs to perform other checks.
  • the reply message carries: Set-Identifier Mismatch.
  • the reply does not match the entry.
  • step S1617 if the phase and the result are 0, "Code 10: Reply BFR is not in the path to any target BFER" is returned.
  • the technical solution of the present invention which is essential or contributes to the prior art, can be embodied in the form of a software product stored in a storage medium (such as a read only memory (ROM, Read). Only Memory) or Random Access Memory (RAM), including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the present invention
  • a storage medium such as a read only memory (ROM, Read). Only Memory) or Random Access Memory (RAM)
  • a fault detecting device is also provided, which is configured to implement the above-mentioned embodiments and optional embodiments, and has not been described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 21 is a structural block diagram of a first type of fault detecting apparatus according to an embodiment of the present invention, as shown in FIG.
  • the device includes a receiving module 212 and a detecting module 214, which are described below.
  • the receiving module 212 is configured to receive an operation management and maintenance OAM detection message from the controller for requesting detection of the bit index display based on the traffic engineering extension to display the duplicate BIER-TE path;
  • the detecting module 214 is connected to the receiving module 212 and configured to perform fault detection on the BIER-TE path according to the OAM detection message.
  • the receiving module 212 is configured to receive an OAM detection message by using a path for receiving a BIER-TE data message.
  • the detecting module 214 is configured to: forward the egress router BFER according to the bit carried in the OAM detection message.
  • the information is forwarded to the BFER corresponding to the BFER information, where the OAM detection message is used to instruct the BFER to perform verification of the fault detection of the BIER-TE path, and feed back the verification result to the controller; or, according to the OAM detection message
  • the TTL of the BIER-TE path is fault-detected. When the TTL value is 1, the OAM detection message is used to perform the check of the BIER-TE path for fault detection.
  • the M value is greater than 1.
  • the OAM detection message is forwarded to the (M-1) hop node after the BFIR or the BFR, and the OAM detection message is used to indicate that the (M-1) hop node after the BFIR or the BFR performs the BIER-TE using the OAM detection message.
  • the path performs verification of the fault detection and feeds back the verification result to the controller.
  • the receiving module 212 is configured to: receive the OAM from the controller forwarded by the bit forwarding ingress router BFIR or the bit forwarding router BFR
  • the detection module 214 is configured to perform verification of fault detection on the BIER-TE path by using the OAM detection message, and feed back the verification result to the controller.
  • the detecting module 214 is configured to perform the verification of the fault detection of the BIER-TE path in the following manner, and feed back the checksum to the controller. Result: Check the bit string BitString in the BIER-TE header of the OAM detection message and the BIER-TE local decapsulation type length value local_decap TLV in the BIER-TE response request echo request carried in the OAM detection message. When the BIER-TE local_decap TLV is verified, the advertising node identifier is carried.
  • the BFER address is filled in the identifier, and when the adjacency id of the BFER is consistent with the index indicated by the corresponding bit in the BitString, the verification succeeds, and the BIER-TE response echo reply carrying the verification success information is sent to the controller.
  • the controller sends a BIER-TE response with an authentication failure message to answer the echo reply.
  • the detecting module 214 is configured to perform the verification of the fault detection of the BIER-TE path in the following manner, and feed back the checksum to the controller.
  • Result the bit string BitString in the BIER-TE header header carried in the OAM detection message is matched with the destination bit string type length value Target SI-BitString TLV in the BIER-TE response request echo request carried in the OAM detection message;
  • the BFER performs the following operations: when determining the original bit string in the BIER-Label-L and BIER-TE echo request in the BIER-multiprotocol label switching MPLS label Lable encapsulated in the BIER-TE header Type length value Original SI-BitString When the label assigned by ⁇ sub-domain, BitStringLen, SI ⁇ is inconsistent, the BIER-TE response echo with the Set-Identifier Mismatch is sent to the controller.
  • the BIER-TE response echo reply carrying the unrecognized TLV is sent to the controller; when determining the BitString and BIER-TE echo req in the BIER-TE header When the egress bit string-type length value Egress BitString Sub-TLV in the downstream mapping downstream mapping carried in the uest does not match, the BIER-TE response echo reply carrying the mismatch information is sent to the controller; when the BFER does not match the BIFT table In the case of the item, the BIER-TE response echo reply carrying the mismatch entry is sent to the controller; when it is determined that there is no problem, if the Target SI-BitString TLV still has a local decapsulation of the BFER other than the exit BFER When the adjacency index is local_decap adjacency, a BIER-TE response echo echo carrying the message "Replying router is one of the BFER in BIER header Bitstring" is sent to the controller
  • the detecting module 214 is configured to perform verification of performing fault detection on the BIER-TE path in the following manner, and feedback to the controller. Verification result: according to the bit string BitString in the BIER-TE header of the OAM detection message and the BIER-TE response request in the OAM detection message, the destination forwarding equivalence class stack type length value Target FEC Stack The corresponding adjacency FEC in the TLV is verified and the verification result is fed back to the controller.
  • the order of each adjacency index in the BitString is consistent with the order of the corresponding FEC in the FEC stack.
  • the corresponding adjacency FEC in the Target FEC Stack TLV includes a forward connection forward_connected TLV and/or a forward route forward_routed TLV, wherein the corresponding adjacency FEC in the Target FEC Stack TLV includes a forward_connected TLV
  • a direct link of BFIR or BFR is filled in, and BFIR or BFR is the adjacency id assigned to the direct link and the index represented by the corresponding bit in the BitString. If the check is successful, the check succeeds.
  • the BIER-TE response echo echo with the check success information is sent to the controller.
  • the BFIR or BFR check out the BIER-TE forward_connected TLV, a direct link that is not BFIR or BFR is filled in. If the adjacency id assigned by the BFIR or BFR for the direct link is inconsistent with the index indicated by the corresponding bit in the BitString, the check fails, and the BIER-TE response with the check failure information is sent to the controller to respond to the echo reply;
  • the corresponding adjacency FEC in the FEC Stack TLV includes the forward_routed TLV, when the BFIR or BFR check out the BIER-TE forward_r
  • the outd TLV is filled with the prefix prefix information, and if the adjacency id assigned by the BFIR or BFR is the same as the index indicated by the corresponding bit in the BitString, the verification succeeds, and the BIER-TE response carrying the verification success information is sent to the controller.
  • the BFIR or BFR when the BFIR or BFR sends a verification success letter to the controller
  • the BIER-TE echo response carries the downstream mapping downstream mapping TLV information and the FEC Stack Change TLV, where the downstream mapping TLV information carries the downstream node address and the downstream interface. Address; FEC Stack Change TLV is used to tell the controller to pop up the corresponding adjacency FEC in the Target FEC Stack TLV.
  • the detecting module 214 is configured to perform verification of performing fault detection on the BIER-TE path in the following manner, and feedback to the controller.
  • BFIR or BFR performs the following operations: when determining the BIER-Label-L in the BIER-Multiprotocol Label Switching MPLS Label Lable of the BIER-TE header and the Original SI in the BIER-TE echo request The label assigned by ⁇ sub-domain, BitStringLen, SI ⁇ given in the -BitString TLV is inconsistent, and the BIER-TE response echo echo carrying the Set-Identifier Mismatch is sent to the controller; when it is determined that the BIER-TE echo request is not recognized The TLV sends
  • the bearer mismatch is sent to the controller.
  • the BIER-TE response of the entry responds to the echo reply; when it is determined that there is no problem, the BIER-TE response echo reply carrying the packet-forward-Success message is sent to the controller; when the phase and result are 0,
  • the BFIR or BFR sends a BIER-TE response acknowledgment echo reply carrying the "Replying BFR is not in the path to any target BFER" message to the controller.
  • FIG. 22 is a structural block diagram of a second type of fault detecting apparatus according to an embodiment of the present invention. As shown in FIG. 22, the apparatus includes a transmitting module 222, which is described below:
  • the sending module 222 is configured to send, to the bit forwarding ingress router BFIR, an operation management and maintenance OAM detection message for requesting detection of the bit index display replication BIER-TE path based on the traffic engineering extension, wherein the OAM detection message is used to indicate that the BFIE uses the OAM Detect message to BIER-TE The path is fault detected.
  • the sending module 222 is configured to: send an OAM detection message for requesting detection of a BIER-TE path to the BFIR, where the OAM detection message carries a bit forwarding egress router BFER information, and the BFER information is used.
  • the BFIR forwards the OAM detection message to the BFER corresponding to the BFER information according to the BFER information, and the OAM detection message is used to instruct the BFER to perform the verification of the fault detection of the BIER-TE path, and feed back the verification result; or, send the BFIR to the BFIR for The request for detecting the OAM detection message carrying the TTL of the BIER-TE path, wherein: when the value of the TTL is 1, the OAM detection message is used to instruct the BFIR to perform the verification of the fault detection of the BIER-TE path by using the OAM detection message.
  • the OAM detection message is used to indicate that the BFIR forwards the OAM detection message to the M-1 hop node after the BFIR, and the OAM detection message is used to indicate the M-1 hop after the BFIR.
  • the node performs the verification of the fault detection of the BIER-TE path by using the OAM detection message, and feeds back the verification result.
  • the BIER-TE response carried in the OAM detection message requests the destination forwarding in the echo request.
  • Equivalent class stack type length value Target FEC Stack TLV pushes the forwarding equivalence class FEC corresponding to all adjacency adjacency in the bit string BitString, where BitString is located in the BIER-TE header of the OAM detection message.
  • the apparatus further includes a processing module configured to receive the BFIR or the bit forwarding router BFR after the BFIR on the path to be detected after transmitting the OAM detection message for requesting detection of the BIER-TE path to the BFIR.
  • the BIER-TE response carrying the verification success information is echoed by the echo reply message, wherein the BIER-TE echo reply message carries the downstream mapping downstream mapping TLV information and the forwarding equivalence class stack change type length value FEC Stack Change TLV;
  • the downstream mapping TLV information sets the TTL of the OAM detection message to be sent, and the corresponding adjacency corresponding FEC in the Target FEC Stack TLV in the echo request in the BIER-TE response request carried in the FEC Stack Change TLV pop-up OAM detection message. Sending an OAM detection message to be sent to the BFIR.
  • each of the foregoing modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • S2 Perform fault detection on the BIER-TE path according to the foregoing OAM detection message.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the bit forwarding forwarding ingress router BFIR sends an operation management and maintenance OAM detection message for requesting detection of the bit index display based on the traffic engineering extension to display the replication BIER-TE path, where the OAM detection message is used to instruct the BFIE to use the OAM detection message pair.
  • the BIER-TE path performs fault detection.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • One or more media that can store program code such as a hard disk, a disk, or a disk.
  • the processor executes the steps in each of the foregoing method embodiments according to the stored program code in the storage medium.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program in a storage and a memory by a processor. / instruction to achieve its corresponding function.
  • the invention is not limited to any particular form of hardware and software. Hehe.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above technical solution implements path detection in BIER-TE, and ensures reliable transmission of packets in BIER-TE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种故障检测方法及装置，其中，该方法包括：接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的OAM检测消息；根据上述OAM检测消息对BIER-TE路径进行故障检测。

Description

故障检测方法及装置 技术领域
本文涉及但不限于通信领域，尤指一种故障检测方法及装置。
背景技术
随着软件定义网络(Software Defined Network，简称为SDN)技术和网络功能虚拟化(Network Function Virtualization，简称为NFV)在这些年的迅速发展，网络的部署可控性越来越强，控制复杂度也随之越来越高。尤其是像核心网络以及汇聚网络这样的中间网络，为了适配不同的业务，满足不同的部署需求，控制手段越来越繁杂。尤其是组播应用如多播虚拟专用网(Multicast Virtual Private Network，简称为MVPN)和交互式网络电视(Internet Protocol Television，简称为IPTV)等，需要的中间网络节点状态数量指数级增长。
为此，业界提出了一种新的用于构建组播转发路径的技术，称为具有位索引的显式复制(Bit Indexed Explicit Replication，简称为BIER)技术。BIER技术，通过对转发层面的彻底改造，能极大的减轻中间网络的协议复杂度和中间状态。将网络的转发简化成只根据比特(bit)位进行，颠覆了传统的互联网协议(Internet Protocol，简称为IP)转发，能够非常容易的实现组播流量在中间网络的传输，无需中间网络记录任何的组播流量状态，极大的方便了网络的运维。
BIER技术是基于bit位的组播复制技术，在BIER域中，给每台位转发出口路由器(Bit-Forwarding Egress Routers，简称为BFER)分配一个在整个BIER子域(sub-domain)中全局唯一的比特位置(bit position)，每台BFER将自己的bit position使用内部网关协议(Interior Gateway Protocol，简称为IGP)在BIER domain(域)中泛洪，所有的bit position组成一个位串(bitstring)，数据报文在BIER域中的传递和路由依赖于bitstring。当其他位转发路由器(Bit Forwarding Router，简称为BFR)收到了包含有BIER的报文头时，根据BIER报文头中携带的bitstring基于位转发表(Bit Forwarding Table)进行转发。这种基于BIER bit(位)进行转发的原理大大减少了网络的转发成本。
图1是相关技术中的BIER-TE组网图，其中，该基于流量工程扩展的位索引显式复制(Bit Index Explicit Replication-Traffic Enginering，简称为BIER-TE)与BIER类似，根据报文头中的BitString转发和复制报文，但是BIER-TE与BIER的关键区别如下：
1)使用BIER-TE控制器计算的显式路径替代网络内的自动路径计算。
2)BitString中的每个bit position表示一个或多个邻接体(adjacency)，而不是表示一个BFER。
3)BFR上只需要有BIER-TE转发表Forwarding Table(BIFT)，不需要有路由表。
但是目前对于BIER-TE并没有相关的路径检测技术。针对相关技术中存在的无法实现BIER-TE中的路径检测的问题，目前尚未提出有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种故障检测方法及装置，能够实现BIER-TE中的路径检测。
本发明实施例提供了一种故障检测方法，包括：接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
可选地，接收来自所述控制器的用于请求检测所述BIER-TE路径的所述OAM检测消息包括：通过用于接收BIER-TE数据报文的路径接收所述OAM检测消息。
可选地，当接收所述OAM检测消息的节点为位转发入口路由器BFIR或位转发路由器BFR时，根据所述OAM检测消息对所述BIER-TE路径进行故障检测包括：所述BFIR或BFR根据所述OAM检测消息中携带的位转发出口路由器BFER信息将所述OAM检测消息转发给所述BFER信息对应的BFER，其中，所述OAM检测消息用于指示所述BFER执行对所述BIER-TE 路径进行故障检测的校验，并向所述控制器反馈校验结果；或者，所述BFIR或BFR根据所述OAM检测消息的生存时间TTL对所述BIER-TE路径进行故障检测，其中：当所述TTL的值为1时，所述BFIR或BFR使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果；当所述TTL的值为大于1的M值时，所述BFIR或BFR将所述OAM检测消息转发给所述BFIR或BFR后的第(M-1)跳节点，所述OAM检测消息用于指示所述BFIR或BFR后的第(M-1)跳节点使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果。
可选地，当接收所述OAM检测消息的节点为位转发出口路由器BFER时，接收来自所述控制器的所述OAM检测消息包括：所述BFER接收位转发入口路由器BFIR或位转发路由器BFR转发的来自所述控制器的所述OAM检测消息；根据所述OAM检测消息对所述BIER-TE路径进行故障检测包括：所述BFER使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果。
可选地，当执行校验操作的为BFER时，所述BFER使用OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：所述BFER将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的BIER-TE本地解封装类型长度值local_decap TLV相校验；当所述BFER校验出所述BIER-TE local_decap TLV中携带的通告节点标识advertising node identifier中填写的是所述BFER地址，并且所述BFER的邻接体标识adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply；
当BFER校验出BIER-TE local_decap TLV中携带的advertising node identifier中填写的不是所述BFER地址，或BFER的adjacency id与所述BitString中相应的bit表示的索引不一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
可选地，当执行校验操作的为BFER时，所述BFER使用OAM检测消 息执行对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：所述BFER将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的目的位串类型长度值Target SI-BitString TLV相与；当相与结果不为0时，所述BFER执行如下操作：当确定所述BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与所述BIER-TE echo request中的原始位串类型长度值Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致时，向所述控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；当确定所述BIER-TE echo request中存在不识别的TLV时，向所述控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；当确定所述BIER-TE header中的BitString与所述BIER-TE echo request中携带的下游映射downstream MappingTLV中的出口位串子-类型长度值Egress BitString Sub-TLV不匹配时，向所述控制器发送携带不匹配信息的BIER-TE响应应答echo reply；当所述BFER没有匹配到BIFT表项时，向所述控制器发送携带不匹配表项的BIER-TE响应应答echo reply；当确定不存在任何问题时，若所述Target SI-BitString TLV中还存在除所述出口BFER之外的其他BFER的本地解封装邻接体local_decap adjacency索引时，向所述控制器发送携带"Replying router is one of the BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；若所述Target SI-BitString TLV中不存在其他BFER的local_decap adjacency索引时，向所述控制器发送携带"Replying router is the only BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；当相与结果为0时，所述BFER向所述控制器发送携带“Replying BFR is not in the path to any target BFER”信息的BIER-TE响应应答echo reply。
可选地，当执行校验操作的为BFIR或BFR时，所述BFIR或BFR使用OAM检测消息执行对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：所述BFIR或BFR根据所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中的相应的邻接体adjacency FEC进行校验，并向所述 控制器反馈校验结果。
可选地，每一个adjacency索引在所述BitString中的前后顺序与相应的FEC在FEC栈中的前后顺序保持一致。
可选地，所述Target FEC Stack TLV中的相应的adjacency FEC包括前向连接forward_connected TLV和/或前向路由forward_routed TLV，其中，当所述Target FEC Stack TLV中的相应的adjacency FEC包括所述forward_connected TLV时，所述BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：当所述BFIR或BFR校验出所述BIER-TE forward_connected TLV中填写的是所述BFIR或BFR的一条直连链路，并且所述BFIR或BFR为所述直连链路分配的adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply，；当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的不是BFIR或BFR的一条直连链路，或者BFIR或BFR为所述直连链路分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply；当所述Target FEC Stack TLV中的相应的adjacency FEC包括所述forward_routed TLV时，所述BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：当所述BFIR或BFR校验出所述BIER-TE forward_routed TLV中填写的是前缀prefix信息，并且所述BFIR或BFR为所述prefix分配的adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply；当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的不是前缀prefix信息，或者BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
可选地，当所述BFIR或BFR向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply时，所述BIER-TE echo reply中还携带有：下游映射downstream Mapping TLV信息，以及，FEC Stack Change TLV；其中，所述downstream Mapping TLV信息中携带下游节点地址，及下游接口地址；所述FEC Stack Change TLV用于告知所述控制器弹出所述Target FEC Stack TLV中的相应的adjacency FEC。
可选地，当执行校验操作的为BFIR或BFR时，所述BFIR或BFR使用OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：BFIR或BFR将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的Target SI-BitString TLV相与；当相与结果不为0时，所述BFIR或BFR执行如下操作：当确定所述BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与所述BIER-TE echo request中的Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，向所述控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；当确定所述BIER-TE echo request中存在不识别的TLV时，向所述控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；当确定所述BIER-TE header中的BitString与所述BIER-TE echo request中携带的下游映射downstream Mapping TLV中的Egress BitString Sub-TLV不匹配时，向所述控制器发送携带不匹配信息的BIER-TE响应应答echo reply；当所述BFIR或BFR没有匹配到BIFT表项时，向所述控制器发送携带不匹配表项的BIER-TE响应应答echo reply；当确定不存在任何问题时，向所述控制器发送携带包转发成功Packet-Forward-Success信息的BIER-TE响应应答echo reply；当相与结果为0时，所述BFIR或BFR向所述控制器发送携带“Replying BFR is not in the path to any target BFER”信息的BIER-TE响应应答echo reply。
本发明实施例还提供了一种故障检测方法，包括：向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，所述OAM检测消息用于指示所 述BFIE根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
可选地，向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息包括：向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息，其中，所述OAM检测消息中携带位转发出口路由器BFER信息，所述BFER信息用于指示所述BFIR根据所述BFER信息将所述OAM检测消息转发给所述BFER信息对应的BFER，所述OAM检测消息用于指示所述BFER执行对所述BIER-TE路径进行故障检测的校验，并反馈校验结果；或者，向所述BFIR发送用于请求检测所述BIER-TE路径的携带有生存时间TTL的所述OAM检测消息，其中：当所述TTL的值为1时，所述OAM检测消息用于指示所述BFIR根据所述OAM检测消息执行对所述BIER-TE路径进行故障检测的校验；当所述TTL的值为大于1的M值时，所述OAM检测消息用于指示所述BFIR将所述OAM检测消息转发给所述BFIR后的第(M-1)跳节点，所述OAM检测消息用于指示所述BFIR后的第(M-1)跳节点根据所述OAM检测消息执行对所述BIER-TE路径进行故障检测的校验，并反馈校验结果。
可选地，当向所述BFIR发送用于请求检测所述BIER-TE路径的携带有生存时间TTL的所述OAM检测消息时，所述OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中压入与位串BitString中所有邻接体adjacency相应的转发等价类FEC，其中，所述BitString位于所述OAM检测消息中携带的BIER-TE数据头header中。
可选地，所述方法还包括：在向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息之后，接收所述BFIR或待检测路径上所述BFIR后的位转发路由器BFR反馈的携带校验成功信息的BIER-TE响应应答echo reply消息，其中，所述BIER-TE echo reply消息中携带有下游映射downstream Mapping TLV信息以及转发等价类堆栈变更类型长度值FEC Stack Change TLV；根据所述downstream Mapping TLV信息设置待发送OAM检测消息的TTL，以及，根据所述FEC Stack Change TLV弹出所述待发送OAM检测消息中携带的BIER-TE响应请求echo request中的Target FEC  Stack TLV中的相应的adjacency相应的FEC；向所述BFIR发送所述待发送OAM检测消息。
本发明实施例提供了一种故障检测装置，包括：
接收模块，设置为接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；
检测模块，设置为根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
本发明实施例提供了一种故障检测装置，包括：
发送模块，设置为向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，所述OAM检测消息用于指示所述BFIE根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
通过本发明实施例，采用接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；根据所述OAM检测消息对所述BIER-TE路径进行故障检测。实现了BIER-TE中的路径检测，保证了BIER-TE中的报文的可靠传输。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是相关技术中的BIER-TE组网图；
图2是本发明实施例的第一种故障检测方法的流程图；
图3是本发明实施例的第二种故障检测方法的流程图；
图4是本发明实施例的用于检测BIER-TE路径的OAM消息格式示意图；
图5是本发明实施例的Echo Request或Reply header format示意图；
图6是本发明实施例的Original bitstring TLV的格式图；
图7是本发明实施例的Target bitstring TLV的格式图；
图8是本发明实施例的Downstream Mapping TLV的格式图；
图9是本发明实施例的BIER-TE forward_connected TLV的格式图；
图10是本发明实施例的BIER-TE local_decap TLV的格式图；
图11是本发明实施例的BIER-TE forward_routed TLV的一种格式图；
图12是本发明实施例的BIER-TE forward_routed TLV的另外一种格式图；
图13是本发明具体实施例一的故障检测示意图；
图14是本发明具体实施例二的故障检测示意图一；
图15是本发明具体实施例二的故障检测示意图二；
图16是本发明具体实施例二的故障检测示意图三；
图17是本发明具体实施例二的故障检测示意图四；
图18是本发明具体实施例三的故障检测示意图一；
图19是本发明具体实施例三的故障检测示意图二；
图20是本发明具体实施例三的故障检测示意图三；
图21是本发明实施例的第一种故障检测装置的结构框图；
图22是本发明实施例的第二种故障检测装置的结构框图。
本发明的实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种故障检测方法，图2是本发明实施例的第一种故障检测方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，接收来自控制器的用于请求检测BIER-TE路径的运行管理和维护(Operation Administration and Maintenance，简称为OAM)检测消息；
步骤S204，根据上述OAM检测消息对BIER-TE路径进行故障检测。
其中，执行上述步骤的可以是位转发入口路由器(Bit-Forwarding Ingress  Router，简称为BFIR)，也可以是BFER，还可以是其他的BFR。
通过上述步骤，可以通过接收控制器发送的用于检测BIER-TE路径的OAM检测消息的方式，进而可以根据该OAM检测消息完成对BIER-TE路径的检测，实现了BIER-TE中的路径检测，保证了BIER-TE中的报文的可靠传输。
在一个可选的实施例中，接收来自上述控制器的用于请求检测BIER-TE路径的OAM检测消息包括：通过用于接收BIER-TE数据报文的路径接收上述OAM检测消息。即，在该实施例中，OAM检测消息与BIER数据面可以走相同的路径，无需增加其他的传输OAM检测消息的路径，从而节省了资源。
在一个可选的实施例中，在对BIER-TE路径进行故障检测时，有两种检测方案，一种是基于PING技术进行检测，一种是基于traceroute技术进行检测，下面分别对两种检测技术进行说明：
当采用的是PING技术对BIER-TE路径进行检测时，当接收上述OAM检测消息的节点为位转发入口路由器BFIR或位转发路由器BFR时，根据该OAM检测消息对BIER-TE路径进行故障检测包括：
BFIR或BFR根据OAM检测消息中携带的位转发出口路由器BFER信息将OAM检测消息转发给BFER信息对应的BFER，其中，该OAM检测消息用于指示BFER执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果。由此可知，BIER-TE PING技术中主要是通过发起节点(对应于上述的控制器)验证BIER-TE路径发送请求消息，在出节点(对应于上述的BFER)进行上送处理。出节点验证需要校验转发等价类(Forwarding Equivalence Class，简称FEC)，向发起节点回应响应应答消息，从而实现BIER-TE路径的故障检测。可选地，可以在BIER请求消息中制定BFER出口信息(对应于上述的BFER信息)，来控制哪些BFER节点回复(reply)。
当采用的是traceroute技术对路径进行检测时，BFIR或BFR根据OAM检测消息的生存时间(Time To Live，简称为TTL)对BIER-TE路径进行故障检测，其中：
当TTL的值为1时，BFIR或BFR使用OAM检测消息对BIER-TE路 径进行故障检测的校验，并向控制器反馈校验结果；
当TTL的值为大于1的M值时，BFIR或BFR将OAM检测消息转发给BFIR或BFR后的第(M-1)跳节点，该OAM检测消息用于指示BFIR或BFR后的第(M-1)跳节点使用OAM检测消息对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果。
在该实施例中，TTL可以携带在控制器发出的OAM检测消息中的BIER-MPLS(多协议标签交换，Multi-Protocol Label Switching)标签(Lable)中，且控制器发出的OAM检测消息中的TTL可以从1开始递增，实现对故障的准确定位。在该实施例中，当控制器收到所有BFER的reply回复的返回码(Return code)均为"Replying router is the only BFER in BIER header Bitstring(回复路由器是BIER头位串中的唯一一个BFER)"时可以停止发送响应请求(echo request)。可选地，控制器可以在echo request中包含出口BFER信息，以控制向哪些BFER做路径追踪(trace)。其中，接收设备(即，上述的BFIR、BFER或者BFR)将检测结果上送给控制器的条件包括以下至少之一：接收设备是BFER，BIER-MPLS Lable中的TTL超时。
在一个可选的实施例中，当接收上述OAM检测消息的节点为位转发出口路由器BFER时，接收来自控制器的OAM检测消息包括：BFER接收位转发入口路由器BFIR或位转发路由器BFR转发的来自控制器的OAM检测消息；根据该OAM检测消息对BIER-TE路径进行故障检测包括：BFER使用OAM检测消息对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果。在该实施例中，BFER接收BFIR或BFR转发的OAM检测消息也可以是在采用上述的PING技术或traceroute技术下接收的。
在一个可选的实施例中，在采用PING技术对BIER-TE路径进行检测时，当执行校验操作的为BFER时，BFER使用OAM检测消息对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果包括：
BFER将OAM检测消息中携带的BIER-TE数据头(header)中的位串(BitString)与OAM检测消息中携带的BIER-TE响应请求(echo request)中的BIER-TE本地解封装类型长度值local_decap TLV相校验；
当BFER校验出BIER-TE local_decap TLV中携带的通告节点标识 advertising node identifier中填写的是BFER地址，并且BFER的邻接体标识adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply；
当BFER校验出BIER-TE local_decap TLV中携带的advertising node identifier中填写的不是BFER地址，或BFER的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，在采用traceroute技术对BIER-TE路径进行检测时，当执行校验操作的为BFER时，BFER使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果包括：
BFER将OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的目的位串类型长度值Target SI-BitString TLV相与；
当相与结果不为0时，BFER执行如下操作：
当确定BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L(即标签L)与BIER-TE echo request中的原始位串类型长度值Original SI-BitString TLV中给出的{子域(sub-domain),位串(BitStringLen),SI(集标识)}分配的标签不一致时，向控制器发送携带集标识不匹配(Set-Identifier Mismatch)的BIER-TE响应应答echo reply；
当确定BIER-TE echo request中存在不识别的TLV时，向控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；
当确定BIER-TE header中的BitString与BIER-TE echo request中携带的下游映射downstream MappingTLV中的出口位串子-类型长度值Egress BitString Sub-TLV不匹配时，向控制器发送携带出口位串子-类型长度值Egress BitString Sub-TLV不匹配信息的BIER-TE响应应答echo reply；
当BFER没有匹配到BIFT表项时，向控制器发送携带不匹配表项的BIER-TE响应应答echo reply；
当确定不存在上述任何不匹配的问题时，若Target SI-BitString TLV中还 存在除所述出口BFER之外的其他BFER的本地解封装邻接体local_decap adjacency索引时，向控制器发送携带"Replying router is one of the BFER in BIER header Bitstring(回复路由器是BIER头位串中的其中一个BFER)"信息的BIER-TE响应应答echo reply；若Target SI-BitString TLV中不存在其他BFER的local_decap adjacency索引时，向控制器发送携带"Replying router is the only BFER in BIER header Bitstring(回复路由器是BIER头位串中的唯一一个BFER)"信息的BIER-TE响应应答echo reply；
当相与结果为0时，BFER向所述控制器发送携带“Replying BFR is not in the path to any target BFER(回复BFR不在任何目标BFER路径上)”信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，在采用PING技术对BIER-TE路径进行检测时，当执行校验操作的为BFIR或BFR时，BFIR或BFR使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果包括：BFIR或BFR根据OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中的相应的邻接体adjacency FEC进行校验，并向控制器反馈校验结果。
在一个可选的实施例中，每一个adjacency索引在BitString中的前后顺序与相应的FEC在FEC栈中的前后顺序保持一致。
在一个可选的实施例中，上述Target FEC Stack TLV中的相应的adjacency FEC包括前向连接forward_connected TLV和/或前向路由forward_routed TLV；
其中，当Target FEC Stack TLV中的相应的adjacency FEC包括上述forward_connected TLV时，BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：
当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的是BFIR或BFR的一条直连链路，并且BFIR或BFR为所述直连链路分配的 adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply；当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的不是BFIR或BFR的一条直连链路，或者BFIR或BFR为所述直连链路分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply；
当Target FEC Stack TLV中的相应的adjacency FEC包括上述forward_routed TLV时，BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：
当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的是前缀prefix信息，并且BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply；当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的不是前缀prefix信息，或者BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，当BFIR或BFR向控制器发送携带校验成功信息的BIER-TE响应应答echo reply时，BIER-TE echo reply中还携带有：下游映射downstream Mapping TLV信息，以及，FEC Stack Change TLV；
其中，该downstream Mapping TLV信息中携带下游节点地址，及下游接口地址；FEC Stack Change TLV用于告知所述控制器弹出Target FEC Stack TLV中的相应的adjacency FEC。在该实施例中，adjacency FEC包括对应的forward_connected TLV或者forward_routed TLV。
在一个可选的实施例中，在采用traceroute技术对BIER-TE路径进行检测时，当执行校验操作的为BFIR或BFR时，BFIR或BFR使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果包括：BFIR或BFR将OAM检测消息中携带的BIER-TE数据头header中的位 串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的Target SI-BitString TLV相与；当相与结果不为0时，BFIR或BFR执行如下操作：当确定BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与BIER-TE echo request中的Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，向控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；当确定BIER-TE echo request中存在不识别的TLV时，向控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；当确定BIER-TE header中的BitString与所述BIER-TE echo request中携带的下游映射downstream Mapping TLV中的Egress BitString Sub-TLV不匹配时，向控制器发送携带不匹配信息的BIER-TE响应应答echo reply；当BFIR或BFR没有匹配到BIFT表项时，向控制器发送携带不匹配表项的BIER-TE响应应答echo reply；当确定不存在任何问题时，向控制器发送携带包转发成功Packet-Forward-Success信息的BIER-TE响应应答echo reply；当相与结果为0时，BFIR或BFR向所述控制器发送携带“Replying BFR is not in the path to any target BFER(回复BFR不在任何目标BFER路径上)”信息的BIER-TE响应应答echo reply。
在本实施例中还提供了一种故障检测方法，图3是本发明实施例的第二种故障检测方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，该OAM检测消息用于指示BFIE使用OAM检测消息对BIER-TE路径进行故障检测。
其中，执行上述步骤的可以是控制器。
通过上述步骤，可以向BFIR发送用于检测BIER-TE路径的OAM检测消息的方式，指示BFIE根据该OAM检测消息完成对BIER-TE路径的检测，实现了BIER-TE中的路径检测，保证了BIER-TE中的报文的可靠传输。
在一个可选的实施例中，在对BIER-TE路径进行故障检测时，有两种检测方案，一种是基于PING技术进行检测，一种是基于traceroute技术进行检测，下面分别对两种检测技术进行说明：
当采用的是PING技术对路径进行检测时，向BFIR发送用于请求检测BIER-TE路径的OAM检测消息包括：向BFIR发送用于请求检测BIER-TE路径的OAM检测消息，其中，该OAM检测消息中携带位转发出口路由器BFER信息，该BFER信息用于指示BFIR根据BFER信息将OAM检测消息转发给BFER信息对应的BFER，上述OAM检测消息用于指示BFER执行对BIER-TE路径进行故障检测的校验，并反馈校验结果；
当采用的是traceroute技术对路径进行检测时，向BFIR发送用于请求检测BIER-TE路径的携带有生存时间TTL的OAM检测消息，其中：当该TTL的值为1时，OAM检测消息用于指示BFIR使用OAM检测消息执行对BIER-TE路径进行故障检测的校验；当TTL的值为大于1的M值时，OAM检测消息用于指示BFIR将OAM检测消息转发给所述BFIR后的第(M-1)跳节点，OAM检测消息用于指示BFIR后的第(M-1)跳节点使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并反馈校验结果。其中，控制器发出的OAM检测消息中的TTL可以从1开始递增，即，控制器可以先发送TTL＝1的OAM检测消息，在收到反馈后，再发送TTL＝2的检测消息，以此类推，以实现对故障的准确定位。
在一个可选的实施例中，当向上述BFIR发送用于请求检测BIER-TE路径的携带有生存时间TTL的OAM检测消息时，该OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中压入与位串BitString中所有邻接体adjacency相应的转发等价类FEC，其中，该BitString位于OAM检测消息中携带的BIER-TE数据头header中。
在一个可选的实施例中，上述方法还包括：在向BFIR发送用于请求检测BIER-TE路径的OAM检测消息之后，接收BFIR或待检测路径上BFIR后的位转发路由器BFR反馈的携带校验成功信息的BIER-TE响应应答echo reply消息，其中，该BIER-TE echo reply消息中携带有下游映射downstream Mapping TLV信息以及转发等价类堆栈变更类型长度值FEC Stack Change TLV；根据downstream Mapping TLV信息设置待发送OAM检测消息的TTL，以及，根据FEC Stack Change TLV弹出所述待发送OAM检测消息中携带的 BIER-TE响应请求echo request中的Target FEC Stack TLV中的相应的adjacency相应的FEC；向BFIR发送上述待发送OAM检测消息。
下面结合具体实施例对本发明进行说明：
图4是本发明实施例的用于检测BIER-TE路径的OAM消息格式示意图。
其中消息类型Message Type包括如下两种类型：
1   BIER-TE Echo Request(BIER-TE响应请求)
2   BIER-TE Echo Reply(BIER-TE响应回复)
图5是本发明实施例的Echo Request或Reply header format示意图，其中，
Reply mode(回复模式)：默认设置为2
               1   Do not Reply(不回复)
               2   Reply via IPv4或IPv6UDP packet(通过IPv4或IPv6用户数据报协议(UDP，User Datagram Protocol)数据包回复)
               3   Reply via BIER-TE packet(通过BIER-TE数据包回复)
Return Code(返回码)：
0   No return code(没有返回码)
//echo request时设置
1   Malformed Echo Request received
//收到echo request的格式不正确时设置
2   One or more of the TLVs was not understood
//收到echo request中有任何TLV不理解时设置
3   Replying BFR is the only BFER in header Bitstring
//收到echo request中的BitString仅包含本节点的local_decap ID
4   Replying BFR is one of the BFER in header Bitstring
//收到echo request中的BitString包含本节点及其它节点的local_decap ID
5   Packet-Forward-Success
//traceroute模式时若中间节点能成功的将报文转发
6   Invalid Multipath Info Request
//收到echo request中针对多个BFER都想使用Multipath Info
8   No matching entry in forwarding table.
//BFER上若不存在相应的组播业务表项
//或BFR上不存在相应的BIFT表项
9   Set-Identifier Mismatch
//收到的BIER-TE MPLS Label不是本节点分配给相应SI的
TLVs：
10   Replying BFR is not in the path to any target BFER
//traceroute模式时节点回复，表示responder不处于到达任何target BFER的路径上。
本发明实施例中引入的TLV，具体格式见图6-图12。
在下述的具体实施例中，具体实施例一至具体实施例三用的TLV，包括图6-图12，而具体实施例四用的TLV仅包含图6-图8。下面从具体的实施例具体介绍一种基于流量工程扩展的位索引显式复制的故障检测方法。
具体实施例一
图1中描述了相关技术中的BIER-TE组网图，图中BIER-TE域内的所有节点均与控制器相连。图13是本发明具体实施例一的故障检测示意图，下 面结合图13对本实施例进行说明：
在本实施例中提供了一种基于流量工程扩展的位索引显式复制的故障检测方法，主要是利用PING技术，BIER-TE PING技术中主要是通过发起节点(即，图13中的控制器)验证BIER-TE路径发送请求消息，在出节点(即，图13中的BFER1和/或BFER2)进行上送处理。出节点验证需要校验FEC，向发起节点回应响应应答消息，从而实现BIER-TE的故障检测，如图13所示，在纯BIER-TE网络中，假设从控制器发起一个BIER-TE故障检测消息到BFER1及BFER2节点，其具体过程如下：
步骤S1301，BIER-TE控制器向BFIR1发起故障检测消息。
故障检测消息中：包括BIER-TE header及BIER-TE echo request消息，其中BIER-TE echo request在BIER-TE header的后面，BIER header中proto字段为5表示是BIER-TE OAM报文。BIER-TE header的外层继续封装BIER-MPLS Label。PING模式时BIER-MPLS Label的TTL设为255。BIER-TE echo request中封装本发明实施例中提出的BIER-TE local_decap TLV。还可以包含Target SI-BitString TLV，控制哪些BFER要回复reply。
步骤S1302，BFIR1接收到控制器发起的故障检测消息，根据BIER-TE header转发故障检测消息，即通过BFR1、BFR2转发至BFER1及BFER2节点。
步骤S1303，BFER1及BFER2节点接收到故障检测消息后，进行FEC校验。
其中FEC的格式见图6所示的BIER-TE local_decap TLV格式，BFER(即，上述的BFER1和/或BFER2)节点将BIER-TE header中的BitString与BIER-TE local_decap TLV相校验。该TLV中，校验成功的情况如下：
BFER1节点收到的advertising node identifier(该advertising node identifier携带在BIER-TE local_decap TLV中)中填写的是BFER1节点地址，并且BFER1adjacency id与BitString中相应的bit表示的索引一致；
BFER2节点收到的advertising node identifier中填写的是BFER2节点地址，并且BFER2adjacency id与BitString中相应的bit表示的索引一致。
步骤S1304，若校验成功，BFER1及BFER2节点分别回应一个BIER-TE echo reply消息给控制器。
步骤S1305，若校验失败，BFER1及BFER2节点分别回应一个携带FEC校验失败的echo reply消息给控制器。
步骤S1306，若链路出现故障，则BFER节点无法收到BIER-TE echo request消息，将不会回复任何BIER-TE echo reply消息。
具体实施例二
图14-17是本发明具体实施例二的故障检测示意图，该实施例中主要是介绍纯BIER-TE网络中的traceroute模式，traceroute模式时可以从TTL＝1递增并且收到所有BFER的reply回复的Return code均为"Replying router is the only BFER in BIER header Bitstring"时停止发送echo request。当然，可以包含Target SI-BitString TLV，控制器控制向哪些BFER做路径trace。如图14-17所示，该流程包括如下步骤：
步骤S1401，BIER-TE控制器向BFIR1发起TTL＝1的故障检测消息。
该故障检测消息中：包括BIER-TE header及BIER-TE echo request消息，其中BIER-TE echo request在BIER-TE header的后面，BIER header中proto字段为5表示该故障检测消息是BIER OAM报文。BIER header的外层继续封装BIER-MPLS Label。traceroute时BIER-MPLS Label的TTL递增。BIER-TE echo request在Target FEC Stack TLV中压入BitString中所有adjacency相应的FEC。每一个adjacency索引在BitString中的前后顺序与相应的FEC在FEC栈中的前后顺序保持一致。
步骤S1402，BFIR1接收到控制器发起的TTL＝1的故障检测消息后，根据BIER header中的BitString与Target FEC Stack TLV中的相应的BIER-TE forward_connected TLV进行校验。验证成功的情况如下：BFIR1节点收到的BIER-TE forward_connected TLV中填写的是BFIR1的一条直连链路，并且BFIR1为该直连链路分配的adjacency id与BitString中相应的bit表示的索引一致。
步骤S1403，若校验成功，BFIR1回应携带校验成功信息的BIER-TE echo reply消息给控制器。
该BIER-TE echo reply消息中需要携带downstream Mapping TLV给控制器，downstream Mapping TLV中携带下游节点地址，及下游接口地址，还可以包括FEC Stack Change TLV，以告知控制器弹出BIER-TE Target FEC Stack TLV中的相应的forward_connected TLV。
步骤S1404，若校验失败，BFIR1回应一个携带FEC校验失败的echo reply消息给控制器。
步骤S1405：控制器向BFIR1发起TTL＝2的故障检测消息。
步骤S1406：BFIR1接收到TTL＝2的报文，将TTL减1，然后转发这个报文给BFR1。
步骤S1407，报文到达BFR1节点时，TTL＝1，BFR1根据BIER header中的BitString与Target FEC Stack TLV中的相应的BIER-TE forward_connected TLV进行校验。校验成功的情况如下：BIR1节点收到的BIER-TE forward_connected TLV中填写的是BFR1的一条直连链路，并且BFIR1为该直连链路分配的adjacency id与BitString中相应的bit表示的索引一致。
步骤S1408，若校验成功，BFR1回应携带校验成功信息的BIER-TE echo reply消息给控制器。
echo reply消息中携带FEC Stack Change TLV，告知控制器弹出BIER-TE Target FEC Stack TLV中的相应的forward_connected TLV，BIER-TE echo reply消息需要携带downstream Mapping TLV给控制器，downstream Mapping TLV中携带下游节点地址，及下游接口地址。
步骤S1409，若校验失败，BFR2回应一个携带FEC校验失败的echo reply消息给控制器。
步骤S1410：控制器发起TTL＝3的故障检测消息。
步骤S1411：报文通过BFIR1及BFR1节点时，TTL分别减1，并按照BIER header转发这个报文给BFR2。
步骤S1412，报文到达BFR2节点时，TTL＝1，BFR2根据BIER header中的BitString与Target FEC Stack TLV中的相应的BIER-TE forward_connected TLV进行校验。校验成功的情况如下：BFR2节点收到的BIER-TE forward_connected TLV中填写的是BFR2的一条直连链路，并且BFIR1为该直连链路分配的adjacency id与BitString中相应的bit表示的索引一致。
步骤S1413，若校验成功，BFR2回应携带校验成功信息的BIER-TE echo reply消息给控制器。
该echo reply消息中携带FEC Stack Change TLV，告知控制器弹出BIER-TE Target FEC Stack TLV中的相应的forward_connected TLV，BIER-TE echo reply消息需要携带downstream Mapping TLV给控制器，downstream Mapping TLV中携带下游节点地址，及下游接口地址。
步骤S1414，若校验失败，BFR2回应一个携带FEC校验失败的echo reply消息给控制器。
步骤S1415：控制器发起TTL＝4的故障检测消息。
步骤S1416：报文通过BFIR1、BFR1及BFR2节点时，TTL分别减1，并按照BIER header转发这个报文给BFER。
步骤S1417，报文到达BFER节点时，TTL＝1，BFER根据BIER header中的BitString与Target FEC Stack TLV中的相应的BIER-TE local_decap TLV进行校验。校验成功的情况如下：BFER节点收到的advertising node identifier中填写的是BFER节点地址，并且分配的BFER的节点地址的adjacency id与BitString中相应的bit表示的索引一致。
步骤S1418，若校验成功，BFER回应携带校验成功信息的BIER-TE echo reply消息给控制器。
步骤S1419，若校验失败，BFER回应一个携带FEC校验失败的echo reply消息给控制器。
具体实施例三
图18-20是本发明具体实施例三的故障检测示意图，该实施例中主要是介绍纯BIER-TE网络中的traceroute模式，traceroute模式时从TTL＝1递增并且收到所有BFER的reply回复的Return code均为"Replying router is the only BFER in BIER header Bitstring"时停止发送echo request。当然，可以包含Target SI-BitString TLV，控制向哪些BFER做路径trace。如图18-20所示，假设BFR2出现故障，该流程包括如下步骤：
步骤S1501-S1509同步骤S1401-1409相同，这里不多做介绍。
步骤S1510：控制器发起TTL＝3的故障检测消息。
步骤S1511：报文通过BFIR1及BFR1节点时，TTL分别减1，并按照BIER header转发这个报文给BFR2。
步骤S1512，报文到达BFR2节点时，由于BFR2节点出现故障，将不会向控制器回复BIER-TE echo reply消息，控制器等待特定的时间后，未收到回复报文，认为BFR1与BFR2之间的链路或者BFR2节点出现故障。
具体实施例四
本实施例中，介绍纯BIER-TE网络中的traceroute模式，traceroute模式时从TTL＝1递增并且收到所有BFER的reply回复的Return code均为"Replying router is the only BFER in BIER header Bitstring"时停止发送echo request。该实施例中引入Original SI-BitString TLV、Target SI-BitString TLV。如图13所示，该流程包括如下步骤：
步骤S1601，BIER-TE控制器发起TTL＝1的故障检测消息。
该故障检测消息中可以包括BIER-TE header及BIER-TE echo request消息，其中BIER-TE echo request在BIER-TE header的后面，BIER-TE header中proto字段为5表示是BIER-TE OAM报文。BIER-TE header的外层继续封装BIER-MPLS Label。traceroute时BIER-MPLS Label的TTL递增。BIER-TE echo request可以包含Target SI-BitString TLV，控制向哪些BFER做路径trace，也可以包含下游节点及接口的一些信息。
步骤S1602，BFIR1接收到控制器发起的TTL＝1的故障检测消息后，将 BIER header中的BitString与Target SI-BitString TLV相与。
步骤S1603，若相与结果不为0，BFIR1节点需要做其他的检查。
如果BIER-Label-L与本地为Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，则回复的报文中携带：Set-Identifier Mismatch。
如果Echo Request消息中存在任何不理解(同上述的不识别)的TLV，则回复：不理解的TLV。
如果BIER header中的BitString与接收echo request报文的入接口对应的echo request报文中的DDMAP TLV中的Egress BitString Sub-TLV不匹配，需要回复不匹配信息。
如果该节点没有匹配到BIFT表项，则回复：不匹配表项。
如果没有任何问题，则回复code5：Packet-Forward-Success给控制器。
步骤S1604：控制器发起TTL＝2的故障检测消息。
步骤S1605：BFIR1接收到TTL＝2的报文，将TTL减1，转发这个报文给BFR1。
步骤S1606，报文到达BFR1节点时，TTL＝1，BFR1根据BIER header中的BitString与Target SI-BitString TLV相与。
步骤S1607，若相与结果不为0，BFR1节点需要做其他的检查。
BIER-TE echo reply消息需要携带downstream Mapping TLV给控制器，downstream Mapping TLV中携带下游节点地址，及下游接口地址。
如果BIER-Label-L与本地为Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，则回复的报文中携带：Set-Identifier Mismatch。
如果Echo Request message中存在任何不理解的TLV，则回复：不理解的TLV。
如果BIER header中的BitString与接收echo request报文的入接口对应的echo request报文中的DDMAP TLV中的Egress BitString Sub-TLV不匹配， 需要回复不匹配信息。
如果该节点没有匹配到BIFT表项，则回复：不匹配表项。
如果没有任何问题，则回复code5：Packet-Forward-Success给控制器。
步骤S1608：控制器发起TTL＝3的故障检测消息。
步骤S1609：报文通过BFIR1及BFR1节点时，TTL分别减1，并按照BIER header转发这个报文给BFR2。
步骤S1610，报文到达BFR2节点时，TTL＝1，BFR2根据BIER header中的BitString与Target SI-BitString TLV相与。
步骤S1611，若相与结果不为0，BFR2节点需要做其他的检查。
如果BIER-Label-L与本地为Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，则回复的报文中携带：Set-Identifier Mismatch。
如果Echo Request message中存在任何不理解的TLV，则回复：不理解的TLV。
如果BIER header中的BitString与接收echo request报文的入接口对应的echo request报文中的DDMAP TLV中的Egress BitString Sub-TLV不匹配，需要回复不匹配信息。
如果该节点没有匹配到BIFT表项，则回复：不匹配表项。
如果没有任何问题，则回复报文转发成功信息给控制器。
步骤S1612：控制器发起TTL＝4的故障检测消息。
步骤S1613：报文通过BFIR1、BFR1及BFR2节点时，TTL分别减1，并按照BIER header转发这个报文给BFER。
步骤S1614，报文到达BFER节点时，TTL＝1，BFER根据BIER header中的BitString与Target SI-BitString TLV相与。
步骤S1615，若相与结果不为0，节点需要做其他的检查。
如果BIER-Label-L与本地为Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，则回复的报文中携带： Set-Identifier Mismatch。
如果Echo Request message中存在任何不理解的TLV，则回复：不理解的TLV。
如果BIER header中的BitString与入接口对应的echo request报文中DDMAP TLV中的Egress BitString Sub-TLV不匹配，需要回复不匹配信息。
如果该节点没有匹配到BIFT表项，则回复：不匹配表项。
如果没有任何问题，即会匹配到BFER的local_decap adjacency对应的BIFT表项，则根据Target SI-BitString TLV若还存在其它BFER的local_decap adjacency索引回复"Replying router is one of the BFER in BIER header Bitstring"信息给控制器，或者根据Target SI-BitString TLV若不存在其它BFER的local_decap adjacency索引回复"Replying router is the only BFER in BIER header Bitstring"信息给控制器。
步骤S1617，若相与结果为0，则会回复“Code 10：Replying BFR is not in the path to any target BFER”。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(ROM，Read Only Memory)或随机存取存储器(RAM，Random Access Memory)、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种故障检测装置，该装置设置为实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图21是本发明实施例的第一种故障检测装置的结构框图，如图21所示， 该装置包括接收模块212和检测模块214，下面对该装置进行说明。
接收模块212，设置为接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；
检测模块214，连接至上述接收模块212，设置为根据上述OAM检测消息对BIER-TE路径进行故障检测。
在一个可选的实施例中，上述接收模块212是设置为：通过用于接收BIER-TE数据报文的路径接收OAM检测消息。
在一个可选的实施例中，当接收上述OAM检测消息的节点为位转发入口路由器BFIR或位转发路由器BFR时，上述检测模块214是设置为：根据OAM检测消息中携带的位转发出口路由器BFER信息将OAM检测消息转发给BFER信息对应的BFER，其中，OAM检测消息用于指示BFER执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果；或者，根据OAM检测消息的生存时间TTL对BIER-TE路径进行故障检测，其中：当TTL的值为1时，使用OAM检测消息执行对BIER-TE路径进行故障检测的校验；当TTL的值为大于1的M值时，将OAM检测消息转发给BFIR或BFR后的第(M-1)跳节点，OAM检测消息用于指示BFIR或BFR后的第(M-1)跳节点使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果。
在一个可选的实施例中，当接收OAM检测消息的节点为位转发出口路由器BFER时，上述接收模块212是设置为：接收位转发入口路由器BFIR或位转发路由器BFR转发的来自控制器的OAM检测消息；上述检测模块214是设置为：使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果。
在一个可选的实施例中，当执行校验操作的为BFER时，上述检测模块214是设置为采用以下方式实现执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果：将OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的BIER-TE本地解封装类型长度值local_decap TLV相校验；当校验出BIER-TE local_decap TLV中携带的通告节点标识advertising node  identifier中填写的是BFER地址，并且BFER的邻接体标识adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply，当校验出BIER-TE local_decap TLV中携带的通告节点标识advertising node identifier中填写的不是BFER地址，或者BFER的邻接体标识adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，当执行校验操作的为BFER时，上述检测模块214是设置为采用以下方式实现执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果：将OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的目的位串类型长度值Target SI-BitString TLV相与；当相与结果不为0时，BFER执行如下操作：当确定BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与BIER-TE echo request中的原始位串类型长度值Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致时，向控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；当确定BIER-TE echo request中存在不识别的TLV时，向控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；当确定BIER-TE header中的BitString与BIER-TE echo request中携带的下游映射downstream MappingTLV中的出口位串子-类型长度值Egress BitString Sub-TLV不匹配时，向控制器发送携带不匹配信息的BIER-TE响应应答echo reply；当BFER没有匹配到BIFT表项时，向控制器发送携带不匹配表项的BIER-TE响应应答echo reply；当确定不存在任何问题时，若Target SI-BitString TLV中还存在除出口BFER之外的其他BFER的本地解封装邻接体local_decap adjacency索引时，向控制器发送携带"Replying router is one of the BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；若Target SI-BitString TLV中不存在其他BFER的local_decap adjacency索引时，向控制器发送携带"Replying router is the only BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；当相与结果为0时，BFER向控制器发送携带“Replying BFR is not in the path to any target  BFER”信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，当执行校验操作的为BFIR或BFR时，上述检测模块214是设置为采用以下方式实现执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果：根据OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中的相应的邻接体adjacency FEC进行校验，并向控制器反馈校验结果。
在一个可选的实施例中，每一个adjacency索引在BitString中的前后顺序与相应的FEC在FEC栈中的前后顺序保持一致。
在一个可选的实施例中，Target FEC Stack TLV中的相应的adjacency FEC包括前向连接forward_connected TLV和/或前向路由forward_routed TLV，其中，当Target FEC Stack TLV中的相应的adjacency FEC包括forward_connected TLV时，当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的是BFIR或BFR的一条直连链路，并且BFIR或BFR为直连链路分配的adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply，当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的不是BFIR或BFR的一条直连链路，或者BFIR或BFR为直连链路分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply；当Target FEC Stack TLV中的相应的adjacency FEC包括forward_routed TLV时，当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的是前缀prefix信息，并且BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引一致时，校验成功，向控制器发送携带校验成功信息的BIER-TE响应应答echo reply，当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的不是前缀prefix信息，或者BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
在一个可选的实施例中，当BFIR或BFR向控制器发送携带校验成功信 息的BIER-TE响应应答echo reply时，BIER-TE echo reply中还携带有：下游映射downstream Mapping TLV信息，以及，FEC Stack Change TLV，其中，downstream Mapping TLV信息中携带下游节点地址，及下游接口地址；FEC Stack Change TLV用于告知控制器弹出Target FEC Stack TLV中的相应的adjacency FEC。
在一个可选的实施例中，当执行校验操作的为BFIR或BFR时，上述检测模块214是设置为采用以下方式实现执行对BIER-TE路径进行故障检测的校验，并向控制器反馈校验结果：BFIR或BFR将OAM检测消息中携带的BIER-TE数据头header中的位串BitString与OAM检测消息中携带的BIER-TE响应请求echo request中的Target SI-BitString TLV相与；当相与结果不为0时，BFIR或BFR执行如下操作：当确定BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与BIER-TE echo request中的Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，向控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；当确定BIER-TE echo request中存在不识别的TLV时，向控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；当确定BIER-TE header中的BitString与BIER-TE echo request中携带的下游映射downstream Mapping TLV中的Egress BitString Sub-TLV不匹配时，向控制器发送携带不匹配信息的BIER-TE响应应答echo reply；当BFIR或BFR没有匹配到BIFT表项时，向控制器发送携带不匹配表项的BIER-TE响应应答echo reply；当确定不存在任何问题时，向控制器发送携带包转发成功Packet-Forward-Success信息的BIER-TE响应应答echo reply；当相与结果为0时，BFIR或BFR向控制器发送携带“Replying BFR is not in the path to any target BFER”信息的BIER-TE响应应答echo reply。
图22是本发明实施例的第二种故障检测装置的结构框图，如图22所示，该装置包括发送模块222，下面对该装置进行说明：
发送模块222，设置为向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，OAM检测消息用于指示BFIE使用OAM检测消息对BIER-TE 路径进行故障检测。
在一个可选的实施例中，上述发送模块222是设置为：向BFIR发送用于请求检测BIER-TE路径的OAM检测消息，其中，OAM检测消息中携带位转发出口路由器BFER信息，BFER信息用于BFIR根据BFER信息将OAM检测消息转发给BFER信息对应的BFER，OAM检测消息用于指示BFER执行对BIER-TE路径进行故障检测的校验，并反馈校验结果；或者，向BFIR发送用于请求检测BIER-TE路径的携带有生存时间TTL的OAM检测消息，其中：当TTL的值为1时，OAM检测消息用于指示BFIR使用OAM检测消息执行对BIER-TE路径进行故障检测的校验；当TTL的值为大于1的M值时，OAM检测消息用于指示BFIR将OAM检测消息转发给BFIR后的第M-1跳节点，OAM检测消息用于指示BFIR后的第M-1跳节点使用OAM检测消息执行对BIER-TE路径进行故障检测的校验，并反馈校验结果。
在一个可选的实施例中，当向BFIR发送用于请求检测BIER-TE路径的携带有生存时间TTL的OAM检测消息时，OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中压入与位串BitString中所有邻接体adjacency相应的转发等价类FEC，其中，BitString位于OAM检测消息中携带的BIER-TE数据头header中。
在一个可选的实施例中，上述装置还包括处理模块，设置为在向BFIR发送用于请求检测BIER-TE路径的OAM检测消息之后，接收BFIR或待检测路径上BFIR后的位转发路由器BFR反馈的携带校验成功信息的BIER-TE响应应答echo reply消息，其中，BIER-TE echo reply消息中携带有下游映射downstream Mapping TLV信息以及转发等价类堆栈变更类型长度值FEC Stack Change TLV；根据downstream Mapping TLV信息设置待发送OAM检测消息的TTL，以及，根据FEC Stack Change TLV弹出待发送OAM检测消息中携带的BIER-TE响应请求echo request中的Target FEC Stack TLV中的相应的adjacency相应的FEC；向BFIR发送待发送OAM检测消息。
需要说明的是，上述每一个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明实施例还提出了一种计算机可读存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述描述的任意一个方法。
本发明的实施例还提供了一种存储介质。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的OAM检测消息；
S2，根据上述OAM检测消息对BIER-TE路径进行故障检测。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，该OAM检测消息用于指示BFIE使用OAM检测消息对BIER-TE路径进行故障检测。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等一种或多种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述每一个方法实施例中的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储与存储器中的程序/指令来实现其相应功能。本发明不限于任何特定形式的硬件和软件的结 合。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
上述技术方案实现了BIER-TE中的路径检测，保证了BIER-TE中的报文的可靠传输。

Claims (17)

  1. 一种故障检测方法，包括：
    接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；
    根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
  2. 根据权利要求1所述的方法，其中，接收来自所述控制器的用于请求检测所述BIER-TE路径的所述OAM检测消息包括：
    通过用于接收BIER-TE数据报文的路径接收所述OAM检测消息。
  3. 根据权利要求1所述的方法，其中，当接收所述OAM检测消息的节点为位转发入口路由器BFIR或位转发路由器BFR时，根据所述OAM检测消息对所述BIER-TE路径进行故障检测包括：
    所述BFIR或BFR根据所述OAM检测消息中携带的位转发出口路由器BFER信息将所述OAM检测消息转发给所述BFER信息对应的BFER，其中，所述OAM检测消息用于指示所述BFER执行对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果；或者，
    所述BFIR或BFR根据所述OAM检测消息的生存时间TTL对所述BIER-TE路径进行故障检测，其中：
    当所述TTL的值为1时，所述BFIR或BFR使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果；
    当所述TTL的值为大于1的M值时，所述BFIR或BFR将所述OAM检测消息转发给所述BFIR或BFR后的第(M-1)跳节点，所述OAM检测消息用于指示所述BFIR或BFR后的第(M-1)跳节点使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果。
  4. 根据权利要求1所述的方法，其中，当接收所述OAM检测消息的节点为位转发出口路由器BFER时，
    接收来自所述控制器的所述OAM检测消息包括：所述BFER接收位转 发入口路由器BFIR或位转发路由器BFR转发的来自所述控制器的所述OAM检测消息；
    根据所述OAM检测消息对所述BIER-TE路径进行故障检测包括：所述BFER使用所述OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果。
  5. 根据权利要求3或4所述的方法，其中，当执行校验操作的为BFER时，所述BFER使用OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：
    所述BFER将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的BIER-TE本地解封装类型长度值local_decap TLV相校验；
    当所述BFER校验出所述BIER-TE local_decap TLV中携带的通告节点标识advertising node identifier中填写的是所述BFER地址，并且所述BFER的邻接体标识adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply；
    当BFER校验出BIER-TE local_decap TLV中携带的advertising node identifier中填写的不是所述BFER地址，或BFER的adjacency id与所述BitString中相应的bit表示的索引不一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
  6. 根据权利要求3或4所述的方法，其中，当执行校验操作的为BFER时，所述BFER使用OAM检测消息执行对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：
    所述BFER将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的目的位串类型长度值Target SI-BitString TLV相与；
    当相与结果不为0时，所述BFER执行如下操作：
    当确定所述BIER-TE header外封装的BIER-多协议标签交换MPLS标签 Lable中的BIER-Label-L与所述BIER-TE echo request中的原始位串类型长度值Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致时，向所述控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；
    当确定所述BIER-TE echo request中存在不识别的TLV时，向所述控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；
    当确定所述BIER-TE header中的BitString与所述BIER-TE echo request中携带的下游映射downstream Mapping TLV中的出口位串子-类型长度值Egress BitString Sub-TLV不匹配时，向所述控制器发送携带不匹配信息的BIER-TE响应应答echo reply；
    当所述BFER没有匹配到BIFT表项时，向所述控制器发送携带不匹配表项的BIER-TE响应应答echo reply；
    当确定不存在任何问题时，若所述Target SI-BitString TLV中还存在除所述出口BFER之外的其他BFER的本地解封装邻接体local_decap adjacency索引时，向所述控制器发送携带"Replying router is one of the BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；若所述Target SI-BitString TLV中不存在其他BFER的local_decap adjacency索引时，向所述控制器发送携带"Replying router is the only BFER in BIER header Bitstring"信息的BIER-TE响应应答echo reply；
    当相与结果为0时，所述BFER向所述控制器发送携带“Replying BFR is not in the path to any target BFER”信息的BIER-TE响应应答echo reply。
  7. 根据权利要求3所述的方法，其中，当执行校验操作的为BFIR或BFR时，所述BFIR或BFR使用OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：
    所述BFIR或BFR根据所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中的相应的邻接体adjacency FEC进行校验，并向所述控制器反馈校验结果。
  8. 根据权利要求7所述的方法，其中，每一个adjacency索引在所述BitString中的前后顺序与相应的FEC在FEC栈中的前后顺序保持一致。
  9. 根据权利要求7所述的方法，其中，所述Target FEC Stack TLV中的相应的adjacency FEC包括前向连接forward_connected TLV和/或前向路由forward_routed TLV，其中，
    当所述Target FEC Stack TLV中的相应的adjacency FEC包括所述forward_connected TLV时，所述BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：
    当所述BFIR或BFR校验出所述BIER-TE forward_connected TLV中填写的是所述BFIR或BFR的一条直连链路，并且所述BFIR或BFR为所述直连链路分配的adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply；当BFIR或BFR校验出BIER-TE forward_connected TLV中填写的不是BFIR或BFR的一条直连链路，或者BFIR或BFR为所述直连链路分配的adjacency id与BitString中相应的bit表示的索引不一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply；
    当所述Target FEC Stack TLV中的相应的adjacency FEC包括所述forward_routed TLV时，所述BFIR或BFR根据OAM检测消息中携带的BIER-TE header中的BitString与OAM检测消息中携带的BIER-TE echo request中的Target FEC Stack TLV中的相应的adjacency FEC进行校验，并向所述控制器反馈校验结果包括：
    当所述BFIR或BFR校验出所述BIER-TE forward_routed TLV中填写的是前缀prefix信息，并且所述BFIR或BFR为所述prefix分配的adjacency id与所述BitString中相应的bit表示的索引一致时，校验成功，向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply；当BFIR或BFR校验出BIER-TE forward_routed TLV中填写的不是前缀prefix信息，或者BFIR或BFR为prefix分配的adjacency id与BitString中相应的bit表示的索引不 一致时，校验失败，向所述控制器发送携带校验失败信息的BIER-TE响应应答echo reply。
  10. 根据权利要求9所述的方法，当所述BFIR或BFR向所述控制器发送携带校验成功信息的BIER-TE响应应答echo reply时，所述BIER-TE echo reply中还携带有：
    下游映射downstream Mapping TLV信息，以及，FEC Stack Change TLV；
    其中，所述downstream Mapping TLV信息中携带下游节点地址，及下游接口地址；所述FEC Stack Change TLV用于告知所述控制器弹出所述Target FEC Stack TLV中的相应的adjacency FEC。
  11. 根据权利要求3所述的方法，其中，当执行校验操作的为BFIR或BFR时，所述BFIR或BFR使用OAM检测消息对所述BIER-TE路径进行故障检测的校验，并向所述控制器反馈校验结果包括：
    BFIR或BFR将所述OAM检测消息中携带的BIER-TE数据头header中的位串BitString与所述OAM检测消息中携带的BIER-TE响应请求echo request中的Target SI-BitString TLV相与；
    当相与结果不为0时，所述BFIR或BFR执行如下操作：
    当确定所述BIER-TE header外封装的BIER-多协议标签交换MPLS标签Lable中的BIER-Label-L与所述BIER-TE echo request中的Original SI-BitString TLV中给出的{sub-domain,BitStringLen,SI}分配的标签不一致，向所述控制器发送携带Set-Identifier Mismatch的BIER-TE响应应答echo reply；
    当确定所述BIER-TE echo request中存在不识别的TLV时，向所述控制器发送携带不识别的TLV的BIER-TE响应应答echo reply；
    当确定所述BIER-TE header中的BitString与所述BIER-TE echo request中携带的下游映射downstream Mapping TLV中的Egress BitString Sub-TLV不匹配时，向所述控制器发送携带不匹配信息的BIER-TE响应应答echo reply；
    当所述BFIR或BFR没有匹配到BIFT表项时，向所述控制器发送携带 不匹配表项的BIER-TE响应应答echo reply；
    当确定不存在任何问题时，向所述控制器发送携带包转发成功Packet-Forward-Success信息的BIER-TE响应应答echo reply；
    当相与结果为0时，所述BFIR或BFR向所述控制器发送携带“Replying BFR is not in the path to any target BFER”信息的BIER-TE响应应答echo reply。
  12. 一种故障检测方法，包括：
    向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，所述OAM检测消息用于指示所述BFIE根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
  13. 根据权利要求12所述的方法，其中，向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息包括：
    向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息，其中，所述OAM检测消息中携带位转发出口路由器BFER信息，所述BFER信息用于指示所述BFIR根据所述BFER信息将所述OAM检测消息转发给所述BFER信息对应的BFER，所述OAM检测消息用于指示所述BFER执行对所述BIER-TE路径进行故障检测的校验，并反馈校验结果；或者，
    向所述BFIR发送用于请求检测所述BIER-TE路径的携带有生存时间TTL的所述OAM检测消息，其中：当所述TTL的值为1时，所述OAM检测消息用于指示所述BFIR根据所述OAM检测消息执行对所述BIER-TE路径进行故障检测的校验；当所述TTL的值为大于1的M值时，所述OAM检测消息用于指示所述BFIR将所述OAM检测消息转发给所述BFIR后的第(M-1)跳节点，所述OAM检测消息用于指示所述BFIR后的第(M-1)跳节点根据所述OAM检测消息执行对所述BIER-TE路径进行故障检测的校验，并反馈校验结果。
  14. 根据权利要求13所述的方法，其中，当向所述BFIR发送用于请求检测所述BIER-TE路径的携带有生存时间TTL的所述OAM检测消息时，所 述OAM检测消息中携带的BIER-TE响应请求echo request中的目的转发等价类堆栈类型长度值Target FEC Stack TLV中压入与位串BitString中所有邻接体adjacency相应的转发等价类FEC，其中，所述BitString位于所述OAM检测消息中携带的BIER-TE数据头header中。
  15. 根据权利要求14所述的方法，所述方法还包括：
    在向所述BFIR发送用于请求检测所述BIER-TE路径的所述OAM检测消息之后，
    接收所述BFIR或待检测路径上所述BFIR后的位转发路由器BFR反馈的携带校验成功信息的BIER-TE响应应答echo reply消息，其中，所述BIER-TE echo reply消息中携带有下游映射downstream Mapping TLV信息以及转发等价类堆栈变更类型长度值FEC Stack Change TLV；
    根据所述downstream Mapping TLV信息设置待发送OAM检测消息的TTL，以及，根据所述FEC Stack Change TLV弹出所述待发送OAM检测消息中携带的BIER-TE响应请求echo request中的Target FEC Stack TLV中的相应的adjacency相应的FEC；
    向所述BFIR发送所述待发送OAM检测消息。
  16. 一种故障检测装置，包括：
    接收模块，设置为接收来自控制器的用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息；
    检测模块，设置为根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
  17. 一种故障检测装置，包括：
    发送模块，设置为向位转发入口路由器BFIR发送用于请求检测基于流量工程扩展的位索引显示复制BIER-TE路径的运行管理和维护OAM检测消息，其中，所述OAM检测消息用于指示所述BFIE根据所述OAM检测消息对所述BIER-TE路径进行故障检测。
PCT/CN2016/100111 2016-03-01 2016-09-26 故障检测方法及装置 WO2017148139A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610114780.1 2016-03-01
CN201610114780.1A CN107147508B (zh) 2016-03-01 2016-03-01 故障检测方法及装置

Publications (1)

Publication Number Publication Date
WO2017148139A1 true WO2017148139A1 (zh) 2017-09-08

Family

ID=59742441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/100111 WO2017148139A1 (zh) 2016-03-01 2016-09-26 故障检测方法及装置

Country Status (2)

Country Link
CN (1) CN107147508B (zh)
WO (1) WO2017148139A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019169268A1 (en) * 2018-03-02 2019-09-06 Huawei Technologies Co.Ltd. Igp topology information and use for bier-te
CN114172798A (zh) * 2021-11-08 2022-03-11 烽火通信科技股份有限公司 Bier网络故障检测方法、装置、设备及可读存储介质
JP7050177B2 (ja) 2018-03-30 2022-04-07 華為技術有限公司 マルチキャストパケットを伝送する方法、デバイス、及びシステム
US11582140B2 (en) 2020-12-16 2023-02-14 Cisco Technology, Inc. OAM-based suboptimal ECMP path detection in software-defined fabric

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109660460B (zh) * 2017-10-10 2021-10-19 中兴通讯股份有限公司 Bier-te信息的处理方法、服务器及存储介质
CN109921987B (zh) * 2017-12-13 2022-01-21 中兴通讯股份有限公司 一种bier-te网络检测方法、装置及系统
CN110391977B (zh) * 2018-04-18 2021-11-09 中兴通讯股份有限公司 一种网络故障保护的方法、系统和存储介质
CN116208525A (zh) 2018-06-06 2023-06-02 华为技术有限公司 一种数据报文的检测方法、设备及系统
CN110825064B (zh) * 2018-08-09 2021-02-09 广州汽车集团股份有限公司 纯电动汽车防盗系统的测试方法、装置和存储介质
CN109246017B (zh) * 2018-11-28 2021-03-23 新华三技术有限公司 一种查询组播转发路径的方法及装置
CN110445677B (zh) * 2019-07-26 2021-05-07 新华三大数据技术有限公司 组播网络检测方法及转发设备
CN112688827B (zh) * 2019-10-18 2023-03-31 华为技术有限公司 一种组播流检测方法、设备及系统
CN113162855B (zh) * 2020-01-22 2022-12-27 华为技术有限公司 组播报文检测方法、网络设备和系统
CN113315701A (zh) * 2020-02-27 2021-08-27 中兴通讯股份有限公司 一种路径检测方法、电子设备及存储介质
CN113541924B (zh) * 2020-04-13 2023-09-29 华为技术有限公司 报文检测的方法、设备以及系统
CN113824608A (zh) * 2020-06-18 2021-12-21 华为技术有限公司 Bier oam检测的方法、设备以及系统
CN114531369B (zh) * 2020-10-30 2023-12-15 华为技术有限公司 性能测量的方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101984587A (zh) * 2010-11-12 2011-03-09 中兴通讯股份有限公司 一种检测组播转发树上两点间连通性的方法、系统和装置
CN101471821B (zh) * 2007-12-29 2011-07-06 华为技术有限公司 运营商骨干网传输网络的故障检测方法和装置
CN103428045A (zh) * 2012-05-25 2013-12-04 华为技术有限公司 连通性检测方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050099951A1 (en) * 2003-11-10 2005-05-12 Nortel Networks Limited Ethernet OAM fault detection and verification
CN101035057B (zh) * 2007-03-30 2011-03-30 华为技术有限公司 建立组播共享树的方法和数据传送的方法、通信网络
CN104811387B (zh) * 2014-01-24 2018-06-01 思科技术公司 具有位索引显式复制的等价多路径

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101471821B (zh) * 2007-12-29 2011-07-06 华为技术有限公司 运营商骨干网传输网络的故障检测方法和装置
CN101984587A (zh) * 2010-11-12 2011-03-09 中兴通讯股份有限公司 一种检测组播转发树上两点间连通性的方法、系统和装置
CN103428045A (zh) * 2012-05-25 2013-12-04 华为技术有限公司 连通性检测方法、装置和系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
WI JNANDS ET AL., MULTICAST USING BIT INDEX EXPLICIT REPLICATION, 19 January 2016 (2016-01-19), pages 1 - 36 *
ZHENG. ZHANG ET AL., BIER TE YANG MODULE, 29 February 2016 (2016-02-29), pages 1 - 14 *
ZHENG. ZHANG ET AL., BIER TE YANG MODULE, 29 February 2016 (2016-02-29), pages 4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019169268A1 (en) * 2018-03-02 2019-09-06 Huawei Technologies Co.Ltd. Igp topology information and use for bier-te
US11627066B2 (en) 2018-03-02 2023-04-11 Huawei Technologies Co., Ltd. IGP topology information and use for BIER-TE
JP7050177B2 (ja) 2018-03-30 2022-04-07 華為技術有限公司 マルチキャストパケットを伝送する方法、デバイス、及びシステム
US11736411B2 (en) 2018-03-30 2023-08-22 Huawei Technologies Co., Ltd. Method, device, and system for transmitting multicast packet
US11582140B2 (en) 2020-12-16 2023-02-14 Cisco Technology, Inc. OAM-based suboptimal ECMP path detection in software-defined fabric
CN114172798A (zh) * 2021-11-08 2022-03-11 烽火通信科技股份有限公司 Bier网络故障检测方法、装置、设备及可读存储介质
CN114172798B (zh) * 2021-11-08 2023-10-24 烽火通信科技股份有限公司 Bier网络故障检测方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN107147508A (zh) 2017-09-08
CN107147508B (zh) 2022-11-01

Similar Documents

Publication Publication Date Title
WO2017148139A1 (zh) 故障检测方法及装置
US10581732B2 (en) Target FEC (forwarding equivalence class) stack based FEC query in segment routing environments
EP3193477B1 (en) Data plane learning of bi-directional service chains
US9860150B2 (en) Fast convergence of EVPN networks for multi homing topologies
US11627070B2 (en) Data packet processing method and apparatus, storage medium, and electronic device
US8107473B2 (en) Automation fallback to P2P LSPs for mLDP built multipoint-trees
CN106603413B (zh) 通过指定路径传输流量的方法和装置
US10574563B2 (en) Seamless bidirectional forwarding detection discriminator based return path determination
EP3917097A1 (en) Bier-based bidirectional forwarding detection session creation method, bfir, bfer, system, and storage medium
US9379964B2 (en) Discovering a topology—transparent zone
WO2018010560A1 (zh) 多协议交换标签的检测、处理方法、装置及系统
EP4024774A1 (en) Reverse path forwarding (rpf) check method and apparatus
TWI492575B (zh) 快速標籤交換路徑警示機制
WO2017143738A1 (zh) 报文发送方法及装置
EP3155772B1 (en) A new instant messaging(im) routing method and router
WO2017124712A1 (zh) 报文生成方法、报文转发方法及装置
WO2018177273A1 (zh) 一种基于bier信息的处理及装置
EP3151486A1 (en) Fast convergence of evpn networks for multi homing topologies
EP3972206A1 (en) Method, network device and system for processing bier packet
CN110545240B (zh) 基于分布式聚合系统的标签转发表的建立及报文转发方法
CN107995113B (zh) 路径建立方法及装置
CN108540343B (zh) 路径的检测方法及装置
WO2023236544A1 (zh) 切片信息的验证方法及装置
CN104335538B (zh) 多播路由器拓扑发现
CN107317753A (zh) 双向转发检测bfd会话建立的方法、装置和系统

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16892321

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16892321

Country of ref document: EP

Kind code of ref document: A1