Multicast service flow detection method and device

Abstract

The embodiment of the invention provides a multicast service flow detection method and device, and relates to the technical field of communication, and the method comprises the steps that a first node receives a multicast service flow sent by a multicast source, and packages a message header for a data message in the multicast service flow; wherein the message header comprises a detection identifier, a first field, a second field and a third field, the detection identifier is used for identifying that the multicast service flow is the multicast service flow detected along with the flow, the first field is used for indicating the detection period of the multicast service flow, and the second field is used for indicating the detection period of the multicast service flow. The second field is used for indicating whether the data message has a packet loss detection dyeing mark or not, and the third field is used for indicating whether the data message participates in time delay detection or not; and sending the data message packaged with the message header to a second node of the next hop. According to the embodiment of the invention, the existing fields in the message header are utilized to indicate the parameters detected along with the flow, and the detection of the multicast service flow can be realized without adding or expanding the fields in the message header.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for detecting a multicast service flow. Background Art

[0002] As Internet Protocol Version 6 (IPv6) enters the implementation stage, major operators are transforming their existing networks to IPv6, from applications (APP), terminals, management systems, business systems to metropolitan area networks and backbone networks. While transforming the network to unicast, they are also transforming multicast. The newly defined multicast protocol must adapt to the trend of IPv6 evolution, and the new multicast also requires flow detection technology.

[0003] Multicast, also known as multi-target broadcast or multicast, is a method of communication between a sender and multiple receivers in a network. Bit Index Explicit Replication (BIER) is a new type of multicast forwarding technology architecture, which is specifically used to build a multicast forwarding path. This technology proposes a multicast technology architecture for building a multicast distribution tree, which not only meets the situation of the increasing multicast traffic, but also reduces the cost of operation.

[0004] The Internet Engineering Task Force (IETF) draft "draft-ietf-bier-pmmm-oam" proposed a new multicast quality detection solution, which adds a BIER message header to the IPv6 message to achieve the purpose of transmitting BIER multicast messages in the IPv6 network. However, the draft does not specify how to detect the BIER multicast service flow, so the transmission reliability of the BIER multicast service flow cannot be guaranteed. Summary of the invention

[0005] The embodiments of the present application provide a multicast service flow detection method and device, which can realize the detection of BIER multicast flow.

[0006] In a first aspect, an embodiment of the present application provides a multicast service flow detection method, which is applied to a first node, and the method includes:

[0007] receiving a multicast service flow sent by a multicast source, wherein the multicast service flow includes at least one data message;

[0008] Encapsulating a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate the detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection;

[0009] A data message encapsulated with the message header is sent to a second node, where the second node is a next-hop node of the first node.

[0010] In some implementations, the second field and the third field belong to an Operations, Administration, and Maintenance (OAM) field in the message header.

[0011] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0012] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0013] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0014] In some embodiments, the method further comprises:

[0015] Sending first detection information and second detection information of the first node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the first node, and the number and timestamp of the data packets received by the first node within the detection period; the second detection information includes the detection identifier, the exit identifier of the first node, and the number and timestamp of the data packets encapsulated with the message header sent by the first node within the detection period;

[0016] This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow according to the first detection information and the second detection information.

[0017] In a second aspect, an embodiment of the present application provides a multicast service flow detection method, which is applied to a second node, and the method includes:

[0018] Receive a data message encapsulated with a message header and sent by a first node; the first node is a previous hop node of the second node, the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected with the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection;

[0019] A data message encapsulated with the message header is sent to a third node, where the third node is a next-hop node of the second node.

[0020] In some implementations, the second field and the third field belong to an OAM field in the packet header.

[0021] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0022] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0023] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0024] In some embodiments, the method further comprises:

[0025] Sending first detection information and second detection information of the second node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the second node, and the number and timestamp of the data packets received by the second node within the detection period; the second detection information includes the detection identifier, the exit identifier of the second node, and the number and timestamp of the data packets encapsulated with the message header sent by the second node within the detection period;

[0026] This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow based on the first detection information and the second detection information.

[0027] In a third aspect, an embodiment of the present application provides a multicast service flow detection device, which is applied to a first node, and the device includes:

[0028] A receiving module, configured to receive a multicast service flow sent by a multicast source, wherein the multicast service flow includes at least one data message;

[0029] An encapsulation module, configured to encapsulate a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection;

[0030] The sending module is used to send the data message encapsulated with the message header to the second node, and the second node is the next hop node of the first node.

[0031] In some implementations, the second field and the third field belong to an OAM field in the packet header.

[0032] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0033] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0034] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0035] In some implementations, the sending module is further configured to:

