WO2021135468A1

WO2021135468A1 - Segment identifier determining method and device

Info

Publication number: WO2021135468A1
Application number: PCT/CN2020/118937
Authority: WO
Inventors: 王其华
Original assignee: 华为技术有限公司
Priority date: 2019-12-30
Filing date: 2020-09-29
Publication date: 2021-07-08
Also published as: CN113132229A; CN113132229B

Abstract

The present application relates to the technical field of SR. Disclosed are a segment identifier determining method and device. In the method, a first network device may determine a second segment identifier corresponding to a second network device according to a first segment identifier corresponding to the second network device. Because the first segment identifier comprises first identifier information used for identifying the autonomous domain of the second network device, and the second segment identifier does not comprise the first identifier information, the second segment identifier can be said to be obtained by compressing the first segment identifier, such that the first network device can carry the compressed segment identifier in a packet sent to the second network device, so as to reduce the pressure of the first network device as a head node to encapsulate the packet. In addition, the compression of the segment identifier also facilitates the improvement of packet forwarding efficiency.

Description

Method and equipment for determining segment identification

This application claims the priority of a Chinese patent application filed on December 30, 2019 with the application number 201911395279.7 and the title of the invention "Method and Equipment for Determining Segment Identification", the entire content of which is incorporated into this application by reference.

Technical field

This application relates to the technical field of segment routing (segment routing, SR), and in particular to a method and device for determining a segment identifier.

Background technique

SR technology is a routing technology in which the head node deploys a forwarding path at the entrance of the network. The SR technology can be applied to networks that support the sixth-generation Internet Protocol (Internet Protocol Version 6, IPv6), which is referred to as an SRv6 network for short. In the SRv6 network, the head node encapsulates the segment routing header (segment routing header, SRH) in the message. The SRH includes a segment identification (segment identification, SID) list field for indicating the forwarding path of the message. The SID list field includes multiple SIDs, and each SID can be used to identify a node or a link on the forwarding path. Currently, each SID is usually 128 bits (bit), which contains a large number of bits, resulting in low efficiency of the head node in encapsulating the message, and if the SID list includes a large number of SIDs, the head node will encapsulate the message The efficiency is further reduced.

Summary of the invention

The present application provides a method and device for determining a segment identifier, which can improve the efficiency of packet encapsulation by the head node and save network bandwidth resources. The technical solution is as follows:

In a first aspect, a method for determining a segment identifier is provided. In the method, a first network device determines a first segment identifier corresponding to a second network device, and the first segment identifier includes first identifier information, and The first identification information is used to identify the autonomous domain to which the second network device belongs. The first network device generates a second segment identifier based on the first segment identifier, and the second segment identifier does not include the first identification information. The first network device sends a message to the second network device, and the message includes the second segment identifier.

In this application, the first network device may determine the second segment identifier corresponding to the second network device according to the first segment identifier corresponding to the second network device. Because the first segment of identification includes the first identification information used to identify the autonomous domain to which the second network device belongs, and the second segment of identification does not include the first identification information. The second segment identifier is equivalent to compressing the first segment identifier. In this way, the first network device can carry the compressed segment identifier in the message sent to the second network device, so that the first network device can be used as the head node. The pressure to encapsulate the message. In addition, compressing the segment identifier is also beneficial to improve the efficiency of message forwarding. It should be noted that the first segment identifier corresponding to the second network device is used to identify the correspondence between the second network device and the first segment identifier. The first segment identifier is the original segment identifier before compression, and the corresponding relationship is, for example, that the first segment identifier is used to identify the second network device, or the first segment identifier is used to identify the transition from another network device to the second network device. The other network device is, for example, the previous hop device of the second network device, or the first segment identifier may also be another type of segment identifier related to the second network device.

Optionally, in this method: the first network device determines a third segment identifier corresponding to the third network device, the third segment identifier includes second identifier information and third identifier information, and the second identifier Information is used to identify the autonomous domain to which the third network device belongs, and the third identification information is used to identify the third network device in the autonomous domain; the first network device is generated based on the third segment identifier The fourth segment identifier, the fourth segment identifier does not include the second identification information and the third identification information; the first network device sends the message to the third network device, the The message includes the fourth segment identifier.

In this application, for the third network device, the second identification information and the third identification information in the third segment of the identification in the third network device can be compressed at the same time, so as to further reduce the first network device as the head node to encapsulate the message pressure. In addition, further compression of the segment identifier is also more conducive to improving the efficiency of message forwarding.

Optionally, the second network device and the third network device are the same device, the first identification information and the second identification information are the same identification information, and the second segment identifier and the fourth segment identifier Identifies the same paragraph. That is, when applying this application, the segment identifier corresponding to the third network device can also be compressed to compress the segment identifier corresponding to the second network device.

Optionally, in this method: the first network device determines multiple segment identifiers corresponding to the multiple network devices, and the multiple segment identifiers respectively include the same fourth identification information; the first network device is based on The plurality of segment identifiers generates a fifth segment identifier, the fifth segment identifier includes the fourth identification information and fifth identification information, and the fifth identification information is used to identify the number of the plurality of network devices; The first network device sends the message, and the message includes the fifth segment identifier.

In this application, for network devices with multiple identical fourth identification information, a compressed fifth-segment identification can be generated uniformly for nodes with the same fourth identification information, and the compressed fifth-segment identification only needs to It suffices to include the same fourth identification information and the number of the multiple network devices, so as to further reduce the pressure of the first network device as the head node to encapsulate packets. In addition, further compression of the segment identifier is also more conducive to improving the efficiency of message forwarding.

Optionally, the fifth segment of identification does not include the first identification information and sixth identification information respectively corresponding to the plurality of network devices, and the sixth identification information is used to uniquely identify the plurality of network devices. The multiple network devices in the autonomous domain to which the network device belongs.

For network devices with multiple identical fourth identification information, in addition to compressing the fourth identification information, the first identification information and the sixth identification information can be further compressed to further reduce the packaging of the first network device as a head node. The pressure of the message. In addition, further compression of the segment identifier is also more conducive to improving the efficiency of message forwarding.

Optionally, the multiple network devices include a second network device, and the second segment identifier and the fifth segment identifier are the same segment identifier. That is, the foregoing second network device may also be one of the plurality of network devices having multiple identical fourth identification information.

Optionally, the message further includes seventh identification information, where the seventh identification information is used to identify a strategy for generating the second segment identifier by the first network device.

Further, in order to facilitate the intermediate node on the packet forwarding path to quickly determine the destination address of the forwarded packet according to the compressed segment identifier, the seventh identification information can also be carried in the packet, so that subsequent intermediate nodes can generate The strategy for the segment identification after compression, that is, the compression scheme, quickly restores the segment identification before compression to obtain the destination address of the forwarded message.

Optionally, the specific process for the first network device to determine the multiple segment identifiers corresponding to the multiple network devices is: the first network device determines based on the internal gateway protocol IGP messages sent by the multiple network devices respectively Multiple segment identifiers corresponding to multiple network devices; or, the first network device determines multiple segment identifiers corresponding to multiple network devices based on a control message sent by the control device.

In the embodiment of the present application, the segment identifiers before compression of each network device may be issued by the network device itself, or may be issued uniformly by the control device, so as to improve the flexibility of issuing the segment identifiers.

In a second aspect, a method for determining a segment identifier is provided. In the method, a first network device receives a message, and the message includes a first segment identifier corresponding to the second network device; The network device determines first identification information corresponding to the second network device, where the first identification information is used to identify the autonomous domain to which the second network device belongs; the first network device is based on the first identification information And the first segment identifier to generate a second segment identifier corresponding to the second network device; the first network device sends the message to the second network device based on the second segment identifier.

In this application, after the head node compresses the segment identifier of each node on the message forwarding path by the method provided in the first aspect, the first network device can obtain the compressed part of the segment identifier when receiving the message. Then the compressed message of the second network device is restored to obtain the destination address for forwarding the message. Since the head node compresses the segment identifiers of each node, the bandwidth occupied by the packet transmission between the first network device and the second network device will be reduced, thereby improving the efficiency of packet forwarding.

Optionally, the second network device is a next-hop device of the first network device. In this case, in this method, the first network device determines second identification information, and the second identification Information is used to identify the second network device in the autonomous domain; the first network device generates a second segment corresponding to the second network device based on the first identification information and the first segment identifier The identification process is specifically as follows: the first network device generates the second segment corresponding to the second network device based on the first identification information, the second identification information, and the first segment identifier Logo.

If when compressing the segment identification, not only the first identification information is compressed, but also the second identification information is also compressed. In this case, the segment before compression needs to be restored based on the first identification information and the second identification information. Logo.

Optionally, the packet forwarding path includes multiple consecutive network devices, the multiple consecutive network devices correspond to multiple segment identifiers, and the first network device is located on the forwarding path. The first of three consecutive network devices, the plurality of segment identifiers include the same third identifier information, the first segment identifier includes the third identifier information and the fourth identifier information, and the fourth identifier information It is used to indicate the number of the multiple consecutive network devices. In this scenario, the first network device sending the message to the second network device based on the second segment identifier includes: the first network device determines a fifth identifier based on the fourth identification information Information; the first network device determines the updated first segment identifier, the updated first segment identifier includes the third identification information and the fifth identification information; the first network device is based on the The second segment identifier sends the message to the second network device, and the message includes the updated first segment identifier.

For network devices with multiple identical third identification information, if a compressed first segment identifier is uniformly generated for the multiple nodes with the same third identification information, the compressed first segment identifier includes the same third identifier. Identification information and fourth identification information used to indicate the number of the multiple network devices. At this time, after the first network device restores the segment identifier of the second network device before compression based on the third identification information, the fourth identification information needs to be updated, so that subsequent nodes can confirm whether to continue to restore the destination address in the above manner. .

Optionally, the fourth identification information is a first value, the fifth identification information is a second value, and the second value is the first value minus one. Since the fourth identification information is used to indicate the number of network devices whose segment identifiers from the first network device on the forwarding path of the message include the third identification information, the number of the fourth identification information is updated The method may be to directly subtract 1 from the value indicated by the fourth identification information.

Optionally, the first network device determining the first identification information corresponding to the second network device includes: the first network device receives a message, and the message includes the first identification information corresponding to the second network device. Six identification information and seventh identification information, where the sixth identification information includes the first identification information, and the seventh identification information is used to identify the length of the first identification information; the first network device is based on the The sixth identification information and the seventh identification information determine the first identification information.

In this application, the first identification information of each network device may be pre-published in the network, so that subsequent intermediate nodes can restore the compressed segment identification based on the first identification information.

In a third aspect, a first network device is provided, the first network device includes: a determining module configured to determine a first segment identifier corresponding to a second network device, the first segment identifier including first identifier information The first identification information is used to identify the autonomous domain to which the second network device belongs; the generating module is configured to generate a second segment identifier based on the first segment identifier, and the second segment identifier does not include the first segment identifier. An identification information; a sending module, configured to send a message to the second network device, the message including the second segment identifier.

Optionally, the determining module is further configured to determine a third segment identifier corresponding to a third network device, where the third segment identifier includes second identification information and third identification information, and the second identification information is used for To identify the autonomous domain to which the third network device belongs, and the third identification information is used to identify the third network device in the autonomous domain; and the generating module is further configured to generate the third network device based on the third segment identifier. The fourth segment identifier, the fourth segment identifier does not include the second identification information and the third identification information; the sending module is further configured to send the message to the third network device, the The message includes the fourth segment identifier.

Optionally, the second network device and the third network device are the same device, the first identification information and the second identification information are the same identification information, and the second segment identifier and the fourth segment identifier Identifies the same paragraph.

Optionally, the determining module is further configured to determine multiple segment identifiers corresponding to multiple network devices, and the multiple segment identifiers respectively include the same fourth identification information; the generating module is further configured to determine The multiple segment identifiers generate a fifth segment identifier, the fifth segment identifier includes the fourth identification information and fifth identification information, and the fifth identification information is used to identify the number of the multiple network devices; The sending module is further configured to send the message, and the message includes the fifth segment identifier.

Optionally, the multiple network devices include the second network device, and the second segment identifier and the fifth segment identifier are the same segment identifier.

Optionally, the determining module determining multiple segment identifiers corresponding to multiple network devices includes: the determining module determines corresponding to multiple network devices based on internal gateway protocol IGP messages sent by the multiple network devices respectively Or, the determining module determines multiple segment identifiers corresponding to multiple network devices based on the control message sent by the control device.

