A method for implementing in-band network telemetry in an SRv6 network

By integrating the INT protocol into the SRv6 network and defining the End.INT and End.INT.SINK instructions, telemetry is performed only at critical nodes, solving the problems of device burden and header overhead in existing technologies and realizing flexible and lightweight network telemetry.

CN117880166BActive Publication Date: 2026-11-10XIAMEN UNIV
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202410090220.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-01-22
Publication Date
2026-11-10
Estimated Expiration
2044-01-22

AI Technical Summary

Technical Problem

Existing SRv6 network telemetry methods have problems with network device processing burden and header overhead, and cannot flexibly select key nodes for on-demand measurement.

Method used

The INT protocol is integrated into the SRv6 framework, defining the End.INT and End.INT.SINK instructions. Telemetry is performed only at critical nodes, and telemetry metadata is stored in the SRH tail, reducing header overhead and device burden.

Benefits of technology

It enables on-demand, refined in-band network telemetry, reducing the processing burden on network devices and header transmission overhead, and improving the flexibility and efficiency of network measurement.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117880166B_ABST
    Figure CN117880166B_ABST
Patent Text Reader

Abstract

The application discloses an implementation method of inband network telemetry in SRv6 (Segment Routing IPv6) network, comprising the following steps: defining SRv6 end node instruction End.INT and End.INT.SINK, and realizing INT function through SRv6 network programming; using SRv6 middle segment list to specify INT telemetry path, covering key network nodes; when the SID (Segment ID) carries End.INT and End.INT.SINK instructions, storing the metadata information of telemetry directly in segment routing extension packet header. The application is different from the existing INT+SRv6 combination scheme, and no longer sets INT as an independent header, but uses End.INT and End.INT.SINK instructions in the SID of the key node to realize inband network telemetry, reduces the header overhead, and further reduces the network equipment burden and shortens the delay; the network manager can not only specify the telemetry path, but also flexibly realize on-demand telemetry (instead of all nodes along the way), can reduce the telemetry metadata in the header, and further reduces the header overhead; fully utilizes the capability of SRv6 network programming, and realizes the functionalization, refinement and light weight of INT.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of network communication technology, and specifically to an in-band network telemetry implementation method in an SRv6 network. Background Technology

[0002] Source routing pushes routing decisions from the network core to the SDN (Software-Defined Networking) controller or source node at the network edge. By setting the complete forwarding path in the packet header, packets reach their destination via a specified series of nodes, without intermediate nodes needing to perform hop-by-hop routing. Segment routing (SR), evolved from source routing, treats each node in the network as a segment and assigns it a segment ID (SID), while the entire forwarding path is treated as a segment list. SR encodes the segment list representing the forwarding path in the packet header, which is transmitted with the packet; network nodes parse the segment list to determine the next hop and complete forwarding and related data processing. SR can be implemented through different data forwarding planes; those based on MPLS are called SR-MPLS, and those based on IPv6 are called SRv6. Compared to SR-MPLS, SRv6 has network compatibility and programmability, and is considered a next-generation core protocol for IP networks, thus attracting more attention. SRv6 has the following characteristics:

[0003] (1) SRv6 does not change the original encapsulation structure of IPv6 packets, but uses the IPv6 extension header SRH (Segment Routing Header) to implement segment routing. This allows SRv6 devices to be deployed together with ordinary IPv6 devices, is compatible with the existing network, and can support rapid service launch and smooth evolution.

[0004] (2) SRv6 possesses powerful programmability, providing a three-layer programmable space. First, SRv6 SIDs can be freely combined for path orchestration: the controller responds and defines forwarding paths according to service requirements. Second, the Function and Arguments fields in the SID can be customized for service functions. Third, the SRH also has an optional TLV (Type Length Value) field, which can further customize service functions. This enables SRv6 to meet the needs of various services, aligns with advanced SDN concepts, and conforms to the development trend of service-driven networks.