[0036] Sending first detection information and second detection information of the first node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the first node, and the number and timestamp of the data packets received by the first node within the detection period; the second detection information includes the detection identifier, the exit identifier of the first node, and the number and timestamp of the data packets encapsulated with the message header sent by the first node within the detection period;

[0037] This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow according to the first detection information and the second detection information.

[0038] In a fourth aspect, an embodiment of the present application provides a multicast service flow detection device, which is applied to a second node, and the device includes:

[0039] A receiving module, configured to receive a data message encapsulated with a message header and sent by a first node; the first node is a previous hop node of the second node, the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected with the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection;

[0040] The sending module is used to send the data message encapsulated with the message header to a third node, and the third node is the next hop node of the second node.

[0041] In some implementations, the second field and the third field belong to an OAM field in the packet header.

[0042] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0043] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0044] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0045] In some implementations, the sending module is further configured to:

[0046] Sending first detection information and second detection information of the second node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the second node, and the number and timestamp of the data packets received by the second node within the detection period; the second detection information includes the detection identifier, the exit identifier of the second node, and the number and timestamp of the data packets encapsulated with the message header sent by the second node within the detection period;

[0047] This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow based on the first detection information and the second detection information.

[0048] In a fifth aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, wherein the processor is communicatively connected to the interface circuit;

[0049] The interface circuit is used to communicate with other communication devices;

[0050] The processor is used to implement the multicast service flow detection method provided in the first aspect, or the multicast service flow detection method provided in the second aspect.

[0051] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, a multicast service flow detection method as provided in the first aspect is implemented, or a multicast service flow detection method as provided in the second aspect is implemented.

[0052] The multicast service flow detection method and device provided in the embodiment of the present application can detect the multicast service flow by using the existing fields in the message header to indicate the parameters of the flow detection, without adding or extending the fields in the message header. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0054] Figure 1 A schematic diagram of the format of a data message provided in an embodiment of the present application;

[0055] Figure 2 It is a schematic diagram of the system architecture of a multicast detection domain provided in an embodiment of the present application;

[0056] Figure 3 A flowchart of a multicast service flow detection method provided in an embodiment of the present application;

[0057] Figure 4 This is a schematic diagram of the coloring mark distribution of the data message in the embodiment of the present application;

[0058] Figure 5 A schematic diagram of another data message format provided in an embodiment of the present application;

[0059] Figure 6 A schematic diagram of the structure of a segment-by-segment detection mode provided in an embodiment of the present application;

[0060] Figure 7 A schematic diagram of the structure of an end-to-end detection mode provided in an embodiment of the present application;

[0061] Figure 8 A program module diagram of a multicast service flow detection device provided in an embodiment of the present application Figure 1 ;

[0062] Fig. 9 A program module diagram of a multicast service flow detection device provided in an embodiment of the present application Figure 2 ;

[0063] Fig.10 A schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0065] The terms "first", "second", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, for example, they can be implemented in an order other than those given in the diagrams or descriptions of the embodiments of this application.

[0066] The term "module" used in the embodiments of the present application refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or a combination of hardware and software code that can perform the functions associated with the element.

[0067] Multicast, also known as multi-target broadcast or multicast, is a method of communication between a sender and multiple receivers in a network. A multicast source sends a message to a specific multicast address. Unlike a unicast address, this multicast address does not belong to a certain host, but to a group of hosts. A multicast address represents a group, and all hosts that need to receive multicast messages join this group. Multicast technology can be applied to point-to-multipoint application scenarios, such as media broadcasting, event notification, status monitoring, data collection, network auctions, etc., as well as to multipoint-to-multipoint application scenarios, such as multipoint conferencing, database synchronization, etc.

[0068] The following is an explanation of some of the terms involved in the embodiments of the present application:

[0069] OAM: Operations, Administration, and Maintenance, refers to the division of network management work into three categories: operations, administration, and maintenance, referred to as OAM, based on the actual needs of the operator's network operations. Operations mainly complete the analysis, prediction, planning, and configuration of daily networks and services; maintenance mainly involves daily operational activities such as testing and fault management of the network and its services.

[0070] In-situ Flow Information Telemetry (IFIT) is a flow detection technology that specifically marks (colors) the actual service flow and performs packet loss and delay detection on the characteristic fields. Among them, IFIT technology does not require external probes, carries OAM instructions in the message header, obtains link performance based on the delay and bit error experienced by the colored bits, and embeds the measurement results in the specified field of the header. The processing node collects data and reports it based on the OAM instruction information in the header.

[0071] BFIR: Bit Forwarding Ingress Router, the node where multicast data traffic enters the BIER domain, responsible for BIER encapsulation of messages entering the BIER network.

[0072] BFR: Bit Forwarding Router, an intermediate node for forwarding multicast data traffic in the BIER domain, responsible for forwarding BIER messages.

