WO2024174668A1 - Information transmission method and related device - Google Patents

Abstract

An information transmission method and a related device. The information transmission method comprises: a controller receives a behavioral capability supported by a first node and reported by the first node, and, according to the supported behavioral capability, issues a first segment list to the first node, the first segment list comprising one or more first segment identifiers. That is, before sending a segment list to a node, the controller will first determine a behavioral capability supported by the node, and the controller may issue the first segment list on the basis of the behavioral capability supported by the node and actual demands, so as to ensure that a forwarding path will not fail.

Description

Information transmission method and related equipment

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on February 22, 2023, with application number CN202310151751.2 and invention name “A method for information transmission and related equipment”, the entire contents of which are incorporated by reference in this application.

Technical Field

The embodiments of the present application relate to the field of communications, and in particular, to an information transmission method and related equipment.

Background Art

Segment routing (SR) is a protocol designed based on the concept of source routing to forward data packets on the network.

SR divides the network path into segments and assigns segment IDs (SIDs) to these segments and network nodes. By arranging the SIDs in order to form a segment list, a forwarding path can be obtained, indicating that the message follows the specified forwarding path to be transmitted in the network node. Among them, the SID also carries a behavior attribute to instruct the network node to perform the corresponding behavior, and the network node needs to be able to support the behavior.

However, different network nodes may support different capabilities. If a network node does not support a certain capability, and the SID sent by the controller indicates that the behavior executed by the network node needs to support the capability, the forwarding path will be blocked.

Summary of the invention

The embodiment of the present application provides an information transmission method and related equipment, which are used to avoid the problem of forwarding path failure when the controller sends a segment list to the network node. The embodiment of the present application also provides a corresponding controller, a network node and a computer-readable storage medium.

The first aspect of the present application provides an information transmission method, which includes: a controller receives capability information reported by a first node, the capability information includes behavioral capabilities supported by the first node; the controller sends a first segment list to the first node based on the capability information, the first segment list includes one or more first segment identifiers.

In this application, the controller and the network node are used as the execution subjects of the interactive schematic to illustrate the method, but this application does not limit the execution subjects of the interactive schematic. For example, the controller can also be a chip, a chip system, or a processor that supports the controller implementation method, and can also be a logical node, a logical module, or software that can implement all or part of the controller function; the network node can also be a chip, a chip system, or a processor that supports the network node implementation method, and can also be a logical node, a logical module, or software that can implement all or part of the network node function.

In this application, an application scenario is used to optimize network traffic by using segment routing (SR) or segment routing policy (SR Policy). SR Policy divides the network path into segments and assigns segment IDs (SIDs) to these segments and network nodes (referred to as nodes). By arranging the SIDs in order to form a segment list (segment list), a forwarding path (which can also be a candidate path) can be obtained, indicating that the message follows the specified forwarding path to be transmitted in the network node.

In the present application, the network may be a routing network, the network includes a controller and multiple network nodes, the controller is an independent controller, specifically a network control engine (NCE) or a computer device, the network node may be regarded as a forwarding device, specifically a router or a switch.

The SR Internet Protocol version 6 in this application is segment routing over IPv6 (SRv6). In SRv6, a network node may support multiple different behavioral capabilities. After receiving capability information including behavioral capabilities supported by a first node, the controller will issue a first segment list to the first node based on the capability information when it needs to issue the first segment list to the first node in the future, wherein the first segment list includes one or more first segment identifiers.

In the first aspect, the controller receives the behavior capabilities supported by the first node reported by the first node, and sends a first segment list to the first node based on the supported behavior capabilities, wherein the first segment list includes one or more first segment identifiers, that is, before sending the segment list to the node, the controller will first determine the behavior capabilities supported by the node. The controller can send the first segment list based on the behavior capabilities supported by the node and actual needs to ensure that the forwarding path will not fail.

In a possible implementation manner of the first aspect, behavior capabilities required by the behavior attributes identified by the one or more first segments do not include behavior capabilities that are not supported by the first node.

In this possible implementation, before sending the segment list to the node, the controller will first determine the behavioral capabilities supported by the node and the behavioral capabilities required by each segment identifier in the segment list. The segment list will be sent down only when the node has the behavioral capabilities required by each segment identifier, thereby ensuring that the forwarding path will not fail, thereby improving the feasibility of the solution.

In a possible implementation manner of the first aspect, the behavior capability supported by the first node includes at least one of a compression capability, an encapsulation capability, and an adhesion capability.

In this possible implementation, the first node supports multiple types of behavioral capabilities, and the first node can report to the controller the specific behavioral capabilities it has or does not have, thereby improving the feasibility of the solution.

In a possible implementation of the first aspect, the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol.

In this possible implementation, the controller and the first node can communicate based on a variety of different communication protocols. When communicating based on different communication protocols, the corresponding capability information that needs to be reported can also be adjusted accordingly, thereby improving the feasibility of the solution.

In a possible implementation manner of the first aspect, the capability information is included in a structure data TLV, a sub-TLV, or a sub-sub-TLV newly added under a preset communication protocol.

In this possible implementation, according to the different communication protocols used by the controller and the first node, the capability information can be included in the newly added structure data TLV, sub-TLV or sub-sub-TLV under the preset communication protocol, thereby improving the feasibility of the solution.

In a possible implementation of the first aspect, the capability information also includes behavioral capabilities supported by the second node, and the behavioral capabilities supported by the second node are sent by the second node to the first node. The method also includes: the controller sends a second segment list to the second node based on the capability information, and the second segment list includes one or more second segment identifiers. The behavioral capabilities required by the behavioral attributes of the one or more second segment identifiers do not include behavioral capabilities that are not supported by the second node.

In this possible implementation, under certain communication protocols, the first node can also receive capability information supported by the remote node and report it to the controller. The controller can determine the behavioral capabilities supported by the first node and the second node respectively based on the capability information, and send down different segment lists in a targeted manner, thereby avoiding multiple nodes communicating with the controller multiple times separately and saving network resources.

