Method for detecting link quality and routing node

Abstract

The invention provides a method for detecting the quality of a link and a routing node, and the method comprises the steps: the routing node obtains the link state information of a downstream routing node, and transmits the obtained link state information and an End.X identifier corresponding to the link to an upstream routing node of routing node equipment. By means of the method, the technical problem of resource waste caused by the fact that a large number of Srv6policy detection messages are borne on the same link can be effectively solved.

Description

Technical Field

[0001] The present specification relates to the field of communication technology, and in particular to a method for detecting link quality and a routing node. Background Art

[0002] SR (Segment Routing) uses the source node path selection mechanism, and pre-encapsulates the SID (Segment Identifier) ​​of the segment that the path will pass through at the source node. When the message passes through the SR node, the node forwards the message according to the SID of the message. Except for the source node, other nodes do not need to maintain the path status. SRv6 refers to the use of SR in an IPv6 network and forwarding messages using IPv6 addresses as SIDs.

[0003] iFIT (in-situ Flow Information Telemetry) is a measurement technology applied to SRv6 networks to measure network performance indicators. It directly measures parameters such as the actual packet loss rate and latency of service messages, and has the advantages of easy deployment and high statistical accuracy.

[0004] Depending on the measurement, iFIT is divided into: iFIT application-level quality measurement and iFIT tunnel-level quality measurement.

[0005] iFIT application-level quality measurement: used to measure parameters such as packet loss rate and latency when business traffic flows through the transmission network. The measurement results can be used to diagnose the transmission quality of the network when business traffic flows through the transmission network.

[0006] iFIT tunnel-level quality measurement: used to measure parameters such as packet loss rate and latency of SRv6 tunnel transmission packets. The measurement results can be used for SRv6 TE policy intelligent path selection.

[0007] iFIT works with SRv6 TE Policy to measure the end-to-end quality of SRv6 tunnels of SRv6 TE Policy. The measurement results are used by SRv6 TE Policy for intelligent path selection.

[0008] In iFIT application-level quality measurement, iFIT measurement results are reported to the collector through Telemetry, which performs aggregation and calculation. To support SRv6 TE Policy intelligent path selection, the iFIT measurement results of the SRv6 TE Policy head node and tail node must be sent to the head node, which performs aggregation and calculation.

[0009] When the same link is reused multiple times (when there are multiple policies), a large number of detection messages will be generated on the link, resulting in a waste of resources. Summary of the invention

[0010] To overcome the problems existing in the related art, this specification provides a method and a routing node for detecting link quality.

[0011] According to a first aspect of an embodiment of this specification, a method for detecting link quality is provided, the method comprising:

[0012] The routing node obtains the link status information of the downstream routing node;

[0013] The acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0014] The routing node obtains link status information of the downstream routing node, including:

[0015] The routing node establishes a neighbor relationship with the downstream routing node;

[0016] The routing node detects the link status information with the downstream device through the TWAMP protocol.

[0017] The step of sending the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device includes:

[0018] Send the link status information and the End.X mark corresponding to the link to the ISIS protocol module;

[0019] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node.

[0020] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node, including:

[0021] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node through an ISIS LSP message.

[0022] The method of enabling the upstream routing node to detect the link quality according to the End.X identifier and the link status information includes:

[0023] After receiving the ISIS LSP message, the upstream routing node obtains the link status information in the ISIS LSP message and the End.X identifier corresponding to the link, and establishes a corresponding relationship;

[0024] The link quality of the policy path to the routing node is calculated according to the corresponding relationship.

[0025] It can be seen from the above embodiments that by detecting the quality of each link segment by segment and using the locator end-X principle published by IGP, the link quality information is published to the head routing node together with the end-x SID, so that the head routing node can calculate the path quality to different destination devices, thereby effectively reducing the technical problem of resource waste caused by carrying a large number of Srv6policy detection messages on the same link.

[0026] According to a second aspect of an embodiment of this specification, a routing node is provided, the routing node comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following method when executing the program:

[0027] The routing node obtains the link status information of the downstream routing node;

[0028] The acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0029] According to a third aspect of an embodiment of this specification, a routing node is provided, the routing node comprising:

[0030] An acquisition module, used to acquire link status information to a downstream routing node;

