A method, apparatus, storage medium, and electronic device for obtaining routes.

By acquiring and utilizing the target rules in Flowspec routes, traffic is redirected to SR-Policy, solving the problem of poor network tuning in traditional routing design and achieving optimization of traffic paths and improvement of network tuning efficiency.

CN115348206BActive Publication Date: 2026-11-10ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110519239.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-05-12
Publication Date
2026-11-10
Estimated Expiration
2041-05-12

AI Technical Summary

Technical Problem

Traditional routing designs suffer from poor network optimization capabilities, require extensive manual configuration, place high demands on maintenance personnel, and exhibit poor network maintainability.

Method used

By obtaining Flowspec routes from the controller, including target rules, traffic is redirected to the target SR-Policy based on the target rules, and traffic matching and processing are performed using extended community attributes and tunnel encapsulation attributes.

Benefits of technology

It optimizes traffic paths, improves network tuning efficiency, simplifies the configuration process, and reduces the difficulty of operation and maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115348206B_ABST
    Figure CN115348206B_ABST
Patent Text Reader

Abstract

This invention provides a route acquisition method, a route sending method, an apparatus, a storage medium, and an electronic device. The route acquisition method includes acquiring a flow specification (Flowspec) route from a controller, wherein the Flowspec route contains target rules that instruct the redirection of received traffic to one or more target traffic engineering paths (SR-Policies). This invention solves the problem of poor network tunability, thereby improving network tunability efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and more specifically, to a route acquisition method, a route transmission method, a device storage medium, and an electronic device. Background Technology

[0002] Traditional routing was initially designed for traffic forwarding. Routing table entries only contained prefix mask information for destination address matching and outgoing interface information. Later, with the development of network services (such as DDoS protection and traffic engineering), support for traffic policies (such as static policy routing) was added. This required forwarding routing table entries to further segment data flows, not just matching data flows based on destination addresses, but also including source addresses, IP protocol numbers, port numbers, etc. The processing actions for flows were also expanded beyond simply forwarding from a specific outgoing interface, including rate limiting, dropping, redirection, and other actions. However, the biggest limitation of policy routing is that it is a local operation, requiring configuration on a device-by-device basis. Manual configuration is labor-intensive, demands high skill from operations and maintenance personnel, and leads to poor network optimization and maintainability. Summary of the Invention

[0003] This invention provides a route acquisition method, a route transmission method, a device storage medium, and an electronic device to at least solve the problem of poor network tunability in related technologies.

[0004] According to an embodiment of the present invention, a route acquisition method is provided, comprising:

[0005] Obtain the Flowspec route from the controller, wherein the Flowspec route contains target rules that indicate to redirect received traffic to one or more target traffic engineering paths SR-Policies.

[0006] In one exemplary embodiment, after obtaining the Flowspec route from the controller, the method further includes:

[0007] Upon receiving the traffic, the traffic is redirected to the target SR-Policy based on the target rule.

[0008] In an exemplary embodiment, the target rule includes target conditions and target actions, wherein the target conditions include conditions for matching the traffic, and the target actions are action information performed on the traffic after matching the traffic.

[0009] In one exemplary embodiment, the target condition is carried in the network layer reachability information (NIRL) included in the Flowspec route.

[0010] In one exemplary embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0011] In one exemplary embodiment, the extended community attribute includes a target bit used to identify a target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute overrides the other community attributes, or the extended community attribute coexists with the other community attributes.

[0012] In one exemplary embodiment, the extended community attribute and the other community attributes are sent by the controller at the same time or at different times.

[0013] In one exemplary embodiment, the extended community attribute is set for the same group of streams or the same service as the other community attributes.

[0014] In one exemplary embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0015] In one exemplary embodiment, the predetermined value includes at least one of the following:

[0016] The type value of the local ID, and the predefined type value.

[0017] In one exemplary embodiment, the extended community attribute includes an identifier of the SR-Policy, wherein when the local ID identifies the meaning of the SR-Policy group or a predefined type value is the meaning of the SR-Policy group, the identifier of the SR-Policy group is carried in the SR-Policy identifier field.

[0018] In one exemplary embodiment, the Flowspec route further includes an extended tunnel encapsulation attribute, which, when the target SR-Policy includes an SR-Policy type identified by the predetermined value, is used to identify a member SR-Policy in the target SR-Policy group.

[0019] In one exemplary embodiment, the Flowspec route further includes an extended tunneling encapsulation attribute, wherein the target action is jointly carried by the extended community attribute and the extended tunneling encapsulation attribute.

[0020] In one exemplary embodiment, redirecting the received traffic to the target SR-Policy based on the target rule includes:

[0021] The traffic is matched according to the target conditions;

[0022] If a target action is matched with the traffic, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy.

[0023] In one exemplary embodiment,

[0024] Matching the traffic according to the target conditions includes: matching the traffic in a pre-generated first flow matching table entry, wherein the first flow matching table entry includes corresponding target conditions and target actions, the target conditions are used to indicate matching information, and the target actions are used to indicate SR-Policy;

[0025] When a target action corresponding to the traffic is matched, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy, which includes: when a match is found in the pre-generated first flow matching entry, the traffic is redirected to the target SR-Policy included in the first flow matching entry.

[0026] In one exemplary embodiment, after performing address matching on the traffic in a pre-generated first flow matching entry, the method further includes:

[0027] If no target action corresponding to the traffic is matched in the pre-generated first flow matching entry, a first instruction is sent to the processor to instruct the processor to generate a second flow matching entry, wherein the second flow matching entry includes information indicating the target condition.

[0028] In one exemplary embodiment, the method further includes:

[0029] Receive the second instruction from the processor;

