WO2022246837A1 - 随流检测方法和电子设备 - Google Patents

随流检测方法和电子设备 Download PDF

Info

Publication number
WO2022246837A1
WO2022246837A1 PCT/CN2021/096929 CN2021096929W WO2022246837A1 WO 2022246837 A1 WO2022246837 A1 WO 2022246837A1 CN 2021096929 W CN2021096929 W CN 2021096929W WO 2022246837 A1 WO2022246837 A1 WO 2022246837A1
Authority
WO
WIPO (PCT)
Prior art keywords
bier
detection
message
service message
flow
Prior art date
Application number
PCT/CN2021/096929
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 新华三技术有限公司
Priority to CN202180001399.3A priority Critical patent/CN115699685A/zh
Priority to EP21942411.6A priority patent/EP4149057A4/en
Priority to PCT/CN2021/096929 priority patent/WO2022246837A1/zh
Priority to US18/001,463 priority patent/US20230231780A1/en
Priority to JP2022577620A priority patent/JP7488921B2/ja
Publication of WO2022246837A1 publication Critical patent/WO2022246837A1/zh

Links

Images

Classifications

    • 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/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • 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
    • 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

Definitions

  • This application relates to the field of network communication technology, and in particular to a flow-based detection method for general bit index explicit replication (G-BIER: Generalized BIER) service packets applied to Internet Protocol Version 6 (IPv6: Internet Protocol Version 6) multicast and electronic equipment.
  • G-BIER Generalized BIER
  • Bit Index Explicit Replication Bit Index Explicit Replication
  • Bit Index Explicit Replication Bit Index Explicit Replication
  • G-BIER based on the IPv6 data plane can deploy IP multicast services on the IPv6 network (the multicast service packets at this time can be called G-BIER service packets).
  • G-BIER The business process of the BIER data plane and the business process of the G-BIER control plane have been determined, but the actual packet loss rate and time delay of the G-BIER business messages transmitted in the IPv6 network are used to characterize the network quality. There is a lack of implementable measurement methods.
  • the embodiment of the present application provides a flow-based detection method and electronic equipment, so as to realize the real packet loss rate and delay when the G-BIER service message is transmitted in the IPv6 network based on the flow-based detection of the G-BIER service message for characterization Network quality data.
  • the embodiment of the present application provides a method for detecting with the flow of G-BIER service messages based on IPv6 multicast, the method is applied to network equipment, and the method includes:
  • the network device serves as the entry node bit forwarding router BFIR of the G-BIER domain
  • the G-BIER service message carries an IPv6 extension header and an IPv6 load field;
  • the IPv6 load field includes the original multicast service message;
  • the purpose option extension header DOH in the IPv6 extension header includes at least: G-BIER A BIER option and a follow-up detection option;
  • the G-BIER option is used to indicate message forwarding in the G-BIER domain, and the follow-up detection option carries a follow-up detection flag and the follow-up detection information;
  • the The follow-up detection mark is used to indicate the execution of follow-up detection;
  • the follow-up detection information includes at least: flow number Flow ID, message sequence number Sequence Number, message receiving timestamp and message sending timestamp;
  • the Flow ID The Sequence Number is custom-set by the BFIR and is prohibited from being changed in the G-BIER domain after setting;
  • the Flow ID is determined according to message characteristics, and the Flow IDs of different messages with different message characteristics are different;
  • the Sequence Number is used to
  • the method further includes:
  • Described network device is as described G-BIER domain's egress node bit forwarding router BFER, when receiving G-BIER business message, records the follow-up detection information carried in the G-BIER service message with the flow detection option, and sends all The G-BIER service message is restored to the original multicast service message and forwarded to the multicast receiver, and will receive the time stamp of the G-BIER service message and the detection data related to the recorded follow-up detection information Report to the analyzer.
  • the flow detection information also includes:
  • the message receiving time stamp and the message sending time stamp follow the time stamp format indicated by the TF.
  • the method further includes:
  • the network device is used as an intermediate BFR device between the BFIR in the G-BIER domain and the egress node bit forwarding router BFER. If it supports G-BIER flow detection, when receiving the G-BIER service message, it will Update the follow-up detection information in the follow-up detection option carried by the G-BIER service message and forward the updated G-BIER service message in the G-BIER domain, which will be compared with the updated G-BIER The detection data related to the flow detection information in the flow detection option carried in the service message is reported to the analyzer.
  • updating the follow-up detection information in the follow-up detection option carried by the G-BIER service message includes:
  • the flow detection information further includes: at least one TLV, and each TLV carries at least one path detection parameter; the path detection parameters at least include: when flow detection is used to detect network transmission delay, the The path detection parameters at least include: delay parameters; when the flow detection is used for packet loss statistics, the path detection parameters at least include: the number of packet loss;
  • the updating of the follow-up detection information in the follow-up detection option carried by the G-BIER service message includes:
  • the packet sending timestamp in the streaming detection option carried in the service message is updated to the timestamp of sending the updated G-BIER service message, and at least one path is filled in at least one TLV detection parameters; or,
  • the time stamp of sending the updated G-BIER service message is added to the message sending timestamp in the follow-up detection information in the follow-up detection option carried by the service message, and at least one path is filled in at least one TLV detection parameters.
  • the detection flag with the flow takes up 8 bits; the Bit0 of the detection flag with the flow is a delay detection flag, and the Bit1 of the detection flag with the flow is a packet loss detection flag; the Bit0 is the detection flag for all The lowest bit of the follow-up detection flag, the Bit1 is the bit adjacent to the Bit0 in the follow-up detection flag.
  • the G-BIER option in the DOH is before the detection option with flow; when the detection with flow is hop-by-hop detection, the The G-BIER option in the DOH is after the flow detection option.
  • the method further includes:
  • the network device is used as an intermediate device between the BFIR in the G-BIER domain and the egress node bit forwarding router BFER, if it does not support G-BIER flow detection, when receiving the G-BIER service message, Directly forward in the G-BIER domain according to the destination IP address of the G-BIER service message.
  • This embodiment also provides an electronic device, where the electronic device includes: a processor and a machine-readable storage medium;
  • the machine-readable storage medium stores machine-executable instructions executable by the processor
  • the processor is configured to execute machine-executable instructions to implement the above method steps.
  • BFIR as the G-BIER domain, and the intermediate BFR between BFIR and BFER will be currently used for network quality detection along with the G-BIER service message
  • the flow detection information transmission based on G-BIER realizes the flow detection of service packets based on G-BIER; at the same time, the BFIR as the G-BIER domain, the intermediate BFR between BFIR and BFER, and the BFER as the G-BIER domain also
  • the detection data currently used for network quality detection will be reported to the analyzer, and finally the analyzer can detect the network quality according to the detection data reported by BFIR, BFER, and intermediate BFR between BFIR and BFER in the G-BIER domain. It realizes the flow detection based on G-BIER service message, which can detect the real packet loss rate and time delay when the G-BIER service message is transmitted in the IPv6 network, which is used to characterize the network quality.
  • Fig. 1 is the flow chart of the first method provided by the embodiment of the present application.
  • Fig. 2 is the structural diagram of the DOH provided by the embodiment of the present application.
  • FIG. 3 is a structural diagram of the G-BIER option provided by the embodiment of the present application.
  • FIG. 4 is a structural diagram of the flow detection option provided by the embodiment of the present application.
  • Fig. 5 is a schematic diagram of the flow detection mark provided by the embodiment of the present application.
  • FIG. 6 is a structural diagram of the flow detection option provided by the embodiment of the present application.
  • FIG. 7 is a structural diagram of the G-BIER service message provided by the embodiment of the present application.
  • FIG. 8 is a flow chart of the second method provided by the embodiment of the present application.
  • FIG. 9 is a flow chart of the third method provided by the embodiment of the present application.
  • FIG. 10 is a schematic diagram of a networking example provided by the present application.
  • Figure 11 is a structural diagram of the device provided by the present application.
  • FIG. 12 is a hardware structural diagram of the device provided by the present application.
  • FIG. 1 is a flow chart of the first method provided by the embodiment of the present application.
  • the method is applied to network devices, where the network devices may be routers, switches, etc., which are not specifically limited in this embodiment.
  • the method may include the following steps:
  • step 101 the network device, acting as a BFIR, forwards the G-BIER service message in the G-BIER domain when receiving the original multicast service message to be detected with the flow.
  • a router supporting the G-BIER capability may be referred to as a bit-forwarding router (BFR: Bit-Forwarding Router), and a domain composed of BFR is referred to as a G-BIER domain.
  • BFR bit-forwarding router
  • the BFR in the G-BIER domain includes the entry node bit forwarding router (BFIR: BFR: Bit-Forwarding Ingress Router), the exit node bit forwarding router (BFER: BFR: Bit-Forwarding Egress Router), between BFIR and BFER The intermediate BFR equipment between them.
  • Original multicast service packets enter the G-BIER domain from the BFIR.
  • the G-BIER service message carries an IPv6 extension header and an IPv6 payload field.
  • the IPv6 payload field may contain the above-mentioned original multicast service message.
  • the IPv6 extension header may include at least one destination option extension header (DOH: Destination Option Header).
  • DOH Destination Option Header
  • this embodiment may at least add a G-BIER option and a flow detection option in one of the DOHs in the IPv6 extension header, that is, the DOH in the final IPv6 extension header includes at least: the G-BIER option and flow detection options.
  • the G-BIER option in the DOH is before the flow detection option; and when the flow detection is hop-by-hop detection, the G-BIER option in the DOH is before the flow detection option after.
  • Figure 2 is the structure of the G-BIER option and the FD option in the DOH when FD is used as end-to-end detection.
  • the G-BIER option is used to indicate packet forwarding in the G-BIER domain.
  • Figure 3 shows an example of the structure of the G-BIER option.
  • the G-BIER option here is consistent with the structure of the existing G-BIER option, which is not specifically limited in this embodiment.
  • the downstream detection option carries a downstream detection flag (Flag) and downstream detection information.
  • Flag downstream detection flag
  • the floating detection option it also follows the option format, in addition to carrying the above floating detection flag and floating detection information, it will also include: option type (Optinon Type), option length (Optinon Length).
  • option type is used to indicate the type of flow detection, and the value can be applied to IETF.
  • the option length may be the number of bytes in the flow detection option except option type and option length.
  • Figure 4 shows an example of the structure of the follow-up detection option.
  • the above-mentioned follow-up detection flag is used to instruct the BFR in the G-BIER domain to perform follow-up detection.
  • the FDFL may occupy 8 bits.
  • Bit0 of the follow-up detection flag is a delay detection flag, for example, when Bit0 is set, it indicates that delay detection is required.
  • Bit0 is the lowest bit of the FDFL. Specifically shown in Figure 5.
  • Bit1 of the follow-through detection flag (a bit adjacent to Bit0 in the follow-through detection flag) is a packet loss detection flag. For example, when Bit1 is set, it indicates that packet loss measurement needs to be performed.
  • the remaining bits of the FDFL can be reserved temporarily, and can be extended and used later.
  • the above-mentioned follow-up detection information includes at least:
  • Flow ID Determined according to packet characteristics such as packet quintuples. Different packets with different packet characteristics have different Flow IDs. Preferably, the Flow ID can occupy 24 bits. It should be emphasized that the Flow ID in the flow detection information in this embodiment is different from the Flow ID carried when the multicast source sends the original multicast service message. In this embodiment, the Flow ID in the flow detection information is It is customized by the above-mentioned network device as BFIR and is prohibited from being changed in the G-BIER domain after setting.
  • Sequence Number It is used to indicate the forwarding sequence of packets with the same packet characteristics. Statistics of packets with different Sequence Numbers under the same Flow ID are convenient for determining the packet loss rate. Examples will be described below, so I won’t go into details here.
  • the Sequence Number can occupy 32 bits. It should be emphasized that the Sequence Number in the flow detection information in this embodiment is different from the Sequence Number carried when the multicast source sends the original multicast service message. In this embodiment, the Sequence Number in the flow detection information is It is customized by the above-mentioned network device as BFIR and is prohibited from being changed in the G-BIER domain after setting.
  • Message Received Timestamp Used to indicate the timestamp of receiving the message.
  • the message receiving timestamp may occupy 64 bits.
  • Message sending timestamp (Timestamp Sent): used to indicate the timestamp of sending the message.
  • the message sending timestamp may occupy 64 bits.
  • the detection information with the flow can also include: timestamp format (TF: Time Format): used to indicate Timestamp format, such as the format defined by Network Time Protocol (NTP: Network Time Protocol) and the format defined by Precision Time Protocol (PTP: Precision Time Protocol).
  • TF Time Format
  • NTP Network Time Protocol
  • PTP Precision Time Protocol
  • the network device when used as the BFIR of the G-BIER domain, when receiving the original multicast service message to be detected with the flow, the original multicast service message will be converted into a G-BIER service message, and The G-BIER domain forwards G-BIER service packets.
  • FIG. 7 shows an example of the structure of the final G-BIER service message.
  • the network device reports the detection data associated with the flow detection information to a designated analyzer so that the analyzer can detect network quality according to the reported detection data.
  • step 101 and this step 102 do not have a fixed time sequence, and they can be executed at the same time, or the G-BIER service message in the above step 101 can be executed first.
  • step 102 and so on are executed, which is not specifically limited in this embodiment.
  • the detection data associated with the above-mentioned flow detection information may directly be the above flow detection information.
  • the detection data associated with the above-mentioned flow-based detection information can also be determined according to the above-mentioned flow-based detection information, for example, the difference between the message sending timestamp and the message receiving time stamp in the above-mentioned flow-based detection information, etc. .
  • This embodiment does not specifically limit the form of the above-mentioned detection data, and finally it only needs to ensure that the analyzer detects the network quality according to the reported detection data.
  • the network device when it is used as the BFIR of the G-BIER domain, it will convert the original multicast service message into a G-BIER service message when it receives the original multicast service message to be detected with the flow , forward the G-BIER service message carrying the flow detection information in the G-BIER domain to realize the flow detection of the G-BIER service message, and report the follow-up information carried by the G-BIER service message to the designated analyzer
  • the detection data associated with the flow detection information enables the analyzer to detect the network quality based on the reported detection data, which realizes the detection based on the flow detection of the G-BIER service message when the G-BIER service message is transmitted in the IPv6 network.
  • the real packet loss rate, delay and other data used to characterize network quality.
  • Figure 1 is a description of an embodiment from the perspective of a network device as a BFIR.
  • the following uses a network device as an intermediate BFR between BFIR and BFER as an example to describe an embodiment:
  • FIG. 8 is a flowchart of a second method provided by an embodiment of the present application. As shown in Figure 8, the process may include:
  • Step 801 the network device is used as an intermediate BFR device between BFIR and BFER in the G-BIER domain. If it supports G-BIER follow-up detection, when receiving a G-BIER service message, the G-BIER service message carries the The follow-up detection information in the follow-up detection option is updated and the updated G-BIER service message is forwarded in the G-BIER domain.
  • updating the follow-up detection information in the follow-up detection option carried by the G-BIER service message may include: updating the G-BIER service message Update the message receiving timestamp in the streaming detection information carried in the streaming detection option to the timestamp of receiving the G-BIER service message; The packet sending timestamp in the detection information is updated to the timestamp of sending the updated G-BIER service packet.
  • updating the above-mentioned on-stream detection information in the on-stream detection option carried by the G-BIER service message may also include: Add the time stamp of receiving the G-BIER service message to the message receiving timestamp in the follow-up detection option carried by the service message, and add the time stamp of receiving the G-BIER service message in the follow-up detection option carried by the G-BIER service message The time stamp of sending the updated G-BIER service message is added to the message sending time stamp in the follow-up flow detection information.
  • the above-mentioned follow-up detection information further includes: at least one TLV (denoted as a TLVs field).
  • each TLV carries other extended follow-up detection information such as path detection parameters.
  • path detection parameters For example, when follow-up detection is used to detect network transmission delay, at least one TLV can carry path detection parameters such as delay parameters; when follow-up Flow detection is used for packet loss statistics, and at least one TLV can carry path detection parameters such as the number of packet loss.
  • the aforementioned updating of the on-stream detection information in the on-stream detection option carried in the G-BIER service message further includes: filling at least one currently detected path detection parameter in the TLVs field.
  • the network device is finally realized as an intermediate BFR device between BFIR and BFER in the G-BIER domain.
  • the G-BIER When supporting G-BIER flow detection, if a G-BIER service message is received, the G-BIER The BIER service message carries the current real-time network quality information, such as updating the follow-up detection information in the follow-up detection option carried by the G-BIER service message and continues to forward it in the G-BIER domain (the forwarding method is similar to the existing BIER message forwarding , will not be described in detail), so as to realize the flow detection of the G-BIER service message in the G-BIER domain.
  • the network device is an intermediate BFR device between BFIR and BFER in the G-BIER domain.
  • the destination IP address of the BIER service message is forwarded in the G-BIER domain.
  • Step 802 the network device, as an intermediate BFR device between BFIR and BFER in the G-BIER domain, reports the detection data related to the detection data related to the detection information in the detection option carried by the updated G-BIER service message to the aforementioned analyzers.
  • step 801 and this step 802 do not have a fixed time sequence, and they can be executed at the same time, or the G-BIER service message in the above step 801 can be executed first.
  • step 802 and so on are executed, which is not specifically limited in this embodiment.
  • the detection data related to the detection information in the follow-up detection option carried by the updated G-BIER service message may be directly included in the updated G-BIER service message.
  • the streaming detection information carried in the streaming detection option can also be determined according to the above streaming detection information, for example, the difference between the packet sending timestamp and the packet receiving timestamp in the streaming detecting information. This embodiment does not specifically limit the form of the above-mentioned detection data, and finally it only needs to ensure that the analyzer detects the network quality according to the reported detection data.
  • the network device when it is used as an intermediate BFR device between BFIR and BFER in the G-BIER domain, if it supports G-BIER follow-up detection, it will carry the current Real-time network quality information, such as updating the packet receiving timestamp and packet sending timestamp in the streaming detection option carried by G-BIER service packets, and continuing to forward them in the G-BIER domain to achieve G - BIER service message in the G-BIER domain with the flow detection, and also report to the specified analyzer the detection data associated with the flow detection information carried in the G-BIER service message so that the analyzer can use the reported detection data Detect network quality, which realizes the flow-based detection of G-BIER service packets to detect the real packet loss rate and time delay when G-BIER service packets are transmitted in the IPv6 network, which are used to characterize the network quality.
  • the current Real-time network quality information such as updating the packet receiving timestamp and packet sending timestamp in the streaming detection option carried by G-BIER service packets, and continuing to
  • FIG. 9 is a flowchart of a third method provided by an embodiment of the present application. As shown in Figure 9, the process may include:
  • Step 901 the network device, as the BFER in the G-BIER domain, records the follow-up detection information carried in the G-BIER service message when receiving the G-BIER service message, and restores the G-BIER service message Forward the original multicast service packet to the multicast receiver.
  • restoring the G-BIER service message to the original multicast service message can be: strip off the outer layer IPv6 header (IPv6 basic header) and IPv6 extension header of the G-BIER service message, and restore the original IPv6 load field Multicast service packets.
  • step 902 the network device, as the BFER in the G-BIER domain, reports the time stamp of receiving the G-BIER service message and the detection data related to the recorded follow-up detection information to the above-mentioned analyzer.
  • Step 901 and this step 902 are not in a fixed order of time, they can be executed at the same time, or the original group broadcast in the above step 801 can be executed first.
  • Step 902 and so on are executed after the broadcast service packet is forwarded to the multicast receiver, which is not specifically limited in this embodiment.
  • the detection data related to the recorded flow detection information can be directly the recorded flow detection information, or can be determined according to the flow detection information, for example, the data in the flow detection information The difference between the packet sending timestamp and the packet receiving timestamp, etc.
  • This embodiment does not specifically limit the form of the above-mentioned detection data, and finally it only needs to ensure that the analyzer detects the network quality according to the reported detection data.
  • the network device When the network device is implemented as a BFER in the G-BIER domain through the process shown in Figure 9, it will report the time stamp of the received G-BIER service message and the detection data related to the recorded follow-up detection information to the analyzer To enable the analyzer to detect network quality, which realizes the flow detection based on G-BIER service packets, and can detect the real packet loss rate and delay when G-BIER service packets are transmitted in the IPv6 network to characterize the network quality data.
  • FIG. 10 is a schematic diagram of a networking of an embodiment provided by the present application.
  • time synchronization is maintained between the analyzer and all BFRs supporting G-BIER follow-the-flow detection in the G-BIER domain through a time synchronization protocol.
  • the multicast source sends an original multicast service message (denoted as message m1).
  • message m1 The structure of the original multicast service message here is similar to the existing multicast message, and will not be repeated here.
  • IPv6 extension header is added to the outer layer of the message m1 and an IPv6 outer layer header (also called an IPv6 basic header) is encapsulated outside the IPv6 extension header, and the message m1 is used as an IPv6 payload.
  • IPv6 outer layer header also called an IPv6 basic header
  • the DOH in the IPv6 extension header includes the G-BIER option and the flow detection option.
  • the G-BIER option and the downstream detection option are described above, and will not be repeated here. If the flow detection in this embodiment is end-to-end flow detection, the G-BIER option in the DOH is before the flow detection option.
  • the destination address in the IPv6 outer header is the next hop, that is, the address of device B.
  • the message m1 is used as the IPv6 payload
  • the IPv6 extension header is added to the outer layer of the message m1
  • the IPv6 outer layer header also called the IPv6 basic header
  • the final message is recorded as a message m2 .
  • Device A sends message m2 to the next hop, that is, device B, and at the same time reports the follow-up detection information carried in message m2 to the analyzer.
  • Device B supports G-BIER follow-up detection.
  • the message m2 When receiving the message m2, it finds that the message m2 carries the follow-up detection option, then parses the IPv6 outer header and IPv6 extension header, counts the number of packets, and counts the Update the message receiving timestamp in the follow-up detection information in the follow-up detection option to the time stamp of receiving message m2; update the message sending time in the follow-up detection information in the follow-up detection option carried by message m2
  • the stamp is updated to the time stamp of the sent message, and at least one path detection parameter is filled in the TLVs field according to the detection requirements; or, the packet receiving time stamp in the follow-up detection information in the follow-up detection option carried by the message m2 Add the timestamp of receiving the message m2 in the G-BIER service message, and add the time to send the G-BIER service message to the message sending timestamp in the follow-up detection information in the follow-up detection option carried by the G-BIER service message
  • the path parameters here may be network parameters such as delay and packet loss.
  • the destination address in the IPv6 outer layer header can be replaced with the next hop, that is, the address of device D.
  • message m3 the message finally processed by device B is denoted as message m3 here.
  • Device B sends message m3 to the next hop, that is, device D, and at the same time reports the follow-up detection information carried in message m3 to the analyzer.
  • Device C does not support G-BIER.
  • As an ordinary IPv6 router after receiving the message m3, it searches for a route and forwards the message m3 according to the destination address in the IPv6 outer header.
  • Device D finds that the message m3 carries the flow detection option when receiving the message m3, then parses the IPv6 outer header and IPv6 extension header, counts the number of packets, and records the G-BIER in the DOH in the IPv6 extension header option and follow-the-flow detection option, strip off the IPv6 outer layer header and IPv6 extension header to restore the above message m1.
  • Device D sends message m1 to the multicast receiver, and at the same time reports to the analyzer the time stamp of device D receiving message m3 and the recorded follow-up detection information.
  • the analyzer After receiving the data reported by device A, device B, and device D, the analyzer calculates the time it takes for the service flow to pass through each network device for the service flow of the same Flow ID, and determines which link is lost. Bag. If multiple sets of packet loss and delay data are continuously tested, the network delay jitter can be determined.
  • the delay can be calculated by the following calculation method:
  • Table 1 shows the delay calculation for the packets of the same Sequence Number with the same Flow ID transmitted in the above G-BIER domain:
  • Timstamp_Sent(A) indicates the timestamp when device A sends the message
  • Timestamp_Received(A) indicates the timestamp when device A receives the message
  • packet loss statistics can be calculated by the following calculation method:
  • Packet statistics for the same Flow ID with different Sequence Numbers If the packet statistics reported by device A are Statis(A), the packet statistics reported by device B are Statis(B), and the packet statistics reported by device D are Statis(D ), the number of lost packets is shown in Table 2:
  • the packet loss rate can be calculated according to the following formula:
  • Packet loss rate number of lost packets/total number of packets with the same Flow ID but different Sequence Numbers.
  • the method for BFR in the G-BIER domain to report detection data to the analyzer can be implemented based on existing telemetry technology such as gRPC, or based on Netconf or other network protocols. This implementation Examples are not specifically limited.
  • FIG. 11 is a structural diagram of a device provided by an embodiment of the present application.
  • the device can be based on the flow detection method of the G-BIER service message of IPv6 multicast, and the device is applied to network equipment, and can include:
  • the message forwarding unit is used to forward the G-BIER service message in the G-BIER domain when the above-mentioned network device is used as a BFIR when receiving the original multicast service message to be detected with the flow; wherein, the G-BIER The service message carries an IPv6 payload field, and the IPv6 payload field contains the original multicast service message; the G-BIER service message also carries an IPv6 extension header, and the DOH in the IPv6 extension header includes at least: G-BIER option and flow detection option ; The G-BIER option is used to indicate message forwarding in the G-BIER domain, and the follow-up detection option carries the follow-up detection flag and flow detection information; the follow-up detection mark is used to indicate nodes in the G-BIER domain The bit-forwarding router BFR performs follow-up detection; the follow-up detection information includes at least: flow number (Flow ID), message serial number (Sequence Number), message receiving timestamp and message sending timestamp; the Flow ID,
  • the detection data reporting unit is configured to report the detection data associated with the flow detection information to a designated analyzer so that the analyzer can detect network quality according to the reported detection data.
  • the message forwarding unit is further used to record the follow-up detection in the G-BIER service message when the above-mentioned network device is used as the BFER of the G-BIER domain when receiving the G-BIER service message
  • the follow-up detection information carried in the option restores the G-BIER service message to the original multicast service message and forwards it to the multicast receiver.
  • the detection data reporting unit is further configured to report the time stamp of receiving the G-BIER service message and the detection data related to the recorded follow-up detection information to the above-mentioned analyzer.
  • the on-stream detection information further includes: TF, which is used to indicate a time stamp format; wherein, the message receiving time stamp and the message sending time stamp comply with the time stamp format indicated by the TF.
  • the message forwarding unit is further configured to, when the network device is used as an intermediate BFR device between BFIR and BFER in the G-BIER domain, if it supports G-BIER follow-up detection, after receiving the G-BIER service report When sending the message, update the follow-up detection information in the follow-up detection option carried by the G-BIER service message, and forward the updated G-BIER service message in the G-BIER domain.
  • the detection data reporting unit is further configured to report the detection data related to the on-stream detection information in the on-stream detection option carried in the updated G-BIER service message to the analyzer.
  • the above message forwarding unit updating the follow-up detection information in the follow-up detection option carried in the G-BIER service message includes:
  • the flow detection information further includes: at least one TLV, and each TLV carries at least one path detection parameter; the path detection parameters at least include: when flow detection is used to detect network transmission delay, the path The detection parameters at least include: a delay parameter; when the flow detection is used for packet loss statistics, the path detection parameters at least include: the number of packet loss.
  • the message forwarding unit updates the follow-up detection information in the follow-up detection option carried by the G-BIER service message to include:
  • the packet sending timestamp in the streaming detection option carried in the service message is updated to the timestamp of sending the updated G-BIER service message, and at least one path is filled in at least one TLV detection parameters; or,
  • the time stamp of sending the updated G-BIER service message is added to the message sending timestamp in the follow-up detection information in the follow-up detection option carried by the service message, and at least one path is filled in at least one TLV detection parameters.
  • the flow detection flag occupies 8 bits; the Bit0 of the flow detection flag is a delay detection flag, and the Bit1 of the flow detection flag is a packet loss detection flag; the Bit0 is the The lowest bit of the follow-through detection flag, the Bit1 is a bit adjacent to the Bit0 in the follow-up detection flag.
  • the G-BIER option in the DOH is before the detection option with flow; when the detection with flow is hop-by-hop detection, the The G-BIER option in the DOH follows the flow detection option.
  • the message forwarding unit is further configured as an intermediate device between BFIR and BFER in the G-BIER domain, if the network device does not support G-BIER follow-up detection, when receiving the G-BIER service message, directly According to the destination IP address of the G-BIER service message, it is forwarded in the G-BIER domain.
  • FIG. 12 is a structural diagram of an electronic device provided by an embodiment of the present application.
  • the hardware structure may include: a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions that can be executed by the processor; Instructions to implement the methods disclosed in the above examples of the present application.
  • the embodiment of the present application also provides a machine-readable storage medium, on which several computer instructions are stored, and when the computer instructions are executed by a processor, the present invention can be realized. Apply the method disclosed by the above example.
  • the above-mentioned machine-readable storage medium may be any electronic, magnetic, optical or other physical storage device, which may contain or store information, such as executable instructions, data, and so on.
  • the machine-readable storage medium can be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage media, or a combination of them.
  • a typical implementing device is a computer, which may take the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, e-mail device, game control device, etc. desktops, tablets, wearables, or any combination of these.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • these computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means,
  • the instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable equipment to produce computer-implemented processing, so that the information executed on the computer or other programmable equipment
  • the instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

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