[0073] BFER: Bit Forwarding Egress Router, the node where multicast data traffic flows out of the BIER domain, is responsible for decapsulating BIER messages and forwarding them to multicast receivers.

[0074] MSR: Multicast Segment Routing.

[0075] MSR6: Multicast Segment Routing Over IPv6.

[0076] BE: Best Effort mode.

[0077] BIER: It is a new type of multicast forwarding technology architecture. By encapsulating the set of destination nodes that the multicast message is to reach in the form of a bit string (BS) in the message header, it makes it unnecessary for intermediate nodes in the network to perceive the multicast service and maintain the multicast flow status. It can better solve the problems existing in traditional IP multicast technology and provide good multicast service scalability.

[0078] In the BIER network, the forwarding of multicast messages relies on the BitIndex Forwarding Table (BIFT) established by BFR through BIER technology, so that multicast messages only need to be copied and forwarded according to the bit string. The Internet Engineering Task Force (IETF) draft "draft-ietf-bier-pmmm-oam" proposed a new multicast quality detection scheme, which adds a BIER message header to the IPv6 message to achieve the purpose of transmitting BIER multicast messages in the IPv6 network. However, the draft does not specify how to implement the detection of BIER multicast service flows, so the transmission reliability of BIER multicast service flows cannot be guaranteed.

[0079] In some embodiments, the OAM field is considered when defining the BIER message header and the MSR BE message header, referring to Figure 1 , Figure 1 The following is a schematic diagram of a data message format provided in an embodiment of the present application. The meanings of the various fields in the above data message are:

[0080] Version: 4 bits, version number.

[0081] Traffic Class: 8 bits, transmission class.

[0082] Flow Label: flow label.

[0083] Payload Length: 16 bits, payload length.

[0084] Hop Limit: 8 bits, hop limit.

[0085] Source Address: 32 bits, used as the IPv6 source address.

[0086] Destination Address: 32 bits, used as the IPv6 destination address.

[0087] Next Header: 8 bits, used to identify the type of the next message header.

[0088] Hdr Ext Len: 8 bits, indicating the length of the IPv6 extension header.

[0089] OT: Option Type, 8 bits, OT=(BIER) means the option type is BIER.

[0090] Option Length: 8 bits, option length.

[0091] Resv: Reserved field.

[0092] TTL: 8 bits, has the same meaning as the TTL in IP packets and can be used to prevent loops.

[0093] Ver: 4 bits, version number.

[0094] BSL: 4 bits, with values ​​ranging from 1 to 7 to represent different bit string lengths.

[0095] Entropy: 20 bits, used to select a path when equal-cost paths exist.

[0096] OAM: 2 bits, the default value is 0, which can be used for OAM function.

[0097] DSCP: 7 bits, the priority level of the message itself, which determines the priority of message transmission.

[0098] Bit String: bit string.

[0099] In the related technology, the OAM field is only used for alternating coloring and cannot detect the BIER multicast service flow.

[0100] In order to solve the above technical problems, the present application provides a method for detecting a multicast service flow, which can detect a multicast service flow by using existing fields in a message header to indicate parameters for follow-up detection without adding or extending fields in the message header. Please refer to the following embodiments of the present application for details.

[0101] Reference Figure 2 , Figure 2 It is a system architecture diagram of a multicast detection domain provided in an embodiment of the present application. The system architecture of the multicast detection domain includes an analyzer 101, a multicast source 102, a head node A, a common IPv6 node B, an intermediate node C, a tail node D, a tail node E and a receiving end 103a, a receiving end 103b.

[0102] In some embodiments, the analyzer 101 may have functions such as network management, service control, and network analysis, and is a core enabling system for realizing network resource pooling, network connection automation, and operation and maintenance automation. It is mainly used for data collection and performance detection of service messages on the transmission path between nodes in the multicast detection domain, and the performance detection includes packet loss detection and delay detection. The analyzer 101 can determine the control domain, obtain the topological structure diagram of the multicast detection domain in the control domain, and determine the ingress and egress identification of the head node of the transmission path to be detected, the ingress and egress identification of the intermediate node, and the ingress and egress identification of the tail node according to the topological structure diagram.

[0103] In some embodiments, the multicast source 102 can be used to send nodes of the multicast service flow to the multicast group in the multicast detection domain. In the multicast detection domain, the multicast source only sends information once, and the nodes in the multicast detection domain use the multicast routing protocol to establish a route for the multicast service flow. The transmitted information is replicated and distributed at the fork as far as possible, and all node members in the multicast group can receive the data message of the multicast service flow. Among them, the multicast group is composed of a head node, an intermediate node, and a tail node. It should be noted that the multicast source does not necessarily belong to the multicast group. It sends data to the multicast group, but it itself is not necessarily a receiver. Multiple multicast sources can send messages to a multicast group at the same time. Figure 2 Only one multicast source is shown.