In a fourth aspect, another first network device is provided, and the first network device includes: a receiving module for receiving a message, the message including a first segment identifier corresponding to the second network device; a determining module, Is used to determine first identification information corresponding to the second network device, where the first identification information is used to identify the autonomous domain to which the second network device belongs; a generating module is used to based on the first identification information and The first segment identifier generates a second segment identifier corresponding to the second network device; a sending module is configured to send the message to the second network device based on the second segment identifier.

Optionally, the second network device is a next hop device of the first network device, and the determining module is further configured to determine second identification information, and the second identification information is used to identify The second network device; the generating module is configured to generate the second segment corresponding to the second network device based on the first identification information, the second identification information, and the first segment identifier Logo.

Optionally, the packet forwarding path includes multiple consecutive network devices, the multiple consecutive network devices correspond to multiple segment identifiers, and the first network device is located on the forwarding path. The first of three consecutive network devices, the plurality of segment identifiers include the same third identifier information, the first segment identifier includes the third identifier information and the fourth identifier information, and the fourth identifier information For indicating the number of the multiple consecutive network devices, the sending module includes: a first determining subunit, configured to determine fifth identification information based on the fourth identification information; and a second determining subunit, configured to determine The updated first segment identifier, the updated first segment identifier includes the third identifier information and the fifth identifier information; a sending subunit is configured to send the second segment identifier to the second segment identifier based on the second segment identifier. The network device sends the message, and the message includes the updated first segment identifier.

Optionally, the fourth identification information is a first value, the fifth identification information is a second value, and the second value is the first value minus one.

Optionally, the determining module includes: a receiving subunit for receiving a message, the message including sixth identification information and seventh identification information corresponding to the second network device, and the sixth identification information includes all The first identification information, the seventh identification information is used to identify the length of the first identification information; the third determining subunit is used to determine the length of the first identification information based on the sixth identification information and the seventh identification information The first identification information.

In a fifth aspect, a network device is provided. The structure of the network device includes a processor and a memory, the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory to execute the above-mentioned first On the one hand, the method described in any possible implementation of the second aspect, or execute the method described in any possible implementation of the second aspect above.

In a sixth aspect, a chip is provided, the chip is set in a network device in a communication network, the chip includes a processor and an interface circuit; the interface circuit is used to receive instructions and transmit them to the processor; The processor is configured to execute the method described in any possible implementation of the foregoing first aspect, or execute the method described in any possible implementation of the foregoing second aspect.

In a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute any possible implementation of the first aspect or the second aspect. The method described.

In an eighth aspect, a computer program product containing instructions is provided, which when run on a computer, causes the computer to execute the method described in any possible implementation of the first aspect or the second aspect.

In a ninth aspect, a network system is provided. The system includes a first network device, a second network device, and a third network device. The first network device is used to determine a first segment corresponding to the second network device. The first segment identifier includes first identifier information, the first identifier information is used to identify the autonomous domain to which the second network device belongs, and the first network device generates a second segment based on the first segment identifier. Segment identifier, the second segment identifier does not include the first identification information, the first network device sends a message to a third network device, the message includes the second segment identifier; the third network A device for receiving a message, the message including the second segment identifier corresponding to the second network device, and the third network device determines the first identifier corresponding to the second network device Information, the first identification information is used to identify the autonomous domain to which the second network device belongs, and the third network device generates a connection with the second network device based on the first identification information and the first segment identification For the first segment identifier corresponding to the device, the third network device sends the message to the second network device based on the first segment identifier.

Description of the drawings

FIG. 1 is a schematic diagram of the format of an SRH provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a format of an SID provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an SRv6 network architecture provided by an embodiment of the present application;

FIG. 4 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of another SID format provided by an embodiment of the present application;

FIG. 6 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a message forwarding process provided by an embodiment of the present application;

FIG. 8 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of another message forwarding process provided by an embodiment of the present application;

FIG. 10 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another message forwarding process provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of another SRH format provided by an embodiment of the present application;

FIG. 13 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of the format of an IGP message provided by an embodiment of the present application;

FIG. 15 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 16 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 17 is a flowchart of another method for determining a segment identifier provided by an embodiment of the present application;

FIG. 18 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 19 is a schematic structural diagram of another network device provided by an embodiment of the present application;

FIG. 20 is a schematic structural diagram of an interface board in the network device shown in FIG. 19 according to an embodiment of the present application;

FIG. 21 is a schematic structural diagram of a first network device provided by an embodiment of the present application;

FIG. 22 is a schematic structural diagram of another first network device provided by an embodiment of the present application;

FIG. 23 is a schematic structural diagram of a network device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions, and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

It should be understood that the "plurality" mentioned herein refers to two or more. In the description of this application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this document is only an association relationship describing associated objects, It means that there can be three kinds of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and order of execution, and words such as "first" and "second" do not limit the difference.

Before explaining the embodiments of the present application, the application scenarios of the embodiments of the present application are first explained.

SRv6 is a network architecture designed based on the concept of source routing to forward IPv6 packets in the network. The head node in the SRv6 network inserts SRH into the IPv6 message header, and presses an IPv6 address list into the SRH. Each forwarding node in the SRv6 network continuously updates the target address according to the IPv6 address list to complete the forwarding of IPv6 data packets one by one. Fig. 1 is a schematic diagram of the format of an SRH provided by an embodiment of the present application. As shown in Figure 1, SRH includes the next header field used to indicate the next header type, the field Hdr Ext Len used to indicate the length of the SRH header, the field routing type used to indicate the routing type, and the field routing type used to indicate the current After the node, the field of the number of nodes that should be visited is segment left, etc. The SRH also includes the SID list field. The SID list field includes multiple SIDs, and each SID may correspond to an IPv6 address, which is used to identify the node or link with the SID on the forwarding path. In addition, as shown in Figure 1, SRH also includes an optional type-length-value (type-length-value, TLV) field. Through these optional TLVs, SRH can achieve more functions, such as failure Diagnostic testing, etc.

The destination address of the message transmitted in the SRv6 network, referred to as IPv6 DA. In traditional IPv6 protocol-based messages, IPv6 DA is fixed. In the SRv6 network, IPv6 DA only corresponds to the next node of the current message, which can be changed continuously.

The SID list in SRH, similar to the label stack information in SR Multi-Protocol Label Switching (MPLS), can be generated at the head node on a forwarding path, and the intermediate nodes on the forwarding path can be based on the SID The list is forwarded. For the convenience of subsequent description, the SID list is expressed as: <Segment List[0], Segment List[1], Segment List[2],...,Segment List[n]>. Among them, each Segment List[m] in the SID list, 0≤m≤n can correspond to each corresponding node on the forwarding path that supports SRv6. Taking the message forwarding path as the strict display path as an example, the strict display path means that the SID corresponding to each node on the message forwarding path is included in the SID list in the SRH header. It should be noted that the segment identifier corresponding to the node is used to identify the corresponding relationship between the second network device and the first segment identifier. The segment identifier is, for example, the originally allocated segment identifier, and the correspondence relationship is, for example, the segment identifier is used to identify the node itself, or the segment identifier is used to identify the link from another node to the node, and the other The node is, for example, the previous hop node of the node. In other situations, the segment identifier may also be other types of segment identifiers related to the node. At this time, Segment List[0] corresponds to the tail node on the forwarding path, Segment List[1] corresponds to the penultimate node on the forwarding path, and Segment List[n] corresponds to the second node on the forwarding path. The two nodes are the nodes immediately after the head node, and so on, pushing the stack in reverse order. In some possible implementations, the forwarding path of the message may also be a loose display path. The loose display path means that the SIDs corresponding to some nodes on the forwarding path of the message are included in the SID list in the SRH header. In this case, Segment List[n] may correspond to, for example, the second or third node on the forwarding path that supports the SRv6 protocol. The situations listed above are only examples. It should be noted that in other situations, the Segment List sequence in the SID list may correspond to multiple corresponding nodes on the forwarding path according to a certain rule, and the multiple corresponding nodes may be, for example, Strictly display continuous nodes on the path, or loosely display multiple corresponding nodes that are not continuous on the path but support the SRv6 protocol.

In the SRv6 network, the Segment List value in the SID list corresponds to the node on the forwarding path as an example. Every time a node that supports SRv6 passes, the value of the SL field is reduced by 1, and the IPv6 DA information is also changed accordingly. The SL field and the SID list field jointly determine the IPv6 DA information. An example of the specific transformation process is as follows:

If the SL value is n, the IPv6 DA value is the value of Segments List[n] in the SID list.

...

If the SL value is 1, the IPv6 DA value is the value of Segments List[1] in the SID list.

If the SL value is 0, the IPv6 DA value is the value of Segments List[0] in the SID list.

The above SID is an instantiated IPv6 address. This type of IPv6 address is given a unique function. The SID in an SRv6 network can represent a node or link, or it can represent an L2/L3 virtual private network (virtual private network). , VPN), or a service.

As shown in FIG. 2, each SID may include two parts, one part is a locator field, and the other part is a function field. The positioning field occupies high bits among 128 bits. The function field occupies the low bit of 128 bits. The location field can take on the routing function, so it needs to be unique in the SR domain. The function field can identify any function of the device, such as a certain forwarding behavior, or a certain service. Based on the difference in the function field, SID specifically includes END, END.X, and END.DT types. The END type SID can be used to identify a node. SID of type END.X can be used to identify a link. The END.DT type SID can be used to identify a VPN or service. END.DT specifically includes END.DT4 and other types, where END.DT is used to indicate the SID of the operator edge (provider edge, PE) device, and is used to identify a fourth-generation Internet protocol (internet protocol version 4) in the network. , IPv4) VPN instance.

The method for determining the segment identifier provided in the embodiment of the present application is applied to the above scenario in which the SRH realizes the hop-by-hop transmission of the message in the SRv6 network. FIG. 3 is a schematic diagram of an SRv6 network architecture provided by an embodiment of the present application. As shown in Figure 3, the SRv6 network includes node R1, node R2, node R3, node R4, and node R5. Among them, node R1 is the head node of the SRv6 network, node R2, node R3, and node R4 are intermediate nodes of the SRv6 network, and node R5 is the tail node of the SRv6 network.

The node R1 is used to press the SRH into the message, and forward the message pressed into the SRH to the node R2, and the node R2 forwards the message to the node R5 hop by hop according to the SRH. Node R1, node R2, node R3, node R4, and node R5 can be any routing device with SRv6 function. In addition, the SRv6 network shown in FIG. 3 only uses five nodes as an example for description, and does not constitute the only limitation on the number of nodes in the SRv6 network provided in the embodiment of the present application.

The method for determining the segment identifier provided in the embodiment of the present application will be explained in detail below.

In the embodiment of the present application, in order to improve the efficiency of packet encapsulation and packet forwarding efficiency of the head node, the head node compresses each SID in the original SID list when determining the SRH, so that the SID carries the compressed SID. . After receiving the message, the subsequent intermediate node restores the compressed SID in the SRH to determine the destination address of the message. Therefore, the method for determining the segment identifier provided in the embodiment of the present application mainly includes two processes, one is a process in which the head node presses the SRH into the message, and the other is a process in which the intermediate node determines the destination address according to the SRH and forwards the message. The two processes are explained separately below.

It should be noted that the first and second concepts in any of the following embodiments and the first and second concepts in other embodiments are independent of each other, and are not strictly corresponding. For example, the first network device in one embodiment and the first network device in another embodiment may not be used to indicate the same network device. The specific concepts will be explained one by one in the following embodiments.

FIG. 4 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is applied to a head node in an SRv6 network, that is, the first network device in the following embodiment is the head node. As shown in Figure 4, the method includes:

S401: The first network device determines a first segment identifier corresponding to the second network device, where the first segment identifier includes first identification information, and the first identification information is used to identify the autonomous domain to which the second network device belongs.

The first network device may be the head node on a certain forwarding path in the SRv6 network, and the second network device may be the next hop node of the head node on the forwarding path, or the forwarding path Other nodes on the upper end, such as intermediate nodes or tail nodes. The first segment identifier corresponding to the second network device is the original SID configured for the second network in the SRv6 network, and the original SID may be an IPv6 address including 128 bits.

The first network device to determine the first segment of the identifier corresponding to the first network device may be implemented as follows: the first network device determines the connection with the second network device based on the Interior Gateway Protocol (IGP) message issued by the second network device The first segment identifier corresponding to the device. Alternatively, the first network device determines the first segment identifier corresponding to the second network device based on the control message sent by the control device. That is, the original SID of each network device in the SRv6 network may be issued by the network device itself in the network, or it may be issued uniformly by the control device.