[0005] In summary, SRv6 combines the advantages of source routing and the simplicity and extensibility of IPv6. Its flexible programming capabilities allow for the rapid implementation of other network protocols and services, making it a powerful tool for building "intelligent and simplified IP" and ushering in a new era of IPv6+. The development of IPv6+ is inseparable from network management and performance optimization, with network measurement playing a crucial role. Traditional network measurement often relies on end-to-end packet loss and latency detection, treating intermediate network devices as "black boxes." In-band network telemetry (INT), by embedding telemetry commands in the packet header, obtains real-time status information of each network device (such as queue length and processing latency), providing a more comprehensive and detailed observation of network performance, which is beneficial for detecting and handling network anomalies and faults. However, INT lacks controllability and flexibility; it inserts telemetry metadata of traversed nodes hop-by-hop into the data packet, meaning that changes in routing alter the telemetry path, let alone performing measurements on specific network nodes.

[0006] A solution combining INT and SRv6 has emerged: SRv6 orchestrates a segment list as the telemetry path using SR Policy, and the SID carried matches the regular End command; all nodes on the path use INT to obtain telemetry metadata and record it in the packet header. For example, SONM-SR-INT. [1][2] SFANT [3] and SRv6-based INT [4] Directly superimposing SRv6 and INT headers and inserting independently functioning SRH and INT headers into the data packet is a simple and easy method, but it increases the processing burden on network devices and significantly increases the packet length. SRv6-INT [5] and invention patents [6] A replacement scheme is then adopted, replacing the SIDs of network nodes in the SRH segment list with relevant telemetry metadata. This method does not incur additional header overhead, but is limited by the 16-byte segment length, only storing the specified node status information, thus limiting INT telemetry capabilities and losing the original SRH segment information. Furthermore, actual network measurements do not necessarily require attention to all nodes; often only information from certain key nodes is necessary. Existing solutions acquire and record telemetry metadata for all nodes, failing to flexibly select key nodes for on-demand measurement, and increasing the processing burden and header overhead on network devices. Therefore, a more efficient, refined, and lightweight solution is needed.

[0007] [1]Liu J, Shi X, Huang Y, et al. Selective and on-demand network measurement with SRv6and INT[J]. Computer Networks, 2023, 234:109914.

[0008] [2] Liu Jiayi, Shi Xiangjie, Network Measurement Method and Device Based on SRv6 and INT, Chinese Patent Application No.: CN202211374811.9, Publication Date: March 2023

[0009] [3]Liu Y, Xia Y, Zhang W, et al. SFANT: A SRv6-based Flexible and ActiveNetwork Telemetry Scheme in Programming Data Plane[J]. IEEE Transactions on Network Science and Engineering, 2023.

[0010] [4] Yu K, Li S. SRv6-based In-band Network Telemetry: Architecture and Strategy [C], Proceedings of 2023International Conference on Networking and Network Applications, 2023, pp.226-230.

[0011] [5]Yan

[0012] [6] Cheng Guang, Zhao Yuyu et al., A network telemetry method based on SRv6, Chinese Patent, Patent No.: CN114050994B, Publication Date: 2023.07, Authorized. Summary of the Invention

[0013] This invention provides an in-band network telemetry implementation method in SRv6 networks (INT over SRv6, INToSR). It integrates the INT protocol into the SRv6 framework in a programmable form, eliminating the need for INT as a separate header. Instead, INT is treated as a new SRv6 function. In-band network telemetry is performed using the End.INT and End.INT.SINK instructions on the SID of critical nodes, reducing header overhead and thus alleviating the burden on network devices and shortening latency. Network administrators can not only specify telemetry paths but also flexibly implement on-demand telemetry (rather than telemetry across all nodes along the path), reducing telemetry metadata in the header and further reducing header overhead.

[0014] The present invention adopts the following technical solution:

[0015] A method for implementing in-band network telemetry in an SRv6 network includes:

[0016] Steps for arranging a segment list:

[0017] Define forwarding paths according to business requirements, and arrange segment lists by combining multiple segment identifiers (SIDs) through SRv6 network programming.

[0018] Instruction and field definition steps:

[0019] Define the SRv6 end-node commands End.INT and End.INT.SINK for instructing network telemetry; place the standard SRv6 end-node commands and the newly defined End.INT or End.INT.SINK commands in the Function field of SID; place the telemetry commands corresponding to the End.INT or End.INT.SINK commands in the Arguments field of SID; place the node telemetry metadata information at the end of SRH to perform INT telemetry on specified network critical nodes;

[0020] Data packet forwarding steps:

[0021] Based on the orchestration list, the source node generates SRv6 data packets and sends them to the next-hop network node;

[0022] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT instruction, the corresponding telemetry metadata is inserted into the SRH tail according to the telemetry command in the Arguments field of the End.INT instruction, the next-hop SID information is updated, and then it is forwarded;

[0023] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT.SINK instruction, a mirror packet of the current data packet is first generated. Then, according to the telemetry commands in the Arguments field of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted into the SRH tail, and an INT telemetry report is generated and sent to the monitoring system. For the current data packet, the telemetry information appended to the SRH tail is removed, and then it is determined whether it is the last hop in the SRH. If not, the next hop SID information is updated and forwarded. If it is, the data packet is received and the next header of the SRH is processed.

[0024] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet does not match the End.INT or End.INT.SINK instruction, then the packet is processed according to the standard instructions of the SRv6 end node.

[0025] If the network node to which the data packet arrives is a relay node, the packet will be processed in accordance with the IPv6 standard protocol.

[0026] Preferably, the newly defined SRv6 end-node instruction End.INT has the following specific processing behaviors:

[0027] Based on the telemetry commands in the Arguments field of the End.INT instruction, the corresponding telemetry metadata is inserted into the SRH tail. The Segments Left field in the SRH header is decremented by 1, the Hop Limit field in the IPv6 header is decremented by 1, the next-hop node SID information is updated to the IPv6 destination address field, and the Hdr Ext Len field in the SRH header and the PayloadLength field in the IPv6 header are modified. Then, the next-hop forwarding interface is determined by looking up a table in the packet.

[0028] Preferably, the newly defined SRv6 end-node instruction End.INT.SINK has the following specific processing behaviors:

[0029] First, a mirror image of the current data packet is generated. Then, according to the telemetry commands in the Arguments field of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted into the SRH tail, and an INT telemetry report is generated and sent to the monitoring system. For the current data packet, the telemetry information appended to the SRH tail is removed, and it is determined whether it is the last hop in the SRH. If it is not the last hop, the Segments Left field in the SRH header is decremented by 1, the Hop Limit field in the IPv6 header is decremented by 1, the next-hop node SID information is updated to the IPv6 destination address field, and the Hdr Ext Len field in the SRH header and the Payload Length field in the IPv6 header are modified. Then, the packet is looked up to determine the next-hop forwarding interface. If it is the last hop, the packet is received, and the next header of the SRH in the data packet is processed.

[0030] Preferably, the Arguments field in the SID occupies 16 bits; telemetry instructions are expressed in bitmap form, and setting the current bit to 1 indicates that telemetry is performed on the metadata item.

[0031] Preferably, the corresponding telemetry metadata is inserted to the end of the SRH, specifically including:

[0032] Insert the corresponding telemetry metadata into the TLV field at the end of the SRH.

[0033] The beneficial effects of this invention are as follows:

[0034] (1) Compared with existing methods that simply overlay or replace the INT header, the method of implementing in-band network telemetry in SRv6 network (INToSR) of the present invention is a more refined integration method. Within the SRv6 framework, two new endpoint instructions End.INT and End.INT.SINK are defined, and the INT telemetry command is stored in the Arguments field of the SRv6 endpoint instruction. The key nodes of the measurement directly store the INT metadata information in the SRv6 segment routing extension header SRH. Therefore, INToSR only needs to process one SRv6 header, which simplifies the processing flow of network devices, reduces the burden on devices, and reduces processing latency and header transmission overhead.

[0035] (2) The INToSR of the present invention fully utilizes the network programming capabilities of SRv6 and uses the SID sequence in SRv6 and the INT telemetry command carried by the SID to perform on-demand measurement of key network nodes on the telemetry path, thereby realizing fine-grained in-band network telemetry. Since the data packets only obtain telemetry data at key nodes rather than all nodes, the burden on the device is further reduced. The embedded telemetry metadata is reduced, and the transmission overhead is also reduced accordingly. While meeting business needs, network administrators can achieve fine-grained and lightweight in-band telemetry for key nodes and paths in the network.

[0036] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments, but the method for implementing in-band network telemetry in an SRv6 network according to the present invention is not limited to the embodiments. Attached Figure Description

[0037] Figure 1 This is a flowchart of the network telemetry implementation method in an SRv6 network according to an embodiment of the present invention;

[0038] Figure 2 This is a format diagram of the SRH according to an embodiment of the present invention;

[0039] Figure 3 This is a diagram of the SRv6 SID format according to an embodiment of the present invention;

[0040] Figure 4 This is a schematic diagram of a standard INT message in existing technology;

[0041] Figure 5 This is a schematic diagram of the data packet forwarding process according to an embodiment of the present invention. Detailed Implementation

[0042] The present invention will be further described below through specific embodiments. It should be noted that the specific embodiments described herein are only for the convenience of illustrating and explaining the specific implementation of the present invention, and are not intended to limit the present invention.

[0043] To make the objectives and technical solutions of this invention clearer, the invention will be further described below with reference to the accompanying drawings and examples. It should be understood that the examples described herein are for illustrative purposes only and are not intended to limit the invention.

[0044] First, the four types of network nodes (switches) used in the embodiments of the present invention will be described.

[0045] 1) SRv6 source node: The source node that generates SRv6 messages.

[0046] 2) Relay node: A regular IPv6 node that forwards SRv6 packets but does not perform SRv6 processing.

[0047] 3) Ordinary SRv6 end node: The node that receives and processes SRv6 packets, where the IPv6 destination address of the packet is the locally configured SID, such as End, End.X, End.T, etc.

[0048] 4) SRv6 end nodes that support INToSR: Nodes that receive and process SRv6 packets whose IPv6 destination address is the locally configured SID. They can handle not only the standard End command, but also the End.INT and End.INT.SINK commands.

[0049] See Figure 1 As shown, a method for implementing in-band network telemetry in an SRv6 network includes:

[0050] Segment list arrangement step 10:

[0051] Define forwarding paths according to business requirements, and arrange segment lists by combining multiple segment identifiers (SIDs) through SRv6 network programming.

[0052] Instruction and field definition step 20:

[0053] Define the SRv6 end-node commands End.INT and End.INT.SINK for instructing network telemetry; place the standard SRv6 end-node commands and the newly defined End.INT or End.INT.SINK commands in the Function field of SID; place the telemetry commands corresponding to the End.INT or End.INT.SINK commands in the Arguments field of SID; place the node telemetry metadata information at the end of SRH to perform INT telemetry on specified network critical nodes;

[0054] Packet forwarding step 30:

[0055] Based on the orchestration list, the source node generates SRv6 data packets and sends them to the next-hop network node;

[0056] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT instruction, the corresponding telemetry metadata is inserted into the SRH tail according to the telemetry command in the Arguments field of the End.INT instruction, the next-hop SID information is updated, and then it is forwarded;

[0057] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT.SINK instruction, a mirror packet of the current data packet is first generated. Then, according to the telemetry commands in the Arguments field of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted into the SRH tail, and an INT telemetry report is generated and sent to the monitoring system. For the current data packet, the telemetry information appended to the SRH tail is removed, and then it is determined whether it is the last hop in the SRH. If not, the next hop SID information is updated and forwarded. If it is, the data packet is received and the next header of the SRH is processed.

[0058] If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet does not match the End.INT or End.INT.SINK instruction, then the packet is processed according to the standard instructions of the SRv6 end node.

[0059] If the network node to which the data packet arrives is a relay node, the packet will be processed in accordance with the IPv6 standard protocol.

[0060] In this embodiment, firstly, the SDN controller, based on the collected network node topology information, service requirements, key nodes to be measured, and a combination of required measurement metrics (such as switch ID, interface ID of data packets entering and exiting the switch, timestamps of data packets entering and exiting the switch, processing latency of data packets within the switch, and buffer queue length when data packets enter the switch), uses an SRv6 orchestration segment list to specify the telemetry path. Then, using the 128-bit space in the SRv6 SID, it designs End.INT and End.INT.SINK instructions with INT functionality and inserts a Segment Routing Header (SRH) carrying INT functionality into the data packet header. Finally, it performs fine-grained on-demand measurements on key network nodes and paths and directly stores the INT telemetry metadata at the end of the SRH. The format of the SRH in this embodiment is described in [reference needed]. Figure 2 As shown.

[0061] The specific processing steps are as follows.

[0062] (1) Segment list arrangement. The SDN controller defines forwarding paths according to service requirements, and arranges multiple segment identifiers (SIDs) into a segment list to achieve path programmability. Then, the standard instructions of SRv6 end nodes, the newly designed End.INT and End.INT.SINK instructions are combined and programmed to perform INT telemetry only on specified network critical nodes and paths, realizing lightweight on-demand telemetry.

[0063] (2) Design End instructions End.INT and End.INT.SINK with INT functionality using the SID space. An SRv6 SID is a 128-bit value in IPv6 address form, composed of three parts: Locator, Function, and Arguments, which can be used to define network instructions. See also Figure 3 As shown, the Locator provides routing and forwarding location functionality, used to identify a network node; the Function describes the forwarding behavior to be executed by the node's instruction, indicating which SRv6 end-node instruction to match; the optional Arguments field supplements the Function, such as parameters corresponding to the instruction execution, including flow, service, or other related information. The function and length of each field in the SID can be defined by the user, thus providing flexible programming capabilities and enabling programmable business logic.

[0064] In the existing standard INT protocol, the INT source node inserts an INT header containing INT telemetry commands and corresponding telemetry information into the received data packet. The INT transit node, upon receiving the data packet, embeds corresponding telemetry information based on the INT telemetry commands within it. The INT sink node first inserts telemetry information into the received data packet, then extracts the INT header and INT metadata from the data packet, generates a telemetry report, and forwards it to the monitoring system. The INToSR method proposed in this embodiment fully leverages the programming capabilities of SRv6 networks, implementing the business functions of these INT nodes within the SRv6 network framework.

[0065] First, two new SRv6 end-node instructions are defined: End.INT and End.INT.SINK. The INT telemetry command is placed in the Arguments field of the SRv6 SID, occupying 16 bits. The INT telemetry command uses a bitmap format, meaning that if the current bit is set to 1, telemetry is performed on this metadata item. Currently, only the first 7 bits are used (this can be expanded later). The items and lengths of the telemetry metadata in the telemetry command from high to low bits are shown in Table 1. For example, if the telemetry command 0xAC (binary 10101100) matches bits 1, 3, 5, and 6 of the bitmap, the telemetry metadata includes: the node switch device ID, the packet processing delay inside the switch, the timestamp of the packet entering the switch, and the timestamp of the packet leaving the switch.

[0066] Table 1. Items of telemetry metadata

[0067] bitmap Fields Length (bit) 1st place Switch Device ID 32 2nd place The interface ID of the data packet entering the switch and the interface ID of the data packet leaving the switch. 32 3rd place Data packet processing delay within the switch 32 4th place Buffer queue ID and length when data packets enter the switch 32 5th place timestamp of data packet entering the switch 64 6th place The timestamp of the data packet leaving the switch 64 7th place Switch port utilization 32