[0030] The first stream matching entry is deleted based on the second instruction.

[0031] According to another embodiment of the present invention, a routing transmission method is provided, comprising:

[0032] Send a Flowspec route to the target client, wherein the Flowspec route contains target rules that instruct the received traffic to be redirected to one or more target traffic engineering paths SR-Policies.

[0033] In one exemplary embodiment, the method further includes:

[0034] The target rule includes target conditions and target actions. The target conditions include conditions for matching the traffic, and the target actions are action information performed on the traffic after matching it.

[0035] In one exemplary embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0036] In one exemplary embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0037] In one exemplary embodiment, the extended community attribute includes an identifier of the SR-Policy, wherein when the local ID identifies the meaning of the SR-Policy group or a predefined type value is the meaning of the SR-Policy group, the identifier of the SR-Policy group is carried in the SR-Policy identifier field.

[0038] According to another embodiment of the present invention, a route acquisition device is provided, comprising:

[0039] The acquisition module is used to acquire the Flowspec route from the controller, wherein the Flowspec route contains target rules, which are used to indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policies.

[0040] According to another embodiment of the present invention, a routing transmission device is provided, comprising:

[0041] The sending module is used to send a Flowspec route to a target client, wherein the Flowspec route contains target rules that indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policies.

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

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

[0044] Through this invention, since the Flowspe routing specification is sent from the control terminal to the client, the client can optimize the route selection according to the filtering and matching rules carried in the Flowspe route, thereby realizing the adjustment and optimization of the traffic path. Therefore, it can solve the problem of poor network optimization in related technologies and improve the efficiency of network optimization. Attached Figure Description

[0045] Figure 1 This is a flowchart of a route acquisition method according to an embodiment of the present invention;

[0046] Figure 2 This is a flowchart of a routing and sending method according to an embodiment of the present invention;

[0047] Figure 3 This is a structural block diagram of a route acquisition device according to an embodiment of the present invention;

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

[0049] Figure 5 This is a structural schematic diagram according to a specific embodiment of the present invention;

[0050] Figure 6 This is a flowchart of a specific embodiment of the present invention;

[0051] Figure 7 This is a schematic diagram of an extended community attribute structure according to a specific embodiment of the present invention;

[0052] Figure 8 This is a schematic diagram of the extended tunnel encapsulation attribute structure according to a specific embodiment of the present invention;

[0053] Figure 9 This is a structural schematic diagram of a specific embodiment two according to the present invention;

[0054] Figure 10 This is a structural schematic diagram of a specific embodiment five of the present invention. Detailed Implementation

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

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

[0057] The methods and embodiments provided in this application can be executed in a mobile terminal, a computer terminal, or a similar device. The similar device includes, but is not limited to, interactive devices such as switches and routers. The mobile terminal can be (but is not limited to) a mobile phone or other devices with remote communication functions.

[0058] This embodiment provides a route acquisition method. Figure 1 This is a flowchart of a route acquisition method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0059] Step S202: Obtain the Flowspec route from the controller, wherein the Flowspec route contains target rules, which are used to indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policies.

[0060] In this embodiment, since the controller sends the Flowspec route containing the target rules to the client, the client can match and filter the traffic according to the target rules and send the filtered traffic to the processing node corresponding to the target rules. This can optimize the traffic transmission path and improve traffic processing efficiency.

[0061] The controller can be a device, module, or node with logic calculation function, such as a CPU or FPGA. The client can be one or more nodes on the SR-Policy. The Flowspec route can be sent simultaneously, sequentially, or one by one.

[0062] Through the above steps, since the controller sends the Flowspec route containing the target rules to the client, the client can match and filter the traffic according to the target rules and send the filtered traffic to the processing node corresponding to the target rules. This enables rapid path optimization, thereby adjusting and optimizing the traffic path, solving the problem of poor network optimization in related technologies, and improving network optimization efficiency. Furthermore, since the Flowspec route containing the target rules can be sent at the same time or at different times, and there can be one or more Flowspec routes, it is possible to redirect the same service or traffic received at the same time or at different times to one or more SR-policies, improving the processing efficiency of traffic or the same service.

[0063] The entities that perform the above steps can be base stations, terminals, etc., but are not limited to these.

[0064] In an optional embodiment, after obtaining the Flowspec route from the controller, the method further includes:

[0065] Step S204: After receiving traffic, redirect the traffic to one or more target SR-Policies based on the target rules.

[0066] In this embodiment, after receiving traffic, the traffic is matched and filtered according to the target rules, and then the filtered traffic is sent to the target SR-Policy to achieve traffic redirection.

[0067] In an optional embodiment, the target rule includes target conditions and target actions, wherein the target conditions include conditions for matching traffic, and the target actions are action information performed on the traffic after matching the traffic.

[0068] In this embodiment, the conditions for matching traffic may include (but are not limited to) the source address SA, destination address DA, traffic encoding format, traffic identifier, DSCP (Differentiated Services Code Point), etc.; the action information performed on the traffic includes (but is not limited to) instructions for performing operations such as forwarding, identification, encoding / decoding, and storage on the traffic, destination address, storage location, etc.

[0069] It should be noted that there can be multiple target conditions and target actions, and in this case, there can also be multiple corresponding action information and conditions.

[0070] In an optional embodiment, the target condition is carried in the network layer reachability information (NIRL) included in the Flowspec route.

[0071] In an optional embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0072] In an optional embodiment, the extended community attribute includes a target bit used to identify the target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute overrides other community attributes, or the extended community attribute coexists with other community attributes.