[0031] The sending module is used to send the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0032] The acquisition module is specifically used to detect link status information with downstream devices through the TWAMP protocol.

[0033] Wherein, the routing node also includes: ISIS protocol module

[0034] The sending module is specifically used to send the link status information and the End.X identifier corresponding to the link to the ISIS protocol module;

[0035] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node.

[0036] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node through an ISIS LSP message.

[0037] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.

[0039] Figure 1 This is a schematic diagram of a network of routing nodes shown in this specification according to an exemplary embodiment.

[0040] Figure 2 It is a flowchart of a method for detecting link quality according to an exemplary embodiment of this specification.

[0041] Figure 3 This is a schematic diagram of a network of routing nodes shown in this specification according to an exemplary embodiment. DETAILED DESCRIPTION

[0042] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

[0043] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0044] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0045] like Figure 1 As shown in the figure, on the head node Router A, three tunnels to Router C, Router D, and Router E are configured respectively, BFD and IFIT are enabled, and three types of BFD packets are sent. The SIDs of the three links (RouterA—>Router B-->Router C, RouterA—>Router B-->Router D, and RouterA—>Router B-->Router E) and the DOH header of IFIT are encapsulated respectively, and the packets are sent from the outbound interface of Router A to detect the link quality on the three policy paths. The measurement results are used for SRv6 Policy intelligent path selection.

[0046] The preceding content shows that the link between Router A and Router B carries IFIT detection messages of three policies at the same time. If the number of policies increases exponentially to thousands, the number of messages on the link will increase, resulting in a waste of resources.

[0047] In order to solve the above technical problems, the present application provides a method for detecting link quality, such as Figure 2 As shown, the method includes:

[0048] S201 The routing node obtains link status information of the downstream routing node;

[0049] S202 sends the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0050] In this embodiment, it is to solve the technical problem of resource waste caused by carrying a large number of Srv6 Policy detection messages on the same link when link reuse exists between routing nodes.

[0051] In step S201, each routing node only needs to detect the link status information of the adjacent downstream routing node, wherein the link status information may include information such as packet loss, delay, jitter, etc., and bind the detected link status information of each link with the End.X of the link.

[0052] For example, Figure 3As shown, Router A detects packet loss, delay, and jitter on the link (End.XA::1) of the adjacent device Router B, and binds it to End.XA::1 of the link. Router B detects the links of Router C (End.XB::1), Router D (End.XB::2), and Router E (End.XB::3) directly connected to it, and binds the link status information detected on Router C to End.XB::1, the link status information detected on Router D to End.XB::2, and the link status information detected on Router E to End.XB::3. In this embodiment, the binding of link status information and End.X can be achieved through a corresponding relationship.

[0053] In step S202, the acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, such as Figure 3 As shown in the figure, Router B can detect the link status information between Router C, Router D, and Router E respectively through the TWAMP protocol. Assume that the link status information of Router C detected by Router B through the TWAMP protocol is link status information 1, and the link status information of Router D detected by Router B through the TWAMP protocol is link status information 2. Assume that the link status information of Router E detected by Router B through the TWAMP protocol is link status information 3. Link status information 1 is bound to End.XB::1, link status information 2 is bound to End.XB::2, and link status information 3 is bound to End.XB::3, and the above bound information is sent to Router A.

[0054] In this embodiment, the above binding information can be published to Router A through the IGP protocol, and Router A can calculate the link quality data to Router C, Router D, and Router E. In this way, redundant detection messages on the link between Router A and Router B are greatly reduced.

[0055] In another example, a routing node device (such as Figure 3 Router B) in the figure can send the detected link status information reaching Router C, Router D, and Router E and the corresponding relationship between End.XB::1, End.XB::2, and End.XB::3 to the ISIS protocol module, and the ISIS protocol module sends the corresponding relationship to the upstream routing node.

[0056] In an example, the ISIS protocol module may send the corresponding relationship to the upstream routing node via an ISIS LSP message.

[0057] In this embodiment, after receiving the ISIS LSP message, the upstream routing node (for example, Router A) obtains the correspondence between the link state information in the ISIS LSP message and the End.X identifier corresponding to the link, and calculates the link quality of the policy path to Router C, Router D, and Router E based on the correspondence.