本申请提供了随流检测方法和电子设备。本申请中，作为G-BIER域的BFIR、介于BFIR与BFER之间的中间BFR会随着G-BIER业务报文将当前用于网络质量检测的随流检测信息传输，这实现了基于G-BIER业务报文随流检测；同时，作为G-BIER域的BFIR、上述中间BFR、作为G-BIER域的BFER也会将当前用于网络质量检测的检测数据上报至分析器，最终分析器可根据G-BIER域中的BFIR、BFER、上述中间BFR上报的检测数据检测网络质量，这实现了基于G-BIER业务报文的随流检测可以检测出G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。

Description

随流检测方法和电子设备 技术领域
本申请涉及网络通信技术领域，特别涉及应用于互联网协议第6版(IPv6：Internet Protocol Version 6)组播的通用位索引显式复制(G-BIER：Generalized BIER)业务报文的随流检测方法和电子设备。
背景技术
基于比特索引的显式复制(BIER：Bit Index Explicit Replication)是一种新型组播技术。和传统组播技术相比，BIER组播技术通过将组播报文目的节点的集合以比特串(Bit String)的方式封装在报文头部进行发送，从而使网络中间节点无需为每一条组播流(Per-flow)建立组播树及保存组播流状态，仅需根据报文头部的目的节点的集合进行复制转发。
结合IPv6和BIER的技术优势，基于IPv6数据平面的G-BIER可在IPv6网络上部署IP组播业务(此时的组播业务报文可称为G-BIER业务报文)，目前，G-BIER数据平面的业务流程、G-BIER控制平面的业务流程已被确定，但G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据，还缺少可实施的测量方法。
发明内容
本申请实施例提供了随流检测方法和电子设备，以实现基于G-BIER业务报文随流检测G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。
本申请实施例提供了一种基于IPv6组播的G-BIER业务报文的随流检测方法，该方法应用于网络设备，该方法包括：
所述网络设备作为G-BIER域的入口节点位转发路由器BFIR，
在接收到待执行随流检测的原始组播业务报文时，在G-BIER域转发G-BIER业务报文；向指定的分析器上报与随流检测信息相关联的检测数据以使所述分析器根据上报的检测数据检测网络质量；
其中，所述G-BIER业务报文携带IPv6扩展头以及IPv6载荷字段；所述IPv6载荷字段包含所述原始组播业务报文；所述IPv6扩展头中目的选项扩展头DOH至少包括：G-BIER选项和随流检测选项；所述G-BIER选项用于指示在所述G-BIER域进行报文转发，所述随流检测选项携带随流检测标记和所述随流检测信息；所述随流检测标记用于指示执行随流检测；所述随流检测信息至少包括：流编号Flow ID、报文序列号Sequence Number、报文接收时间戳和报文发送时间戳；所述Flow ID、Sequence Number是由所述BFIR自定义设置且在设置后被禁止在所述G-BIER域更改；所述Flow ID依据报文特征确定，具有不同报文特征的不同报文的Flow ID不同；所述Sequence Number用于表示相同报文特征的报文转发顺序；所述报文接收时间戳用于指示接收报文的时间戳；所述报文发送时间戳用于指示发送报文的时间戳。
作为一个实施例，该方法进一步包括：
所述网络设备作为所述G-BIER域的出口节点位转发路由器BFER，在接收到G-BIER业务报文时记录G-BIER业务报文中随流检测选项携带的随流检测信息，将所述G-BIER业务报文恢复为原始组播业务报文转发给组播接收者，并将收到所述G-BIER业务报文的时间戳、以及与记录的随流检测信息相关的检测数据上报至所述分析器。
作为一个实施例，所述随流检测信息还包括：
TF，用于指示时间戳格式；
其中，所述报文接收时间戳、报文发送时间戳遵守所述TF指示的时间戳格式。
作为一个实施例，该方法进一步包括：
所述网络设备作为所述G-BIER域中所述BFIR和出口节点位转发路由器BFER之间的中间BFR设备，若支持G-BIER随流检测，在接收到G-BIER业务报文时，将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新并在所述G-BIER域中转发更新后的G-BIER业务报文，将与更新后的G-BIER业务报文携带的随流检测选项中的随流检测信息相关的检测数据上报至所述分析器。
作为一个实施例，所述将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳；或者，
在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳。
作为一个实施例，所述随流检测信息还包括：至少一个TLV，每一TLV携带至少一个路径检测参数；所述路径检测参数至少包括：当随流检测用于检测网络传输时延，所述路径检测参数至少包括：延时参数；当随流检测用于丢包统计，所述路径检测参数至少包括：丢包数；
所述将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数；或者，
在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数。
作为一个实施例，所述随流检测标记占用8bits；所述随流检测标记的Bit0位为延时检测标记，所述随流检测标记的Bit1位为丢包检测标记；所述Bit0位为所述随流检测标记的最低比特位，所述Bit1位为所述随流检测标记中与所述Bit0位相邻的比特位。
作为一个实施例，当所述随流检测为端到端检测时，所述DOH中所述G-BIER选项 在所述随流检测选项之前；当所述随流检测为逐跳检测时，所述DOH中所述G-BIER选项在所述随流检测选项之后。
作为一个实施例，该方法进一步包括：
所述网络设备作为所述G-BIER域中所述BFIR和出口节点位转发路由器BFER之间的中间设备，若不支持G-BIER随流检测，则在接收到G-BIER业务报文时，直接按照G-BIER业务报文的目的IP地址在G-BIER域转发。
本实施例还提供一种电子设备，该电子设备包括：处理器和机器可读存储介质；
所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令；
所述处理器用于执行机器可执行指令，以实现上述方法步骤。
通过本申请的以上技术方案可以看出，在本申请中，作为G-BIER域的BFIR、介于BFIR与BFER之间的中间BFR会随着G-BIER业务报文将当前用于网络质量检测的随流检测信息传输，这实现了基于G-BIER业务报文随流检测；同时，作为G-BIER域的BFIR、介于BFIR与BFER之间的中间BFR、作为G-BIER域的BFER也会将当前用于网络质量检测的检测数据上报至分析器，最终分析器可根据G-BIER域中的BFIR、BFER、介于BFIR与BFER之间的中间BFR上报的检测数据检测网络质量，这实现了基于G-BIER业务报文的随流检测可以检测出G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。
附图说明
图1为本申请实施例提供的第一方法流程图；
图2为本申请实施例提供的DOH的结构图；
图3为本申请实施例提供的G-BIER选项的结构图；
图4为本申请实施例提供的随流检测选项的结构图；
图5为本申请实施例提供的随流检测标记示意图；
图6为本申请实施例提供的随流检测选项的结构图；
图7为本申请实施例提供的G-BIER业务报文的结构图；
图8为本申请实施例提供的第二方法流程图；
图9为本申请实施例提供的第三方法流程图；
图10为本申请提供的实施例组网示意图；
图11为本申请提供的装置结构图；
图12为本申请提供的装置的硬件结构图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
为了使本领域技术人员更好地理解本申请实施例提供的技术方案，并使本申请实施例的上述目的、特征和优点能够更加明显易懂，下面结合附图对本申请实施例中技术方案作进一步详细的说明。
参见图1，图1为本申请实施例提供的第一方法流程图。该方法应用于网络设备，这里的网络设备可为路由器、交换机等，本实施例并不具体限定。
如图1所示，该方法可包括以下步骤：
步骤101，网络设备作为BFIR在接收到待执行随流检测的原始组播业务报文时，在G-BIER域转发G-BIER业务报文。
这里，支持G-BIER能力的路由器可称为位转发路由器(BFR：Bit-Forwarding Router)，而BFR组成的域简称G-BIER域。其中，G-BIER域中的BFR包括入口节点位转发路由器(BFIR：BFR：Bit-Forwarding Ingress Router)、出口节点位转发路由器(BFER：BFR：Bit-Forwarding Egress Router)、介于BFIR和BFER之间的中间BFR设备。原始组播业务报文从BFIR进入G-BIER域。如步骤101描述，一旦BFIR接收到原始组播业务报文时，其会基于预先配置的随流检测方式识别出原始组播业务报文是否需要进行随流检测，当识别出原始组播业务报文需要进行随流检测，则认为该原始组播业务报文为待执行随流检测的原始组播业务报文，之后会在G-BIER域转发G-BIER业务报文。这里，G-BIER业务报文携带IPv6扩展头以及IPv6载荷字段。其中，IPv6载荷字段可包含上述原始组播业务报文。
至于IPv6扩展头，按照IPv6协议，IPv6扩展头中可包括至少一个目的选项扩展头(DOH：Destination Option Header)。可选地，作为一个实施例，本实施例可在IPv6扩展头中的其中一个DOH中至少添加G-BIER选项和随流检测选项，即最终IPv6扩展头中的DOH至少包括：G-BIER选项和随流检测选项。可选地，当随流检测为端到端检测时，DOH中G-BIER选项在随流检测选项之前；而当随流检测为逐跳检测时，DOH中G-BIER选项在随流检测选项之后。图2以随流检测为端到端检测时，DOH中G-BIER选项、随流检测选项的结构。
可选地，在本实施例中，G-BIER选项用于指示在G-BIER域进行报文转发。图3举例示出了G-BIER选项的结构。这里的G-BIER选项与现有定义的G-BIER选项的结构一致，本实施例并不具体限定。
可选地，在本实施例中，随流检测选项携带随流检测标记(Flag)和随流检测信息。需要说明的是，对于随流检测选项，其也遵守选项格式，除了携带上述随流检测标记和随流检测信息外，还会包括：选项类型(Optinon Type)、选项长度(Optinon Length)。其中，选项类型用于指示随流检测类型，取值可向IETF申请。选项长度可为随流检测选项中除选项类型、选项长度之外的字节数。图4举例示出了随流检测选项的结构。
作为一个实施例，上述随流检测标记用于指示G-BIER域中BFR执行随流检测。可选地，在本实施例中，随流检测标记可占用8bits。其中，随流检测标记的Bit0位为延时检测标记，比如当Bit0位置位时表示需要进行延时检测。这里，Bit0位为随流检测标记的最低比特位。具体如图5所示。通常，在一个业务周期内同一业务特征下一般只有一个业务报文中随流检测标记的Bit0位置位表示需要进行延时检测。随流检测标记的Bit1位(随流检测标记中与Bit0位相邻的比特位)为丢包检测标记，比如，当Bit1位置位时表示需要进行丢包测量。在本实施例中，随流检测标记的剩余Bit可暂时保留， 后续可扩展使用。
作为一个实施例，在本实施例中，上述随流检测信息至少包括：
流编号(Flow ID)：依据报文特征比如报文五元组等确定。具有不同报文特征的不同报文的Flow ID不同。优选地，Flow ID可占用24bits。需要强调的是，本实施例中随流检测信息中的Flow ID不同于组播源发送原始组播业务报文时携带的Flow ID，在本实施例中，随流检测信息中的Flow ID是由上述作为BFIR的网络设备自定义设置且在设置后被禁止在所述G-BIER域更改的。
报文序列号(Sequence Number)：用于表示相同报文特征的报文转发顺序，同一Flow ID下不同Sequence Number的报文统计方便确定丢包率，下文会举例描述，这里暂不赘述。可选地，Sequence Number可占用32bits。需要强调的是，本实施例中随流检测信息中的Sequence Number不同于组播源发送原始组播业务报文时携带的Sequence Number，在本实施例中，随流检测信息中的Sequence Number是由上述作为BFIR的网络设备自定义设置且在设置后被禁止在所述G-BIER域更改的。
报文接收时间戳(Timestamp Received)：用于指示接收报文的时间戳。可选地，报文接收时间戳可占用64bits。
报文发送时间戳(Timestamp Sent)：用于指示发送报文的时间戳。可选地，报文发送时间戳可占用64bits。
在本实施例中，优选地，为方便定义报文接收时间戳、报文发送时间戳中时间戳的格式，随流检测信息还可包括：时间戳格式(TF：Time Format)：用于指示时间戳格式，比如网络时间协议(NTP：Network Time Protocol)定义的格式、精确时间协议(PTP：Precision Time Protocol)定义的格式。需要说明的是，上述报文接收时间戳、报文发送时间戳遵守TF指示的时间戳格式。基于上面描述，图6举例示出了随流检测选项的具体结构。
通过上述步骤101，网络设备作为G-BIER域的BFIR时在接收到待执行随流检测的原始组播业务报文，会将原始组播业务报文转换为G-BIER业务报文，并在G-BIER域转发G-BIER业务报文。基于上面描述，以随流检测为端到端检测为例，图7举例示出了最终的G-BIER业务报文的结构。
步骤102，网络设备作为BFIR向指定的分析器上报与上述随流检测信息相关联的检测数据以使所述分析器根据上报的检测数据检测网络质量。
需要注意的是，上述步骤101中的在G-BIER域转发G-BIER业务报文与本步骤102并没有固定的时间先后顺序，其可同时执行，也可先执行上述步骤101中的在G-BIER域转发G-BIER业务报文之后再执行步骤102等，本实施例并不具体限定。
在本步骤102中，作为一个实施例，与上述随流检测信息相关联的检测数据可直接为上述随流检测信息。作为另一个实施例，与上述随流检测信息相关联的检测数据也可依据上述随流检测信息确定，比如为上述随流检测信息中的报文发送时间戳与报文接收时间戳之差等。本实施例不具体限定上述检测数据的形式，最终只要保证分析器根据上报的检测数据检测网络质量即可。
至此，完成图1所示流程。
通过图1所示流程实现了网络设备作为G-BIER域的BFIR时在接收到待执行随流检测的原始组播业务报文，会将原始组播业务报文转换为G-BIER业务报文，在G-BIER域转发携带随流检测信息的G-BIER业务报文以实现G-BIER业务报文的随流检测，同时还向指定的分析器上报与G-BIER业务报文携带的随流检测信息相关联的检测数据以 使分析器根据上报的检测数据检测网络质量，这实现了基于G-BIER业务报文的随流检测来检测出G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。
图1是站在网络设备作为BFIR的角度进行的实施例描述，下面以网络设备作为BFIR和BFER之间的中间BFR为例进行实施例描述：
参见图8，图8为本申请实施例提供的第二方法流程图。如图8所示，该流程可包括：
步骤801，网络设备作为G-BIER域中BFIR和BFER之间的中间BFR设备，若支持G-BIER随流检测，在接收到G-BIER业务报文时，将G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新并在G-BIER域中转发更新后的G-BIER业务报文。
随流检测信息如上描述，则作为一个实施例，本步骤801中，上述将G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新可包括：将G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到G-BIER业务报文的时间戳；将G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送更新后的G-BIER业务报文的时间戳。
为了保证随流检测的精准性，作为另一个实施例，本步骤801中，上述将G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新也可包括：在G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到G-BIER业务报文的时间戳，在G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送更新后的G-BIER业务报文的时间戳。
可选地，在本实施例中，上述随流检测信息还包括：至少一个TLV(记为TLVs字段)。其中，每一TLV携带扩展的其他随流检测信息比如路径检测参数，比如，当随流检测用于检测网络传输时延，可通过至少一个TLV可携带诸如延时参数等路径检测参数；当随流检测用于丢包统计，可通过至少一个TLV携带丢包数等路径检测参数。基于此，上述将G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新还进一步包括：在TLVs字段中填充当前检测到的至少一个路径检测参数。
通过本步骤801，最终实现了网络设备作为G-BIER域中BFIR和BFER之间的中间BFR设备，在支持G-BIER随流检测时，若接收到G-BIER业务报文，会将G-BIER业务报文携带当前实时网络质量信息比如将G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新并继续在G-BIER域转发(转发方式类似现有BIER报文转发，不再赘述)，以实现G-BIER业务报文在G-BIER域的随流检测。需要说明的是，网络设备作为G-BIER域中BFIR和BFER之间的中间BFR设备，当不支持G-BIER随流检测时，则在接收到G-BIER业务报文时，直接按照G-BIER业务报文的目的IP地址在G-BIER域转发。
步骤802，网络设备作为G-BIER域中BFIR和BFER之间的中间BFR设备，将与更新后的G-BIER业务报文携带的随流检测选项中的随流检测信息相关的检测数据上报至上述分析器。
需要注意的是，上述步骤801中的在G-BIER域转发G-BIER业务报文与本步骤802并没有固定的时间先后顺序，其可同时执行，也可先执行上述步骤801中的在G-BIER域转发G-BIER业务报文之后再执行步骤802等，本实施例并不具体限定。
在本步骤802中，作为一个实施例，与更新后的G-BIER业务报文携带的随流检测选项中的随流检测信息相关的检测数据可直接为更新后的G-BIER业务报文所携带的随 流检测选项中的随流检测信息，也可依据上述随流检测信息确定，比如为上述随流检测信息中的报文发送时间戳与报文接收时间戳之差等。本实施例不具体限定上述检测数据的形式，最终只要保证分析器根据上报的检测数据检测网络质量即可。
至此，完成图8所示流程。
通过图8所示流程实现了网络设备作为G-BIER域中BFIR和BFER之间的中间BFR设备时，若支持G-BIER随流检测，则会在收到的G-BIER业务报文携带当前实时网络质量信息比如将G-BIER业务报文携带的随流检测选项中随流检测信息内的报文接收时间戳、报文发送时间戳等进行更新并继续在G-BIER域转发以实现G-BIER业务报文在G-BIER域的随流检测，同时还向指定的分析器上报与G-BIER业务报文携带的随流检测信息相关联的检测数据以使分析器根据上报的检测数据检测网络质量，这实现了基于G-BIER业务报文的随流检测来检测出G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。
下面以网络设备作为BFER为例进行实施例描述：
参见图9，图9为本申请实施例提供的第三方法流程图。如图9所示，该流程可包括：
步骤901，网络设备作为G-BIER域中BFER，在接收到G-BIER业务报文时记录G-BIER业务报文中随流检测选项携带的随流检测信息，将G-BIER业务报文恢复为原始组播业务报文转发给组播接收者。
这里，将G-BIER业务报文恢复为原始组播业务报文可为：剥掉G-BIER业务报文的外层IPv6头(IPv6基本报头)和IPv6扩展头，恢复IPv6载荷字段中的原始组播业务报文。
步骤902，网络设备作为G-BIER域中BFER将收到所述G-BIER业务报文的时间戳、以及与记录的随流检测信息相关的检测数据上报至上述分析器。
需要注意的是，上述步骤901中将原始组播业务报文转发给组播接收者与本步骤902并没有固定的时间先后顺序，其可同时执行，也可先执行上述步骤801中将原始组播业务报文转发给组播接收者之后再执行步骤902等，本实施例并不具体限定。
在本步骤902中，作为一个实施例，与记录的随流检测信息相关的检测数据可直接为记录的随流检测信息，也可依据该随流检测信息确定比如为该随流检测信息中的报文发送时间戳与报文接收时间戳之差等。本实施例不具体限定上述检测数据的形式，最终只要保证分析器根据上报的检测数据检测网络质量即可。
至此，完成图9所示流程。
通过图9所示流程实现了网络设备作为G-BIER域中BFER时，则会将收到G-BIER业务报文的时间戳、以及与记录的随流检测信息相关的检测数据上报至分析器以使分析器检测网络质量，这实现了基于G-BIER业务报文的随流检测可检测出G-BIER业务报文在IPv6网络中传输时的真实丢包率、时延等用于表征网络质量的数据。
下面通过一个具体实施例并结合图1、图8、图9所示流程进行描述：
参见图10，图10为本申请提供的实施例组网示意图。在本实施例中，分析器和G-BIER域中所有支持G-BIER随流检测的BFR之间通过时间同步协议保持时间同步。
如图10所示，组播源发送原始组播业务报文(记为报文m1)。这里的原始组播业务报文的结构类似现有组播报文，不再赘述。
设备A作为G-BIER域的BFIR，接收到报文m1后，解析报文m1的报文特征比如 源地址、目的地址等，基于解析出的报文特征并按照预先配置的随流检测识别方式识别出报文m1需要进行随流检测，则在报文m1的外层添加IPv6扩展头以及再在IPv6扩展头外封装IPv6外层头(也称IPv6基础报头)，报文m1作为IPv6载荷。其中，IPv6扩展头中DOH包括G-BIER选项和随流检测选项。G-BIER选项和随流检测选项如上描述，这里不再赘述。本实施例中的随流检测假若为端到端随流检测，则DOH中G-BIER选项在随流检测选项之前。IPv6外层头中的目的地址为下一跳即设备B的地址。这里，将报文m1作为IPv6载荷，在报文m1的外层添加IPv6扩展头以及再在IPv6扩展头外封装IPv6外层头(也称IPv6基础报头)最终形成的报文记为报文m2。
设备A向下一跳即设备B发送报文m2，同时向分析器上报报文m2携带的随流检测信息。
设备B支持G-BIER随流检测，在收到报文m2时发现报文m2携带随流检测选项，则解析IPv6外层头和IPv6扩展头，统计报文数量，并将报文m2携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到报文m2的时间戳；将报文m2携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送报文的时间戳，并根据检测要求在TLVs字段中填充至少一个路径检测参数；或者，在报文m2携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到报文m2的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送G-BIER业务报文的时间戳，并根据检测要求在TLVs字段中填充至少一个路径检测参数。这里的路径参数可为时延、丢包等网络参数。之后可替换IPv6外层头中的目的地址为下一跳即设备D的地址。为便于描述，这里将设备B最终处理得到的报文记为报文m3。
设备B向下一跳即设备D发送报文m3，同时向分析器上报报文m3携带的随流检测信息。
设备C不支持G-BIER，作为普通的IPv6路由器，在收到报文m3后，按照IPv6外层头中的目的地址查找路由转发报文m3。
设备D作为BFER，在接收到报文m3时发现报文m3携带随流检测选项，则解析IPv6外层头和IPv6扩展头，统计报文数量，并记录IPv6扩展头中DOH内的G-BIER选项和随流检测选项，剥掉IPv6外层头和IPv6扩展头恢复出上述报文m1。
设备D向组播接收者发送报文m1，同时向分析器上报设备D接收到报文m3的时间戳和记录的随流检测信息。
分析器收到设备A、设备B、设备D上报的数据后，针对同一Flow ID的业务流，计算出该业务流经过每一台网络设备所消耗的时间，以及确定在哪一条链路存在丢包。如果连续测试多组丢包和多组时延数据，则可以确定网络时延抖动。
可选地，作为一个实施例，时延可通过以下计算方法计算：
针对同一Flow ID的同一Sequence Number的报文在上述G-BIER域传输时时延计算如表1所示：
Figure PCTCN2021096929-appb-000001
Figure PCTCN2021096929-appb-000002
表1
在表1中，Timstamp_Sent(A)表示设备A发送报文的时间戳，Timestamp_Received(A)表示设备A接收报文的时间戳，其他依次类推，不再一一解释。
可选地，作为一个实施例，丢包统计可通过以下计算方法计算：
针对同一Flow ID不同Sequence Number的报文统计：假如设备A上报的报文统计为Statis(A)，设备B上报的报文统计为Statis(B)，设备D上报的报文统计为Statis(D)，则丢包数如表2所示：
测量点 丢包数
设备A与设备B间链路丢包数 Statis(B)-Statis(A)
设备B与设备D间链路丢包数 Statis(D)-Statis(B)
表2
而丢包率可按照如下公式计算：
丢包率＝丢包数/同一Flow ID不同Sequence Number下的报文总数。
至此，完成实施例的描述。需要说明的是，在本实施例中，G-BIER域中中BFR在向分析器上报检测数据的方法可以基于现有的遥测技术实现比如gRPC、也可以基于Netconf或者其他网络协议实现，本实施例并不具体限定。
以上对本申请实施例提供的方法进行了描述，下面对本申请实施例提供的装置进行描述：
参见图11，图11为本申请实施例提供的装置结构图。该装置可基于IPv6组播的G-BIER业务报文的随流检测方法，该装置应用于网络设备，可包括：
报文转发单元，用于当上述网络设备作为BFIR，则在接收到待执行随流检测的原始组播业务报文时，在G-BIER域转发G-BIER业务报文；其中，G-BIER业务报文携带IPv6载荷字段，IPv6载荷字段包含所述原始组播业务报文；G-BIER业务报文还携带IPv6扩展头，IPv6扩展头中DOH至少包括：G-BIER选项和随流检测选项；G-BIER选项用于指示在所述G-BIER域进行报文转发，随流检测选项携带随流检测标记和随流检测信息；随流检测标记用于指示所述G-BIER域中节点位转发路由器BFR执行随流检测；随流检测信息至少包括：流编号(Flow ID)、报文序列号(Sequence Number)、报文接收时间戳和报文发送时间戳；所述Flow ID、Sequence Number是由所述BFIR自定义设置且在设置后被禁止在所述G-BIER域更改；所述Flow ID是依据报文特征确定的，具有不同报文特征的不同报文的Flow ID不同；所述Sequence Number用于表示相同报文特征的报文转发顺序；所述报文接收时间戳用于指示接收报文的时间戳；所述报文发送时间戳用于指示发送报文的时间戳；
检测数据上报单元，用于向指定的分析器上报与所述随流检测信息相关联的检测数据以使所述分析器根据上报的检测数据检测网络质量。
可选地，作为一个实施例，报文转发单元，进一步用于当上述网络设备作为G-BIER 域的BFER，在接收到G-BIER业务报文时记录G-BIER业务报文中随流检测选项携带的随流检测信息，将所述G-BIER业务报文恢复为原始组播业务报文转发给组播接收者。
检测数据上报单元进一步用于将收到所述G-BIER业务报文的时间戳、以及与记录的随流检测信息相关的检测数据上报至上述分析器。
可选地，所述随流检测信息还包括：TF，用于指示时间戳格式；其中，所述报文接收时间戳、报文发送时间戳遵守所述TF指示的时间戳格式。
可选地，报文转发单元，进一步用于当网络设备作为所述G-BIER域中BFIR和BFER之间的中间BFR设备，若支持G-BIER随流检测，在接收到G-BIER业务报文时，将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新并在所述G-BIER域中转发更新后的G-BIER业务报文。
检测数据上报单元进一步用于将与更新后的G-BIER业务报文携带的随流检测选项中的随流检测信息相关的检测数据上报至所述分析器。
可选地，上述报文转发单元将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳；或者，
在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳。
可选地，所述随流检测信息还包括：至少一个TLV，每一TLV携带至少一个路径检测参数；所述路径检测参数至少包括：当随流检测用于检测网络传输时延，所述路径检测参数至少包括：延时参数；当随流检测用于丢包统计，所述路径检测参数至少包括：丢包数。
基于此，报文转发单元将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数；或者，
在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数。
可选地，所述随流检测标记占用8bits；所述随流检测标记的Bit0位为延时检测标记，所述随流检测标记的Bit1位为丢包检测标记；所述Bit0位为所述随流检测标记的最低比特位，所述Bit1位为所述随流检测标记中与所述Bit0位相邻的比特位。
可选地，当所述随流检测为端到端检测时，所述DOH中所述G-BIER选项在所述随流检测选项之前；当所述随流检测为逐跳检测时，所述DOH中所述G-BIER选项在所 述随流检测选项之后。
可选地，报文转发单元进一步当网络设备作为G-BIER域中BFIR和BFER之间的中间设备，若不支持G-BIER随流检测，则在接收到G-BIER业务报文时，直接按照G-BIER业务报文的目的IP地址在G-BIER域转发。
至此，完成图11所示装置的结构描述。
本申请实施例还提供了图11所示装置的硬件结构。参见图12，图12为本申请实施例提供的电子设备结构图。如图12所示，该硬件结构可包括：处理器和机器可读存储介质，机器可读存储介质存储有能够被所述处理器执行的机器可执行指令；所述处理器用于执行机器可执行指令，以实现本申请上述示例公开的方法。
基于与上述方法同样的申请构思，本申请实施例还提供一种机器可读存储介质，所述机器可读存储介质上存储有若干计算机指令，所述计算机指令被处理器执行时，能够实现本申请上述示例公开的方法。
示例性的，上述机器可读存储介质可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是：RAM(Radom Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、dvd等)，或者类似的存储介质，或者它们的组合。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可以由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其它可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其它可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
而且，这些计算机程序指令也可以存储在能引导计算机或其它可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或者多个流程和/或方框图一个方框或者多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其它可编程数据处理设备上，使得在计算机或者其它可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计 算机或其它可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (10)

  1. 一种基于IPv6组播的G-BIER业务报文的随流检测方法，其特征在于，该方法应用于网络设备，该方法包括：
    所述网络设备作为G-BIER域的入口节点位转发路由器BFIR，
    在接收到待执行随流检测的原始组播业务报文时，在G-BIER域转发G-BIER业务报文；
    向指定的分析器上报与随流检测信息相关联的检测数据以使所述分析器根据上报的检测数据检测网络质量；
    其中，所述G-BIER业务报文携带IPv6扩展头以及IPv6载荷字段；
    所述IPv6载荷字段包含所述原始组播业务报文；
    所述IPv6扩展头中目的选项扩展头DOH至少包括：G-BIER选项和随流检测选项；所述G-BIER选项用于指示在所述G-BIER域进行报文转发，所述随流检测选项携带随流检测标记和所述随流检测信息；所述随流检测标记用于指示执行随流检测；所述随流检测信息至少包括：流编号Flow ID、报文序列号Sequence Number、报文接收时间戳和报文发送时间戳；所述Flow ID、Sequence Number是由所述BFIR自定义设置且在设置后被禁止在所述G-BIER域更改；所述Flow ID依据报文特征确定，具有不同报文特征的不同报文的Flow ID不同；所述Sequence Number用于表示相同报文特征的报文转发顺序；所述报文接收时间戳用于指示接收报文的时间戳；所述报文发送时间戳用于指示发送报文的时间戳。
  2. 根据权利要求1所述的方法，其特征在于，该方法进一步包括：
    所述网络设备作为所述G-BIER域的出口节点位转发路由器BFER，在接收到G-BIER业务报文时记录G-BIER业务报文中随流检测选项携带的随流检测信息，将所述G-BIER业务报文恢复为原始组播业务报文转发给组播接收者，并将收到所述G-BIER业务报文的时间戳、以及与记录的随流检测信息相关的检测数据上报至所述分析器。
  3. 根据权利要求1所述的方法，其特征在于，所述随流检测信息还包括：
    TF，用于指示时间戳格式；
    其中，所述报文接收时间戳、报文发送时间戳遵守所述TF指示的时间戳格式。
  4. 根据权利要求1所述的方法，其特征在于，该方法进一步包括：
    所述网络设备作为所述G-BIER域中所述BFIR和出口节点位转发路由器BFER之间的中间BFR设备，若支持G-BIER随流检测，在接收到G-BIER业务报文时，将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新并在所述G-BIER域中转发更新后的G-BIER业务报文，将与更新后的G-BIER业务报文携带的随流检测选项中的随流检测信息相关的检测数据上报至所述分析器。
  5. 根据权利要求1所述的方法，其特征在于，所述将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
    将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳；或者，
    在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳。
  6. 根据权利要求4所述的方法，其特征在于，所述随流检测信息还包括：至少一个TLV，每一TLV携带至少一个路径检测参数；所述路径检测参数至少包括：当随流检测用于检测网络传输时延，所述路径检测参数至少包括：延时参数；当随流检测用于 丢包统计，所述路径检测参数至少包括：丢包数；
    所述将所述G-BIER业务报文携带的随流检测选项中的随流检测信息进行更新包括：
    将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳更新为接收到所述G-BIER业务报文的时间戳；将所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳更新为发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数；或者，
    在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文接收时间戳中添加接收到所述G-BIER业务报文的时间戳，在所述G-BIER业务报文携带的随流检测选项中的随流检测信息中的报文发送时间戳中添加发送所述更新后的G-BIER业务报文的时间戳，并在至少一个TLV中填充至少一个路径检测参数。
  7. 根据权利要求1所述的方法，其特征在于，所述随流检测标记占用8bits；
    所述随流检测标记的Bit0位为延时检测标记，所述随流检测标记的Bit1位为丢包检测标记；所述Bit0位为所述随流检测标记的最低比特位，所述Bit1位为所述随流检测标记中与所述Bit0位相邻的比特位。
  8. 根据权利要求1所述的方法，其特征在于，
    当所述随流检测为端到端检测时，所述DOH中所述G-BIER选项在所述随流检测选项之前；
    当所述随流检测为逐跳检测时，所述DOH中所述G-BIER选项在所述随流检测选项之后。
  9. 根据权利要求1所述的方法，其特征在于，该方法进一步包括：
    所述网络设备作为所述G-BIER域中所述BFIR和出口节点位转发路由器BFER之间的中间设备，若不支持G-BIER随流检测，则在接收到G-BIER业务报文时，按照G-BIER业务报文的目的IP地址在G-BIER域转发。
  10. 一种电子设备，其特征在于，该电子设备包括：处理器和机器可读存储介质；
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令；
    所述处理器用于执行机器可执行指令，以实现权利要求1-9任一项的方法步骤。