A second aspect of the present application provides an information transmission method, which includes: a first node sends capability information to a controller, the capability information includes behavioral capabilities supported by the first node; the first node receives a first segment list sent by the controller, the first segment list includes one or more first segment identifiers.

In a possible implementation manner of the second aspect, behavior capabilities required by the behavior attributes of the one or more first segment identifiers do not include behavior capabilities that are not supported by the first node.

In a possible implementation manner of the second aspect, the behavior capability supported by the first node includes at least one of a compression capability, an encapsulation capability, and an adhesion capability.

In a possible implementation of the second aspect, the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol.

In a possible implementation manner of the second aspect, the capability information is included in a structure data TLV, a sub-TLV, or a sub-sub-TLV newly added under a preset communication protocol.

In a possible implementation of the second aspect, it is characterized in that, in the above-mentioned step: before the first node sends the capability information to the controller, the method also includes: the first node receives the behavior capabilities supported by the second node sent by the second node, so that the controller sends a second segment list to the second node according to the capability information, the capability information also includes the behavior capabilities supported by the second node, the second segment list includes one or more second segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more second segment identifiers do not include behavior capabilities not supported by the second node.

The third aspect of the present application provides a controller, including: a receiving unit, used to receive capability information reported by a first node, the capability information including behavioral capabilities supported by the first node; a sending unit, used to send a first segment list to the first node according to the capability information, the first segment list including one or more first segment identifiers.

The controller of the third aspect of the present application executes the method in the first aspect of the present application or any possible implementation of the first aspect.

A fourth aspect of the present application provides a network node, comprising: a sending unit, configured to send capability information to a controller, wherein the capability information includes a behavior capability supported by a first node; a receiving unit, configured to receive a first segment list sent by the controller, wherein the first segment list includes one or more The first paragraph identifies.

The network node in the fourth aspect of the present application executes the method in the second aspect of the present application or any possible implementation manner of the second aspect.

In a fifth aspect, the present application provides a controller, comprising: a processor, a communication interface and a memory, wherein the memory is used to store program code, and the processor is used to call the program code in the memory so that the controller executes the method in the first aspect or any possible implementation of the first aspect.

In a sixth aspect, the present application provides a network node, comprising: a processor, a communication interface and a memory, wherein the memory is used to store program code, and the processor is used to call the program code in the memory so that the network node executes the method in the second aspect of the present application or any possible implementation of the second aspect.

A seventh aspect of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enable the computer to execute a method as in the first aspect or any possible implementation of the first aspect.

An eighth aspect of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enable the computer to execute a method as in the second aspect or any possible implementation of the second aspect.

A ninth aspect of the present application provides a computer program product storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes a method as described in the first aspect or any possible implementation of the first aspect.

The tenth aspect of the present application provides a computer program product storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes a method as described in the second aspect or any possible implementation of the second aspect.

In the eleventh aspect of the present application, a chip system is provided, which includes at least one processor and an interface, the interface is used to receive data and/or signals, and at least one processor is used to support a computer device to implement the functions involved in the above-mentioned first aspect or any possible implementation of the first aspect. In one possible design, the chip system may also include a memory, which is used to store program instructions and data necessary for the computer device. The chip system can be composed of chips, or it can include chips and other discrete devices.

The twelfth aspect of the present application provides a chip system, which includes at least one processor and an interface, the interface is used to receive data and/or signals, and at least one processor is used to support a computer device to implement the functions involved in the above-mentioned second aspect or any possible implementation of the second aspect. In one possible design, the chip system may also include a memory, which is used to store program instructions and data necessary for the computer device. The chip system can be composed of chips, or it can include chips and other discrete devices.

The thirteenth aspect of the present application provides a communication system, which includes the controller provided by the third aspect of the present application and the network node provided by the fourth aspect of the present application.

The fourteenth aspect of the present application provides a communication system, which includes the controller provided by the fifth aspect of the present application and the network node provided by the sixth aspect of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is an architecture diagram for issuing SR Policy in the network;

FIG2 is a schematic diagram of a structure of a network node;

FIG3 is another schematic diagram of the structure of a network node;

FIG4 is a schematic diagram of network node encapsulation capabilities;

FIG5 is a schematic diagram of the compression capability of a network node;

FIG6 is a schematic diagram showing the relationship between a segment identifier and a general segment identifier;

FIG7 is a schematic diagram of a network architecture in which network nodes do not have compression capabilities;

FIG8 is a schematic diagram of a network architecture in which network nodes do not have encapsulation capabilities;

FIG9 is a schematic diagram of an embodiment of an information transmission method provided in an embodiment of the present application;

10-12 are TLV format diagrams of capability information provided in embodiments of the present application;

FIG13 is a schematic diagram of another embodiment of the information transmission method provided in an embodiment of the present application;

FIG14 is a schematic diagram of a network architecture of an information transmission method provided in an embodiment of the present application;

FIG15 is a schematic diagram of a structure of a controller provided in an embodiment of the present application;

FIG16 is a schematic diagram of a structure of a network node provided in an embodiment of the present application;

FIG17 is another schematic diagram of the structure of the controller provided in an embodiment of the present application;

FIG18 is another schematic diagram of the structure of a network node provided in an embodiment of the present application;

FIG19 is a schematic diagram of the structure of a communication system provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following describes the embodiments of the present application in conjunction with the accompanying drawings. Obviously, the described embodiments are only embodiments of a part of the present application, rather than all embodiments. It is known to those skilled in the art that with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

In addition, in order to better illustrate the present application, numerous specific details are provided in the following specific embodiments. It should be understood by those skilled in the art that the present application can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present application.

The embodiment of the present application provides an information transmission method and related equipment, which are used to avoid the problem of forwarding path failure when the controller sends a segment list to the network node. The embodiment of the present application also provides a corresponding controller, a network node, and a computer-readable storage medium, etc. The following are detailed descriptions.

The following is an example of the application scenario involved in the embodiments of the present application.