[0104] It should be noted that although Figure 2 Only one head node A, one intermediate node C and two tail nodes D and E are shown, but the nodes in the multicast group can be composed of multiple head nodes, multiple intermediate nodes and multiple tail nodes. In addition, the ordinary IPv6 node B may exist or not.

[0105] In some embodiments, head node A is the first node in the multicast detection domain that receives data packets of multicast service flows, and is used to receive data packets sent by multicast source 102, as well as to count detection information of incoming and outgoing service flows, and upload the detection information to analyzer 101.

[0106] In some embodiments, the intermediate node C is used to receive data packets sent by the head node, and to collect statistics on detection information of incoming and outgoing multicast service flows, and upload the detection information to the analyzer 101.

[0107] The tail nodes D and E are used to receive the data packets sent by the intermediate node C, collect statistics on the detection information of the incoming and outgoing service flows, and upload the detection information to the analyzer 101 .

[0108] It should be noted that the detection information counted by the above-mentioned head node, intermediate node and tail node includes the entry identifier and exit identifier of each node, the number and timestamp of data packets received and sent by each node, the multicast source address, multicast group address, multicast source port, receiving end port, and one or more of the multicast protocol number.

[0109] The receiving ends 103a and 103b are used to receive data messages sent by the tail nodes.

[0110] It should be noted that in the multicast mode, the sender of information is called the "multicast source" and the receiver of information is called the "multicast group" of the information.

[0111] It should be noted that the nodes mentioned in the embodiments of the present application are electronic devices with data transceiver functions. In the specific implementation process, the head node A, the middle node C and the tail nodes D and E can be data transfer devices, such as routers, repeaters, bridges or switches. The receiving ends 103a and 103b can be terminal devices, such as various types of user equipment (UE), mobile phones, tablet computers, desktop computers, headphones, speakers, televisions, etc.

[0112] In some embodiments, the head node A may be a BFIR; the middle node C may be a BFR; and the tail nodes D and E may be BFER.

[0113] Reference Figure 3 , Figure 3 A flow chart of a multicast service flow detection method provided in an embodiment of the present application, the multicast service flow detection method comprising:

[0114] S301. A first node receives configuration information.

[0115] Among them, the above-mentioned first node is the head node in the multicast detection domain. In the embodiment of the present application, the first node in the multicast detection domain that receives the service flow to be tested sent by the multicast source is defined as the head node.

[0116] In some embodiments of the present application, the above configuration information includes any one or more of the following items: service flow identification information, detection period, detection mode and delay detection start information corresponding to the multicast service flow.

[0117] In some embodiments, the flow detection function of the head node, intermediate node, and tail node can be pre-enabled, and the detection parameters can be pre-configured on the head node. The detection parameters include: specifying the flow characteristics of the detection message, such as configuring the detection of a certain multicast VPN traffic; specifying the detection period as 30 seconds; specifying the detection type as segment-by-segment detection; and enabling delay detection.

[0118] S302: The first node receives a multicast service flow sent by a multicast source, where the multicast service flow includes at least one data message.

[0119] S303. The first node encapsulates a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected with the flow, the first field is used to indicate the detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection.

[0120] In some embodiments, the first node may encapsulate a message header for the data message according to the received configuration information.

[0121] In some implementations, the data message may be encapsulated with a message header according to the received configuration information and in accordance with the header encapsulation format of the MSR BE message, wherein the MSR BE message is a multicast segment routing message using a best effort delivery mode.

[0122] In some implementations, the data message may be encapsulated with a message header according to the received configuration information and in accordance with the header encapsulation format of the MSR6 BE message, wherein the MSR6 BE message is an IPv6-based multicast segment routing message in a best-effort delivery mode.

[0123] In some embodiments, the multicast service flow corresponding to the above detection identifier is unique in the entire detection domain.

[0124] In some embodiments, after receiving the multicast service flow sent by the multicast source, the first node determines whether the VPN to which the multicast service flow belongs is consistent with the flow detection configuration. If consistent, the first node modifies the relevant fields in the message header of the data message in the multicast service flow.

[0125] In some embodiments, the first field may be 2 bits, which can be used to indicate four different detection periods. For example, when the first field is 00, it indicates that the detection period of the multicast service flow is 10s; when the first field is 01, it indicates that the detection period of the multicast service flow is 30s; when the first field is 10, it indicates that the detection period of the multicast service flow is 60s; when the first field is 11, it indicates that the detection period of the multicast service flow is 300s.