[0073] In this embodiment, the settings can be configured (but are not limited to) in the following ways: when the target bit is set to 1, it means that for the same matching condition, the node will generate a new filtering rule and will not overwrite the previously generated filtering rule; when the target bit is not set, it means that for the same matching condition, the node will generate only one filtering rule and overwrite the previously generated filtering rule.

[0074] In an optional embodiment, the extended community attributes and other community attributes are sent by the controller at the same time or at different times.

[0075] In an optional embodiment, the extended community attribute is set for the same group of streams or the same service, along with other community attributes.

[0076] In an optional embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0077] In this embodiment, the target field can be ID-Type (ID type) or other fields.

[0078] In an optional embodiment, the predetermined value includes at least one of the following:

[0079] The type value of the local ID, and the predefined type value.

[0080] In this embodiment, the predetermined value may also be one of the following values:

[0081] 1: SID(index), the corresponding Generalized indirection_id is SID(index);

[0082] 2: SID(Label), the corresponding Generalized indirection_id is SID(Label);

[0083] 3: BSID(index), the corresponding Generalized indirection_id is BSID(index);

[0084] 4: BSID(label), the corresponding Generalized indirection_id is BSID(label);

[0085] 5: Tunnel ID, the corresponding Generalized indirection_id is the tunnel ID.

[0086] In an optional embodiment, the extended community attribute includes an SR-Policy identifier, wherein the SR-Policy identifier is carried in the SR-Policy identifier field when the local ID identifies the meaning of the SR-Policy group or when a predefined type value is the meaning of the SR-Policy group.

[0087] In this embodiment, in order to identify the meaning of SR-Policy groups, an SR-Policy identifier field needs to be set in the Flowspec route to identify the meaning of SR-Policy groups and their member SR-Policies.

[0088] In an optional embodiment, the Flowspec route further includes an extended tunnel encapsulation attribute, which identifies a member SR-Policy in the target SR-Policy group if the target SR-Policy includes an SR-Policy type identified by a predetermined value.

[0089] In this embodiment, when there are multiple SR-Policies, in order to achieve the effect of carrying the target SR-Policy group, an extended tunneling encapsulation attribute can be set, and the action information of the target action can be carried by the extended tunneling encapsulation attribute and the extended group attribute.

[0090] In an optional embodiment, the Flowspec route also includes an extended tunneling encapsulation attribute, with the target action jointly carried by the extended community attribute and the extended tunneling encapsulation attribute.

[0091] In an optional embodiment, redirecting received traffic to a target SR-Policy based on a target rule includes:

[0092] Step S2042: Match traffic according to target conditions;

[0093] Step S2044: If a target action corresponding to the traffic is matched, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy.

[0094] In an optional embodiment,

[0095] Matching traffic according to target conditions includes: matching traffic in a pre-generated first-flow matching table entry, wherein the first-flow matching table entry includes corresponding target conditions and target actions, the target conditions are used to indicate matching information, and the target actions are used to indicate SR-Policy;

[0096] When a target action corresponding to the traffic is matched, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy, which includes: when a traffic is matched in a pre-generated first-stream matching entry, the traffic is redirected to the target SR-Policy included in the first-stream matching entry.

[0097] In this embodiment, the creation of the first flow match can be done by the controller and sent to the client by the controller along with the Flowspec route.

[0098] In an optional embodiment, after address matching of the traffic in a pre-generated first flow matching entry, the method further includes:

[0099] If no target action corresponding to the traffic is matched in the pre-generated first flow matching entry, a first instruction is sent to the processor to instruct the processor to generate a second flow matching entry, wherein the second flow matching entry includes conditions for indicating the target.

[0100] In this embodiment, if no target action corresponding to the traffic is matched, the data is sent to the CPU to trigger the generation of a related second flow matching entry. At this time, the forwarding action is copied from the latest BGP-FS for SRv6 Policy (such as SRv6 Policy-2 issued at time T2).

[0101] In an optional embodiment, the method further includes:

[0102] Step S206: Receive a second instruction from the processor;

[0103] Step S208: Delete the first stream matching entry based on the second instruction.

[0104] In this embodiment, the platform needs to collect traffic statistics for specific "flow entries" on the forwarding plane. If no new traffic is found within a certain period of time, the specific "flow entry" is aged out and a deletion command is sent to the forwarding plane to instruct the forwarding plane to delete the specific flow entry.

[0105] In an optional embodiment, such as Figure 2 As shown, this embodiment also provides a routing transmission method, including:

[0106] Step S302: Send a Flowspec route to the target client. The Flowspec route contains target rules that indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policies.

[0107] In an optional embodiment, the target rule includes target conditions and target actions, wherein the target conditions include conditions for matching traffic, and the target actions are action information performed on the traffic after matching the traffic.

[0108] In an optional embodiment, the target condition is carried in the network layer reachability information (NIRL) included in the Flowspec route.

[0109] In an optional embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0110] In an optional embodiment, the extended community attribute includes a target bit used to identify the target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute overrides other community attributes, or the extended community attribute coexists with other community attributes.

[0111] In an optional embodiment, the extended community attributes and other community attributes are sent by the controller at the same time or at different times.

[0112] In an optional embodiment, the extended community attribute is set for the same group of streams or the same service, along with other community attributes.

[0113] In an optional embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0114] In an optional embodiment, the predetermined value includes at least one of the following:

[0115] The type value of the local ID, and the predefined type value.

[0116] In an optional embodiment, the extended community attribute includes an SR-Policy identifier, wherein the SR-Policy identifier is carried in the SR-Policy identifier field when the local ID identifies the meaning of the SR-Policy group or when a predefined type value is the meaning of the SR-Policy group.

[0117] In an optional embodiment, the Flowspec route further includes an extended tunnel encapsulation attribute, which identifies a member SR-Policy in the target SR-Policy group if the target SR-Policy includes an SR-Policy type identified by the predetermined value.