Please refer to Figure 1. When the user needs to tune the network traffic, segment routing (SR) or segment routing policy (SR Policy) can be used. SR Policy divides the network path into segments and assigns segment IDs (SIDs) to these segments and network nodes (referred to as nodes). By arranging the SIDs in order to form a segment list (segment list), a forwarding path (which can also be a candidate path) can be obtained, indicating that the message follows the specified forwarding path to be transmitted in the network node. Among them, the network can be a routing network, the network includes a controller and multiple network nodes, the controller is an independent controller, specifically a network control engine (NCE) or a computer device, the network node can be regarded as a forwarding device, and the forwarding device can specifically be a router or a switch.

Exemplarily, referring to FIG. 2 , the network node may include a main control board 210 and an interface board 220, the main control board 210 and the interface board 220 are connected, the main control board 210 includes a first processor 211 and a first memory 212, the first processor 211 and the first memory 212 are connected, the interface board 220 includes a second processor 221, a second memory 222 and an interface card 223, the second processor 221 and the second memory 222 are connected, and the second memory 222 and the interface card 223 are connected. The first processor 211 is used to call the program instructions in the first memory 212 to perform the corresponding processing function, the second processor 221 is used to call the program instructions in the second memory 222 to perform the reception and transmission of the message, and the interface card 223 is used to connect to an external device to receive data.

3, the network node may include a transceiver 302, a processor 301, a memory 303 and a bus 304. The transceiver 302 is used to receive and send messages, the memory 303 is used to store program instructions, and the processor 301 is used to call the program instructions in the memory 303 to perform corresponding processing functions.

Referring to FIG. 1 , the network includes network nodes P1, P2, PE1, PE2, PE3, PE4, CE1 and CE2. The controller completes the entire network topology collection through network node PE3, thereby determining the forwarding path. The data of network node CE2 will be sent to network node CE1 according to the specified forwarding path. Among them, SR can be based on Internet protocol version 4 (internet protocol version 4, IPv4) or Internet protocol version 6 (internet protocol version 6, IPv6). At this time, SR can be expressed as segment routing over IPv4 (segment routing over IPv4, SRv4) or segment routing over IPv6 (segment routing over IPv6, SRv6).

Specifically, SRv6 Segment is in the form of an IPv6 address, which is also commonly referred to as an SRv6 SID. The SRv6 SID is determined by the locator. The format is Locator:Function, where the Locator occupies the high bits of the IPv6 address and the Function part occupies the rest of the IPv6 address. Locator has a positioning function, so it is generally unique in the SR domain. After the node is configured with Locator, the system will generate a Locator network segment route and spread it in the SR domain. Other nodes in the network can locate this node through the Locator network segment route, and all SRv6 SIDs published by this node can also be reached through this Locator network segment route. Function represents the device's instructions, which are pre-set by the device. The Function part is used to instruct the SRv6 SID generation node to perform corresponding functional operations. The Function part can also be divided into an optional parameter segment (Arguments). At this time, the format of the SRv6 SID becomes Locator:Function:Arguments. Arguments occupy the low bits of the IPv6 address. The Arguments field can be used to define some message flows and services. In SRv6, network nodes may support a variety of different behavioral capabilities, such as compression capability, encapsulation capability, and adhesion capability, which are described below.

1. Packaging capability:

The extended header (SRH) can be encapsulated through the source node (starting node) or the end node (terminating node) in the network node. There are three main ways to encapsulate SRH: insert, encapsulate, and reduce.

(1) Insert: Specify the SRv6 SID stack encapsulation mode as insert mode, and copy the SID to the SRH header. Specifically, as shown in Figure 4, when node CE1 transmits information to node CE2, the transmitted information is a message, which includes a message header and a payload. The source address (SA) of the IPv6 message header is CE1, and the destination address (DA) is CE2. An SRH carrying label stack (CE2, B:13::1:0, B:12::1:0, B:11::1:0) is inserted after the IPv6 header of the data message, and the destination address of the current IPv6 message header is modified to the first SID (B::11:1:0), that is, segment list [SL]. The new IPv6 message is forwarded by table lookup. The forwarding path will indicate node 11, node 12, node 13, and finally reach node CE2. Insert mode will continuously modify the destination address (DA) field of the original IPv6 packet header. When encapsulating the Segment List, the original IPv6 packet DA will be placed in segment list[0]. In Insert mode, the penultimate segment pop of the SRH (PSP) is configured for the SID of segment list[1]. After reaching the node, the command operation is executed to clear the SRH and perform corresponding operations on the new IPv6 packet header.

(2) Encap: Specify the SRv6 SID stack encapsulation mode as encaps mode, which will add an IPv6 header (the SID will not be copied to the newly added SRH header). Specifically, as shown in Figure 5, when node CE1 transmits information to node CE2, the source address (SA) of the IPv6 header is CE1, and the destination address (DA) is CE2. Before the IPv6 header of the data message, a new set of IPv6 headers and SRH headers are encapsulated. The source address in the new IPv6 message is set to the current node address, and the destination address is set to the first SID. After configuring other fields, the new IPv6 message is forwarded by table lookup. The content in the message header can refer to Insert. The Encap mode is to add a new IPv6 message header. The original DA does not need to be encapsulated during encapsulation. At this time, USD is configured for the SID of segment list[0]. When reaching the corresponding last node in the signature stack, the outer IPv6 is decapsulated and corresponding operations are performed according to the inner IPv6 message header.

(3) Reduce: Enable the Reduced SRH function. The first SID is not encapsulated in the SRH. The length of the SRH can be reduced without affecting service forwarding. Specifically, the SRH extension header itself occupies a long length, and when the SRv6 source node encapsulates the SRH, it has already encapsulated the first SID to be processed into the destination address field of the IPv6 packet header. Therefore, the first SID in the SRH is no longer meaningful for forwarding. In order to reduce the size of the SRH extension header, the SRv6 source node can use the Reduced SRH mode when encapsulating the SRH, that is, the first SID to be processed is not encapsulated. If the SRH itself has only one SID, then according to the standard, the SRH extension header can be not encapsulated.