[0068] Then, during packet forwarding, after receiving the packet, the network node uses the longest prefix to match the IPv6 destination address and finds that it is the locally configured SID. It then determines which SRv6 end node instruction to execute based on the bits of the Function field, such as End, End.INT, and End.INT.SINK.

[0069] The two new instructions are defined as follows.

[0070] 1) End.INT instruction (applicable to INT Source nodes and INT Transit nodes):

[0071] When an SRv6 end node receives a data packet and performs an End.INT instruction to match the IPv6 destination address to the current node, it inserts the current node's telemetry metadata information into the SRH tail based on the telemetry commands carried in the Arguments field of the SID. Then, it decrements the Segments Left field in the SRH header by 1, decrements the Hop Limit field in the IPv6 header by 1, updates the next-hop node SID information to the IPv6 destination address field, modifies the Hdr Ext Len field in the SRH header and the Payload Length field in the IPv6 header, and finally performs a table lookup to determine the next-hop forwarding interface. For a detailed implementation of the End.INT instruction, please refer to Algorithm 1 below.

[0072] 2) End.INT.SINK instruction (applicable to INT SINK nodes):

[0073] When an SRv6 end node receives a data packet, it performs an IPv6 destination address match to the current node's End.INT.SINK instruction. First, it generates a mirror image of the current packet in the switch. In this mirror image, based on the telemetry commands carried in the Arguments field of the SID, it inserts the current node's telemetry metadata information into the SRH appendix. Then, it generates an INT telemetry report and sends it to the monitoring system. For the current data packet, it removes the telemetry information appended to the SRH appendix and determines if it is the last hop in the SRH. If it is not the last hop, it decrements the Segments Left field in the SRH header by 1, decrements the Hop Limit field in the IPv6 header by 1, updates the next-hop node SID information to the IPv6 destination address field, and modifies the HdrExt Len field in the SRH header and the Payload Length field in the IPv6 header. Then, it looks up the packet to determine the next-hop forwarding interface. If it is the last hop, it receives the packet and processes the next header of the SRH in the data packet. For a detailed implementation of the End.INT.SINK instruction, please refer to Algorithm 2 below.

[0074] It should be noted that End.INT.SINK can be the last instruction in the SR policy, or it may not be the last instruction. That is, the SR policy may contain other instructions, depending on the value of SL in the SRH. Important fields in IPv6 and SRH are shown in Table 2 below.

[0075] Table 2. Key Fields in IPv6 and SRH

[0076]

[0077] Algorithm 1: Pseudocode for the End.INT instruction

[0078]

[0079]

[0080] Algorithm 2: Pseudocode for the End.INT.SINK instruction

[0081]

[0082]

[0083] (3) Design of the SRH tail. The optional TLV (Type-Length-Value) field after the segment list can be used for further customized functions. When the data packet is transmitted in the network, some telemetry metadata can be encapsulated in the data forwarding plane and accomplished through the flexible combination of TLV in the SRH, realizing application programmability. Unlike the existing scheme that inserts two separate headers, SRH and INT, into the data packet, this patent abandons the separate INT header and uses the fields in the INT header (see Figure 4 (As shown) is integrated into the SRH header (see...) Figure 2 (As shown in Table 3). This simplifies the processing flow of network devices, reduces the processing burden and latency of devices, and also reduces the overhead of header transmission. The SRH fields related to the INT function in the INToSR method are shown in Table 3.

[0084] Table 3. SRH fields related to the INT function in the INToSR method.

[0085]

[0086] Specifically, this includes the following processing.

[0087] a) RemainingHop Cnt is represented by SRH's Segments Left.

[0088] b) The Instruction Bitmap is represented by the Arguments in the SRv6 end-node instructions End.INT and End.INT.SINK, and longer Instruction Bitmaps can be supported by dynamically adjusting the length of the Arguments, thereby collecting more data.

[0089] c) The Instruction Bitmap already contains the Hop ML information, so the Hop ML field can be omitted.