PCT/CN2021/096929 2021-05-28 2021-05-28 随流检测方法和电子设备 WO2022246837A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202180001399.3A CN115699685A (zh) 2021-05-28 2021-05-28 随流检测方法和电子设备
EP21942411.6A EP4149057A4 (en) 2021-05-28 2021-05-28 IN SITU FLOW INFORMATION TELEMETRY METHOD AND ELECTRONIC DEVICE
PCT/CN2021/096929 WO2022246837A1 (zh) 2021-05-28 2021-05-28 随流检测方法和电子设备
US18/001,463 US20230231780A1 (en) 2021-05-28 2021-05-28 In-situ flow detection methods and electronic devices
JP2022577620A JP7488921B2 (ja) 2021-05-28 2021-05-28 インサイチュフロー検出方法及び電子デバイス

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/096929 WO2022246837A1 (zh) 2021-05-28 2021-05-28 随流检测方法和电子设备

Publications (1)

Publication Number Publication Date
WO2022246837A1 true WO2022246837A1 (zh) 2022-12-01

Family

ID=84228389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/096929 WO2022246837A1 (zh) 2021-05-28 2021-05-28 随流检测方法和电子设备

Country Status (5)

Country Link
US (1) US20230231780A1 (zh)
EP (1) EP4149057A4 (zh)
JP (1) JP7488921B2 (zh)
CN (1) CN115699685A (zh)
WO (1) WO2022246837A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116668343A (zh) * 2023-07-31 2023-08-29 新华三技术有限公司 一种随流检测方法、装置、设备及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4074013A1 (en) * 2019-12-10 2022-10-19 Telefonaktiebolaget LM Ericsson (publ) Mechanism to enable third party services and applications discovery in distributed edge computing environment
CN113949650A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 随流检测方法及相关设备
CN114598635A (zh) * 2020-12-02 2022-06-07 华为技术有限公司 报文传输的方法和装置
CN114598634A (zh) * 2020-12-02 2022-06-07 华为技术有限公司 报文传输的方法、获取对应关系的方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104067559A (zh) * 2012-12-31 2014-09-24 华为技术有限公司 组播通道的性能检测方法、装置和系统
CN106161128A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 一种组播数据流监测方法、装置及组播转发设备
WO2018177437A1 (zh) * 2017-03-31 2018-10-04 新华三技术有限公司 路径探测

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107566280A (zh) 2016-06-30 2018-01-09 上海诺基亚贝尔股份有限公司 验证组播数据路径的方法和路由器设备
WO2018161221A1 (zh) * 2017-03-06 2018-09-13 华为技术有限公司 组播业务处理方法及接入设备
CN114189473B (zh) * 2019-06-06 2023-07-14 华为技术有限公司 一种报文的发送方法和装置
CN112468397B (zh) * 2019-09-09 2023-09-26 华为技术有限公司 一种IPv6报文的处理方法及装置
CN112714034B (zh) 2019-10-26 2022-09-23 华为技术有限公司 组播报文的处理方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104067559A (zh) * 2012-12-31 2014-09-24 华为技术有限公司 组播通道的性能检测方法、装置和系统
CN106161128A (zh) * 2015-04-09 2016-11-23 中兴通讯股份有限公司 一种组播数据流监测方法、装置及组播转发设备
WO2018177437A1 (zh) * 2017-03-31 2018-10-04 新华三技术有限公司 路径探测

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4149057A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116668343A (zh) * 2023-07-31 2023-08-29 新华三技术有限公司 一种随流检测方法、装置、设备及存储介质
CN116668343B (zh) * 2023-07-31 2023-10-31 新华三技术有限公司 一种随流检测方法、装置、设备及存储介质