2. Compression Capacity:

The SRH (segment routing header) extended header is a key extension to implement SRv6. In encapsulation mode, the SRv6 head node will encapsulate the outer IPv6 header and SRH extended header on the message before forwarding it, but this brings a certain header overhead, and when the number of SRv6 SIDs is large, the length of the SRH extended header will further increase. This may cause the following problems: 1. Decreased payload efficiency: The message header added by SRv6 is a transmission overhead. When the number of SIDs in the SRH is large, the header length increases and the payload ratio decreases, resulting in low transmission efficiency. 2. Decreased hardware forwarding performance: As the number of SIDs increases, the position of the SID in the SRv6 message may exceed the depth of the hardware's one-time read, causing the hardware to perform a second read, resulting in a decrease in forwarding processing performance. 3. The maximum transmission unit (MTU) limits message forwarding. MTU refers to the maximum data packet size that the network can transmit. The size of MTU determines the maximum number of bytes that the sender can send at one time. Because of the increase in the SRv6 message header, the size of the final generated SRv6 message may exceed the MTU limit, causing fragmentation or packet loss in the middle.

G-SRv6 is an SRv6-compatible SRH compression solution. G-SRv6 not only supports SRH compression and reduces SRv6 header overhead, but can also be mixed with traditional SRv6 SIDs in one SRH, thus supporting the smooth evolution of SRv6 from non-compression to compression solutions. G-SRv6 is mainly divided into two parts: SRv6 SRH compression and compatibility with traditional SRv6. The principle of SRv6 SRH compression is based on the regularity of the SRv6 SID format. The redundant information of the segment list in the SRH is stripped off, and only the changed part is carried, thereby reducing the header overhead and achieving compression. Compatibility with SRv6 is to increase the behavior attribute (Flavor) to indicate the format of the next SID to achieve the processing of SIDs of different lengths, thereby supporting mixed programming and processing of different types of SIDs. For example, Flavor includes PSP, the last segment performs SRH removal operation (ultimate segment POP of the SRH, USP), the last segment performs outer IPv6 decapsulation operation (ultimate segment decapsulation, USD), continue compression (COC) and shift (Next) and other types.

SIDs in the SRv6 domain are all allocated from the SID address block, so these SIDs all have a common prefix (CP). If the SID in the destination address of the IPv6 message header already carries a common prefix, then the SID in the SRH only needs to carry the difference part. In this way, when the address is updated, the difference part is updated to the destination address of the IPv6 message header to completely restore the original SID. This difference part is called a generalized segment identifier (G-SID) in Generalized SRv6 Network Programming (G-SRv6). As shown in Figure 6, the relationship between the full SID and the 32-bit G-SID is shown. Arguments or blank padding are also set in the SID.

3. Adhesion ability

Binding SID is used to provide network expansion capabilities, network internal invisibility, and service independence. Specifically, Binding SID (BSID) is used to identify the entire candidate path, provide tunnel connection, traffic guidance and other functions. If the message carries the BSID corresponding to the candidate path, it will be directed to the corresponding candidate path. If SRv6 Policy is regarded as a network service, then Binding SID is the interface to access this service. Therefore, the design of SRv6 Policy is a subscription and publication model. The business subscribes to the network service according to its own needs, and the network can provide the interface of the connection service it provides to the business.

BSID traffic diversion is a data plane traffic diversion method used in scenarios where the service head node and the SRv6 Policy head node are not the same node. For example: providing SRv6 Policy connection services across management domains, or SRv6 Policy as a sub-path of an end-to-end path.

However, different network nodes may support different capabilities. If a network node does not support a certain capability, and the SID sent by the controller indicates that the behavior executed by the network node needs to support the capability, the forwarding path will be blocked.

Exemplarily, based on the compression capability, as shown in Figure 7, there is an SRv6 tunnel from node 0 to node 9, where head node 0 is a device from manufacturer A, and node 3 and node 5 are devices from manufacturer B. The device from manufacturer B sends a SID containing next. However, the device from manufacturer A does not support next intercommunication and cannot perform next-format compression on the 128-bit SID sent by the controller. If the controller does not perceive that head node 0 does not support next compression, the label stack sent to head node 0 contains node 3 and node 5, and the flavors of node 3 and node 5 also have the next attribute. Head node 0 cannot perform next-format compression on the label stack, and the SRv6 tunnel path is blocked (down).

Exemplarily, based on the encapsulation capability, as shown in Figure 8, there is an SRv6 tunnel from 0 to 9, where head node 0 is an old version device and does not have the encap capability. Node 9 is a new version device with the encap capability and supports publishing SIDs with PSP-USP-USD attributes. If the controller does not perceive that head node 0 does not have the encap capability, the label stack sent to head node 0 contains node 9, and the flavor of node 9 is psp-usp-usd. The old version of the head node cannot encap the label stack, and the SRv6 tunnel is down.

For example, based on the adhesion capability, the controller needs to sense which node in the network has the BSID adhesion capability in order to send the BSID. However, the current implementation is to manually specify which nodes the controller sends the BSID to, or the controller reads the SR Policy and other configurations of the network device and then tries to send the BSID. After the node reports the adhesion capability, it is convenient for the controller to send it, but when there are many nodes and many hops in the network, the current implementation has problems such as high maintenance cost and long time consumption.

The information transmission method provided in the embodiment of the present application is described below in combination with the above application scenario.

In this application, "sending information to... (e.g., a node)/sending information to..." can be understood as the destination of the information being a node. It can include sending information to a node directly or indirectly. "Receiving information from... (e.g., a node)/receiving information sent by..." can be understood as the source of the information being a node, which can include receiving information from a node directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