[0126] In some embodiments, the second field and the third field both belong to the OAM field in the message header.

[0127] The second field is the L field in the OAM field, which is used to indicate whether the data message has a packet loss detection coloring mark. For example, when the L field is 1, it indicates that the data message has a packet loss detection coloring mark, and when the L field is 0, it indicates that the data message does not have a packet loss detection coloring mark. The third field is the D field in the OAM field, which is used to indicate whether the data message has a delay detection coloring mark. For example, when the D field is 1, it indicates that delay detection is required, and when it is 0, it indicates that delay detection is not required.

[0128] In some embodiments, the first node may color the received data message according to the detection period indicated by the first field.

[0129] Reference Figure 4 , Figure 4 Schematic diagram of the coloring mark distribution of data packets in an embodiment of the present application.

[0130] exist Figure 4 In the example, the coloring is switched at the whole cycle, the coloring of the odd cycle is 1, and the coloring of the even cycle is 0.

[0131] In some embodiments, the D field in the first data message of each cycle may be marked as 1, and the D fields in the remaining data messages may be marked as 0, indicating that the first data message of each cycle requires delay detection.

[0132] In some embodiments of the present application, the above-mentioned message header also includes a fourth field, and the fourth field is used to indicate whether the above-mentioned data message performs flow detection.

[0133] After the BFIR node identifies the multicast service flow to be detected, it sets this field to 1, indicating that the multicast message is detected along with the flow. The BFR node and the BFER node determine whether to perform flow learning and detection based on this field.

[0134] In some embodiments, the above-mentioned message header also includes a fifth field, and the fifth field is used to indicate the detection mode of the above-mentioned multicast service flow.

[0135] In some embodiments, the first field, the fourth field and the fifth field are all reserved fields in the message header.

[0136] In some embodiments, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0137] Optionally, the detection identifier is carried in the source address corresponding to the data message. Exemplarily, the opcode: src.dt of the source IP address can be used as the service flow identification information flow-id corresponding to the multicast service flow; the Locator of the source IP address can be used as the node information Node-ID of the first node.

[0138] It can be understood that in the MSR BE network, each node supporting MSR has a unique locator route, so the Locator can be used to identify a unique node in the network; since the Opcode is the traffic that identifies a multicast VPN allocated under the locator of a node and is used to represent a specific detection flow in the node, the Locator+opcode can uniquely identify a detection flow in the entire network.

[0139] In order to better understand the embodiments of the present application, refer to Figure 5 , Figure 5 A schematic diagram of the format of another data message provided in an embodiment of the present application.

[0140] Among them, the first field is Figure 5 The P field shown above, the second field is Figure 5 The L field shown, the third field is Figure 5 The D field shown above, the fourth field is Figure 5 The F field shown above, the fifth field is Figure 5 In the E field shown, the detection identifier is carried in the source address Source Address corresponding to the data message.

[0141] In some embodiments, the detection modes of the multicast service flow include a segment-by-segment detection mode and an end-to-end detection mode.

[0142] Reference Figure 6 , Figure 6 A structural schematic diagram of a segment-by-segment detection mode provided in an embodiment of the present application.

[0143] Among them, the segment-by-segment detection requires that each node of BFIR, BFR, and BFER be detected.

[0144] Reference Figure 7 , Figure 7 A structural diagram of an end-to-end detection mode provided in an embodiment of the present application.

[0145] Among them, the end-to-end detection mode only performs detection at the inlet of BFIR and the outlet of BFER.

[0146] In some embodiments, when the fifth field E is 0, it indicates that the detection mode of the multicast service flow is a segment-by-segment detection mode; and when the fifth field E is 1, it indicates that the detection mode of the multicast service flow is an end-to-end detection mode.

[0147] S304: The first node sends a data message encapsulated with the above message header to the second node, where the second node is the next hop node of the first node.

[0148] S305: The second node sends a data message encapsulated with the message header to a third node, where the third node is a next-hop node of the second node.

[0149] The second node is an intermediate node in the multicast detection domain. It can be understood that there may be at least one intermediate node on the transmission path.

[0150] In some embodiments, after receiving the data message encapsulated with the message header sent by the first node, the second node may forward the received data message to the third node.

[0151] S306: The third node sends a data message to the receiving end.

[0152] In some embodiments, after receiving the data message encapsulated with the message header sent by the second node, the third node may continue to send the received data message to the receiving end.

[0153] Optionally, the number of the above-mentioned receiving ends may be one or more.

[0154] In some embodiments, the first node repeatedly colors and decolorizes the data packets in the multicast service flow in the inbound direction according to the detection period, counts the packets and records the timestamps, and reports the first detection information of the service flow to the analyzer after each period. In some embodiments, the first detection information includes the detection identifier, the ingress identifier of the first node, and the number and timestamp of the data packets received by the first node in the detection period.

