Resource-aware partition information transmission method, storage medium, and electronic apparatus

Abstract

Provided in the embodiments of the present disclosure are a resource-aware partition information transmission method, a storage medium, and an electronic apparatus. The method comprises: by means of a first extension protocol, sending to a target device a control message that carries resource-aware partition information, such that the target device acquires the resource-aware partition information on the basis of the control message.

Description

Resource sensing distinguishes between information transmission methods, storage media, and electronic devices.

[0001] Cross-reference of related applications

[0002] This disclosure is based on and claims priority to Chinese patent application CN202410674188.1, filed on May 28, 2024, entitled “Resource Perception Differentiation Information Transmission Method, Storage Medium and Electronic Device”, and incorporates the entire contents of that patent application by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a resource-aware differentiation information transmission method, storage medium, and electronic device. Background Technology

[0004] The core requirement of 5G slicing for the transport network is that different slices correspond to dedicated transport sub-networks. These dedicated transport sub-networks can achieve hard resource isolation or soft isolation with near-hard isolation effects. Traditional packet networks support statistical multiplexing instead of hard isolation, which is more economical than dedicated transport sub-networks or Time Division Multiplexing (TDM) networks. Due to the requirements of 5G slicing, packet networks need to isolate resources at the underlying network level to meet the needs of different overlay services, such as Virtual Private Network (VPN) services. Several solutions have been proposed for isolating resources at the underlying network level, including flexible algorithm identification and packet-carrying Network Resource Awareness (NRP) IDs. For IPv6 networks, there are three methods:

[0005] The first method involves the IPv6 hop-by-hop option header (HBH) carrying a Network Resource Partition ID (NRP ID) in its options. The second method uses the IPv6 source address scheme, where the NRP ID is encapsulated in the source address field of the IPv6 header to identify the NRP ID to which the datagram belongs. The third method, based on the IPv6 header defined in Request for Comments (RFC) 8200, reserves one bit in the Traffic Class field of the IPv6 header. Setting this bit indicates that the NRP ID is carried in the Flow Label field of the header, with a portion of the Flow Label field representing the NRP ID. For Multi-Protocol Label Switching (MPLS) networks, the traditional approach uses MPLS Network Actions (MNAs) to carry NRP IDs (e.g., draft-li-mpls-mna-nrp-selector-00). For network resource awareness differentiation, various NRP ID encoding formats are defined, such as 13-bit NRP ID encapsulation, 20-bit NRP ID encapsulation, and 20-bit entropy tag and NRP ID formats. The method of carrying the Network Resource Awareness Differentiation Identifier (NRP ID) in data packets is used to determine the reserved resources (specifically, sub-interfaces or channels) of a slice under an interface. After a service packet arrives, the device determines the next hop and outgoing interface based on the destination address, then determines the resources under the outgoing interface based on the NRP ID, and finally forwards the service packet using the corresponding resource-reserved sub-interface or channel.

[0006] In end-to-end resource assurance scenarios, multiple Interior Gateway Protocol (IGP) or Border Gateway Protocol (BGP) domains are involved, with each domain independently deploying network resource differentiation identifiers or flexible algorithm schemes. To achieve end-to-end resource assurance, network devices need to establish end-to-end resource assurance paths based on resource-aware mapping relationships. However, related technologies do not address the generation and announcement of resource-aware mapping relationships. Summary of the Invention

[0007] This disclosure provides a resource-aware differentiation information transmission method, storage medium, and electronic device to at least solve the problem of the lack of resource-aware mapping relationship generation and notification in related technologies.

[0008] According to one embodiment of this disclosure, a method for transmitting resource-aware differentiation information is provided for a network device, comprising: sending a control message carrying resource-aware differentiation information to a target device via a first extended protocol, so that the target device obtains the resource-aware differentiation information according to the control message.

[0009] According to another embodiment of this disclosure, a method for transmitting resource-aware differentiation information is provided for network management or a controller, comprising: sending a control message carrying resource-aware differentiation information to a network device via a second extended protocol, so that the network device obtains the resource-aware differentiation information according to the control message.

[0010] According to another embodiment of this disclosure, a method for transmitting resource-aware differentiation information is provided for a network device, comprising: sending a control message carrying resource-aware differentiation information to a target device via an Interior Gateway Protocol (IGP), so that the target device obtains the resource-aware differentiation information according to the control message.

[0011] According to another embodiment of this disclosure, a method for transmitting resource-aware differentiation information is provided for a network device, comprising: sending a control message carrying resource-aware differentiation information to a controller via a southbound interface protocol, so that the controller obtains the resource-aware differentiation information according to the control message.

[0012] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0013] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0014] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program / instructions that, when executed by a processor, implement the steps in any of the above method embodiments. Attached Figure Description

[0015] Figure 1 is a hardware structure block diagram of a computer terminal for a resource-aware differentiation information transmission method according to an embodiment of the present disclosure.

[0016] Figure 2 is a flowchart of a resource-aware differentiation information transmission method according to an embodiment of the present disclosure;

[0017] Figure 3 is another flowchart of the resource-aware differentiation information transmission method according to an embodiment of the present disclosure;

[0018] Figure 4 is another flowchart of the resource-aware differentiation information transmission method according to an embodiment of the present disclosure;

[0019] Figure 5 is another flowchart of the resource-aware differentiation information transmission method according to an embodiment of the present disclosure;

[0020] Figure 6 is a flowchart of a resource awareness differentiation information transmission method based on the IGP protocol according to an embodiment of this disclosure;

[0021] Figure 7 is a flowchart of a resource awareness and differentiation capability information transmission method based on the southbound interface protocol according to an embodiment of this disclosure;

[0022] Figure 8 is an example diagram of the molecular TLV format of the resource awareness region based on the ISIS protocol;

[0023] Figure 9 is an example diagram of the molecular TLV format of the resource-aware region based on the BGP-LS protocol;

[0024] Figure 10 is an example diagram of another resource awareness region molecular TLV format based on the ISIS protocol;

[0025] Figure 11 is an example diagram of another resource-aware region molecular TLV format based on the BGP-LS protocol;

[0026] Figure 12 is an example diagram of another resource-aware region molecular TLV format based on the ISIS protocol;

[0027] Figure 13 is an example diagram of another resource-aware region molecular TLV format based on the BGP-LS protocol;

[0028] Figure 14 is a flowchart of resource awareness differentiation information transmission in an end-to-end resource protection scenario according to an embodiment of this disclosure.

[0029] Figure 15 is a format example diagram of extended community attributes based on the BGP protocol;

[0030] Figure 16 is a format example diagram of extended community attributes based on the BGP-FS protocol;

[0031] Figure 17 is another flowchart of resource awareness differentiation information transmission in an end-to-end resource protection scenario according to an embodiment of this disclosure. Detailed Implementation

[0032] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0034] In some scenarios, IPv6 network nodes support the ability to carry Network Resource Partition IDs (NRP IDs) in packets, which needs to be advertised to the head node and controller, who then encapsulate packets based on this capability. Existing solutions for network resource partitioning include various methods for carrying NRP IDs in packets, but nodes may only partially support them. For example, node 1 supports HBH encapsulation, while node 2 supports HBH and NRP IDs carried by the source address. Therefore, the head node and controller need to obtain the NRP ID encapsulation methods supported by nodes along the path and select the appropriate encapsulation method to ensure that nodes along the path can correctly parse packets and find the corresponding resources for packet forwarding based on the NRP ID.

[0035] The Multi-Protocol Label Switching (MPLS) protocol also defines various encoding methods for network resource awareness and differentiation. Similarly, its head node and controller require the NRP ID encapsulation methods supported by the nodes on the path and select the appropriate encapsulation method to ensure that the nodes on the path can correctly parse the packets and find the corresponding resources for packet forwarding based on the NRP ID.

[0036] In the process of generating a reusable flexible algorithm forwarding table from a resource-aware forwarding table, resource-aware devices need to find the corresponding resource-aware forwarding table based on the mapping relationship between the flexible algorithm identifier and the resource-aware identifier. Currently, there is no solution to achieve this function. The conventional approach is to form a local resource-aware forwarding table by flooding forwarding identifiers and resource-aware identifier information from the control plane.

[0037] In end-to-end resource assurance scenarios, multiple IGP or BGP domains are involved, with each domain independently deploying network resource awareness identifiers or flexible algorithm schemes. For example, one IGP domain might use a flexible algorithm for isolation, while another IGP domain might use an IPv6 hop-by-hop option header carrying an NRP ID for isolation. Therefore, in such scenarios, an end-to-end path needs to be established to meet the resource requirements of the business. To achieve end-to-end resource assurance, domain boundary nodes also need to establish end-to-end resource assurance paths based on the mapping relationship between resource-aware identifiers and flexible algorithms.

[0038] In some cases, traditional IPv6 and MPLS advertisements do not include relevant capability resource information advertisements. Currently, only HBH (Host-Based Hierarchical) is accepted by the working group in the standard scheme. Based on this, the head node or controller can encapsulate packets according to the known capabilities. When different network nodes support different NRP ID encapsulation formats, operators prioritize according to local policies. For example, they can choose the NRP ID encapsulation format supported by the most network nodes. If the number of supported encapsulation formats is not significantly different, priorities can be set, such as prioritizing the source address carrying resource-aware identifier scheme. Generally, network devices support one or more unified encapsulation methods during network deployment, but operators can choose a specific encapsulation method according to their policies. If a small number of network nodes do not support the NRP ID encapsulation format selected by the head node / controller, the unsupported network nodes only need to ignore the identifier and will not find the sub-interface corresponding to the NRP ID for forwarding. However, they will still find the outgoing interface based on the destination. Since resource guarantees are not implemented on this node, the transmission of resource-aware information will not be affected.

[0039] This embodiment generates a reusable flexible algorithm forwarding table based on a resource-aware forwarding table. Each resource-aware device needs to know the mapping relationship between the flexible algorithm identifier and the resource-aware identifier in order to find the corresponding resource-aware forwarding table and be able to reuse the corresponding flexible algorithm forwarding table.

[0040] The methods and embodiments provided in this disclosure can be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking a computer terminal as an example, FIG1 is a hardware structure block diagram of a computer terminal for a resource-aware differentiation information transmission method according to an embodiment of this disclosure. As shown in FIG1, the computer terminal may include one or more (only one is shown in FIG1) processors 102 (processors 102 may include, but are not limited to, microprocessors MCUs or programmable logic devices FPGAs, etc.) and a memory 104 for storing data. The computer terminal may also include a transmission device 106 for communication functions and an input / output device 108. It will be understood by those skilled in the art that the structure shown in FIG1 is only illustrative and does not limit the structure of the computer terminal. For example, the computer terminal may also include more or fewer components than shown in FIG1, or have a different configuration than shown in FIG1.

[0041] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the resource-aware differentiation information transmission method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0042] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0043] This disclosure provides a resource-aware differentiation information transmission method for network devices. Figure 2 is a flowchart of the resource-aware differentiation information transmission method according to this disclosure. As shown in Figure 2, the process includes the following steps:

[0044] Step S202: A control message carrying resource awareness differentiation information is sent to the target device through the first extended protocol, so that the target device can obtain the resource awareness differentiation information according to the control message.

[0045] In one exemplary embodiment, the first extended protocol includes at least one of the following: Interior Gateway Protocol (IGP); Border Gateway Protocol (BGP); Path Computation Element Protocol (PCEP); Border Gateway Protocol Link-State (BGP-LS) protocol; and Border Gateway Flow Specification (BGP-FS) protocol.

[0046] In one exemplary embodiment, the resource-aware differentiation information includes at least one of the following: a mapping relationship between a resource-aware differentiation identifier of the local domain and a flexible algorithm identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a resource-aware differentiation identifier of the local domain; a mapping relationship between a resource-aware differentiation identifier of another domain and an end-to-end resource-aware differentiation identifier; and a mapping relationship between a resource-aware differentiation identifier of another domain and a flexible algorithm identifier of the local domain.

[0047] In one exemplary embodiment, when sending control messages via Intermediate System to Intermediate System (ISIS) in the IGP protocol, resource-aware differentiation information is carried in the ISIS Router-Capability TLV of the control message; or, when sending control messages via Open Shortest Path First (OSPF), resource-aware differentiation information is carried in the OSPF Router Information Link State Advertisement (OSPFv3 Router Information LSA) of the control message; when sending control messages via OSPF-GT in the IGP protocol, resource-aware differentiation information is carried in the top-level application TLV of the control message; or, when sending control messages via ISIS-GT in the IGP protocol, resource-aware differentiation information is carried in the GENINFO TLV of the control message; or, when sending control messages via the PECP protocol, resource-aware differentiation information is carried in the OPEN Object of the control message; or, when sending control messages via the BGP-LS protocol, resource-aware differentiation information is carried in the Node Attribute TLV of the control message. In TLV; or, when control messages are sent via BGP or BGP-FS, resource-aware differentiation information is carried in the BGP community attribute of the control message.

[0048] In one exemplary embodiment, the resource-aware distinguishable encapsulation format is identified by controlling the Flag bit at at least one preset position of the Flag field in the extended portion of the message.

[0049] In one exemplary embodiment, the method further includes: receiving a data packet carrying a resource-aware differentiation identifier, obtaining a forwarding path corresponding to the resource-aware differentiation identifier based on resource-aware differentiation information, and forwarding the data packet according to the forwarding path.

[0050] In one exemplary embodiment, the method further includes: receiving a prefix segment identifier (prefix-SID) carrying the resource-aware distinction, obtaining a flexible algorithm identifier according to the mapping relationship between the resource-aware distinction identifier and the flexible algorithm identifier, and modifying the resource-aware distinction prefix-SID to the flexible algorithm's prefix-SID.

[0051] This disclosure provides a resource-aware differentiation information transmission method for network management or controllers. Figure 3 is another flowchart of the resource-aware differentiation information transmission method according to this disclosure. As shown in Figure 3, the process includes the following steps:

[0052] Step S302: A control message carrying resource awareness differentiation information is sent to the network device through the second extended protocol, so that the network device can obtain the resource awareness differentiation information according to the control message.

[0053] In one exemplary embodiment, the second extended protocol includes at least one of the following: Border Gateway Protocol (BGP); Border Gateway Flow Specification (BGP-FS); Network Configuration Protocol (Netconf).

[0054] In one exemplary embodiment, the resource-aware differentiation information includes at least one of the following: a mapping relationship between a resource-aware differentiation identifier and a flexible algorithm identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a resource-aware differentiation identifier of this domain; a mapping relationship between a resource-aware differentiation identifier of another domain and an end-to-end resource-aware differentiation identifier; and a mapping relationship between a resource-aware differentiation identifier of another domain and a flexible algorithm identifier of this domain.

[0055] In one exemplary embodiment, when a control message is sent via the BGP protocol or the BGP-FS protocol, resource-aware differentiation information is carried in the BGP community attribute of the control message; or, when a control message is sent via the Netconf protocol configured by the network device, the format of the Resource-Aware Differentiation Information Advertisement (Yet Another Next Generation, YANG) model is distributed to the network device.

[0056] In one exemplary embodiment, the resource-aware distinguishable encapsulation format is identified by a Flag bit at at least one preset position in the Flag field of the extended portion of the message.

[0057] In one exemplary embodiment, the method further includes: sending a data packet carrying a resource-aware differentiation identifier to a network device, so that the network device obtains a forwarding path corresponding to the resource-aware differentiation identifier based on the resource-aware differentiation information, and forwards the data packet according to the forwarding path.

[0058] In one exemplary embodiment, the method further includes: sending a prefix segment identifier carrying a resource-aware distinction to a network device, so that the network device obtains a flexible algorithm identifier according to the mapping relationship between the resource-aware distinction identifier and the flexible algorithm identifier, and modifies the prefix-SID of the resource-aware distinction to the prefix-SID of the flexible algorithm identifier.

[0059] This disclosure provides a resource-aware differentiation information transmission method for network devices. Figure 4 is another flowchart of the resource-aware differentiation information transmission method according to this disclosure. As shown in Figure 4, the process includes the following steps:

[0060] In step S402, a control message carrying resource awareness differentiation information is sent to the target device via the Interior Gateway Protocol (IGP) so that the target device can obtain the resource awareness differentiation information based on the control message.

[0061] In one exemplary embodiment, the IGP protocol includes at least one of the following: Intermediate System to Intermediate System (ISIS) protocol; Open Shortest Path First (OSPF) protocol; Intermediate System to Intermediate System-Generalized Transport (ISIS-GT) protocol; and Open Shortest Path First-Generalized Transport (OSPF-GT) protocol.

[0062] In one exemplary embodiment, when a control message is sent via the ISIS protocol, the resource awareness information is carried in the ISIS Router-Capability TLV of the control message; or, when a control message is sent via the OSPF protocol, the resource awareness information is carried in the OSPF Link State Advertisement (OSPFv3 Router Information LSA) of the control message; or, when a control message is sent via the ISIS-GT protocol, the resource awareness information is carried in the GENINFO TLV of the control message; or, when a control message is sent via the OSPF-GT protocol, the resource awareness information is carried in the Top-Level Application Type Length value of the control message.

[0063] In one exemplary embodiment, the resource-aware differentiation information includes at least one of the following: resource-aware differentiation capability information supported by the network device; and a data packet encapsulation method supported by the network device that carries resource-aware differentiation information.

[0064] In one exemplary embodiment, the resource-aware differentiation capability information includes at least one of the following: per-resource-aware differentiation per SID; data packet encapsulation resource-aware differentiation identifier.

[0065] In one exemplary embodiment, the network device supports encapsulation methods for data packets carrying resource-aware distinguishing information, including at least one of the following: IPv6 hop-by-hop option header (HBH) encapsulation format; IPv6 source address encapsulation format; IPv6 flow label encapsulation format; 13-bit resource-aware distinguishing identifier encapsulation format; 20-bit resource-aware distinguishing identifier encapsulation format; and 8-bit resource-aware distinguishing identifier encapsulation format.

[0066] In one exemplary embodiment, resource awareness discrimination information is identified by a Flag bit at at least one preset position in the Flag field of the extended portion of the control message.

[0067] This disclosure provides a resource-aware differentiation information transmission method for network devices. Figure 5 is another flowchart of the resource-aware differentiation information transmission method according to this disclosure. As shown in Figure 5, the process includes the following steps:

[0068] Step S502: A control message carrying resource awareness differentiation information is sent to the controller via the southbound interface protocol, so that the controller can obtain the resource awareness differentiation information based on the control message.

[0069] In one exemplary embodiment, the southbound interface protocol includes at least one of the following: Path Computation Element (PCEP) protocol; Border Gateway Link State BGP-LS protocol; and Network Device Configuration Netconf protocol.

[0070] In one exemplary embodiment, when a control message is sent via the PECP protocol, resource-aware differentiation information is carried in the OPEN Object of the control message; or, when a control message is sent via the BGP-LS protocol, resource-aware differentiation information is carried in the Node Attribute TLV value of the control message.

[0071] In one exemplary embodiment, the resource-aware differentiation information includes at least one of the following: resource-aware differentiation capability information supported by the network device; and a data packet encapsulation method supported by the network device that carries the resource-aware differentiation information.

[0072] In one exemplary embodiment, the resource-aware differentiation capability information includes at least one of the following: per-resource-aware differentiation per SID; data packet encapsulation resource-aware differentiation identifier.

[0073] In one exemplary embodiment, the network device supports the following encapsulation methods for data packets carrying the resource-aware distinguishing information: IPv6 hop-by-hop option header (HBH) encapsulation format; IPv6 source address encapsulation format; IPv6 flow label encapsulation format; 13-bit resource-aware distinguishing identifier encapsulation format; 20-bit resource-aware distinguishing identifier encapsulation format; and 8-bit resource-aware distinguishing identifier encapsulation format.

[0074] In one exemplary embodiment, resource awareness discrimination information is identified by a Flag bit at at least one preset position in the Flag field of the extended portion of the control message.

[0075] The above steps provide a method for transmitting resource-aware differentiation information. A control message carrying resource-aware differentiation information is sent to the target device via a first extended protocol, enabling the target device to obtain the resource-aware differentiation information based on the control message. This solves the problem of the lack of resource-aware mapping relationship generation and notification in related technologies, achieving the generation and notification of resource-aware mapping relationships, and effectively reducing the pressure on control plane flooding forwarding identifiers and resource-aware identifier information.

[0076] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0077] This embodiment also provides a resource-aware differentiation information transmission device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0078] This disclosure provides a resource awareness differentiation information transmission device, which is installed in a network device. The transmission device includes a first sending module, configured to send a control message carrying resource awareness differentiation information to a target device through a first extended protocol, so that the target device can obtain the resource awareness differentiation information according to the control message.

[0079] This disclosure provides a resource awareness differentiation information transmission device, which is installed in a network management system or controller. The transmission device includes a second sending module, configured to send a control message carrying resource awareness differentiation information to a network device through a second extended protocol, so that the network device can obtain the resource awareness differentiation information according to the control message.

[0080] This disclosure provides a resource awareness differentiation information transmission device, which is installed in a network device. The transmission device includes a third sending module, configured to send a control message carrying resource awareness differentiation information to a target device via an Interior Gateway Protocol (IGP), so that the target device can obtain the resource awareness differentiation information based on the control message.

[0081] This disclosure provides a resource awareness differentiation information transmission device, which is installed in a network device. The transmission device includes a fourth sending module, configured to send a control message carrying resource awareness differentiation information to a controller via a southbound interface protocol, so that the controller can obtain the resource awareness differentiation information according to the control message.

[0082] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0083] It should be noted that the aforementioned resource awareness and differentiation information transmission device can be installed in network devices, network management systems, or controllers, or it can be installed independently; no specific limitations are imposed here. In this embodiment, the module division, module function division, and module naming method in the aforementioned resource awareness and differentiation information transmission device are merely illustrative examples and are not subject to specific limitations. In practice, the aforementioned resource awareness and differentiation information transmission device may also include different modules, and the modules may adopt different functional divisions and naming methods, as long as they can implement the steps in the aforementioned resource awareness and differentiation information transmission method embodiments.

[0084] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0085] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0086] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0087] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0088] Embodiments of this disclosure also provide a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps in any of the method embodiments described above.

[0089] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0090] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0091] To enable those skilled in the art to better understand the technical solutions disclosed herein, specific embodiments are described below.

[0092] Example 1

[0093] For the announcement of resource-aware discrimination information, the corresponding IGP, IGP-GT, PCEP, and BGP-LS can be extended and announced accordingly. Resource-aware discrimination capabilities are carried and announced by encapsulating them into TLV or sub-TLV formats.

[0094] Figure 6 is a flowchart of a resource-aware differentiation information transmission method based on the IGP protocol according to an embodiment of this disclosure. As shown in Figure 6, it includes the following steps:

[0095] In step S602, the network device uses the extended IGP protocol / IGP-GT to advertise resource awareness differentiation information to other devices in the network.

[0096] The extended IGP protocol can be either a traditional IGP protocol or an Interior Gateway Protocol-Generalized Transport (IGP-GT) protocol. IGP-GT is a general IGP transport mechanism for non-routing information and is not limited by traditional IGP semantics. IGP-GT neighbors do not need to be directly connected because the information transmitted by IGP-GT is not used for route calculation. It defines an independent sparse topology to propagate resource-aware differentiation information and sends it only to those IGP-GT routers that need it.

[0097] Traditional IGP protocol:

[0098] 1. The ISIS protocol carries resource awareness differentiation information in IS-IS Router-Capability TLV 242.

[0099] 2. The OSPF protocol is carried in the OSPFv3 Router Information LSA.

[0100] IGP-GT protocol:

[0101] 1. The ISIS-GT protocol carries resource awareness and differentiation information in the GENINFO TLV.

[0102] 2. The OSPF-GT protocol carries resource awareness information in the top-level application TLV.

[0103] From a coarse-grained perspective, resource awareness differentiation information includes the device's ability to carry resource awareness differentiation information in data packets and the method of supporting each resource awareness differentiation per SID (not the method of carrying resource awareness differentiation in data packets, but rather the method of announcing the allocation of each SID for each resource awareness differentiation, and relying on the SID to differentiate resources).

[0104] From a fine-grained perspective, this includes the device's announcement of specific data packet encapsulation resource-aware differentiation capabilities. These specific data packet encapsulation resource-aware differentiation capabilities include at least one of the following: IPv6 HBH option encapsulation format, IPv6 source address encapsulation format functionality, encapsulation format functionality in the IPv6 Flow Label field, 13-bit resource-aware differentiation encapsulation format functionality, 20-bit resource-aware differentiation encapsulation format functionality, and 8-bit resource-aware differentiation encapsulation format functionality.

[0105] In one embodiment, the resource-aware differentiation information also includes the mapping relationship between resource-aware differentiation identifiers and flexible algorithms.

[0106] In step S604, after receiving the resource awareness differentiation information, other devices in the network obtain the resource awareness differentiation capability information of the devices in the network.

[0107] After the head node learns that other nodes in the network support multiple encapsulation formats, it selects a suitable encapsulation format and encapsulates the message by setting a certain strategy.

[0108] Example 2

[0109] For the announcement of resource-aware discrimination capability information, the corresponding IGP, IGP-GT, PCE, and BGP-LS can be extended for announcement. Resource-aware discrimination capabilities are announced by encapsulating them into TLV or sub-TLV formats.

[0110] Figure 7 is a flowchart of the resource awareness differentiation capability information transmission method based on the southbound interface protocol according to an embodiment of this disclosure. As shown in Figure 7, it includes the following steps:

[0111] In step S702, the network device sends resource awareness differentiation information to the controller in the network via the southbound interface protocol.

[0112] In one embodiment, the southbound interface protocol includes the PCEP protocol and the BGP-LS protocol.

[0113] PCEP Protocol: Resource awareness information is announced in the OPEN Object of the OPEN message.

[0114] BGP-LS protocol: Resource awareness information is advertised in the Node Attribute TLV.

[0115] In this embodiment of the disclosure, the coarse-grained perspective of resource-aware differentiation information includes the device's ability to carry resource-aware differentiation information in data packets and the method of supporting each resource-aware differentiation per SID (not the method of carrying resource-aware differentiation in data packets, but rather announcing the allocation of each SID for each resource-aware differentiation, and relying on the SID to differentiate resources).

[0116] From a fine-grained perspective, this includes the device's announcement of specific data packet encapsulation resource-aware differentiation capabilities. These specific data packet encapsulation resource-aware differentiation capabilities include at least one of the following: IPv6 HBH option encapsulation format, IPv6 source address encapsulation format functionality, encapsulation format functionality in the IPv6 Flow Label field, 13-bit resource-aware differentiation encapsulation format functionality, 20-bit resource-aware differentiation encapsulation format functionality, and 8-bit resource-aware differentiation encapsulation format functionality.

[0117] In one embodiment, the resource-aware differentiation information also includes the mapping relationship between resource-aware differentiation identifiers and flexible algorithms.

[0118] Step S704: After receiving the resource awareness and differentiation information, the controller obtains the resource awareness and differentiation capability information of the devices in the network.

[0119] Example 3

[0120] Network nodes only advertise support for Resource Awareness Distinguishing Features (RAD) in packet encapsulation, without advertising specific packet encapsulation capabilities. This is useful in certain scenarios, such as when a specific packet encapsulation capability is determined to be used in the network, but the head node / controller still needs to collect information on which nodes in the network support RAD. RAD capabilities can be advertised using extended traditional IGP protocols, or a generic IGP transport mechanism for non-routing information can be used. IGP-GT is not limited by traditional IGP semantics. IGP-GT neighbors do not need to be directly connected because the information transmitted by IGP-GT is not used for route calculation. Therefore, an independent sparse topology can be defined to propagate RAD information and send it only to those IGP-GT routers that need it.

[0121] Figure 8 is an example diagram of the resource-aware zone molecular TLV format based on the ISIS protocol. As shown in Figure 8, a new resource-aware zone molecular TLV is extended for the traditional ISIS protocol. The resource-aware zone molecular TLV is carried in IS-IS Router-Capability TLV 242. The Type field indicates whether resource-aware differentiation capability is supported. Currently, a flag bit is defined: E. E set to 1 indicates that the device supports carrying the resource-aware differentiation identifier in data packets, and E set to 0 indicates that the device supports the method of distinguishing each resource-aware zone from each service identifier (SID).

[0122] In this embodiment of the disclosure, the ISIS general transport mechanism for announcing non-routing information still uses the resource awareness area sub-TLV defined in Figure 8, but the NRP sub-TLV is carried in the GENINFO TLV.

[0123] In this embodiment of the disclosure, for the conventional OSPF protocol, the Resource Awareness Region (TLV) defined in Figure 8 is still used, but the TLV is carried in the OSPFv3 Router Information LSA. For OSPF-GT, the TLV defined in Figure 8 is carried in the top-level application TLV.

[0124] Figure 9 is an example diagram of the TLV format of the resource-aware zone based on the BGP-LS protocol. As shown in Figure 9, the Type field indicates that the resource-aware differentiation capability is supported. Currently, a flag bit is defined: E. Setting E to 1 indicates that the device supports the data packet to carry the resource-aware differentiation identifier, and setting E to 0 indicates that the device supports the method of differentiating each SID for each resource.

[0125] In this embodiment of the disclosure, a new resource awareness differentiation capability TLV is defined for the PCEP protocol. The resource awareness differentiation capability TLV is carried in the OPEN Object, and its specific format is shown in Figure 9 as the resource awareness region molecular TLV format.

[0126] Example 4

[0127] Network nodes support various packet encapsulation resource-aware discrimination capabilities and need to advertise specific packet encapsulation capabilities. Resource-aware discrimination capabilities can be advertised using extended traditional IGP protocols, or they can be transmitted using general IGP transport mechanisms for non-routing information. IGP-GT is not limited by traditional IGP semantics. IGP-GT neighbors do not need to be directly connected because the information transmitted by IGP-GT is not used for route calculation. Therefore, an independent sparse topology can be defined to propagate resource-aware discrimination information and send it only to those IGP-GT routers that require it.

[0128] Figure 10 is an example of another resource-aware zone (RAZ) molecular TLV format based on the ISIS protocol. As shown in Figure 10, a new RAZ molecular TLV is extended for the traditional ISIS protocol. The RAZ molecular TLV is carried in IS-IS Router-Capability TLV 242. The Type field indicates the resource-aware identification capability carried by the data.

[0129] H: Set, indicating that the router has the ability to process IPv6 HBH option encapsulation format.

[0130] S: Set bit, indicating that the router has the function of processing IPv6 source address encapsulation format.

[0131] E: Set, indicating that the router has the ability to process the encapsulation format in the IPv6 Flow Label field.

[0132] S: Set bit, indicating that the router has the ability to process 13-bit resource-aware distinguishing identifier encapsulation format.

[0133] N: Set, indicating that the router has the ability to process 20-bit resource-aware distinguishing identifier encapsulation format.

[0134] C: Set bit, indicating that the router has the function of processing 8-bit resource-aware distinguishing identifier encapsulation format.

[0135] If none of them are set, it means that the device supports the method of distinguishing each SID by each resource awareness.

[0136] In this embodiment of the disclosure, the ISIS general transport mechanism for announcing non-routable information still uses the NRP sub-TLV defined in Figure 10, but it is carried in the GENINFO TLV.

[0137] In this embodiment of the disclosure, for the conventional OSPF protocol, the resource-aware area sub-TLV defined in Figure 10 is carried in the OSPFv3 Router Information LSA. For the OSPF-GT protocol, the NRP sub-TLV defined in Figure 10 is carried in the top-level application TLV.

[0138] Figure 11 is an example diagram of another resource-aware region molecular TLV format based on the BGP-LS protocol. As shown in Figure 11, a new Node Attribute TLV: NRP-Capabilities TLV is defined, where the Type field indicates the data carries resource-aware distinguishing and identifying capabilities.

[0139] H: Set, indicating that the router has the ability to process IPv6 HBH option encapsulation format.

[0140] S: Set bit, indicating that the router has the function of processing IPv6 source address encapsulation format.

[0141] E: Set, indicating that the router has the ability to process the encapsulation format in the IPv6 Flow Label field.

[0142] S: Set bit, indicating that the router has the ability to process 13-bit resource-aware distinguishing identifier encapsulation format.

[0143] N: Set, indicating that the router has the ability to process 20-bit resource-aware distinguishing identifier encapsulation format.

[0144] C: Set bit, indicating that the router has the function of processing 8-bit resource-aware distinguishing identifier encapsulation format.

[0145] If none of them are set, it means that the device supports the method of distinguishing each SID by each resource awareness.

[0146] In this embodiment of the disclosure, a new resource-aware discrimination capability TLV is defined for PCEP, and the resource-aware discrimination capability TLV is carried in the OPEN Object. Its specific format is shown in Figure 11 as the resource-aware region molecular TLV format.

[0147] After the PCEP session is established, the PCC and PCE exchange OPEN messages, which carry the Resource Awareness Differentiation Capability (TLV) as defined in Figure 11. Upon receiving the TLV carrying the TLV, the PCC learns about the PCE's processing capabilities; this is to ensure that the PCE has the ability to encapsulate resource awareness differentiation identifiers. Similarly, upon receiving the TLV carrying the TLV, the PCE learns about the PCC's processing capabilities; this is to ensure that the PCE can guarantee that the encapsulated message carrying the resource awareness differentiation identifier can be processed / recognized by all devices in the path.

[0148] Example 5

[0149] In addition to announcing slicing capabilities, network nodes also need to announce the mapping relationship between resource-aware distinguishing identifiers and flexible algorithms. If a resource-aware forwarding table is generated and reused as a flexible algorithm forwarding table, the mapping relationship between the flexible algorithm identifier and the resource-aware distinguishing identifier is needed to locate the corresponding resource-aware forwarding table. This requires each resource-aware device to be aware of and announce the mapping relationship between the resource-aware distinguishing identifier and the flexible algorithm.

[0150] Figure 12 is an example of another resource-aware region (RAR) molecular TLV format based on the ISIS protocol. As shown in Figure 12, a new RRA molecular TLV is extended for the traditional ISIS protocol. The RRA molecular TLV is carried in IS-IS Router-Capability TLV 242. The Type field indicates the data carries resource-aware distinguishing and identifying capabilities.

[0151] NRP ID: Resource Awareness Distinguishing Identifier.

[0152] Algorithm: The algorithm value for a flexible algorithm, ranging from 128 to 255.

[0153] Context Type: Specifies the type and length of the NRP ID.

[0154] CT=0: NRP ID value is a 13-bit NRP ID;

[0155] CT=1: NRP ID value is a 20-bit NRP ID;

[0156] CT=2: NRP ID value is a 8-bit NRP ID;

[0157] CT-4: NRP ID value is a 32-bit NRP ID;

[0158] Flags: Currently defined in the following ways:

[0159] H: Set, indicating that the router has the ability to process IPv6 HBH option encapsulation format.

[0160] S: Set bit, indicating that the router has the function of processing IPv6 source address encapsulation format.

[0161] E: Set, indicating that the router has the ability to process the encapsulation format in the IPv6 Flow Label field.

[0162] S: Set bit, indicating that the router supports the MPLS Network Operations (MNA) encapsulation format.

[0163] In this embodiment of the disclosure, the ISIS general transport mechanism for announcing non-routing information still uses the resource awareness zone (TLV) defined in Figure 12, but it is carried in the GENINFO TLV.

[0164] In this embodiment of the disclosure, for the conventional OSPF protocol, the resource-aware region (TLV) element defined in Figure 12 is carried in the OSPFv3 Router Information LSA. For OSPF-GT, the resource-aware region (TLV) element defined in Figure 12 is carried in the top-level application TLV.

[0165] In this embodiment of the disclosure, Figure 13 is an example diagram of another resource-aware region molecular TLV format based on the BGP-LS protocol. As shown in Figure 13, for BGP-LS, a new Node Attribute TLV is defined, where the Type field indicates the data carrying resource differentiation identification capability.

[0166] NRP ID: Resource Awareness Distinguishing Identifier.

[0167] Algorithm: The algorithm value for flex algo, ranging from 128 to 255.

[0168] Context Type: Specifies the type and length of the NRP ID.

[0169] CT=0: NRP ID value is 13-bit NRP ID;

[0170] CT=1: NRP ID value is 20-bit NRP ID;

[0171] CT=2: NRP ID value is 8-bit NRP ID;

[0172] CT-4: NRP ID value is 32-bit NRP ID.

[0173] Flags: Currently defined in the following ways:

[0174] H: Set, indicating that the router has the ability to process IPv6 HBH option encapsulation format.

[0175] S: Set bit, indicating that the router has the function of processing IPv6 source address encapsulation format.

[0176] E: Set, indicating that the router has the ability to process the encapsulation format in the IPv6 Flow Label field.

[0177] S: Set bit, indicating that the router supports the MPLS Network Operations (MNA) encapsulation format.

[0178] In this embodiment of the disclosure, the ISIS general transport mechanism for announcing non-routing information still uses the resource awareness zone (TLV) defined in Figure 12, but it is carried in the GENINFO TLV.

[0179] In this embodiment of the disclosure, a new resource-aware differentiation capability TLV is defined for the PCEP protocol, and the resource-aware differentiation capability TLV is carried in the OPEN Object. Its specific format is shown in Figure 13 as the TLV format of the resource-aware region molecule.

[0180] After the PCEP session is established, the PCC and PCE exchange OPEN messages, which carry the Resource Awareness Differentiation Capability (TLV) as defined in Figure 13. Upon receiving the TLV, the PCC learns the mapping relationship between the resource awareness differentiation identifier and the flexible algorithm. When forwarding data packets, the PCC can find the path in the corresponding flexible algorithm based on the resource awareness differentiation identifier. After obtaining the mapping relationship between the resource awareness differentiation identifier and the flexible algorithm, the PCE can use it to calculate the path of the slice in the corresponding flexible algorithm.

[0181] Example 6

[0182] In end-to-end resource assurance scenarios, which span multiple IGP / BGP domains, each domain independently deploys network resource awareness differentiation identifiers or flexible algorithm schemes. In order to achieve end-to-end resource assurance, the boundary nodes of the domains need to establish end-to-end resource assurance paths based on the mapping relationship between resource awareness identifiers and flexible algorithms.

[0183] Figure 14 is a flowchart of resource awareness differentiation information transmission in an end-to-end resource assurance scenario according to an embodiment of this disclosure. As shown in Figure 14, it includes the following steps:

[0184] In step S1402, the boundary node of the domain receives a prefix-SID announcement related to the resource-aware distinction identifier from a domain.

[0185] Step S1404: Based on the mapping relationship between resource-aware differentiation identifiers and flexible algorithms, find the corresponding flexible algorithm identifier and replace it with the relevant prefix-sid announcement of the flexible algorithm.

[0186] The mapping relationship between the resource-aware distinguishing identifier of the boundary node and the flexible algorithm can be announced through the BGP protocol or BGP-FS. In this embodiment of the disclosure, Figure 15 is a format example diagram of the extended community attribute based on the BGP protocol. As shown in Figure 15, a new extended community attribute is defined for the BGP protocol: the resource-aware mapping relationship community attribute.

[0187] In this embodiment of the disclosure, for the BGP-FS protocol: the function is to match the slice ID and redirect traffic behavior to a flexible algorithm path. Figure 16 is a format example diagram of the extended community attribute based on the BGP-FS protocol. As shown in Figure 16, on "FlowSpec Redirect to indirection-id Extended Community", a new ID-Type is extended to represent the flexible algorithm, and Generalized indirection_id carries specific flex-algo information.

[0188] Through the above-described method of this disclosure embodiment, interoperability between resource awareness and flexible algorithms on boundary nodes is achieved, thereby establishing an end-to-end resource awareness path, and the network-wide uniqueness of prefix-sid is guaranteed by the original notification node.

[0189] Example 7

[0190] In end-to-end resource assurance scenarios, spanning multiple IGP / BGP domains, each domain independently deploys network resource awareness distinguishing identifiers or flexible algorithm schemes. Through Example 4, after the end-to-end resource assurance path is established and a resource awareness distinguishing identifier mapping table is formed, the main contents of the resource awareness identifier mapping table include a relationship between different NRP IDs of two IGP / BGP domains, and the process for forwarding packets carrying the resource awareness distinguishing identifier scheme.

[0191] Figure 17 is another flowchart of resource awareness differentiation information transmission in an end-to-end resource assurance scenario according to an embodiment of this disclosure. As shown in Figure 17, it includes the following steps:

[0192] Step S1702: The boundary node of the domain receives a data packet carrying a resource-aware distinguishing identifier from a domain.

[0193] Step S1704: Locate the resource-aware differentiation identifier mapping relationship to find the corresponding flexible algorithm identifier, thereby finding the forwarding path of the corresponding flexible algorithm.

[0194] In summary, this disclosure provides a method for transmitting resource-aware differentiation information. The network controller senses the resource-aware differentiation information supported by network devices through a southbound interface protocol, including the mapping relationship between resource-aware differentiation identifiers and flexible algorithms, and the node's resource-aware differentiation identifier encapsulation capability. The network devices advertise their own node's resource-aware differentiation information to other devices through IGP / IGP-GT protocol extensions, including the mapping relationship between resource-aware differentiation identifiers and flexible algorithms, and the node's resource-aware differentiation identifier encapsulation capability.

[0195] The above description is merely a preferred embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for transmitting resource-aware differentiation information, comprising: sending a control message carrying resource-aware differentiation information to a target device through a first extended protocol, so that the target device acquires the resource-aware differentiation information according to the control message.

2. The method of claim 1, wherein, The first extended protocol comprises at least one of: an Interior Gateway Protocol (IGP) ; a Border Gateway Protocol (BGP) ; a Path Computation Element Protocol (PCEP) ; a Border Gateway Link State (BGP-LS) ; a Border Gateway Flow Specification (BGP-FS).

3. The method of claim 1, wherein, The resource-aware differentiation information comprises at least one of: a mapping relationship between a resource-aware differentiation identifier and a flexible algorithm identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a resource-aware differentiation identifier of a local domain; a mapping relationship between a resource-aware differentiation identifier of another domain and an end-to-end resource-aware differentiation identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a flexible algorithm identifier of a local domain. 4.The method of claim 2, wherein, in the case of sending the control message through ISIS in the IGP protocol, the resource-aware differentiation information is carried in an ISIS Router-Capability Type Length Value (IS-IS Router-Capability TLV) of the control message; or, in the case of sending the control message through the OSPF protocol, the resource-aware differentiation information is carried in an OSPFv3 Router Information Link State Advertisement (OSPFv3 Router Information LSA) of the control message; in the case of sending the control message through OSPF-GT in the IGP protocol, the resource-aware differentiation information is carried in a top-level application TLV of the control message; or, in the case of sending the control message through ISIS-GT in the IGP protocol, the resource-aware differentiation information is carried in a General Information Type Length Value (GENINFO TLV) of the control message; or, in the case of sending the control message through the PCEP protocol, the resource-aware differentiation information is carried in an OPEN Object of the control message; or, in the case of sending the control message through the BGP-LS protocol, the resource-aware differentiation information is carried in a Node Attribute Type Length Value (Node Attribute TLV) of the control message; or, in the case of sending the control message through the BGP protocol or BGP-FS protocol, the resource-aware differentiation information is carried in a BGP community attribute of the control message. 5.The method of claim 3, wherein, an encapsulation format of the resource-aware differentiation is identified by a Flag bit in at least one preset position of a Flag field of an extended part of the control message.

6. The method of claim 3, wherein, Further comprising: receiving a data packet carrying the resource-aware differentiation identifier, obtaining a forwarding path corresponding to the resource-aware differentiation identifier according to the resource-aware differentiation information, and forwarding according to the forwarding path.

7. The method of claim 3, wherein, Further comprising: receiving a prefix segment identifier (prefix-SID) carrying the resource-aware differentiation, obtaining the flexible algorithm identifier according to the mapping relationship between the resource-aware differentiation identifier and the flexible algorithm identifier, and modifying the prefix-SID to the prefix-SID of the flexible algorithm.