It is understood that the schematic diagram of the method in this application uses the controller and the network node as the execution subject of the interactive diagram as an example to illustrate the method, but this application does not limit the execution subject of the interactive diagram. For example, the controller in the figure can also be a chip, chip system, or processor that supports the controller to implement the method, or a logical node, logic module, or software that can implement all or part of the controller function; the network in the figure can also be a logical node, logic module, or software that can implement all or part of the controller function. The node may also be a chip, a chip system, or a processor that supports the network node implementation method, or may be a logical node, a logical module, or software that can implement all or part of the network node functions.

As shown in FIG. 9 , an embodiment of the information transmission method provided in the embodiment of the present application includes:

101. A first node sends capability information to a controller.

102. The controller sends a first segment list to the first node according to the capability information.

The information transmission method can be applied in a network as shown in FIG1 , for example, node PE3 is the first node, the first node sends capability information to the controller, wherein the capability information includes the behavior capabilities supported by the first node, and after receiving the capability information, the controller will issue the first segment list to the first node based on the capability information when it needs to issue the first segment list to the first node in the future, wherein the first segment list includes one or more first segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more first segment identifiers issued by the controller to the first node do not include behavior capabilities not supported by the first node.

The behavior capabilities supported by the first node include at least one of compression capability, encapsulation capability and adhesion capability. Specifically, the reported behavior capabilities include but are not limited to G-SID 32bit compression capability, G-SID 16bit compression capability, micro segment identifier (micro SID, uSID) 16bit compression capability, uSID 32bit compression capability, insert, encap or reduce encapsulation capability and Binding SID adhesion capability. The capability information can be included in the newly added structure data (type-length-value, TLV), sub-TLV or sub-sub-TLV under the preset communication protocol, and the controller and the first node can communicate based on the preset communication protocol. The following is a detailed description based on different communication protocols.

1. Intermediate system to intermediate system protocol (IS-IS)

Based on the ISIS protocol, a new type of sub-sub TLV (sub-sub TLV) can be added under the sub-TLV (sub-TLV) of SRv6Capabilities No. 25 of IS-IS routing capability (Router Capability) No. 242 in the protocol number to carry the supported SRv6 compression, encapsulation, Binding SID adhesion and other behavioral capabilities, that is, capability information, so as to publish, parse and flood (synchronize) the supported SRv6 compression, encapsulation, Binding SID adhesion and other behavioral capabilities of the first node within the ISIS level.

The newly added extended sub-sub TLVs of SRv6Capabilities sub-TLV include but are not limited to the following sub-sub TLVs: 32-bit compression capability sub-sub TLV, 16-bit compression capability sub-sub TLV, encapsulation capability sub-sub TLV, Binding SID adhesion capability sub-sub TLV, etc. 32-bit compression means that the length of the compressed SID is fixed to 32 bits, and 16-bit compression means that the length of the compressed SID is fixed to 16 bits.

For example, in each sub-sub TLV, bits are used to identify specific various behavior capabilities. As shown in FIG10 , the length of each sub-sub TLV is 2, and 16 bits are used to identify such behavior capabilities; or as shown in FIG11 , the length is 4, and 32 bits are used to identify such behavior capabilities.

Furthermore, the 32-bit compression capability includes, but is not limited to: 32-bit next compression capability (compressing a group of 128-bit SID label stacks sent by the controller into 32-bit format in the form of next), 32-bit coc compression capability (compressing a group of 128-bit SID label stacks sent by the controller into 32-bit format in the form of coc), whether the format after 32-bit next compression under the controller can be forwarded (the controller sends a SID label stack compressed 32 bits in the form of next, whether the node can forward it normally), whether the format after 32-bit coc compression under the controller can be forwarded (the controller sends a SID label stack compressed 32 bits in the form of coc, whether the node can forward it normally), etc.

The 16-bit compression capability includes but is not limited to: 16-bit next compression capability (compressing a group of 128-bit SID label stacks sent by the controller into 16-bit format in the form of next), 16-bit coc compression capability (compressing a group of 128-bit SID label stacks sent by the controller into 16-bit format in the form of coc), whether the format after 16-bit next compression under the controller can be forwarded (the controller sends a SID label stack compressed 16 bits in the form of next, whether the node can forward it normally), whether the format after 16-bit coc compression under the controller can be forwarded (the controller sends a SID label stack compressed 16 bits in the form of coc, whether the node can forward it normally), etc.

Encapsulation capabilities include but are not limited to: encap, insert, reduce, etc. Binding SID adhesion capabilities include but are not limited to: node adhesion capabilities.

2. Open Shortest Path First v3 (OSPFv3)

Based on the OSPFv3 protocol, a new type of sub TLV can be added under the SRv6Capabilities TLV of the OSPFv3Router Information LSA (used to describe the status of all interfaces of the node) in the protocol number to carry the supported SRv6 compression, encapsulation, Binding SID adhesion capabilities and other behavioral capabilities, so as to publish, parse and flood the supported SRv6 compression, encapsulation, Binding SID adhesion capabilities and other behavioral capabilities of the first node in the OSPFv3 area.

The newly added extended sub TLVs of SRv6Capabilities TLV include but are not limited to the following sub TLVs: 32-bit compression capability sub TLV, 16-bit compression capability sub TLV, encapsulation capability sub TLV, Binding SID adhesion capability sub TLV, etc. In each sub TLV, bits are used to identify specific capabilities.

For example, as shown in Figure 12, each sub TLV has a length of 4 and 32 bits to identify this type of behavior capability. For specific examples of 32-bit compression capability, 16-bit compression capability, encapsulation capability, and Binding SID adhesion capability, refer to the corresponding description of the ISIS protocol.

3. Border Gateway Protocol-Link State (BGP-LS)

Based on the BGP-LS protocol, the first node where BGP-LS is deployed can report the first node's SRv6 compression, encapsulation, Binding SID adhesion capabilities and other behavioral capabilities to the controller through BGP-LS. The newly added extended top-level TLVs include but are not limited to the following top-level TLVs: 32-bit compression capability sub TLV, 16-bit compression capability sub TLV, encapsulation capability sub TLV, Binding SID adhesion capability sub TLV, etc.