[0155] In some embodiments, in addition to encapsulating a message header for a data message of a multicast service flow, the first node also needs to count the detection information of the multicast service flow according to a detection period, and the detection information includes quantity information and time information. The quantity information is the number of data messages in the multicast service flow received by the first node within the detection period. For example, the first node alternately colors the tag field of the detected flow (multicast service flow) according to the detection period, and then counts the number of colored messages in this detection period as the first quantity; the time information is the timestamp of the data message in the multicast service flow received at the time point of the detection period. For example, one of the data messages of the detected multicast service flow received at the start time point, end time point or middle time point in each detection period is delayed colored, and the entry timestamp of the data message is recorded. If the detection period is 10 seconds, the data message received at the first second within the first 10 seconds can be delayed colored, or the data message received at the 10th second within the first 10 seconds can be delayed colored.

[0156] In some implementations, during the process of the first node sending the data message encapsulated with the above message header to the second node, the first node also needs to send the second detection information of the first node to the analyzer according to the detection period.

[0157] In some embodiments, the second detection information includes the detection identifier, the egress identifier of the first node, and the number and timestamp of data packets encapsulated with the packet header sent by the first node within the detection period. Based on the first detection information and the second detection information, the analyzer can perform packet loss detection and / or delay detection on the multicast service flow.

[0158] It can be understood that after the analyzer receives the first detection information and the second detection information sent by the first node, because the received first detection information and the second detection information both contain detection identifiers, the analyzer can identify that the reported detection information is a multicast service flow carrying the same detection identifier, thereby performing packet loss detection and / or delay detection on the multicast service flow.

[0159] Among them, the packet loss detection result = {first detection information - second detection information}.

[0160] In some implementations, when the second node receives the data message encapsulated with the message header and sent by the first node, it is also necessary to send the first detection information of the second node to the analyzer according to the detection period.

[0161] The first detection information of the second node includes the detection identifier, the entry identifier of the second node, and the number and timestamp of data packets received by the second node within the detection period.

[0162] In some implementations, when the second node sends the data message encapsulated with the message header to the third node, it is also necessary to send the second detection information of the second node to the analyzer according to the detection cycle.

[0163] The second detection information of the second node includes the detection identifier, the egress identifier of the second node, and the number and timestamp of data packets encapsulated with the packet header and sent by the second node within the detection period.

[0164] In some implementations, when the third node receives the data message encapsulated with the message header sent by the second node, it is also necessary to send the first detection information of the third node to the analyzer according to the detection period.

[0165] The first detection information of the third node includes the detection identifier, the entry identifier of the third node, and the number and timestamp of data packets received by the third node within the detection period.

[0166] In some implementations, when the third node sends a data message to the receiving end, it is also necessary to send the second detection information of the third node to the analyzer according to the detection cycle.

[0167] The second detection information of the third node includes the detection identifier, the egress identifier of the third node, and the number and timestamp of data packets encapsulated with the packet header and sent by the third node within the detection period.

[0168] In some implementations, after receiving the detection information sent by each of the above nodes, the analyzer performs packet loss detection and / or delay detection on the multicast service flow.

[0169] In some embodiments, the analyzer can subscribe to detection data from the head node, the middle node, and the tail node through the Telemetry system. Among them, Telemetry is a closed-loop automated operation and maintenance system, also known as an intelligent operation and maintenance system, which consists of network devices, collectors, analyzers, controllers and other components.

[0170] In some embodiments, the analyzer can determine a detection domain, which is a detection range determined by the analyzer. In one possible implementation, a network engineer sends device information of a transmission path to be detected to the analyzer through a network management device or a user device, and the device information includes a head node device identifier and a tail node device identifier of the data path to be detected. For example, a network engineer requires detection of a transmission path between a first network device and a second network device. The network engineer sends the device identifier of the first network device and the device identifier of the second network device to the analyzer through a network management device or a user device. After receiving the device identifier of the first network device and the device identifier of the second network device, the analyzer uses the first network device as the head node device of the transmission path to be detected and the second network device as the tail node of the transmission path to be detected, thereby determining the detection domain.

[0171] In another possible implementation, the analyzer may determine the head node device of the detection domain according to the multicast source address of the data message of the multicast service flow, and determine the tail node device to be detected according to the destination address of the data message, thereby determining the detection domain.

[0172] It can be understood that each network node in the detection domain can send detection information to the analyzer, and the detection information sent by the ingress of each node in the detection domain includes the ingress identifier of each node, the detection identifier, the number of data packets in the multicast service flow received during the detection period, and the timestamp; the detection information sent by the egress of each node in the detection domain includes the egress identifier of each node, the detection identifier, the number of data packets in the multicast service flow sent during the detection period, and the timestamp.