[0118] In an optional embodiment, the Flowspec route also includes an extended tunneling encapsulation attribute, with the target action jointly carried by the extended community attribute and the extended tunneling encapsulation attribute.

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

[0120] This embodiment also provides a route acquisition device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs 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.

[0121] Figure 3 This is a structural block diagram of a route acquisition device according to an embodiment of the present invention, such as... Figure 3 As shown, the device includes:

[0122] The acquisition module 42 is used to acquire the flow specification Flowspec route from the controller, wherein the Flowspec route contains target rules, which are used to indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policy.

[0123] In an optional embodiment, the device further includes:

[0124] Redirect module 44 is used to redirect traffic to the target SR-Policy based on the target rule after receiving traffic, after obtaining the Flowspec route from the controller.

[0125] In an optional embodiment, the target rule includes target conditions and target actions, wherein the target conditions include conditions for matching traffic, and the target actions are action information performed on the traffic after matching the traffic.

[0126] In an optional embodiment, the target condition is carried in the network layer reachability information (NIRL) included in the Flowspec route.

[0127] In an optional embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0128] In an optional embodiment, the extended community attribute includes a target bit used to identify the target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute overrides other community attributes, or the extended community attribute coexists with other community attributes.

[0129] In an optional embodiment, the extended community attributes and other community attributes are sent by the controller at the same time or at different times.

[0130] In an optional embodiment, the extended community attribute is set for the same group of streams or the same service, along with other community attributes.

[0131] In an optional embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0132] In an optional embodiment, the predetermined value includes at least one of the following:

[0133] The type value of the local ID, and the predefined type value.

[0134] In an optional embodiment, the extended community attribute includes an SR-Policy identifier, wherein the SR-Policy identifier is carried in the SR-Policy identifier field when the local ID identifies the meaning of the SR-Policy group or when a predefined type value is the meaning of the SR-Policy group.

[0135] In an optional embodiment, the Flowspec route further includes an extended tunnel encapsulation attribute, which identifies a member SR-Policy in the target SR-Policy group if the target SR-Policy includes an SR-Policy type identified by a predetermined value.

[0136] In this embodiment, when there are multiple SR-Policies, in order to achieve the effect of carrying the target SR-Policy group, an extended tunneling encapsulation attribute can be set, and the action information of the target action can be carried by the extended tunneling encapsulation attribute and the extended group attribute.

[0137] In an optional embodiment, the Flowspec route also includes an extended tunneling encapsulation attribute, with the target action jointly carried by the extended community attribute and the extended tunneling encapsulation attribute.

[0138] In an optional embodiment, the redirection module 44 includes:

[0139] Matching unit 42 is used to match traffic according to target conditions;

[0140] Redirection unit 44 is used to process the traffic according to the target action when a target action corresponding to the traffic is matched, so as to redirect the traffic to the target SR-Policy.

[0141] In an optional embodiment,

[0142] Matching unit 42 includes:

[0143] The first entry matching subunit 422 is used to match traffic in a pre-generated first flow matching entry, wherein the first flow matching entry includes a corresponding target condition and a target action, the target condition is used to indicate matching information, and the target action is used to indicate SR-Policy;

[0144] Redirection unit 44 includes:

[0145] Redirection subunit 442 is used to redirect traffic to a target SR-Policy included in the first-stream matching entry if a match is found in the pre-generated first-stream matching entry.

[0146] In an optional embodiment, the device further includes:

[0147] The second entry generation unit 424 is used to send a first instruction to the processor after performing address matching on the traffic in the pre-generated first flow matching entry, in the case that no target action corresponding to the traffic is matched in the pre-generated first flow matching entry, to instruct the processor to generate a second flow matching entry, wherein the second flow matching entry includes a target condition.

[0148] In an optional embodiment, the device further includes:

[0149] Instruction receiving module 46 is used to receive a second instruction from the processor;

[0150] The entry deletion module 48 is used to delete the first stream matching entries based on the second instruction.

[0151] Figure 4 This is a structural block diagram of a routing transmission device according to an embodiment of the present invention, such as... Figure 4 As shown, the device includes:

[0152] Sending module 52 is used to send a Flowspec route to the target client, wherein the Flowspec route contains target rules, which are used to instruct the received traffic to be redirected to one or more target traffic engineering paths SR-Policies.

[0153] In an optional embodiment, the target rule includes target conditions and target actions, wherein the target conditions include conditions for matching traffic, and the target actions are action information performed on the traffic after matching the traffic.

[0154] In an optional embodiment, the target condition is carried in the network layer reachability information (NIRL) included in the Flowspec route.

[0155] In an optional embodiment, the target action is carried in an extended community attribute included in the Flowspec route.

[0156] In an optional embodiment, the extended community attribute includes a target bit used to identify the target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute overrides other community attributes, or the extended community attribute coexists with other community attributes.

[0157] In an optional embodiment, the extended community attributes and other community attributes are sent by the controller at the same time or at different times.

[0158] In an optional embodiment, the extended community attribute is set for the same group of streams or the same service, along with other community attributes.

[0159] In an optional embodiment, the extended community attribute includes a target field, wherein the value of the target field is a predetermined value used to indicate the identifier type of the target SR-Policy.

[0160] In an optional embodiment, the predetermined value includes at least one of the following:

[0161] The type value of the local ID, and the predefined type value.

[0162] In an optional embodiment, the extended community attribute includes an SR-Policy identifier, wherein the SR-Policy identifier is carried in the SR-Policy identifier field when the local ID identifies the meaning of the SR-Policy group or when a predefined type value is the meaning of the SR-Policy group.