For example, referring to FIG. 12, in each sub TLV, bits are used to identify specific various behavior capabilities. Each sub TLV has a length of 4 and 32 bits to identify such capabilities. For specific examples of 32-bit compression capability, 16-bit compression capability, encapsulation capability, and Binding SID adhesion capability, refer to the corresponding description of the ISIS protocol.

4. Path Computation Element Communication Protocol (PCEP)

Based on the PCEP protocol, the first node where PCEP is deployed can report the SRv6 compression, encapsulation, Binding SID adhesion and other behavioral capabilities supported by the first node to the controller through PCEP. The behavioral capabilities will be carried in the sub-TLV newly added under PATH-SETUP-TYPE-CAPABILITY TLV No. 34 in the protocol number (TLV used to indicate support for path creation capabilities).

The newly added extended sub TLVs of PATH-SETUP-TYPE-CAPABILITY TLV No. 34 include but are not limited to the following sub TLVs: 32-bit compression capability sub TLV, 16-bit compression capability sub TLV, encapsulation capability sub TLV, Binding SID adhesion capability sub TLV, etc.

For example, referring to FIG. 12 , in each sub TLV, bits are used to identify specific behavior capabilities. Each sub TLV has a length of 4 and 32 bits are used to identify such behavior capabilities.

It should be understood that the above-mentioned protocols are merely examples provided in the embodiments of the present application. The actual controller and the first node may also communicate based on other preset protocols, and the embodiments of the present application are not limited to this.

For the first node that has announced its supported SRv6 compression, encapsulation, Binding SID adhesion capability and other capability information, the controller will issue an SRv6 SID label stack to the first node based on the received SRv6 compression, encapsulation, Binding SID adhesion capability and other capability information supported by the first node, that is, issue an SL, wherein the SID of the SRv6 label stack issued by the controller to the first node will not contain the SID of the SRv6 compression, encapsulation, Binding SID adhesion capability that the first node does not support. It can also be understood that the behavior capabilities required by the behavior attributes of the SID in the SRv6 label stack issued by the controller to the first node do not include the behavior capabilities such as SRv6 compression, encapsulation or Binding SID adhesion capability that the first node does not support. For the node that has not announced its supported SRv6 compression, encapsulation, Binding SID adhesion capability, the controller will issue the SR Policy label stack to the node according to the original policy.

Optionally, the capability information sent by the first node to the controller may also include behavior capabilities not supported by the first node to facilitate the judgment of the controller.

Optionally, as shown in Figure 13, in a scenario of communication based on the above-mentioned IS-IS protocol, OSPFv3 protocol or BGP-LS protocol, the first node can also receive capability information reported from the remote node and send it to the controller together, that is, the capability information sent by the first node also includes behavioral capabilities supported by the second node. In addition to sending the first segment list to the first node based on the capability information, the controller can also send the second segment list to the second node based on the capability information. The second segment list includes one or more second segment identifiers, and the behavioral capabilities required by the behavioral attributes of the one or more second segment identifiers do not include behavioral capabilities that are not supported by the second node.

201. A first node receives a behavior capability supported by a second node and sent by the second node.

202. The first node sends capability information to the controller.

203. The controller sends a first segment list to the first node according to the capability information.

204. The controller sends a second segment list to the second node according to the capability information.

It should be understood that the execution order of step 203 and step 204 is not limited.

The information transmission method provided in the embodiment of the present application is described below with reference to an example.

As shown in Figure 14, in the upgrade scenario of network nodes, each network node floods the supported SRv6 compression, encapsulation, Binding SID adhesion and other capabilities through the interior gateway protocol (IGP) protocol in the IGP domain. The node deployed with BGP-LS reports the supported SRv6 compression, encapsulation, Binding SID adhesion and other capability information of its own node and the received remote node to the controller. The controller will issue the SID label stack to the node based on the received SRv6 compression, encapsulation, Binding SID adhesion and other capability information supported by the node.

Among them, the head node 0 is initially an old version device, which does not support the next compression capability and the encap encapsulation capability. Node 0 parses, publishes, and floods the supported capability information in the IGP domain through the above-mentioned ISIS/OSPFv3 extension protocol, and reports it to the controller through the BGP-LS extension protocol. The capability information supported by node 0 does not include the next compression capability and the encap encapsulation capability. The controller then sends the SR Policy label stack to the node based on the capability information, and the label stack will not contain SIDs with the usp and next behavior attributes.

Then, the head node 0 is upgraded to a new version device, which supports the next compression capability and the encap encapsulation capability. Node 0 will parse, publish, and flood the capability information of supporting the next compression capability and the encap encapsulation capability in the IGP domain through the ISIS/OSPFv3 extension protocol, and report it to the controller through the BGP-LS extension protocol. The controller sends the SR Policy label stack to the node, which may contain SIDs with usp and next behavior attributes. In the embodiment of the present application, the controller receives the behavior capabilities supported by the first node reported by the first node, and sends the first segment list to the first node according to the supported behavior capabilities, wherein the first segment list includes one or more first segment identifiers, that is, before sending the segment list to the node, the controller will first determine the behavior capabilities supported by the node and the behavior capabilities required by each segment identifier in the segment list, and only send the segment list when the node has the behavior capabilities required by each segment identifier, so as to ensure that the forwarding path will not fail.

The above introduces the information transmission method provided in the embodiment of the present application. The following introduces the related equipment provided in the embodiment of the present application in conjunction with the accompanying drawings.

Please refer to FIG. 15 , an embodiment of a controller 1500 in the embodiment of the present application includes:

The receiving unit 1501 is used to receive capability information reported by the first node, where the capability information includes behavior capabilities supported by the first node; the receiving unit 1501 can be used to execute step 101 or step 202 in the aforementioned method embodiment.

The sending unit 1502 is configured to send a first segment list to the first node according to the capability information, wherein the first segment list includes one or more first segment identifiers. The sending unit 1502 may be configured to execute step 102 or step 203 in the above method embodiment.

