CN118540259A - Information transmission method and related equipment - Google Patents

Abstract

An information transmission method and related equipment, the information transmission method includes: the controller receives behavior capability supported by the first node and reports the behavior capability to the first node, and issues a first segment list to the first node according to the supported behavior capability, wherein the first segment list comprises one or more first segment identifiers, that is, before the controller sends the segment list to the node, the controller determines the behavior capability supported by the node, and the controller can issue the first segment list based on the behavior capability supported by the node and actual requirements so as to ensure that a forwarding path cannot be invalid.

Description

Information transmission method and related equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to an information transmission method and related equipment.

Background

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

The SR divides the network path into individual segments and assigns segment identities (SEGMENT ID, SID) to the segments and network nodes. By ordering the SIDs to form a segment list (SEGMENT LIST), a forwarding path can be obtained, indicating that the message follows the designated forwarding path for transmission in the network node. The SID further carries a behavior attribute, which is used to instruct the network node to execute the corresponding behavior, and the network node needs to have a capability to support the behavior.

But different network nodes may support different capabilities, if a network node does not support a certain capability, and the SID issued by the controller indicates that the network node performs an action that requires supporting the capability, the forwarding path may be blocked.

Disclosure of Invention

The embodiment of the application provides an information transmission method and related equipment, which are used for avoiding the problem that a forwarding path is invalid when a controller issues a segment list to a network node. The embodiment of the application also provides a corresponding controller, a network node, a computer readable storage medium and the like.

The first aspect of the present application provides an information transmission method, which includes: the method comprises the steps that a controller receives capability information reported by a first node, wherein the capability information comprises behavior capability supported by the first node; the controller issues a first segment list to the first node according to the capability information, the first segment list including one or more first segment identifiers.

In the present application, the method is illustrated by taking the controller and the network node as the execution body of the interactive schematic, but the present application is not limited to the execution body of the interactive schematic. For example, the controller may be a chip, a system on a chip, or a processor that supports the method of implementing the controller, or may be a logic node, a logic module, or software that can implement all or part of the controller's functions; the network node may also be a chip, a system-on-a-chip, or a processor supporting the network node implementation method, or may be a logic node, a logic module, or software capable of implementing all or part of the network node functions.

In the application, the application scenario is to illustrate the flow optimization of the network by using Segment Routing (SR) or segment routing Policy (segment routing Policy, SR Policy). SR Policy divides a network path into segments and assigns segment identities (SEGMENT ID, SID) to the segments and network nodes (simply referred to as nodes). By ordering the SIDs to form a segment list (SEGMENT LIST), a forwarding path (which may also be a candidate path) may be obtained, indicating that the message follows the designated forwarding path for transmission in the network node.

In the present application, the network may be a routing network, and the network includes a controller and a plurality of network nodes, where the controller is an independent controller, specifically may be a Network Control Engine (NCE) or a computer device, and the network nodes may be regarded as a forwarding device, and the forwarding device may specifically be a router or a switch.

SR internet protocol version 6 in the present application, i.e. IPv6 based segment routing (segment routing over IPv, SRv 6), in SRv the network node may support a number of different behavior capabilities. After receiving the capability information containing the behavior capability supported by the first node, the controller issues the capability information based on the capability information when the first segment list needs to be issued to the first node later, wherein the first segment list comprises one or more first segment identifiers.

According to the first aspect, the controller receives behavior capability supported by a first node and reports the behavior capability to the first node, and issues a first segment list to the first node according to the supported behavior capability, wherein the first segment list comprises one or more first segment identifiers, that is, the controller determines the behavior capability supported by the node before sending the segment list to the node, and the controller can issue the first segment list based on the behavior capability supported by the node and actual requirements so as to ensure that a forwarding path cannot be invalid.

In a possible implementation manner of the first aspect, the behavior capabilities required by the behavior attribute of the one or more first segment identifications do not include behavior capabilities not supported by the first node.

In the possible implementation manner, before the controller sends the segment list to the node, the behavior capability supported by the node and the behavior capability required by each segment identification in the segment list are determined, the segment list is issued only when the node has the behavior capability required by each segment identification, and therefore the forwarding path is guaranteed not to be invalid, and the feasibility of the scheme is improved.

In a possible implementation manner of the first aspect, the behavior capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities and blocking capabilities.

In the possible implementation manner, the behavior capability supported by the first node is of multiple types, and the first node can report the behavior capability or the behavior capability which is not specific to the first node to the controller, so that the feasibility of the scheme is improved.

In a possible implementation manner of the first aspect, the controller and the first node communicate based on a preset communication protocol, where the preset communication protocol includes any one of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

In the possible implementation manner, the controller and the first node can communicate based on a plurality of different communication protocols, and when the controller and the first node communicate based on different communication protocols, corresponding capability information to be reported can be correspondingly adjusted, so that the feasibility of the scheme is improved.

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

In this possible implementation manner, according to different communication protocols used by the controller and the first node, the capability information may be included in a newly added structural data TLV, sub-TLV or sub-TLV under a preset communication protocol, so as to improve the feasibility of the scheme.

In a possible implementation manner of the first aspect, the capability information further includes a behavior capability supported by the second node, and the behavior capability supported by the second node is sent to the first node by the second node, and the method further includes: the controller issues a second segment list to the second node according to the capability information, wherein the second segment list comprises one or more second segment identifiers, and the behavior capability required by the behavior attribute of the one or more second segment identifiers does not comprise the behavior capability which is not supported by the second node.

In the possible implementation manner, under certain communication protocols, the first node can also receive the self-supported capability information sent by the remote node and report the self-supported capability information to the controller, and the controller can determine the behavior capability supported by the first node and the second node according to the capability information and issue different segment lists in a targeted manner, so that a plurality of nodes are prevented from communicating with the controller for multiple times respectively, and network resources are saved.

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