[0163] In an optional embodiment, the Flowspec route further includes an extended tunnel encapsulation attribute, which identifies a member SR-Policy in the target SR-Policy group if the target SR-Policy includes an SR-Policy type identified by a predetermined value.

[0164] In this embodiment, when there are multiple SR-Policies, in order to achieve the effect of carrying the target SR-Policy group, an extended tunneling encapsulation attribute can be set, and the action information of the target action can be carried by the extended tunneling encapsulation attribute and the extended group attribute.

[0165] In an optional embodiment, the Flowspec route also includes an extended tunneling encapsulation attribute, with the target action jointly carried by the extended community attribute and the extended tunneling encapsulation attribute.

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

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

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

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

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

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

[0172] The present invention will now be described with reference to specific embodiments. Specific Implementation Example 1

[0174] like Figure 5 and Figure 6 As shown, the specific implementation steps of the present invention mainly include:

[0175] Step 701: The BGPFLOWSPEC controller sends a Flowspc route carrying filtering rules that redirect to one or more SR-Policies (Segment Routing-Policies, Traffic Engineering Paths).

[0176] Step 702: The BGPFlowspec client receives the Flowspec route carrying the extended community attributes and saves the contents of the flow filtering rules.

[0177] The slice / application filtering rules include: matching conditions and actions to be performed after traffic matching; the matching conditions are carried in NLRI (Network Layer Reachability Information), and the matching type included in the matching conditions can be an existing defined Flowspec component type, i.e., based on packet source address / destination address / DSCP, etc. The matching process can match traffic according to the matching conditions; the actions to be performed after traffic matching are carried by extended community attributes, wherein a bit can be set in the existing redirection community attribute to indicate whether the community attribute covers other community attributes sent at the same time / simultaneously or coexists.

[0178] It should be noted that the extended redirection community property includes the following:

[0179] 1) The format of the extended community attribute for redirecting to indirection-id (indirect ID) is as follows: Figure 7 As shown in the figure:

[0180] Setting bit N to 1 means that for the same matching condition, the node will generate a new filtering rule, which will not overwrite the previously generated filtering rule.

[0181] If the N bits are not set, it means that for the same matching condition, the node will generate only one filtering rule, which will overwrite the previously generated filtering rule.

[0182] besides, Figure 7 It also includes:

[0183] ID-Type (ID type):

[0184] 0: Local ID, the corresponding Generalized indirection_id is the local ID;

[0185] 1: SID(index), the corresponding Generalized indirection_id is SID(index);

[0186] 2: SID(Label), the corresponding Generalized indirection_id is SID(Label);

[0187] 3: BSID(index), the corresponding Generalized indirection_id is BSID(index);

[0188] 4: BSID(label), the corresponding Generalized indirection_id is BSID(label);

[0189] 5: Tunnel ID, the corresponding Generalized indirection_id is the tunnel ID.

[0190] 2) The format of the extended community attribute for redirecting to indirection-id is as follows: Figure 7 As shown, the ID-type field can be defined using newly defined content, so that the Generalizedindirection_id corresponding to the ID-type field is the SR-Policy group. Alternatively, the ID-type field can be defined using existing content, such as 0: local ID. In this case, the corresponding Generalized indirection_id is the local ID, and the meaning of the local ID is to indicate the SR-Policy group.

[0191] In addition, such as Figure 8 As shown, a new tunnel encapsulation attribute, Sub-TLV:SR-Policy Sub-TLV, can also be defined under the tunnel encapsulation attributes, as shown in the figure:

[0192] Setting bit N to 1 means that for the same matching condition, the node will generate a new filtering rule and will not overwrite the previously generated filtering rule.

[0193] If bit N is not set, it means that for the same matching condition, the node will generate only one filtering rule, which will overwrite the previously generated filtering rule.

[0194] In this example, Color+Endpoint is used to identify an SR-Policy. If multiple SR-Policies need to be identified, multiple SR-Policy Sub-TLVs need to be carried. BSID can also be used to identify an SR-policy. The format of the SR-policysub-TLV is diverse; this embodiment only provides one format.

[0195] At this point, the action to be executed after traffic matching can be carried together by <redirecting to the extended community attribute of the extended indirection-id, the new tunnel encapsulation attribute Sub-TLV:SR-Policy Sub-TLV>, to achieve the effect of carrying multiple SR-Policies.

[0196] It should be noted that flow filtering rules consist of two parts: the matching type and the action to be performed. The matching type is carried by the NLRI in the Flowspec route, and the action to be performed is carried by the extended community attribute. Specific Implementation Example 2

[0198] like Figure 9 As shown, when host client 1 needs to access remote computing resource Service 1, the controller will inform the BGPFlowspec client of the latest redirection policy for a certain service in real time. The basic principle of this redirection policy is to redirect to a relatively idle cloud resource pool. The idle status of the cloud resource pool can be obtained through polling, access, etc. To implement the redirection policy, the filtering rules issued at different times need to be able to redirect to multiple SR-Policies. Specifically... Figure 9 In this embodiment, the Segment List corresponding to SR-Policy1 is {PE1}, and the Segment List corresponding to SR-Policy2 is {PE2}. At this time, the Binding SID is used to identify an SR-Policy.

[0199] At this point, the specific steps are as follows:

[0200] Step 1001: When host client 1 needs to access remote computing resource Service 1, it generates a business message.<SA=client1-IP,DA=service1-IP> And send the service message to gateway PE3.

[0201] Step 1002: On gateway PE3, first, based on the characteristics of the service packets...<SA,DA> It matches "flow matching rule entries", where the entries contained in the "flow matching rule entries" are similar to those in traditional policy routing entries (and can be maintained uniformly during implementation). It can guide business packets to the SR Policy to reach the cloud resource pool of the other end. At this time, the SR Policy is an SRv6 Policy in PIv6 format.