Optionally, the behavior capabilities required by the behavior attributes identified by one or more first segments do not include behavior capabilities that are not supported by the first node.

Optionally, the behavior capabilities supported by the first node include at least one of compression capability, encapsulation capability, and adhesion capability.

Optionally, the controller 1500 and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol.

Optionally, the capability information is included in a structure data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol.

Optionally, the capability information also includes the behavior capabilities supported by the second node, and the behavior capabilities supported by the second node are sent by the second node to the first node. The sending unit 1502 is also used to send a second segment list to the second node according to the capability information, and the second segment list includes one or more second segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more second segment identifiers do not include behavior capabilities that are not supported by the second node. The sending unit 1502 can also be used to execute step 204 in the aforementioned method embodiment.

The controller 1500 provided in the embodiment of the present application can be understood by referring to the corresponding content of the aforementioned information transmission method embodiment. For example, the controller 1500 is the controller in the aforementioned information transmission method embodiment, and will not be repeated here.

Please refer to FIG. 16 , an embodiment of a network node 1600 in an embodiment of the present application includes:

The sending unit 1601 is used to send capability information to the controller, where the capability information includes the behavior capabilities supported by the first node; the sending unit 1601 can be used to execute step 101 or step 202 in the aforementioned method embodiment.

The receiving unit 1602 is configured to receive a first segment list sent by the controller, wherein the first segment list includes one or more first segment identifiers. The receiving unit 1602 may be configured to execute step 102 or step 203 in the above method embodiment.

Optionally, the behavior capabilities required by the behavior attributes identified by one or more first segments do not include behavior capabilities that are not supported by the first node.

Optionally, the behavior capabilities supported by the first node include at least one of compression capability, encapsulation capability, and adhesion capability.

Optionally, the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes an intermediate system to intermediate system ISIS protocol, an open shortest path first OSPFv3 protocol version 3, a BGP link state BGP-LS protocol, or a path computation unit communication PCEP protocol. Any item in the Agreement.

Optionally, the capability information is included in a structure data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol.

Optionally, the receiving unit 1602 is further used to receive the behavior capabilities supported by the second node sent by the second node, so that the controller sends a second segment list to the second node according to the capability information, the capability information also includes the behavior capabilities supported by the second node, the second segment list includes one or more second segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more second segment identifiers do not include behavior capabilities not supported by the second node. The receiving unit 1602 can also be used to execute step 201 in the aforementioned method embodiment.

The network node 1600 provided in the embodiment of the present application can be understood by referring to the corresponding content of the aforementioned information transmission method embodiment. For example, the network node 1600 is the first node or the second node in the aforementioned information transmission method embodiment, and will not be repeated here.

As shown in the controller of Figure 17, it is a possible logical structure diagram of the controller 1700 provided in the embodiment of the present application. The controller 1700 includes: a processor 1701, a communication interface 1702, a storage system 1703 and a bus 1704. The processor 1701, the communication interface 1702 and the storage system 1703 are interconnected through the bus 1704. In the embodiment of the present application, the processor 1701 is used to control and manage the actions of the controller 1700. For example, the processor 1701 is used to execute the information transmission method performed by the controller described in the above embodiment. The communication interface 1702 is used to support the controller 1700 to communicate. The storage system 1703 is used to store the program code and data of the controller 1700.

Among them, the processor 1701 can be a central processing unit, a general processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 1701 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1704 can be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.

As shown in the network node of Figure 18, a possible logical structure diagram of a network node 1800 provided in an embodiment of the present application is provided. The network node 1800 includes: a processor 1801, a communication interface 1802, a storage system 1803 and a bus 1804. The processor 1801, the communication interface 1802 and the storage system 1803 are interconnected via the bus 1804. In an embodiment of the present application, the processor 1801 is used to control and manage the actions of the network node 1800. For example, the processor 1801 is used to execute the information transmission method performed by the network node described in the above embodiment. The communication interface 1802 is used to support the network node 1800 to communicate. The storage system 1803 is used to store the program code and data of the network node 1800.

Among them, the processor 1801 can be a central processing unit, a general processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 1801 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The bus 1804 can be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in Figure 18, but it does not mean that there is only one bus or one type of bus.

As shown in FIG. 19 , an embodiment of the present application further provides a communication system, which includes a controller 1910 and a network node 1920 .

The controller 1910 may be a controller as shown in FIG. 15 or a controller as shown in FIG. 17 . For example, the controller 1910 includes: a processor 1911, a communication interface 1912, a storage system 1913, and a bus 1914. The processor 1911, the communication interface 1912, and the storage system 1913 are interconnected via the bus 1914. In an embodiment of the present application, the processor 1911 is used to control and manage the actions of the controller 1910. For example, the processor 1911 is used to execute the information transmission method executed by the controller described in the above embodiment. The communication interface 1912 is used to support the controller 1910 to communicate. The storage system 1913 is used to store the program code and data of the controller 1910.

The network node 1920 may be a controller as shown in FIG. 16 or a network node as shown in FIG. 18. For example, the network node 1920 includes: a processor 1921, a communication interface 1922, a storage system 1923, and a bus 1924. The processor 1921, the communication interface 1922, and the storage system 1923 are interconnected via the bus 1924. In an embodiment of the present application, the processor 1921 is used to control and manage the actions of the network node 1920. For example, the processor 1921 is used to execute the information transmission method executed by the controller described in the above embodiment. The communication interface 1922 is used to support the network node 1920 to communicate. The storage system 1923 is used to store the program code and data of the network node 1920.

The controller 1910 and the network node 1920 are connected via a network. The communication interface in is connected to the network, and the network protocol may specifically be ISIS protocol, OSPFv3 protocol, BGP-LS protocol or PCEP protocol.

In another embodiment of the present application, a computer-readable storage medium is provided, in which computer-executable instructions are stored. When at least one processor of a device executes the computer-executable instructions, the device executes the information transmission method described in the above embodiment.

