Routing management method and apparatus, network device, and readable storage medium

1. A routing management method, comprising:

obtaining, by a controller, network topology information of a network side;

calculating, by the controller, path information of a Segment Routing-Traffic Engineering (SR-TE) instance to be created, based on the network topology information, and sending the path information to a network-side head node; wherein the path information comprises segment list information and Entropy Label (EL) insertion position information; and

creating, by the controller, the SR-TE instance from the network-side head node to a tail node, and

wherein the EL insertion position information comprises whether to insert the EL and one or more positions into which the EL to be inserted.

2. The routing management method of claim 1 , wherein creating, by the controller, the SR-TE instance from the network-side head node to the tail node, comprises:

creating actively, by the controller, the SR-TE instance; and/or

creating, by the controller, the SR-TE instance, in response to an SR-TE instance creation request initiated by the network-side head node.

3. The routing management method of claim 1 , wherein sending, by the controller, the path information to the network-side head node, comprises:

sending, by the controller, the path information to the network-side head node, through a Path Computation Element Communication Protocol (PCEP) session established between the controller and the network-side head node; or

sending, by the controller, the path information to the network-side head node, through a Border Gateway Protocol (BGP) session established between the controller and the network-side head node.

4. The routing management method of claim 3 , wherein when the path information is sent to the network-side head node through the PCEP session established between the controller and the network-side head node, sending, by the controller, the path information to the network-side head node, comprises:

describing the segment list information and the EL insertion position information by using a first object; wherein the first object comprises at least one first-object Sub-object.

5. The routing management method of claim 4 , wherein an encapsulation format of one first-object Sub-object of the at least one first-object Sub-object comprises a first flag; wherein a value of the first flag is used for indicating whether it is the EL insertion position information immediately after the first-object Sub-object.

6. The routing management method of claim 3 , wherein when the path information is sent to the network-side head node through the BGP session established between the controller and the network-side head node, sending, by the controller, the path information to the network-side head node, comprises:

describing the segment list information and the EL insertion position information by using a second object; wherein the second object comprises at least one second-object Sub-object.

7. The routing management method of claim 6 , wherein an encapsulation format of one second-object Sub-object of the at least one second-object Sub-object comprises a second flag; wherein a value of the second flag is used for indicating whether it is the EL insertion position information immediately after the second-object Sub-object.

8. The routing management method of claim 1 , wherein the SR-TE instance comprises: an SR-TE tunnel, and/or an SR-TE policy.

9. The routing management method of claim 1 , further comprising:

converting, by the network-side head node, the path information to Next Hop Label Forwarding Entry (NHLFE) forwarding information; and

sending, by the network-side head node, the NHLFE forwarding information to a forwarding plane;

wherein the NHLFE forwarding information comprises the EL insertion position information.

10. The routing management method of claim 1 , further comprising:

calculating, by the network-side head node, in response to determining that there is a service packet to be carried and forwarded on the SR-TE instance, a corresponding EL according to service load content of the service packet; and

inserting, by the network-side head node, the EL into a specified position in a label stack encapsulated in the service packet, according to the EL insertion position information.

11. A non-transitory computer-readable storage medium having one or more computer programs stored thereon, wherein the one or more computer programs are configured to, when executed by one or more processors, a step of the routing management method of claim 1 is implemented.

12. A network device, comprising a processor, a memory, and a communication bus, wherein

the communication bus is configured to enable a communication connection between the processor and the memory; and

the processor is configured to execute one or more computer programs stored in the memory, to implement:

obtaining, by a controller, network topology information of a network side;

calculating, by the controller, path information of a Segment Routing-Traffic Engineering (SR-TE) instance to be created, based on the network topology information, and sending the path information to a network-side head node; wherein the path information comprises segment list information and Entropy Label (EL) insertion position information; and

creating, by the controller, the SR-TE instance from the network-side head node to a tail node, and

wherein the EL insertion position information comprises whether to insert the EL and one or more positions into which the EL to be inserted.

13. The network device of claim 12 , wherein the processor is configured to execute the one or more computer programs stored in the memory to implement:

creating actively, by the controller, the SR-TE instance; and/or

creating, by the controller, the SR-TE instance, in response to an SR-TE instance creation request initiated by the network-side head node.

14. The network device of claim 12 , wherein the processor is configured to execute the one or more computer programs stored in the memory to implement:

sending, by the controller, the path information to the network-side head node, through a Path Computation Element Communication Protocol (PCEP) session established between the controller and the network-side head node; or

sending, by the controller, the path information to the network-side head node, through a Border Gateway Protocol (BGP) session established between the controller and the network-side head node.

15. The network device of claim 14 , wherein when the path information is sent to the network-side head node through the PCEP session established between the controller and the network-side head node, the processor is configured to execute the one or more computer programs stored in the memory to implement:

describing the segment list information and the EL insertion position information by using a first object; wherein the first object comprises at least one first-object Sub-object.

16. The network device of claim 15 , wherein an encapsulation format of one first-object Sub-object of the at least one first-object Sub-object comprises a first flag; wherein a value of the first flag is used for indicating whether it is the EL insertion position information immediately after the first-object Sub-object.

17. The network device of claim 14 , wherein when the path information is sent to the network-side head node through the BGP session established between the controller and the network-side head node, the processor is configured to execute the one or more computer programs stored in the memory to implement:

describing the segment list information and the EL insertion position information by using a second object; wherein the second object comprises at least one second-object Sub-object.

18. The network device of claim 17 , wherein an encapsulation format of one second-object Sub-object of the at least one second-object Sub-object comprises a second flag; wherein a value of the second flag is used for indicating whether it is the EL insertion position information immediately after the second-object Sub-object.

19. The network device of claim 12 , wherein the SR-TE instance comprises: an SR-TE tunnel, and/or an SR-TE policy.