[0090] d) Other less frequently used fields can be added directly to the end of the Arguments section in the End.INT and End.INT.SINK directives if needed.

[0091] e) Store the INT telemetry information directly in the SRH tail of the segment routing extension header.

[0092] Next, we will illustrate this with a network example using INToSR.

[0093] See Figure 5 As shown, the SDN controller intelligently orchestrates SRHs with in-band network telemetry (INT) functionality based on collected topology information and network management requirements. For example, a current service requires monitoring the performance status of critical network nodes R3, R6, R7, R8, and R9 (these five nodes may experience high load). First, a source routing policy (SRpolicy) is formulated to forward data packets sent by host 1 to host 2 via R2→R3→R4→R6→R7→R8→R9→R10. The SDN controller leverages the SRv6 network programming capabilities, using the INT telemetry parameters carried by the SIDs, to intelligently orchestrate telemetry paths containing the critical network nodes, and issues an SRH containing the SID sequence of R3, R4, R6, R7, R8, R9, R10, and host 2 at the SRv6 source node R1. Therefore, when orchestrating SRHs, R3, R6, R7, and R8 use the SID of End.INT, and R9 uses the SID of End.INT.SINK. These five nodes directly store the metadata information of INT telemetry in the header and footer of the SRH.

[0094] The complete forwarding process of a data packet in the case network is as follows.

[0095] 1) Insert SRH at R1, where the SID information includes: R3 (End.INT), R4 (End), R6 (End.INT), R7 (End.INT), R8 (End.INT), R9 (End.INT.SINK), R10 (End) and host 2 (IPv6 address).

[0096] 2) The relay node R2 does not perform SRv6 processing, but will forward the data packets by looking up the routing table.

[0097] 3) When the IPv6 destination address at R3 matches the End.INT instruction of the current node, the corresponding telemetry metadata will be inserted according to the telemetry parameters in Arguments of the End.INT instruction, the next-hop SID information will be updated, and then the message will be forwarded.

[0098] 4) At R4, the IPv6 destination address matches the End instruction of the current node. Since it is not a node that needs to be measured by INT, the next-hop SID information is updated directly and forwarded.

[0099] 5) The IPv6 destination address at R6, R7 and R8 all match the End.INT instruction of the current node. Therefore, the corresponding telemetry metadata will be inserted according to the telemetry parameters of Arguments in the End.INT instruction, the next-hop SID information will be updated, and then forwarded.

[0100] 6) When the IPv6 destination address at R9 matches the current node's End.INT.SINK instruction, a mirror image of the original packet is first generated here. Then, based on the telemetry parameters in the Arguments section of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted, and an INT telemetry report is generated and sent to the monitoring system. For the original packet, the telemetry information appended to the SRH tail is removed, and then it is forwarded.

[0101] 7) At R10, the IPv6 destination address matches the current node's End instruction, so no INT measurement is needed. Therefore, the next-hop SID information is updated. At this point, the current node is the second-to-last hop in the segment list. The SRH header in the packet is popped, and then the data packet is forwarded to its destination, i.e., host 2.

[0102] This case fully demonstrates the advantages of the INToSR method: (1) It only needs to process the SRv6 header, which simplifies the processing flow of network devices and effectively reduces the processing burden and processing latency of devices; (2) It gives full play to the capabilities of SRv6 network programming, giving in-band network telemetry lightweight and refined features. Not only can telemetry paths be specified, but telemetry information can also be flexibly selected to be collected at key nodes according to application service requirements; (3) It has good network compatibility and can achieve transparent transmission in network environments that include ordinary IPv6 nodes, ordinary SRv6 nodes and INToSR-supporting nodes.

