WO2021073377A1 - 一种组播流检测方法、设备及系统 - Google Patents

一种组播流检测方法、设备及系统 Download PDF

Info

Publication number
WO2021073377A1
WO2021073377A1 PCT/CN2020/116937 CN2020116937W WO2021073377A1 WO 2021073377 A1 WO2021073377 A1 WO 2021073377A1 CN 2020116937 W CN2020116937 W CN 2020116937W WO 2021073377 A1 WO2021073377 A1 WO 2021073377A1
Authority
WO
WIPO (PCT)
Prior art keywords
node device
identifier
bier
bier multicast
multicast
Prior art date
Application number
PCT/CN2020/116937
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 WO2021073377A1 publication Critical patent/WO2021073377A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1868—Measures taken after transmission, e.g. acknowledgments
    • 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/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • 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/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing
    • 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/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0894—Packet rate

Definitions

  • This application relates to the field of communications, and in particular to a method, equipment and system for detecting multicast streams.
  • Multicast also known as multi-target broadcast and multicast, is a method of communication between a sender and multiple receivers in the network.
  • Multicast technology can be applied to point-to-multipoint application scenarios, such as media broadcasting, event notification, status monitoring, data collection, network auctions, etc., and it can also be applied to multipoint-to-multipoint application scenarios, such as multipoint conferences, Database synchronization, etc., so it is valued by many developers.
  • Bit indexed explicit replication (BIER) technology is a type of multicast technology, which is specifically used to construct multicast transmission and forwarding paths. This technology proposes a multicast technology architecture for constructing a multicast distribution tree, namely It meets the increasing situation of multicast traffic and reduces the operating cost.
  • the Internet Engineering Task Force (the Internet Engineering Task Force, IETF) draft "draft-xie-bier-ipv6-encapsulation" defines the sixth protocol of the non-multi-protocol label switching (MPLS) Internet protocol.
  • MPLS non-multi-protocol label switching
  • IPv6 Internet protocol version 6
  • the protocol does not define the operation administration and maintenance (OAM) mechanism of BIER multicast packets, that is, it does not specify how to detect BIER multicast streams, so the transmission reliability of BIER multicast streams cannot be guaranteed. . Therefore, there is an urgent need to provide a method for detecting BIER multicast streams to realize the detection of BIER multicast streams.
  • OAM operation administration and maintenance
  • the embodiments of the present application provide a method, equipment, and system for detecting a multicast stream, so as to realize the detection of a BIER multicast stream.
  • a method for detecting a multicast stream is provided.
  • the method is applied to a first node device, and the first node device may be, for example, a router or a switch.
  • the method specifically includes the following steps: First, the first node device obtains the first index to explicitly copy the BIER multicast message, and the first BIER multicast message includes a stream identifier and a first identifier.
  • the stream identifier is used to indicate the multicast stream to which the first BIER multicast packet belongs, and can be specifically determined according to the multicast source address and the multicast group address of the first BIER multicast packet.
  • the first identifier is used to indicate a node device that detects the multicast stream and sends corresponding detection data on the forwarding path of the first BIER multicast packet.
  • the first identifier may, for example, be carried in the BIER message header of the first BIER multicast message, and specifically may be carried in the TLV field of the BIER message header.
  • the first node device determines whether to detect the multicast stream and sends corresponding detection data according to the first identifier.
  • the first node device obtains the detection data of the multicast stream, and reports to the management The device sends the detection data to realize the detection of the multicast stream.
  • the node device indicated by the first identifier is all nodes in the BIER multicast domain on the forwarding path of the first BIER multicast packet, that is, All node devices on the forwarding path need to send detection data to the management device.
  • the node device indicated by the first identifier is the head node device and the head node device on the forwarding path of the first BIER multicast packet in the BIER multicast domain. All tail node devices. In other words, only the head node device and all tail node devices on the forwarding path need to send detection data to the management device. When the node device is a head node device or a tail node device, the detection data needs to be acquired and sent to the management device. data.
  • the first node device determining whether to detect the multicast stream and sending corresponding detection data according to the first identifier includes: the first node device is in the first identifier according to the first identifier.
  • the node device identification list is determined in a BIER multicast packet, and the node device identification list is used to indicate the designated tail node device in the BIER multicast domain on the forwarding path of the first BIER multicast packet .
  • the node device identification list is a bit string of the designated tail node device.
  • the first node device determines whether to detect the multicast stream and sends corresponding detection data according to the list of node device identifiers. Specifically, if the first node device is an intermediate node device, and the node device indicated by the first identifier is the head node device, the designated tail node device, and the designated tail node device on the forwarding path of the multicast stream in the BIER multicast domain An intermediate node device between the head node device and the designated tail node device, the first node device can determine whether the identifier of the destination node in the first BIER multicast packet is in the node device identifier list, and if so, it will be described.
  • the destination node of the first BIER multicast packet belongs to the designated tail node device, and the intermediate node device is an intermediate node device between the head node device and the specified tail node device, and the detection data of the multicast stream needs to be obtained And sending the detection data to the management device.
  • the first node device is a tail node device, and the node device indicated by the first identifier includes the designated tail node device, the first node device can determine whether the first node device's identifier is in the node device identifier list, and if so , It means that the tail node device is a designated tail node device and needs to obtain the detection data of the multicast stream and send the detection data to the management device.
  • the method further includes the following steps: the first node device obtains a second BIER multicast packet, the second BIER multicast packet includes the stream identifier; the first node device is in the first corresponding relationship according to the first correspondence relationship. 2.
  • the first identifier is added to the BIER multicast message to obtain the first BIER multicast message, and the first correspondence is the correspondence between the flow identifier and the first identifier.
  • the first corresponding relationship may come from the management device or pre-configured in the head node device.
  • the first BIER multicast message further includes a second identifier, and the second identifier is used to indicate that the detection data includes data received within a preset period Statistical information of the BIER multicast packets of the multicast stream, where the statistical information includes the number of the BIER multicast packets and/or the total number of bytes of the BIER multicast packets.
  • the first node device may obtain the received statistical information of the BIER multicast packet of the multicast stream within the preset period according to the second identifier and send it to the management device, so as to realize the group Check whether the streaming is lost.
  • the first BIER multicast packet may further include the preset period.
  • the method when the first node device is the head node device in the multicast domain on the forwarding path of the first BIER multicast packet, the method further The method includes: the first node device obtains a second BIER multicast packet within the preset period, and the second BIER multicast packet includes the flow identifier.
  • the first node device adds a first field and a second field to the second BIER multicast message, the value of the address field is the first identifier, and the value of the second field is the same as the preset value.
  • the preset value corresponding to the period, and the value of the second field is used to indicate that the statistics information of the received BIER multicast packet of the multicast stream is obtained within the preset period. That is to say, if the first node device is the head node device, the first node device may add the first identifier and the second identifier to the second BIER multicast message to obtain the first BIER multicast message.
  • the first BIER multicast message further includes a third identifier, and the third identifier is used to indicate that the first BIER multicast message is used to determine Delayed packets.
  • the first node device obtains the receiving time of the first BIER multicast packet and/or the sending time of the first BIER multicast packet according to the first identifier and the third identifier, And send it to the management device to realize the detection of the delay of the multicast stream.
  • the method further Including: First, the first node device acquires at least one BIER multicast message within a preset period, and each BIER multicast message in the at least one BIER multicast message includes the flow identifier. Secondly, the first node device determines a second BIER multicast message from the at least one BIER multicast message, and the first node device adds the first identifier and the second BIER multicast message to the second BIER multicast message. The third identifier is to obtain the first BIER multicast message. In other words, if the first node device is the head node device, the first node device may add the first identifier and the third identifier to the second BIER multicast message to obtain the first BIER multicast message.
  • the first BIER multicast message further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes receiving the first BIER multicast The inbound interface identifier of the packet and/or the outbound interface identifier for sending the first BIER multicast packet.
  • the first node device may obtain the identifier of the inbound interface identifier for receiving the first BIER multicast packet according to the first identifier and the second identifier and/or send the first BIER multicast packet Identifies the outgoing interface identifier of the packet and sends it to the management device to realize the detection of the topology information of the multicast stream.
  • the method when the first node device is the head node device in the multicast domain on the forwarding path of the first BIER multicast packet, the method further The method includes: the first node device obtains a second BIER multicast packet, the second BIER multicast packet includes the stream identifier; the first node device adds the second BIER multicast packet The first identifier and the fourth identifier obtain the first BIER multicast message. In other words, if the first node device is the head node device, the first node device may add the first identifier and the fourth identifier to the second BIER multicast message to obtain the first BIER multicast message.
  • the method further includes: the first node device sends the first node device to the next-hop node device on the forwarding path of the first BIER multicast packet A BIER multicast message to realize the transmission of the first BIER multicast message.
  • a method for detecting a multicast stream is provided.
  • the method is applied to a management device, and the management device may be, for example, a controller.
  • the method includes the following steps: First, the management device obtains a first correspondence, the first correspondence being a correspondence between a stream identifier and a first identifier, the stream identifier is the identifier of the BIER multicast stream, and the first correspondence The identifier is used to indicate a node device on the forwarding path of the BIER multicast stream that detects the BIER multicast stream and sends corresponding detection data. Second, the management device sends the first correspondence to the first node device.
  • the first node device may generate the foregoing first BIER multicast message according to the first correspondence, so as to further realize the detection of the BIER multicast stream.
  • the node device indicated by the first identifier is all nodes in the BIER multicast domain on the forwarding path of the BIER multicast stream; or, the first identifier The indicated node device is the head node device and all tail node devices on the forwarding path of the BIER multicast stream in the BIER multicast domain.
  • the node device indicated by the first identifier is the head node device and the designated tail node on the forwarding path of the BIER multicast stream in the BIER multicast domain Device; or, the node device indicated by the first identifier is the head node device in the BIER multicast domain on the forwarding path of the BIER multicast stream, the designated tail node device, and the head node device and The intermediate node device between the designated tail node devices.
  • the method further includes: the management device sends the identification of the specified tail node device to the first node device, so that the first node device generates the first node that carries the identification of the specified tail node device. BIER multicast packets.
  • the first correspondence further includes a second identifier, and the second identifier is used to indicate that the detection data includes the BIER received within a preset period.
  • Statistical information of the BIER multicast packets of the multicast stream where the statistical information includes the number of the BIER multicast packets and/or the total number of bytes of the BIER multicast packets, so as to realize the monitoring of the BIER multicast stream Detection of packet loss information.
  • the first correspondence further includes a third identifier, and the third identifier is used to indicate that the detection data includes a BIER multicast packet in the BIER multicast stream.
  • the receiving time and/or sending time of the text to realize the detection of the delay information of the BIER multicast stream.
  • the first correspondence further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes receiving the BIER multicast in the BIER multicast stream.
  • the method further includes: the management device receives detection data from the node device indicated by the first identifier; The BIER multicast stream is detected to achieve the purpose of detecting the BIER multicast stream.
  • a first node device in a third aspect, is provided, and the first node device has a function of realizing the behavior of the first node device in the foregoing method.
  • the functions can be implemented based on hardware, or implemented by corresponding software based on hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the first node device includes a processor and an interface, and the processor is configured to support the first node device to perform corresponding functions in the foregoing method.
  • the interface is used to support the communication between the first node device and the management device, send the information or instructions involved in the above method to the management device, or receive the information or instructions involved in the above method from the management device.
  • the first node device may further include a memory, which is configured to be coupled with the processor and stores necessary program instructions and data for the first node device.
  • the first node device includes: a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to guide the system to start, and the first node device is guided to enter the normal operating state.
  • the application program and the operating system are run in the random access memory, so that the processor executes the first aspect or the method in any possible implementation manner of the first aspect.
  • the processor is configured to obtain a first index to explicitly copy a BIER multicast message, where the first BIER multicast message includes a stream identifier and a first identifier, and the stream identifier is used to indicate the first The multicast stream to which the BIER multicast message belongs, and the first identifier is used to indicate a node device on the forwarding path of the first BIER multicast message that detects the multicast stream and sends corresponding detection data .
  • the processor is further configured to determine whether to detect the multicast stream and send corresponding detection data according to the first identifier; in response to determining according to the first identifier that the multicast stream needs to be detected and sent Send the corresponding detection data to obtain the detection data of the multicast stream.
  • the transmitter is used to send the detection data to the management device.
  • the node device indicated by the first identifier is all nodes in the BIER multicast domain on the forwarding path of the first BIER multicast packet; or, the The node device indicated by the first identifier is the head node device and all tail node devices on the forwarding path of the first BIER multicast packet in the BIER multicast domain.
  • the first node device is a tail node device or an intermediate node device on the forwarding path of the first BIER multicast packet in the BIER multicast domain
  • the processor determines whether to detect the multicast stream according to the first identifier and sends corresponding detection data, including: the processor is configured to perform the detection in the first BIER group according to the first identifier
  • the node device identification list is determined in the broadcast message, and the node device identification list is used to indicate the designated tail node device on the forwarding path of the first BIER multicast message in the BIER multicast domain;
  • the node device identification list determines whether to detect the multicast stream and send corresponding detection data.
  • the node device identification list is a bit string of the designated tail node device.
  • the processing A device configured to: obtain a second BIER multicast message, where the second BIER multicast message includes the stream identifier; add the first identifier to the second BIER multicast message according to the first correspondence, Obtain the first BIER multicast message, and the first correspondence is the correspondence between the flow identifier and the first identifier.
  • the first node device further includes: a receiver, configured to receive the first correspondence from the management device.
  • the first BIER multicast message further includes a second identifier, and the second identifier is used to indicate that the detection data includes data received within a preset period.
  • Statistical information of the BIER multicast packets of the multicast stream where the statistical information includes the number of the BIER multicast packets and/or the total number of bytes of the BIER multicast packets; the processor uses And obtaining the received statistical information of the BIER multicast packet of the multicast stream within the preset period according to the second identifier.
  • the first BIER multicast message further includes the preset period.
  • the processor when the first node device is a head node device on the forwarding path of the first BIER multicast packet in the multicast domain, the processor , Is also used to obtain a second BIER multicast message within the preset period, where the second BIER multicast message includes the stream identifier; adding a first field and a first field to the second BIER multicast message Two fields, the value of the address field is the first identifier, the value of the second field is a preset value corresponding to the preset period, and the value of the second field is used to indicate It is assumed that the statistical information of the received BIER multicast packet of the multicast stream is acquired within a period.
  • the first BIER multicast message further includes a third identifier, and the third identifier is used to indicate that the first BIER multicast message is used for determining Delayed message; the processor is configured to obtain the reception time of the first BIER multicast message and/or the first BIER multicast message according to the first identifier and the third identifier Send time.
  • each BIER multicast message in the at least one BIER multicast message includes the stream identifier; from the at least one BIER multicast message Determine the second BIER multicast message; add the first identifier and the third identifier to the second BIER multicast message to obtain the first BIER multicast message.
  • the first BIER multicast message further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes receiving the first BIER multicast The inbound interface identifier of the packet and/or the outbound interface identifier for sending the first BIER multicast packet; the processor is configured to acquire and receive the first BIER according to the first identifier and the second identifier The identifier of the inbound interface identifier of the multicast packet and/or the identifier of the outbound interface identifier for sending the first BIER multicast packet.
  • the processor when the first node device is a head node device on the forwarding path of the first BIER multicast packet in the multicast domain, the processor , Also used to obtain a second BIER multicast message, the second BIER multicast message including the stream identifier; adding the first identifier and the fourth identifier to the second BIER multicast message, Obtain the first BIER multicast message.
  • the first identifier is carried in a BIER packet header of the first BIER multicast packet.
  • the first identifier is carried in a TLV field of the BIER packet header.
  • the stream identifier is determined according to the multicast source address and the multicast group address of the first BIER multicast packet.
  • the transmitter is further configured to send the first BIER multicast to the next-hop node device on the forwarding path of the first BIER multicast packet Message.
  • a management device in a fourth aspect, has the function of realizing the behavior of the management device in the foregoing method.
  • the functions can be implemented based on hardware, or implemented by corresponding software based on hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the management device includes a processor and an interface, and the processor is configured to support the management device to perform corresponding functions in the foregoing method.
  • the interface is used to support communication between the management device and the first node device, to send information or instructions involved in the above method to the first node device, or to receive information or instructions involved in the above method from the node device indicated by the first identifier Information or instructions.
  • the management device may also include a memory, which is used for coupling with the processor and stores program instructions and data necessary for the management device.
  • the management device includes a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to guide the system to start, and the management device is guided to enter a normal operating state. After the management device enters the normal operating state, the application program and the operating system are run in the random access memory, so that the processor executes the first aspect or the method in any possible implementation manner of the first aspect.
  • the management device includes: a processor, configured to obtain a first correspondence, where the first correspondence is a correspondence between a stream identifier and a first identifier, the stream identifier is an identifier of a BIER multicast stream, and The first identifier is used to indicate the node device that detects the BIER multicast stream and sends corresponding detection data on the forwarding path of the BIER multicast stream; the transmitter is used to send the node device to the first node device The first correspondence.
  • the node device indicated by the first identifier is all nodes in the BIER multicast domain on the forwarding path of the BIER multicast stream; or, the first identifier The indicated node device is the head node device and all tail node devices on the forwarding path of the BIER multicast stream in the BIER multicast domain.
  • the node device indicated by the first identifier is the head node device and the designated tail node on the forwarding path of the BIER multicast stream in the BIER multicast domain Device; or, the node device indicated by the first identifier is the head node device in the BIER multicast domain on the forwarding path of the BIER multicast stream, the designated tail node device, and the head node device and The intermediate node device between the designated tail node devices; the sending unit is further configured to send the identification of the designated tail node device to the first node device.
  • the first correspondence relationship further includes a second identifier, and the second identifier is used to indicate that the detection data includes the BIER received within a preset period.
  • the first correspondence further includes a third identifier, and the third identifier is used to indicate that the detection data includes the BIER multicast packet in the BIER multicast stream. The time when the text was received and/or sent.
  • the first correspondence further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes receiving the BIER multicast in the BIER multicast stream.
  • the management device further includes: a receiver, configured to receive detection data from a node device indicated by the first identifier; and the processor, further configured to receive The detection data detects the BIER multicast stream.
  • a computer-readable storage medium including instructions, which when run on a computer, cause the computer to execute the foregoing multicast stream detection method.
  • a network system in a sixth aspect, includes a first node device and a management device, the first node device is the aforementioned first node device, and the management device is the aforementioned management device.
  • Figure 1 is a schematic structural diagram of a multicast stream detection system provided by an embodiment of the application.
  • FIG. 2 is a flowchart of a method for detecting a multicast stream according to an embodiment of the application
  • FIG. 3 is a schematic diagram of the format of a BIER message header provided by an embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a first node device 400 provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of the hardware structure of the first node device 500 according to an embodiment of the application.
  • FIG. 6 is a schematic structural diagram of a management device 600 provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of the hardware structure of a management device 700 provided by an embodiment of the application.
  • the embodiments of the present application provide a method, device, and system for detecting a multicast stream, which are used to detect the BIER multicast stream and improve the reliability of BIER multicast stream transmission.
  • FIG. 1 is a schematic structural diagram of a multicast stream detection system provided by an embodiment of the application.
  • the multicast stream detection system provided by the embodiment of the present application includes a server 101, a terminal device 101, a terminal device 102, a terminal device 103, a node device 201, a node device 202, a node device 203, a node device 204, and a node device.
  • the server 101 is connected to the node device 201, the node device 201 is connected to the node device 202 and the node device 203, the node device 202 is connected to the node device 204 and the node device 205, and the node device 203 is connected to the node device 206 and the node device 207.
  • the terminal device 101 is connected to the node device 204, the terminal device 102 is connected to the node device 205, and the terminal device 103 is connected to the node device 207.
  • the management device 301 is connected to the node device 201-the node device 207.
  • the server 101 may be used to generate a unicast stream such as a video stream and an image stream, for example.
  • the terminal device 101, the terminal device 102, and the terminal device 103 are also referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), terminal, etc., which are a kind of user equipment A device that provides voice and/or data connectivity, or a chip set in the device, for example, a handheld device with a wireless connection function, a vehicle-mounted device, etc.
  • terminal devices are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented Augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid)
  • the management device 301 may be, for example, a device such as a controller.
  • the node device 201, the node device 202, the node device 203, the node device 204, the node device 205, the node device 206, and the node device 207 may be forwarding devices such as routers and switches, for example.
  • the aforementioned node device is a router, it can be called a BIER forwarding router (bit-forwarding router, BFR).
  • the node device 201 and the node device 207 together constitute a BIER multicast domain.
  • the BIER multicast domain is a domain for forwarding BIER packets, and it is an administrative domain.
  • the edge node device (node device 201) in the BIER multicast domain connected to the multicast source node device can be a BIER forwarding ingress router (bit-forwarding ingress router, BFIR), and the terminal device ( For example, the terminal device 101, the terminal device 102, and the terminal device 103 in FIG.
  • edge node devices such as the node device 204, the node device 205, the node device 206, and the node device 207) for the BIER forwarding egress router (bit-forwarding).
  • egress router BFIR
  • Each edge node device in the BIER multicast domain can be identified by a bit in a bit string.
  • the edge node device in FIG. 1 includes node device 201, node device 204, node device 205, node device 206, and node device 207, then the bit string of node device 201 can be 00001, and the bit string of node device 204 can be 00010
  • the bit string of the node device 205 may be 00100
  • the bit string of the node device 206 may be 01000
  • the bit string of the node device 207 may be 10000.
  • Node devices in the BIER multicast domain can learn the complete BIER neighbor table by flooding.
  • Each directly connected neighbor in the neighbor table corresponds to an entry.
  • the content of the table entry includes the identification of the edge node device that the directly connected neighbor is reachable. .
  • the neighbor table of the node device 201 can refer to the example in Table 1:
  • Node device 204 Node device 204 00010 Node device 205 Node device 205 00100
  • the head node device of the BIER multicast domain receives a unicast packet from the multicast source node (ie, server 101), and converts the unicast packet into a BIER multicast packet .
  • the header of the BIER multicast message carries the bit string of the destination node.
  • the destination nodes are, for example, the node device 204, the node device 205, and the node device 207, then the bit string of the destination node is 10110.
  • the node device used to forward the BIER multicast message searches the neighbor table according to the bit string of the destination node in the header of the message, and the BIER group is based on the number of neighbor nodes corresponding to the destination node.
  • the broadcast message is copied, and each neighbor node copies one copy.
  • the bit string of the destination node in the header of the copied BIER multicast message is modified, and the copied BIER multicast message is distributed to the corresponding neighbor nodes after the modification.
  • the bit string of the destination node in the header of the BIER multicast packet generated by the node device 201 is, for example, 10110
  • the destination node corresponding to the BIER multicast packet is the node device 204 and the node device 205 through the lookup table 1.
  • the neighbor nodes corresponding to these destination nodes are node device 202 and node device 203, then node device 201 copies two BIER multicast packets, one of which is sent to node device 202 and the other is to node device 203 send.
  • the bit string of the destination node included in the header of the BIER multicast message sent to the node device 202 is 00110; because the node device 203 corresponds to The destination node is the node device 207, so the bit string of the destination node included in the header of the BIER multicast message sent to the node device 203 is 10000.
  • the node device 202 After the node device 202 receives the BIER multicast message from the node device 201, it looks up in Table 2 and learns that the destination nodes corresponding to the BIER multicast message are the node device 204 and the node device 205, and both node devices are The node device 202 is a neighbor node, therefore, the node device 202 copies the received BIER multicast message in two copies, one copy is sent to the node device 204, and the other copy is sent to the node device 205.
  • the bit string of the destination node of the BIER multicast message sent to the node device 204 is 00010
  • the bit string of the destination node of the BIER multicast message sent to the node device 205 is 00100.
  • the node device 204 After the node device 204 receives the BIER multicast message from the node device 202, it converts the BIER multicast message into a unicast message and sends it to the terminal device 101; the node device 205 receives the BIER multicast message from the node device 202 After the message, the BIER multicast message is converted into a unicast message and sent to the terminal device 102.
  • the node device 203 After the node device 203 receives the BIER multicast message from the node device 201, it looks up in Table 3 and learns that the destination node corresponding to the BIER multicast message is the node device 207, and the node device is the neighbor node of the node device 203, Therefore, the node device 203 copies the received BIER multicast message and sends it to the node device 207.
  • the bit string of the destination node of the BIER multicast message sent to the node device 207 is 10000.
  • the node device 207 After the node device 207 receives the BIER multicast message from the node device 203, it converts the BIER multicast message into a unicast message, and sends it to the terminal device 103.
  • the BIER multicast domain is a management domain, which may include, for example, all forwarding nodes between the multicast source node and the terminal device, or only a part of the forwarding nodes.
  • the BIER multicast domain may include a total of 7 node devices of node device 201-node device 207, or may only include node device 202, node device 204, and node device 205, for example.
  • the BIER multicast domain in FIG. 1 mentioned below includes node device 201-node device 207.
  • node devices with different roles have slightly different methods for detecting multicast streams.
  • the following will detect the multicast streams performed by the head node device, intermediate node device, and tail node device of the BIER multicast domain. Methods are introduced.
  • FIG. 2 is a flowchart of a method for detecting a multicast stream according to an embodiment of the application.
  • the head node device receives the first correspondence from the management device, where the first correspondence is the correspondence between the flow identifier and the first identifier.
  • the head node device is, for example, the node device 201 shown in FIG. 1
  • the management device is, for example, the management device 301 shown in FIG. 1.
  • the stream identifier is the identifier of the multicast stream, and is used to identify the multicast stream.
  • the stream identifier may be the multicast source address and the multicast group address of the multicast stream, and the stream identifier may also be the hash value of the multicast source address and the multicast group address, etc., in the embodiment of the present application
  • the first identifier is used to indicate a node device that detects the multicast stream and sends corresponding detection data on the forwarding path of the multicast stream corresponding to the stream identifier.
  • the node device indicated by the first identifier may be all nodes on the forwarding path of the multicast stream in the BIER multicast domain.
  • the BIER multicast domain all nodes on the forwarding path of the multicast stream whose bit string of the destination node is 10110 are node equipment 201, node equipment 202, node equipment 203, node equipment 204, and node equipment. 205 and node equipment 207.
  • the node device indicated by the first identifier may be the head node device and all tail node devices on the forwarding path of the multicast stream in the BIER multicast domain.
  • the head node device on the forwarding path of the multicast stream whose bit string of the destination node is 10110 is node device 201
  • all tail node devices are node device 204, node device 205, and Node device 207.
  • the node device indicated by the first identifier is the head node device and the designated tail node device on the forwarding path of the multicast stream in the BIER multicast domain.
  • the designated tail node device is one or more tail node devices among all tail node devices on the forwarding path. Taking FIG. 1 as an example, in the BIER multicast domain, the designated tail node device on the forwarding path of the multicast stream whose bit string of the destination node is 10110 is, for example, the node device 204.
  • the node device indicated by the first identifier is the head node device in the BIER multicast domain on the forwarding path of the multicast stream, the designated tail node device, and the head node device and the The intermediate node device between the designated tail node devices.
  • the head node device on the forwarding path of the multicast stream whose bit string of the destination node is 10110 is node device 201
  • the designated tail node device is, for example, node device 204.
  • the node device is, for example, the node device 202.
  • the management device When the node device indicated by the first identifier is the third possible implementation manner and the fourth possible implementation manner, the management device also needs to send the identification of the designated node device to the head node device, for example, the designated node device Bit string.
  • the first correspondence sent by the management device to the head node device may further include indicating that the detection data includes packet loss information, delay information, and/or topology information for detecting the multicast flow corresponding to the flow identifier To realize the detection of packet loss information, delay information and/or topology information of the multicast stream.
  • the detection data used to detect the packet loss information of the multicast stream corresponding to the stream identifier may include the number of BIER multicast packets and/or the total number of bytes of the BIER multicast packets in a preset period.
  • the head node device obtains the BIER multicast message S1, and the BIER multicast message S1 includes the stream identifier.
  • the head node device can receive a unicast message from a multicast source node and convert the unicast message into a BIER multicast message S1.
  • the stream identifier included in the BIER multicast message S1 can be obtained from the multicast source address and the multicast group address of the BIER multicast message S1.
  • S202 may be executed after S201, and may be executed before S201, which is not specifically limited in the embodiment of the present application.
  • the head node device obtains the corresponding first identifier according to the flow identifier in the BIER multicast message S1 and the first correspondence, and adds the first identifier to the BIER multicast message S1 to obtain the BIER multicast message S2.
  • the first identifier may be carried in the extended type-length-value (TLV) field of the BIER header of the BIER multicast message S1.
  • TLV extended type-length-value
  • the BIER message header includes the following fields: the specified extension header (Next Header) field, the total byte length of the extension header (Hdr Ext Len) field, and the option type (Option Type) 1 (recommended in the draft OX70) field, the total byte length of option type 1 (Option Length) field, the non-MPLS BIER header (Non-MPLS BIER Header) field, the option type (Option Type) 2 field, the total byte length of option type 2 (Option Length) Length) field, reserved (Reserve) field and E2E field.
  • the Option Type 2 field is the type of the extended TLV, and its value is, for example, 0x70.
  • the Option Length field of option type 2 is the length of the extended TLV.
  • the E2E field is the value of the extended TLV and is used to carry the first identifier.
  • the value of the E2E field is different, which can be used to indicate that the first identifier is different.
  • the node device indicated by the first identifier is all the nodes in the BIER multicast domain on the forwarding path of the BIER multicast packet S2;
  • the value of the E2E field is 1, it means The node device indicated by the first identifier may be the head node device and all tail node devices on the forwarding path of the BIER multicast packet S1 in the BIER multicast domain; when the value of the E2E field is 2, it represents the first identifier
  • the indicated node device is the head node device and the designated tail node device on the forwarding path of the BIER multicast packet S2 in the BIER multicast domain; when the value of the E2E field is 3, it indicates that the first identifier indicates The node device is the head node device on the forwarding path of the BIER multicast message S2 in the BIER multicast domain, the designated tail node
  • the value of the extended TLV field may also include a list of node device identifiers
  • the node device identification list is used to indicate the designated tail node devices on the forwarding path of the BIER multicast packet S2 in the BIER multicast domain.
  • the node device identification list includes the identification of one or more designated tail node devices, for example, a bit string of the tail node device.
  • the extended TLV field also includes the OAM BitString field, and the OAM BitString field is used to carry the bit string of the designated node device.
  • the OAM BitString field can occupy an integer multiple of 32 bits.
  • the head node device specifically obtains can be configured in the head node device in advance, or it can be issued by the management device. If it is the latter, the first correspondence sent by the management device to the head node device further includes: an identifier for indicating that the detection data includes packet loss information of the multicast stream corresponding to the flow identifier, then the head node device A second identifier may be added to the BIER multicast message S1, that is, the BIER multicast message S2 also includes a second identifier, and the second identifier indicates that the detection data includes the group received within a preset period.
  • the statistical information of the BIER multicast message of the broadcast, the statistical information includes the number of the BIER multicast message and/or the total number of bytes of the BIER multicast message.
  • the extended TLV of the BIER header of the BIER multicast message S2 may also include a P field and a period field.
  • the P field may occupy 1 bit and the period field may occupy 3 bits.
  • the P field may be used to carry the second identifier.
  • the value of the P field of the BIER multicast packet in the same preset period is the same, and the value of the P field in the BIER multicast packet of two adjacent preset periods is different. For example, in the first preset period, the value of the P field in the BIER multicast message obtained by the head node device is all 1, and in the second preset period, the value of the BIER multicast message obtained by the head node is 1.
  • the value of the P field is 0.
  • the period field can be used to carry the preset period. Different values of the period field may indicate different preset periods. For example, a value of 0 in the period field indicates that the preset period is 100 milliseconds; a value of 1 in the period field indicates that the preset period is 1 second; a value of 2 in the period field indicates that the preset period is 10 seconds; a value of 3 in the period field Indicates that the preset period is 30 seconds; a value of 4 in the period field indicates that the preset period is 1 minute; a value of 5 in the period field indicates that the preset period is 5 minutes.
  • the head node device may multicast in the BIER A third identifier is added to the message S1, that is, the BIER multicast message S2 also includes a third identifier, and the third identifier is used to indicate whether the BIER multicast message S2 is a message for determining the delay.
  • the extended TLV of the BIER header of the BIER multicast message S2 may also include the D field.
  • the value of the D field indicates whether the BIER multicast message S2 is a message used to determine the delay, for example, When the D field is 1, it means that the BIER multicast message S2 is a message used to determine the delay; when the D field is 0, it means that the BIER multicast message S2 is not a message used to determine the delay.
  • the management device can obtain the delay information of the multicast stream by obtaining the sending time and/or receiving time of one or more BIER multicast packets. If the BIER multicast message S2 is a message used to determine the delay, the value of the D field in the BIER multicast message S2 is different from the value of the D field of other multicast messages in the same multicast stream.
  • the head node device may determine from at least one BIER multicast packet obtained in the preset period A BIER multicast message used to determine the delay, and a second identifier is added to the BIER multicast message.
  • the first BIER multicast message obtained by the head node device in each preset period is a message used to determine the delay
  • the value of the D field in the BIER multicast message can be 1
  • the head node device may broadcast the multicast message in the BIER A fourth identifier is added to the message S1, that is, the BIER multicast message S2 includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes the inbound interface identifier for receiving the BIER multicast message S2 and/or sending the The outbound interface identifier of the BIER multicast packet S2.
  • the extended TLV of the BIER header of the BIER multicast message S2 may also include a T field.
  • the T field may occupy 1 bit and is used to carry the fourth identifier. For example, when the value of the T field is 1, it means that the node device indicated by the first identifier needs to send to the management device the inbound interface identifier for receiving the BIER multicast packet S2 and/or for sending the BIER multicast packet S2 Outbound interface identifier.
  • the value of the T field may indicate that the node device indicated by the first identifier needs to periodically send and receive the BIER multicast report to the management device using the value of the preset period field.
  • inbound interface identification and/or outbound interface identification may not be sent periodically, but sent after changes.
  • the head node device determines, according to the first identifier in the BIER multicast message S2, that it needs to detect the multicast stream to which the BIER multicast message S2 belongs and sends corresponding detection data.
  • the head node device may, for example, read the value of the E2E field in the BIER multicast message S2 to determine whether it is necessary to detect the multicast stream to which the BIER multicast message S2 belongs and send corresponding detection data.
  • the four possible implementations of the node device indicated by the first identifier include the head node device, so the head node device needs to detect and check the multicast stream to which the BIER multicast packet S2 belongs. Send the corresponding detection data.
  • the head node device obtains the detection data of the multicast stream and sends the detection data to the management device.
  • the head node device when the head node device determines according to the first identifier in the BIER multicast message S2 that it needs to detect the multicast stream to which the BIER multicast message S2 belongs and send corresponding detection data, the head node device may Obtain the detection data of the multicast stream and send the detection data to the management device.
  • the head node device may also count the BIER multicast messages of the multicast stream to which the BIER multicast message S2 sent in the preset period belongs according to the indication of the second identifier.
  • the number and/or total number of bytes are sent to the management device. For example, if the header of the BIER multicast message S2 includes the P field and the period field, and the value of the period field is 1, then in the first second, the head node device counts the BIER multicast messages sent by the P field of 1 In the second second, the head node device counts the number and/or total number of bytes of BIER multicast packets sent with a P field of 0. In the third second, the header The node device counts the number and/or total number of bytes of BIER multicast packets sent with a P field of 1.
  • the head node device may also obtain the BIER according to the indication of the third identifier.
  • the sending time of the multicast message S2 and sending it to the management device For example, if the header of the BIER multicast message S2 includes the D field, and the value of the D field is 1, then the head node device can obtain the sending time of the BIER multicast message S2.
  • the fourth identifier is used to indicate that the detection data includes the identifier of the inbound interface for receiving the BIER multicast message S2 and/or the identifier for sending the BIER multicast message S2
  • the head node device may also obtain the outbound interface identifier for sending the BIER multicast packet S2 according to the indication of the fourth identifier, and send it to the management device. For example, if the T field is included in the header of the BIER multicast message S2, and the value of the T field is 1, then the head node device can obtain the outbound interface identifier of the BIER multicast message S2.
  • the head node device may periodically obtain the outbound interface identifier of the BIER multicast message in the multicast stream and send it to the management device.
  • the head node device can compare the outbound interface identifier of the BIER multicast packet S2 with the outbound interface identifier of the previous BIER multicast packet that includes the fourth identifier and belongs to the same multicast stream. Yes, if the two are different, the head node device can obtain the outbound interface identifier of the BIER multicast packet and send it to the management device.
  • the head node device sends the BIER multicast packet S2 to the next-hop node device on the forwarding path of the BIER multicast packet S2 in the BIER multicast domain.
  • the next hop node on the forwarding path of the BIER multicast packet S2 can be the node device 202 or the node device 203, depending on the BIER multicast packet S2
  • the carried bit string used to identify the destination node can be the node device 202 or the node device 203, depending on the BIER multicast packet S2
  • the carried bit string used to identify the destination node can be the node device 202 or the node device 203, depending on the BIER multicast packet S2
  • the carried bit string used to identify the destination node is the head node device 201.
  • S206 may be executed after S205, or may be executed before S205 and after S204.
  • the BIER multicast message S2 is obtained by adding the first identifier to the BIER multicast message S1, so that the node device indicated by the first identifier can obtain the multicast stream to which the BIER multicast message S2 belongs
  • the corresponding detection data is sent to the management device, and the node device not indicated by the first identifier may not send it, which not only realizes the detection of the multicast stream, but also saves bandwidth.
  • the BIER multicast message S2 may also include one or more of the second identifier, the third identifier, and the fourth identifier, so as to realize the detection of packet loss information, delay information, and topology information of the multicast stream.
  • the following describes the method for detecting a multicast stream performed by an intermediate node device according to an embodiment of the present application in conjunction with FIG. 2.
  • the method includes the following steps:
  • the intermediate node device receives the BIER multicast message S2, and the BIER multicast message S2 includes the flow identifier and the first identifier.
  • the intermediate node device determines whether there is a node device identification list in the BIER multicast message S2 according to the first identifier, if yes, execute S305; if not, execute S307 .
  • the intermediate node device determines whether the identifier of the destination node of the BIER multicast message S2 is in the node device identifier list, if yes, execute S306 and S307; if not, execute S307.
  • the intermediate node device can determine whether the node device identification list includes the identification of the destination node of the BIER multicast message S2 by obtaining the identification of the destination node in the BIER multicast message S2. If so, it indicates that the BIER multicast
  • the destination node of the message S2 belongs to the specified tail node device, and the intermediate node device is an intermediate node device between the head node device and the specified tail node device, and it needs to obtain the detection data of the multicast stream and send it to the management device.
  • the node device 202 determines that the bit string of the destination node carried in the BIER multicast message S2 is 00110, that is, the identifier of the destination node whose bit string is 00010 is in In the node identification list, it indicates that the node device 204 is the designated tail node device, and the node device 202 is an intermediate node device between the node device 201 and the node device 204.
  • the node device 202 determines that the bit string of the destination node carried in the BIER multicast message S2 is 10000, then it means that the node device 207 is not the designated tail node device, and the node device 202 is not the one between the node device 201 and the node device 207. Intermediate node equipment.
  • the intermediate node device obtains the detection data of the multicast stream and sends the detection data to the management device.
  • what detection data the intermediate node device specifically obtains can be configured in the intermediate node device in advance, or can be determined according to the BIER multicast message S2.
  • the intermediate node device can count the BIER multicast messages of the multicast stream to which the BIER multicast message S2 belongs, according to the indication of the second identifier, in the preset period. The number and/or total number of bytes are sent to the management device.
  • the intermediate node device can also obtain according to the indication of the third identifier The receiving time and/or sending time of the BIER multicast message S2, and sending it to the management device.
  • the intermediate node device can also obtain the inbound interface identifier for receiving the BIER multicast packet S2 and/or the outbound interface for sending the BIER multicast packet S2 according to the indication of the fourth identifier. Identify and send to the management device.
  • the intermediate node device sends the BIER multicast packet S2 to the next-hop node device on the forwarding path of the BIER multicast packet S2 in the BIER multicast domain.
  • the intermediate node device forwarding the BIER multicast message S2 actually needs to copy and forward the BIER multicast message S2, as mentioned above, but for the sake of simplicity of description, in the embodiment of this application Zhongdu is abbreviated as forwarding BIER multicast message S2.
  • the intermediate node device For the intermediate node device, according to the first identification or the first identification and the node device identification list, it is determined whether the detection data needs to be acquired and sent to the management device. If needed, the detection data is acquired and sent; if not, it is not sent. Not only realizes the detection of multicast streams, but also saves bandwidth.
  • the BIER multicast message S2 may also include one or more of the second identifier, the third identifier, and the fourth identifier, so as to realize the detection of packet loss information, delay information, and topology information of the multicast stream.
  • the following describes a method for detecting a multicast stream performed by a tail node device provided by an embodiment of the present application in conjunction with FIG. 2.
  • the method includes the following steps:
  • the tail node device receives the BIER multicast message S2, and the BIER multicast message S2 includes the stream identifier and the first identifier.
  • S402 When the node device indicated by the first identifier is all the nodes in the BIER multicast domain on the forwarding path of the BIER multicast packet S2, or the node device indicated by the first identifier is in the BIER multicast domain and is in the BIER multicast domain.
  • the tail node device executes S404.
  • the tail node device determines that the identification of the tail node device is in the node device identification list of the BIER multicast message S2, it indicates that the tail node device is the designated tail node device and needs to obtain the detection data and direction of the multicast stream.
  • the management device sends the detection data; if not, it means that the tail node device is a designated tail node device and does not need to obtain the detection data of the multicast stream and send the detection data to the management device.
  • the tail node device obtains the detection data of the multicast stream and sends the detection data to the management device.
  • what detection data the tail node device specifically obtains can be configured in the tail node device in advance, or can be determined according to the BIER multicast message S2.
  • the tail node device can count the number of BIER multicast messages of the multicast stream to which the BIER multicast message S2 belongs in the preset period according to the indication of the second identifier. The number and/or total number of bytes are sent to the management device.
  • the tail node device can also obtain it according to the indication of the third identifier The time when the BIER multicast packet S2 was received and sent to the management device.
  • the tail node device may also obtain the inbound interface identifier for receiving the BIER multicast message S2 according to the indication of the fourth identifier, and send it to the management device.
  • the tail node device can strip the header of the BIER multicast message S2, turn it into a unicast message, and send it to the terminal device.
  • the tail node device it is determined whether the detection data needs to be acquired and sent to the management device according to the first identification or the first identification and the node device identification list. If necessary, the detection data is acquired and sent; if not, it is not sent. Not only realizes the detection of multicast streams, but also saves bandwidth.
  • the BIER multicast message S2 may also include one or more of the second identifier, the third identifier, and the fourth identifier, so as to realize the detection of packet loss information, delay information, and topology information of the multicast stream.
  • the management device After introducing the multicast stream detection methods of the head node device, the intermediate node device, and the tail node device, the following describes how the management device processes the detection data sent by the node device:
  • the management device receives the detection data from the node device indicated by the first identifier, and detects the multicast stream according to the detection data.
  • the management device When the management device receives the number and/or total number of bytes of multicast packets sent within a preset period from the head node device, and the number of the same multicast stream received within the preset time period from the tail node device When the number of multicast packets and/or the total number of bytes are used, the management device can compare the two.
  • the management device also receives the number of multicast packets and/or the total number of bytes of the same multicast stream received or sent by the intermediate node device in the preset period, it can determine that the packet loss occurs in the packet. On which links or nodes where the text is forwarded, the fault can be located.
  • the management device When the management device receives the sending time of the BIER multicast packet S2 from the head node device, and the receiving time of the BIER multicast packet S2 from the tail node device, the management device can determine the difference between the sending time and the receiving time The difference determines the delay of the BIER multicast message S2. If the receiving time of the BIER multicast packet S2 comes from different tail node devices, the delay of the BIER multicast packet S2 on different forwarding paths can be determined according to the different tail node devices. If the delay on a certain forwarding path does not meet the requirements, you can stop using the forwarding path to forward the BIER multicast packet S2, or generate a new forwarding path to replace the forwarding path.
  • the management device When the management device receives the outgoing port ID of the BIER multicast packet S2 from the head node device, the ingress port ID and the outgoing port ID of the BIER multicast packet S2 from the intermediate node device, and the BIER group from the tail node device By broadcasting the ingress port identifier of the message S2, the management device can establish a topology for forwarding the BIER multicast message S2. When the above-mentioned ingress port identifier and/or egress port identifier changes, the management device can obtain the new topology in a timely manner.
  • the processing method of the detection data by the above-mentioned management device does not constitute a limitation to the technical solution of the present application, and those skilled in the art can design by themselves according to specific conditions.
  • FIG. 4 is a schematic structural diagram of a first node device 400 according to an embodiment of the application.
  • the first node device 400 shown in FIG. 4 can execute the corresponding steps performed by the first node device in the method of the foregoing embodiment.
  • the first node device 400 includes a processing unit 401, a sending unit 402, and a receiving unit 403.
  • the processing unit 401 is configured to obtain a first bit index to explicitly copy a BIER multicast packet, where the first BIER multicast packet includes a stream identifier and a first identifier, and the stream identifier is used to indicate the first BIER group The multicast stream to which the broadcast message belongs, and the first identifier is used to indicate a node device on the forwarding path of the first BIER multicast message that detects the multicast stream and sends corresponding detection data.
  • the processing unit 401 is further configured to determine whether to detect the multicast stream and send corresponding detection data according to the first identifier; in response to determining that the multicast stream needs to be detected according to the first identifier And sending corresponding detection data to obtain the detection data of the multicast stream.
  • the sending unit 402 is configured to send the detection data to the management device.
  • the node devices indicated by the first identifier are all nodes in the BIER multicast domain on the forwarding path of the first BIER multicast packet; or, the node devices indicated by the first identifier are all nodes The head node device and all tail node devices on the forwarding path of the first BIER multicast packet in the BIER multicast domain.
  • the first node device is a tail node device or an intermediate node device on the forwarding path of the first BIER multicast packet in the BIER multicast domain
  • the processing unit 401 is based on the An identifier determines whether to detect the multicast stream and sends corresponding detection data, including: the processing unit 401 is configured to determine the node device identifier in the first BIER multicast packet according to the first identifier List, the node device identification list is used to indicate the designated tail node device on the forwarding path of the first BIER multicast packet in the BIER multicast domain; and whether to determine whether it is correct according to the node device identification list
  • the multicast stream performs detection and sends corresponding detection data.
  • the node device identification list is a bit string of the designated tail node device.
  • the processing unit 401 is configured to: obtain a second BIER A multicast message, the second BIER multicast message includes the stream identifier; the first identifier is added to the second BIER multicast message according to the first correspondence to obtain the first BIER multicast message
  • the first correspondence is a correspondence between the flow identifier and the first identifier.
  • the first node device further includes: a receiving unit 403, configured to receive the first correspondence from the management device.
  • the first BIER multicast message further includes a second identifier, and the second identifier is used to indicate that the detection data includes the BIER multicast message of the multicast stream received within a preset period.
  • the statistical information includes the number of the BIER multicast packet and/or the total number of bytes of the BIER multicast packet; the processing unit 401 is configured to be in place according to the second identifier. Obtain the received statistical information of the BIER multicast packet of the multicast stream within the preset period.
  • the first BIER multicast message further includes the preset period.
  • the processing unit 401 is further configured to Acquire a second BIER multicast message within a period, the second BIER multicast message includes the stream identifier; add a first field and a second field to the second BIER multicast message, and the value of the address field For the first identifier, the value of the second field is a preset value corresponding to the preset period, and the value of the second field is used to indicate that the received Statistics of BIER multicast packets of a multicast stream.
  • the first BIER multicast message further includes a third identifier, and the third identifier is used to indicate that the first BIER multicast message is a message for determining delay; the processing unit 401, configured to obtain the receiving time of the first BIER multicast packet and/or the sending time of the first BIER multicast packet according to the first identifier and the third identifier.
  • the processing unit 401 is further configured to: Acquiring at least one BIER multicast message, each BIER multicast message in the at least one BIER multicast message includes the stream identifier; determining a second BIER multicast message from the at least one BIER multicast message; Add the first identifier and the third identifier to the second BIER multicast message to obtain the first BIER multicast message.
  • the first BIER multicast packet further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes an inbound interface identifier for receiving the first BIER multicast packet and/or sending The outbound interface identifier of the first BIER multicast packet; the processing unit 401 is configured to obtain the identifier of the inbound interface for receiving the first BIER multicast packet according to the first identifier and the second identifier The identifier and/or the identifier of the outbound interface identifier for sending the first BIER multicast packet.
  • the processing unit 401 is further configured to obtain the second BIER group Broadcast a message, the second BIER multicast message includes the flow identifier; add the first identifier and the fourth identifier to the second BIER multicast message to obtain the first BIER multicast message Text.
  • the first identifier is carried in a BIER packet header of the first BIER multicast packet.
  • the first identifier is carried in the TLV field of the BIER packet header.
  • the stream identifier is determined according to the multicast source address and the multicast group address of the first BIER multicast packet.
  • the sending unit 402 is further configured to send the first BIER multicast packet to a next-hop node device on the forwarding path of the first BIER multicast packet.
  • the first node device 400 shown in FIG. 4 can execute the corresponding steps performed by the first node device in the method of the foregoing embodiment.
  • the first node device of the BIER multicast domain can determine whether it needs to obtain the detection data of the multicast stream and send it to the management device according to the first identifier, so as to realize the detection of the BIER multicast stream.
  • FIG. 5 is a schematic diagram of the hardware structure of the first node device 500 according to an embodiment of the application.
  • the first node device 500 shown in FIG. 5 can execute the corresponding steps performed by the first node device in the method of the foregoing embodiment and the function of the first node device 400 in the embodiment shown in FIG. 4.
  • the first node device 500 includes a processor 501, a memory 502, an interface 503, and a bus 504.
  • the interface 503 may be implemented in a wireless or wired manner, and specifically may be a network card.
  • the aforementioned processor 501, memory 502, and interface 503 are connected through a bus 504.
  • the interface 503 may specifically include a transmitter and a receiver, which are used to send and receive information between the first node device and the previous-hop network device or the next-hop network device of the first node device in the foregoing embodiment; and/or use Information is sent and received between the management devices in the above embodiments.
  • the interface 503 is used to support receiving the first correspondence sent by the management device; used to receive the first BIER multicast packet sent by the previous-hop network device of the first node device; and/or use Send a first BIER multicast message to the next-hop network device of the first node device.
  • the interface 503 is used to support the processes S201, S205, and S206 in FIG. 2.
  • the processor 501 is configured to execute the processing performed by the first node device in the foregoing embodiment. For example, the processor 501 is configured to determine whether to detect the multicast stream and send corresponding detection data according to the first identifier; in response to the first node device determining that it needs to check according to the first identifier The multicast stream detects and sends corresponding detection data, the first node device obtains the detection data of the multicast stream and sends the detection data to the management device; and/or is used for the technology described herein Other processes. As an example, the processor 501 is configured to support the processes S202-S204 in FIG. 3.
  • the memory 502 includes an operating system and application programs, and is used to store programs, codes, or instructions.
  • the memory 502 may include a read-only memory (English: Read-only Memory, abbreviation: ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM includes a basic input/output system (English: Basic Input/Output System, abbreviation: BIOS) or an embedded system;
  • BIOS Basic Input/Output System
  • the RAM includes an application program and an operating system.
  • FIG. 5 only shows a simplified design of the first node device 500.
  • the first node device may include any number of interfaces, processors or memories.
  • FIG. 6 is a schematic structural diagram of a management device 600 provided by an embodiment of the application.
  • the management device 600 shown in FIG. 6 can execute the corresponding steps performed by the management device in the method of the foregoing embodiment.
  • the management device 600 includes a processing unit 601, a sending unit 602, and a receiving unit 603.
  • the processing unit 601 is configured to obtain a first correspondence, where the first correspondence is a correspondence between a stream identifier and a first identifier, the stream identifier is the identifier of the BIER multicast stream, and the first identifier is used to indicate On the forwarding path of the BIER multicast stream, a node device that detects the BIER multicast stream and sends corresponding detection data; the sending unit 602 is configured to send the first correspondence to the first node device.
  • the node device indicated by the first identifier is all nodes in the BIER multicast domain on the forwarding path of the BIER multicast stream; or, the node device indicated by the first identifier is the BIER group The head node device and all tail node devices on the forwarding path of the BIER multicast stream in the broadcast domain.
  • the node device indicated by the first identifier is the head node device and the designated tail node device on the forwarding path of the BIER multicast stream in the BIER multicast domain; or, the first identifier indicates The node device in the BIER multicast domain is the head node device on the forwarding path of the BIER multicast stream, the designated tail node device, and between the head node device and the designated tail node device.
  • the intermediate node device; the sending unit is further configured to send the identification of the designated tail node device to the first node device.
  • the first correspondence further includes a second identifier, and the second identifier is used to indicate that the detection data includes information about the BIER multicast packet of the BIER multicast stream received within a preset period. Statistics.
  • the first correspondence further includes a third identifier, and the third identifier is used to indicate that the detection data includes the reception time and/or the transmission time of the BIER multicast packet in the BIER multicast stream.
  • the first correspondence relationship further includes a fourth identifier, and the fourth identifier is used to indicate that the detection data includes an inbound interface identifier for receiving BIER multicast packets in the BIER multicast stream and/or sending The outbound interface identifier of the BIER multicast packet.
  • the management device further includes: a receiving unit 603, configured to receive detection data from a node device indicated by the first identifier; and the processing unit 601, further configured to perform data processing on the BIER according to the detection data.
  • the multicast stream is tested.
  • the management device 600 shown in FIG. 6 can execute the corresponding steps performed by the management device in the method of the foregoing embodiment.
  • the management device 600 delivers the first correspondence to the first node device, and the first node device adds the first identifier to the BIER multicast packet corresponding to the flow identifier, so that the node device indicated by the first identifier receives the BIER multicast packet.
  • the detection data of the multicast stream can be obtained and sent to the management device to realize the detection of the BIER multicast stream.
  • FIG. 7 is a schematic diagram of the hardware structure of a management device 700 according to an embodiment of the application.
  • the management device 700 shown in FIG. 7 can execute the corresponding steps performed by the management device in the method of the foregoing embodiment and the functions of the management device 600 in the embodiment shown in FIG. 6.
  • the management device 700 includes a processor 701, a memory 702, an interface 703, and a bus 704.
  • the interface 703 may be implemented in a wireless or wired manner, and specifically may be a network card.
  • the aforementioned processor 701, memory 702, and interface 703 are connected through a bus 704.
  • the interface 703 may specifically include a transmitter and a receiver, which are used to send and receive information between the management device and the node device in the foregoing embodiment.
  • the interface 703 is used to support sending the first corresponding relationship to the first node device; and/or used to receive the detection data of the node device indicated by the first identifier.
  • the processor 701 is configured to execute the processing performed by the management device in the foregoing embodiment.
  • the processor 701 is configured to perform detection based on detection data.
  • the processor 701 is configured to support the processes S202-S204 in FIG. 3.
  • the memory 702 includes an operating system 7021 and an application program 7022 for storing programs, codes, or instructions.
  • the memory 702 may include a read-only memory (English: Read-only Memory, abbreviation: ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM includes a basic input/output system (English: Basic Input/Output System, abbreviation: BIOS) or an embedded system;
  • BIOS Basic Input/Output System
  • the RAM includes an application program and an operating system.
  • FIG. 7 only shows a simplified design of the management device 700.
  • the management device can include any number of interfaces, processors or memories.
  • the embodiment of the present application also provides a network system, including the first node device 500 and the management device 700 described above.
  • the embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the foregoing multicast stream detection method applied to the first node device 500.
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the foregoing multicast stream detection method applied to the management device 700.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical module division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be acquired according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each module unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software module unit.
  • the integrated unit is implemented in the form of a software module unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .
  • the functions described in the present invention can be implemented by hardware, software, firmware, or any combination thereof.
  • these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

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组播报文，第一BIER组播报文包括流标识和第一标识，流标识用于指示第一BIER组播报文所属的组播流，第一标识用于指示第一BIER组播报文的转发路径上、对组播流进行检测和发送相应的检测数据的节点设备；第一节点设备根据第一标识确定是否对组播流进行检测和发送相应的检测数据；响应于第一节点设备根据第一标识确定需要对组播流进行检测和发送相应的检测数据，第一节点设备获取组播流的检测数据和向管理设备发送检测数据。

Description

一种组播流检测方法、设备及系统
本申请要求于2019年10月18日提交的申请号为201910996012.7、发明名称为“一种组播报文处理方法、设备及系统”的中国专利申请的优先权和于2019年12月19日提交的申请号为201911320778.X、发明名称为“一种组播流检测方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，特别是涉及一种组播流检测方法、设备及系统。
背景技术
组播(Multicast)又称多目标广播、多播，是网络中一种在一个发送者和多个接收者之间进行通信的方法。组播技术即可以应用到点到多点的应用场景，例如媒体广播、事件通知、状态监控、数据收集、网络竞拍等，又可以应用到多点到多点的应用场景，例如多点会议、数据库同步等，所以受到很多开发者的重视。
位索引显式复制(bit indexed explicit replication，BIER)技术是组播技术的一种，具体用于构建组播发转发路径，该技术提出了一种构建组播分发树的组播技术架构，即满足了组播流量日益剧增的情况，又降低了运营的成本。在国际互联网工程任务组(the internet engineering task force，IETF)草案《draft-xie-bier-ipv6-encapsulation》中定义了在非多协议标签交换(multi-protocol label switching，MPLS)的互联网协议第6版(internet protocol version 6，IPv6)报文中增加BIER报文头，以在IPv6网络中实现传输BIER组播报文的目的。
但是，该协议并未定义BIER组播报文的操作维护管理(operation administration and maintenance，OAM)机制，即未规定如何实现对BIER组播流的检测，所以无法保障BIER组播流的传输可靠性。因而，目前急需提供一种BIER组播流的检测方法以实现对BIER组播流的检测。
发明内容
本申请实施例提供了一种组播流检测方法、设备及系统，实现对BIER组播流的检测。
第一方面，提供了一种组播流检测方法，所述方法应用于第一节点设备，该第一节点设备可以例如为路由器或交换机等。该方法具体包括如下步骤：首先，第一节点设备获取第一位索引显式复制BIER组播报文，所述第一BIER组播报文包括流标识和第一标识。所述流标识用于指示所述第一BIER组播报文所属的组播流，具体可以根据第一BIER组播报文的组播源地址和组播组地址进行确定。所述第一标识用于指示所述第一BIER组播报文的转发路径上、对所述组播流进行检测和发送相应的检测数据的节点设备。第一标识可以例如携带在所述第一BIER组播报文的BIER报文头中，具体可以携带在所述BIER报文头的TLV字段中。然后，所述第一节点设备根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据。响应于所述第一节点设备根据所述第一标识确定需要对所述组播流进行检测和发送相应的检测数据，所述第一节点设备获取所述组播流的检测数据，并且向管理设备发送所述检测数据，实现对组播流的检测。
在第一方面的一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的所有节点，也就是说，转发路径上的所有节点设备都需要向管理设备发送检测数据。
在第一方面的再一种可能的实现方式中，所述第一标识指示的节点设备为所述BIER组 播域中在所述第一BIER组播报文的转发路径上的头节点设备和所有尾节点设备。也就是说，只有转发路径上的头节点设备和所有尾节点设备需要向管理设备发送检测数据，当该节点设备为头节点设备或尾节点设备时，需要获取检测数据并向管理设备发送该检测数据。
在第一方面的又一种可能的实现方式中，当所述第一节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的尾节点设备或中间节点设备时，所述第一节点设备根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据，包括：所述第一节点设备根据所述第一标识在所述第一BIER组播报文中确定所述节点设备标识列表，所述节点设备标识列表用于指示所述BIER组播域中在所述第一BIER组播报文的转发路径上的被指定的尾节点设备。例如，所述节点设备标识列表为所述被指定的尾节点设备的比特串。所述第一节点设备根据所述节点设备标识列表确定是否对所述组播流进行检测和发送相应的检测数据。具体的，如果第一节点设备为是中间节点设备，且第一标识指示的节点设备为该BIER组播域中在该组播流的转发路径上的头节点设备、被指定的尾节点设备以及该头节点设备和该被指定的尾节点设备之间的中间节点设备，那么该第一节点设备可以确定第一BIER组播报文中目的节点的标识是否在节点设备标识列表中，如果是，则说明第一BIER组播报文的目的节点属于指定的尾节点设备，并且该中间节点设备为头节点设备与该指定的尾节点设备之间的中间节点设备，需要获取所述组播流的检测数据和向管理设备发送所述检测数据。如果第一节点设备为尾节点设备，且第一标识指示的节点设备包括被指定的尾节点设备，那么第一节点设备可以确定该第一节点设备的标识是否在节点设备标识列表中，如果是，则说明该尾节点设备为被指定的尾节点设备，需要获取所述组播流的检测数据和向管理设备发送所述检测数据。
在第一方面的又一种可能的实现方式中，当所述第一节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括如下步骤：所述第一节点设备获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；所述第一节点设备根据第一对应关系在所述第二BIER组播报文中添加所述第一标识，得到所述第一BIER组播报文，所述第一对应关系为所述流标识和所述第一标识的对应关系。其中，第一对应关系可以来自所述管理设备或者预先在头节点设备配置的。
在第一方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数。相应的，所述第一节点设备可以根据所述第二标识在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息并发送给管理设备，实现对组播流是否丢包的检测。
在第一方面的又一种可能的实现方式中，除了第二标识以外，所述第一BIER组播报文还可以包括所述预设周期。
在第一方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：所述第一节点设备在所述预设周期内获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识。所述第一节点设备在所述第二BIER组播报文中添加第一字段和第二字段，所述地址字段的值为所述第一标识，所述第二字段的值为与所述预设周期对应的预设值，所述第二字段的值用于指示在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。也就是说，如果 第一节点设备为头节点设备，那么第一节点设备可以通过在第二BIER组播报文中添加第一标识和第二标识，以得到第一BIER组播报文。
在第一方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第三标识，所述第三标识用于指示所述第一BIER组播报文为用于确定时延的报文。相应的，所述第一节点设备根据所述第一标识和所述第三标识获取所述第一BIER组播报文的接收时间和/或所述第一BIER组播报文的发送时间，并向管理设备发送，实现对组播流时延的检测。
在第一方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：首先，所述第一节点设备在预设周期内获取至少一个BIER组播报文，所述至少一个BIER组播报文中的每个BIER组播报文均包括所述流标识。其次，所述第一节点设备从所述至少一个BIER组播报文中确定第二BIER组播报文，所述第一节点设备在所述第二BIER组播报文中添加所述第一标识和所述第三标识，得到所述第一BIER组播报文。也就是说，如果第一节点设备为头节点设备，那么第一节点设备可以通过在第二BIER组播报文中添加第一标识和第三标识，以得到第一BIER组播报文。
在第一方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述第一BIER组播报文的入接口标识和/或发送所述第一BIER组播报文的出接口标识。相应的，所述第一节点设备可以根据所述第一标识和所述第二标识获取接收所述第一BIER组播报文的入接口标识的标识和/或发送所述第一BIER组播报文的出接口标识的标识，并向管理设备发送，实现对组播流拓扑信息的检测。
在第一方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：所述第一节点设备获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；所述第一节点设备在所述第二BIER组播报文中添加所述第一标识和所述第四标识，得到所述第一BIER组播报文。也就是说，如果第一节点设备为头节点设备，那么第一节点设备可以通过在第二BIER组播报文中添加第一标识和第四标识，以得到第一BIER组播报文。
在第一方面的又一种可能的实现方式中，所述方法还包括：所述第一节点设备向所述第一BIER组播报文的转发路径上的下一跳节点设备发送所述第一BIER组播报文，以实现对第一BIER组播报文的传输。
第二方面，提供了一种组播流检测方法，该方法应用于管理设备，该管理设备可以例如为控制器。所述方法包括如下步骤：首先，管理设备获取第一对应关系，所述第一对应关系为流标识和第一标识的对应关系，所述流标识为BIER组播流的标识，所述第一标识用于指示所述BIER组播流的转发路径上、对所述BIER组播流进行检测和发送相应的检测数据的节点设备。其次，所述管理设备向第一节点设备发送所述第一对应关系。第一节点设备可以根据该第一对应关系生成上述第一BIER组播报文，从而进一步实现对BIER组播流的检测。
在第二方面的一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备和所有尾节点设备。
在第二方面的再一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的头节点设备和被指定的尾节点设备；或，所述第一标 识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备、被指定的尾节点设备以及所述头节点设备和所述被指定的尾节点设备之间的中间节点设备。相应的，所述方法还包括：所述管理设备向第一节点设备发送所述被指定的尾节点设备的标识，以便第一节点设备生成上述携带有被指定的尾节点设备的标识的第一BIER组播报文。
在第二方面的又一种可能的实现方式中，所述第一对应关系还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述BIER组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数，以实现对BIER组播流的丢包信息的检测。
在第二方面的又一种可能的实现方式中，所述第一对应关系还包括第三标识，所述第三标识用于指示所述检测数据包括所述BIER组播流中BIER组播报文的接收时间和/或发送时间，以实现对BIER组播流的时延信息的检测。
在第二方面的又一种可能的实现方式中，所述第一对应关系还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述BIER组播流中BIER组播报文的入接口标识和/或发送所述BIER组播报文的出接口标识，以实现对BIER组播流的拓扑信息的检测。
在第二方面的又一种可能的实现方式中，所述方法还包括：所述管理设备接收来自所述第一标识指示的节点设备的检测数据；所述管理设备根据所述检测数据对所述BIER组播流进行检测，实现对所述BIER组播流检测的目的。
第三方面，提供了一种第一节点设备，所述第一节点设备具有实现上述方法中第一节点设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第一节点设备的结构中包括处理器和接口，所述处理器被配置为支持第一节点设备执行上述方法中相应的功能。所述接口用于支持第一节点设备与管理设备之间的通信，向管理设备发送上述方法中所涉及的信息或者指令，或者从管理设备接收上述方法中所涉及的信息或者指令。所述第一节点设备还可以包括存储器，所述存储器用于与处理器耦合，其保存第一节点设备必要的程序指令和数据。
在另一个可能的设计中，所述第一节点设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行第一节点设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导第一节点设备进入正常运行状态。在第一节点设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
具体的，处理器，用于获取第一位索引显式复制BIER组播报文，所述第一BIER组播报文包括流标识和第一标识，所述流标识用于指示所述第一BIER组播报文所属的组播流，所述第一标识用于指示所述第一BIER组播报文的转发路径上、对所述组播流进行检测和发送相应的检测数据的节点设备。所述处理器，还用于根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据；响应于根据所述第一标识确定需要对所述组播流进行检测和发送相应的检测数据，获取所述组播流的检测数据。发送器，用于向管理设备发送所述检测数据。
在第三方面的一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中 在所述第一BIER组播报文的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备和所有尾节点设备。
在第三方面的另一种可能的实现方式中，所述第一节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的尾节点设备或中间节点设备，所述处理器根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据，包括：所述处理器，用于根据所述第一标识在所述第一BIER组播报文中确定所述节点设备标识列表，所述节点设备标识列表用于指示所述BIER组播域中在所述第一BIER组播报文的转发路径上的被指定的尾节点设备；根据所述节点设备标识列表确定是否对所述组播流进行检测和发送相应的检测数据。
在第三方面的又一种可能的实现方式中，所述节点设备标识列表为所述被指定的尾节点设备的比特串。
在第三方面的又一种可能的实现方式中，当所述第一节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，用于：获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；根据第一对应关系在所述第二BIER组播报文中添加所述第一标识，得到所述第一BIER组播报文，所述第一对应关系为所述流标识和所述第一标识的对应关系。
在第三方面的又一种可能的实现方式中，所述第一节点设备还包括：接收器，用于接收来自所述管理设备的所述第一对应关系。
在第三方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数；所述处理器，用于根据所述第二标识在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
在第三方面的又一种可能的实现方式中，所述第一BIER组播报文还包括所述预设周期。
在第三方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于在所述预设周期内获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加第一字段和第二字段，所述地址字段的值为所述第一标识，所述第二字段的值为与所述预设周期对应的预设值，所述第二字段的值用于指示在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
在第三方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第三标识，所述第三标识用于指示所述第一BIER组播报文为用于确定时延的报文；所述处理器，用于根据所述第一标识和所述第三标识获取所述第一BIER组播报文的接收时间和/或所述第一BIER组播报文的发送时间。
在第三方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于在预设周期内获取至少一个BIER组播报文，所述至少一个BIER组播报文中的每个BIER组播报文均包括所述流标识；从所述至少一个BIER组播报文中确定第二BIER组播报文；在所述第二BIER组播报文中添加所述第一标识和所述第三标识，得到所述第一BIER组播报文。
在第三方面的又一种可能的实现方式中，所述第一BIER组播报文还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述第一BIER组播报文的入接口标识和/或发送所述第一BIER组播报文的出接口标识；所述处理器，用于根据所述第一标识和所述第二标识获取接收所述第一BIER组播报文的入接口标识的标识和/或发送所述第一BIER组播报文的出接口标识的标识。
在第三方面的又一种可能的实现方式中，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加所述第一标识和所述第四标识，得到所述第一BIER组播报文。
在第三方面的又一种可能的实现方式中，所述第一标识携带在所述第一BIER组播报文的BIER报文头中。
在第三方面的又一种可能的实现方式中，所述第一标识携带在所述BIER报文头的TLV字段中。
在第三方面的又一种可能的实现方式中，所述流标识根据所述第一BIER组播报文的组播源地址和组播组地址确定。
在第三方面的又一种可能的实现方式中，所述发送器，还用于向所述第一BIER组播报文的转发路径上的下一跳节点设备发送所述第一BIER组播报文。
第四方面，提供了一种管理设备，所述管理设备具有实现上述方法中管理设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，管理设备的结构中包括处理器和接口，所述处理器被配置为支持管理设备执行上述方法中相应的功能。所述接口用于支持管理设备与第一节点设备之间的通信，向第一节点设备发送上述方法中所涉及的信息或者指令，或者从第一标识指示的节点设备接收上述方法中所涉及的信息或者指令。所述管理设备还可以包括存储器，所述存储器用于与处理器耦合，其保存管理设备必要的程序指令和数据。
在另一个可能的设计中，所述管理设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行管理设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导管理设备进入正常运行状态。在管理设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
具体的，所述管理设备包括：处理器，用于获取第一对应关系，所述第一对应关系为流标识和第一标识的对应关系，所述流标识为BIER组播流的标识，所述第一标识用于指示所述BIER组播流的转发路径上、对所述BIER组播流进行检测和发送相应的检测数据的节点设备；发送器，用于向第一节点设备发送所述第一对应关系。
在第四方面的一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备和所有尾节点设备。
在第四方面的再一种可能的实现方式中，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的头节点设备和被指定的尾节点设备；或，所述第一标 识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备、被指定的尾节点设备以及所述头节点设备和所述被指定的尾节点设备之间的中间节点设备；所述发送单元，还用于向第一节点设备发送所述被指定的尾节点设备的标识。
在第四方面的又一种可能的实现方式中，所述第一对应关系还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述BIER组播流的BIER组播报文的统计信息。
在第四方面的又一种可能的实现方式中，所述第一对应关系还包括第三标识，所述第三标识用于指示所述检测数据包括所述BIER组播流中BIER组播报文的接收时间和/或发送时间。
在第四方面的又一种可能的实现方式中，所述第一对应关系还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述BIER组播流中BIER组播报文的入接口标识和/或发送所述BIER组播报文的出接口标识。
在第四方面的又一种可能的实现方式中，所述管理设备还包括：接收器，用于接收来自所述第一标识指示的节点设备的检测数据；所述处理器，还用于根据所述检测数据对所述BIER组播流进行检测。
第五方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述组播流检测方法。
第六方面，提供了一种网络系统，所述网络系统包括第一节点设备和管理设备，所述第一节点设备为上述第一节点设备，所述管理设备为上述管理设备。
附图说明
图1为本申请实施例提供的组播流检测系统的结构示意图；
图2为本申请实施例提供的组播流检测方法的流程图；
图3为本申请实施例提供的BIER报文头的格式示意图；
图4为本申请实施例提供的第一节点设备400的结构示意图；
图5为本申请实施例提供的第一节点设备500的硬件结构示意图；
图6为本申请实施例提供的管理设备600的结构示意图；
图7为本申请实施例提供的管理设备700的硬件结构示意图。
具体实施方式
本申请实施例提供了一种组播流检测方法、装置及系统，用于实现对BIER组播流的检测，提高BIER组播流传输的可靠性。
为方便理解，首先结合图1对本申请实施例的应用场景进行介绍。
图1为本申请实施例提供的组播流检测系统的结构示意图。在图1中，本申请实施例提供的组播流检测系统包括服务器101、终端设备101、终端设备102、终端设备103、节点设备201、节点设备202、节点设备203、节点设备204、节点设备205、节点设备206、节点设备207以及管理设备301。其中，服务器101与节点设备201连接，节点设备201分别与节点设备202和节点设备203连接，节点设备202分别与节点设备204和节点设备205连接，节点设备203分别与节点设备206以及节点设备207连接，终端设备101连接节点设备204，终端设备102连接节点设备205，终端设备103连接节点设备207。管理设备301连接节点设备201-节点设备207。
在本申请实施例中，服务器101例如可以用于生成视频流、图像流等单播流。
终端设备101、终端设备102和终端设备103又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、终端等，是一种向用户提供语音和/或数据连通性的设备，或，设置于该设备内的芯片，例如，具有无线连接功允许的手持式设备、车载设备等。目前，一些终端设备的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
管理设备301例如可以为控制器等设备。
在本申请实施例中，节点设备201、节点设备202、节点设备203、节点设备204、节点设备205、节点设备206以及节点设备207例如可以为路由器、交换机等转发设备。当上述节点设备为路由器时，可以被称为BIER转发路由器(bit-forwarding router，BFR)。
在本申请实施例中，节点设备201-节点设备207一起构成了BIER组播域(BIER domain)。BIER组播域是一个转发BIER报文的域，它是个管理域。BIER组播域中与组播源节点设备(例如图1中的服务器101)连接的边缘节点设备(节点设备201)可以为BIER转发入口路由器(bit-forwarding ingress router，BFIR)，与终端设备(例如图1中的终端设备101、终端设备102和终端设备103)连接的边缘节点设备(例如节点设备204、节点设备205、节点设备206以及节点设备207)可以为BIER转发出口路由器(bit-forwarding egress router，BFIR)。
BIER组播域的每个边缘节点设备可以通过比特串(bit string)中的一个比特(bit)位来进行标识。例如，图1中的边缘节点设备包括节点设备201、节点设备204、节点设备205、节点设备206和节点设备207，那么节点设备201的比特串可以为00001，节点设备204的比特串可以为00010，节点设备205的比特串可以为00100，节点设备206的比特串可以为01000，节点设备207的比特串可以为10000。
BIER组播域中的节点设备可以通过泛洪的方式学习到完整的BIER邻居表，邻居表中每个直连邻居对应一条表项，表项内容包括直连邻居可达的边缘节点设备的标识。
以图1为例，节点设备201的邻居表可以参见表1的示例：
表1
Figure PCTCN2020116937-appb-000001
节点设备202的邻居表可以参见表2的示例：
表2
邻居节点 可达节点 可达节点的比特串
节点设备201 节点设备201 00001
节点设备204 节点设备204 00010
节点设备205 节点设备205 00100
节点设备203的邻居表可以参见表3的示例：
表3
邻居节点 可达节点 可达节点的比特串
节点设备201 节点设备201 00001
节点设备206 节点设备206 01000
节点设备207 节点设备207 10000
在转发BIER组播报文时，BIER组播域的头节点设备，即节点设备201接收来自组播源节点(即服务器101)的单播报文，将该单播报文转换为BIER组播报文，该BIER组播报文的报文头中携带有目的节点的比特串。以图1为例，目的节点例如为节点设备204、节点设备205和节点设备207，那么目的节点的比特串为10110。
在生成BIER组播报文之后，用于转发BIER组播报文的节点设备根据报文头中的目的节点的比特串查找邻居表，根据与目的节点对应的邻居节点的个数对该BIER组播报文进行复制，每个邻居节点复制一份，同时修改复制后BIER组播报文中报文头的目的节点的比特串，修改之后向对应的邻居节点分发复制后的BIER组播报文。
例如，节点设备201生成的BIER组播报文的报文头的目的节点的比特串例如为10110，通过查找表1得知该BIER组播报文对应的目的节点为节点设备204、节点设备205和节点设备207，这些目的节点对应的邻居节点为节点设备202和节点设备203，那么节点设备201复制两份BIER组播报文，其中一份向节点设备202发送，另外一份向节点设备203发送。由于节点设备202对应的目的节点为节点设备204和节点设备205，所以向节点设备202发送的BIER组播报文的报文头中包括的目的节点的比特串为00110；由于节点设备203对应的目的节点为节点设备207，所以，向节点设备203发送的BIER组播报文的报文头中包括的目的节点的比特串为10000。
节点设备202在接收到来自节点设备201的BIER组播报文之后，查找表2得知该BIER组播报文对应的目的节点为节点设备204和节点设备205，而这两个节点设备均为节点设备202的邻居节点，所以，节点设备202将接收到的BIER组播报文复制两份，一份向节点设备204发送，另一份向节点设备205发送。向节点设备204发送的BIER组播报文的目的节点的比特串为00010，向节点设备205发送的BIER组播报文的目的节点的比特串为00100。
节点设备204接收到来自节点设备202的BIER组播报文之后，将该BIER组播报文转换为单播报文，并向终端设备101发送；节点设备205接收到来自节点设备202的BIER组播报文之后，将该BIER组播报文转换为单播报文，并向终端设备102发送。
节点设备203在接收到来自节点设备201的BIER组播报文之后，查找表3得知该BIER组播报文对应的目的节点为节点设备207，且该节点设备为节点设备203的邻居节点，所以，节点设备203将接收到的BIER组播报文复制一份并向节点设备207发送。向节点设备207发送的BIER组播报文的目的节点的比特串为10000。
节点设备207接收到来自节点设备203的BIER组播报文之后，将该BIER组播报文转换为单播报文，并向终端设备103发送。
上面描述了一条BIER组播流中一个BIER组播报文的转发流程，在实际转发过程中，可能会出现丢包、传输速度慢等问题，如何发现这些问题从而保证组播流传输的可靠性是本申请实施例需要解决的技术问题。下面结合图1-图4对本申请实施例提供的组播流检测方法进行介绍。
在介绍本申请实施例提供的组播流检测方法之前，先介绍一下BIER组播域的概念。如前文所提，BIER组播域是一个管理域，它可以例如包括组播源节点和终端设备之间的所有转发节点，也可以仅包括一部分转发节点。例如，以图1为例，BIER组播域可以包括节点设备201-节点设备207一共7个节点设备，也可以仅包括比如节点设备202、节点设备204和节点设备205。为了介绍方便，下文中提到的图1中的BIER组播域包括节点设备201-节点设备207。
在本申请实施例中，不同角色的节点设备对组播流的检测方法略有不同，下面将分别对BIER组播域的头节点设备、中间节点设备以及尾节点设备执行的组播流的检测方法进行介绍。
参见图2，该图为本申请实施例提供的组播流检测方法的流程图。
本申请实施例提供的由头节点设备执行的组播流检测方法包括如下步骤：
S201：头节点设备接收来自管理设备的第一对应关系，第一对应关系为流标识和第一标识的对应关系。
在本申请实施例中，头节点设备例如为图1所示的节点设备201，管理设备例如为图1所示的管理设备301。
在本申请实施例中，流标识为组播流的标识，用于标识组播流。例如，流标识可以是组播流的组播源(source)地址和组播组(group)地址，流标识还可以是组播源地址和组播组地址的哈希值等，本申请实施例不做具体限定。第一标识用于指示与流标识对应的组播流的转发路径上、对该组播流进行检测和发送相应检测数据的节点设备。
作为第一种可能的实现方式，第一标识指示的节点设备可以为BIER组播域中在该组播流的转发路径上的所有节点。以图1为例，在BIER组播域中、目的节点的比特串为10110的组播流的转发路径上的所有节点为节点设备201、节点设备202、节点设备203、节点设备204、节点设备205和节点设备207。
作为第二种可能的实现方式，第一标识指示的节点设备可以为该BIER组播域中在该组播流的转发路径上的头节点设备和所有尾节点设备。以图1为例，在BIER组播域中、目的节点的比特串为10110的组播流的转发路径上的头节点设备为节点设备201，所有尾节点设备为节点设备204、节点设备205和节点设备207。
作为第三种可能的实现方式，该第一标识指示的节点设备为该BIER组播域中在该组播流的转发路径上的头节点设备和被指定的尾节点设备。其中，被指定的尾节点设备为该转发路径上所有尾节点设备中的一个或多个尾节点设备。以图1为例，在BIER组播域中、目的节点的比特串为10110的组播流的转发路径上的被指定的尾节点设备例如为节点设备204。
作为第四种可能的实现方式，第一标识指示的节点设备为该BIER组播域中在该组播流的转发路径上的头节点设备、被指定的尾节点设备以及该头节点设备和该被指定的尾节点设备之间的中间节点设备。以图1为例，在BIER组播域中、目的节点的比特串为10110的组播流的转发路径上的头节点设备为节点设备201，被指定的尾节点设备例如为节点设 备204，中间节点设备例如为节点设备202。
当第一标识指示的节点设备为第三种可能的实现方式和第四种可能的实现方式时，管理设备还需要向头节点设备发送被指定的节点设备的标识，例如被指定的节点设备的比特串。
可选的，管理设备向头节点设备发送的第一对应关系中还可以包括用于指示检测数据包括用于检测与流标识对应的组播流的丢包信息、时延信息和/或拓扑信息等的标识，以实现对组播流的丢包信息、时延信息和/或拓扑信息的检测。其中，用于检测与流标识对应的组播流的丢包信息的检测数据可以包括在预设周期内BIER组播报文的数目和/或所述BIER组播报文的字节总数。
S202：头节点设备获取BIER组播报文S1，该BIER组播报文S1中包括流标识。
如前文所提，头节点设备可以接收来自组播源节点的单播报文，并将该单播报文转换为BIER组播报文S1。BIER组播报文S1中包括的流标识可以根据BIER组播报文S1的组播源地址和组播组地址得到。
需要说明的是，S202可以在S201之后执行，可以在S201之前执行，本申请实施例不做具体限定。
S203：头节点设备根据BIER组播报文S1中的流标识和第一对应关系得到对应的第一标识，并将该第一标识添加到BIER组播报文S1中，得到BIER组播报文S2。
在本申请实施例中，第一标识可以携带在BIER组播报文S1的BIER报文头的扩展类型-长度-值(type-length-value，TLV)字段中。参见图3，该图为本申请实施例提供的BIER报文头的格式示意图。在图3中，BIER报文头包括如下字段：指定的扩展头(Next Header)字段、扩展头的总字节长度(Hdr Ext Len)字段、选项类型(Option Type)1(在草案中建议使用OX70)字段、选项类型1的总字节长度(Option Length)字段、非MPLS BIER头(Non-MPLS BIER Header)字段、选项类型(Option Type)2字段、选项类型2的总字节长度(Option Length)字段、保留(Reserve)字段和E2E字段。其中，Option Type 2字段为扩展TLV的类型，其值例如为0x70。选项类型2的Option Length字段为扩展TLV的长度。E2E字段为扩展TLV的值，用于携带第一标识。
E2E字段的值不同，可以用于表示第一标识不同的指示。例如当E2E字段的值为0时，表示第一标识指示的节点设备为BIER组播域中在该BIER组播报文S2的转发路径上的所有节点；当E2E字段的值为1时，表示第一标识指示的节点设备可以为该BIER组播域中在该BIER组播报文S1的转发路径上的头节点设备和所有尾节点设备；当E2E字段的值为2时，表示第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S2的转发路径上的头节点设备和被指定的尾节点设备；当E2E字段的值为3时，表示第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S2的转发路径上的头节点设备、被指定的尾节点设备以及该头节点设备和该被指定的尾节点设备之间的中间节点设备。
当E2E字段的值表示第一标识指示的节点设备为第三种和第四种可能的实现方式(例如E2E字段的值为2或3)时，扩展TLV字段的值还可以包括节点设备标识列表，该节点设备标识列表用于指示所述BIER组播域中在BIER组播报文S2的转发路径上的被指定的尾节点设备。节点设备标识列表包括被指定的一个或多个尾节点设备的标识，例如为尾节点设备的比特串。例如，扩展TLV字段还包括OAM BitString字段，OAM BitString字段用于携带被指定的节点设备的比特串。OAM BitString字段可以占用32bit的整数倍。
此外，头节点设备具体获取什么检测数据可以预先在头节点设备进行配置，也可以通过由管理设备下发。如果是后者，那么管理设备向头节点设备发送的第一对应关系中还包括：用于指示检测数据包括用于检测与流标识对应的组播流的丢包信息的标识，那么头节点设备可以在BIER组播报文S1中加入第二标识，即BIER组播报文S2中还包括第二标识，该第二标识为指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数。
以图3为例，BIER组播报文S2的BIER报文头的扩展TLV中还可以包括P字段和周期字段，该P字段可以占1bit，该周期字段可以占用3bit。其中，P字段可以用于携带第二标识，在同一个预设周期内的BIER组播报文P字段的值相同，相邻两个预设周期内的BIER组播报文中P字段的值不同。例如，在第一个预设周期内，头节点设备获取到的BIER组播报文中的P字段的值均为1，在第二个预设周期内，头节点获取到的BIER组播报文的P字段的值均为0。
周期字段可以用于携带该预设周期。周期字段的值不同可以表示不同的预设周期。例如，周期字段的值为0表示预设周期为100毫秒；周期字段的值为1表示预设周期为1秒；周期字段的值为2表示预设周期为10秒；周期字段的值为3表示预设周期为30秒；周期字段的值为4表示预设周期为1分钟；周期字段的值为5表示预设周期为5分钟。
若管理设备向头节点设备发送的第一对应关系中还包括：用于指示检测数据包括用于检测与流标识对应的组播流的时延信息的标识，那么头节点设备可以在BIER组播报文S1中加入第三标识，即BIER组播报文S2还包括第三标识，第三标识用于指示所述BIER组播报文S2是否为用于确定时延的报文。
以图3为例，BIER组播报文S2的BIER报文头的扩展TLV中还可以包括D字段，D字段的值表示BIER组播报文S2是否为用于确定时延的报文，例如D字段为1时表示BIER组播报文S2为用于确定时延的报文；D字段为0时表示BIER组播报文S2不为用于确定时延的报文。
在一条组播流中，管理设备可以通过获取一个或多个BIER组播报文的发送时间和/或接收时间来获取该组播流的时延信息。如果BIER组播报文S2为用于确定时延的报文，那么BIER组播报文S2中的D字段的值与同一组播流中的其他组播报文的D字段的值不同。
可选的，每个预设周期内可以有一个BIER组播报文为用于确定时延的报文，那么头节点设备可以从在该预设周期内获取到的至少一个BIER组播报文中确定一个用于确定时延的BIER组播报文，并在该BIER组播报文中添加第二标识。
例如，在每个预设周期内的头节点设备获取到的第一个BIER组播报文为用于确定时延的报文，那么该BIER组播报文中D字段的值可以为1，该预设周期内头节点设备获取到的其他BIER组播报文中D字段的值均为0。
若管理设备向头节点设备发送的第一对应关系中还包括：用于指示检测数据包括用于检测与流标识对应的组播流的拓扑信息的标识，那么头节点设备可以在BIER组播报文S1中加入第四标识，即BIER组播报文S2包括第四标识，第四标识用于指示所述检测数据包括接收所述BIER组播报文S2的入接口标识和/或发送所述BIER组播报文S2的出接口标识。
以图3为例，BIER组播报文S2的BIER报文头的扩展TLV中还可以包括T字段，T 字段可以占用1bit，用于携带第四标识。例如，当T字段的值为1时，表示第一标识指示的节点设备需要向管理设备发送接收所述BIER组播报文S2的入接口标识和/或发送所述BIER组播报文S2的出接口标识。
可选的，当扩展TLV中还包括预设周期字段时，T字段的值可以表示第一标识指示的节点设备需要以预设周期字段的值为周期向管理设备发送接收所述BIER组播报文S2的入接口标识和/或发送所述BIER组播报文S2的出接口标识。
当然，上述入接口标识和/或出接口标识可以不是周期性的发送，而是出现变化后再发送。
可以理解的是，上述第二标识、第三标识和第四标识并不构成对本申请技术方案的限定，本领域技术人员可以根据实际情况自行设计。
S204：头节点设备根据BIER组播报文S2中的第一标识确定需要对BIER组播报文S2所属的组播流进行检测和发送相应的检测数据。
在本申请实施例中，头节点设备例如可以读取BIER组播报文S2中E2E字段的值，来确定是否需要对BIER组播报文S2所属的组播流进行检测和发送相应的检测数据。而在本申请实施例中，第一标识指示的节点设备的四种可能的实现方式中均包括头节点设备，所以头节点设备都需要对BIER组播报文S2所属的组播流进行检测和发送相应的检测数据。
S205：头节点设备获取该组播流的检测数据并向管理设备发送该检测数据。
在本申请实施例中，当头节点设备根据BIER组播报文S2中的第一标识确定需要对BIER组播报文S2所属的组播流进行检测和发送相应的检测数据时，头节点设备可以获取该组播流的检测数据并向管理设备发送该检测数据。
当BIER组播报文S2中包括第二标识时，头节点设备还可以根据第二标识的指示统计在预设周期内发送的BIER组播报文S2所属的组播流的BIER组播报文的个数和/或字节总数，并向管理设备发送。例如，若BIER组播报文S2的报文头中包括P字段和周期字段，周期字段的值为1，那么在第1秒内，头节点设备统计发送的P字段为1的BIER组播报文的个数和/或字节总数，在第2秒内，头节点设备统计发送的P字段为0的BIER组播报文的个数和/或字节总数，在第3秒内，头节点设备统计发送的P字段为1的BIER组播报文的个数和/或字节总数。
当BIER组播报文S2中包括第三标识，且第三标识用于指示BIER组播报文S2为用于确定时延的报文时，头节点设备还可以根据第三标识的指示获取BIER组播报文S2的发送时间，并向管理设备发送。例如，若BIER组播报文S2的报文头中包括D字段，且D字段的值为1，那么头节点设备可以获取BIER组播报文S2的发送时间。
当BIER组播报文S2中包括第四标识，第四标识用于指示所述检测数据包括接收所述BIER组播报文S2的入接口标识和/或发送所述BIER组播报文S2的出接口标识，那么头节点设备还可以根据第四标识的指示获取发送BIER组播报文S2的出接口标识，并向管理设备发送。例如，若BIER组播报文S2的报文头中包括T字段，且T字段的值为1，那么头节点设备可以获取BIER组播报文S2的出接口标识。当BIER组播报文S2中还包括周期字段时，头节点设备可以周期性获取组播流中BIER组播报文的出接口标识并向管理设备发送。当T字段的值为0，那么头节点设备可以将BIER组播报文S2的出接口标识和上一个包括第四标识且属于同一个组播流的BIER组播报文的出接口标识进行比对，如果二者不同，则头节点设备可以获取BIER组播报文的出接口标识并发送给管理设备。
S206：头节点设备向BIER组播域中BIER组播报文S2的转发路径上的下一跳节点设备发送BIER组播报文S2。
以图1为例，当头节点设备为节点设备201，那么BIER组播报文S2的转发路径上的下一跳节点可以为节点设备202或节点设备203，具体取决于BIER组播报文S2中携带的用于标识目的节点的比特串。
另外，可以理解的是，S206可以在S205之后执行，也可以在S205之前、S204之后执行。
对于头节点设备而言，通过在BIER组播报文S1中添加第一标识得到BIER组播报文S2，这样第一标识指示的节点设备就可以获取BIER组播报文S2所属的组播流对应的检测数据并向管理设备发送，第一标识不指示的节点设备可以不发送，不仅实现对组播流的检测，而且节约了带宽。同时，BIER组播报文S2中还可以包括第二标识、第三标识和第四标识的其中一个或多个，实现对组播流丢包信息、时延信息和拓扑信息的检测。
下面结合图2介绍本申请实施例提供的由中间节点设备执行的组播流检测方法，该方法包括如下步骤：
S301：中间节点设备接收BIER组播报文S2，BIER组播报文S2中包括流标识和第一标识。
S302：当第一标识指示的节点设备为BIER组播域中在该BIER组播报文S2的转发路径上的所有节点时，中间节点设备执行S306和S307。
S303：当第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S2的转发路径上的头节点设备和所有尾节点设备，或，第一标识指示的节点设备为在该BIER组播报文S2的转发路径上的头节点设备和被指定的尾节点设备时，中间节点设备执行S307。
S304：当第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S2的转发路径上的头节点设备、被指定的尾节点设备以及该头节点设备和该被指定的尾节点设备之间的中间节点设备时，中间节点设备根据所述第一标识在所述BIER组播报文S2中确定是否存在节点设备标识列表，若是，则执行S305；若否，则执行S307。
S305：中间节点设备确定BIER组播报文S2的目的节点的标识是否在节点设备标识列表中，若是，则执行S306和S307；若否，则执行S307。
在本申请实施例中，中间节点设备可以通过获取BIER组播报文S2中目的节点的标识确定节点设备标识列表是否包括BIER组播报文S2的目的节点的标识，若是，则说明BIER组播报文S2的目的节点属于指定的尾节点设备，并且该中间节点设备为头节点设备与该指定的尾节点设备之间的中间节点设备，需要获取所述组播流的检测数据和向管理设备发送所述检测数据；若否，则说明BIER组播报文S2的目的节点不属于指定的尾节点设备，该中间节点设备不为头节点设备与该指定的尾节点设备之间的中间节点设备，不需要获取所述组播流的检测数据和向管理设备发送所述检测数据。
例如，BIER组播报文S2中OAM BitString字段的值为00010，若节点设备202确定BIER组播报文S2中携带的目的节点的比特串为00110，即比特串为00010的目的节点的标识在节点标识列表中，那么说明节点设备204为指定的尾节点设备，且节点设备202为节点设备201与节点设备204之间的中间节点设备。若节点设备202确定BIER组播报文S2中携带的目的节点的比特串为10000，那么说明节点设备207不为指定的尾节点设备， 节点设备202不为节点设备201与节点设备207之间的中间节点设备。
S306：中间节点设备获取组播流的检测数据并向管理设备发送该检测数据。
在本申请实施例中，中间节点设备具体获取什么检测数据可以预先在该中间节点设备进行配置，或者可以根据BIER组播报文S2进行确定。
如果BIER组播报文S2包括第二标识，那么中间节点设备可以根据第二标识的指示统计在预设周期内接收或发送的BIER组播报文S2所属的组播流的BIER组播报文的个数和/或字节总数，并向管理设备发送。
如果BIER组播报文S2中包括第三标识，且第三标识用于指示BIER组播报文S2为用于确定时延的报文时，那么中间节点设备还可以根据第三标识的指示获取BIER组播报文S2的接收时间和/或发送时间，并向管理设备发送。
如果BIER组播报文S2中包括第四标识，那么中间节点设备还可以根据第四标识的指示获取接收BIER组播报文S2的入接口标识和/或发送BIER组播报文S2的出接口标识，并向管理设备发送。
S307：中间节点设备向BIER组播域中BIER组播报文S2的转发路径上的下一跳节点设备发送BIER组播报文S2。
需要说明的是，在实际应用中，中间节点设备转发BIER组播报文S2实际上需要对BIER组播报文S2进行复制并转发，如前文所提，但是为了描述简便，在本申请实施例中都简写为转发BIER组播报文S2。
对于中间节点设备而言，根据第一标识或第一标识和节点设备标识列表确定是否需要获取检测数据并发送给管理设备，如果需要，则获取检测数据并发送；如果不需要，则不发送，不仅实现对组播流的检测，而且节约了带宽。同时，BIER组播报文S2中还可以包括第二标识、第三标识和第四标识的其中一个或多个，实现对组播流丢包信息、时延信息和拓扑信息的检测。
下面结合图2介绍本申请实施例提供的由尾节点设备执行的组播流检测方法，该方法包括如下步骤：
S401：尾节点设备接收BIER组播报文S2，BIER组播报文S2中包括流标识和第一标识。
S402：当第一标识指示的节点设备为BIER组播域中在该BIER组播报文S2的转发路径上的所有节点，或第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S1的转发路径上的头节点设备和所有尾节点设备时，尾节点设备执行S404。
S403：当第一标识指示的节点设备为在该BIER组播报文S2的转发路径上的头节点设备和被指定的尾节点设备，或，第一标识指示的节点设备为该BIER组播域中在该BIER组播报文S2的转发路径上的头节点设备、被指定的尾节点设备以及该头节点设备和该被指定的尾节点设备之间的中间节点设备时，尾节点设备确定该尾节点设备的标识是否在BIER组播报文S2的节点设备标识列表中，如果是，则执行S404。
当尾节点设备确定该尾节点设备的标识在BIER组播报文S2的节点设备标识列表中，说明该尾节点设备为被指定的尾节点设备，需要获取所述组播流的检测数据和向管理设备发送所述检测数据；如果不在，则说明该尾节点设备为被指定的尾节点设备，不需要获取所述组播流的检测数据和向管理设备发送所述检测数据。
S404：尾节点设备获取所述组播流的检测数据和向管理设备发送所述检测数据。
在本申请实施例中，尾节点设备具体获取什么检测数据可以预先在该尾节点设备进行配置，或者可以根据BIER组播报文S2进行确定。
如果BIER组播报文S2包括第二标识，那么尾节点设备可以根据第二标识的指示统计在预设周期内接收的BIER组播报文S2所属的组播流的BIER组播报文的个数和/或字节总数，并向管理设备发送。
如果BIER组播报文S2中包括第三标识，且第三标识用于指示BIER组播报文S2为用于确定时延的报文时，那么尾节点设备还可以根据第三标识的指示获取BIER组播报文S2的接收时间，并向管理设备发送。
如果BIER组播报文S2中包括第四标识，那么尾节点设备还可以根据第四标识的指示获取接收BIER组播报文S2的入接口标识，并向管理设备发送。
此外，尾节点设备可以剥离BIER组播报文S2的报文头，变成单播报文，并向终端设备发送。
对于尾节点设备而言，根据第一标识或第一标识和节点设备标识列表确定是否需要获取检测数据并发送给管理设备，如果需要，则获取检测数据并发送；如果不需要，则不发送，不仅实现对组播流的检测，而且节约了带宽。同时，BIER组播报文S2中还可以包括第二标识、第三标识和第四标识的其中一个或多个，实现对组播流丢包信息、时延信息和拓扑信息的检测。
在介绍了头节点设备、中间节点设备和尾节点设备的组播流检测方法之后，下面介绍管理设备如何对上述节点设备发送的检测数据进行处理的方法：
管理设备接收来自第一标识指示的节点设备的检测数据，根据检测数据对组播流进行检测。具体的，
当管理设备接收到来自头节点设备的在预设周期内发送的组播报文的数目和/或字节总数，和来自尾节点设备的在预设时间周期内接收的同一条组播流的组播报文的数目和/或字节总数时，管理设备可以将二者进行比较，若同一条组播流、同一个预设时间周期内，头节点设备发送的组播报文的数目大于尾节点设备接收到组播报文的数目，和/或，头节点设备发送的组播报文的字节总数大于尾节点设备接收到组播报文的字节总数，那么意味着该组播流发生丢包现象。进一步的，如果管理设备还接收到中间节点设备的在预设周期内接收或发送的同一条组播流的组播报文的数目和/或字节总数，就可以判断出丢包出现在报文转发的哪些链路上或哪些节点上，进而对故障进行定位。
当管理设备接收到来自头节点设备的BIER组播报文S2的发送时间，以及来自尾节点设备的BIER组播报文S2的接收时间时，管理设备可以该发送时间和该接收时间之间的差值确定出BIER组播报文S2的时延。如果BIER组播报文S2的接收时间来自不同的尾节点设备，那么可以根据来自不同的尾节点设备确定出BIER组播报文S2在不同转发路径上的时延。如果某条转发路径上的时延不满足要求，则可以停止利用该转发路径转发BIER组播报文S2，或者生成新的转发路径来代替该条转发路径。
当管理设备接收到的来自头节点设备的BIER组播报文S2的出端口标识、来自中间节点设备的BIER组播报文S2的入端口标识和出端口标识，以及来自尾节点设备的BIER组播报文S2的入端口标识，管理设备可以建立转发BIER组播报文S2的拓扑架构。当上述 入端口标识和/或出端口标识发生变化，管理设备可以及时的获取到新的拓扑架构。
上述管理设备对检测数据的处理方式并不构成对本申请技术方案的限定，本领域技术人可以根据具体情况自行设计。
参见图4，该图为本申请实施例提供的第一节点设备400的结构示意图。图4所示的第一节点设备400可以执行上述实施例的方法中第一节点设备执行的相应步骤。如图4所示，所述第一节点设备400包括处理单元401、发送单元402和接收单元403。
处理单元401，用于获取第一位索引显式复制BIER组播报文，所述第一BIER组播报文包括流标识和第一标识，所述流标识用于指示所述第一BIER组播报文所属的组播流，所述第一标识用于指示所述第一BIER组播报文的转发路径上、对所述组播流进行检测和发送相应的检测数据的节点设备。所述处理单元401，还用于根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据；响应于根据所述第一标识确定需要对所述组播流进行检测和发送相应的检测数据，获取所述组播流的检测数据。发送单元402，用于向管理设备发送所述检测数据。
可选的，所述第一标识指示的节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备和所有尾节点设备。
可选的，所述第一节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的尾节点设备或中间节点设备，所述处理单元401根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据，包括：所述处理单元401，用于根据所述第一标识在所述第一BIER组播报文中确定所述节点设备标识列表，所述节点设备标识列表用于指示所述BIER组播域中在所述第一BIER组播报文的转发路径上的被指定的尾节点设备；根据所述节点设备标识列表确定是否对所述组播流进行检测和发送相应的检测数据。
可选的，所述节点设备标识列表为所述被指定的尾节点设备的比特串。
可选的，当所述第一节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理单元401，用于：获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；根据第一对应关系在所述第二BIER组播报文中添加所述第一标识，得到所述第一BIER组播报文，所述第一对应关系为所述流标识和所述第一标识的对应关系。
可选的，所述第一节点设备还包括：接收单元403，用于接收来自所述管理设备的所述第一对应关系。
可选的，所述第一BIER组播报文还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数；所述处理单元401，用于根据所述第二标识在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
可选的，所述第一BIER组播报文还包括所述预设周期。
可选的，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理单元401，还用于在所述预设周期内获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加第一字段和第二字段，所述地址字段的值为所述第一标识，所述第二字段的值为与所述预设周期对应的预设值，所述第二字段的值用于指示在所述预设周期内获取接收到的所述组播流的BIER组播报 文的统计信息。
可选的，所述第一BIER组播报文还包括第三标识，所述第三标识用于指示所述第一BIER组播报文为用于确定时延的报文；所述处理单元401，用于根据所述第一标识和所述第三标识获取所述第一BIER组播报文的接收时间和/或所述第一BIER组播报文的发送时间。
可选的，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理单元401，还用于在预设周期内获取至少一个BIER组播报文，所述至少一个BIER组播报文中的每个BIER组播报文均包括所述流标识；从所述至少一个BIER组播报文中确定第二BIER组播报文；在所述第二BIER组播报文中添加所述第一标识和所述第三标识，得到所述第一BIER组播报文。
可选的，所述第一BIER组播报文还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述第一BIER组播报文的入接口标识和/或发送所述第一BIER组播报文的出接口标识；所述处理单元401，用于根据所述第一标识和所述第二标识获取接收所述第一BIER组播报文的入接口标识的标识和/或发送所述第一BIER组播报文的出接口标识的标识。
可选的，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理单元401，还用于获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加所述第一标识和所述第四标识，得到所述第一BIER组播报文。
可选的，所述第一标识携带在所述第一BIER组播报文的BIER报文头中。
可选的，所述第一标识携带在所述BIER报文头的TLV字段中。
可选的，所述流标识根据所述第一BIER组播报文的组播源地址和组播组地址确定。
可选的，所述发送单元402，还用于向所述第一BIER组播报文的转发路径上的下一跳节点设备发送所述第一BIER组播报文。
图4所示的第一节点设备400可以执行上述实施例的方法中第一节点设备执行的相应步骤。BIER组播域的第一节点设备可以根据第一标识确定是否需要获取组播流的检测数据并向管理设备发送，实现对BIER组播流的检测。
图5为本申请实施例的第一节点设备500的硬件结构示意图。图5所示的第一节点设备500可以执行上述实施例的方法中第一节点设备执行的相应步骤和图4所示实施例中第一节点设备400的功能。
如图5所示，所述第一节点设备500包括处理器501、存储器502、接口503和总线504。其中接口503可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器501、存储器502和接口503通过总线504连接。
所述接口503具体可以包括发送器和接收器，用于第一节点设备与上述实施例中的第一节点设备的上一跳网络设备或下一跳网络设备之间收发信息；和/或用于上述实施例中的管理设备之间收发信息。例如，所述接口503用于支持接收所述管理设备发送的第一对应关系；用于接收所述第一节点设备的上一跳网络设备发送的第一BIER组播报文；和/或用于向所述第一节点设备的下一跳网络设备发送第一BIER组播报文。作为举例，所述接口503用于支持图2中的过程S201、S205和S206。所述处理器501用于执行上述实施例中由第一节点设备进行的处理。例如，所述处理器501用于确定根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据；响应于所述第一节点设备根据所述第一标识确定需 要对所述组播流进行检测和发送相应的检测数据，所述第一节点设备获取所述组播流的检测数据和向管理设备发送所述检测数据；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器501用于支持图3中的过程S202-S204。存储器502包括操作系统和应用程序，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及第一节点设备的处理过程。可选的，所述存储器502可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行第一节点设备500时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导第一节点设备500进入正常运行状态。在第一节点设备500进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及第一节点设备的处理过程。
可以理解的是，图5仅仅示出了第一节点设备500的简化设计。在实际应用中，第一节点设备可以包含任意数量的接口，处理器或者存储器。
参见图6，该图为本申请实施例提供的管理设备600的结构示意图。图6所示的管理设备600可以执行上述实施例的方法中管理设备执行的相应步骤。如图6所示，所述管理设备600包括处理单元601、发送单元602和接收单元603。
处理单元601，用于获取第一对应关系，所述第一对应关系为流标识和第一标识的对应关系，所述流标识为BIER组播流的标识，所述第一标识用于指示所述BIER组播流的转发路径上、对所述BIER组播流进行检测和发送相应的检测数据的节点设备；发送单元602，用于向第一节点设备发送所述第一对应关系。
可选的，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备和所有尾节点设备。
可选的，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的头节点设备和被指定的尾节点设备；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备、被指定的尾节点设备以及所述头节点设备和所述被指定的尾节点设备之间的中间节点设备；所述发送单元，还用于向第一节点设备发送所述被指定的尾节点设备的标识。
可选的，所述第一对应关系还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述BIER组播流的BIER组播报文的统计信息。
可选的，所述第一对应关系还包括第三标识，所述第三标识用于指示所述检测数据包括所述BIER组播流中BIER组播报文的接收时间和/或发送时间。
可选的，所述第一对应关系还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述BIER组播流中BIER组播报文的入接口标识和/或发送所述BIER组播报文的出接口标识。
可选的，所述管理设备还包括：接收单元603，用于接收来自所述第一标识指示的节点设备的检测数据；所述处理单元601，还用于根据所述检测数据对所述BIER组播流进行检测。
图6所示的管理设备600可以执行上述实施例的方法中管理设备执行的相应步骤。管理 设备600通过向第一节点设备下发第一对应关系，第一节点设备将第一标识加入到与流标识对应的BIER组播报文中，以使第一标识指示的节点设备在接收到该BIER组播报文之后能够获取组播流的检测数据并发送给管理设备，实现对BIER组播流的检测。
图7为本申请实施例的管理设备700的硬件结构示意图。图7所示的管理设备700可以执行上述实施例的方法中管理设备执行的相应步骤和图6所示实施例中管理设备600的功能。
如图7所示，所述管理设备700包括处理器701、存储器702、接口703和总线704。其中接口703可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器701、存储器702和接口703通过总线704连接。
所述接口703具体可以包括发送器和接收器，用于管理设备与上述实施例中的节点设备之间收发信息。例如，所述接口703用于支持向第一节点设备发送第一对应关系；和/或用于接收第一标识指示的节点设备的检测数据。所述处理器701用于执行上述实施例中由管理设备进行的处理。例如，所述处理器701用于根据检测数据进行检测。作为举例，所述处理器701用于支持图3中的过程S202-S204。存储器702包括操作系统7021和应用程序7022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及管理设备的处理过程。可选的，所述存储器702可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行管理设备700时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导管理设备700进入正常运行状态。在管理设备700进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及管理设备的处理过程。
可以理解的是，图7仅仅示出了管理设备700的简化设计。在实际应用中，管理设备可以包含任意数量的接口，处理器或者存储器。
本申请实施例还提供了一种网络系统，包括上述第一节点设备500和管理设备700。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述应用于第一节点设备500的组播流检测方法。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述应用于管理设备700的组播流检测方法。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑模块划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要获取其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各模块单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件模块单元的形式实现。
所述集成的单元如果以软件模块单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (41)

  1. 一种组播流检测方法，其特征在于，所述方法包括：
    第一节点设备获取第一位索引显式复制BIER组播报文，所述第一BIER组播报文包括流标识和第一标识，所述流标识用于指示所述第一BIER组播报文所属的组播流，所述第一标识用于指示所述第一BIER组播报文的转发路径上、对所述组播流进行检测和发送相应的检测数据的节点设备；
    所述第一节点设备根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据；
    响应于所述第一节点设备根据所述第一标识确定需要对所述组播流进行检测和发送相应的检测数据，所述第一节点设备获取所述组播流的检测数据和向管理设备发送所述检测数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备和所有尾节点设备。
  3. 根据权利要求1所述的方法，其特征在于，所述第一节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的尾节点设备或中间节点设备，所述第一节点设备根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据，包括：
    所述第一节点设备根据所述第一标识在所述第一BIER组播报文中确定所述节点设备标识列表，所述节点设备标识列表用于指示所述BIER组播域中在所述第一BIER组播报文的转发路径上的被指定的尾节点设备；
    所述第一节点设备根据所述节点设备标识列表确定是否对所述组播流进行检测和发送相应的检测数据。
  4. 根据权利要求3所述的方法，其特征在于，所述节点设备标识列表为所述被指定的尾节点设备的比特串。
  5. 根据权利要求1所述的方法，其特征在于，当所述第一节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法包括：
    所述第一节点设备获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；
    所述第一节点设备根据第一对应关系在所述第二BIER组播报文中添加所述第一标识，得到所述第一BIER组播报文，所述第一对应关系为所述流标识和所述第一标识的对应关系。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一节点设备接收来自所述管理设备的所述第一对应关系。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第一BIER组播报文还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数；
    所述第一节点设备获取所述组播流的检测数据包括：
    所述第一节点设备根据所述第二标识在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第一BIER组播报文还包括所述预设 周期。
  9. 根据权利要求7或8所述的方法，其特征在于，
    当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：
    所述第一节点设备在所述预设周期内获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；
    所述第一节点设备在所述第二BIER组播报文中添加第一字段和第二字段，所述地址字段的值为所述第一标识，所述第二字段的值为与所述预设周期对应的预设值，所述第二字段的值用于指示在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述第一BIER组播报文还包括第三标识，所述第三标识用于指示所述第一BIER组播报文为用于确定时延的报文；
    所述第一节点设备获取所述组播流的检测数据包括：
    所述第一节点设备根据所述第一标识和所述第三标识获取所述第一BIER组播报文的接收时间和/或所述第一BIER组播报文的发送时间。
  11. 根据权利要求10所述的方法，其特征在于，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：
    所述第一节点设备在预设周期内获取至少一个BIER组播报文，所述至少一个BIER组播报文中的每个BIER组播报文均包括所述流标识；
    所述第一节点设备从所述至少一个BIER组播报文中确定第二BIER组播报文；
    所述第一节点设备在所述第二BIER组播报文中添加所述第一标识和所述第三标识，得到所述第一BIER组播报文。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一BIER组播报文还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述第一BIER组播报文的入接口标识和/或发送所述第一BIER组播报文的出接口标识；
    所述第一节点设备获取所述组播流的检测数据包括：
    所述第一节点设备根据所述第一标识和所述第二标识获取接收所述第一BIER组播报文的入接口标识的标识和/或发送所述第一BIER组播报文的出接口标识的标识。
  13. 根据权利要求12所述的方法，其特征在于，当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述方法还包括：
    所述第一节点设备获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；
    所述第一节点设备在所述第二BIER组播报文中添加所述第一标识和所述第四标识，得到所述第一BIER组播报文。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述第一标识携带在所述第一BIER组播报文的BIER报文头中。
  15. 根据权利要求14所述的方法，其特征在于，所述第一标识携带在所述BIER报文头的TLV字段中。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述流标识根据所述第一BIER组播报文的组播源地址和组播组地址确定。
  17. 根据权利要求1-16任一项所述的方法，其特征在于，所述方法还包括：
    所述第一节点设备向所述第一BIER组播报文的转发路径上的下一跳节点设备发送所 述第一BIER组播报文。
  18. 一种组播流检测方法，其特征在于，所述方法包括：
    管理设备获取第一对应关系，所述第一对应关系为流标识和第一标识的对应关系，所述流标识为BIER组播流的标识，所述第一标识用于指示所述BIER组播流的转发路径上、对所述BIER组播流进行检测和发送相应的检测数据的节点设备；
    所述管理设备向第一节点设备发送所述第一对应关系。
  19. 根据权利要求18所述的方法，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备和所有尾节点设备。
  20. 根据权利要求18所述的方法，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的头节点设备和被指定的尾节点设备；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备、被指定的尾节点设备以及所述头节点设备和所述被指定的尾节点设备之间的中间节点设备；所述方法还包括：
    所述管理设备向第一节点设备发送所述被指定的尾节点设备的标识。
  21. 根据权利要求18-20任一项所述的方法，其特征在于，所述第一对应关系还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述BIER组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数。
  22. 根据权利要求18-21任一项所述的方法，其特征在于，所述第一对应关系还包括第三标识，所述第三标识用于指示所述检测数据包括所述BIER组播流中BIER组播报文的接收时间和/或发送时间。
  23. 根据权利要求18-22任一项所述的方法，其特征在于，所述第一对应关系还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述BIER组播流中BIER组播报文的入接口标识和/或发送所述BIER组播报文的出接口标识。
  24. 根据权利要求18-23任一项所述的方法，其特征在于，所述方法还包括：
    所述管理设备接收来自所述第一标识指示的节点设备的检测数据；
    所述管理设备根据所述检测数据对所述BIER组播流进行检测。
  25. 一种第一节点设备，其特征在于，所述第一节点设备包括：
    处理器，用于获取第一位索引显式复制BIER组播报文，所述第一BIER组播报文包括流标识和第一标识，所述流标识用于指示所述第一BIER组播报文所属的组播流，所述第一标识用于指示所述第一BIER组播报文的转发路径上、对所述组播流进行检测和发送相应的检测数据的节点设备；
    所述处理器，还用于根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据；响应于根据所述第一标识确定需要对所述组播流进行检测和发送相应的检测数据，获取所述组播流的检测数据；
    发送器，用于向管理设备发送所述检测数据。
  26. 根据权利要求25所述的第一节点设备，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的头节点 设备和所有尾节点设备。
  27. 根据权利要求25所述的第一节点设备，其特征在于，所述第一节点设备为所述BIER组播域中在所述第一BIER组播报文的转发路径上的尾节点设备或中间节点设备，所述处理器根据所述第一标识确定是否对所述组播流进行检测和发送相应的检测数据，包括：
    所述处理器，用于根据所述第一标识在所述第一BIER组播报文中确定所述第一节点设备标识列表，所述节点设备标识列表用于指示所述BIER组播域中在所述第一BIER组播报文的转发路径上的被指定的尾节点设备；根据所述节点设备标识列表确定是否对所述组播流进行检测和发送相应的检测数据。
  28. 根据权利要求27所述的第一节点设备，其特征在于，所述节点设备标识列表为所述被指定的尾节点设备的比特串。
  29. 根据权利要求25所述的第一节点设备，其特征在于，当所述第一节点设备为BIER组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，用于：
    获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；根据第一对应关系在所述第二BIER组播报文中添加所述第一标识，得到所述第一BIER组播报文，所述第一对应关系为所述流标识和所述第一标识的对应关系。
  30. 根据权利要求29所述的第一节点设备，其特征在于，所述第一节点设备还包括：
    接收器，用于接收来自所述管理设备的所述第一对应关系。
  31. 根据权利要求25-30任一项所述的第一节点设备，其特征在于，所述第一BIER组播报文还包括第二标识，所述第二标识用于指示所述检测数据包括在预设周期内接收到的所述组播流的BIER组播报文的统计信息，所述统计信息包括所述BIER组播报文的数目和/或所述BIER组播报文的字节总数；
    所述处理器，用于根据所述第二标识在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
  32. 根据权利要求31所述的第一节点设备，其特征在于，所述第一BIER组播报文还包括所述预设周期。
  33. 根据权利要求31或32所述的第一节点设备，其特征在于，
    当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于在所述预设周期内获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加第一字段和第二字段，所述地址字段的值为所述第一标识，所述第二字段的值为与所述预设周期对应的预设值，所述第二字段的值用于指示在所述预设周期内获取接收到的所述组播流的BIER组播报文的统计信息。
  34. 根据权利要求25-33任一项所述的第一节点设备，其特征在于，所述第一BIER组播报文还包括第三标识，所述第三标识用于指示所述第一BIER组播报文为用于确定时延的报文；
    所述处理器，用于根据所述第一标识和所述第三标识获取所述第一BIER组播报文的接收时间和/或所述第一BIER组播报文的发送时间。
  35. 根据权利要求34所述的第一节点设备，其特征在于，
    当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于在预设周期内获取至少一个BIER组播报文，所述至少一个BIER 组播报文中的每个BIER组播报文均包括所述流标识；从所述至少一个BIER组播报文中确定第二BIER组播报文；在所述第二BIER组播报文中添加所述第一标识和所述第三标识，得到所述第一BIER组播报文。
  36. 根据权利要求25-35任一项所述的第一节点设备，其特征在于，所述第一BIER组播报文还包括第四标识，所述第四标识用于指示所述检测数据包括接收所述第一BIER组播报文的入接口标识和/或发送所述第一BIER组播报文的出接口标识；
    所述处理器，用于根据所述第一标识和所述第二标识获取接收所述第一BIER组播报文的入接口标识的标识和/或发送所述第一BIER组播报文的出接口标识的标识。
  37. 根据权利要求36所述的第一节点设备，其特征在于，
    当所述第一节点设备为组播域中在所述第一BIER组播报文的转发路径上的头节点设备时，所述处理器，还用于获取第二BIER组播报文，所述第二BIER组播报文包括所述流标识；在所述第二BIER组播报文中添加所述第一标识和所述第四标识，得到所述第一BIER组播报文。
  38. 一种管理设备，其特征在于，所述管理设备包括：
    处理器，用于获取第一对应关系，所述第一对应关系为流标识和第一标识的对应关系，所述流标识为BIER组播流的标识，所述第一标识用于指示所述BIER组播流的转发路径上、对所述BIER组播流进行检测和发送相应的检测数据的节点设备；
    发送器，用于向第一节点设备发送所述第一对应关系。
  39. 根据权利要求38所述的管理设备，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的所有节点；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备和所有尾节点设备。
  40. 根据权利要求38所述的管理设备，其特征在于，所述第一标识指示的节点设备为BIER组播域中在所述BIER组播流的转发路径上的头节点设备和被指定的尾节点设备；或，所述第一标识指示的节点设备为所述BIER组播域中在所述BIER组播流的转发路径上的头节点设备、被指定的尾节点设备以及所述头节点设备和所述被指定的尾节点设备之间的中间节点设备；
    所述发送单元，还用于向第一节点设备发送所述被指定的尾节点设备的标识。
  41. 一种网络系统，其特征在于，所述网络系统包括第一节点设备和管理设备，所述第一节点设备为权利要求25至37中任一所述的第一节点设备，所述管理设备为权利要求38至40中任一所述的管理设备。
PCT/CN2020/116937 2019-10-18 2020-09-22 一种组播流检测方法、设备及系统 WO2021073377A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910996012.7 2019-10-18
CN201910996012 2019-10-18
CN201911320778.XA CN112688827B (zh) 2019-10-18 2019-12-19 一种组播流检测方法、设备及系统
CN201911320778.X 2019-12-19

Publications (1)

Publication Number Publication Date
WO2021073377A1 true WO2021073377A1 (zh) 2021-04-22

Family

ID=75445536

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116937 WO2021073377A1 (zh) 2019-10-18 2020-09-22 一种组播流检测方法、设备及系统

Country Status (2)

Country Link
CN (1) CN112688827B (zh)
WO (1) WO2021073377A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113992564A (zh) * 2021-09-17 2022-01-28 新华三信息安全技术有限公司 报文处理方法及装置
CN117411738A (zh) * 2023-12-15 2024-01-16 格创通信(浙江)有限公司 组播复制方法、装置、电子设备和存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277552A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 传输报文的方法、装置及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812197A (zh) * 2014-12-30 2016-07-27 华为技术有限公司 位转发入口路由器、位转发路由器及操作管理维护检测方法
US20170033939A1 (en) * 2015-07-28 2017-02-02 Ciena Corporation Multicast systems and methods for segment routing
CN107147508A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 故障检测方法及装置
US10103981B2 (en) * 2015-11-01 2018-10-16 Cisco Technology, Inc. BIER forwarding validation
CN109921987A (zh) * 2017-12-13 2019-06-21 中兴通讯股份有限公司 一种bier-te网络检测方法、装置及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104067559B (zh) * 2012-12-31 2018-03-09 华为技术有限公司 组播通道的性能检测方法、装置和系统
US20180367456A1 (en) * 2017-06-20 2018-12-20 Cisco Technology, Inc. System and method to facilitate packet forwarding using stateful bit index explicit replication (bier) in a networking environment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812197A (zh) * 2014-12-30 2016-07-27 华为技术有限公司 位转发入口路由器、位转发路由器及操作管理维护检测方法
US20170033939A1 (en) * 2015-07-28 2017-02-02 Ciena Corporation Multicast systems and methods for segment routing
US10103981B2 (en) * 2015-11-01 2018-10-16 Cisco Technology, Inc. BIER forwarding validation
CN107147508A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 故障检测方法及装置
CN109921987A (zh) * 2017-12-13 2019-06-21 中兴通讯股份有限公司 一种bier-te网络检测方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
XIONG QUAN, GREG MIRSKY, FANGWEI HU: "BIER BFD draft-hu-bier-bfd-03.txt", BIER WG INTERNET-DRAFT, 1 March 2019 (2019-03-01), pages 1 - 8, XP055801971, Retrieved from the Internet <URL:https://tools.ietf.org/pdf/draft-hu-bier-bfd-03.pdf> [retrieved on 20210506] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113992564A (zh) * 2021-09-17 2022-01-28 新华三信息安全技术有限公司 报文处理方法及装置
CN117411738A (zh) * 2023-12-15 2024-01-16 格创通信(浙江)有限公司 组播复制方法、装置、电子设备和存储介质
CN117411738B (zh) * 2023-12-15 2024-03-08 格创通信(浙江)有限公司 组播复制方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN112688827B (zh) 2023-03-31
CN112688827A (zh) 2021-04-20

Similar Documents

Publication Publication Date Title
WO2021073377A1 (zh) 一种组播流检测方法、设备及系统
US20230261962A1 (en) Method for Detecting Multicast Service Flow and Related Apparatus
US20080019265A1 (en) Systems and methods for configuring a network to include redundant upstream connections using an upstream control protocol
US20090213855A1 (en) Method and switch for implementing internet group management protocol snooping
WO2012003743A1 (zh) 组播流量的转发方法及装置
WO2017117956A1 (zh) 一种信息传输方法及装置
US20110075599A1 (en) Method and apparatus for multicast group management
EP3432527B1 (en) Information processing method and device, and computer storage medium
US11991066B2 (en) Method of establishing bidirectional forwarding detection session based on BIER, and BFIR, BFER, system and storage medium
KR20150007623A (ko) 패킷 전달 시스템에서의 보호 절체 방법 및 장치
US20220368623A1 (en) Multicast Packet Detection Method, Network Device, and System
US20220272028A1 (en) Packet Forwarding Method, First Network Device, and First Device Group
WO2021197141A1 (zh) 业务处理方法、装置、设备及存储介质
CN102281165A (zh) 一种基于服务质量的故障检测方法、系统和装置
WO2022160665A1 (zh) 一种报文转发的方法、报文处理方法及设备
WO2017041534A1 (zh) 一种电力线网络通信的方法及装置、计算机存储介质
WO2016131359A1 (zh) 环型组网组播线路切换的方法及装置
WO2022048466A1 (zh) 一种操作管理维护oam报文处理方法及设备
WO2021169254A1 (zh) 一种路由匹配方法、信息发送方法及装置
WO2020168982A1 (zh) 一种发送和获取断言报文的方法和网络节点
CN114079583A (zh) 发送组播报文的方法、获取转发表项的方法及装置
WO2023165544A1 (zh) 一种用于发现根节点的方法及装置
EP3128703B1 (en) Path detection method, destination node device and communication system
WO2022033449A1 (zh) 发送组播报文的方法、获取转发表项的方法及装置
WO2022267619A1 (zh) 一种通信方法及相关设备

Legal Events

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

Ref document number: 20876190

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20876190

Country of ref document: EP

Kind code of ref document: A1