Segment routing policy association group advertisement method, computer program product

Abstract

This invention provides a method and computer program product for announcing segment routing policy association groups. A first device receives first information from a second device. This first information is segment routing policy association group information corresponding to multiple segment routing policies, and it has a globally unique association group identifier. The first device transmits traffic based on this first information. This solves the problem in related technologies where it is impossible to support the announcement of association groups formed by multiple SR Policies, achieving the effect of supporting the announcement of association groups formed by multiple SR Policies, improving network resource utilization, and enhancing network stability and service quality.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and more specifically, to a method for announcing segment routing policy association groups and a computer program product. Background Technology

[0002] In related technologies, paths included in a Segment Routing Policy (SR Policy) are formed into Equal Cost Multi-Path (ECMP) or Fast Re-Route (FRR) to achieve balanced load balancing or redundancy protection. However, some emerging service requirements demand the formation of association groups from multiple SR Policies with different destination nodes, and the setting of traffic sharing modes within these association groups to rationally utilize the resources of different destination nodes. The Border Gateway Protocol (BGP) defines a mechanism for advertising SRPolicies, but it does not support advertising association groups formed by multiple SR Policies; while the Path Computation Element Communication Protocol (PCEP) supports advertising association groups formed by multiple candidate paths (CP) of the same SR Policy, it also does not support advertising association groups formed by multiple SR Policies. Summary of the Invention

[0003] This invention provides a method and computer program product for announcing segment routing policy association groups, to at least solve the problem in related technologies that cannot support the announcement of association groups formed by multiple SR Policies.

[0004] According to an embodiment of the present invention, a method for announcing segment routing policy association groups is provided, comprising: a first device receiving first information from a second device, the first information being segment routing policy association group information corresponding to multiple segment routing policies, the first information having globally unique association group identifier information; and the first device performing traffic transmission based on the first information.

[0005] According to another embodiment of the present invention, a method for announcing a segment routing policy association group is provided, comprising: a second device establishing a segment routing policy association group containing multiple segment routing policies; the second device sending first information to a first device, wherein the first information is segment routing policy association group information corresponding to the multiple segment routing policies, and the first information has globally unique association group identifier information.

[0006] According to another embodiment of the present invention, a network device is also provided, the network device including a receiver, a transmitter and a processor, the network device being configured to perform the steps of any of the above method embodiments via at least one of the receiver, the transmitter and the processor.

[0007] According to yet another embodiment of the present invention, 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 executed.

[0008] According to yet another embodiment of the present invention, 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.

[0009] According to yet another embodiment of the present invention, a computer program product is also provided, comprising a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0010] The present invention provides a method for announcing segment routing policy association groups through the above embodiments. A first device receives first information from a second device. This first information is information about segment routing policy association groups corresponding to multiple segment routing policies, and the first information has a globally unique association group identifier. The first device then transmits traffic based on this first information. This method solves the problem in related technologies where it is impossible to support the announcement of association groups formed by multiple SR Policies, achieving the effect of supporting the announcement of association groups formed by multiple SR Policies, improving network resource utilization, and enhancing network stability and service quality. Attached Figure Description

[0011] Figure 1 This is a hardware structure block diagram of a mobile terminal for the segment routing policy association group announcement method according to an embodiment of the present invention.

[0012] Figure 2 This is a flowchart of the segment routing policy association group announcement method according to an embodiment of the present invention;

[0013] Figure 3 This is another flowchart of the segment routing policy association group announcement method according to an embodiment of the present invention;

[0014] Figure 4 This is a structural block diagram of a network device according to an embodiment of the present invention;

[0015] Figure 5 This is a schematic diagram of the newly added Sub-TLV format in an embodiment of the present invention;

[0016] Figure 6 This is a schematic diagram of the newly added TLV format in an embodiment of the present invention. Detailed Implementation

[0017] The embodiments of the present invention will be described in detail below with reference to the accompanying drawings and examples.

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

[0019] In related technologies, the standard document RFC 8402 describes the architecture of segment routing. Segment routing technology allows a node to specify a forwarding path for a specific packet, instead of forwarding it according to the general shortest path. This is achieved by appending information related to the SID List, consisting of segment identifiers (SIDs), to the packet, without needing to maintain state information for each path at intermediate nodes. When it is necessary to modify the forwarding path of a packet, only a new SID List needs to be installed in the head node for the corresponding flow. The standard document RFC 9256 further describes the architecture of segment routing policy (SR Policy) and the method of traffic being imported into the SR Policy. The standard documents draft-ietf-pce-segment-routing-policy-cp-22 and draft-ietf-idr-sr-policy-safi-13 define the mechanisms for announcing SR Policies using the PCEP and BGP protocols, respectively.