In the embodiment of the present application, in order to achieve compression of the original SID, the location field in the original SID is re-divided, that is, the space of the original SID is re-planned. As shown in FIG. 5, the positioning field in FIG. 2 is divided into a first positioning field and a second positioning field. To facilitate subsequent descriptions, this application refers to the first positioning field as a flocator field, and the second positioning field as a vlocator field. For the original SID of the second network device, the flocator field is used to identify the autonomous domain (Autonomous Systems, AS) to which the second network device belongs, and the vlocator field is used to identify the second network device. At this time, the original SID includes three parts, the flocator field, the vlocator field, and the function field. For ease of presentation, this application refers to the function field as a function field. In a possible implementation manner, the function field may be fixed to 16 bits, and the number of bits included in the vlocator field may be less than or equal to 16 bits. It should be noted that the length of the above-mentioned fields is only an example, and does not constitute the only limitation on the length of the flocator field, the vlocator field, and the function field in the embodiment of the present application.

S402: The first network device generates a second segment identifier based on the first segment identifier, and the second segment identifier does not include the first identification information.

The first network device in S402 may be the head node R1 in FIG. 3, and the first identification information may be the flocator field in the original SID. Because the flocator field of each node in the SRv6 network is usually the same, that is, it identifies the same AS where each node is located. Therefore, the first network device may compress the original SID of the second network device through S402 to obtain the second segment identifier, so that the second segment identifier does not include the flocator field. When the next-hop network device of the first network device receives the SRH that includes the compressed second segment identifier, the next-hop network device may perform a check on the AS information according to the locally known AS information. The second segment identifier is restored to obtain the complete first segment identifier corresponding to the second segment identifier. The AS information known by the next-hop network device may be pre-configured and stored locally, or may be obtained and stored from the network control device, for example.

It should be noted that there can be multiple compression methods for the second segment of the identification that does not include the first identification information. For example, for the scenario where the forwarding path of the message is a strict display path, in some cases, because in the strict display path The two adjacent nodes corresponding to the SID list are located in the same IGP domain, so the two adjacent nodes can know in advance the relevant information of each other's original SID (for example, the vlocator field in the original SID), so For scenarios where the forwarding path of the message is strictly displayed, there are at least the following three compression methods. The first is that the compressed second segment identifier not only does not include the flocator field (that is, the first identification information in S401), nor does it include the vlocator field, but only includes the function field. If the length of the function field is 16 bits, this This compression method can be called 16-bit compression. The second is that the compressed second segment identifier not only does not include the flocator field (also the first identification information in S401), nor does it include the vlocator field, but only includes the function field and other necessary indication information. If the length of the function field is It is 16 bits, and the indication information occupies 4 bits, so this compression method can be called 20-bit compression. The 20-bit compression method is suitable for scenarios where the function field of the SID corresponding to each node on the forwarding path has certain characteristics. For example, when the function field of the SID corresponding to some or all consecutive nodes on the forwarding path is the same, it can be passed This 20-bit compression method performs compression, where the indication information is used to identify the number of SIDs with the same function field remaining after the current node. The third type is that the compressed second segment identifier does not include the flocator field (that is, the first identification information in S401), but includes the vlocator field and the function field. If the vlocator field and the function field are both 16 bits, this kind of compression The method can be called 32-bit compression. The specific implementations of the above three compression methods will be separately explained in the following, and will not be repeated here.

In addition, for the scenario where the forwarding path of the message is a loosely displayed path, since the two adjacent nodes in the SID list may not be nodes in the same IGP domain at this time, the two adjacent nodes may not be able to know each other’s vlocator field. Therefore, for the scenario where the forwarding path of the message is a loosely displayed path, at least the following two compression methods are possible. One is the above-mentioned 32-bit compression method, which compresses only the flocator field, but retains the vlocator field and the function field. The other is that the compressed second segment identifier not only does not include the flocator field (that is, the first identification information in S401), nor the function field, but only includes the vlocator field. In order to distinguish it from the above 16-bit compression method, This compression method can be called 16-bit compression under loose path. Among them, the 16-bit compression method under the loose path is suitable for scenarios where the function field of the SID corresponding to each node on the forwarding path is the same. For example, in the scenario where the path is loosely displayed, if each SID in the SID list is an END type SID , It can be compressed by 16-bit compression under this scattered path. The implementation of the 16-bit compression method under the loose path can refer to the implementation of the three compression methods under the strict display path described above, which is not described in detail in the embodiment of the present application.

It should be noted that the above-mentioned compression schemes applicable to the strict display path and the loose display path respectively are taken as examples. It is understandable that in some possible implementations, the application scenarios of different compression schemes may also change. For example, if the node on the forwarding path is allowed to request the vlocator field corresponding to other nodes from the controller, or the node on the forwarding path that supports SR is based on a mechanism agreed with the controller, it can obtain and store the downloads that support SR in advance. When the vlocator field corresponding to a one-hop node is used, the 16bit compression mode under the strict display path (that is, the compression scheme of flocator and vlocator is not included) can also be applied on the loose path.

S403: The first network device sends a message to the second network device, and the message includes a second segment identifier.

The second network device is, for example, the next-hop network device R2 of the head node R1. After obtaining the compressed second segment identifier, R1 encapsulates it into the SRH header, for example, as a Segment List[3], and sends it to R2 through a message. In some possible implementation manners, the head node R1 may also determine the compressed identifiers for other network devices on the forwarding path, and encapsulate them into the SRH header. For example, for the network structure shown in Figure 3, R1 can respectively compress the initial segment identifiers corresponding to R3, R4, and R5 and place them into Segment List[2], Segment List[1], and Segment List[0]. Into the SRH header, and then send a message encapsulated with the SRH to the second network device. It should be noted that the second network device in S403 may be the next-hop device of the head node on the packet forwarding path, such as R2 shown in FIG. 3, or other network devices on the forwarding path, such as Figure 3 shows R3, R4 or R5. Taking the second network device as R3 as an example, the message sent by R1 after encapsulating the SRH header will be sent to R2 first and perform an update operation, such as restoring the compressed Segment List[3] to the original value and then hitting it. Pop up, and update the destination address DA according to the original value. Then, the updated message is forwarded from R2 to R3. At this time, R3 can receive the updated message including the corresponding second segment identifier.

In the embodiment of the present application, the first network device may determine the second segment identifier corresponding to the second network device according to the first segment identifier corresponding to the second network device, because the first segment identifier includes the identifier used to identify the second network device to which the second network device belongs. The first identification information of the autonomous domain, and the second identification information does not include the first identification information. Therefore, the second identification is equivalent to compressing the first identification. In this way, the first network device is sending to the second network device. The compressed segment identifier can be carried in the message to reduce the pressure of the first network device as the head node to encapsulate the message. In addition, compressing the segment identifier is also beneficial to improve the efficiency of message forwarding.

Based on the foregoing embodiment, it can be seen that the embodiment of the present application provides three different compression methods: 16-bit compression, 20-bit compression, and 32-bit compression. The above three compression methods will be explained in conjunction with specific examples. For ease of description, take the original SID length of 128 bits, where the flocator occupies 96 bits, the vlocator and function fields occupies 16 bits respectively, and when the second compression method is used, the indication information field occupies 4 bits as an example , Respectively explain the above three compression methods as examples. Understandably, under the foregoing premise, three compression methods can be used to compress the original SID into 16-bit, 20-bit, and 32-bit compression schemes, referred to as 16-bit, 20-bit, and 32-bit compression schemes. It should be noted that if the length of the flocator, vlocator, and/or function field changes, the original SID can still be compressed using the aforementioned three compression methods, but the length of the compressed SID may change.

Fig. 6 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is used to explain the 32-bit compression scheme. The method includes the following processes:

S601: The first network device determines a first segment identifier corresponding to the second network device, where the first segment identifier includes first identification information, and the first identification information is used to identify the autonomous domain to which the second network device belongs.

The implementation manner of S601 may refer to the implementation manner of S401 in the embodiment of FIG. 4, and the description will not be repeated here.

S602: The first network device generates a second segment identifier based on the first segment identifier. Compared with the first segment identifier, the second segment identifier only does not include first identification information, and the first identification information identifies the AS to which the second network device belongs.

In the above 32-bit compression method, the function field and the vlocator field in the original SID are retained, and the flocator field in the original SID is deleted. It should be noted that the 32-bit compression method can be applied to all types of original SIDs.

S603: The first network device sends a message to the second network device, where the message includes the second segment identifier.

For the implementation of S603, reference may be made to the implementation of S403 in the embodiment of FIG. 4, which will not be repeated here in detail.

FIG. 7 is a schematic diagram of a packet forwarding based on the 32-bit compression mode of FIG. 6 provided by an embodiment of the present application. As shown in Figure 7, node R1 can be configured with two types of original SIDs, for example, END A:1:0 and END.X A:1:3, END A:1:0 are used to identify nodes R1 and END. X A: 1:3 is used to identify the link from node R1 to the next hop node R2. Similarly, node R2 can also be configured with two types of original SIDs, namely END A: 2:0 and END. X A: 2: 5, END A: 2:0 is used to identify node R2, END. X A :2:5 is used to identify the link from node R2 to node R3. Node R3 is configured with two types of original SIDs, namely END A: 3:0 and END. X A: 3: 6, END A: 3:0 is used to identify node R3, and END. X A: 3: 6 To identify the link from node R3 to node R4. Node R4 is configured with two types of original SIDs, namely END A: 4:0 and END. X A: 4: 1, END A: 4:0 is used to identify node R4, and END. X A: 4: 1 To identify the link from node R4 to node R5. The node R5 is configured with a type of original SID, which is END DT4 A:5:8001, and END DT4 A:5:8001 is used to identify that the node R5 corresponds to an IPv4 VPN instance. These original SIDs are all expressed in the format of ××:××:××, where the field before the first ":" is the flocator field, and the field between the first ":" and the second ":" is The vlocator field, the field after the second ":" is the function field.

When forwarding the message, the head node can use the SID list encapsulated in the SRH to specify the message forwarding path. The SID type in the SID list can be, for example, the node SID, the link SID, or the IPv4 VPN type SID.

Still taking Fig. 7 as an example, the original SID list before compression received by the head node R1 can be expressed as: <A:5:8001, A:4:0, A:3:6, A:2:0>. If the head node R1 compresses the original SID list according to the 32-bit compression method, as shown in Figure 7, the compressed SID list can be expressed as: <5:8001, 4:0, 3:6, 2:0 >, that is, the compressed SID does not include the same AS domain identifier "A". The compressed SID list in the message sent by the head node R1 to the intermediate node R2 is represented as <5:8001, 4:0, 3:6, 2:0>. It should be noted that, for ease of understanding, the SID list in Figure 7 lists the types of each SID, such as END A before compression and cEND A after compression, but in the actual forwarded message, the above-mentioned types are not identified. Does not appear in the SID list. The SID list only includes SID values of each corresponding type.

FIG. 8 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is used to explain the 16-bit compression method. The method includes the following processes:

S801: The first network device determines a first segment identifier corresponding to the second network device, where the first segment identifier includes first identification information and second identification information, and the first identification information is used to identify the second network device to which the second network device belongs The second identification information is used to identify the second network device.

For the implementation of S801, reference may be made to the implementation of S401 in the embodiment of FIG. 4. That is, in S801, the first network device may be the head node on a certain forwarding path in the SRv6 network, and the second network device may be the next hop node of the head node on the forwarding path , It can also be other nodes on the forwarding path, such as an intermediate node or a tail node.

S802: The first network device generates a second segment identifier based on the first segment identifier. Compared with the first segment identifier, the second segment identifier does not include the first identifier information and the second segment identifier. Identification information.

That is, the 16-bit compression scheme can only retain the function field in the original SID, and delete the flocator field and vlocator field in the original SID. Based on the embodiment shown in Fig. 4, it can be seen that since the two adjacent nodes corresponding to the SID list in the strict display path are located in the same IGP domain, the two adjacent nodes can know the original source of each other in advance. The vlocator field of the SID. For the scenario where the forwarding path of the message is a loosely displayed path, since two adjacent nodes corresponding to the SID list may not be located in the same IGP domain at this time, the two adjacent nodes may not be able to learn each other's vlocator field. In the 16-bit compression scheme provided in the embodiment of FIG. 8, the vlocator field needs to be compressed. Therefore, the 16-bit compression scheme provided in the embodiment of FIG. 8 is only applicable to the scenario where the forwarding path of the message is a strict display path.