[0202] It should be noted that before encapsulating the service packet with the outer SRv6 Policy, PE3 needs to perform NAT translation on the SA of the service packet and change it to the public IP address of PE3 (PE3-NAT-IP).

[0203] The creation of the "stream filtering rule entry" mainly involves two steps:

[0204] 1) The controller informs the BGP Flowspec client of the latest redirection policy for a certain service in real time. The basic principle is to redirect to a relatively idle cloud resource pool.

[0205] Subsequently, the BGP Flowspec client receives the flow-route redirected to the SRv6 Policy from the controller via BGP-Flowspec. The BGP flow-route carries the following information:

[0206] Matching criteria: Carried by NLRI, and the specific format of the matching criteria is: match DA:service IP;

[0207] The action following the match: is carried over to the extended community attribute of the extended indirection-id, specifically in the following format:

[0208] action:set<redirecting to the extended community property of the extended indirection-id: Binding SID1>.

[0209] Specifically, an additional flag, N, is added to the extended community attribute of the extended indirection-id. This flag indicates that when multiple extended community attributes of the extended indirection-id are carried at different times for the same matching condition, the relationship between the community attributes is not overlapping, but an additional relationship. The rest of the format remains unchanged.

[0210] Among them, Binding SID is used to associate SR-Policy, Binding SID1 is used to associate SR-Policy1, and Binding SID2 is used to associate SR-Policy2, that is:

[0211] At time T1, the controller receives a flow-route: match service-1 IP, set Binding SID1, where the Segment List of SRv6 Policy-1 is {PE1}, indicating that the service flow should be directed to resource pool A.

[0212] At time T2, the controller receives the flow-route command: match service-1 IP, set Binding SID2. The Segment List of SRv6 Policy-2 is {PE2}, indicating that the service flow should be directed to resource pool B.

[0213] 2) The BGP Flowspec client generates two entries in the "Flow Matching Filtering Entries".

[0214] The contents of the “Stream Matching Filtering Entries” are shown in Table 1.

[0215] Table 1

[0216]

[0217] In addition, when the forwarding plane finds that a service packet cannot match a flow table entry (SA, DA), it will send it to the CPU to trigger the generation of the relevant flow table entry. Its forwarding action is copied from the latest issued BGP-FS for SRv6 Policy (such as SRv6 Policy-2 issued at time T2).

[0218] In addition, the platform needs to collect traffic statistics for specific "flow entries" on the forwarding surface. If no new traffic is found within a certain period of time, the specific "flow entry" will be aged out and a deletion order will be sent to the forwarding surface. Specific Implementation Example 3:

[0220] The working scenario is as described in Specific Embodiment Two, but the difference lies in that, in this embodiment, color+Endpoint is used to identify SR-Policy, and the creation of the "Stream Filtering Rule Entries" is different. In this embodiment, the creation of the "Stream Filtering Rule Entries" involves two steps:

[0221] 1) The controller informs the BGP Flowspec client of the latest redirection policy for a certain service in real time. The basic principle is to redirect to a relatively idle cloud resource pool.

[0222] Subsequently, the BGP Flowspec client receives the flow-route redirected to the SRv6 Policy from the controller via BGP-Flowspec. The BGP flow-route carries the following information:

[0223] Matching criteria: Carried by NLRI, with the specific format: match DA:service IP;

[0224] The matched action is carried by the extended community attribute of the redirected indirection-id and the tunnel encapsulation attribute SR-Policy Sub-TLV, specifically in the following format:

[0225] action:set<redirecting to the extended community attribute of the indirection-id: SR Policy group identifier, SR-Policy Sub-TLV: color+Endponit>.

[0226] Among them, for community attributes that redirect to the extended indirection-id, the SR Policy group has two extensions: one is to use the community attribute format of the redirected indirection-id extension, such as... Figure 7 As shown, the ID-type field defines a new type: SR-Policy group, corresponding to Generalized indirection_id as SR-Policy group or using the existing 0; another option is to use the existing ID-type field, 0: local ID, corresponding to Generalizedindirection_id as local ID, which means SR-Policy group.

[0227] The SR-Policy Sub-TLV is used to carry color+endpoint to identify an SR-Policy. The SR-Policy Sub-TLV is a newly defined tunnel encapsulation attribute Sub-TLV, which can carry multiple attributes.

[0228] for example:

[0229] At time T1, the controller receives the flow-route: match service-1 IP, set <the community attribute of the extension to the extension indirection-id: SR Policy group identifier: 1, SR-Policy Sub-TLV: color C1+Endponit: PE1>, where the Segment List of SRv6 Policy-1 is {PE1}, and it is desired to direct the service flow to resource pool A.

[0230] At time T2, the controller receives the flow-route: match service-1 IP, set <the community attribute of the extension to the extension indirection-id: SR Policy group identifier: 1, SR-Policy Sub-TLV: color C2+Endponit: PE2>, where the Segment List of SRv6 Policy-2 is {PE2}, and it is desired to direct the service flow to resource pool B.

[0231] Since the SR-Policy Sub-TLV carries N bits, and the N bits are set to 1, it means that for the same matching condition, the node will generate a new filtering rule and will not overwrite the previously generated filtering rule.

[0232] 2) The BGP Flowspec client generates two entries in the "Flow Matching Filtering Entries".

[0233] The contents of the “Stream Matching Filtering Entries” are shown in Table 2:

[0234] Table 2

[0235]