In another embodiment of the present application, a computer program product is also provided, which includes computer execution instructions, which are stored in a computer-readable storage medium; at least one processor of the device can read the computer execution instructions from the computer-readable storage medium, and at least one processor executes the computer execution instructions so that the device executes the information transmission method described in the above embodiment.

In another embodiment of the present application, a chip system is also provided, the chip system includes at least one processor and an interface, the interface is used to receive data and/or signals, and at least one processor is used to support the information transmission method described in the above embodiment. In one possible design, the chip system may also include a memory, the memory is used to store program instructions and data necessary for the computer device. The chip system can be composed of chips, and may also include chips and other discrete devices.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims (27)

An information transmission method, characterized by comprising: The controller receives capability information reported by the first node, where the capability information includes behavior capabilities supported by the first node; The controller sends a first segment list to the first node according to the capability information, where the first segment list includes one or more first segment identifiers. The method according to claim 1 is characterized in that the behavioral capabilities required by the behavioral attributes of the one or more first segment identifiers do not include behavioral capabilities that are not supported by the first node. The method according to claim 1 or 2 is characterized in that the behavioral capabilities supported by the first node include at least one of compression capability, encapsulation capability and adhesion capability. The method according to any one of claims 1-3 is characterized in that the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol. The method according to claim 4 is characterized in that the capability information is included in a structure data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol. The method according to any one of claims 1 to 5, characterized in that the capability information further includes behavior capabilities supported by the second node, and the behavior capabilities supported by the second node are sent by the second node to the first node, and the method further includes: The controller sends a second segment list to the second node according to the capability information, the second segment list includes one or more second segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more second segment identifiers do not include behavior capabilities that are not supported by the second node. An information transmission method, characterized by comprising: The first node sends capability information to the controller, where the capability information includes behavior capabilities supported by the first node; The first node receives a first segment list sent by the controller, where the first segment list includes one or more first segment identifiers. The method according to claim 7 is characterized in that the behavioral capabilities required by the behavioral attributes of the one or more first segment identifiers do not include behavioral capabilities that are not supported by the first node. The method according to claim 7 or 8 is characterized in that the behavioral capabilities supported by the first node include at least one of compression capability, encapsulation capability and adhesion capability. The method according to any one of claims 7-9 is characterized in that the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol. The method according to claim 10 is characterized in that the capability information is included in a structure data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol. The method according to any one of claims 7 to 11, characterized in that before the first node sends the capability information to the controller, the method further comprises: The first node receives the behavior capabilities supported by the second node sent by the second node, so that the controller sends a second segment list to the second node according to the capability information, the capability information also includes the behavior capabilities supported by the second node, the second segment list includes one or more second segment identifiers, and the behavior capabilities required by the behavior attributes of the one or more second segment identifiers do not include behavior capabilities not supported by the second node. A controller, characterized in that it comprises: A receiving unit, configured to receive capability information reported by a first node, wherein the capability information includes behavior capabilities supported by the first node; A sending unit is used to send a first segment list to the first node according to the capability information, where the first segment list includes one or more first segment identifiers. The controller according to claim 13 is characterized in that the behavioral capabilities required by the behavioral attributes of the one or more first segment identifiers do not include behavioral capabilities that are not supported by the first node. The controller according to claim 13 or 14 is characterized in that the behavioral capabilities supported by the first node include at least one of compression capability, encapsulation capability and adhesion capability. The controller according to any one of claims 13-15 is characterized in that the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol. The controller according to claim 16 is characterized in that the capability information is included in a structure data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol. The controller according to any one of claims 13-17 is characterized in that the capability information also includes behavioral capabilities supported by the second node, and the behavioral capabilities supported by the second node are sent by the second node to the first node. The sending unit is also used to send a second segment list to the second node based on the capability information, and the second segment list includes one or more second segment identifiers. The behavioral capabilities required by the behavioral attributes of the one or more second segment identifiers do not include behavioral capabilities that are not supported by the second node. A network node, comprising: a sending unit, configured to send capability information to the controller, wherein the capability information includes behavior capabilities supported by the first node; A receiving unit is used to receive a first segment list sent by the controller, where the first segment list includes one or more first segment identifiers. The node according to claim 19 is characterized in that the behavioral capabilities required by the behavioral attributes of the one or more first segment identifiers do not include behavioral capabilities that are not supported by the first node. The node according to claim 19 or 20 is characterized in that the behavioral capabilities supported by the first node include at least one of compression capability, encapsulation capability and adhesion capability. The node according to any one of claims 19-21 is characterized in that the controller and the first node communicate based on a preset communication protocol, and the preset communication protocol includes any one of the Intermediate System to Intermediate System ISIS protocol, the Open Shortest Path First OSPFv3 version 3 protocol, the BGP Link State BGP-LS protocol, or the Path Computation Unit Communication PCEP protocol. The node according to claim 22 is characterized in that the capability information is included in a structured data TLV, sub-TLV or sub-sub-TLV newly added under the preset communication protocol. The node according to any one of claims 19-23 is characterized in that the receiving unit is also used to receive the behavioral capabilities supported by the second node sent by the second node, so that the controller sends a second segment list to the second node according to the capability information, the capability information also includes the behavioral capabilities supported by the second node, the second segment list includes one or more second segment identifiers, and the behavioral capabilities required by the behavioral attributes of the one or more second segment identifiers do not include behavioral capabilities not supported by the second node. A controller comprises: a processor, a communication interface and a memory, wherein the memory is used to store program codes, and the processor is used to call the program codes in the memory so that the controller executes the method according to any one of claims 1 to 6. A network node comprises: a processor, a communication interface and a memory, wherein the memory is used to store program codes, and the processor is used to call the program codes in the memory so that the network node executes the method according to any one of claims 7 to 12. A computer-readable storage medium comprises instructions, and when the instructions are executed on a computer, the computer is caused to execute the method as claimed in any one of claims 1 to 6 or 7 to 12.