In a possible implementation manner of the second aspect, the behavior capabilities required by the behavior attribute of the one or more first segment identifications do not include behavior capabilities 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, a packaging capability and a blocking capability.

In a possible implementation manner of the second aspect, the controller and the first node communicate based on a preset communication protocol, where the preset communication protocol includes any one of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

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

In a possible implementation manner of the second aspect, the steps are: before the first node sends the capability information to the controller, the method further comprises: the first node receives the behavior capability supported by the second node and 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 further comprises the behavior capability supported by the second node, the second segment list comprises one or more second segment identifiers, and the behavior capability required by the behavior attribute of the one or more second segment identifiers does not comprise the behavior capability not supported by the second node.

A third aspect of the present application provides a controller comprising: the receiving unit is used for receiving the capability information reported by the first node, wherein the capability information comprises the behavior capability supported by the first node; and the sending unit is used for sending a first segment list to the first node according to the capability information, wherein the first segment list comprises one or more first segment identifiers.

The controller of the third aspect of the application performs the method of the first aspect of the application or any possible implementation of the first aspect.

A fourth aspect of the present application provides a network node comprising: a transmitting unit, configured to transmit capability information to the controller, where the capability information includes behavior capabilities supported by the first node; and the receiving unit is used for receiving the first segment list sent by the controller, and the first segment list comprises one or more first segment identifiers.

The network node of the fourth aspect of the application performs the method of the second aspect of the application or any possible implementation of the second aspect.

A fifth aspect of the present application provides a controller comprising: a processor, a communication interface, and a memory for storing program code, the processor for invoking the program code in the memory to cause the controller to perform the method of the first aspect or any possible implementation of the first aspect.

A sixth aspect of the application provides a network node comprising: a processor, a communication interface and a memory for storing program code, the processor being adapted to invoke the program code in the memory to cause the network node to perform the method of the second aspect or any possible implementation of the second aspect of the present application.

A seventh aspect of the application provides a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method as in the first aspect or any possible implementation of the first aspect.

An eighth aspect of the application provides a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform a method as in the second aspect or any possible implementation of the second aspect.

A ninth aspect of the application provides a computer program product storing one or more computer-executable instructions which, when executed by a processor, perform a method as described above or any one of the possible implementations of the first aspect.

A tenth aspect of the application provides a computer program product storing one or more computer-executable instructions which, when executed by a processor, perform a method as described above in the second aspect or any one of the possible implementations of the second aspect.

An eleventh aspect of the present application provides a chip system comprising at least one processor and an interface for receiving data and/or signals, the at least one processor being adapted to support a computer device for carrying out the functions referred to in the first aspect or any one of the possible implementations of the first aspect. In one possible design, the chip system may further include memory to hold program instructions and data necessary for the computer device. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

A twelfth aspect of the application provides a chip system comprising at least one processor and an interface for receiving data and/or signals, the at least one processor being adapted to support a computer device for carrying out the functions referred to in the second aspect or any one of the possible implementations of the second aspect. In one possible design, the chip system may further include memory to hold program instructions and data necessary for the computer device. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

A thirteenth aspect of the present application provides a communication system comprising the controller provided in the third aspect of the present application and the network node provided in the fourth aspect of the present application.

A fourteenth aspect of the present application provides a communication system comprising the controller provided in the fifth aspect of the present application and the network node provided in the sixth aspect of the present application.

Drawings

FIG. 1 is a diagram of an architecture for delivering SR Policy in a network;

FIG. 2 is a schematic diagram of a network node;

fig. 3 is another schematic structural diagram of a network node;

FIG. 4 is a schematic diagram of network node encapsulation capability;

FIG. 5 is a schematic diagram of network node compression capability;

FIG. 6 is a schematic diagram of a relationship between segment identifiers and generic segment identifiers;

FIG. 7 is a schematic diagram of a network architecture in which network nodes do not have compression capability;

FIG. 8 is a schematic diagram of a network architecture in which network nodes do not have encapsulation capability;

fig. 9 is a schematic diagram of an embodiment of an information transmission method according to an embodiment of the present application;

FIGS. 10-12 are TLV format diagrams of capability information provided by an embodiment of the present application;

fig. 13 is a schematic diagram of another embodiment of an information transmission method according to an embodiment of the present application;

Fig. 14 is a schematic diagram of a network architecture of an information transmission method according to an embodiment of the present application;

FIG. 15 is a schematic diagram of a controller according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a network node according to an embodiment of the present application;

FIG. 17 is a schematic diagram of another configuration of a controller according to an embodiment of the present application;

fig. 18 is another schematic structural diagram of a network node according to an embodiment of the present application;

Fig. 19 is a schematic structural diagram of a communication system according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will now be described with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the present application. As one of ordinary skill in the art can know, with the development of technology and the appearance of new scenes, the technical scheme provided by the embodiment of the application is also applicable to similar technical problems.

The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

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

In addition, numerous specific details are set forth in the following description in order to provide a better illustration of the application. It will be understood by those skilled in the art that the present application may be practiced without some of these specific details. In some instances, well known methods, procedures, components, and circuits have not been described in detail so as not to obscure the present application.

The embodiment of the application provides an information transmission method and related equipment, which are used for avoiding the problem that a forwarding path is invalid when a controller issues a segment list to a network node. The embodiment of the application also provides a corresponding controller, a network node, a computer readable storage medium and the like. The following will describe in detail.

The following illustrates an application scenario according to an embodiment of the present application.