[0020] Traditional business requirements typically necessitate the formation of ECMP or FRR between multiple paths leading to the same destination node. This can be achieved by forming FRR between multiple candidate paths (CPs) of an SR Policy, or by forming ECMP or FRR between multiple segment lists contained within a CP. For example, BGP can dynamically distribute multiple SR Policies to ingress routers and configure SR Policies for multiple different destination nodes (Endpoints) with the same Color value, allocating traffic to different paths according to the policy (e.g., based on link utilization or weight). However, some new business requirements demand the formation of association groups between multiple paths leading to different destination nodes, and the setting of traffic sharing modes within these association groups. For instance, in computing power network scenarios, it is necessary to form association groups between nodes reaching multiple destination computing power gateways and implement flow stickiness mode flow sharing within these association groups; similarly, in intelligent computing network scenarios, it is necessary to distribute tokens to association groups formed by multiple experts and implement multicast mode flow sharing within these association groups. To address this, this application extends the BGP and PCEP protocols to support the announcement of association groups formed by multiple SRPolicies.

[0021] The methods and embodiments provided in this application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal for announcing a segment routing policy association group according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0022] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the segment routing policy association group announcement method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, thereby 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.

[0023] 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 the mobile terminal's communication provider. 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.

[0024] This embodiment provides a method for announcing segment routing policy association groups. Figure 2 This is a flowchart of the segment routing policy association group announcement method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:

[0025] In step S202, the first device receives first information from the second device. The first information is the segment routing policy association group information corresponding to multiple segment routing policies. The first information has globally unique association group identifier information.

[0026] In this embodiment of the invention, the first device may be a head node, and the second device may be a controller or a management device.

[0027] In one exemplary embodiment, the first information includes traffic sharing mode information, which is used to indicate the traffic sharing strategy of multiple segment routing policies within a segment routing policy association group. The traffic sharing strategy includes at least one of the following: load balancing ECMP mode; fast rerouting FRR mode; multicast mode; flow stickiness mode; anycast mode.

[0028] In one exemplary embodiment, multiple segment routing policies within the same segment routing policy association group have different destination nodes; or, some segment routing policies within the same segment routing policy association group have the same destination node.

[0029] In this embodiment of the invention, all SR Policies added to the same association group can have different endpoints, or they can have the same endpoint. However, not all SR Policies will have the same endpoint.

[0030] In one exemplary embodiment, multiple segment routing policies within the same segment routing policy association group have the same head node.

[0031] In this embodiment of the invention, SR Policies within the same segment routing policy association group generally have the same headend.

[0032] In one exemplary embodiment, the first information further includes attribute information for each segment routing policy, the attribute information including at least one of the following: the weight of the segment routing policy; the priority of the segment routing policy.

[0033] In this embodiment of the invention, the weight of an SR Policy can be used in ECMP mode. For example, the proportion of traffic shared by each SR Policy in the associated group is equal to the proportion of the weight of that SR Policy to the sum of the weights of all SR Policies in the associated group.

[0034] In this embodiment of the invention, the preference of an SR Policy can be used in either FRR mode (including 1:1 and 1+1 protection modes) or flow-stickiness mode. For example, when used in FRR mode, the SR Policy with the highest priority within the association group is the primary SR Policy, while the other SR Policies are backup SR Policies. When used in flow-stickiness mode, the SR Policy with the highest priority within the association group always attracts new traffic, while previous traffic already mapped to a specific SR Policy within the association group continues to maintain this mapping relationship.

[0035] In one exemplary embodiment, the first device receives first information from the second device, including: the first device receives the first information from the second device via Extended Border Gateway Protocol (BGP), the first information being carried in a newly added Sub-TLV in the BGP tunnel encapsulation attribute.

[0036] In an exemplary embodiment, the first device receives first information from the second device, including: the first device receives the first information from the second device via the Extended Path Computing Element Communication Protocol (PCEP), and the first information is carried in a newly added TLV in the PCEP associated object.

[0037] In one exemplary embodiment, the first device receives first information from the second device, including: the first device receiving the first information from the second device via a network configuration protocol.