In addition, it should be noted that in some application scenarios, such as the strict display of message forwarding, only the last 8 bits in the function field of each original SID on the path may be different, and the values of the first 8 bits are all 0-, at this time, when compressing the original SID of each node, the head node can only retain the last 8 bits of the function field in the original SID. This compression scheme is actually similar to the 16-bit compression scheme, that is, only the relevant information of the function field is retained, but it can further save network resources and improve the forwarding efficiency by combining the actual characteristics of the SID.

S803: The first network device sends a message to the second network device, where the message includes the second segment identifier.

For the implementation of S803, reference may be made to the implementation of S403 in the embodiment of FIG. 4, which will not be repeated here in detail.

FIG. 9 is a schematic diagram of a packet forwarding based on the 16-bit compression method of FIG. 8 provided by an embodiment of the present application. As shown in Figure 9, node R1 is configured with two types of original SIDs, namely END A:1:0 and END.X A:1:3. The node R2 is configured with two types of original SIDs, namely END A: 2:0 and END. X A: 2:5. Node R3 is configured with two types of original SIDs, namely END A: 3:0 and END. X A: 3:6. Node R4 is configured with two types of original SIDs, namely END A: 4:0 and END. X A: 4: 1. Node R5 is configured with a type of original SID, which is END DT4 A:5:8001. The original SID of each node has been described in detail in the embodiment shown in FIG. 7, and will not be repeated here.

As shown in Figure 9, the original SID list before compression can be expressed as: <A:5:8001, A:4:1, A:3:6, A:2:5>. The path for the message to be forwarded from R1 to R5 is a strict display path, so the head node can compress the intermediate node R2, the intermediate node R3, and the intermediate node R4 in a 16-bit compression mode. In some cases, since the original SID of the tail node is usually used to indicate a VPN, for this type of SID, in order to avoid other problems caused by the inability to restore the real IP address of the VPN due to the interruption of the intermediate link, you can It is agreed that the original SID of the tail node is compressed according to the 32-bit compression method, that is, the tail node R5 is compressed using a 32-bit compression scheme, as shown in Figure 9, the compressed SID list can be expressed as <5:8001, 1, 6, 5>. That is, the SID list included in the SRH in the message sent by the head node R1 to the intermediate node R2 is <5:8001, 1, 6, 5>. It should be noted that in the foregoing process of compressing the tail node R5, a 16-bit compression scheme may also be used for compression, which is not specifically limited in the embodiment of the present application.

Based on the explanation about the original SID in the example shown in FIG. 4, it can be known that the function field in the original SID is usually used to indicate the function of the corresponding SID. Therefore, different original SIDs may have the same function field, which is used to indicate that these original SIDs correspond to the same function. Therefore, for the scenario where the forwarding path of the message is a strictly displayed path, if the function field of the original SID of each node on the forwarding path of the message is the same, the head node can also use the compression method shown in Figure 10 below (that is, It is a 20-bit compression method) to compress the original SID of each node.

FIG. 10 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is used to explain the 20-bit compression scheme. The method includes the following processes:

S1001: The first network device determines multiple segment identifiers corresponding to the multiple network devices, and the multiple segment identifiers respectively include the same fourth identification information.

In S1001, the segment identifier corresponding to each network device is the original SID of the network device, and the specific type can be a node type, a link type, or other types. The multiple network devices may be multiple consecutive nodes in the packet forwarding path, for example. The fourth identification information is the function field in the original SID. As shown in FIG. 3, the first network device may be a head node R1, and the multiple network devices may be intermediate nodes R2, R3, and R4 after the head node R1.

In S1001, the implementation manner for the first network device to determine the multiple segment identifiers corresponding to the multiple network devices can refer to S401 in the embodiment shown in FIG. 4 for the first network device to determine the first segment identifier corresponding to the second network device. The implementation method of, I won’t go into details here.

S1002: The first network device generates a fifth segment identifier based on the plurality of segment identifiers, where the fifth segment identifier includes the fourth identification information and fifth identification information, and the fifth identification information is used to identify the plurality of networks The number of devices.

That is, when the function fields of multiple nodes on the message forwarding path are the same, a compressed SID can be generated uniformly for these nodes with the same function field, and the compressed SID only needs to include the same function field and this number. The number of network devices is sufficient.

In a possible implementation manner, when the function fields of multiple nodes on the message forwarding path are the same, only the function fields may be compressed in the foregoing manner, but the flocator fields of the multiple nodes may not be compressed. At this time, the compressed SIDs used to indicate the corresponding multiple nodes may also include the flocator fields of the multiple nodes.

In another possible implementation, based on the explanation of the original SID in S401, it can be known that the original SID also includes the flocator field and the vlocator field. Therefore, if each subsequent node can obtain the flocator field and the vlocator field from other means, At this time, when compressed by the 20-bit compression method shown in FIG. 10, the compressed fifth segment of identification may also not include the first identification information (that is, the flocator field) and the sixth segment corresponding to multiple network devices. Identification information (that is, the vlocator field). The sixth identification information is respectively used to uniquely identify multiple network devices in the autonomous domain. That is, when the function field of each node on the message forwarding path is the same, the function field, the flocator field, and the vlocator field are compressed at the same time.

S1003: The first network device sends a message to the multiple network devices, where the message includes the fifth segment identifier.

For example, the first device among the plurality of network devices to receive the message may be the next hop node of the first network device; for another example, the first device among the plurality of network devices to receive the message The device of the text may not be the next hop node of the first network device, but a subsequent node on the strict display path forwarding the message, and the next hop node of the first network device may use the aforementioned 32bit Or 16bit compression scheme.

FIG. 11 is a schematic diagram of a forwarded packet based on the 20-bit compression method shown in FIG. 10 according to an embodiment of the present application. As shown in Figure 11, node R1 is configured with two types of original SIDs, namely END A:1:0 and END.X A:1:5060. The node R2 is configured with two types of original SIDs, namely END A: 2:0 and END. X A: 2:5060. Node R3 is configured with two types of original SIDs, namely END A: 3:0 and END. X A: 3:5060. Node R4 is configured with two types of original SIDs, namely END A: 4:0 and END. X A: 4: 5060. Node R5 is configured with a type of original SID, which is END DT4 A:5:8001. For the related functions of each original SID of each node, reference may be made to the embodiment shown in FIG. 7, which will not be repeated here.

As shown in Figure 11, the original SID before compression can be expressed as: <A:5:8001, A:4:5060, A:3:5060, A:2:5060>. At this time, since the forwarding path of the message is strictly displayed, and the function field of the original SID corresponding to each intermediate node is the same, the head node can compress the intermediate node R2, intermediate node R3, and intermediate node R4 according to the 20-bit compression scheme. The 32-bit compression scheme compresses the intermediate node R5. As shown in Figure 11, the compressed SID list can be expressed as <5:8001, 5060:3>. In the above SID list, 5:8001 corresponds to the tail node R5. 5060:3 is used to indicate that there are 3 nodes R2 to R4 whose function fields are all 5060. The SID list included in the SRH in the message sent by the head node R1 to the intermediate node R2 is <5:8001, 5060:3>.

Based on the above embodiments of FIG. 4 to FIG. 11, it can be seen that when the head node compresses the original SID corresponding to each node on the forwarding path of the message, different compression methods can be used for compression. In order to facilitate subsequent nodes to be able to determine the destination address of the message from the compressed SID. The message sent by the head node to the second network device may further include seventh identification information, where the seventh identification information is used to identify a strategy for generating the second segment identifier by the first network device. For example, for the method of determining a segment identifier shown in FIG. 6, the seventh identification information may be used to identify that the first network device generates a compressed second segment identifier corresponding to the second network device through a 32-bit compression method.

In some possible implementations, different compression methods can be used for the original SID of each node or link on the forwarding path. In this case, multiple identification information can be used to respectively identify the first network device to generate the corresponding node or the corresponding node on the forwarding path. The strategy of the compressed segment identifier of the link, so that the corresponding node on the forwarding path can determine the corresponding segment identifier restoration method based on the strategy. For example, for the packet forwarding path shown in Figure 9, multiple identification information is used to identify the first network device to generate the second segment identifiers of the intermediate nodes R2 to R4 through 8-bit compression, and to generate the second segment identifiers through 32-bit compression. The second segment identifier of the tail node R5. Through the multiple identification information, the present application can support the generation of each SID in the same SID table using different compression schemes. In other possible implementation manners, the identification information may also be used to identify a solution that does not compress the original SID, for example, one or more SIDs on the forwarding path are not compressed, and the original 128 bits are still retained. The content of the identification information corresponding to each different compression scheme and the uncompressed scheme is different.

In a possible implementation manner, the SRH shown in FIG. 1 may be extended, so that the extended SRH carries the seventh identification information. It should be noted that there can be multiple specific implementations of SRH extension, and it is only necessary to ensure that the extended SRH can indicate the compression scheme (including the uncompressed scheme) of each SID in the SID list.

As a possible example, FIG. 12 is a schematic diagram of an extended SRH format provided in an embodiment of the present application. As shown in Figure 12, the field used to carry the SID list in Figure 1 is currently used to carry various types of compressed SIDs, for example, cSID compressed according to 20-bit compression, and cSID compressed according to 8-bit compression And the cSID compressed according to the 32-bit compression method, in addition to the uncompressed 128-bit original SID. It should be noted that in Figure 12, all compression methods are reflected in the SID list. In practical applications, the compressed SID in the SID list can be the SID compressed by the same compression method, or it can be used as needed. SID compressed by a variety of optional compression methods.

As shown in FIG. 12, a type-length-value (type-length-value, TLV) field may be used to carry multiple pieces of identification information used to indicate the compression strategy. The identification information includes, for example, corresponding to the second network device. Of the seventh identification information. Specifically, a bitmap (bitmap) BMP field can be set in the TLV. The BMP field is used to indicate the compression strategy corresponding to each compressed SID in the SID list. That is, the bitmap field includes indication information for indicating the compression mode of each SID in the SID list. In addition, since the SL field in SRH is used to indicate which SID is currently processed into the SID list, and each SID in the traditional SID list is 128 bits, the SID list in the traditional SRH is actually based on each SID list. The 128 bits are divided into a group. At this time, the SL field in the SRH actually indicates which group of 128 bits are currently processed into the SID list. In this application, since the SIDs in the SID list may be compressed SIDs, each group of 128 bits may also include multiple compressed SIDs. Therefore, only the SL field cannot directly locate the specific SID. Therefore, other indication fields can be set in the TLV field accordingly, such as the pointer (PI) field. The PI field is used to coordinate with the SL field to locate the indication of the SL field. Which specific SID in a set of 128 bits. Based on the above configuration, in the process of forwarding the message, the network device receiving the message can first locate the compressed SID corresponding to the current node in the forwarding path according to the PI field and the SL field in the SRH, and then determine the compression through the BMP field The compression strategy corresponding to the SID. The network device receiving the message can restore the acquired SID according to the acquired compressed SID and compression strategy, and then obtain the original SID before compression for subsequent forwarding of the message.

It should be noted that the embodiment of the present application does not limit the specific implementation manner and setting location of the PI field and the BMP field, and only the set PI field and BMP field can implement the above-mentioned functions. The foregoing Figures 8 to 11 are used to explain the three compression schemes provided by the embodiments of the present application. In applying the method for determining the segment identifier provided by the embodiment of the present application, the head node may determine the original SID compression scheme for each network device according to actual requirements. Alternatively, the control device determines the compression scheme for the original SID of each network device according to actual requirements, and then sends the determined compression scheme to the head node, so that the head node determines the SRH based on the compression scheme for the original SID of each network device.

The embodiments shown in Figures 4 to 12 above are used to explain how the head node compresses the original SID of each node in the message forwarding path. Next, the intermediate node determines the destination address according to the compressed SID and forwards it. The message process is explained.

FIG. 13 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is applied to an intermediate node in an SRv6 network, that is, the second network device in the following embodiment can be any on the forwarding path Intermediate node, the method can be used to restore the compressed SID. As shown in Figure 13, the method includes the following processes:

S1301: The second network device receives a message, and the message includes a second segment identifier corresponding to the third network device.

The second network device may be an intermediate node in the packet forwarding path in the embodiments shown in FIGS. 4 to 12, and the third network device is the next SRv6-supporting node on the forwarding path and located after the second network device. node. As shown in FIG. 3, for example, the second network device may be the intermediate node R2, and the third network device may be the intermediate node R3 in this case. For another example, the second network device may also be the intermediate node R3, and in this case, the third network device may be the intermediate node R4. In the above strict display path, the third network device is actually the next hop device of the second network device. It should be noted that in some situations, for example, when the forwarding path is a loose display path, the third network device may not necessarily be the next hop device of the second network device, but after the third network device on the path, The next network device that supports SRv6. In this case, there may be one or more network devices between the third network device and the second network device. The one or more network devices may not support SRv6, but it can be done Transparent transmission of messages.