Referring to fig. 1, when a user needs to perform traffic optimization on a network, a Segment Routing (SR) or a segment routing Policy (segment routing Policy, SR Policy) may be used, the SR Policy divides a network path into segments, and assigns segment identifiers (SEGMENT ID, SID) to the segments and network nodes (abbreviated as nodes). By ordering the SIDs to form a segment list (SEGMENT LIST), a forwarding path (which may also be a candidate path) may be obtained, indicating that the message follows the designated forwarding path for transmission in the network node. The network may be a routing network, and the network includes a controller and a plurality of network nodes, where the controller is an independent controller, and may specifically be a Network Control Engine (NCE) or a computer device, and the network nodes may be regarded as a forwarding device, and the forwarding device may specifically be a router or a switch.

For example, referring to fig. 2, the network node may include a main control board 210 and an interface board 220, where the main control board 210 is connected to the interface board 220, the main control board 210 includes a first processor 211 and a first memory 212, the first processor 211 is connected to the first memory 212, the interface board 220 includes a second processor 221, a second memory 222 and an interface card 223, the second processor 221 is connected to the second memory 222, and the second memory 222 is connected to the interface card 223. The first processor 211 is used for calling the program instructions in the first memory 212 to execute corresponding processing functions, the second processor 221 is used for calling the program instructions in the second memory 222 to execute the receiving and sending of the messages, and the interface card 223 is used for connecting with an external device to receive data.

For example, referring to fig. 3, a network node may include a transceiver 302, a processor 301, a memory 303, and a bus 304. The transceiver 302 is configured to perform reception and transmission of a message, the memory 303 is configured to store program instructions, and the processor 301 is configured to invoke the program instructions in the memory 303 to perform corresponding processing functions.

Referring to fig. 1, the network includes network node P1, network node P2, network node PE1, network node PE2, network node PE3, network node PE4, network node CE1 and network node CE2, and the controller completes the whole network topology collection through network node PE3, so as to determine a forwarding path, and the data of network node CE2 is sent to network node CE1 according to the designated forwarding path. Where the SR may be based on internet protocol version 4 (internet protocol version, IPv 4) or internet protocol version 6 (internet protocol version, IPv 6), the SR may be represented as an IPv 4-based segment route (segment routing over IPv, SRv 4) or an IPv 6-based segment route (segment routing over IPv, SRv 6).

Specifically, SRv segments are in the form of an IPv6 address, which can also be commonly referred to as SRv SID, and the SRv6 SID consists of a Locator (Locator) and a Function (Function), wherein the format is Locator: function, the Locator occupies the upper bit of the IPv6 address, and the Function occupies the rest of the IPv6 address. The Locator has a locating function, so that the Locator is generally unique in the SR domain, and after the node configures the Locator, the system generates a Locator network segment route and diffuses in the SR domain. Other nodes in the network can be positioned to the node through the Locator network segment route, and all SRv SIDs issued by the node can also reach through the Locator network segment route. The Function represents instructions (instructions) of the device, which are preset by the device, and the Function part is used for instructing the SRv SID generating node to perform corresponding functional operations. The Function part can also separate an optional parameter section (Arguments), at this time, the format of SRv SID is changed into a Locator, the Function is Arguments, arguments occupies the low bit of the IPv6 address, and the Arguments field can define the flow and service information of some messages. In SRv, the network node may support a number of different behavior capabilities, such as compression capability, encapsulation capability, blocking capability, etc., as described below.

1. Encapsulation capability:

Extended header (segment routing header, SRH) encapsulation may be implemented by either a source node (originating node) or an end node (terminating node) in the network node. The main ways of packaging SRH are divided into three types: insert, package Encap, and Reduce.

(1) Specifying SRv that the SID stack encapsulation mode is an Insert mode, copying SIDs into an SRH header, specifically, as shown in fig. 4, in the process of transmitting information to a node CE2 by a node CE1, the transmitted information is a message, the message comprises a message header and a payload (payload), a Source Address (SA) of the IPv6 message header is CE1, a Destination Address (DA) is CE2, an SRH carrying label stack (CE 2, B:13: 1:0, B:12: 1:0, B:11: 1:0) is inserted behind the IPv6 header of the data message, the destination address of the current IPv6 message header is modified to be the first SID (B: 11:1:0), namely SEGMENT LIST [ SL ], and the forwarding path indicates nodes 11, 12 and 13 to reach the node CE2 finally. The Insert mode will continuously modify the Destination Address (DA) field of the original IPv6 header, when packaging SEGMENT LIST, the original IPv6 header DA will be put into SEGMENT LIST [0], in the Insert mode, the information of the second last hop SRH segment will pop up (penultimate segment pop of the SRH, PSP) for SID configuration of SEGMENT LIST [1], after reaching the node, instruction operation will be performed, SRH will be cleared, and corresponding operation will be performed for the new IPv6 header.

(2) Encap specify that SRv SID stack encapsulation mode is encaps mode, an IPv6 header is newly added (SID is not copied to the newly added SRH header), specifically, as shown in fig. 5, in the process of transmitting information from node CE1 to node CE2, the Source Address (SA) of the IPv6 header is CE1, the Destination Address (DA) is CE2, a set of new IPv6 header and SRH header is encapsulated before the IPv6 header of the data packet, the source address in the new IPv6 header is set as the current node address, the destination address is set as the first SID, other fields are configured, and table lookup forwarding is performed on the new IPv6 packet, where the content in the header can refer to Insert. The Encap mode is to add an IPv6 message header, and the original DA is not needed to be sealed when the message is packaged, at the moment, USD is configured for the SID of SEGMENT LIST [0], the outer IPv6 is unpacked when the message reaches the corresponding last node in the label stack, and corresponding operation is executed according to the inner IPv6 message header.