[0103] It should be understood that those skilled in the art can make improvements and modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A method for implementing in-band network telemetry in an SRv6 network, characterized in that, include: Steps for arranging a segment list: Define forwarding paths according to business requirements, and arrange segment lists by combining multiple segment identifiers (SIDs) through SRv6 network programming. Instruction and field definition steps: Define the SRv6 end-node commands End.INT and End.INT.SINK for instructing network telemetry; place the standard SRv6 end-node commands, the newly defined End.INT or End.INT.SINK commands in the Function field of SID; place the telemetry commands corresponding to the End.INT or End.INT.SINK commands in the Arguments field of SID; place the node telemetry metadata information at the end of the SRH to perform INT telemetry on specified network critical nodes; Data packet forwarding steps: Based on the orchestration list, the source node generates SRv6 data packets and sends them to the next-hop network node; If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT instruction, the corresponding telemetry metadata is inserted into the SRH tail according to the telemetry command in the Arguments field of the End.INT instruction, the next-hop SID information is updated, and then it is forwarded; If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet matches the End.INT.SINK instruction, a mirror packet of the current data packet is first generated. Then, according to the telemetry commands in the Arguments field of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted into the SRH tail, and an INT telemetry report is generated and sent to the monitoring system. For the current data packet, the telemetry information appended to the SRH tail is removed, and then it is determined whether it is the last hop in the SRH. If not, the next hop SID information is updated and the packet is forwarded. If so, receive the data packet and process the next header of the SRH; If the network node to which the data packet arrives is an SRv6 end node, and the IPv6 destination address of the data packet does not match the End.INT or End.INT.SINK instruction, then the packet is processed according to the standard instructions of the SRv6 end node. If the network node to which the data packet arrives is a relay node, the packet will be processed in accordance with the IPv6 standard protocol.

2. The in-band network telemetry implementation method in an SRv6 network according to claim 1, characterized in that, The newly defined SRv6 end-node instruction End.INT has the following specific processing behaviors: Based on the telemetry commands in the Arguments field of the End.INT instruction, insert the corresponding telemetry metadata to the tail of the SRH, decrement the Segments Left field in the SRH header by 1, decrement the Hop Limit field in the IPv6 header by 1, update the next-hop node SID information to the IPv6 destination address field, modify the Hdr Ext Len field in the SRH header and the Payload Length field in the IPv6 header, and then look up the table to determine the next-hop forwarding interface for the packet.

3. The in-band network telemetry implementation method in an SRv6 network according to claim 1, characterized in that, The newly defined SRv6 end-node instruction End.INT.SINK has the following specific processing behaviors: First, a mirror image of the current data packet is generated. Then, according to the telemetry commands in the Arguments field of the End.INT.SINK instruction, the corresponding telemetry metadata is inserted into the SRH tail, and an INT telemetry report is generated and sent to the monitoring system. For the current data packet, the telemetry information appended to the SRH tail is removed, and it is determined whether it is the last hop in the SRH. If it is not the last hop, the Segments Left field in the SRH header is decremented by 1, the Hop Limit field in the IPv6 header is decremented by 1, the next-hop node SID information is updated to the IPv6 destination address field, and the Hdr Ext Len field in the SRH header and the PayloadLength field in the IPv6 header are modified. Then, the packet is looked up to determine the next-hop forwarding interface. If it is the last hop, the current packet is received, and the next header of the SRH in the data packet is processed.

4. The in-band network telemetry implementation method in an SRv6 network according to claim 1, characterized in that, The Arguments field in the SID occupies 16 bits; telemetry instructions are expressed in bitmap form, and setting the current bit to 1 indicates that telemetry is performed on the metadata item.

5. The in-band network telemetry implementation method in an SRv6 network according to claim 1, characterized in that, Insert the relevant telemetry metadata to the end of the SRH, specifically including: Insert the corresponding telemetry metadata into the TLV field at the end of the SRH.

Citation Information

Patent Citations

  • A network telemetry method based on SRv6

    CN114050994B

  • Network measurement method and device based on SRv6 and INT

    CN115766552B

  • Network telemetering method based on SRv6

    CN114050994A

  • Stateful in-band network telemetering method and system

    CN114666681A