Based on the embodiments shown in Figures 4 to 12, it can be seen that the second segment of the identifier corresponding to the third network device included in the message is the original SID of the head node to the third network device (that is, the original SID shown in Figure 4). The first segment identifier in the embodiment) is the SID obtained after compression. That is, the second segment of identification in S1301 does not include the first identification information, and the first identification information is used to identify the AS to which the second network device belongs (that is, the flocator field in the original SID).

S1302: The second network device determines first identification information corresponding to the third network device, where the first identification information is used to identify the autonomous domain to which the third network device belongs.

Based on S1301, it can be known that the second segment identifier in S1301 does not include the first identifier information. Therefore, in order to be able to send the message to the third network device, the first identification information corresponding to the third network device needs to be determined first, so as to restore the original SID of the third network device through the following S1303.

In a possible implementation manner, the implementation process of S1302 may be: the second network device receives a message, the message includes the sixth identification information and the seventh identification information corresponding to the third network device, and the sixth identification information includes the first The identification information, the seventh identification information is used to identify the length of the first identification information; the first network device determines the first identification information based on the sixth identification information and the seventh identification information.

The message may be an IGP message issued by the third network device, and the IGP message is used to advertise the location identifier (locator) of the third network device. The sixth identification information in the foregoing implementation manner is also the location identification of the third network device, and the location identification includes the first identification information (that is, the flocator field). The seventh identification information is used to identify the length of the flocator. Therefore, the second network device can determine, according to the IGP message, to parse the first identification information from the location identification.

That is, in the embodiment of the present application, it is equivalent to an extension of the IGP message issued by the network device. In addition to carrying the location identifier of the corresponding network device, the extended IGP message also carries the length of the flocator field.

In addition, based on the embodiment shown in FIG. 4, it can be known that the location field of the original SID is divided into a flocator field and a vlocator field. Therefore, in a possible implementation manner, in addition to carrying the location identifier of the network device and the length of the flocator field, the extended IGP message may also carry the length of the vlocator field.

FIG. 14 is a schematic diagram of the format of an IGP message provided by an embodiment of the present application. As shown in Figure 14, the IGP message includes a location identification field (locator) and a subtype length value (type-length-value, TLV). The sub-TLV is used to carry a flocator (denoted as the first in Figure 14). The length of the location) field and the length of the vlocator (denoted as the second location in FIG. 14) field. That is, the embodiment of the present application extends a sub-TLV in the existing IGP message, and the flocator field and the vlocator field of the network device are advertised through the sub-TLV.

The third network device may publish the above-mentioned IGP message for advertising the locator based on the IGP protocol, so that other nodes in the same IGP domain can receive the IGP message to learn the flocator field and the vlocator field of the third network device. It should be noted that if the network devices on the message forwarding path are all in the same IGP domain, each network device can use the IGP message to advertise the locator in the domain, and in other possible implementations, the control device can also send the message. To advertise the locator and the length of the corresponding flocator field and/or vlocator field. If the network devices on the packet forwarding path belong to different IGP domains, the control device can also publish an IGP packet for the third network device in the IGP domain, so that other network devices in the IGP domain can learn based on the IGP packet The flocator field and vlocator field of the third network device.

S1303: The second network device generates a first segment identifier corresponding to the third network device based on the first identification information and the second segment identifier.

The second network device generates the first segment identifier corresponding to the third network device, that is, the second network device restores the compressed SID to obtain the original SID of the third network device. The original SID of the third network device is the first segment identifier corresponding to the third network device in S1303.

Based on the implementation of S402 in the embodiment shown in FIG. 4, it can be known that in S1301, the second segment identifier corresponding to the third network device does not include the first identification information in a variety of compression methods. Therefore, in S1303, the implementation manner in which the second network device generates the first segment identifier corresponding to the third network device is related to the compression method of the first segment identifier, and S1303 will be described in detail for different compression methods respectively. I won't expand the explanation here.

S1304: The second network device sends the message to the third network device based on the first segment identifier.

Based on S1303, the first segment identifier is the original SID of the third network device. Therefore, the second network device can use the first segment identifier as the destination address to forward the message, so as to forward the message to the third network device. Internet equipment.

15 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is applied to an intermediate node in an SRv6 network, that is, the second network device in the following embodiment can be any on the forwarding path Intermediate node. The embodiment shown in FIG. 15 is used to explain the process of restoring the segment identifier compressed based on the 32-bit compression method in the embodiment shown in FIG. 6. As shown in Figure 15, the method includes the following processes:

S1501: The second network device receives a message, the message includes a second segment identifier corresponding to the third network device, the second segment identifier only does not include the first identification information, and the first identification information is used to identify the Describe the AS to which the third network device belongs.

Like the embodiment shown in FIG. 13, the second network device may be an intermediate node in the packet forwarding path in the embodiments shown in FIG. 4 to FIG. 12. The third network device is located on the forwarding path of the second network device. The next node after the network device that supports SRv6. For example, the second network device may be the intermediate node R2, and in this case, the third network device may be the intermediate node R3. For another example, the second network device may also be the intermediate node R3, and in this case, the third network device may be the intermediate node R4. The second network device may also be the intermediate node R4, and in this case, the third network device may be the intermediate node R5. Regarding the relationship between the second network device and the third network device, reference may be made to the explanation in the embodiment shown in FIG. 13, which will not be repeated here.

In addition, the implementation manner of S1501 may refer to the implementation manner of S1301 in the embodiment of FIG. 13, which is not repeated here again. In addition, based on the embodiment shown in Figure 6, if the second segment identifier corresponding to the third network device is obtained based on the 32-bit compression method, then the second segment identifier corresponding to the third network device only includes the function in the original SID Field and vlocator field, excluding the flocator field in the original SID.

S1502: The second network device determines first identification information corresponding to the third network device, where the first identification information is used to identify the autonomous domain to which the third network device belongs.

For the implementation of S1502, reference may be made to S1302 in the embodiment of FIG. 13, and details are not described herein again. In a possible implementation manner, since the flocator of each network node on the forwarding path is the same, the information of the flocator may also be stored in each network node in advance for use when restoring the SID.

S1503: The second network device generates a first segment identifier corresponding to the third network device based on the first identification information and the second segment identifier.

Because the second segment identifier in S1501 only does not include the flocator field, but includes the vlocator field and the function field. Therefore, the implementation of S1503 may be that the second network device can directly generate the first segment identifier corresponding to the third network device based on the first identification information and the second segment identifier.

That is, the second segment of the identifier includes the vlocator field and the function field of the original SID of the third network device, and then, for example, the flocator field of the original SID of the third network device is obtained through an IGP message pre-published by the third network device, and the The combination of these three fields can restore the original SID of the third network device, that is, generate the first segment identifier corresponding to the third network device.

S1504: The second network device sends the message to the third network device based on the first segment identifier.

For the implementation of S1504, reference may be made to S1304 in the embodiment of FIG. 3, and the description will not be repeated here again.

For the process of forwarding messages based on 32-bit compression provided in Figure 7, as shown in Figure 7, the SID list included in the SRH in the message sent by the head node R1 to the intermediate node R2 is: <5:8001, 4: 0, 3:6, 2:0>. When the intermediate node R2 receives the message, it determines that the flocator field of the intermediate node R3 is A according to the IGP message pre-published by the intermediate node R3 or the message pre-sent by the control device, and then according to the SID list corresponding to the intermediate node R3 After the compressed 3:6, the original SID of the intermediate node R3 is restored to A:3:6, so that the determined original SID A:3:6 is subsequently used as the destination address DA of the next hop to forward the message.

When the intermediate node R3 receives the message, it determines that the flocator field of the intermediate node R4 is A according to the IGP message issued by the intermediate node R4 or the message sent in advance by the control device, and then according to the compression corresponding to the intermediate node R4 in the SID list After 4:0, the original SID of the intermediate node R4 is restored to A:4:0, so that the determined original SID A:4:0 will be used as the destination address DA to forward the message.

When the intermediate node R4 receives the message, according to the IGP message issued by the tail node R5 or the control device or the message sent in advance by the control device, the flocator field of the tail node R5 is determined to be A, and then according to the SID list and the tail node R5 Corresponding to the compressed 5:8001, the original SID of the tail node R5 is restored to A:5:8001, so that the determined original SID A:5:8001 is subsequently used as the destination address DA to forward the message.

The above described SID restoration process based on FIG. 7 is only a possible example, and the above restoration method can also be applied to SID restoration of network nodes on other forwarding paths. For example, in a possible situation, the forwarding path may be a loose display path, that is, the path includes one or more forwarding nodes that are only used for transparent transmission of packets. In this case, only network nodes that support the SR protocol may be Perform the SID restore operation. Or, in another possible situation, the head node does not compress the SID of the next hop network node supporting the SR protocol, but directly uses the original SID of the next hop network node as the next hop destination address, etc., At this time, even if the next-hop network node supports the SR protocol, there is no need to perform a compression and restoration operation.

FIG. 16 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is applied to an intermediate node in an SRv6-based network, that is, the second network device in the following embodiment is any one on the forwarding path Intermediate node. The embodiment shown in FIG. 16 is used to explain the process of restoring the segment identifier compressed based on the 16-bit compression method in the embodiment shown in FIG. 8. As shown in Figure 16, the method includes the following processes:

S1601: The second network device receives a message, the message includes a second segment identifier corresponding to the third network device, and the second segment identifier does not include the first identification information and the second identification information at the same time, and the first identifier The information is used to identify the AS to which the third network device belongs, and the second identification information is used to identify the third network device.

Like the embodiment shown in FIG. 13, the second network device may be an intermediate node in the packet forwarding path in the embodiments shown in FIG. 4 to FIG. 12, and the third network device is on the forwarding path and is located in the first The next node after the second network device that supports SRv6. For example, the second network device may be the intermediate node R2, and in this case, the third network device may be the intermediate node R3. For another example, the second network device may also be the intermediate node R3, and in this case, the third network device may be the intermediate node R4. For another example, the second network device may also be the intermediate node R4, and in this case, the third network device may be the intermediate node R5. Regarding the relationship between the second network device and the third network device, reference may be made to the explanation in the embodiment shown in FIG. 13, which will not be repeated here.

In addition, the implementation manner of S1601 may refer to the implementation manner of S1301 in the embodiment of FIG. 13, and details are not described herein again. In addition, based on the embodiment shown in FIG. 8, if the second segment identifier corresponding to the third network device is obtained based on the 16-bit compression method, then the second segment identifier corresponding to the third network device only includes the function in the original SID Field, excluding the flocator field and vlocator field in the original SID.

S1602: The second network device determines first identification information and second identification information corresponding to the third network device.

Based on S1601, it can be known that the second segment identifier corresponding to the third network device not only does not include the flocator field, but also does not include the vlocator field, but only includes the function field. Therefore, in addition to determining the first identification information, the first network device also needs to determine the second identification information, which is used to identify the second network device in the autonomous domain (that is, the vlocator field).

The implementation manner for the second network device to determine the second identification information of the third network device may refer to the implementation manner for the second network device to determine the first identification information of the third network device in the embodiment shown in FIG. 13. That is, the second identification information can also be determined through an IGP message, or the control device sends a message to inform the third network device of the content of the second identification information.

S1603: The second network device generates a first segment identifier corresponding to the third network device based on the first identification information, the second identification information, and the second segment identifier.

Specifically, the second segment of the identifier includes the function field of the original SID of the third network device, and then the flocator field and the flocator field of the original SID of the third network device are obtained through the IGP message issued by the third network device or the message sent by the control device The vlocator field, combining these three fields can restore the original SID of the third network device, that is, to generate the first segment identifier corresponding to the third network device.

S1604: The second network device sends the message to the third network device based on the first segment identifier.

For the implementation of S1604, reference may be made to S1304 in the embodiment of FIG. 3, which will not be described again here.

For the process of forwarding packets based on 16-bit compression provided in Figure 9, as shown in Figure 9, the SID list included in the SRH in the message sent by the head node R1 to the intermediate node R2 is: <8001, 1, 6, 5>. When the intermediate node R2 receives the message, according to the IGP message issued by the intermediate node R3 or the message sent by the control device, it is determined that the flocator field of the intermediate node R3 is A and the vlocator field is 3, and then according to the SID list and the intermediate node The compressed 6 corresponding to R3 restores the original SID of the intermediate node R3 as A:3:6, so that the determined original SID A:3:6 is subsequently used as the destination address DA to forward the message.