[0058] To explain the solution in the present disclosure in detail, the present disclosure also provides the following examples for illustration: Figure 3 shown.

[0059] The routing nodes establish neighbor relationships, and after establishing neighbor relationships, they use the TWAMP protocol to detect link status information such as bidirectional path delay, jitter, and packet loss rate of network links. For example, after Router B establishes neighbor relationships with Router C, Router D, and Router E, it uses the TWAMP protocol to detect the link status information from Router B to Router C, Router D, and Router E, and sends each link status information to the ISIS protocol module.

[0060] The ISIS module publishes the link status information of each link to the upstream routing node. For example, Router B detects the quality of the End.XB::1, End.XB::2, and End.XB::3 links through the TWAMP protocol and sends the result to the ISIS module. Through the ISIS neighbor with Router A, the result is included in the sub-TLV of the Extended ISReachability TLV and sent to Router A.

[0061] After Router A receives the following ISIS LSP message, a corresponding relationship between End.X and its link quality is formed in lsdb. When planning the SRv6 Policy path, the link quality of the Policy path to each destination node can be calculated;

[0062] For example, if the policy path configured on Router A is A::1,B::1, the link quality of the policy is the sum of the link quality of End.XA::1 and End.x B:1.

[0063] Through the calculation in the above manner, after the path of the Policy is configured, the quality of the path can be calculated, which can greatly reduce the redundant detection messages on the repeated path of the Policy.

[0064] Based on the above method embodiments, the present disclosure also provides a routing node, the routing node comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following method when executing the program:

[0065] The routing node obtains the link status information of the downstream routing node;

[0066] The acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0067] Based on the above method embodiments, the present disclosure further provides a routing node, the routing node comprising:

[0068] An acquisition module, used to acquire link status information to a downstream routing node;

[0069] The sending module is used to send the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

[0070] The acquisition module is specifically used to detect the link status information with the downstream device through the TWAMP protocol.

[0071] The routing node also includes: an ISIS protocol module

[0072] The sending module is specifically used to send the link status information and the End.X identifier corresponding to the link to the ISIS protocol module;

[0073] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node.

[0074] The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node via an ISIS LSP message.

[0075] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0076] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0077] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention claimed herein. The specification is intended to cover any variations, uses or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not claimed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.

[0078] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0079] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for detecting link quality, characterized in that: The method comprises: The routing node obtains the link status information of the downstream routing node; The acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

2. The method according to claim 1, characterized in that The routing node obtains link status information of a downstream routing node, including: The routing node establishes a neighbor relationship with the downstream routing node; The routing node detects the link status information with the downstream device through the TWAMP protocol.

3. The method according to claim 1, characterized in that The step of sending the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device includes: Send the link status information and the End.X mark corresponding to the link to the ISIS protocol module; The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node.

4. The method according to claim 3, characterized in that: The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node, including: The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node through an ISIS LSP message.

5. The method according to claim 4, characterized in that The method of enabling the upstream routing node to detect the link quality according to the End.X identifier and the link status information includes: After receiving the ISIS LSP message, the upstream routing node obtains the link status information in the ISIS LSP message and the End.X identifier corresponding to the link, and establishes a corresponding relationship; The link quality of the policy path to the routing node is calculated according to the corresponding relationship.

6. A routing node, characterized in that: The routing node includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following method when executing the program: The routing node obtains the link status information of the downstream routing node; The acquired link status information and the End.X identifier corresponding to the link are sent to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

7. A routing node, characterized in that: The routing node comprises: An acquisition module, used to acquire link status information to a downstream routing node; The sending module is used to send the acquired link status information and the End.X identifier corresponding to the link to the upstream routing node of the routing node device, so that the upstream routing node detects the link quality according to the End.X identifier and the link status information.

8. The routing node according to claim 7, characterized in that: The acquisition module is specifically used to detect the link status information with the downstream device through the TWAMP protocol.

9. The routing node according to claim 7, characterized in that: The routing node also includes: an ISIS protocol module The sending module is specifically used to send the link status information and the End.X identifier corresponding to the link to the ISIS protocol module; The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node.

10. The routing node according to claim 9, characterized in that: The ISIS protocol module sends the link status information and the End.X identifier corresponding to the link to the upstream routing node via an ISIS LSP message.

Images