[0038] In this embodiment of the invention, segment routing policy association group information transmission is achieved by extending the BGP protocol, the PCEP protocol, or the network configuration protocol. In actual implementation, other protocols may also be used, which will not be elaborated here.

[0039] In this embodiment of the invention, the control device can send the following configuration information (i.e., the first information in the above embodiment) to the head node. The control device supports association groups at the SR Policy level through the Network Configuration Protocol (Netconf), and in particular, these SR Policies have different destination nodes.

[0040] Step S204: The first device performs traffic transmission based on the first information.

[0041] In an exemplary embodiment, the first device performs traffic transmission based on the first information, including: the first device mapping one or more traffic flows to a segment routing policy association group; the first device determining the segment routing policy corresponding to each traffic flow based on the traffic sharing mode information of the first information, and performing traffic transmission.

[0042] In this embodiment of the invention, after receiving a notification from the second device, the first device creates an SR Policy association group locally. The first device can map one or more flows to the SR Policy association group and select to send traffic on a specific SR Policy within the association group according to the traffic sharing mode within the association group.

[0043] This embodiment provides a method for announcing segment routing policy association groups. Figure 3 This is another flowchart of the segment routing policy association group announcement method according to an embodiment of the present invention, such as... Figure 3 As shown, the process includes the following steps:

[0044] Step S302: The second device establishes a segment routing policy association group containing multiple segment routing policies.

[0045] In this embodiment of the invention, the second device designs SR Policy strategies based on network requirements and service objectives. This may include determining parameters such as the destination node, path selection, weight, priority, and traffic sharing mode of the SR Policy. The second device generates multiple SR Policies based on the policy design. Each SR Policy contains key information such as the head node, destination node, and SID list, as well as its attributes in the association group, such as weight and priority. The controller defines an association group, assigns it a globally unique ID, and sets the traffic sharing mode. This association group will contain the multiple SR Policies generated previously. The specific method for establishing the association group for segment routing policies can be implemented using conventional techniques in the field based on the actual situation, and will not be elaborated here.

[0046] In step S304, the second device sends first information to the first device. The first information is the segment routing policy association group information corresponding to multiple segment routing policies. The first information has globally unique association group identifier information.

[0047] The present invention provides a method for announcing segment routing policy association groups through the above embodiments. A first device receives first information from a second device. This first information is information about segment routing policy association groups corresponding to multiple segment routing policies, and the first information has a globally unique association group identifier. The first device then transmits traffic based on this first information. This method solves the problem in related technologies where it is impossible to support the announcement of association groups formed by multiple SR Policies, achieving the effect of supporting the announcement of association groups formed by multiple SR Policies, improving network resource utilization, and enhancing network stability and service quality.

[0048] 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 the present invention, 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 the present invention.

[0049] This embodiment also provides a segment routing policy association group announcement device, which is used to implement the above embodiments and preferred embodiments, and will not be repeated as already described. 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.

[0050] The segment routing policy association group notification device provided in this embodiment of the invention can be set in a first device (head node), including a receiving module for receiving first information from a second device, the first information being segment routing policy association group information corresponding to multiple segment routing policies, the first information having globally unique association group identifier information; and a transmission module for transmitting traffic based on the first information.

[0051] The segment routing policy association group notification device provided in this embodiment of the invention can be set in a second device (controller / management device), including an establishment module for establishing a segment routing policy association group containing multiple segment routing policies; and a sending module for sending first information to a first device, wherein the first information is segment routing policy association group information corresponding to multiple segment routing policies, and the first information has globally unique association group identifier information.

[0052] In this embodiment of the invention, the notification device for the above-mentioned segment routing policy association group may also include different modules, and the naming and functional division of the modules may be selected in different ways according to the actual situation, without specific restrictions.

[0053] 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.

[0054] This invention also provides a network device. Figure 4 This is a structural block diagram of a network device according to an embodiment of the present invention, such as... Figure 4 As shown, the network device 400 includes a receiver 401, a transmitter 402, and a processor 403. The network device 400 is used to perform the steps of the above-described model access method embodiment through at least one of the receiver 401, transmitter 402, and processor 403.

[0055] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.

[0056] 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.

[0057] Embodiments of the present invention 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.

[0058] 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.

[0059] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0060] In one exemplary embodiment, the computer program product described above includes a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this application.

[0061] 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.

[0062] It is obvious to those skilled in the art that the modules or steps of the present invention 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 described 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, the present invention is not limited to any particular combination of hardware and software.

[0063] To enable those skilled in the art to better understand the technical solutions of the present invention, the following description is provided in conjunction with different embodiments.

[0064] In this embodiment of the invention, the first device is a head node, and the second device is a controller, a centralized controller, or a management and control device.

[0065] Example 1

[0066] In this embodiment of the invention, the centralized controller creates multiple SR Policies locally and forms these SR Policies into an association group. Each SR Policy association group has globally unique association group identification information to distinguish it from other SR Policy association groups.

[0067] In this embodiment of the invention, traffic sharing modes are set for associated groups, including but not limited to: load balancing ECMP mode, fast rerouting FRR 1:1 protection mode, fast rerouting FRR 1+1 protection mode, multicast mode, flow-stickiness mode, and anycast mode.

[0068] In one embodiment, ECMP mode means that traffic is load-sharing across all SR Policies in the associated group based on the weight of each SR Policy, and at any given time a single packet of traffic will only be sent on a specific SR Policy.

[0069] In one embodiment, the FRR 1:1 protection mode means that traffic preferentially runs on the primary SR Policy in the association group, and only when the primary SR Policy fails will the traffic switch to the backup SR Policy.

[0070] In one embodiment, the FRR 1+1 protection mode means that traffic runs simultaneously on the primary and backup SR policies in the association group, and redundant traffic is eliminated on the destination node.

[0071] In one embodiment, multicast mode means that traffic runs on all SR Policies in the associated group, and a single packet of traffic is copied multiple times and sent separately on each SR Policy.

[0072] In one embodiment, the flow-stickiness mode refers to traffic being consistently selected to run on a specific SRPolicy within the association group.

[0073] In one embodiment, the anycast mode refers to traffic preferentially running on the SR Policy that has the destination node closest to the source node.

[0074] In this embodiment of the invention, all SR Policies added to the same association group can have different endpoints, or they can have the same endpoint. These SR Policies generally have the same header.

[0075] In this embodiment of the invention, SR Policies can be dynamically deleted or added from the associated group.

[0076] In one embodiment, when a new path or destination needs to be added to the network, or when more resources are needed to distribute traffic, this can be achieved by dynamically adding SR Policies to the association group. Based on network expansion, new service requirements, or fault recovery strategy needs, the controller or network device can create a new SR Policy, set its attributes (such as weight, priority, etc.) to match the current association group, and then advertise it to the head node via a network protocol (such as BGP, PCEP). Upon receiving the new SR Policy information, the head node will add this new SR Policy to its local association group instance and automatically adjust traffic allocation according to the traffic sharing mode.

[0077] In one embodiment, if an SR Policy is no longer needed, its path becomes unavailable, or the network administrator decides to reduce traffic to that destination, this can be achieved by dynamically deleting the SR Policy from the association group. The controller or network device will notify the head node of the identification information of the SR Policy to be deleted. After receiving this information, the head node will remove the SR Policy from its local association group instance, recalculate traffic allocation, and ensure that traffic is not mistakenly sent to the path of the deleted SR Policy.

[0078] In this embodiment of the invention, in order to support the different traffic sharing modes described above, each SRPolicy in the association group also includes the following attributes: weight and preference.

[0079] In one embodiment, the weight of an SR Policy can be used in ECMP mode. For example, the proportion of traffic shared by each SR Policy within an association group is equal to the proportion of that SR Policy's weight to the sum of the weights of all SR Policies within the association group.

[0080] In one embodiment, the preference of an SR Policy can be used in either FRR mode (including 1:1 and 1+1 protection modes) or flow-stickiness mode. For example, when used in FRR mode, the SR Policy with the highest priority within the association group is the primary SR Policy, while the others are backup SR Policies. When used in flow-stickiness mode, the SR Policy with the highest priority within the association group always attracts new traffic, while existing flows already mapped to a specific SR Policy within the association group continue to maintain this mapping.

[0081] In this embodiment of the invention, the controller can announce all SR Policies belonging to a group to the head node individually, or it can announce them together as a group. The controller needs to inform the head node that these SR Policies belong to the same group. When using the former announcement method, the announced SR Policy object should include group identification information and traffic sharing mode information. When using the latter announcement method, the announced group object should include group identification information, traffic sharing mode information, and keywords of all SR Policies belonging to that group.<endpoint,color> .

[0082] In this embodiment of the invention, after receiving the announcement from the controller (i.e., the announcement of the first information in the above embodiment), the head node creates an SR Policy association group locally. The head node can map one or more flows to the SR Policy association group and select to send the flow on a specific SR Policy within the association group according to the traffic sharing mode within the association group.

[0083] Example 2

[0084] In this embodiment, the BGP protocol is extended to support the announcement of SR Policy association groups between the controller and the head node.

[0085] In the existing standard draft-ietf-idr-sr-policy-safi-13, BGP announces SR Policy according to the granularity of SR Policy CP (candidate path). The same SR Policy may contain multiple CandidatePaths, and each CandidatePath may contain multiple Segment Lists to form load sharing.

[0086] In this embodiment of the invention, based on the encapsulation structure of SR Policy CP, additional information required for SR Policy association groups, namely SR Policy Level Association Group Sub-TLV, is added. This Sub-TLV contains...<ID,FlowSharing Mode,Weight,Preference> The main fields are as follows:

[0087]

[0088] Among them, the key value of SR Policy SAFI NLRI<Distinguisher,Policy Color,Endpoint> This represents a key-value pair of a Candidate Path, while<Policy Color,Endpoint> An SR Policy is identified, and different Candidate Paths within an SR Policy are distinguished by the Distinguisher identifier. The Candidate Path's attributes (such as Binding SID, Preference, etc.) are encapsulated in the form of a Sub-TLV in the Tunnel Encapsulation Attribute.

[0089] In this embodiment, if an SR Policy contains multiple CPs, the SR PolicyLevel Association Group information contained in each CP should be consistent, because the SR Policy Level Association Group information is essentially an attribute of the SR Policy level.

[0090] Figure 5 This is a schematic diagram of the newly added Sub-TLV format in an embodiment of the present invention, as shown below. Figure 5 As shown, ID represents the identifier of the associated group to which the SRPolicy belongs; Mode represents the traffic sharing mode of the associated group, and its value can be: 0 (ECMP mode), 1 (FRR 1:1 protection mode), 2 (FRR 1+1 protection mode), 3 (multicast mode), 4 (flow-stickiness mode), 5 (anycast mode). Preference represents the priority of the SR Policy within its associated group, mainly used in FRR mode and flow-stickiness mode. Weight represents the weight of the SR Policy within its associated group, mainly used in ECMP mode.

[0091] In this embodiment of the invention, the controller may include the aforementioned SRPolicy Level Association Group Sub-TLV in the SR Policy CP announced to the head node, enabling the head node to add multiple SR Policies with the same SR PolicyLevel Association Group information to a designated association group. The head node establishes the corresponding association group instance locally and forwards the service flows mapped to that association group according to the traffic sharing mode of the association group.

[0092] Example 3

[0093] In this embodiment, the PCEP protocol is extended to support the announcement of SRPolicy association groups between the controller and the head node.

[0094] In the existing standard draft-ietf-pce-segment-routing-policy-cp-22, PCEP announces SR policies at the granularity of SRPolicy CP (Candidate Path). The same SR policy may contain multiple Candidate Paths, and each Candidate Path may contain multiple Segment Lists to form load sharing.

[0095] In this embodiment of the invention, based on the encapsulation structure of the SR Policy CP described above, additional information required for the SR Policy association group, namely the SR Policy Level Association Group TLV, is added. This TLV contains...<ID,Flow SharingMode,Weight,Preference> The main fields are as follows:

[0096] <lsp>

[0097] <association>:

[0098] Extended Association ID TLV:<color,endpoint>

[0099] SR Policy Level Association Group TLV:<ID,Flow Sharing Mode,Weight,Preference>

[0100] Other TLVS

[0101] <end-point>

[0102] <intended-path> ::＝( <ero> |

[0103] ( <path-attrib> <ero> )

[0104] [ <intended-path> ])

[0105] <actual-path> ::＝( <rro> |

[0106] ( <path-attrib> <rro> )

[0107] [ <actual-path>])

[0108] The LSP object provides the PLSP_ID of the CP, and the ASSOCIATION object provides the key value of the SRPolicy to which the CP belongs.<color,endpoint> In addition to other attribute information, the Explicit RouteObject (ERO) or Record Route Object (RRO) provides information on all the segments contained in the CP.

[0109] In this embodiment, if an SR Policy contains multiple CPs, the SR PolicyLevel Association Group information contained in each CP should be consistent, because the SR Policy Level Association Group information is essentially an attribute of the SR Policy level.

[0110] Figure 6 This is a schematic diagram of the newly added TLV format in an embodiment of the present invention, as shown below. Figure 6 As shown, explanations of each field can be found in [link to documentation]. Figure 5 The explanations of the fields in the code will not be repeated here.

[0111] In this embodiment of the invention, the controller may include the aforementioned SRPolicy Level Association Group TLV in the SR Policy CP announced to the head node, enabling the head node to add multiple SR Policies with the same SR PolicyLevel Association Group information to a designated association group. The head node establishes the corresponding association group instance locally and forwards the service flows mapped to that association group according to the traffic sharing mode of the association group.

[0112] Example 4

[0113] In this embodiment, the network configuration protocol netconf is used to configure and support association groups at the SR Policy level, specifically, these SR Policies have different destination nodes.

[0114] In this embodiment, the control device can send the following configuration information to the head node (where each line represents a configuration command, and <> contains the parameters of the command):

[0115]

[0116] Among them, association-group <id>An associated group instance will be created, with the associated group identifier determined by parameters. <id>designation.

[0117] flow-sharing-mode <value>This will specify the traffic sharing mode for the associated group; the specific mode is determined by the parameter. <value>specified.

[0118] sr-policy <color> <endpoint> <weight> <preference>This command will include the specified SR Policy within the associated group. It can appear multiple times to include multiple SR Policies; the specific key value of each SR Policy is determined by the parameter. <color>and <endpoint>The weight and priority of the SR Policy within this association group are specified by the parameters. <weight>and <preference>specified.

[0119] In this embodiment of the invention, after receiving the above configuration information, the head node establishes a corresponding association group instance locally and forwards the service flow mapped to the association group according to the traffic sharing mode of the association group.

[0120] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention should be included within the scope of protection of the present invention.< / preference> < / weight> < / endpoint> < / color> < / preference> < / weight> < / endpoint> < / color> < / value> < / value> < / id> < / id> < / rro> < / path-attrib> < / rro> < / actual-path> < / intended-path> < / ero> < / path-attrib> < / ero> < / intended-path> < / end-point> < / association> < / lsp>

Claims

1. A method for announcing segment routing policy association groups, characterized in that, include: The first device receives first information from the second device. The first information is segment routing policy association group information corresponding to multiple segment routing policies. The first information has globally unique association group identifier information. The first device transmits traffic based on the first information.

2. The method according to claim 1, characterized in that, The first information includes traffic sharing mode information, which is used to indicate the traffic sharing strategy of the multiple segment routing policies within the segment routing policy association group. The traffic sharing strategy includes at least one of the following: Load balancing ECMP mode; Fast Rerouting (FRR) mode; Multicast mode; Stream stickiness mode; Anycast mode.

3. The method according to claim 1, characterized in that, Multiple segment routing policies within the same segment routing policy association group have different destination nodes; or, some segment routing policies within the same segment routing policy association group have the same destination node.

4. The method according to claim 3, characterized in that, Multiple segment routing policies within the same segment routing policy association group have the same head node.

5. The method according to claim 1, characterized in that, The first information also includes attribute information for each segment routing policy, the attribute information including at least one of the following: The weight of the segment routing policy; the priority of the segment routing policy.

6. The method according to claim 1, characterized in that, The first device receives first information from the second device, including: The first device receives the first information from the second device via Extended Border Gateway Protocol (BGP), and the first information is carried in a newly added Sub-TLV in the BGP tunnel encapsulation attribute.

7. The method according to claim 1, characterized in that, The first device receives first information from the second device, including: The first device receives the first information from the second device via the Extended Path Calculation Element Communication Protocol (PCEP), and the first information is carried in a newly added TLV in the PCEP associated object.

8. The method according to claim 1, characterized in that, The first device receives first information from the second device, including: The first device receives the first information from the second device via a network configuration protocol.

9. The method according to claim 1, characterized in that, The first device performs traffic transmission based on the first information, including: The first device maps one or more traffic flows to a segment routing policy association group; The first device determines the segment routing strategy corresponding to each traffic flow based on the traffic sharing mode information of the first information, and performs traffic transmission.

10. A method for announcing segment routing policy association groups, characterized in that, include: The second device establishes a segment routing policy association group containing multiple segment routing policies; The second device sends first information to the first device. The first information is the segment routing policy association group information corresponding to the multiple segment routing policies. The first information has globally unique association group identifier information.

11. A network device, characterized in that, The network device includes a receiver, a transmitter, and a processor, and is configured to perform the steps of the method according to any one of claims 1 to 10 via at least one of the receiver, the transmitter, and the processor.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 10.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 10.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 10.

Images