[0173] Exemplarily, after receiving the above data message, the second node matches the traffic according to the information in the flow detection message header in the inbound direction, generates detection information according to the detection period, and reports it to the analyzer. At the same time, in the outbound direction, it is necessary to generate detection information for each interface and report it to the analyzer according to the detection period. For the third node, after receiving the above data message, it also performs message statistics in the inbound direction according to the flow detection message header, generates detection information according to the detection period, and reports it to the analyzer. At the same time, in the outbound direction, message statistics are also performed based on the interface, and the detection results are reported to the analyzer according to the detection period. Finally, the above message header is stripped off and forwarded to the receiving device.

[0174] The multicast service flow detection method provided in the embodiment of the present application can detect the multicast service flow by using the existing fields in the message header to indicate the parameters of the flow detection, without adding or extending the fields in the message header.

[0175] Based on the contents described in the above embodiments, Figure 8 , Figure 8A program module diagram of a multicast service flow detection device provided in an embodiment of the present application Figure 1 , applied to the first node. In the embodiment of the present application, the multicast service flow detection device 80 includes:

[0176] The receiving module 801 is configured to receive a multicast service flow sent by a multicast source, wherein the multicast service flow includes at least one data message.

[0177] The encapsulation module 802 is used to encapsulate a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate the detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection.

[0178] The sending module 803 is used to send the data message encapsulated with the message header to the second node, where the second node is the next hop node of the first node.

[0179] In some implementations, the second field and the third field belong to an OAM field in the packet header.

[0180] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0181] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0182] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0183] In some implementations, the sending module 803 is further configured to:

[0184] The first detection information and the second detection information of the first node are sent to the analyzer; the first detection information includes the detection identifier, the entry identifier of the first node, and the number and timestamp of the data packets received by the first node within the detection period; the second detection information includes the detection identifier, the exit identifier of the first node, and the number and timestamp of the data packets encapsulated with the packet header sent by the first node within the detection period; so that the analyzer can perform packet loss detection and / or delay detection on the multicast service flow according to the first detection information and the second detection information.

[0185] It can be understood that the implementation principle and method of the above-mentioned multicast service flow detection device 80 are the same as the implementation principle and method of the multicast service flow detection method described in the above-mentioned embodiments. Therefore, reference can be made to the description of each embodiment of the above-mentioned multicast service flow detection method, and no further details will be given here.

[0186] Based on the contents described in the above embodiments, Fig. 9 , Fig. 9 A program module diagram of a multicast service flow detection device provided in an embodiment of the present application Figure 2 , applied to the second node. In the embodiment of the present application, the multicast service flow detection device 90 includes:

[0187] The receiving module 901 is used to receive a data message encapsulated with a message header and sent by a first node; the first node is the previous hop node of the second node, and the message header includes a detection identifier, a first field, a second field and a third field. The detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate the detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection.

[0188] The sending module 902 is used to send the data message encapsulated with the message header to a third node, and the third node is the next hop node of the second node.

[0189] In some implementations, the second field and the third field belong to an OAM field in the packet header.

[0190] In some implementations, the message header further includes a fourth field, and the fourth field is used to indicate whether the data message performs in-stream detection.

[0191] In some implementations, the message header further includes a fifth field, and the fifth field is used to indicate a detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

[0192] In some implementations, the detection identifier includes service flow identification information corresponding to the multicast service flow and node information of the first node.

[0193] In some implementations, the sending module 902 is further configured to:

[0194] The first detection information and the second detection information of the second node are sent to the analyzer; the first detection information includes the detection identifier, the entry identifier of the second node, and the number and timestamp of the data packets received by the second node within the detection period; the second detection information includes the detection identifier, the exit identifier of the second node, and the number and timestamp of the data packets encapsulated with the packet header sent by the second node within the detection period; so that the analyzer can perform packet loss detection and / or delay detection on the multicast service flow according to the first detection information and the second detection information.

[0195] It can be understood that the implementation principle and method of the above-mentioned multicast service flow detection device 90 are the same as the implementation principle and method of the multicast service flow detection method described in the above-mentioned embodiments. Therefore, reference can be made to the description of each embodiment of the above-mentioned multicast service flow detection method, and no further details will be given here.

[0196] Furthermore, based on the contents described in the above embodiments, a communication device is also provided in an embodiment of the present application, including a processor and an interface circuit, wherein the processor is communicatively connected to the interface circuit.

[0197] In some implementations, the interface circuit is used to communicate with other communication devices; the processor is used to implement the contents described in each embodiment of the above multicast service flow detection method.