Also Published As

Publication number Publication date
JP7488921B2 (ja) 2024-05-22
EP4149057A4 (en) 2023-08-02
JP2023530994A (ja) 2023-07-20
CN115699685A (zh) 2023-02-03
US20230231780A1 (en) 2023-07-20
EP4149057A1 (en) 2023-03-15

Similar Documents

Publication Publication Date Title
WO2022246837A1 (zh) 随流检测方法和电子设备
US10623123B2 (en) Virtual HDBaseT link
US7327676B2 (en) Data transmission control method, program therefor and data transmission unit using the same
CA2469169C (en) Method and apparatus for determination of network topology
JP7468969B2 (ja) 第１のネットワークノードにおいて使用される装置及びコントローラにおいて使用される装置
CN111602370B (zh) 使用有限额外字节的带内遥测
US20050281259A1 (en) Method of generating a monitoring datagram
WO2016000513A1 (zh) 更新业务流报文的处理方式的方法及装置
US8885502B2 (en) Feedback protocol for end-to-end multiple path network systems
US9253237B2 (en) Rich media status and feedback for devices and infrastructure components using in path signaling
CN110943935A (zh) 一种实现数据传输的方法、装置和系统
US20220294712A1 (en) Using fields in an encapsulation header to track a sampled packet as it traverses a network
US11057299B2 (en) Real-time video transmission method for multipath network
JP2004007361A (ja) データ送信制御方法及びこの方法のプログラム並びにこれを用いるデータ送信装置
US20230327983A1 (en) Performance measurement in a segment routing network
JP2008167034A (ja) 通信性能測定方法
CN110784378A (zh) 使用twamp实现精准流量均衡的方法及装置
WO2022198560A1 (zh) 随流检测方法和电子设备
JP4938042B2 (ja) フロー情報送信装置、中間装置、フロー情報送信方法およびプログラム
JP2004312725A5 (zh)
WO2023184218A1 (zh) 通过bgp下发随流检测配置的方法及装置
WO2022088994A1 (zh) 性能测量的方法、装置及系统
KR100708589B1 (ko) ＩＰｖ6 패킷망에서 타임스탬프 메시지를 이용한 홉별가용속도 측정 방법
CN111211959A (zh) 一种虚拟网络路由权重设置的方法

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2022577620

Country of ref document: JP

Kind code of ref document: A

Ref document number: 2021942411

Country of ref document: EP

Effective date: 20221206

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

Ref document number: 21942411

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE