A method for generating a forwarding table entry, a controller and a network device
By sending resource allocation request messages to network devices with network shards in 5G networks and generating forwarding tables, resource binding is achieved using segment identifiers, the problems of network shard resource isolation and flexible packet forwarding in 5G networks are solved, and the problem of network shard resource isolation and flexible packet forwarding in 5G networks is met. Differentiated service quality and isolation requirements for different business needs have improved the scalability of network sharding.
Patent Information
- Application Number
- CN202110542648.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2017-06-30
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2037-06-30
AI Technical Summary
5G network technology fails to provide specific flexible message forwarding methods to achieve network sharding resource isolation, and cannot meet the differentiated service quality and isolation requirements of different service needs.
The controller sends a resource allocation request message to the network equipment in the network shard, triggers resource allocation, and generates a forwarding table. The resource is bound by segment identification to achieve flexible message forwarding based on network shards.
It realizes packet forwarding and resource isolation in specific network shards, meets differentiated service quality to meet different service needs, and improves the scalability and flexibility of network shard resources.
Smart Images

Figure CN113364687B_ABST
Abstract
Description
[0001] This application is a divisional application of an application filed with the China Intellectual Property Office on June 30, 2017, with application number 201710527679.3 and invention name “A method for generating forwarding table entries, controller and network device”. Technical Field
[0002] The present invention relates to the field of communications, and in particular to a method for generating a forwarding table entry, a controller and a network device. Background Art
[0003] The vision of 5G (5th generation mobile networks) is to support a variety of new services, such as virtual reality (VR), augmented reality (AR), remote industrial control, autonomous driving and the Internet of Things, by enhancing the capabilities of various aspects of the network. Since different types of services have very different requirements for the network, 5G proposes to divide different logical network slices on the same physical network through network slicing to meet the differentiated needs of different services. For operator networks, network slicing requires the operator network to provide network connections that meet the needs of users and different services between the core network, access network and various service functions. The most critical requirement is that the operator network provides differentiated and guaranteed service quality for different network slices and achieves isolation between slices. This requires the operator network to allocate exclusive network resources to different network slices and achieve isolation between different network slices. However, 5G technology does not provide a specific technical solution to achieve a flexible message forwarding method based on network slice resource isolation. Summary of the invention
[0004] The present application provides a method, a controller and a network device for generating a forwarding table entry, which helps to provide users with a flexible message forwarding method based on network sharding resource isolation.
[0005] In a first aspect, a method for generating a forwarding table entry is provided, comprising:
[0006] The controller sends multiple resource allocation request messages to multiple network devices in a network slice to trigger each of the multiple network devices to perform resource allocation according to the corresponding resource allocation request message. The multiple resource allocation request messages correspond to the multiple network devices one by one. The resource allocation request message includes the identifier of the network slice and the resources that the corresponding network device needs to allocate to the network slice. The resources include device processing resources and / or link resources. The controller receives multiple resource allocation response messages sent by the multiple network devices. The multiple resource allocation response messages correspond to the multiple network devices one by one. The resource allocation response message includes the identifier of the network slice and the segment identifier of the corresponding network device. The segment identifier is used to identify the resources allocated by the corresponding network device to the network slice. The segment identifier includes a node segment identifier and / or an adjacent segment identifier. The resources allocated to each of the multiple network devices belong to the network slice. The controller generates a forwarding table corresponding to the network slice based on the multiple resource allocation response messages, the forwarding table is identified by the network slice identifier, the forwarding table includes forwarding table entries of network devices reaching the network slice, and the forwarding table entries include segment identifiers of destination network devices reaching the forwarding table entries.
[0007] Through the above technical solution, the controller can notify the network devices in the network slice to allocate resources through the resource allocation request message, and bind the allocated resources to the network slice. The network slice can use the network resources, and each network device allocates and allocates the corresponding segment identifier of the network resources. In this way, the controller can establish a forwarding table corresponding to the network slice according to the resource allocation response message sent by each network device, which helps to provide users with a flexible message forwarding method based on network slice resource isolation. This technical solution helps to realize message forwarding in a specific network slice, and because the network device can use the resources allocated to the network slice to process the message through the segment identifier contained in the message. Thus, a flexible message forwarding method based on network slice resource isolation can be realized.
[0008] In a possible implementation manner, before the controller sends multiple resource allocation request messages to multiple network devices in the network slice, the method further includes:
[0009] The controller obtains the network slice from the network according to business requirements, the network slice includes the multiple network devices, and the business requirements include topology requirements and / or user requirements for quality of service.
[0010] In a possible implementation, the method further includes:
[0011] The controller sends the forwarding table to the network device in the network slice. By sending the forwarding table to the network device in the network slice, when a message enters the network slice through the network device, the network device can implement message forwarding based on network slice resource isolation.
[0012] In one possible implementation, the device processing resources include one or more of the following resources: a queue, a memory, a processor, and a network function;
[0013] The link resources include one or more of the following resources: bandwidth, time slot, or sub-interface.
[0014] In a second aspect, a method for generating a forwarding table entry is provided, comprising:
[0015] A first network device obtains a resource allocation request message, the resource allocation request message includes an identifier of a network slice and resources that the first network device needs to allocate to the network slice, the resources including device processing resources and / or link resources. The first network device allocates resources according to the resource allocation request message, and allocates a segment identifier, the segment identifier is used to identify the resources allocated by the first network device to the network slice, the allocated resources belong to the network slice, the allocated resources include device processing resources and / or link resources, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier. The first network device sends a notification message to a second network device to trigger the second network device to generate a forwarding table corresponding to the network slice according to the notification message, the notification message includes the identifier of the network slice and the segment identifier, the forwarding table includes a forwarding table entry of a network device that reaches the network slice, and the forwarding table entry includes a segment identifier of a destination network device that reaches the forwarding table entry.
[0016] The first network device allocates resources according to the resource allocation request message, and binds the allocated resources to the network slice. The network slice can use the network resources. The network device allocates a segment identifier corresponding to the network slice, which can trigger the second network device to establish a forwarding table corresponding to the network slice according to the resource allocation response message sent by each network device, which helps to provide users with a flexible message forwarding method based on network slice resource isolation.
[0017] In a possible implementation manner, the second network device is a controller, and the method further includes:
[0018] The first network device receives the forwarding table sent by the second network device, and the first network device receives a first message, and the first message belongs to the forwarding table. The network device searches for a matching forwarding table entry in the forwarding table with a destination Internet Protocol (IP) address of the first message, and the destination IP address of the forwarding table entry corresponds to the destination IP address of the first message. The network device inserts a segment identifier in the forwarding table entry into a message header of the first message to generate a second message. The network device sends the second message to the network device corresponding to the next hop in the forwarding table entry.
[0019] In a third aspect, a method for generating a forwarding table entry is provided, comprising:
[0020] A first network device receives multiple notification messages sent by multiple network devices in a network slice, wherein the multiple notification messages correspond to the multiple network devices one by one, and the notification messages include an identifier of the network slice and a segment identifier of the corresponding network device, wherein the segment identifier is used to identify the resources allocated by the corresponding network device to the network slice, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier, and the first network device is a network device in the network slice. The first network device generates a forwarding table corresponding to the network slice according to the multiple notification messages, wherein the identifier of the forwarding table is the identifier of the network slice, and the forwarding table includes forwarding table entries of the network devices that reach the network slice, and the forwarding table entries include segment identifiers of the destination network devices that reach the forwarding table entries.
[0021] The first network device serves as the entry node of the network slice and selects a suitable network slice through the forwarding table to forward the message. The intermediate nodes in the network slice do not need to perceive the network slice information related to the message, and the message forwarding is more flexible.
[0022] In a possible implementation, the method further includes:
[0023] The first network device receives a first message, where the first message belongs to the forwarding table;
[0024] The first network device searches for a matching forwarding entry in the forwarding table according to the destination IP address of the first message, where the destination IP address of the forwarding entry corresponds to the destination IP address of the first message;
[0025] The first network device inserts the segment identifier in the forwarding table entry into the message header of the first message to generate a second message;
[0026] The first network device sends the second message to the network device corresponding to the next hop in the forwarding table entry.
[0027] In a fourth aspect, a controller for generating a forwarding table entry is provided, and the controller executes the method in the first aspect or any possible implementation of the first aspect. Specifically, the controller includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.
[0028] In a fifth aspect, a first network device for generating a forwarding table entry is provided, and the first network device executes the method in the second aspect or any possible implementation of the second aspect. Specifically, the first network device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.
[0029] In a sixth aspect, a first network device for generating a forwarding table entry is provided, and the first network device executes the method in the third aspect or any possible implementation of the third aspect. Specifically, the first network device includes a unit for executing the method in the third aspect or any possible implementation of the third aspect.
[0030] In a seventh aspect, a network device is provided, the network device comprising: a processor, a network interface and a memory. The memory can be used to store program code, and the processor is used to call the program code in the memory to execute the method designed in the above aspect. The specific execution steps can be referred to the above aspect, which will not be repeated here.
[0031] In an eighth aspect, a network device is provided, the network device comprising: a main control board and an interface board. The main control board comprises: a first processor and a second memory. The interface board comprises: a second processor, a second memory and an interface card. The main control board and the interface board are coupled. The first memory can be used to store program code, and the first processor is used to call the program code in the first memory to perform the following operations:
[0032] Obtain a resource allocation request message, the resource allocation request message including an identifier of a network slice and resources that the first network device needs to allocate to the network slice, the resources including device processing resources and / or link resources; allocate resources according to the resource allocation request message, and allocate a segment identifier, the segment identifier being used to identify the resources allocated by the first network device to the network slice, the allocated resources including device processing resources and / or link resources, the segment identifier including a segment identifier and / or an adjacent segment identifier, and the allocated resources belong to the network slice.
[0033] The second memory may be used to store program codes, and the second processor is used to call the program codes in the second memory to perform the following operations:
[0034] The trigger interface card sends a notification message to the second network device to trigger the second network device to generate a forwarding table corresponding to the network slice according to the notification message, the notification message includes the identifier of the network slice and the segment identifier, the forwarding table includes a forwarding table entry of the network device reaching the network slice, and the forwarding table entry includes the segment identifier of the destination network device reaching the forwarding table entry.
[0035] In a possible implementation, an inter-process communication (IPC) control channel is established between the main control board and the interface board.
[0036] In a ninth aspect, a computer storage medium is provided for storing computer software instructions for the above-mentioned controller or network device, which includes a program designed for executing the above-mentioned aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solution of the present invention, the following is a brief introduction to the drawings used in the embodiments. Obviously, the following drawings are only drawings of some embodiments of the present invention. For ordinary technicians in this field, other technical solutions and drawings that can also implement the present invention can be obtained based on these drawings without creative work.
[0038] Figure 1 A schematic diagram of an application scenario provided by an embodiment of the present invention;
[0039] Figure 2 A schematic flow chart of a method for generating a forwarding table entry provided by an embodiment of the present invention;
[0040] Figure 3 A schematic flow chart of a method for generating a forwarding table entry provided by an embodiment of the present invention;
[0041] Figure 4 A schematic flow chart of a method for generating a forwarding table entry provided by an embodiment of the present invention;
[0042] Figure 5 A schematic diagram of an application scenario provided by an embodiment of the present invention;
[0043] Figure 6 A schematic diagram of a sub-TLV message provided in an embodiment of the present invention;
[0044] Figure 7 A schematic diagram of a controller provided by an embodiment of the present invention;
[0045] Figure 8 A schematic diagram of the structure of a first network device provided in an embodiment of the present invention;
[0046] Fig. 9 A schematic diagram of the structure of a first network device provided in an embodiment of the present invention;
[0047] Fig.10 A schematic diagram of the structure of a network device provided by an embodiment of the present invention;
[0048] Fig.11 A schematic diagram of the structure of a network device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0049] The embodiments of the present invention are described below in conjunction with the accompanying drawings.
[0050] The embodiment of the present invention provides a method for generating a forwarding table entry and a network device based on the method, which is used to implement resource allocation of network slicing and can also implement a flexible message forwarding method based on network slicing. The method and the network device are based on the same inventive concept. Since the principles of solving problems by the method and the network device are similar, the implementation of the network device and the method can refer to each other, and the repeated parts will not be repeated.
[0051] Figure 1 A possible application scenario of an embodiment of the present invention is shown. In this application scenario, network device 101, network device 102, network device 103, network device 104 and network device 105 form a physical network. Controller 106 controls and manages the network topology. Controller 106 can be a network management device or a controller under a software-defined networking (SDN) architecture. Network devices 101-105 can be routers or switches, respectively, or forwarders under an SDN network architecture. The network slicing in the embodiment of the present invention is a logical network formed by selecting some or all network devices from an actual physical network. For example: Figure 1 In the example, network devices 101-105 form an actual physical network, and network devices 101, 102, 103, 104 and 105 can form a network slice, such as network slice A. In this case, network slice A is an actual physical network topology formed by network devices 101-105. Network devices 101, 102, 103 and 104 can form a network slice, such as network slice B. Network devices 101, 102, 104 and 105 can form a network slice, such as network slice C. Different network slices have different network slice identifiers.
[0052] Combination Figure 1 The application scenario shown is shown in Figure 2, an embodiment of the present invention provides a method for generating a forwarding table entry, the method comprising:
[0053] 201, the controller sends multiple resource allocation request messages to multiple network devices in the network slice to trigger each of the multiple network devices to allocate resources according to the corresponding resource allocation request message, the multiple resource allocation request messages correspond to the multiple network devices one by one, the resource allocation request message includes the identifier of the network slice, the resources that the corresponding network device needs to allocate to the network slice, and the resources include device processing resources and / or link resources. The multiple network devices include Figure 2 Network device 1 to network device n in.
[0054] In a possible implementation manner, before the controller sends multiple resource allocation request messages to multiple network devices in the network slice, the method further includes:
[0055] The controller obtains the network slice from the network according to the service demand, and the network slice includes the plurality of network devices. The service demand includes topology demand and / or user's service quality (QoS) demand. The service demand can be customized by the operator or the user. Optionally, the topology demand specifically refers to the need to consider the actual location of the specific network device or the current load of the network device to select specific network devices to form the network slice when dividing the network into network slices, for example: based on Figure 1 In the scenario shown, the operator needs to exclude network device 103 from the network composed of network devices 101-105, because the geographical location of network device 103 is a war zone and its reliability cannot be guaranteed. Accordingly, the obtained network slice specifically includes network device 101, network device 102, network device 104 and network device 105. Optionally, the service quality requirement is specifically to select some network devices with strong processing capabilities to ensure the service quality of the service, and exclude some network devices with high resource utilization, such as: based on Figure 1 In the scenario shown, network device 104 has better performance and stronger processing capability. When obtaining network slices, network device 104 is preferentially selected as a network device in the network slice. The resource occupancy rate of network device 102 has exceeded 90%. When obtaining network slices, network device 103 is not selected. Therefore, the network slices finally determined include network device 101, network device 103, network device 104 and network device 105.
[0056] 202, the controller receives multiple resource allocation response messages sent by the multiple network devices, the multiple resource allocation response messages correspond to the multiple network devices one by one, the resource allocation response messages include the identifier of the network slice and the segment identifier of the corresponding network device, the segment identifier is used to identify the resources allocated by the corresponding network device to the network slice, the segment identifier includes a node segment identifier and / or an adjacent segment identifier, the resources allocated to each device in the multiple network devices belong to the network slice, and the allocated resources include device processing resources and / or link resources. The node segment identifier is used to identify the allocated device processing resources, and the adjacent segment identifier is used to identify the allocated link resources.
[0057] 203. The controller generates a forwarding table corresponding to the network slice according to the multiple resource allocation response messages, wherein the forwarding table is identified by the network slice identifier, the forwarding table includes forwarding table entries of the network device reaching the network slice, and the forwarding table entries include the segment identifier of the destination network device reaching the forwarding table entries.
[0058] When receiving the corresponding resource allocation request message, each network device in the plurality of network devices allocates resources to the network slice according to the resources required to be allocated to the network slice as contained in the resource allocation request message. Optionally, the forwarding table may include forwarding table entries of each network device reaching the network slice or forwarding table entries of an egress network device.
[0059] In a possible implementation, the device processing resources include one or more of the following resources: a queue, a memory, a processor, and a network function. Accordingly, the network device performs device processing resource allocation including:
[0060] The network device allocates part of the total queue in the device to the network slice for use, or allocates part of the processors from multiple processors to the network slice for use, or allocates part of the memory from the total memory to the network for use. In addition, the network device can divide part of the network functions from the supported network functions, and this part of the network functions can be implemented in the network slice. Specifically: the network device supports functions such as firewall, deep packet inspection (DPI) or network address translation (NAT), and the firewall function can be divided into the network slice, that is, the message can be processed by the firewall after passing through the network slice.
[0061] In a possible implementation, the link resource includes one or more of the following resources: bandwidth, time slot, or sub-interface. Accordingly, the network device performs link resource allocation including:
[0062] The network device allocates part of the bandwidth from the total link bandwidth to the network slice, or allocates part of the time slot from the time slot to the network slice, or divides part of the sub-interfaces from all the sub-interfaces for the network slice.
[0063] In a possible implementation, the network device binds the node segment identifier (Node SID) of the network device and the allocated device processing resources, so that when the received message contains the node segment identifier, the network device can determine that the device resources corresponding to the node segment identifier need to be used to process the message. Optionally, the network device binds the adjacency segment identifier (Adj SID) of the network device and the allocated link resources, so that when the received message contains the adjacency segment identifier, the network device can determine that the link resources corresponding to the adjacency segment identifier need to be used to process the message. Among them, the definition of Node SID and Adj SID can refer to the draft related to Segment Routing (SR) published by the Internet Engineering Task Force (IETF), such as: draft-ietf-spring-segment-routing-11.
[0064] After receiving the resource allocation response message, the controller can establish a forwarding table corresponding to the network slice according to the identifier of the network slice in the resource allocation response message and the segment identifier of the corresponding network device. The identifier or index of the forwarding table is the identifier of the network slice.
[0065] In a possible implementation, the method further includes:
[0066] The controller sends the forwarding table to the network devices in the network slice. After receiving the forwarding table, the network devices in the network slice store the forwarding table, and when receiving a message, they can select the forwarding table according to the matching strategy and forward or process the message through the network slice. Figure 2 The network device 1 in the figure may be the entry network device.
[0067] Through the above technical solution, the controller can notify the network devices in the network slice to allocate resources through the resource allocation request message, and bind the allocated resources to the network slice. The network slice can use the network resources, and each network device allocates a segment identifier corresponding to the network slice. In this way, the controller can establish a forwarding table corresponding to the network slice according to the resource allocation response message sent by each network device, which helps to provide users with a flexible message forwarding method based on network slice resource isolation. This technical solution helps to realize message forwarding in a specific network slice, and because the network device can use the resources allocated to the network slice to process the message through the segment identifier contained in the message. Thus, a message forwarding method based on network slice resource isolation can be realized.
[0068] See also Figure 3 The embodiment of the present invention provides a method for generating a forwarding table entry, the method comprising:
[0069] 301, a first network device obtains a resource allocation request message, the resource allocation request message including an identifier of a network slice and resources that the first network device needs to allocate to the network slice, the resources including device processing resources and / or link resources. The first network device may be Figure 2 The network device 1 in the illustrated embodiment.
[0070] 302. The first network device allocates resources according to the resource allocation request message, and allocates a segment identifier, wherein the segment identifier is used to identify the resources allocated by the first network device to the network slice, the allocated resources belong to the network slice, the allocated resources include device processing resources and / or link resources, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier.
[0071] 303, the first network device sends a notification message to the second network device to trigger the second network device to generate a forwarding table corresponding to the network slice according to the notification message, the notification message includes the identifier of the network slice and the segment identifier, the forwarding table includes a forwarding table entry of the network device reaching the network slice, and the forwarding table entry includes the segment identifier of the destination network device reaching the forwarding table entry.
[0072] In a possible implementation manner, the second network device is Figure 1 or Figure 2 The controller in the embodiment of the present invention, wherein the first network device is a network device in the network slice, and the method further comprises:
[0073] The first network device receives the forwarding table sent by the second network device;
[0074] The first network device receives a first message, where the first message belongs to the forwarding table;
[0075] The network device searches for a matching forwarding entry in the forwarding table according to the destination IP address of the first message, wherein the destination IP address of the forwarding entry corresponds to the destination IP address of the first message;
[0076] The network device inserts the segment identifier in the forwarding table entry into the message header of the first message to generate a second message;
[0077] The network device sends the second message to the network device corresponding to the next hop in the forwarding table entry.
[0078] In a possible implementation manner, the first network device obtaining the resource allocation request message includes: the first network device receiving the resource allocation request message sent by a controller, and the controller may be the second network device.
[0079] In a possible implementation manner, the first network device obtaining the resource allocation request message includes: the first network device receiving the resource allocation request message sent by other network devices in the network slice.
[0080] The first network device allocates resources according to the resource allocation request message, and binds the allocated resources to the network slice. The network slice can use the network resources. The network device allocates and allocates the corresponding segment identifier of the allocated resources. This can trigger the second network device to establish a forwarding table corresponding to the network slice according to the resource allocation response message sent by each network device, which helps to provide users with a flexible message forwarding method based on network slice resource isolation.
[0081] See also Figure 4 , an embodiment of the present invention provides a method for generating a forwarding table entry, the method comprising:
[0082] 401. A first network device receives a plurality of notification messages sent by a plurality of network devices in a network slice, wherein the plurality of notification messages correspond one-to-one to the plurality of network devices, and the notification message includes an identifier of the network slice and a segment identifier of the corresponding network device, wherein the segment identifier is used to identify resources allocated by the corresponding network device to the network slice, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier, and the first network device is a network device of the network slice.
[0083] 402. The first network device generates a forwarding table corresponding to the network slice according to the multiple notification messages, wherein the forwarding table is identified by the identifier of the network slice, the forwarding table includes forwarding table entries of the network device reaching the network slice, and the forwarding table entries include segment identifiers of the destination network devices reaching the forwarding table entries.
[0084] In a possible implementation, the first network device may also generate multiple forwarding table entries according to the multiple notification messages in step 402, wherein the multiple forwarding table entries correspond to the notification messages one by one, wherein each forwarding table entry includes an identifier of a network slice and a segment identifier of the network device sending the notification message.
[0085] In a possible implementation, the method further includes:
[0086] The first network device receives a first message, where the first message belongs to the forwarding table;
[0087] The first network device searches for a matching forwarding entry in the forwarding table according to the destination IP address of the first message, where the destination IP address of the forwarding entry corresponds to the destination IP address of the first message;
[0088] The first network device inserts the segment identifier in the forwarding table entry into the message header of the first message to generate a second message;
[0089] The first network device sends the second message to the network device corresponding to the next hop in the forwarding table entry.
[0090] In a possible implementation manner, the destination IP address of the forwarding entry and the destination IP address of the first message have a corresponding relationship, specifically including:
[0091] The destination IP address of the forwarding entry may be the same as the destination IP address of the first message. In this case, the network device corresponding to the destination address of the first message is the network device corresponding to the destination address of the forwarding entry.
[0092] In a possible implementation manner, the destination IP address of the forwarding entry and the destination IP address of the first message have a corresponding relationship, specifically including:
[0093] The destination IP address of the forwarding table entry may be different from the destination IP address of the first message, but a corresponding relationship is established in advance. At this time, it means that the network device corresponding to the destination address of the forwarding table entry is a hop in the first message reaching the destination network device, that is, the edge device of the network slice. After the first message arrives at the network device corresponding to the destination address of the forwarding table entry, the network device still needs to forward the message according to the traditional forwarding method.
[0094] In a possible implementation manner, the destination IP address of the forwarding entry and the destination IP address of the first message have a corresponding relationship, which specifically includes: the destination IP address of the first message belongs to the network segment corresponding to the destination IP address of the forwarding entry.
[0095] In one possible implementation, a forwarding strategy is pre-configured on the first network device. When the first message is received, the forwarding table to which the first message belongs can be determined based on the information of the first message and the forwarding strategy. The forwarding strategy includes a matching item and a result item. For example, the matching item includes the destination IP address or the source IP address of the first message, and the result item includes the identifier of the network slice. Determining the forwarding table to which the first message belongs based on the forwarding strategy includes: when it is determined that the destination IP address of the first message matches the matching item of the forwarding policy, the identifier of the network slice included in the action item is used to determine the corresponding forwarding table, that is, selecting a forwarding table whose identifier is the identifier of the network slice.
[0096] Optionally, the matching item of the forwarding policy may include port information of the received message. Determining the forwarding table to which the first message belongs according to the forwarding policy includes: when it is determined that the input interface for receiving the first message matches the matching item of the forwarding policy, using the identifier of the network slice included in the action item to determine the corresponding forwarding table.
[0097] When a message enters a network slice through the first network device, the first network device selects a suitable network slice through a forwarding table and uses the resources of the network slice to forward or process the message. The intermediate nodes in the network slice do not need to forward the message according to the forwarding strategy, but only need to forward the message according to the segment identifier carried by the message, so that the message forwarding is more flexible.
[0098] Combination Figure 5 The scenario shown is used to illustrate the above method embodiment. Figure 5 Based on Figure 1 Based on the scenario shown, the node segment ID and adjacent segment ID assigned to each network device are identified. Figure 5 In the example, network device 101, network device 102, network device 103, network device 104 and network device 105 respectively received the first resource allocation request message sent by the controller, and the identifier of the network slice contained in the first resource allocation request message is A. Network device 101, network device 102, network device 103 and network device 104 respectively received the second resource allocation request message, and the identifier of the network slice contained in the second resource allocation request message is B. In other words, network devices 101-104 belong to network slice A and network slice B, and network device 105 only belongs to network slice A.
[0099] The Node SID allocated by the network device 101 to the network slice A is 101, and the Node SID allocated to the network slice B is 201, that is, the network device 101 allocates different Node SIDs to different network slices. Figure 5 In the figure, network device 101 is connected to network device 102 through one link and to network device 103 through another link. Therefore, the Adj SIDs corresponding to the two links allocated by network device 101 to network slice A are 1001 and 1002 respectively, and the Adj SIDs allocated to network slice B are 2001 and 2002 respectively. Similarly, the Node SID allocated by network device 102 to network slice A is 102, and the Node SID allocated to network slice B is 202. The Adj SIDs allocated by network device 102 to network slice A are 1001, 1002 and 1003 respectively, and the Adj SIDs allocated to network slice B are 2001, 2002 and 2003 respectively. The Node SID allocated by network device 103 to network slice A is 103, and the Node SID allocated to network slice B is 203. The AdjSIDs allocated by network device 103 to network slice A are 1001 and 1002, respectively, and the Adj SIDs allocated to network slice B are 2001 and 2002, respectively. The Node SID allocated by network device 104 to network slice A is 104, and the Node SID allocated to network slice B is 204. The Adj SIDs allocated by network device 104 to network slice A are 1001, 1002, and 1003, respectively, and the Adj SIDs allocated to network slice B are 2001, 2002, and 2003, respectively. The Node SID allocated by network device 105 to network slice A is 105, and the Adj SIDs allocated by network device 105 to network slice A are 1001 and 1002, respectively.
[0100] Optionally, different network devices in the same network slice have different Node SIDs, and Node SIDs in different network slices may be the same or different. Different links in the same network device may have different Adj SIDs, and different links between different network devices may have the same Adj SIDs.
[0101] Optionally, the network devices 101-105 send the allocated Node SID and / or Adj SID to the controller, and the controller generates a forwarding table A corresponding to the network slice A and a forwarding table B corresponding to the network slice B, and then the controller sends the forwarding table A and the forwarding table B to the network devices in the network slice, for example, sending the forwarding table A and the forwarding table B to the network device 101. Optionally, the network devices 101-105 notify the allocated Node SID and / or Adj SID to other network devices in the network through notification messages, and accordingly, the network devices belonging to the same network slice respectively establish forwarding tables belonging to the network slice, for example, the network device 101 receives the notification messages sent by the network devices 102-105, and then establishes the forwarding table A corresponding to the network slice A and the forwarding table B corresponding to the network slice B. For example, the identifier or index of the forwarding table A is the identifier of the network slice A. Forwarding table A includes forwarding table entries for reaching network devices in network slice A. For example, forwarding table A includes forwarding table entries for reaching network device 105. The index of the forwarding table entry is the IP address of network device 105. The forwarding table also includes the Node SID of the network device on the path to reach network device 105, or includes the Node SID and Adj SID on the path to reach network device 105.
[0102] Optionally, when the message forwarding mode in network slice A is to strictly specify the forwarding path, the forwarding table includes the Node SID and Adj SID on the path to the destination network device. For example, the forwarding path included in the forwarding table entry is from network device 101 to network device 105, and the forwarding path passes through network device 102, network device 104 and network device 105, then the forwarding table entry includes: Node SID 102, Adj SID 1003, Node SID 104, Adj SID 1002 and Node SID105.
[0103] Optionally, when the message forwarding mode in network slice A is to strictly specify the forwarding path, the forwarding table includes the Adj SID on the path to the destination network device. For example, if the forwarding path included in the forwarding table entry is from network device 101 to network device 105, and the forwarding path passes through network device 102, network device 104 and network device 105, then the forwarding table entry includes: Adj SID 1003 and Adj SID 1002.
[0104] Optionally, when the message forwarding mode in network slice A is a loose forwarding path, the forwarding table includes the Node SID on the path to the destination network device, for example, the forwarding path included in forwarding table item F is from network device 101 to network device 105, and the forwarding path passes through network device 102, network device 104 and network device 105, then the forwarding table item may include: Node SID 102 and Node SID 105, or the forwarding table item includes Node SID 104 and Node SID 105. Specifically, the forwarding path from network device 101 to network device 105 must pass through network device 102, and the forwarding table item at this time includes the Node SIDs of the intermediate network devices and the tail network devices, such as: Node SID 102 and Node SID 105.
[0105] Optionally, when the message forwarding mode in network slice A is a loose forwarding path, the forwarding table includes an Adj SID on the path to the destination network device. For example, the forwarding path included in forwarding table item F is from network device 101 to network device 105, and the forwarding path passes through network device 102, network device 104, and network device 105. Then, the forwarding table item may include: Adj SID 1003 and Adj SID 1002. Optionally, the forwarding table item may include: Node SID 104 and AdjSID 1002.
[0106] When the network device 101 receives the first message, it obtains the source IP address of the first message, and according to the forwarding strategy, it is determined that the message whose source address is the IP address needs to be forwarded through the network slice A, and then the matching forwarding table item is searched in the forwarding table A according to the destination IP address of the first message. For example, the destination IP address of the first message is the address of the network device 105, and the matching forwarding table item is the forwarding table item F. When the message forwarding mode in the network slice A is a strictly specified forwarding path, the Node SID 102, Adj SID 1003, Node SID 104, Adj SID1002 and Node SID 105 in the forwarding table item F are pressed into the header of the first message to obtain the second message. When the message forwarding mode in the network slice A is a loose forwarding path, the Node SID 102 and Node SID 105 in the forwarding table item F are pressed into the header of the first message to obtain the second message. Then the network device 101 sends the second message to the network device corresponding to the next hop in the forwarding table item F. When network device 102 receives the second message, it determines that the message header of the second message contains Node SID 102 and Adj SID 1003, and considers that the message needs to be processed by itself. When processing the second message, it uses the device processing resources bound to Node SID 102, and when forwarding the second message, it uses the link resources bound to Adj SID 1003, that is, uses the resources in network slice A to process and forward the second message. Before network device 102 forwards the second message to network device 104, it pops out SID 102 and Adj SID 1003 in the message header, generates a third message, and then sends the third message to network device 104. When the network device 104 receives the third message, it determines that the message header of the third message contains Node SID 104 and Adj SID 1002, and it is considered that the message needs to be processed by itself. When processing the third message, the device processing resources bound to Node SID 104 are used, and when forwarding the third message, the link resources bound to Adj SID 1002 are used. Before the network device 104 forwards the third message to the network device 105, the SID 104 and Adj SID 1002 in the message header are popped out, a fourth message is generated, and then the fourth message is sent to the network device 105. When the network device 105 receives the fourth message, it determines that the message header of the fourth message contains NodeSID 105, and it is considered that the message needs to be processed by itself. When processing the fourth message, the device processing resources bound to NodeSID 105 are used.After the network device 105 processes the fourth message, it pops out the Node SID 105 from the message header of the fourth message, recovers the first message, and then continues to forward the first message according to the IP forwarding process.
[0107] Above Figure 2-Figure 5 In the illustrated embodiment, the controller or network device first generates a forwarding table corresponding to the network slice, and then generates a corresponding forwarding table entry. In a possible implementation, the controller or network device may not generate a forwarding table, but directly generate a forwarding table entry. In this case, the index of the forwarding table entry includes the identifier of the network slice and the IP address of the destination network device. Accordingly, when the subsequent network device forwards a message, it directly searches for the forwarding table entry to implement message forwarding.
[0108] In one possible implementation, the notification message is an Open Shortest Path First (OSPF) link-state advertisement (LSA) or an Intermediate System-to-Intermediate System (IS-IS) link state protocol data unit (LSP).
[0109] In one possible implementation, a sub-type length value (sub-TLV) is defined in an OSPF LSA or an ISIS LSP. For a specific format, see Figure 6 ,in,
[0110] The Type field is used to identify that the sub-TLV carries a node segment identifier and / or an adjacent segment identifier of the corresponding network fragment;
[0111] The Length field is used to identify the length of the sub-TLV message.
[0112] A Slice ID field is used to identify the identifier of the network slice carried in the notification message;
[0113] Reserved field, for subsequent expansion;
[0114] Slice specific SID, used to identify the node segment ID and / or adjacent segment ID carried in the notification message.
[0115] It can be seen from the above technical solution that when a message enters a network slice through a network device, the network device selects a suitable network slice through the forwarding table and uses the resources of the network slice to forward or process the message. The intermediate nodes in the network slice do not need to perceive the network slice information related to the message, and the message forwarding is more flexible. In addition, through the allocation of resources to the network slice, resource sharing based on the network slice can be achieved, and there is no need to reserve resources based on each LSP in the prior art. Therefore, it is no longer limited by the number of LSPs, and has higher scalability, which is conducive to meeting the business needs of more users under 5G.
[0116] See also Figure 7 The present application embodiment provides a controller 700 for generating a forwarding table entry, including:
[0117] A sending unit 701 is used to send multiple resource allocation request messages to multiple network devices in a network slice to trigger each of the multiple network devices to perform resource allocation according to the corresponding resource allocation request message. The multiple resource allocation request messages correspond to the multiple network devices one by one. The resource allocation request message includes an identifier of the network slice and resources that the corresponding network device needs to allocate to the network slice. The resources include device processing resources and / or link resources.
[0118] The receiving unit 702 is used to receive multiple resource allocation response messages sent by the multiple network devices, the multiple resource allocation response messages correspond one-to-one to the multiple network devices, the resource allocation response message includes an identifier of the network slice and a segment identifier of the corresponding network device, the segment identifier is used to identify the resources allocated by the corresponding network device to the network slice, the segment identifier includes a node segment identifier and / or an adjacent segment identifier, and the resources allocated to each device in the multiple network devices belong to the network slice.
[0119] Processing unit 703 is used to generate a forwarding table corresponding to the network slice according to the multiple resource allocation response messages, wherein the identifier of the forwarding table is the network slice identifier, the forwarding table includes forwarding table entries that reach the network device in the network slice, and the forwarding table entries include the segment identifier of the destination network device that reaches the forwarding table entries.
[0120] In a possible implementation, the controller 700 further includes:
[0121] An acquisition unit is used for the sending unit to acquire the network slice from the network according to business requirements before sending multiple resource allocation request messages to multiple network devices in the network slice, wherein the network slice includes the multiple network devices, and the business requirements include topology requirements and / or user requirements for quality of service.
[0122] In a possible implementation, the sending unit 701 is further configured to send the forwarding table to the network device in the network slice.
[0123] The controller 700 is a network management device or a controller under the SDN network architecture, which can implement the functions related to the controller in the above-mentioned embodiment. The specific execution steps can be referred to the above-mentioned method embodiment, which will not be repeated here.
[0124] See also Figure 8 The embodiment of the present invention provides a first network device 800 for generating a forwarding table entry, including:
[0125] The acquisition unit 801 is used to obtain a resource allocation request message, where the resource allocation request message includes an identifier of a network slice and resources that the first network device needs to allocate to the network slice, where the resources include device processing resources and / or link resources.
[0126] The processing unit 802 is used to allocate resources according to the resource allocation request message and allocate a segment identifier, wherein the segment identifier is used to identify the resources allocated by the first network device 800 to the network slice, the allocated resources belong to the network slice, the allocated resources include device processing resources and / or link resources, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier.
[0127] The sending unit 803 is used to send a notification message to the second network device to trigger the second network device to generate a forwarding table corresponding to the network slice according to the notification message, the notification message includes the identifier of the network slice and the segment identifier, the forwarding table includes a forwarding table entry for the network device in the network slice, and the forwarding table entry includes the segment identifier of the destination network device of the forwarding table entry.
[0128] In a possible implementation, the first network device 800 further includes a receiving unit and a matching unit.
[0129] The receiving unit is configured to receive the forwarding table sent by the second network device, and receive a first message, where the first message belongs to the forwarding table;
[0130] The matching unit is used to search for a matching forwarding entry in the forwarding table with the destination IP address of the first message, and the destination IP address of the forwarding entry has a corresponding relationship with the destination IP address of the first message;
[0131] The processing unit is further configured to insert the segment identifier in the forwarding table entry into the message header of the first message to generate a second message;
[0132] The sending unit is further configured to send the second message to a network device corresponding to a next hop in the forwarding table entry.
[0133] The first network device 800 may be a router or a switch or a network device with a forwarding function. The first network device 800 can implement the functions of the first network device in the aforementioned embodiment. The specific execution steps may refer to the aforementioned method embodiment, which will not be repeated here.
[0134] See also Fig. 9 The embodiment of the present invention provides a first network device 900 for generating a forwarding table entry, including:
[0135] The receiving unit 901 is used to receive multiple notification messages sent by multiple network devices in a network slice, where the multiple notification messages correspond one-to-one to the multiple network devices. The notification message includes an identifier of the network slice and a segment identifier of the corresponding network device. The segment identifier is used to identify the resources allocated by the corresponding network device to the network slice. The segment identifier includes a node segment identifier and / or an adjacent segment identifier. The first network device is a network device in the network slice.
[0136] Processing unit 902 is used to generate a forwarding table corresponding to the network slice based on the multiple notification messages, the forwarding table is identified by the identifier of the network slice, the forwarding table includes forwarding table entries for network devices in the network slice, and the forwarding table entries include segment identifiers of destination network devices for reaching the forwarding table entries.
[0137] In a possible implementation, the first network device further includes a receiving unit and a matching unit.
[0138] The receiving unit is configured to receive a first message, where the first message belongs to the forwarding table;
[0139] The matching unit is used to search for a matching forwarding entry in the forwarding table with the destination IP address of the first message, and the destination IP address of the forwarding entry has a corresponding relationship with the destination IP address of the first message;
[0140] The processing unit is further configured to insert the segment identifier in the forwarding table entry into the message header of the first message to generate a second message;
[0141] The sending unit is further configured to send the second message to a network device corresponding to a next hop in the forwarding table entry.
[0142] The first network device may be a router or a switch or a network device with a forwarding function. The first network device can implement the functions of the first network device in the aforementioned embodiment. The specific execution steps may refer to the aforementioned method embodiment, which will not be repeated here.
[0143] See also Fig.10 The embodiment of the present invention provides a network device 1000. The network device 1000 may be a router or a switch or a network device with a forwarding function. The network device 1000 can implement the function of the controller or the first network device in the aforementioned method embodiment. The network device 1000 includes: a processor 1003, a network interface 1002, and a memory 1001. The memory may be used to store program codes and data of the network device. The processor 1003 is used to call the program instructions in the memory 1001 to execute the method shown in the aforementioned embodiment. The specific execution steps can be referred to the aforementioned method embodiment, which will not be repeated here.
[0144] See also Fig.11 The embodiment of the present invention provides a first network device 1100. The first network device 1100 includes: a main control board 1101 and an interface board 1102. The main control board 1101 includes: a processor 1103 and a memory 1104. The interface board 1102 includes: a processor 1105, a memory 1106 and an interface card 1107. The main control board 1101 and the interface board 1102 are coupled.
[0145] The memory 1104 may be used to store the program code of the main control board 1101, and the processor 1103 is used to call the program code in the memory 1104 to perform the following operations:
[0146] Obtain a resource allocation request message, the resource allocation request message including an identifier of a network slice and resources that the first network device 1100 needs to allocate to the network slice, the resources including device processing resources and / or link resources; allocate resources according to the resource allocation request message, and allocate a segment identifier, the segment identifier being used to identify the resources allocated by the first network device 1100 to the network slice, the allocated resources including device processing resources and / or link resources, the segment identifier including a segment identifier and / or an adjacent segment identifier, and the allocated resources belong to the network slice.
[0147] The memory 1106 may be used to store the program code of the interface board 1102, and the processor 1105 is used to call the program code in the memory 1106 to perform the following operations:
[0148] The trigger interface card 1107 sends a notification message to the second network device to trigger the second network device to generate a forwarding table corresponding to the network slice according to the notification message, the notification message includes the identifier of the network slice and the segment identifier, the forwarding table includes a forwarding table entry of the network device reaching the network slice, and the forwarding table entry includes the segment identifier of the destination network device reaching the forwarding table entry.
[0149] In a possible implementation, an inter-process communication protocol IPC control channel is established between the main control board 1101 and the interface board 1102 .
[0150] The first network device 1100 may be a router or a switch or a network device with a forwarding function. The network device 1100 can implement the function of the first network device in the aforementioned method embodiment. The specific execution steps may refer to the aforementioned method embodiment and will not be repeated here.
[0151] The present invention also provides a computer storage medium for storing Figure 2 or Figure 3 or Figure 4 The computer software instructions used by the first network device in the illustrated embodiment include a program for executing the method illustrated in the aforementioned embodiment.
[0152] The "first" in the first network device mentioned in the embodiment of the present invention is only used as a name identifier and does not represent the first in order. The same rule applies to the "second".
[0153] The steps of the method or algorithm described in conjunction with the disclosure of the present invention may be implemented in hardware or by executing software instructions by a processor. The software instructions may be composed of corresponding software modules, which may be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), hard disk, mobile hard disk, optical disk or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in an ASIC. In addition, the ASIC may be located in a core network interface device. Of course, the processor and the storage medium may also exist in the core network interface device as discrete components.
[0154] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented using software, the functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that a general or special-purpose computer can access.
[0155] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solution of the present invention should be included in the scope of protection of the present invention.
Claims
1. A method for resource allocation, characterized in that: include: The controller sends a plurality of resource allocation request messages to a plurality of network devices to trigger each of the plurality of network devices to perform resource allocation according to the corresponding resource allocation request message, wherein the plurality of resource allocation request messages correspond to the plurality of network devices one by one, and the resource allocation request message includes an identifier of a network slice and resources that the corresponding network device needs to allocate to the network slice, wherein the resources include device processing resources and / or link resources; The controller receives a plurality of resource allocation response messages sent by the plurality of network devices, the plurality of resource allocation response messages corresponding to the plurality of network devices one by one, the resource allocation response message comprising an identifier of the network slice and a segment identifier of the corresponding network device, the segment identifier being used to identify resources allocated by the corresponding network device, the segment identifier comprising a node segment identifier and / or an adjacent segment identifier, and the resources comprising a device processing resource and / or a link resource; The controller calculates a forwarding path according to the segment identifier.
2. The method according to claim 1, characterized in that Before the controller sends a plurality of resource allocation request messages to a plurality of network devices, the method further includes: The controller determines the plurality of network devices from the network according to business requirements, wherein the business requirements include topology requirements and / or user requirements for quality of service.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: The controller sends a forwarding table entry to the network device, where the forwarding table entry is used to forward the message.
4. The method according to claim 1 or 2, characterized in that: The device processing resources include one or more of the following resources: queues, storage resources, processing resources and network functions; or, The link resources include one or more of the following resources: bandwidth, time slot, or sub-interface.
5. A method for resource allocation, characterized in that: include: The first network device obtains a resource allocation request message, where the resource allocation request message is used to instruct the first network device to allocate resources, and the resource allocation request message includes an identifier of a network slice and resources that the corresponding network device needs to allocate to the network slice, where the resources include device processing resources and / or link resources; The first network device allocates resources according to the resource allocation request message, and associates the allocated resources with a segment identifier, where the segment identifier is used to identify the resources allocated by the first network device, the allocated resources include device processing resources and / or link resources, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier; The first network device sends a notification message to the second network device, where the notification message includes an identifier of the network slice and the segment identifier.
6. The method according to claim 5, characterized in that The device processing resources include one or more of the following resources: queues, storage resources, processing resources and network functions; or, The link resources include one or more of the following resources: bandwidth, time slot, or sub-interface.
7. The method according to claim 6, characterized in that The segment identifier is a segment identifier allocated by the network device.
8. The method according to claim 5 or 6, characterized in that: The second network device is a controller.
9. The method according to claim 8, characterized in that The method further comprises: The first network device receives a forwarding entry sent by the second network device; The first network device receives a first message; The network device matches the forwarding table entry with the destination Internet Protocol IP address of the first message, and the destination IP address of the forwarding table entry has a corresponding relationship with the destination IP address of the first message; The network device inserts the segment identifier in the forwarding table entry into the message header of the first message to generate a second message; The network device sends the second message to the network device corresponding to the next hop in the forwarding table entry.
10. A resource allocation controller, characterized in that: include: A sending unit, configured to send a plurality of resource allocation request messages to a plurality of network devices, so as to trigger each of the plurality of network devices to perform resource allocation according to the corresponding resource allocation request message, wherein the plurality of resource allocation request messages correspond to the plurality of network devices one by one, and the resource allocation request message includes an identifier of a network slice, and resources that the corresponding network device needs to allocate to the network slice, wherein the resources include device processing resources and / or link resources; A receiving unit, configured to receive a plurality of resource allocation response messages sent by the plurality of network devices, wherein the plurality of resource allocation response messages correspond to the plurality of network devices one by one, and the resource allocation response message includes an identifier of the network slice and a segment identifier of the corresponding network device, wherein the segment identifier is used to identify resources allocated by the corresponding network device, and the segment identifier includes a node segment identifier and / or an adjacent segment identifier; A processing unit is used to calculate a forwarding path according to the segment identifier.
11. The controller according to claim 10, characterized in that: Also includes: The acquiring unit is used for determining the multiple network devices according to service requirements before the sending unit sends the multiple resource allocation request messages to the multiple network devices. The service requirements include topology requirements and / or user requirements for quality of service.
12. The controller according to claim 10 or 11, characterized in that: The device processing resources include one or more of the following resources: queues, memory, processors, and network functions; or, The link resources include one or more of the following resources: bandwidth, time slot, or sub-interface.
13. A first network device for resource allocation, characterized in that: include: an acquisition unit, configured to obtain a resource allocation request message, wherein the resource allocation request message includes resources that need to be allocated by the first network device, the resource allocation request message includes an identifier of a network slice, resources that need to be allocated to the network slice by the corresponding network device, and the resources include device processing resources and / or link resources; a processing unit, configured to allocate resources according to the resource allocation request message, and associate the allocated resources with a segment identifier, wherein the segment identifier is used to identify the resources allocated by the first network device, wherein the allocated resources include an identifier of the network slice and device processing resources and / or link resources, and wherein the segment identifier includes a node segment identifier and / or an adjacent segment identifier; A sending unit is used to send a notification message to the second network device, where the notification message includes the segment identifier.
14. The first network device according to claim 13, characterized in that: The segment identifier is a segment identifier allocated by the network device.
15. The first network device according to claim 13 or 14, characterized in that: The device processing resources include one or more of the following resources: queues, storage resources, processing resources and network functions; or, The link resources include one or more of the following resources: bandwidth, time slot, or sub-interface.
16. The first network device according to claim 13 or 14, characterized in that: The second network device is a controller.
17. The first network device according to claim 16, characterized in that: The first network device further includes a receiving unit and a matching unit. The receiving unit is used to receive the forwarding table entry sent by the second network device and receive the first message; The matching unit is used to match the destination Internet Protocol IP address of the first message to the forwarding table entry, and the destination IP address of the forwarding table entry has a corresponding relationship with the destination IP address of the first message; The processing unit is further configured to insert the segment identifier in the forwarding table entry into the message header of the first message to generate a second message; The sending unit is further configured to send the second message to a network device corresponding to a next hop in the forwarding table entry.