[0236] In addition, if the forwarding plane finds that a service packet cannot match a flow table entry (SA, DA), it will send the message to the CPU to trigger the generation of the relevant flow table entry. Its forwarding action is copied from the latest BGP-FS for SRv6 Policy (such as SRv6 Policy-2 issued at time T2).

[0237] The platform needs to collect traffic statistics for specific "flow entries" on the forwarding plane. If no new traffic is found within a certain period of time, the specific "flow entry" will be aged out and a deletion order will be sent to the forwarding plane. Specific Implementation Example 4:

[0239] The difference from Specific Implementation Example 2 is that in this embodiment, at the same time, a group of traffic will be redirected to multiple SR-Policies simultaneously. At this time, Binding SID is used to identify SR-Policies, where Binding SID1 identifies SR-Policy1 and Binding SID2 identifies SR-Policy2. The process of "flow filtering rule entries" will be described below.

[0240] This embodiment specifically includes the following steps:

[0241] Step 1101: The BGP FLOWSPEC controller sends a Flowspc route carrying filtering rules that redirect to one or more SR-Policies.

[0242] Step 1102: The BGP Flowspec client generates "flow matching filter entries".

[0243] The BGP flow-route carries the following information:

[0244] Matching criteria: carried by NLRI, with the specific format: match DA;

[0245] The matched action can be carried by the extended community attribute of the extended indirection-id, specifically in the following format:

[0246] action:set<community property of the extension of the indirection-id: Binding SID1, Binding SID2>.

[0247] It can also be carried together by the extended community attribute of the redirected indirection-id and the tunnel encapsulation attribute, with the following format:

[0248] action:set<redirecting to the extended community attribute of the indirection-id: SR Policy group identifier: 1, SR-Policy Sub-TLV: color C1+Endponit: PE1, SR-Policy Sub-TLV: color C2+Endponit: PE2>.

[0249] For the community attribute of the redirected indirection-id, the SR Policy group has two extension methods: one is to use the community attribute format of the redirected indirection-id extension, such as... Figure 7 As shown, the ID-type field defines a new type: SR-Policy group, corresponding to Generalized indirection_id as SR-Policy group or using the existing 0; another option is to use the existing ID-type field, 0: local ID, corresponding to Generalizedindirection_id as local ID, which means SR-Policy group.

[0250] At the same time, an additional flag, N, is added to the extended community attribute of the extended indirection-id. This flag indicates that when multiple extended community attributes of the extended indirection-id are carried simultaneously for the same matching condition, the relationship between the community attributes is not overlapping, but rather an additional relationship. All other formatting remains unchanged.

[0251] The partial contents of the "Stream Matching Filtering Entries" are shown in Table 3:

[0252] Table 3

[0253] Matching conditions Action after traffic matching <da> < / da> Binding SID1 <da> < / da> Binding SID2

[0254] In addition, when the forwarding plane finds that a service packet cannot match a flow table entry (DA), it will send it to the CPU to trigger the generation of the relevant flow table entry. Its forwarding action is copied from the latest issued BGP-FS for SRv6 Policy (such as BindingSID1 and Binding SID2).

[0255] The platform needs to collect traffic statistics for specific "flow entries" on the forwarding plane. If no new traffic is found within a certain period of time, the specific "flow entry" will be aged out and a deletion order will be sent to the forwarding plane. Specific Implementation Example 5:

[0257] The difference from Specific Embodiment Two is that, as Figure 10As shown, in this embodiment, at the same time, a group of traffic will be redirected to multiple SR-Policies simultaneously. In this embodiment, color+endpoint is used to identify SR-Policies. Specifically, color C1+Endpoint:D identifies SR-Policy1, and color C2+Endpoint:D identifies SR-Policy2. The process of "flow filtering rule entries" will be described below.

[0258] Step 1201: The BGP FLOWSPEC controller sends a Flowspc route carrying filtering rules that redirect to one or more SR-Policies.

[0259] Step 1202: The BGP Flowspec client generates "flow matching filter entries".

[0260] The BGP flow-route carries the following information:

[0261] Matching criteria: carried by NLRI, in the format: match DA;

[0262] The matched action is jointly carried by the extended community attribute of the redirected indirection-id and the tunnel encapsulation attribute, in the following format:

[0263] action:set<redirecting to the extended community attribute of the indirection-id: SR Policy group identifier: 1, SR-Policy Sub-TLV: color C1+Endponit: D, SR-Policy Sub-TLV: color C2+Endponit: D>.

[0264] The community attribute for redirecting to the extended indirection-id is as follows: The SR Policy group has two types of extensions: one uses the community attribute format for redirecting to the extended indirection-id, such as... Figure 7 As shown, the ID-type field defines a new type: SR-Policy group, corresponding to Generalized indirection_id as SR-Policy group or using the existing 0; another option is to use the existing ID-type field, 0: local ID, corresponding to Generalizedindirection_id as local ID, which means SR-Policy group.

[0265] The partial contents of the “Stream Matching Filtering Entries” are shown in Table 4:

[0266] Table 4

[0267]

[0268] In addition, when the forwarding plane finds that a service packet cannot match a flow table entry (DA), it will send it to the CPU to trigger the generation of the relevant flow table entry, and its forwarding action will copy the latest issued BGP-FS for SRv6 Policy.

[0269] The platform needs to collect traffic statistics for specific "flow entries" on the forwarding plane. If no new traffic is found within a certain period of time, the specific "flow entry" will be aged out and a deletion order will be sent to the forwarding plane.

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

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

Claims

1. A route acquisition method, characterized in that, include: Obtain the Flowspec route from the controller, wherein the Flowspec route contains target rules that indicate to redirect received traffic to one or more target traffic engineering paths SR-Policies; The target rule includes target conditions and target actions. The target conditions include conditions for matching the traffic, and the target actions are the action information performed on the traffic after matching it. The target action is carried in the extended community attribute included in the Flowspec route; The extended community attribute includes a target field, the value of which is a predetermined value used to indicate the identifier type of the target SR-Policy. The Flowspec route further includes an extended tunnel encapsulation attribute, which is used to identify member SR-Policies in the target SR-Policy group when the target SR-Policy includes the SR-Policy type identified by the predetermined value.

2. The method according to claim 1, characterized in that, After obtaining the Flowspec route from the controller, the method further includes: Upon receiving the traffic, the traffic is redirected to the target SR-Policy based on the target rule.

3. The method according to claim 1, characterized in that, The target condition is carried in the Network Layer Reachability Information (NIRL) contained in the Flowspec route.

4. The method according to claim 1, characterized in that, The extended community attribute includes a target bit, which is used to identify the target relationship between the extended community attribute and other received community attributes, wherein the target relationship includes one of the following: the extended community attribute covers the other community attributes, or the extended community attribute coexists with the other community attributes.

5. The method according to claim 4, characterized in that, The extended community attribute, along with the other community attributes, is sent by the controller at the same time or at different times.

6. The method according to claim 5, characterized in that, The extended community attribute is set for the same group of streams or the same service, along with the other community attributes.

7. The method according to claim 1, characterized in that, The predetermined value includes at least one of the following: The type value of the local ID, and the predefined type value.

8. The method according to claim 1, characterized in that, The extended group attribute includes the identifier of the SR-Policy, wherein when the local ID identifies the meaning of the SR-Policy group or the predefined type value is the meaning of the SR-Policy group, the identifier of the SR-Policy group is carried in the SR-Policy identifier field.

9. The method according to claim 1, characterized in that, The Flowspec route also includes extended tunneling encapsulation attributes, and the target action is jointly carried by the extended community attributes and the extended tunneling encapsulation attributes.

10. The method according to claim 2, characterized in that, The step of redirecting the traffic to the target SR-Policy based on the target rule includes: The traffic is matched according to the target conditions; If a target action is matched with the traffic, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy.

11. The method according to claim 10, characterized in that, Matching the traffic according to the target conditions includes: matching the traffic in a pre-generated first flow matching table entry, wherein the first flow matching table entry includes corresponding target conditions and target actions, the target conditions are used to indicate matching information, and the target actions are used to indicate SR-Policy; When a target action corresponding to the traffic is matched, the traffic is processed according to the target action to redirect the traffic to the target SR-Policy, which includes: when a match is found in the pre-generated first flow matching entry, the traffic is redirected to the target SR-Policy included in the first flow matching entry.

12. The method according to claim 11, characterized in that, After performing address matching on the traffic in a pre-generated first flow matching entry, the method further includes: If no target action corresponding to the traffic is matched in the pre-generated first flow matching entry, a first instruction is sent to the processor to instruct the processor to generate a second flow matching entry, wherein the second flow matching entry includes information indicating the target condition.

13. The method according to claim 11, characterized in that, The method further includes: Receive the second instruction from the processor; The first stream matching entry is deleted based on the second instruction.

14. A routing transmission method, characterized in that, include: Send a Flowspec route to the target client, wherein the Flowspec route contains a target rule that instructs the received traffic to be redirected to one or more target traffic engineering paths SR-Policies; The method further includes: the target rule includes target conditions and target actions, the target conditions include conditions for matching the traffic, and the target action is action information performed on the traffic after matching the traffic; The target action is carried in the extended community attribute included in the Flowspec route; The extended community attribute includes a target field, the value of which is a predetermined value used to indicate the identifier type of the target SR-Policy. The Flowspec route further includes an extended tunnel encapsulation attribute, which is used to identify member SR-Policies in the target SR-Policy group when the target SR-Policy includes the SR-Policy type identified by the predetermined value.

15. The method according to claim 14, characterized in that, The extended group attribute includes the identifier of the SR-Policy, wherein when the local ID identifies the meaning of the SR-Policy group or the predefined type value is the meaning of the SR-Policy group, the identifier of the SR-Policy group is carried in the SR-Policy identifier field.

16. A route acquisition device, characterized in that, include: The acquisition module is used to acquire the Flowspec route from the controller, wherein the Flowspec route contains target rules, which are used to indicate that the received traffic should be redirected to one or more target traffic engineering paths SR-Policies; The target rule includes target conditions and target actions. The target conditions include conditions for matching the traffic, and the target actions are the action information performed on the traffic after matching it. The target action is carried in the extended community attribute included in the Flowspec route; The extended community attribute includes a target field, the value of which is a predetermined value used to indicate the identifier type of the target SR-Policy. The Flowspec route further includes an extended tunnel encapsulation attribute, which is used to identify member SR-Policies in the target SR-Policy group when the target SR-Policy includes the SR-Policy type identified by the predetermined value.

17. A routing transmission device, characterized in that, include: The sending module is used to send a Flowspec route to the target client, wherein the Flowspec route contains a target rule, which is used to instruct the received traffic to be redirected to one or more target traffic engineering paths SR-Policies; The target rule includes target conditions and target actions. The target conditions include conditions for matching the traffic, and the target actions are the action information performed on the traffic after matching it. The target action is carried in the extended community attribute included in the Flowspec route; The extended community attribute includes a target field, the value of which is a predetermined value used to indicate the identifier type of the target SR-Policy. The Flowspec route further includes an extended tunnel encapsulation attribute, which is used to identify member SR-Policies in the target SR-Policy group when the target SR-Policy includes the SR-Policy type identified by the predetermined value.

18. 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 15.

19. 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 15.