8. A resource-aware differentiation information transmission method, used for a network management or controller, comprising: sending a control message carrying resource-aware differentiation information to a network device through a second extended protocol, so that the network device obtains the resource-aware differentiation information according to the control message.

9. The method of claim 8, wherein, The second extended protocol comprises at least one of: a border gateway protocol (BGP); a border gateway flow specification (BGP-FS) protocol; a network device configuration (Netconf) protocol.

10. The method of claim 8, wherein, The resource-aware differentiation information comprises at least one of: a mapping relationship between a resource-aware differentiation identifier and a flexible algorithm identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a resource-aware differentiation identifier of the domain; a mapping relationship between a resource-aware differentiation identifier of another domain and an end-to-end resource-aware differentiation identifier; a mapping relationship between a resource-aware differentiation identifier of another domain and a flexible algorithm identifier of the domain.

11. The method of claim 9, wherein, in the case of sending the control message through the BGP protocol or the BGP-FS protocol, the resource-aware differentiation information is carried in a BGP community attribute of the control message; or, in the case of sending the control message through the network device configuration (Netconf) protocol, the resource-aware differentiation information is issued to the network device in the format of a YANG model.

12. The method of claim 10, wherein, a Flag bit in at least one preset position of a Flag field of an extended part of the control message identifies the encapsulation format of the resource-aware differentiation.

13. The method of claim 10, wherein, Further comprising: sending a data packet carrying the resource-aware differentiation identifier to a network device, so that the network device obtains a forwarding path corresponding to the resource-aware differentiation identifier according to the resource-aware differentiation information, and forwards according to the forwarding path.

14. The method of claim 10, wherein, Further comprising: sending a prefix segment identifier (prefix-SID) carrying the resource-aware differentiation to a network device, so that the network device obtains the flexible algorithm identifier according to the mapping relationship between the resource-aware differentiation identifier and the flexible algorithm identifier, and modifies the prefix-SID of the resource-aware differentiation to the prefix-SID of the flexible algorithm identifier.

15. A resource-aware differentiation information transmission method, used for a network device, comprising: sending a control message carrying resource-aware differentiation information to a target device through an interior gateway protocol (IGP), so that the target device obtains the resource-aware differentiation information according to the control message.

16. The method of claim 15, wherein, The IGP protocol comprises at least one of: Intermediate System to Intermediate System, ISIS, protocol; Open Shortest Path First, OSPF, protocol; Intermediate System to Intermediate System Generalized Traffic, ISIS-GT, protocol; Open Shortest Path First Generalized Traffic, OSPF-GT, protocol.

17. The method of claim 16, wherein, in case that the control message is sent through the ISIS protocol, the resource-aware differentiation information is carried in an ISIS Router-Capability Type Length Value, IS-IS Router-Capability TLV, of the control message; or, in case that the control message is sent through the OSPF protocol, the resource-aware differentiation information is carried in an OSPFv3 Router Information Link State Advertisement, OSPFv3 Router Information LSA, of the control message; or, in case that the control message is sent through the ISIS-GT protocol, the resource-aware differentiation information is carried in a Generalized Information Type Length Value, GENINFO TLV, of the control message; or, in case that the control message is sent through the OSPF-GT protocol, the resource-aware differentiation information is carried in a Top Level Application Type Length Value of the control message.

18. The method of claim 15, wherein, the resource-aware differentiation information comprises at least one of: resource-aware differentiation capability information supported by the network device; encapsulation manner of data packet carrying the resource-aware differentiation information supported by the network device.

19. The method of claim 18, wherein, the resource-aware differentiation capability information comprises at least one of: per-resource-aware differentiation per-SID manner; data packet encapsulation resource-aware differentiation identifier manner.

20. The method of claim 18, wherein, the encapsulation manner of data packet carrying the resource-aware differentiation information supported by the network device comprises at least one of: IPv6 Hop-by-Hop Option Header, HBH, encapsulation format; IPv6 source address encapsulation format; IPv6 flow label encapsulation format; 13-bit resource-aware differentiation identifier encapsulation format; 20-bit resource-aware differentiation identifier encapsulation format; 8-bit resource-aware differentiation identifier encapsulation format.

21. The method of claim 18, wherein, the resource-aware differentiation capability information is identified by a Flag bit at at least one preset position of a Flag field of an extended part of the control message.

22. A resource-aware differentiation information transmission method, for a network device, comprising: sending, through a southbound interface protocol, a control message carrying resource-aware differentiation information to a controller, so that the controller acquires the resource-aware differentiation information according to the control message.

23. The method of claim 22, wherein, the southbound interface protocol comprises at least one of: Path Computation Element Protocol, PCEP, protocol; Border Gateway Link State, BGP-LS, protocol; Network Device Configuration, Netconf, protocol.

24. The method of claim 23, wherein, in case that the control message is sent through the PCEP protocol, the resource-aware differentiation information is carried in an OPEN Object of the control message; Or, in the case of sending the control message through the BGP-LS protocol, the resource-aware differentiation information is carried in a node attribute type length value (Node Attribute TLV) of the control message.

25. The method of claim 22, wherein, The resource-aware differentiation information includes at least one of: Resource-aware differentiation capability information supported by the network device; An encapsulation manner of a data packet carrying the resource-aware differentiation information supported by the network device.

26. The method of claim 25, wherein, The resource-aware differentiation capability information includes at least one of: A per-resource-aware differentiation per SID manner; A data packet encapsulation resource-aware differentiation identifier manner.

27. The method of claim 25, wherein, The encapsulation manner of the data packet carrying the resource-aware differentiation information supported by the network device includes at least one of: An IPv6 hop-by-hop (HBH) option header encapsulation format; An IPv6 source address encapsulation format; An IPv6 flow label encapsulation format; A 13-bit resource-aware differentiation identifier encapsulation format; A 20-bit resource-aware differentiation identifier encapsulation format; An 8-bit resource-aware differentiation identifier encapsulation format.

28. The method of claim 25, wherein The resource-aware differentiation capability information is identified by a flag bit in at least one preset position of a flag field of an extended part of the control message.

29. A computer readable storage medium having stored therein a computer program, wherein, The computer program, when executed by the processor, implements the method recited in any one of claims 1 to 28.

30. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method recited in any one of claims 1 to 28.

31. A computer program product comprising computer programs / instructions, wherein the computer programs / instructions, when executed by a processor, implement the method recited in any one of claims 1 to 28.

Images