When the intermediate node R3 receives the message, according to the IGP message issued by the intermediate node R4 or the message sent by the control device, it is determined that the flocator field of the intermediate node R4 is A and the vlocator field is 4, and then according to the SID list and the intermediate node The compressed 0 corresponding to R4 restores the original SID of the intermediate node R4 to A:4:0, so that the determined original SID A:4:0 is subsequently used as the destination address DA to forward the message.

When the intermediate node R4 receives the message, according to the IGP message issued by the tail node R5 or the message sent by the control device, the flocator field of the tail node R5 is determined to be A, and then according to the compression corresponding to the tail node R5 in the SID list After 5:8001, the original SID of the tail node R5 is restored to A:5:8001, so that the determined original SID A:5:8001 is used as the destination address DA to forward the message.

The above described SID restoration process based on FIG. 9 is only a possible example, and the above restoration method can also be applied to SID restoration of network nodes on other forwarding paths. For other possible situations, reference may be made to the explanations in the embodiment shown in FIG. 15, which will not be repeated here.

FIG. 17 is a flowchart of a method for determining a segment identifier provided by an embodiment of the present application, which is applied to an intermediate node in an SRv6-based network, that is, the first network device in the following embodiment may be any device on the forwarding path. An intermediate node. The embodiment shown in FIG. 17 is used to explain the process of restoring the segment identifier after compression based on the 20-bit compression method shown in FIG. 10. As shown in Figure 17, the method includes the following processes:

S1701: The second network device receives a packet. The packet includes a second segment of identifiers corresponding to multiple consecutive network devices on the forwarding path. The second segment of identifiers includes third identification information and fourth identification information. A continuous network device corresponds to multiple segment identifiers, the second network device is located in the first of the multiple continuous network devices on the forwarding path, and the multiple segment identifiers include the same third identification information. Four identification information uses the number of these multiple consecutive network devices.

Like the embodiment shown in FIG. 13, the second network device may be an intermediate node in the packet forwarding path in the embodiments shown in FIG. 4 to FIG. 12. Based on the embodiment shown in Figure 10, the application scenario of the 20-bit compression scheme is that the function fields of multiple network devices on the forwarding path are the same. Therefore, at this time, the forwarding path includes multiple consecutive network devices. The network device corresponding to multiple segment identifiers, the first network device is located in the first of the multiple consecutive network devices on the forwarding path, and the multiple segment identifiers include the same third identification information (that is, the function field ). For example, the second network device may be any one of node R2, node R3, or the like. The multiple consecutive network devices may be nodes on the forwarding path that are located behind the second network device and support SRv6 and have the same function field as the function field of the second network device.

For the implementation manner of S1701, reference may be made to the implementation manner of S1301 in the embodiment of FIG. 13, and details are not described herein again. In addition, based on the embodiment shown in FIG. 10, it can be known that when the function fields of multiple network devices are the same, the original SID of each node can be compressed through a 20-bit compression method. At this time, the second segment of identification in S1701 includes third identification information and fourth identification information. The third identification information is used to indicate the same function field, and the fourth identification information is used to indicate that the packet forwarding path of the current node is left. The number of network devices with the same function field below. That is, if the second segment identifiers corresponding to multiple network devices are obtained based on 20-bit compression, then the second segment identifier in S1701 only includes the same function field and the identifier used to indicate network devices with the same function field. The quantity information does not include the flocator field and vlocator field in the original SID. In other possible implementations, the second segment of identification may include the same function field and information used to indicate the number of network devices with the same function field, and include the flocator field in the original SID, but not the original SID Or the second segment of identification may include the same function field and information used to indicate the number of network devices with the same function field, and include the vlocator field in the original SID, but not the original SID flocator field.

At this time, for the third network device that is the next hop of the second network device among the multiple network devices, the second network device is equivalent to knowing the function field of the third network device through the second segment identifier. Therefore, the second network device The device can determine the first segment identifier corresponding to the third network device in the implementation manner in the embodiment shown in FIG. 15, that is, generate the first segment identifier corresponding to the third network device through the following S1702 and S1703, so as to facilitate The message is sent according to the first segment identifier through the following S1704.

S1702: For the third network device that is the next hop of the second network device among the plurality of network devices, the second network device determines the first identification information and the second identification information corresponding to the third network device, so The first identification information is used to identify the autonomous domain to which the third network device belongs, and the second identification information is used to identify the third network device in the autonomous domain.

As shown in FIG. 3, the second network device may be the intermediate node R2, and the third network device may be the intermediate node R3 in this case. The second network device may also be an intermediate node R3, and in this case, the third network device may be an intermediate node R4.

S1703: The second network device generates a first segment identifier corresponding to the third network device based on the first identification information, the second identification information, and the second segment identifier.

S1704: The second network device sends the message to the third network device based on the first segment identifier.

The implementation manners of S1702, S1703, and S1704 may refer to the implementation manners of S1502, S1503, and S1504 in the embodiment of FIG. 15 respectively, and the description is not repeated here.

In addition, since the second segment of identification is achieved by compressing the original SIDs of multiple network devices with the same function field through the third identification information and the fourth identification information, in order to facilitate subsequent nodes to determine whether the next hop node is still this One of the multiple network devices, the second network device needs to update the fourth identification information before sending the message to the third network device. In a possible implementation manner, the second network device may determine the fifth identification information based on the fourth identification information; determine the updated first-segment identification, and the updated first-segment identification includes the third identification information and the fifth identification information. Identification information; the second network device sends the message to the second network device based on the second segment identifier, and the message includes the updated first segment identifier.

Specifically, the fourth identification information may be a first value, the fifth identification information may be a second value, and the second value may be the first value minus one. That is, the fourth identification information is updated to advertise the remaining number of network devices with the same function field in the next hop node. When the next hop node receives the updated fourth identification information, if the value indicated by the updated fourth identification information is greater than 1, it continues to determine the destination address of the message in the above-mentioned manner. If the value indicated by the updated fourth identification information is 1, other information in the SID list needs to be used to determine the compression mode of the SID of the next hop node to determine the destination address of the message.

For the process of forwarding messages based on 20-bit compression provided in Figure 11, as shown in Figure 11, the SID list included in the SRH in the message sent by the head node R1 to the intermediate node R2 is: <5:8001, 5060: 3>. When the intermediate node R2 receives the message, it determines that the flocator field of the intermediate node R3 is A and the vlocator field is 3, and then restores the original SID of the intermediate node R3 according to the compressed 5060 corresponding to the intermediate node R3 in the SID list It is A:3:5060, and the 5060:3 in the message is updated to 5060:2, which is used to indicate that there are two network devices with a function field of 5060 on the message forwarding path. R2 uses the determined original SID A:3:5060 as the destination address DA to forward the message.

When the intermediate node R3 receives the message, it determines that the flocator field of the intermediate node R4 is A and the vlocator field is 4, and then restores the original SID of the intermediate node R4 according to the compressed 5060 corresponding to the intermediate node R4 in the SID list It is A:4:5060, and the 5060:2 in the message is updated to 5060:1, which is used to indicate that there is a network device with a function field of 5060 on the message forwarding path. R3 uses the determined original SID A:4:5060 as the destination address DA to forward the message.

When the intermediate node R4 receives the message, because 5060:1 in the message indicates that there is only one network device with a function field of 5060, and this network device is the intermediate node R4, the intermediate node R4 needs to determine the tail node's The compression method of R5, after determining that the compression method of the tail node is 32-bit compression, according to the IGP message issued by the tail node R5 or the message sent by the control device, the flocator field of the tail node R5 is determined to be A, and then according to the SID list The compressed 5:8001 corresponding to the tail node R5, the original SID of the tail node R5 is restored to A:5:8001, and then the determined original SID A:5:8001 is used as the destination address DA to forward the message.

Similarly, the SID restoration process described above based on FIG. 11 is only used as a possible example, and the above restoration method can also be applied to SID restoration of network nodes on other forwarding paths. For other possible situations, reference may be made to the explanations in the embodiment shown in FIG. 15, which will not be repeated here.

Based on the three different ways of restoring the original SID in Figures 14 to 17, it can be seen that in different compression schemes, the second network device determines the first segment identifier corresponding to the third network device in different ways. Therefore, the second network device Before restoring the first segment identifier corresponding to the third network device based on the second segment identifier, it is necessary to determine the compression scheme included in the received message corresponding to the second segment identifier of the third network device.

In a possible implementation manner, based on the embodiment shown in FIG. 12, it can be known that the received message also carries identification information for identifying the compression scheme of the second segment identification corresponding to the third network device. For ease of description, this identification information is called compression strategy identification information (that is, identification information in the embodiment shown in FIG. 12). Therefore, the first network device may first determine the second segment according to the compression strategy identification information. Identify the corresponding compression scheme, and then restore the first segment identifier corresponding to the third network device through the corresponding embodiments in FIGS. 14 to 16 according to the determined compression scheme.

In a possible implementation manner, as shown in FIG. 12, it is assumed that the compression strategy identification information is carried in a TLV in the SRH. At this time, when the first network device receives the message, it can parse the TLV and determine the compression scheme of the third network device according to the TLV. The compression scheme of each SID indicated in the TLV has been described in detail in the embodiment shown in FIG. 12. The first network device only needs to analyze the compression scheme of the third network device according to the embodiment shown in FIG. 12 .

Next, the structure of any network device in the SRv6 network provided in the embodiment of the present application will be explained.

FIG. 18 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device may be any one of multiple nodes in the packet forwarding path in the SRv6 network in any of the foregoing embodiments. The network device 1800 may be a switch, a router, or other network device that forwards packets. In this embodiment, the network device 1800 includes: a main control board 1810, an interface board 1830, and an interface board 1840. In the case of multiple interface boards, a switching network board (not shown in the figure) may be included, and the switching network board is used to complete data exchange between various interface boards (interface boards are also called line cards or service boards).

The main control board 1810 is used to complete functions such as system management, equipment maintenance, and protocol processing. The interface boards 1830 and 1840 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and implement message forwarding. There are mainly three types of functional units on the main control board 1810: system management control unit, system clock unit, and system maintenance unit. The main control board 1810, the interface board 1830, and the interface board 1840 are connected to the system backplane through a system bus to achieve intercommunication. The interface board 1830 includes one or more processors 1831. The processor 1831 is used for controlling and managing the interface board, communicating with the central processing unit on the main control board, and for forwarding processing of messages. The memory 1832 on the interface board 1830 is used to store forwarding entries, and the processor 1831 forwards the message by looking up the forwarding entries stored in the memory 1832.

The interface board 1830 includes one or more network interfaces 1833 for receiving the message sent by the previous hop node, and sending the processed message to the next hop network node according to the instruction of the processor 1831. The specific implementation process will not be repeated here one by one. The specific functions of the processor 1831 are also not repeated here one by one.

It can be understood that, as shown in FIG. 18, this embodiment includes multiple interface boards and adopts a distributed forwarding mechanism. Under this mechanism, the operation on the interface board 1840 is basically similar to that of the interface board 1830. For the sake of brevity ,No longer. In addition, it can be understood that the processor 1831 and/or 1841 in the interface board 1830 in FIG. 18 may be dedicated hardware or chips, such as a network processor or an application specific integrated circuit (application specific integrated circuit) to implement the above functions. One way to achieve this is the so-called forwarding plane using dedicated hardware or chip processing. For a specific implementation manner using a dedicated hardware or chip of a network processor, reference may be made to the embodiment shown in FIG. 19 below. In another implementation manner, the processor 1831 and/or 1841 may also adopt a general-purpose processor, such as a general-purpose CPU, to implement the functions described above.

In addition, it should be noted that there may be one or more main control boards, and when there are more than one, it may include a main main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the device, the more interface boards provided. In the case of multiple interface boards, the multiple interface boards can communicate with each other through one or more switching network boards, and when there are more than one, the load sharing and redundant backup can be realized together. Under the centralized forwarding architecture, the device does not need to switch the network board, and the interface board undertakes the processing function of the business data of the entire system. Under the distributed forwarding architecture, the device includes multiple interface boards, which can realize data exchange between multiple interface boards through the switching network board, and provide large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network equipment with a distributed architecture are greater than those with a centralized architecture. The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

In a specific embodiment, the memory 1832 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM), or can store Other types of dynamic storage devices for information and instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only Memory, CD-ROM, or Other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures And any other media that can be accessed by the computer, but not limited to this. The memory 1832 may exist independently, and is connected to the processor 1831 through a communication bus. The memory 1832 may also be integrated with the processor 1831.