(3) The Reduced SRH function is enabled, the first SID is not packaged in the SRH, the length of the SRH can be Reduced under the condition that service forwarding is not affected, specifically, the SRH extension header itself occupies a longer length, and SRv source nodes already package the first SID to be processed into the destination address field of the IPv6 message header when the SRH is packaged, so the first SID in the SRH has no meaning for forwarding. In order to reduce the size of the SRH extension header, the SRv source node may use Reduced SRH mode when encapsulating SRH, i.e., not encapsulate the first SID to be processed. If the SRH itself has only one SID, then the SRH extension header may not be encapsulated as specified by the standard.

2. Compression capability:

SRH (segment routing header) extension header is a key extension to implement SRv. In the encapsulation mode, the SRv head node forwards the IPv6 header and the SRH extension header of the outer layer on the packet encapsulation, but this brings a certain header overhead, and when the SRv SID number is large, the length of the SRH extension header is further increased. This may cause problems in terms of: 1. payload efficiency decreases: SRv6 the added message header belongs to transmission overhead, when the number of SIDs in SRH is large, the header length is increased, the effective load ratio is reduced, and the transmission efficiency is low; 2. hardware forwarding performance decreases: as the number of SIDs increases, the position of the SID in the SRv message may exceed the depth of the first reading by the hardware, which results in the second reading by the hardware and the degradation of forwarding performance; 3. the maximum transmission unit (maximum transmission unit, MTU) limits packet forwarding, the MTU refers to the maximum data packet size that can be transmitted by the network, and the size of the MTU determines the maximum byte number that the sender can send a packet at a time, because the increase of the SRv message header may cause the size of the finally generated SRv message to exceed the limit of the MTU, resulting in midway fragmentation or packet loss.

G-SRv is a SRv6 compliant SRH compression solution. The G-SRv is not only capable of supporting SRH compression, reducing SRv6 header overhead, but also can be programmed in one SRH mixed with the legacy SRv SID, thus supporting a smooth evolution of SRv from non-compressed to compressed schemes. G-SRv is divided into SRv SRH compression and conventional SRv compatible parts. The principle of SRv SRH compression is that redundant information of SEGMENT LIST in SRH is stripped based on regularity of SRv SID format, and only a change part is carried, so that header overhead is reduced, and compression is realized. Compatibility SRv is to enable the processing of different length SIDs by adding a behavior attribute (color) to indicate the format of the Next SID, thus supporting hybrid programming and processing of different types of SIDs, illustratively, color includes various types of PSP, last segment performing SRH removal operation (ultimate segment POP of the SRH, USP), last segment performing outer IPv6 decapsulation operation (ultimate segment decapsulation, USD), continued compression (COC), and shift (Next).

The SIDs in SRv fields are each assigned from a block of SID addresses, and thus all have a Common Prefix (CP). If the SID in the destination address of the IPv6 header already carries the public prefix, then the SID in the SRH only needs to carry the difference part, so that when the address is updated, the difference part is updated to the destination address of the IPv6 header, and the original SID can be completely restored, and the difference part is called a generic SID (G-SID) in the generic SRv6 (Generalized SRv6 Network Programming, G-SRv 6). The relationship of a full SID and a 32 bit (bit) G-SID is shown in FIG. 6, with Arguments or blank Padding (Padding) also provided in the SID.

3. Adhesion ability

The Binding SID is used to provide network expansion capability, network internal invisibility, and service independence capability, and in particular, the Binding SID (BSID) is used to identify the entire candidate path (CANDIDATE PATH), provide tunnel connection, traffic steering, etc. If the message carries CANDIDATE PATH the corresponding BSID, it is directed to the corresponding CANDIDATE PATH. If SRv Policy (SRv Policy) is considered a network service, then the Binding SID is the interface to access this service. Therefore, SRv the design of Policy is a subscription publishing model, the business subscribes to network services according to its own needs, and the network can provide interfaces for the connection services he provides to the business.

BSID drainage is a data surface drainage mode and is used for a scene that a service head node and SRv Policy head nodes are not the same node. For example: SRv6 Policy connectivity services are provided across the administrative domains, or SRv6 Policy is provided as a sub-Path scenario for end-to-end Path.

However, different network nodes may support different capabilities, and if a network node does not support a capability, the SID issued by the controller indicates that the network node performs an action that requires supporting the capability, the forwarding path may be blocked.

Illustratively, based on the compression capability, there is a SRv tunnel from node 0 to node 9, as shown in FIG. 7, where head node 0 is vendor A's device, nodes 3 and 5 are vendor B's devices, which sent SIDs containing next. The vendor a device does not support next interworking and cannot compress the 128bit SID issued by the controller in next form. If the controller does not sense that the header node 0 does not support the next compression mode, the label stack issued to the header node 0 contains the node 3 and the node 5, and the flag of the node 3 and the node 5 also has the next attribute, the header node 0 cannot compress the label stack in the next mode, and the SRv tunnel path is not open (down).

Illustratively, based on encapsulation capability, there is a SRv tunnel from 0 to 9 as shown in fig. 8, where head node 0 is an older version of the device, without encap capability. Node 9 is a new version of the device with encap capabilities supporting the release of SIDs of the PSP-USP-USD attribute. If the controller does not sense that the head node 0 does not have encap capability, the label stack issued to the head node 0 contains the node 9, the flag of the node 9 is psp-usp-usd, and the old version head node cannot package the label stack encap, and the SRv tunnel down is not performed.

Illustratively, based on the blocking capability, the controller needs to perceive which node in the network has BSID blocking capability in order to issue BSID. However, the current implementation is to manually specify to which nodes the controller issues the BSID, or the controller reads the SR Policy of the network device and tries to issue the BSID. After the node reports the adhesion capability, the controller is convenient to issue, but when the nodes in the network are many and the hop count is many, the current implementation has the problems of high maintenance cost, long time consumption and the like.