[0198] In order to better understand the embodiments of the present application, refer to Fig.10 , Fig.10 A schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application.

[0199] like Fig.10 As shown, the communication device 100 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are connected in communication. It is understood that the interface circuit 1020 can be a transceiver or an input-output interface. Optionally, the communication device 100 may also include a memory 1030 for storing instructions executed by the processor 1010 or storing input data required by the processor 1010 to execute instructions or storing data generated after the processor 1010 executes instructions.

[0200] An embodiment of the present application provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, each step of the multicast service flow detection method described in the above embodiment is implemented. For details, please refer to the relevant description in the above method embodiment.

[0201] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0202] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0203] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0204] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in the present application may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0205] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for detecting a multicast service flow, characterized in that: Applied to the first node, the method comprises: receiving a multicast service flow sent by a multicast source, wherein the multicast service flow includes at least one data message; Encapsulating a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate the detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection; A data message encapsulated with the message header is sent to a second node, where the second node is a next-hop node of the first node.

2. The method according to claim 1, characterized in that The second field and the third field belong to an Operation, Maintenance and Management (OAM) field in the message header.

3. The method according to claim 1, characterized in that The message header further includes a fourth field, and the fourth field is used to indicate whether the data message is subjected to flow detection.

4. The method according to claim 1, characterized in that: The message header also includes a fifth field, and the fifth field is used to indicate the detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

5. The method according to claim 1, characterized in that: The detection identifier includes service flow identifier information corresponding to the multicast service flow and node information of the first node.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Sending first detection information and second detection information of the first node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the first node, and the number and timestamp of the data packets received by the first node within the detection period; the second detection information includes the detection identifier, the exit identifier of the first node, and the number and timestamp of the data packets encapsulated with the message header sent by the first node within the detection period; This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow according to the first detection information and the second detection information.

7. A multicast service flow detection method, characterized in that: Applied to the second node, the method comprises: Receive a data message encapsulated with a message header and sent by a first node; the first node is a previous hop node of the second node, the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected with the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection; A data message encapsulated with the message header is sent to a third node, where the third node is a next-hop node of the second node.

8. The method according to claim 7, characterized in that The second field and the third field belong to an Operation, Maintenance and Management (OAM) field in the message header.

9. The method according to claim 7, characterized in that: The message header further includes a fourth field, and the fourth field is used to indicate whether the data message is subjected to flow detection.

10. The method according to claim 7, characterized in that The message header also includes a fifth field, and the fifth field is used to indicate the detection mode of the multicast service flow; the detection mode includes a segment-by-segment detection mode and an end-to-end detection mode.

11. The method according to claim 7, characterized in that The detection identifier includes service flow identifier information corresponding to the multicast service flow and node information of the first node.

12. The method according to any one of claims 7 to 11, characterized in that The method further comprises: Sending first detection information and second detection information of the second node to the analyzer; the first detection information includes the detection identifier, the entry identifier of the second node, and the number and timestamp of the data packets received by the second node within the detection period; the second detection information includes the detection identifier, the exit identifier of the second node, and the number and timestamp of the data packets encapsulated with the message header sent by the second node within the detection period; This allows the analyzer to perform packet loss detection and / or delay detection on the multicast service flow based on the first detection information and the second detection information.

13. A multicast service flow detection device, characterized in that: Applied to a first node, the device comprises: A receiving module, configured to receive a multicast service flow sent by a multicast source, wherein the multicast service flow includes at least one data message; An encapsulation module, configured to encapsulate a message header for the data message; wherein the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected by the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection; The sending module is used to send the data message encapsulated with the message header to the second node, and the second node is the next hop node of the first node.

14. A multicast service flow detection device, characterized in that: Applied to a second node, the device comprises: A receiving module, configured to receive a data message encapsulated with a message header and sent by a first node; the first node is a previous hop node of the second node, the message header includes a detection identifier, a first field, a second field, and a third field, the detection identifier is used to identify the multicast service flow as a multicast service flow detected with the flow, the first field is used to indicate a detection period of the multicast service flow, the second field is used to indicate whether the data message has a packet loss detection coloring mark, and the third field is used to indicate whether the data message participates in delay detection; The sending module is used to send the data message encapsulated with the message header to a third node, and the third node is the next hop node of the second node.

15. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the processor is communicatively connected with the interface circuit; The interface circuit is used to communicate with other communication devices; The processor is used to implement the multicast service flow detection method as described in any one of claims 1 to 6, or to implement the multicast service flow detection method as described in any one of claims 7 to 12.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions. When the processor executes the computer-executable instructions, the multicast service flow detection method as described in any one of claims 1 to 6 is implemented, or the multicast service flow detection method as described in any one of claims 7 to 12 is implemented.

Images