The memory 1832 is used to store program codes, and is controlled by the processor 1831 to execute, so as to execute the path detection method provided in the foregoing embodiments. The processor 1831 is configured to execute the program code stored in the memory 1832. One or more software modules can be included in the program code. The one or more software modules may be the software modules provided in any of the following embodiments in FIG. 21 or FIG. 22.

In a specific embodiment, the network interface 1833 may be any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network RAN, and wireless local area network (wireless local area network). local area networks, WLAN), etc.

FIG. 19 is a schematic structural diagram of another network device provided by an embodiment of the present application. The network device may be any one of the multiple nodes in the SRv6 network provided in any embodiment of the above figure. The network device 1900 may be a switch, a router, or other network device that forwards packets. In this embodiment, the network device 1900 includes: a main control board 1910, an interface board 1930, a switching network board 1920, and an interface board 1940. The main control board 1910 is used to complete functions such as system management, equipment maintenance, and protocol processing. The switching network board 1920 is used to complete data exchange between various interface boards (interface boards are also called line cards or service boards). The interface boards 1930 and 1940 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.) and implement data packet forwarding. The control plane is composed of the management and control units of the main control board 1910 and the management and control units on the interface boards 1930 and 1940. There are mainly three types of functional units on the main control board 1910: a system management control unit, a system clock unit, and a system maintenance unit. The main control board 1910, the interface boards 1930 and 1940, and the switching network board 1920 are connected to the system backplane through the system bus to achieve intercommunication. The central processing unit 1931 on the interface board 1930 is used to control and manage the interface board and communicate with the central processing unit on the main control board. The forwarding entry memory 1934 on the interface board 1930 is used to store forwarding entries, and the network processor 1932 forwards the message by searching for the forwarding entries stored in the forwarding entry memory 1934.

The physical interface card 1933 of the interface board 1930 is used to receive the message sent by the previous hop node. The specific implementation process will not be repeated here one by one.

The specific functions of the network processor 1932 will not be repeated here.

Then, the processed message is sent to the next hop node of the first node through the physical interface card 1933. The specific implementation process will not be repeated here one by one.

It can be understood that, as shown in FIG. 19, this embodiment includes multiple interface boards and adopts a distributed forwarding mechanism. Under this mechanism, the operation on the interface board 1940 is basically similar to the operation of the interface board 1930. For the sake of brevity ,No longer. In addition, as described above, the functions of the

network processors

1932 and 1942 in FIG. 19 can be implemented by replacing application specific integrated circuits.

In addition, it should be noted that there may be one or more main control boards, and when there are more than one, it may include a main main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the device, the more interface boards provided. There may also be one or more physical interface cards on the interface board. The switching network board may not exist, or there may be one or more. When there are more than one, the load sharing and redundant backup can be realized together. Under the centralized forwarding architecture, the device does not need to switch the network board, and the interface board undertakes the processing function of the business data of the entire system. Under the distributed forwarding architecture, the device can have at least one switching network board, and data exchange between multiple interface boards can be realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network equipment with a distributed architecture are greater than those with a centralized architecture. The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

FIG. 20 is a schematic structural diagram of the interface board 2000 in the network device shown in FIG. 19 provided by an embodiment of the present application. The network device where the interface board 2000 is located may be included in the packet forwarding path in any of the foregoing embodiments. Any one of multiple nodes. The interface board 2000 may include a physical interface card (PIC) 2030, a network processor (NP) 2020, and a traffic management module (traffic management) 2020.

Among them, PIC: physical interface card (physical interface card), used to realize the docking function of the physical layer, the original traffic enters the interface board of the network device from this, and the processed message is sent from the PIC card.

The network processor NP2020 is used to implement message forwarding processing. Specifically, the processing of upstream packets includes: packet inbound interface processing, upstream classification, forwarding table lookup; downstream packet processing: forwarding table lookup, downstream flow classification, outgoing interface processing, and so on.

Traffic ManagementTM is used to implement functions such as Quality of Service (QoS), wire-speed forwarding, large-capacity buffering, and queue management. Specifically, upstream traffic management includes: upstream QoS processing (such as congestion management and queue scheduling, etc.) and slicing processing; downstream traffic management includes: packet processing, multicast replication, and downstream QoS processing (such as congestion management and queue scheduling, etc.) ).

It is understandable that if the network device has multiple interface boards 2000, the multiple interface boards 2000 can communicate through the switching network 2040.

It should be noted that FIG. 20 only shows a schematic processing flow or module inside the NP, and the processing sequence of each module in a specific implementation is not limited to this, and other modules or processing flows can be deployed as needed in practical applications. The comparison of the embodiments of this application is not limited.

FIG. 21 is a schematic diagram of a first network device provided by an embodiment of the present application, which is applied to a network supporting the SRv6 protocol. The SRv6 network includes at least a plurality of network devices supporting the SRv6 protocol. In a possible implementation manner, the SRv6 network may also include one or more other network devices that do not support the SRv6 protocol. The first network device may be, for example, R1 shown in FIG. 3, and may be the first network device used to implement any of the methods provided in FIG. 4, FIG. 6, FIG. 8, and FIG. 10, etc. As shown in FIG. 21, the first network device 2100 includes:

The determining module 2101 is configured to determine a first segment identifier corresponding to a second network device, where the first segment identifier includes first identification information, and the first identification information is used to identify the autonomous domain to which the second network device belongs . For specific implementation manners, reference may be made to S401 in the embodiment of FIG. 4, S601 in the embodiment of FIG. 6, S801 in the embodiment of FIG. 8, and S1001 in the embodiment of FIG. 10.

The generating module 2102 is configured to generate a second segment identifier based on the first segment identifier, where the second segment identifier does not include the first identifier information. For a specific implementation manner, reference may be made to S402 in the embodiment of FIG. 4, S602 in the embodiment of FIG. 6, S802 in the embodiment of FIG. 8, and S1002 in the embodiment of FIG. 10.

The sending module 2103 is configured to send a message to the second network device, where the message includes the second segment identifier. For specific implementation manners, reference may be made to S403 in the embodiment of FIG. 4, S603 in the embodiment of FIG. 6, S803 in the embodiment of FIG. 8, and S1003 in the embodiment of FIG. 10.

Optionally, the determining module 2101 is further configured to determine a third segment identifier corresponding to a third network device, where the third segment identifier includes second identification information and third identification information, and the second identification information is used to identify The autonomous domain to which the third network device belongs, and the third identification information is used to identify the third network device in the autonomous domain;

The generating module 2102 is further configured to generate the fourth segment identifier based on the third segment identifier, where the fourth segment identifier does not include the second identification information and the third identification information;

The sending module 2103 is further configured to send the message to the third network device, where the message includes the fourth segment identifier.

Optionally, the determining module 2101 is further configured to determine multiple segment identifiers corresponding to multiple network devices, where the multiple segment identifiers respectively include the same fourth identification information;

The generating module 2102 is further configured to generate a fifth segment identifier based on the multiple segment identifiers, where the fifth segment identifier includes the fourth identifier information and fifth identifier information, and the fifth identifier information is used to identify the The number of multiple network devices;

The sending module 2103 is further configured to send the message, and the message includes the fifth segment identifier.

Optionally, the multiple network devices include a second network device, and the second segment identifier and the fifth segment identifier are the same segment identifier.

Optionally, the determining module 2101 determining multiple segment identifiers corresponding to multiple network devices includes:

The determining module determines the multiple segment identifiers corresponding to the multiple network devices based on the internal gateway protocol IGP messages sent by the multiple network devices respectively; or, the determining module determines the multiple segments based on the control message sent by the control device. Multiple segment identifiers corresponding to each network device.

It should be noted that when the first network device provided in the above embodiment determines the segment identifier, only the division of the above functional modules is used as an example for illustration. In actual applications, the above functions can be allocated by different functional modules according to needs. , Divide the internal structure of the device into different functional modules to complete all or part of the functions described above. In addition, the first network device and the method embodiment for determining the segment identifier provided in the above-mentioned embodiment belong to the same concept. For the specific implementation process, please refer to the method embodiment for details, which will not be repeated here.

FIG. 22 is a schematic diagram of another first network device provided by an embodiment of the present application, which is applied to an SRv6 network, and the SRv6 network includes at least a plurality of network devices supporting the SRv6 protocol. In a possible implementation manner, the SRv6 network may also include one or more other network devices that do not support the SRv6 protocol. The first network device may be, for example, any intermediate node R2, R3, or R4 shown in FIG. 3, and may be used to implement the second network in any of the methods provided in FIG. 13, FIG. 15, FIG. 16, and FIG. Equipment, etc. As shown in FIG. 22, the first network device 2200 includes:

The receiving module 2201 is configured to receive a message, the message including a first segment identifier corresponding to the second network device. For specific implementations, refer to S1301 in the embodiment of FIG. 13, S1501 in the embodiment of FIG. 15, S1601 in the embodiment of FIG. 16, and S1701 in the embodiment of FIG. 17.

The determining module 2202 is configured to determine first identification information corresponding to the second network device, where the first identification information is used to identify the autonomous domain to which the second network device belongs. For a specific implementation manner, reference may be made to S1302 in the embodiment of FIG. 13, S1502 in the embodiment of FIG. 15, S1602 in the embodiment of FIG. 16, and S1702 in the embodiment of FIG. 17.

The generating module 2203 is configured to generate a second segment identifier corresponding to the second network device based on the first identifier information and the first segment identifier. For specific implementations, refer to S1303 in the embodiment of FIG. 13, S1503 in the embodiment of FIG. 15, S1603 in the embodiment of FIG. 16, and S1703 in the embodiment of FIG. 17.

The sending module 2204 is configured to send the message to the second network device based on the second segment identifier. For specific implementations, refer to S1304 in the embodiment of FIG. 13, S1504 in the embodiment of FIG. 15, S1604 in the embodiment of FIG. 16, and S1704 in the embodiment of FIG. 17.

Optionally, the second network device is a next hop device,

The determining module 2202 is further configured to determine second identification information, where the second identification information is used to identify the second network device in the autonomous domain;

The generating module 2203 is further configured to generate the second segment identifier corresponding to the second network device based on the first identification information, the second identification information, and the first segment identifier.

Optionally, the forwarding path of the message includes multiple consecutive network devices, the multiple consecutive network devices correspond to multiple segment identifiers, and the first network device is located in the multiple consecutive network devices on the forwarding path The first one, the multiple segment identifiers include the same third identifier information, the first segment identifier includes the third identifier information and the fourth identifier information, and the fourth identifier information is used to indicate the number of the multiple consecutive network devices ；

The sending module 2204 includes:

The first determining subunit is configured to determine fifth identification information based on the fourth identification information;

The second determining subunit is configured to determine the updated first segment identifier, where the updated first segment identifier includes the third identification information and the fifth identification information;

The sending subunit is configured to send the message to the second network device based on the second segment identifier, where the message includes the updated first segment identifier.

Optionally, the fourth identification information is the first value, the fifth identification information is the second value, and the second value is the first value minus one.

Optionally, the determining module 2202 includes:

The receiving subunit is configured to receive a message, the message including sixth identification information and seventh identification information corresponding to the second network device, the sixth identification information including the first identification information, and the seventh identification information. The identification information is used to identify the length of the first identification information;

The third determining subunit is configured to determine the first identification information based on the sixth identification information and the seventh identification information.

It should be noted that the foregoing embodiment provides that when the first network device determines the segment identifier, only the division of the foregoing functional modules is used as an example for illustration. In actual applications, the foregoing function allocation can be completed by different functional modules as required. That is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the foregoing embodiment provides the same conception of the method for determining the first network device and the segment identifier. For the specific implementation process, refer to the method embodiment, which will not be repeated here.

In addition, an embodiment of the present application also provides a network system, which includes a first network device, a second network device, and a third network device. The first network device is used to determine the network device corresponding to the second network device. The first segment identifier, the first segment identifier includes first identification information, the first identification information is used to identify the autonomous domain to which the second network device belongs, and the first network device is based on the first segment identifier Generating a second segment identifier, the second segment identifier does not include the first identification information, the first network device sends a message to a third network device, and the message includes the second segment identifier; The third network device is configured to receive a message, the message including the second segment identifier corresponding to the second network device, and the third network device determines the First identification information, where the first identification information is used to identify the autonomous domain to which the second network device belongs, and the third network device generates a connection with the first identification information based on the first identification information and the first segment identification The first segment identifier corresponding to the second network device, and the third network device sends the message to the second network device based on the first segment identifier.