The information transmission method provided by the embodiment of the application is described below with reference to the application scenario.

The term "send information to … (e.g., node) and send information to …" in the present application is understood to mean that the destination of the information is the node. May include directly or indirectly sending information to the node. "receiving information from … (e.g., a node)/receiving information sent …" may be understood as the source of the information being a node, and may include receiving information directly or indirectly from the node. The information may be subjected to necessary processing, such as format change, etc., between the source and destination of the information transmission, but the destination can understand the valid information from the source. Similar expressions in the present application can be understood similarly, and will not be described here again.

It will be appreciated that in the schematic diagram of the method of the present application, the controller and the network node are taken as the execution bodies of the interactive schematic to illustrate the method, but the present application is not limited to the execution bodies of the interactive schematic. For example, the controller in the figures may be a chip, a system on a chip, or a processor that supports the method of implementing the controller, or may be a logic node, a logic module, or software that can implement all or part of the functions of the controller; the network node in the figure may also be a chip, a system-on-chip, or a processor supporting the network node implementation method, or may also be a logic node, a logic module, or software capable of implementing all or part of the network node functions.

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

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

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

The information transmission method may be applied to a network as shown in fig. 1, for example, the node PE3 is a first node, where the first node sends capability information to the controller, where the capability information includes a behavior capability supported by the first node, and after receiving the capability information, the controller issues a first segment list based on the capability information when it needs to issue the first segment list to the first node, where the first segment list includes one or more first segment identifiers, and the behavior capability required by the behavior attribute of the one or more first segment identifiers issued by the controller to the first node does not include the behavior capability that is not supported by the first node.

The behavior capability supported by the first node includes at least one of compression capability, encapsulation capability and adhesion capability, and specifically, the reported behavior capability includes, but is not limited to, G-SID32bit compression capability, G-SID16bit compression capability, micro SID (u SID) 16bit compression capability, uSID bit compression capability, insert, encap or reduce encapsulation capability, binding SID adhesion capability, and the like. The capability information may be included in a type-length-value (TLV), a sub-TLV, or a sub-TLV that are newly added under a preset communication protocol, and the controller and the first node may communicate based on the preset communication protocol, which will be described in detail below based on different communication protocols, respectively.

1. Intermediate System-to-intermediate System protocol (INTERMEDIATE SYSTEM-to-INTERMEDIATE SYSTEM, IS-IS)

Based on the ISIS protocol, a class of sub-TLVs (sub-TLVs) can be added under the sub-TLVs (sub-TLVs) of No. 25 IS-IS routing capability (Router Capability) of No. SRv Capabilities in the protocol number, and the class of sub-TLVs (sub-TLVs) are used for carrying supported behavior Capabilities such as SRv compression, encapsulation, binding SID adhesion and the like, namely capability information, so that the supported behavior Capabilities such as SRv compression, encapsulation, binding SID adhesion capability and the like of the first node are issued, analyzed, flooded (synchronized) and the like in the hierarchy (level) of the ISIS.

Wherein SRv Capabilities sub-TLV the newly extended sub-sub TLV includes, but is not limited to, the following form of sub-sub TLV: a 32bit compression capability sub-sub TLV, a 16bit compression capability sub-sub TLV, an encapsulation capability sub-sub TLV, a bonding SID adhesion capability sub-sub TLV and the like. Wherein, the length of the compressed SID is fixed to be 32 bits by 32bit compression, and the length of the compressed SID is fixed to be 16 bits by 16bit compression.

Illustratively, in each sub-sub TLV, specific various behavioral capabilities are identified using bit bits. As shown in fig. 10, each sub-sub TLV has a length (length) of 2, and 16 bits are used to identify such behavior capabilities; or as shown in fig. 11, length is 4, with 32 bits to identify such behavior capabilities.

Further, 32bit compression capabilities include, but are not limited to: 32bit next compression capability (32 bit compression is performed on a group of 128bit SID label stacks issued by a controller according to a next form), 32bit coc compression capability (32 bit compression is performed on a group of 128bit SID label stacks issued by a controller according to a coc form), whether a format after 32bit next compression can be forwarded (whether a SID label stack subjected to 32bit compression according to a next form is issued by a controller or not, whether a node can forward normally), whether a format after 32bit coc compression can be forwarded (whether a SID label stack subjected to 32bit compression according to a coc form is issued by a controller or not, and whether a node can forward normally) and the like.

The 16bit compression capability includes, but is not limited to: 16bit next compression capability (16 bit compression is performed on a group of 128bit SID label stacks issued by a controller according to a next form), 16bit coc compression capability (16 bit compression is performed on a group of 128bit SID label stacks issued by a controller according to a coc form), whether a format after 16bit next compression can be forwarded (whether a SID label stack subjected to 16bit compression according to a next form is issued by a controller or not, whether a node can forward normally), whether a format after 16bit coc compression can be forwarded (whether a SID label stack subjected to 16bit compression according to a coc form is issued by a controller or not, and whether a node can forward normally) and the like.

Packaging capabilities include, but are not limited to: encap, insert, reduce, et al, binding SID blocking capabilities include, but are not limited to: the adhesive capability of the node.

2. Version 3 open shortest path first protocol (open shortest PATH FIRST V, OSPF 3)

Based on the OSPFv3 protocol, under the SRv Capabilities TLV of the OSPFv3 Router Information LSA (for describing all interface conditions of the node) in the protocol number, the supported behavior Capabilities such as SRv compression, encapsulation, binding SID adhesion capability and the like carried in a sub TLV of a new class can be added, so that the supported behavior Capabilities such as SRv compression, encapsulation, binding SID adhesion capability and the like of the first node can be issued, parsed, flooded and the like in the area (area) of the OSPFv 3.

SRv6 Capabilities TLV the newly extended sub TLV includes, but is not limited to, the following form of sub TLV: a 32bit compression capability sub TLV, a 16bit compression capability sub TLV, an encapsulation capability sub TLV, a Binding SID adhesion capability sub TLV and the like. In each sub TLV, specific various capabilities are identified using bit bits.

Illustratively, as shown in FIG. 12, each sub TLV, length, is 4, with 32 bits to identify such behavioral capabilities. Specific examples of 32bit compression capability, 16bit compression capability, encapsulation capability, and bonding SID blocking capability are referenced in the corresponding descriptions of the ISIS protocol.

3. Border gateway link status protocol (border gateway protocol-LINK STATE, BGP-LS)

Based on BGP-LS protocol, the behavior capabilities of the first node such as SRv compression, encapsulation, binding SID adhesion capability and the like can be reported to the controller by the BGP-LS at the first node deployed with BGP-LS. The newly extended top-level (top-level) TLVs include, but are not limited to, the following forms of top-level TLVs: a 32bit compression capability sub TLV, a16 bit compression capability sub TLV, an encapsulation capability sub TLV, a Binding SID adhesion capability sub TLV and the like.

Illustratively, referring collectively to FIG. 12, in each sub-TLV, specific various behavioral capabilities are identified using bit bits. Each sub TLV, length, is 4, with 32 bits to identify such capability. Specific examples of 32bit compression capability, 16bit compression capability, encapsulation capability, and bonding SID blocking capability are referenced in the corresponding descriptions of the ISIS protocol.

4. Path computation element communication protocol (path computation element communication protocol, PCEP)

Based on the PCEP protocol, the behavior capabilities of SRv compression, encapsulation, binding SID adhesion capability and the like supported by the first node can be reported to the controller by the PCEP at the first node deployed with the PCEP. This behavior CAPABILITY will be carried in a sub-TLV added under the PATH-SETUP-TYPE-CAPABILITY TLV number 34 (a TLV for indicating support of the CAPABILITY to create PATHs) in the protocol number.

The newly extended sub TLVs of the pat-SETUP-TYPE-CAPABILITY TLV number 34 include, but are not limited to, the following forms of sub TLVs: a 32bit compression capability sub TLV, a 16bit compression capability sub TLV, an encapsulation capability sub TLV, a Binding SID adhesion capability sub TLV and the like.

Illustratively, referring collectively to FIG. 12, in each sub-TLV, specific various behavioral capabilities are identified using bit bits. Each sub TLV, length, is 4, with 32 bits to identify such behavior capabilities.

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

For the first node which announces the capability information such as SRv compression, encapsulation, binding SID adhesion capability and the like supported by the first node, the controller issues a SRv SID label stack to the first node based on the received capability information such as SRv compression, encapsulation, binding SID adhesion capability and the like supported by the first node, namely issues SL, wherein the SID of the SRv label stack issued by the controller to the first node does not contain the SID of SRv compression, encapsulation, binding SID adhesion capability and the like not supported by the first node, and the SID of the SRv label stack issued by the controller to the first node does not contain the behavior capability such as SRv compression, encapsulation, binding SID adhesion capability and the like not supported by the first node. For a node that does not advertise its own capability information of supported SRv compression, encapsulation, binding SID blocking capabilities, the controller will issue an SR Policy tag stack to that node according to the original Policy.

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

Optionally, as shown in fig. 13, in a scenario based on communication in the above IS-IS protocol, OSPFv3 protocol, or BGP-LS protocol, the first node may further receive capability information reported from the remote node and send the capability information to the controller together, that IS, the capability information sent by the first node further includes behavior capabilities supported by the second node, where the controller may send, in addition to the first section list to the first node according to the capability information, the first section list may also send, in addition to the second section list to the second node according to the capability information, the second section list including one or more second section identifiers, where the behavior capabilities required by the behavior attribute of the one or more second section identifiers do not include behavior capabilities not supported by the second node.

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

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

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

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

It should be appreciated that the order of execution of steps 203 and 204 is not limited.

An information transmission method provided by the embodiment of the present application will be described with reference to an example.

As shown in fig. 14, in an upgrade scenario of network nodes, each network node is within an interior gateway protocol (interior gateway protocol, IGP) domain, and uses SRv compression, encapsulation, binding SID-blocking, etc. capabilities supported by IGP protocol flooding. The node deployed with BGP-LS reports the capability information of compression, encapsulation, binding SID adhesion and the like of the self node and the received SRv supported by the remote node to the controller. The controller issues SID label stacks to the nodes based on received SRv compression, encapsulation, binding SID blocking and other capability information supported by the nodes.

The header node 0 is an old version device, does not support next compression capability and does not support encap encapsulation capability, the node 0 analyzes, publishes and floods the supported capability information in an IGP domain through the above ISIS/OSPFv3 extension protocol, and reports the supported capability information to the controller through BGP-LS extension protocol, wherein the capability information supported by the node 0 does not include next compression capability and encap encapsulation capability, and the controller issues an SR Policy tag stack to the node based on the capability information, where the tag stack will not contain a SID with usp and next behavior attribute.

Then, the head node 0 is upgraded to a new version device, the next compression capability is supported, encap encapsulation capability is supported, the capability information of the next compression capability and the encap encapsulation capability is analyzed, released and flooded in an IGP domain through an ISIS/OSPFV3 expansion protocol, the information is reported to a controller through a BGP-LS expansion protocol, and the controller issues an SR Policy label stack to the node, wherein the label stack can contain SIDs with usp and next behavior attributes. In the embodiment of the application, the controller receives the behavior capability supported by the first node and reports the behavior capability to the first node, and issues the first segment list to the first node according to the supported behavior capability, wherein the first segment list comprises one or more first segment identifiers, that is, before the controller sends the segment list to the node, the controller determines the behavior capability supported by the node and the behavior capability required by each segment identifier in the segment list, and issues the segment list only when the node has the behavior capability required by each segment identifier, so that the forwarding path is ensured not to be invalid.

Having described the information transmission method provided by the embodiment of the present application, the related devices provided by the embodiment of the present application are described below with reference to the accompanying drawings.

Referring to fig. 15, an embodiment of a controller 1500 according to the present application includes:

a receiving unit 1501, configured to receive capability information reported by a first node, where the capability information includes behavior capabilities supported by the first node; the receiving unit 1501 may be used to perform step 101 or step 202 in the foregoing method embodiment.

The sending unit 1502 is configured to send a first segment list to a first node according to the capability information, where the first segment list includes one or more first segment identifiers. The sending unit 1502 may be configured to perform step 102 or step 203 in the foregoing method embodiments.

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

Optionally, the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

Optionally, the controller 1500 and the first node communicate based on a preset communication protocol, where the preset communication protocol includes any one of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

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

Optionally, the capability information further includes a behavior capability supported by the second node, where the behavior capability supported by the second node is a behavior capability that is sent by the second node to the first node, and the sending unit 1502 is further configured to send, to the second node, a second segment list according to the capability information, where the second segment list includes one or more second segment identifiers, and the behavior capability required by the behavior attribute of the one or more second segment identifiers does not include a behavior capability that is not supported by the second node. The sending unit 1502 may also be configured to perform step 204 in the foregoing method embodiment.

The controller 1500 provided in the embodiment of the present application may be understood by referring to the corresponding content of the foregoing information transmission method embodiment, for example, the controller 1500 is a controller in the foregoing information transmission method embodiment, and the detailed description is not repeated here.

Referring to fig. 16, one embodiment of a network node 1600 according to an embodiment of the present application includes:

A transmitting unit 1601, configured to transmit capability information to the controller, where the capability information includes a behavior capability supported by the first node; the sending unit 1601 may be configured to perform step 101 or step 202 in the foregoing method embodiment.

The receiving unit 1602 is configured to receive a first segment list sent by the controller, where the first segment list includes one or more first segment identifiers. The receiving unit 1602 may be configured to perform step 102 or step 203 in the foregoing method embodiments.

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

Optionally, the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

Optionally, the controller and the first node communicate based on a preset communication protocol, where the preset communication protocol includes any one of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

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

Optionally, the receiving unit 1602 is further configured to receive the behavior capabilities supported by the second node and sent by the second node, so that the controller issues a second segment list to the second node according to the capability information, where the capability information further 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 attribute of the one or more second segment identifiers do not include the behavior capabilities not supported by the second node. The receiving unit 1602 may also be adapted to perform step 201 in the method embodiment described above.

The network node 1600 provided in the embodiment of the present application may be understood by referring to the corresponding content of the foregoing information transmission method embodiment, for example, the network node 1600 is the first node or the second node in the foregoing information transmission method embodiment, and the detailed description is not repeated here.

As shown in the controller of fig. 17, a schematic diagram of one possible logic structure of a controller 1700 is provided according to an embodiment of the present application. The controller 1700 includes: a processor 1701, a communication interface 1702, a memory system 1703, and a bus 1704. The processor 1701, communication interface 1702, and storage system 1703 are interconnected by a bus 1704. In an embodiment of the present application, the processor 1701 is configured to control and manage the actions of the controller 1700, for example, the processor 1701 is configured to perform the information transmission method performed by the controller described in the above embodiment. The communication interface 1702 is used to support the controller 1700 for communication. A memory system 1703 for storing program codes and data for controller 1700.

The processor 1701 may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. The processor 1701 may also be a combination that performs computing functions, such as including one or more microprocessors, a combination of digital signal processors and microprocessors, and the like. The bus 1704 may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 17, but not only one bus or one type of bus.

As shown in the network node of fig. 18, a schematic diagram of a possible logic structure of a network node 1800 is provided according to an embodiment of the present application. The network node 1800 comprises: 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 by a bus 1804. In an embodiment of the present application, the processor 1801 is configured to control and manage actions of the network node 1800, for example, the processor 1801 is configured to perform an information transmission method performed by the network node described in the above embodiment. The communication interface 1802 is used to support communication by the network node 1800. A storage system 1803 for storing program code and data for the network node 1800.

The processor 1801 may be a central processor unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. The processor 1801 may also be a combination that implements computing functionality, e.g., comprising one or more microprocessors, a combination of digital signal processors and microprocessors, and the like. The bus 1804 may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 18, but not only one bus or one type of bus.

As shown in fig. 19, an embodiment of the present application further provides a communication system comprising 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 connected to each other through a bus 1914. In an embodiment of the present application, the processor 1911 is configured to control and manage the actions of the controller 1910, for example, the processor 1911 is configured to perform the information transmission method performed by the controller described in the above embodiment. The communication interface 1912 is used to support communication by the controller 1910. A memory system 1913 for storing program codes and data for controller 1910.

The network node 1920 may be a controller as shown in fig. 16 or a network node as shown in fig. 18, e.g. the network node 1920 comprises: a processor 1921, a communication interface 1922, a memory system 1923, and a bus 1924. The processor 1921, the communication interface 1922, and the memory system 1923 are coupled to one another via a bus 1924. In an embodiment of the present application, the processor 1921 is configured to control and manage actions of the network node 1920, for example, the processor 1921 is configured to perform the information transmission method performed by the controller described in the above embodiment. The communication interface 1922 is for supporting communication by the network node 1920. A storage system 1923 for storing program code and data for the network node 1920.

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