The first network device in the network system may be, for example, R1 shown in FIG. 3, which is used to implement the first network device in any of the methods provided in FIG. 4, FIG. 6, FIG. 8, and FIG. Other possible methods executed by R1 mentioned in the foregoing embodiment of this application.

The second network device in the network system may be R2, R3, and/or R4 shown in FIG. 3, which is used to implement the second network device in any of the methods provided in FIG. 13, FIG. 15, FIG. 16, and FIG. It can also be used in other possible methods performed by R2, R3, and/or R4 mentioned in the foregoing embodiments of this application.

The specific functions of the first network device, the second network device, and the third network device in the network system have been described in detail in the above method embodiment, and will not be repeated here.

FIG. 23 is a schematic structural diagram of a network device provided by an embodiment of the present invention. Any network device in the foregoing embodiment may be implemented by the network device 2300 shown in FIG. 23. In this case, the network device 2300 may be a switch, a router, or other network device that forwards packets. In addition, the control device in the foregoing embodiment can also be implemented by the network device 2300 shown in FIG. 23. At this time, the specific functions of the network device 2300 can refer to the specific implementation of the control device in the foregoing embodiment, which will not be repeated here. Go into details. Referring to FIG. 23, the network device includes at least one processor 2301, a communication bus 2302, a memory 2303, and at least one communication interface 2304.

The processor 2301 may be a general-purpose central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling program execution of the solution of the present application.

The communication bus 2302 may include a path for transferring information between the above-mentioned components.

The memory 2303 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions The dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only Memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer Any other media, but not limited to this. The memory 2303 may exist independently, and is connected to the processor 2301 through a communication bus 2302. The memory 2303 may also be integrated with the processor 2301.

Among them, the memory 2303 is used to store the program code for executing the solution of the present application, and the processor 2301 controls the execution. The processor 2301 is configured to execute the program code stored in the memory 2303. One or more software modules can be included in the program code. The control node or any one of the multiple nodes in the embodiment of FIG. 4 can determine the data used to develop the application through the processor 2301 and one or more software modules in the program code in the memory 2303. The one or more software modules may be the software modules provided in any embodiment of FIG. 21 or FIG. 22.

The communication interface 2304 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network RAN, wireless local area networks (WLAN), and so on.

In a specific implementation, as an embodiment, the network device may include multiple processors, for example, the processor 2301 and the processor 2305 shown in FIG. 23. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).

The aforementioned network device may be a general network device or a dedicated network device. In a specific implementation, the network device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device. The embodiments of this application do not limit the type of network equipment.

It can be understood that the network device shown in FIG. 23 is a node that can be any of the foregoing method embodiments. In addition, any node involved in the embodiments of the present application may also be a virtual node implemented based on a general physical server combined with network function virtualization NFV technology. The virtual node may be a virtual router. The virtual node may be a virtual machine (English: Virtual Machine, VM) running a program for providing a message sending function, and the virtual machine is deployed on a hardware device (for example, a physical server). A virtual machine refers to a complete computer system with complete hardware system functions that is simulated by software and runs in a completely isolated environment. Those skilled in the art can combine NFV technology to virtualize multiple nodes with the above-mentioned functions on a general physical server by reading this application. I won't repeat them here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (for example: coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example: infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)) )Wait.

Those of ordinary skill in the art can understand that all or part of the process of implementing the above-mentioned embodiments can be completed by hardware, or by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The storage medium mentioned can be a read-only memory, a magnetic disk or an optical disk, etc.

The above-mentioned examples provided for this application are not intended to limit this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection scope of this application. Inside.

Claims

A method for determining a segment identifier, characterized in that the method includes:

The first network device determines a first segment identifier corresponding to the second network device, where the first segment identifier includes first identification information, and the first identification information is used to identify the autonomous domain to which the second network device belongs;

Generating, by the first network device, a second segment identifier based on the first segment identifier, the second segment identifier does not include the first identification information;

The first network device sends a message to the second network device, and the message includes the second segment identifier.
The method of claim 1, wherein the method further comprises:

The first network device determines a third segment identifier corresponding to the third network device, the third segment identifier includes second identification information and third identification information, and the second identification information is used to identify the third network The autonomous domain to which the device belongs, where the third identification information is used to identify the third network device in the autonomous domain;

Generating, by the first network device, the fourth segment identifier based on the third segment identifier, the fourth segment identifier does not include the second identification information and the third identification information;

The first network device sends the message to the third network device, and the message includes the fourth segment identifier.
The method according to claim 2, wherein the second network device and the third network device are the same device, the first identification information and the second identification information are the same identification information, and the second The segment identifier and the fourth segment identifier are the same segment identifier.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The first network device determines multiple segment identifiers corresponding to the multiple network devices, and the multiple segment identifiers respectively include the same fourth identification information;

The first network device generates a fifth segment identifier based on the plurality of segment identifiers, where the fifth segment identifier includes the fourth identification information and fifth identification information, and the fifth identification information is used to identify the multiple The number of network devices;

The first network device sends the message, and the message includes the fifth segment identifier.
The method according to claim 4, wherein the fifth segment of identification does not include the first identification information and sixth identification information respectively corresponding to the plurality of network devices, and the sixth identification information respectively It is used to uniquely identify the multiple network devices in the autonomous domain to which the multiple network devices belong.
The method according to claim 4 or 5, wherein the multiple network devices include a second network device, and the second segment identifier and the fifth segment identifier are the same segment identifier.
The method according to any one of claims 1 to 6, wherein the message further includes seventh identification information, and the seventh identification information is used to identify that the first network device generates the second segment Identify the strategy.
The method according to any one of claims 4 to 7, wherein the first network device determines that the multiple segment identifiers corresponding to the multiple network devices are:

The first network device determines multiple segment identifiers corresponding to the multiple network devices based on the interior gateway protocol IGP messages sent by the multiple network devices respectively; or,

The first network device determines multiple segment identifiers corresponding to the multiple network devices based on the control message sent by the control device.
A method for determining a segment identifier, characterized in that the method includes:

The first network device receives a message, where the message includes a first segment identifier corresponding to the second network device;

Determining, by the first network device, first identification information corresponding to the second network device, where the first identification information is used to identify the autonomous domain to which the second network device belongs;

Generating, by the first network device, a second segment identifier corresponding to the second network device based on the first identification information and the first segment identifier;

The first network device sends the message to the second network device based on the second segment identifier.
The method according to claim 9, wherein the second network device is a next hop device of the first network device, and the method comprises:

Determining second identification information by the first network device, where the second identification information is used to identify the second network device in the autonomous domain;

The first network device generates a second segment identifier corresponding to the second network device based on the first identification information and the first segment identifier, specifically:

The first network device generates the second segment identifier corresponding to the second network device based on the first identification information, the second identification information, and the first segment identifier.
The method according to claim 9 or 10, wherein the forwarding path of the message includes multiple consecutive network devices, and the multiple consecutive network devices correspond to multiple segment identifiers, and the first The network device is located at the first of the plurality of consecutive network devices on the forwarding path, the plurality of segment identifiers include the same third identification information, and the first segment identifier includes the third identification information and Fourth identification information, where the fourth identification information is used to indicate the number of the multiple consecutive network devices, and the first network device sends the message to the second network device based on the second segment identifier ,include:

Determining, by the first network device, fifth identification information based on the fourth identification information;

Determining, by the first network device, an updated first segment identifier, where the updated first segment identifier includes the third identification information and the fifth identification information;

The first network device sends the message to the second network device based on the second segment identifier, and the message includes the updated first segment identifier.
The method of claim 11, wherein the fourth identification information is a first value, the fifth identification information is a second value, and the second value is the first value minus one.
According to the method according to any one of claims 9 to 12, the first network device determining the first identification information corresponding to the second network device includes:

The first network device receives a message, the message includes sixth identification information and seventh identification information corresponding to the second network device, the sixth identification information includes the first identification information, and the seventh identification information The identification information is used to identify the length of the first identification information;

The first network device determines the first identification information based on the sixth identification information and the seventh identification information.
A first network device, characterized in that, the first network device includes:

A determining module, configured to determine a first segment identifier corresponding to a second network device, where the first segment identifier includes first identification information, and the first identification information is used to identify the autonomous domain to which the second network device belongs;

A generating module, configured to generate a second segment identifier based on the first segment identifier, where the second segment identifier does not include the first identifier information;

The sending module is configured to send a message to the second network device, where the message includes the second segment identifier.
The device according to claim 14, wherein:

The determining module is further configured to determine a third segment identifier corresponding to a third network device, where the third segment identifier includes second identification information and third identification information, and the second identification information is used to identify the second identification information. 3. The autonomous domain to which the network device belongs, where the third identification information is used to identify the third network device in the autonomous domain;

The generating module is further configured to generate the fourth segment identifier based on the third segment identifier, where the fourth segment identifier does not include the second identification information and the third identification information;

The sending module is further configured to send the message to the third network device, where the message includes the fourth segment identifier.
The device according to claim 15, wherein the second network device and the third network device are the same device, the first identification information and the second identification information are the same identification information, and the second The segment identifier and the fourth segment identifier are the same segment identifier.
The device according to any one of claims 14 to 16, characterized in that:

The determining module is further configured to determine multiple segment identifiers corresponding to multiple network devices, and the multiple segment identifiers respectively include the same fourth identification information;

The generating module is further configured to generate a fifth segment identifier based on the multiple segment identifiers, where the fifth segment identifier includes the fourth identifier information and fifth identifier information, and the fifth identifier information is used to identify the State the number of multiple network devices;

The sending module is further configured to send the message, and the message includes the fifth segment identifier.
The device according to claim 17, wherein the fifth segment of identification does not include the first identification information and sixth identification information respectively corresponding to the plurality of network devices, and the sixth identification information respectively It is used to uniquely identify the multiple network devices in the autonomous domain to which the multiple network devices belong.
The device according to claim 17 or 18, wherein the plurality of network devices include the second network device, and the second segment identifier and the fifth segment identifier are the same segment identifier.
The device according to any one of claims 14 to 19, wherein the message further includes seventh identification information, and the seventh identification information is used to identify that the first network device generates the second segment Identify the strategy.
The device according to any one of claims 17 to 20, wherein the determining module determines multiple segment identifiers corresponding to multiple network devices, comprising:

The determining module determines the multiple segment identifiers corresponding to the multiple network devices based on the internal gateway protocol IGP messages sent by the multiple network devices respectively; or,

The determining module determines multiple segment identifiers corresponding to multiple network devices based on the control message sent by the control device.
A first network device, characterized in that, the first network device includes:

A receiving module, configured to receive a message, the message including the first segment identifier corresponding to the second network device;

A determining module, configured to determine first identification information corresponding to the second network device, where the first identification information is used to identify the autonomous domain to which the second network device belongs;

A generating module, configured to generate a second segment identifier corresponding to the second network device based on the first identifier information and the first segment identifier;

The sending module is configured to send the message to the second network device based on the second segment identifier.
The device according to claim 22, wherein the second network device is a next hop device of the first network device,

The determining module is further configured to determine second identification information, where the second identification information is used to identify the second network device in the autonomous domain;

The generating module is configured to generate the second segment identifier corresponding to the second network device based on the first identification information, the second identification information, and the first segment identifier.
The device according to claim 22 or 23, wherein the forwarding path of the message includes a plurality of consecutive network devices, and the plurality of consecutive network devices correspond to a plurality of segment identifiers, and the first The network device is located at the first of the plurality of consecutive network devices on the forwarding path, the plurality of segment identifiers include the same third identification information, and the first segment identifier includes the third identification information and Fourth identification information, where the fourth identification information is used to indicate the number of the multiple consecutive network devices, and the sending module includes:

The first determining subunit is configured to determine fifth identification information based on the fourth identification information;

The second determining subunit is configured to determine the updated first segment identifier, where the updated first segment identifier includes the third identification information and the fifth identification information;

The sending subunit is configured to send the message to the second network device based on the second segment identifier, where the message includes the updated first segment identifier.
The device of claim 24, wherein the fourth identification information is a first value, the fifth identification information is a second value, and the second value is the first value minus one.
The device according to any one of claims 22 to 25, the determining module comprises:

The receiving subunit is configured to receive a message, the message including sixth identification information and seventh identification information corresponding to the second network device, the sixth identification information including the first identification information, and the seventh identification information. The identification information is used to identify the length of the first identification information;

The third determining subunit is configured to determine the first identification information based on the sixth identification information and the seventh identification information.
A network device, characterized in that, the network device includes a memory and a processor;

The memory is used to store a computer program;

The processor is configured to execute a computer program stored in the memory to execute the method according to any one of claims 1-8, or to execute the method according to any one of claims 9-13.