In another embodiment of the present application, there is also provided a computer-readable storage medium having stored therein computer-executable instructions which, when executed by at least one processor of a device, perform the information transmission method described in the above embodiment.

In another embodiment of the present application, there is also provided a computer program product comprising computer-executable instructions stored in a computer-readable storage medium; the at least one processor of the apparatus may read the computer-executable instructions from the computer-readable storage medium, and execution of the computer-executable instructions by the at least one processor causes the apparatus to perform the information transmission method described in the above embodiments.

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

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of 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 the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Claims (27)

1. An information transmission method, comprising:

the method comprises the steps that a controller receives capability information reported by a first node, wherein the capability information comprises behavior capability supported by the first node;

the controller issues a first segment list to the first node according to the capability information, wherein the first segment list comprises one or more first segment identifiers.

2. The method of claim 1, wherein the behavioral capabilities required by the behavioral attributes identified by the one or more first segments are exclusive of behavioral capabilities not supported by the first node.

3. The method of claim 1 or 2, wherein the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

4. A method according to any of claims 1-3, wherein the controller and the first node communicate based on a preset communication protocol, the preset communication protocol comprising any of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

5. The method of claim 4, wherein the capability information is contained in a newly added configuration data TLV, sub-TLV, or sub-TLV under the preset communication protocol.

6. The method of any of claims 1-5, wherein the capability information further comprises behavioral capabilities supported by a second node for the second node to send to the first node, the method further comprising:

And the controller issues a second segment list to the second node according to the capability information, wherein the second segment list comprises one or more second segment identifiers, and the behavior capability required by the behavior attribute of the one or more second segment identifiers does not comprise the behavior capability which is not supported by the second node.

7. An information transmission method, comprising:

The method comprises the steps that a first node sends capability information to a controller, wherein the capability information comprises behavior capabilities supported by the first node;

The first node receives a first segment list sent by the controller, wherein the first segment list comprises one or more first segment identifiers.

8. The method of claim 7, wherein the behavioral capabilities required by the behavioral attributes identified by the one or more first segments are exclusive of behavioral capabilities not supported by the first node.

9. The method of claim 7 or 8, wherein the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

10. The method of any of claims 7-9, wherein the controller and the first node communicate based on a preset communication protocol including any of an intermediate system-to-intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

11. The method of claim 10, wherein the capability information is contained in a newly added configuration data TLV, sub-TLV, or sub-TLV under the preset communication protocol.

12. The method according to any of claims 7-11, wherein before the first node sends the capability information to the controller, the method further comprises:

The first node receives the behavior capability supported by the second node and sends the behavior capability supported by the second node to the second node, so that the controller sends a second segment list to the second node according to the capability information, the capability information further comprises the behavior capability supported by the second node, the second segment list comprises one or more second segment identifiers, and the behavior capability required by the behavior attribute of the one or more second segment identifiers does not comprise the behavior capability not supported by the second node.

13. A controller, comprising:

the receiving unit is used for receiving the capability information reported by the first node, wherein the capability information comprises the behavior capability supported by the first node;

And the sending unit is used for sending a first segment list to the first node according to the capability information, wherein the first segment list comprises one or more first segment identifiers.

14. The controller of claim 13, wherein the behavior capabilities required by the behavior attributes identified by the one or more first segments do not include behavior capabilities not supported by the first node.

15. The controller of claim 13 or 14, wherein the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

16. The controller according to any of claims 13-15, wherein the controller and the first node communicate based on a preset communication protocol, the preset communication protocol comprising any of an intermediate system to intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

17. The controller according to claim 16, wherein the capability information is contained in a newly added configuration data TLV, sub-TLV or sub-TLV under the preset communication protocol.

18. The controller according to any of claims 13-17, wherein the capability information further comprises a behavior capability supported by a second node, the behavior capability supported by the second node being the behavior capability supported by the first node, and the sending unit is further configured to issue a second segment list to the second node according to the capability information, the second segment list comprising one or more second segment identities, and the behavior capability not supported by the second node is not included in the behavior capabilities required by the behavior attributes of the one or more second segment identities.

19. A network node, comprising:

a transmitting unit, configured to transmit capability information to the controller, where the capability information includes behavior capabilities supported by the first node;

and the receiving unit is used for receiving the first segment list sent by the controller, and the first segment list comprises one or more first segment identifiers.

20. The node of claim 19, wherein the behavior capabilities required by the behavior attributes identified by the one or more first segments do not include behavior capabilities not supported by the first node.

21. The node of claim 19 or 20, wherein the behavioral capabilities supported by the first node include at least one of compression capabilities, encapsulation capabilities, and blocking capabilities.

22. The node of any of claims 19-21, wherein the controller and the first node communicate based on a preset communication protocol including any of an intermediate system-to-intermediate system ISIS protocol, a release 3 open shortest path first OSPFv3 protocol, a BGP link state BGP-LS protocol, or a path computation element communication PCEP protocol.

23. The node of claim 22, wherein the capability information is contained in a newly added configuration data TLV, sub-TLV, or sub-TLV under the preset communication protocol.

24. The node according to any of claims 19-23, wherein the receiving unit is further configured to receive the behavior capabilities supported by the second node and sent by the second node, so that the controller issues a second segment list to the second node according to the capability information, where the capability information further includes the behavior capabilities supported by the second node, and the second segment list includes one or more second segment identifiers, where 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.

25. A controller, comprising: a processor, a communication interface, and a memory for storing program code, the processor for invoking the program code in the memory to cause the controller to perform the method of any of claims 1-6.

26. A network node, comprising: a processor, a communication interface and a memory for storing program code, the processor for invoking the program code in the memory to cause the network node to perform the method of any of claims 7-12.

27. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1-6 or 7-12.