WO2022247689A1 - 流量报文转发方法、客户端、控制器及存储介质 - Google Patents

流量报文转发方法、客户端、控制器及存储介质 Download PDF

Info

Publication number
WO2022247689A1
WO2022247689A1 PCT/CN2022/093301 CN2022093301W WO2022247689A1 WO 2022247689 A1 WO2022247689 A1 WO 2022247689A1 CN 2022093301 W CN2022093301 W CN 2022093301W WO 2022247689 A1 WO2022247689 A1 WO 2022247689A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
traffic
block resource
forwarding
identifier
Prior art date
Application number
PCT/CN2022/093301
Other languages
English (en)
French (fr)
Inventor
吴海生
陈然
王为宝
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP22810416.2A priority Critical patent/EP4311311A1/en
Publication of WO2022247689A1 publication Critical patent/WO2022247689A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227—Filtering policies

Definitions

  • the embodiments of the present application relate to but are not limited to the field of communications, and in particular, relate to a method for forwarding traffic packets, a client, a controller, and a storage medium.
  • Routing entries only contain prefix mask information for destination address matching and traffic outbound interface information.
  • the complexity of the network increases.
  • the requirements for routing It is getting higher and higher, and the information supporting the traffic policy is usually added to the routing table entry, that is, the data flow in the forwarding routing table item is subdivided, but the routing of the information supporting the traffic policy belongs to the local behavior, which needs to be performed on each device.
  • Configuration, manual configuration requires a lot of work and requires high requirements for operation and maintenance personnel.
  • 5G network applications there are requirements for flexible scheduling and massive connections.
  • Existing routing technologies cannot meet customers' needs for traffic path adjustment and optimization.
  • the embodiment of the present application proposes a flow packet forwarding method, a client, a controller, and a storage medium.
  • the embodiment of the present application provides a flow message forwarding method, including: receiving the flow message; when the flow message includes a block resource identifier, according to the block resource identifier and the filtering rule The information determines the target block resource, and the filtering rule information is obtained by sending the border gateway controller; the target block resource is used to forward the traffic message.
  • the embodiment of the present application also provides a border gateway client, including: a memory, a processor, and a computer program stored on the memory and operable on the processor.
  • a border gateway client including: a memory, a processor, and a computer program stored on the memory and operable on the processor.
  • the processor executes the computer program, the first In one aspect, the traffic message forwarding method.
  • the embodiment of the present application also provides a traffic packet forwarding method, including: sending filtering rule information carrying block resource identifiers to the border gateway client, so that the border gateway client The information determines the target block resource of the flow message, and forwards the flow message according to the target block resource, and the flow message is received by the border gateway client.
  • the embodiment of the present application also provides a border gateway controller, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, when the processor executes the computer program Realize the traffic packet forwarding method described in the third aspect.
  • a computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the traffic packet forwarding method described in the first aspect, or to execute the method described in the third aspect. Traffic packet forwarding method.
  • FIG. 1 is a schematic diagram of a system architecture for performing a traffic packet forwarding method provided by an embodiment of the present application
  • FIG. 2 is a flow chart of a method for forwarding traffic packets on the border gateway client side provided by an embodiment of the present application
  • Fig. 3 is a schematic diagram of the encapsulation format of the slicing BGP Flowspc Component type in the flow message forwarding method on the border gateway client side provided by an embodiment of the present application;
  • Fig. 4 is a schematic diagram of the community attribute format of the slice identifier in the flow packet forwarding method on the client side of the border gateway provided by an embodiment of the present application;
  • FIG. 5 is a schematic diagram of the SUB-TLV format of the community attribute format in the flow packet forwarding method on the client side of the border gateway provided by an embodiment of the present application;
  • Fig. 6 is a schematic diagram of the community attribute format of the slice identifier in the flow packet forwarding method on the client side of the border gateway provided by an embodiment of the present application;
  • FIG. 7 is a flow chart of forwarding processing of a method for forwarding traffic packets on the border gateway client side provided by an embodiment of the present application
  • FIG. 8 is a flow chart of a flow message forwarding method on the border gateway controller side provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a traffic packet forwarding network provided by an embodiment of the present application.
  • FIG. 10 is a flow chart of a flow packet forwarding method provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a traffic packet forwarding network redirected to slices provided by an embodiment of the present application.
  • FIG. 12 is a flowchart of a method for forwarding traffic packets redirected to slices provided by an embodiment of the present application
  • FIG. 13 is a schematic diagram of a traffic packet forwarding network redirected to slices provided by another embodiment of the present application.
  • FIG. 14 is a flowchart of a method for forwarding traffic packets redirected to slices according to another embodiment of the present application.
  • Fig. 15 is a schematic diagram of a traffic packet forwarding network redirected to slices provided by another embodiment of the present application.
  • FIG. 16 is a flowchart of a method for forwarding traffic packets redirected to slices according to another embodiment of the present application.
  • Fig. 17 is a flow chart of a method for forwarding traffic packets redirected to an application provided by another embodiment of the present application.
  • the embodiment of the present application provides a flow message forwarding method, a client, a controller, and a storage medium.
  • the flow message forwarding method includes but is not limited to the following steps: receiving a flow message; including a block resource identifier in the flow message
  • the target block resource is determined according to the block resource identifier and filtering rule information, and the filtering rule information is sent by the border gateway controller; the target block resource is used to forward the traffic message.
  • the border gateway client when the border gateway client receives the traffic message carrying the block resource identifier, it can determine the target block according to the block resource identifier and the filtering rule information sent by the border gateway controller resources, and then use the target block resource to forward the traffic message; the block resource identifier can be used to flexibly segment network resources, so the target block resource determined by the block resource identifier can forward the traffic message, which can Meet customers' needs for traffic path adjustment and optimization.
  • FIG. 1 is a schematic diagram of a system architecture platform 100 for implementing a traffic packet forwarding method provided by an embodiment of the present application.
  • the system architecture platform 100 is provided with a processor 110 and a memory 120 , wherein the processor 110 and the memory 120 may be connected via a bus or in other ways.
  • connection via a bus is taken as an example.
  • the memory 120 can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory 120 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices.
  • the memory 120 may include memories that are remotely located relative to the processor 110, and these remote memories may be connected to the system architecture platform through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • system architecture platform can be applied to a communication network system and a subsequent evolved mobile communication network system, etc., which is not specifically limited in this embodiment.
  • FIG. 1 does not constitute a limitation to the embodiment of the present application, and may include more or less components than those shown in the illustration, or combine some components, or have different Part placement.
  • the processor 110 can call a service flow management program stored in the memory 120 to execute the flow packet forwarding method.
  • Figure 2 is a flowchart of a flow message forwarding method provided by an embodiment of the present application, the flow message forwarding method is applied to a border gateway client, and the flow message forwarding method includes but is not limited to Step S100, step S200, step S300.
  • Step S100 receiving traffic packets.
  • Step S200 in the case that the traffic message includes a block resource identifier, determine the target block resource according to the block resource identifier and filtering rule information, and the filtering rule information is obtained from the border gateway controller.
  • Step S300 using the target block resource to forward the traffic message.
  • the border gateway client when the border gateway client receives the traffic packet carrying the block resource identifier, it can determine the target block resource according to the block resource identifier and the filtering rule information sent by the border gateway controller, and then use the target block resource Block resources forward and process traffic packets; network resources can be flexibly segmented by using block resource identifiers. Therefore, the target block resources determined by block resource identifiers forward traffic packets, which can satisfy customers' adjustment of traffic paths. Tuning needs.
  • the border gateway client can be applied to the Border Gateway Protocol Flow Specification (BGP Flowspc) of the 5G network.
  • BGP Flowspc Border Gateway Protocol Flow Specification
  • the border network management flow protocol can be Optimization, expand the filter rule information in the border network management flow protocol, add block resource identifiers in the filter rules, that is, the border gateway controller sends the filter rule information carrying the block resource identifier to the border gateway client, and the border gateway client After the terminal receives the filtering rule information carrying the block resource identifier, it installs the filtering rule information into the local mapping information.
  • the border gateway client When the border gateway client receives the traffic message carrying the block resource identifier, the border gateway client can Determine the target block resource according to the block resource identifier of the traffic message and the local mapping information installed with the filtering rule information, and then use the target block resource to forward the traffic message; using the block resource identifier can flexibly manage network resources Segmentation, so the target block resource determined by the block resource identifier forwards the traffic message, which can meet the customer's needs for traffic path adjustment and optimization.
  • block resource identifier may be a slice identifier or an application identifier, which is not specifically limited in this example.
  • the filtering rule information includes matching condition information and execution action information, wherein the matching condition information is carried in the Network Layer Reachability Information (NLRI for short) of the filtering rule, and the execution action information is the traffic matching information. Execution action, the execution action information is carried by the extended community attribute in the filter rule.
  • NLRI Network Layer Reachability Information
  • block resource identifier is carried by matching condition information or execution action information, which is not specifically limited in this embodiment.
  • the matching condition information can use the existing defined flow specification component type information, and the flow specification component type information can be understood as the source address/destination address/differentiated services code point (Differentiated Services Code Point, referred to as DSCP) to match the traffic, or by expanding the information of the border network management flow protocol component type, so that it carries a slice identifier/application identifier, which is used to support slice/application filtering.
  • DSCP Differentiated services code point
  • a slice identifier list or an application identifier list can be set, and the matching can be performed for multiple slice sources or multiple Each application source can be matched without sending multiple traffic rules (matching condition information), which can save memory overhead.
  • SR-Policy Segment Routing Policy
  • SR-TE Segmental Routing-Traffic Engineering
  • SR-TP Segment Routing Transport Profile-Traffic Engineering
  • the community attribute information of the new redirection extension mainly carries the slice identifier/application identifier, and the specific identifier of a certain path.
  • the identifiers of SR-TE tunnels and SR-TP tunnels are tunnel identifiers (Tunnel-Identity Document, Tunnel-ID for short), the identification of SR-policy is a triplet, and the triplet includes destination address, color attribute, and prefix unique identity number (Security Identifiers, SID for short).
  • the BGP Flowspc client can receive the Flowspc routing information carrying the extended community attribute information, and then save the content of the flow filtering rule in the Flowspc routing information.
  • the BGP Flowspc client searches for the forwarding entries in the local mapping information through the slice identifier/application identifier (for the scenario that does not specify a certain path), which can be realized through the existing redirection to the next hop action; the BGP Flowspc client also The corresponding forwarding entry can be directly found and forwarded through a certain path in the slice identifier/application identifier.
  • the forwarding entries in the local mapping information of the BGP Flowspc client can be established through routing protocols between autonomous systems, Interior Gateway Protocols (Interior Gateway Protocols, IGP for short), Label Distribution Protocol (Label Distribution Protocol, LDP for short) , Segmental Routing (SR for short), Resource Reservation Protocol (RSVP for short) and other models are established.
  • IGP Interior Gateway Protocols
  • LDP Label Distribution Protocol
  • SR Segmental Routing
  • RSVP Resource Reservation Protocol
  • the slice identifier may be a slice identifier, a multi-topology identifier, a Flexible-Algorithm (Flex-Algo for short) identifier or a virtual topology identifier.
  • the extended redirection extends community attribute information, and the community attribute information is used to carry specific action attributes.
  • the types of slice identifiers in the community attribute information are as follows.
  • SUB-TYPE in SUB-TLV may include as follows.
  • RSVP-TE tunnel ID or triplet tunnel ID or triplet (tunnel ID, head node router identifier (RouterID), tail node router ID).
  • the SUB-TYPE in the SUB-TLV can be SR-Policy or SR- TE tunnel or SR-TP tunnel or RSVP-TE tunnel; Value can correspond to the keyword identifier of a specific SR-Policy/SR-TE tunnel/SR-TP tunnel/RSVP-TE tunnel.
  • the format of the SUB-TLV in the extended community attribute information of the application identifier is consistent with the format of the SUB-TLV in the extended community attribute information of the slice identifier.
  • step S300 includes but is not limited to step S710, step S720 and step S730.
  • a forwarding entry is determined from local mapping information according to the target block resource, and the local mapping information includes resource information corresponding to the target block resource and forwarding entries corresponding to the resource information.
  • Step S720 perform forwarding processing on the traffic message according to the forwarding entry.
  • the border gateway client can determine the forwarding entry from the local mapping information according to the target block resource, and then forward the traffic packet according to the forwarding entry, where the local mapping information includes the resource information corresponding to the target block resource and the resource information corresponding to Forwarding entries, network resources can be flexibly segmented by using block resource identifiers. Therefore, the target block resources determined by block resource identifiers can forward traffic packets, which can meet customers' needs for traffic path adjustment and optimization.
  • the border gateway client when the traffic packet includes community attribute information, can determine the forwarding entry from the local mapping information according to the target block resource and the community attribute information, and then forward the traffic packet according to the forwarding entry,
  • the local mapping information includes the resource information corresponding to the target block resource and the forwarding entry corresponding to the resource information.
  • the network resource can be flexibly segmented by using the block resource identifier. Forwarding files can meet customers' needs for traffic path adjustment and optimization.
  • FIG. 8 is a flowchart of a flow message forwarding method provided by an embodiment of the present application.
  • the flow message forwarding method is applied to a border gateway controller, and the flow message forwarding method includes but is not limited to Step S810.
  • Step S810 sending filtering rule information carrying block resource identifiers to the border gateway client, so that the border gateway client determines the target block resource of the traffic message according to the filter rule information, and processes the traffic message according to the target block resource For forwarding processing, traffic packets are received by the border gateway client.
  • the border gateway controller can send the filtering rule information carrying the block resource identifier to the border gateway client, so that the border gateway client installs the filtering rule into the local mapping information.
  • the target block resources of the traffic packets can be determined according to the filtering rule information and the block resource identifiers, and then the traffic packets can be forwarded according to the target block resources.
  • the block resource identifiers can Network resources are segmented flexibly. Therefore, traffic packets are forwarded through target block resources identified by block resource identifiers, which can meet customers' needs for traffic path adjustment and optimization.
  • block resource identifier may be a slice identifier or an application identifier, which is not specifically limited in this example.
  • the filtering rule information includes matching condition information and execution action information, wherein the matching condition information is carried in the Network Layer Reachability Information (NLRI for short) of the filtering rule, and the execution action information is the traffic matching information. Execution action, the execution action information is carried by the extended community attribute in the filter rule.
  • NLRI Network Layer Reachability Information
  • block resource identifier is carried by matching condition information or execution action information, which is not specifically limited in this embodiment.
  • FIG. 9 is a schematic diagram of a flow message forwarding network provided by an embodiment of the present application, the network includes a BGP Flowspc controller (equivalent to a border gateway controller) and node A (equivalent to a border network management client) , wherein node A can transmit traffic packets to node B through the IP/MPLS network.
  • FIG. 9 is a flow chart of a traffic packet forwarding method provided by an embodiment of the present application, which is applied to the system in FIG. 9 , and the traffic packet forwarding method includes but is not limited to steps S1010, S1020, and S1030.
  • Step S1010 the BGP Flowspc controller sends the Flowspc routing information carrying the flow filtering rules identified by the block resource.
  • block resource identifier is consistent with that in the foregoing embodiments, and details are not described here.
  • Step S1020 the BGP Flowspc client receives the Flowspc routing information carrying the flow filtering rules of the community attribute, and saves the content of the flow filtering rules.
  • the flow filtering rule includes two parts: matching condition information and execution action information.
  • the execution action information is carried in the extended community attribute information.
  • Step S1030 the BGP Flowspc client searches for forwarding entries of the local device according to the flow filtering rules.
  • the BGP Flowspc client looks up the forwarding entries in the local mapping table through the list of slice identifiers/application identifiers/or both, or directly forwards through specific paths in the extended community attribute information.
  • the forwarding entries of the local mapping information of the BGP Flowspc client can be established through models such as BGP, IGP, LDP, SR, RSVP, and YANG models.
  • FIG. 11 a schematic diagram of a flow message forwarding network redirected to slices provided by an embodiment of the present application
  • nodes and controllers in the network all have the BGP Flowspc function, and the network is set
  • the network is set
  • Each slice has a corresponding forwarding path, and the head node S (equivalent to a border network management client) can transmit traffic packets to node D through slice 1 and/or slice 2.
  • FIG. 12 is a flowchart of a traffic packet forwarding method provided by an embodiment of the present application, which is applied to the network in FIG. 11 , and the traffic packet forwarding method includes but is not limited to steps S1210, S1220, and S1230.
  • step S1210 the controller sends BGP Flowspc routing information carrying slice identifier filtering rules to the head node.
  • the delivered BGP Flowspc route carrying algorithm identification filtering rules is:
  • NLRI Carries matching conditions, which can be defined in RFC5575, such as the destination IP address of the traffic (the IP address of the D node), or can be based on the slice identifier as the matching condition.
  • the matching condition information carries the slice 1 identifier as an example.
  • the community attribute information redirected to the slice carries the execution action after the traffic is matched.
  • it carries the identifier of the slice 1, which is used to indicate the corresponding path for sending the traffic packet to the slice 1 after the traffic is matched.
  • Step S1220 the head node receives the BGP Flowspc routing information carrying the slice identifier filtering rules, and installs the filtering rules into local mapping information.
  • Step S1230 when the head node receives the data message carrying the slice 1 identifier, the head node searches the filtering rules in the local mapping information to obtain a forwarding entry, and forwards the traffic message to the forwarding entry corresponding to slice 1.
  • the head node queries the local mapping information of the slice according to the filtering rules, finds the forwarding entry corresponding to the corresponding slice 1, that is, finds the corresponding SR path corresponding to the slice 1 plane.
  • FIG. 13 another embodiment of the present application provides a schematic diagram of a flow message forwarding network redirected to slices.
  • Nodes and controllers in the network all have the BGP Flowspc function.
  • the slice filtering rules include: matching condition information and execution action information after traffic matching.
  • the matching condition information uses the slice identifier as the matching condition, that is, defines the slice BGP Flowspc Component type in the new NLRI, and the execution action information uses the existing execution action, which can redirect the tunnel, or redirect to the tunnel ID, Binding SID , in Figure 13, Bingding SID1 identifies the S-A-D path, and Binding SID identifies the S-C-D path.
  • FIG. 14 is a flowchart of a traffic packet forwarding method provided by an embodiment of the present application, which is applied to the network in FIG. 13 , and the traffic packet forwarding method includes but is not limited to steps S1410, S1420, and S1430.
  • Step 1410 the controller sends the BGP Flowspc routing information carrying slice identification filtering rules to the head node.
  • the filter rule in this embodiment includes using the slice identifier as the matching condition information, which can be defined as the slice BGP Flowspc Component type in the new NLRI; the matched execution action information can use the existing execution action information, that is, the execution action information It can indicate that the path is determined by redirecting the tunnel, and it can be indicated that the path is determined by redirecting to the Tunnel ID and Binding SID.
  • the matching condition information can be defined as the slice BGP Flowspc Component type in the new NLRI
  • the matched execution action information can use the existing execution action information, that is, the execution action information It can indicate that the path is determined by redirecting the tunnel, and it can be indicated that the path is determined by redirecting to the Tunnel ID and Binding SID.
  • Step 1420 the head node receives the BGP Flowspc routing information carrying the slice identifier filtering rule, and installs the filtering rule into the local mapping information.
  • Step 1430 when the head node receives the data packet carrying the identifier of slice 1, the head node looks up the filtering rules in the local mapping information to obtain the forwarding entry, and forwards the traffic packet according to the forwarding entry corresponding to slice 1.
  • the head node queries the local mapping information of the slice according to the filtering rules, and determines the forwarding entry corresponding to the slice 1, that is, the corresponding SR path corresponding to the plane of the slice 1 can be found.
  • FIG. 15 another embodiment of the present application provides a schematic diagram of a flow packet forwarding network redirected to slices.
  • nodes and controllers in the network all have the BGP Flowspc function.
  • there are two Flex-Algo planes in the network where the Algorithm value corresponding to the Flex-Algo 128 plane is 128, and the Algorithm value corresponding to the Flex-Algo 129 plane is 129.
  • the Flex-Algo 128 plane includes nodes S, A, B, D and bidirectional links between these nodes.
  • the Flex-Algo 129 plane includes nodes S, B, C, D and the bidirectional links between these nodes, and each Flex-Algo plane has a corresponding SR path.
  • FIG. 16 is a flowchart of a traffic packet forwarding method provided by an embodiment of the present application, which is applied to the network in FIG. 15 , and the traffic packet forwarding method includes but is not limited to steps S1610, S1620, and S1630.
  • step S1610 the controller sends BGP Flowspc routing information carrying algorithm identification filtering rules to the head node.
  • the BGP Flowspc routing information carrying algorithm identifiers (implicit slice identifiers) filtering rules issued by the controller is as follows.
  • the NLRI carries matching condition information.
  • it may be the destination IP address of the traffic (the IP address of the D node) or an identifier based on a flexible algorithm as the matching condition information.
  • the community attribute information redirected to the flexible algorithm carries the execution action information after traffic matching.
  • Flex-algo128 is carried to indicate that after the traffic is matched, the traffic packet is sent to the SR path corresponding to the Flex-algo128 plane. superior.
  • Step S1620 the head node receives the BGP Flowspc routing information carrying the algorithm identification filter rule, and installs the filter rule into the local mapping information.
  • Step S1630 when the head node receives the flow message carrying the IP address of the D node, the head node searches the filtering rules in the local mapping information to obtain the forwarding entry, and forwards the flow message according to the forwarding entry corresponding to the Flex-algo128 plane Forward.
  • the head node queries the local mapping information of the Flex-algo according to the filtering rules, and determines the forwarding entry corresponding to the corresponding Flex-algo128, that is, the SR path corresponding to the corresponding Flex-algo128 plane can be found.
  • Fig. 17 is a flow chart of a flow packet forwarding method redirected to an application provided by an embodiment of the present application.
  • the network is set There are two applications, namely application 1 and application 2, and the above-mentioned applications may be App-related applications.
  • the flow packet forwarding method includes but is not limited to step S1710, step S1720 and step S1730.
  • Step 1710 the controller sends the BGP Flowspc route carrying the application identification filtering rule to the head node.
  • the BGP Flowspc routing information delivered by the controller carrying application identification filtering rule information is as follows.
  • the matching condition information carried by the NLRI may be the matching condition information defined in RFC5575, such as the destination IP address of the traffic packet (the IP address of the D node), or it may be based on the application identifier as the matching condition information.
  • the matching condition carries the application 1 identifier as an example.
  • the community attribute information redirected to application 1 carries the execution action after the traffic is matched.
  • the application 1 identifier is used to indicate that after the traffic is matched, the report The text traffic is forwarded through the forwarding entry corresponding to application 1.
  • Step 1720 the head node receives the BGP Flowspc routing information carrying the application identification filtering rule, and installs the filtering rule into the local mapping information.
  • Step 1730 when the head node receives the traffic packet carrying application 1, the head node searches the filtering rules in the local mapping information to obtain forwarding entries, and forwards the traffic packets according to the forwarding entries corresponding to application 1.
  • the head node queries the local mapping information of application 1 according to the filtering rules, and determines the forwarding entry corresponding to application 1, that is, the SR path corresponding to the corresponding application 1 plane can be found.
  • an embodiment of the present application provides a border gateway client, which includes: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor and memory can be connected by a bus or other means.
  • the terminal in this embodiment may correspond to include the memory and the processor in the embodiment shown in Figure 1, which can constitute a part of the system architecture platform in the embodiment shown in Figure 1, and both belong to the same Therefore, both have the same realization principle and beneficial effect, and will not be described in detail here.
  • the non-transitory software programs and instructions required to realize the traffic packet forwarding method on the terminal side of the above-mentioned embodiments are stored in the memory, and when executed by the processor, the traffic packet forwarding method of the above-mentioned embodiment is executed, for example, the above Described method steps S100 to S300 in Fig. 2, method steps S710 to S720 in Fig. 7, method steps S1020 and step S1030 in Fig. 10, method steps S1220 and step S1230 in Fig. 12, method steps in Fig. 14 S1420 and step S1430, method step S1620 and step S1630 in FIG. 16 , method step S1720 and step S1730 in FIG. 17 .
  • an embodiment of the present application provides a border gateway controller, which includes: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor and memory can be connected by a bus or other means.
  • border gateway controller in this embodiment may correspond to include the memory and the processor in the embodiment shown in FIG. 1, which can constitute a part of the system architecture platform in the embodiment shown in FIG. 1. Both belong to the same inventive concept, so both have the same realization principle and beneficial effect, and will not be described in detail here.
  • the non-transitory software programs and instructions required to realize the traffic packet forwarding method on the border gateway controller side of the above-mentioned embodiment are stored in the memory, and when executed by the processor, the traffic packet forwarding method of the above-mentioned embodiment is executed, for example , execute method step S810 in Fig. 8 described above, method step S1010 in Fig. 10 , method step S1210 in Fig. 12 , method step S1410 in Fig. 14 , method step S1610 in Fig. 16 , method in Fig. 17 Step S1710.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are used to execute the traffic packet on the client side of the border gateway
  • the forwarding method for example, executes method steps S100 to S300 in FIG. 2 described above, method steps S710 to S720 in FIG. 7 , method steps S1020 and step S1030 in FIG. 10 , method steps S1220 and step S1230 in FIG. 12 , method step S1420 and step S1430 in FIG. 14 , method step S1620 and step S1630 in FIG. 16 , method step S1720 and step S1730 in FIG. 17 .
  • the computer-executable instructions when used to execute the traffic packet forwarding method on the side of the border gateway controller, for example, execute the method step S810 in FIG. 8 described above, the method step S1010 in FIG. 10 , and FIG. Method step S1210 in FIG. 12 , method step S1410 in FIG. 14 , method step S1610 in FIG. 16 , method step S1710 in FIG. 17 .
  • the embodiment of the present application includes: receiving a flow message; in the case that the flow message includes a block resource identifier, determining the target block resource according to the block resource identifier and filtering rule information, and the filtering rule information is determined by the boundary
  • the gateway controller sends and obtains; and uses the target block resource to forward and process the traffic message.
  • the border gateway client when the border gateway client receives the traffic message carrying the block resource identifier, it can determine the target block according to the block resource identifier and the filtering rule information sent by the border gateway controller resources, and then use the target block resource to forward the traffic message; the block resource identifier can be used to flexibly segment network resources, so the target block resource determined by the block resource identifier can forward the traffic message, which can Meet customers' needs for traffic path adjustment and optimization.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种流量报文转发方法、客户端、控制器及存储介质，该流量报文转发方法包括如下步骤：接收流量报文(S100)；在流量报文包括分块资源标识的情况下，根据分块资源标识和过滤规则信息确定目标分块资源，过滤规则信息由边界网关控制器发送得到(S200)；采用目标分块资源对流量报文进行转发处理(S300)。

Description

流量报文转发方法、客户端、控制器及存储介质
相关申请的交叉引用
本申请基于申请号为202110564009.5，申请日为2021年05月24日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信领域，尤其涉及一种流量报文转发方法、客户端、控制器及存储介质。
背景技术
传统的路由最初设计是为流量转发的，路由表项中只包含用于目的地址匹配的前缀掩码信息及流量出接口信息，随着网络业务发展需求，网络的复杂性增加，对于路由的要求越来越高，通常会在路由表项中增加支持流量策略的信息，即将转发路由表项中数据流进行细分，但是支持流量策略的信息的路由属于本地行为，需要对每一台设备进行配置，手工配置工作量大，对运维人员要求高，特别在5G网络应用中，具有灵活调度、海量连接的要求，现有的路由技术无法满足客户对流量路径调整调优需求。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提出一种流量报文转发方法、客户端、控制器及存储介质。
第一方面，本申请实施例提供了一种流量报文转发方法，包括：接收流量报文；在所述流量报文包括分块资源标识的情况下，根据所述分块资源标识和过滤规则信息确定目标分块资源，所述过滤规则信息由边界网关控制器发送得到；采用所述目标分块资源对所述流量报文进行转发处理。
第二方面，本申请实施例还提供了边界网关客户端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现第一方面所述的流量报文转发方法。
第三方面，本申请实施例还提供了一种流量报文转发方法，包括：向边界网关客户端发送携带分块资源标识的过滤规则信息，以使所述边界网关客户端根据所述过滤规则信息确定流量报文的目标分块资源，并根据所述目标分块资源将所述流量报文进行转发处理，所述流量报文为所述边界网关客户端接收所得。
第四方面，本申请实施例还提供了一种边界网关控制器，包括：存储器、处 理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现第三方面所述的流量报文转发方法。
第五方面，一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行第一方面所述的流量报文转发方法，或者用于执行第三方面所述的流量报文转发方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
图1是本申请一个实施例提供的用于执行流量报文转发方法的系统架构的示意图；
图2是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法的流程图；
图3是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法中切片BGP Flowspc Component类型的封装格式的示意图；
图4是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法中切片标识的团体属性格式的示意图；
图5是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法中团体属性格式的SUB-TLV格式示意图；
图6是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法中切片标识的团体属性格式的示意图；
图7是本申请一个实施例提供的边界网关客户端侧的流量报文转发方法的转发处理的流程图；
图8是本申请一个实施例提供的边界网关控制器侧的流量报文转发方法的流程图；
图9是本申请一个实施例提供的流量报文转发网络的示意图；
图10是本申请一个实施例提供的流量报文转发方法的流程图；
图11是本申请一个实施例提供的重定向到切片的流量报文转发网络的示意图；
图12是本申请一个实施例提供的重定向到切片的流量报文转发方法的流程图；
图13是本申请另一个实施例提供的重定向到切片的流量报文转发网络的示意图；
图14是本申请另一个实施例提供的重定向到切片的流量报文转发方法的流程图；
图15是本申请另一个实施例提供的重定向到切片的流量报文转发网络的示 意图；
图16是本申请另一个实施例提供的重定向到切片的流量报文转发方法的流程图；
图17是本申请另一个实施例提供的重定向到应用的流量报文转发方法的流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例提供了一种流量报文转发方法、客户端、控制器及存储介质，该流量报文转发方法包括但不限于如下步骤：接收流量报文；在流量报文包括分块资源标识的情况下，根据分块资源标识和过滤规则信息确定目标分块资源，过滤规则信息由边界网关控制器发送得到；采用目标分块资源对流量报文进行转发处理。根据本申请实施例的技术方案，边界网关客户端在接收到携带分块资源标识的流量报文的情况下，可以根据分块资源标识和由边界网关控制器发送得到过滤规则信息确定目标分块资源，然后采用目标分块资源对流量报文进行转发处理；采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
下面结合附图，对本申请实施例作进一步阐述。
如图1所示，图1是本申请一个实施例提供的用于执行流量报文转发方法的系统架构平台100的示意图。
在图1的示例中，该系统架构平台100设置有处理器110和存储器120，其中，处理器110和存储器120可以通过总线或者其他方式连接，图1中以通过总线连接为例。
存储器120作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器120可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器120可包括相对于处理器110远程设置的存储器，这些远程存储器可以通过网络连接至该系统架构平台。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本领域技术人员可以理解的是，该系统架构平台可以应用于通信网络系统以及后续演进的移动通信网络系统等，本实施例对此并不作具体限定。
本领域技术人员可以理解的是，图1中示出的系统架构平台并不构成对本申请实施例的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
在图1所示的系统架构平台中，处理器110可以调用储存在存储器120中的业务流管理程序，从而执行流量报文转发方法。
基于上述系统架构平台，下面提出本申请的流量报文转发方法的各个实施例。
如图2所示，图2是本申请一个实施例提供的流量报文转发方法的流程图，该流量报文转发方法应用于边界网关客户端，并且该流量报文转发方法包括但不限于有步骤S100、步骤S200、步骤S300。
步骤S100，接收流量报文。
步骤S200，在流量报文包括分块资源标识的情况下，根据分块资源标识和过滤规则信息确定目标分块资源，过滤规则信息由边界网关控制器发送得到。
步骤S300，采用目标分块资源对流量报文进行转发处理。
具体地，边界网关客户端在接收到携带分块资源标识的流量报文的情况下，可以根据分块资源标识和由边界网关控制器发送得到过滤规则信息确定目标分块资源，然后采用目标分块资源对流量报文进行转发处理；采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
在一实施例中，该边界网关客户端能够应用在5G网络的边界网管流协议(Border Gateway Protocol Flow Specification，简称BGP Flowspc)，为提高对流量路径调整调优能力，可以对边界网管流协议进行优化，对边界网管流协议中的过滤规则信息进行扩展，在过滤规则中增加分块资源标识，即边界网关控制器向边界网关客户端发送携带有分块资源标识的过滤规则信息，边界网关客户端接收到携带分块资源标识的过滤规则信息后，将该过滤规则信息则安装至本地映射信息中，当边界网关客户端接收到携带分块资源标识的流量报文后，边界网关客户端可以根据流量报文的分块资源标识和安装有过滤规则信息的本地映射信息确定目标分块资源，然后采用目标分块资源对流量报文进行转发处理；采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
需要说明的是，分块资源标识可以是切片标识，也可以是应用标识，本实例对其不作具体限定。
需要说明的是，过滤规则信息包括匹配条件信息和执行动作信息，其中匹配条件信息由过滤规则的网络层可达信息(Network Layer Reachability Information，简称NLRI)中携带，执行动作信息为流量匹配后的执行动作，该执行动作信息由过滤规则中在扩展的团体属性携带。
需要说明的是，分块资源标识由匹配条件信息携带或者由执行动作信息携带，本实施例对其不作具体限定。
需要说明的是，匹配条件信息可以使用现有定义的流规范组件类型信息，流规范组件类型信息可以理解为即基于数据包的源地址/目的地址/差分服务代码点(Differentiated Services Code Point，简称DSCP)对流量进行匹配，也可以是通过对边界网管流协议组件类型进行拓展的信息，使其携带切片标识/应用标识，切片标识/应用标识用于使其支持切片/应用的过滤。
需要说明的是，扩展的边界网管流协议组件类型中所携带的切片标识/应用标识可以有多组，即可以设置有切片标识列表或者应用标识列表，在匹配时可以针对多个切片来源或者多个应用来源进行匹配，而不需要下发多个流量规则(匹配条件信息)，能够节省内存开销。
需要说明的是，对于重定向扩展的团体属性信息，可以重定向到通用切片标识或者应用标识或者两者之内的某个路径，例如：段路由策略(Segment Routing Policy，简称SR-Policy)/流量工程分段路由(Segmental Routing-Traffic Engineering，简称SR-TE)隧道/基于流量工程的段路由传送子集(Segment Routing Transport Profile-Traffic Engineering，简称SR-TP)隧道。
需要说明的是，新的重定向扩展的团体属性信息主要携带切片标识/应用标识，以及某个路径的具体标识，SR-TE隧道和SR-TP隧道的标识为隧道标识(Tunnel-Identity Document，简称Tunnel-ID)，SR-policy的标识为三元组，三元组包括目的地址、颜色属性、前缀唯一身份编号(Security Identifiers，简称SID)。
具体地，BGP Flowspc客户端可以接收携带扩展的团体属性信息的Flowspc路由信息，然后保存Flowspc路由信息中的流过滤规则的内容。BGP Flowspc客户端通过切片标识/应用标识查找本地映射信息中的转发条目(针对没有具体到某个路径的场景)，可以通过现有的重定向到下一跳动作来实现；BGP Flowspc客户端也可以通过切片标识/应用标识内的某个路径，直接找到相应的转发条目进行转发。
需要说明的是，BGP Flowspc客户端的本地映射信息中的转发条目的建立可以通过自治系统间的路由协议、内部网关协议(Interior Gateway Protocols，简称IGP)、标签分发协议(Label Distribution Protocol，简称LDP)、分段式路由协议(Segmental Routing，简称SR)、资源预留协议(Resource ReSerVation Protocol，简称RSVP)等模型进行建立。
在一实施例中，可以扩展到BGP Flowspc Component类型的封装格式：
1)切片BGP Flowspc Component类型。
封装:<类型(1 octet),[运营商,值]+>，如图3所示。
其中值字段：切片标识。
需要说明书的是，切片标识可以是切片标识，可以是多拓扑标识，可以是灵 活算法(Flexible-Algorithm，简称Flex-Algo)标识或者虚拟拓扑标识。
2)应用BGP Flowspc Component类型。
封装:<类型(1 octet),[运营商,值]+>，如图3所示。
其中值字段：应用标识。
在一实施例中，扩展的重定向扩展的团体属性信息，团体属性信息用于携带具体的动作属性。
1)重定向到通用切片标识的扩展的团体属性信息格式如图4所示。
团体属性信息中的切片标识的类型如下。
1---切片标识。
2---多拓扑标识。
3---灵活算法标识。
4---虚拟拓扑标识。
团体属性信息中的SUB-TLV格式如图5所示。
SUB-TLV中的SUB-TYPE可以包括如下。
1---RSVP-TE隧道
2---SR-TP/SR-TE隧道
3---SR-Policy。
SUB-TLV中的Value分别如下。
1---RSVP-TE隧道ID或者三元组(隧道ID、头节点路由器标识(RouterID)、尾节点路由器ID)。
2---SR-TP/SR-TE隧道ID或者三元组(隧道ID、头节点路由器标识(RouterID)、尾节点路由器ID)。
3---SR-POLICY ID或者三元组(SR-Policy的颜色Color、SR-Policy的目的地址Endpoint、SR-Policy的前缀分段标识Prefix-SID)。
如图4-5所示，可以重定向到某个切片下的某些路径下，具体的路径由SUB-TLV字段来携带，其中SUB-TLV中的SUB-TYPE可以是SR-Policy或者SR-TE隧道或者SR-TP隧道或者RSVP-TE隧道；Value可以对应具体的SR-Policy/SR-TE隧道/SR-TP隧道/RSVP-TE隧道的关键字标识。
2)重定向到通用应用标识的扩展的团体属性信息格式如图6所示。
需要说明的是，应用标识的扩展的团体属性信息中的SUB-TLV格式和切片标识的扩展的团体属性信息中的SUB-TLV格式一致。
参照图7，步骤S300包括但不限定于S710、步骤S720和步骤S730。
步骤S710，根据目标分块资源从本地映射信息确定转发条目，本地映射信息包括目标分块资源对应的资源信息和资源信息对应的转发条目。
步骤S720，根据转发条目对流量报文进行转发处理。
具体地，边界网关客户端可以根据目标分块资源从本地映射信息确定转发条目，然后根据转发条目对流量报文进行转发处理，其中本地映射信息包括目标分 块资源对应的资源信息和资源信息对应的转发条目，采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
在一实施例中，当流量报文包括团体属性信息时，边界网关客户端可以根据目标分块资源和团体属性信息从本地映射信息确定转发条目，然后根据转发条目对流量报文进行转发处理，其中本地映射信息包括目标分块资源对应的资源信息和资源信息对应的转发条目，采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
如图8所示，图8是本申请一个实施例提供的流量报文转发方法的流程图，该流量报文转发方法应用于边界网关控制器，并且该流量报文转发方法包括但不限于有步骤S810。
步骤S810，向边界网关客户端发送携带分块资源标识的过滤规则信息，以使边界网关客户端根据过滤规则信息确定流量报文的目标分块资源，并根据目标分块资源将流量报文进行转发处理，流量报文为边界网关客户端接收所得。
具体地，边界网关控制器可以向边界网关客户端发送携带分块资源标识的过滤规则信息，以使边界网关客户端将过滤规则安装至本地映射信息中，当边界网关客户端接收到携带分块资源标识的流量报文时，可以根据过滤规则信息和分块资源标识能够确定流量报文的目标分块资源，然后根据目标分块资源将流量报文进行转发处理，采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
需要说明的是，分块资源标识可以是切片标识，也可以是应用标识，本实例对其不作具体限定。
需要说明的是，过滤规则信息包括匹配条件信息和执行动作信息，其中匹配条件信息由过滤规则的网络层可达信息(Network Layer Reachability Information，简称NLRI)中携带，执行动作信息为流量匹配后的执行动作，该执行动作信息由过滤规则中在扩展的团体属性携带。
需要说明的是，分块资源标识由匹配条件信息携带或者由执行动作信息携带，本实施例对其不作具体限定。
如图9所示，图9是本申请一个实施例提供的流量报文转发网络的示意图，该网络包括BGP Flowspc控制器(相当于边界网关控制器)和节点A(相当于边界网管客户端)，其中节点A可以通过IP/MPLS网络将流量报文传输至节点B。图9是本申请一个实施例提供的流量报文转发方法的流程图，应用于图9的系统，并且该流量报文转发方法包括但不限于有步骤S1010、步骤S1020和步骤S1030。
步骤S1010，BGP Flowspc控制器发送携带分块资源标识的流过滤规则的Flowspc路由信息。
需要说明的是，分块资源标识与上述实施例中一致，此处不作具体赘述。
步骤S1020，BGP Flowspc客户端接收携带团体属性的流过滤规则的Flowspc路由信息，保存流过滤规则的内容。
其中，流过滤规则包括两部分内容：匹配条件信息及执行动作信息。
执行动作信息由扩展的团体属性信息中携带。
步骤S1030，BGP Flowspc客户端根据流过滤规则查找本地设备的转发条目。
需要说明的是，BGP Flowspc客户端通过切片标识/应用标识/或者两者的列表查找本地映射表中的转发条目，或者直接通过扩展团体属性信息中的具体路径进行转发。
需要说明的是，BGP Flowspc客户端的本地映射信息的转发条目可以通过BGP、IGP、LDP、SR、RSVP、YANG模型等模型进行建立。
如图11所示，本申请一个实施例提供的重定向到切片的流量报文转发网络示意图，网络中的节点及控制器(相当于边界网关控制器)都具有BGP Flowspc功能，该网络中设置有两个切片，分别为切片1及切片2，其中切片1包括节点S、A、B、D以及这些节点间相连的双向链路，切片2中包括节点S、B、C、D以及这些节点间相连的双向链路。每个切片都有相应的转发路径，头节点S(相当于边界网管客户端)可以通过切片1和/或切片2将流量报文传输至节点D。
图12是本申请一个实施例提供的流量报文转发方法的流程图，应用于图11的网络，并且该流量报文转发方法包括但不限于有步骤S1210、步骤S1220和步骤S1230。
步骤S1210，控制器向头节点下发携带切片标识过滤规则的BGP Flowspc路由信息。
具体地，下发的携带算法标识过滤规则的BGP Flowspc路由为：
NLRI：携带匹配条件，可以RFC5575定义的匹配条件例如流量的目的IP地址(D节点的IP地址)，也可以基于切片标识作为匹配条件。
本实施例中匹配条件信息携带切片1标识为例。
重定向到切片的团体属性信息携带流量匹配后的执行动作，本实施例中携带切片1的标识，用于指示流量匹配后，将流量报文发送到切片1的对应的路径。
步骤S1220，头节点接收携带切片标识过滤规则的BGP Flowspc路由信息，并安装过滤规则到本地映射信息。
步骤S1230，当头节点接收到携带切片1标识的数据报文时，头节点查找本地映射信息中的过滤规则得到转发条目，将流量报文转发到与切片1对应的的转发条目。
具体地，头节点根据过滤规则，查询切片的本地映射信息，找到相应的切片1对应的转发条目，即可以找到相应的切片1平面对应的SR路径。
如图13所示，本申请另一个实施例提供的重定向到切片的流量报文转发网络示意图，网络中的节点及控制器(相当于边界网关控制器)都具有BGP Flowspc 功能，该网络中设置有两个切片，分别为切片1及切片2，其中切片1包括节点S、A、B、D以及这些节点间相连的双向链路，切片2中包括节点S、B、C、D以及这些节点间相连的双向链路。其中切片过滤规则包括：匹配条件信息及流量匹配后的执行动作信息。匹配条件信息使用基于切片标识作为匹配条件，即定义新的NLRI中的切片BGP Flowspc Component类型，执行动作信息使用现有的执行动作，可以重定向隧道，也可以通过重定向到tunnel ID、Binding SID,图13中Bingding SID1标识S-A-D路径，Binding SID标识S-C-D的路径。
图14是本申请一个实施例提供的流量报文转发方法的流程图，应用于图13的网络，并且该流量报文转发方法包括但不限于有步骤S1410、步骤S1420和步骤S1430。
步骤1410，控制器向头节点下发携带切片标识过滤规则的BGP Flowspc路由信息。
本实施例的过滤规则包括使用基于切片标识作为匹配条件信息，即可以定义为新的NLRI中的切片BGP Flowspc Component类型；匹配后的执行动作信息可以使用现有的执行动作信息，即执行动作信息可以指示通过重定向隧道确定路径，可以指示通过重定向到Tunnel ID、Binding SID确定路径。
步骤1420，头节点接收携带切片标识过滤规则的BGP Flowspc路由信息，并安装此过滤规则至本地映射信息。
安装后的过滤规则如表1所示。
匹配条件信息 转发条目
切片1 Binding SID 1
切片2 Binding SID 2
表1
步骤1430，当头节点接收到携带切片1标识的数据报文时，头节点查找本地映射信息中的过滤规则得到转发条目，将流量报文根据与切片1对应的的转发条目进行转发。
具体地，头节点根据过滤规则，查询切片的本地映射信息，确定切片1对应的转发条目，即可以找到相应的切片1平面对应的SR路径。
如图15所示，本申请另一个实施例提供的重定向到切片的流量报文转发网络示意图，如图所示网络中的节点及控制器(相当于边界网关控制器)均具有BGP Flowspc功能，网络中设置有两个Flex-Algo平面，其中Flex-Algo 128平面对应的Algorithm取值为128，Flex-Algo 129平面对应的Algorithm取值为129。Flex-Algo 128平面中包含节点S、A、B、D以及这些节点间相连的双向链路。Flex-Algo 129平面中包含节点S、B、C、D以及这些节点间相连的双向链路，每个Flex-Algo平面都设置有相应的SR路径。
图16是本申请一个实施例提供的流量报文转发方法的流程图，应用于图15的网络，并且该流量报文转发方法包括但不限于有步骤S1610、步骤S1620和步 骤S1630。
步骤S1610，控制器向头节点下发携带算法标识过滤规则的BGP Flowspc路由信息。
具体地，控制器下发的携带算法标识(隐含切片标识)过滤规则的BGP Flowspc路由信息如下。
NLRI中携带匹配条件信息，本实施例中可以是流量的目的IP地址(D节点的IP地址)或者是基于灵活算法标识作为匹配条件信息。
重定向到灵活算法的团体属性信息中携带流量匹配后的执行动作信息，本实施例中携带Flex-algo128，用于指示流量匹配后，将流量报文发送到Flex-algo128平面所对应的SR路径上。
步骤S1620，头节点接收携带算法标识过滤规则的BGP Flowspc路由信息，并安装此过滤规则至本地映射信息。
步骤S1630，当头节点接收到携带目的地址为D节点的IP地址的流量报文时，头节点查找本地映射信息中的过滤规则得到转发条目，将流量报文根据Flex-algo128平面对应的转发条目进行转发。
具体地，头节点根据过滤规则，查询Flex-algo的本地映射信息，确定到相应的Flex-algo128对应的转发条目，即可以找到相应的Flex-algo128平面对应的SR路径。
图17是本申请一个实施例提供的重定向到应用的流量报文转发方法的流程图，当网络中的节点及控制器(相当于边界网关控制器)均具有BGP-FS功能，网络中设置有两个应用，分别是应用1及应用2，上述应用可以是App相关的应用，那么该流量报文转发方法包括但不限于有步骤S1710、步骤S1720和步骤S1730。
步骤1710，控制器向头节点下发携带应用标识过滤规则的BGP Flowspc路由。
具体地，控制器下发的携带应用标识过滤规则信息的BGP Flowspc路由信息如下。
NLRI携带匹配条件信息可以是RFC5575定义的匹配条件信息，例如流量报文的目的IP地址(D节点的IP地址)，也可以基于应用标识作为匹配条件信息。
本实施例中以匹配条件携带应用1标识为例，重定向到应用1的团体属性信息携带流量匹配后的执行动作，本实施例中携带应用1的标识，用于指示流量匹配后，将报文流量通过应用1对应的转发条目进行转发。
步骤1720，头节点接收携带应用标识过滤规则的BGP Flowspc路由信息，并安装此过滤规则至本地映射信息。
步骤1730，当头节点接收到携带应用1的流量报文时，头节点查找本地映射信息中的过滤规则得到转发条目，将流量报文根据应用1对应的转发条目进行转发。
具体地，头节点根据过滤规则，查询应用1的本地映射信息，确定应用1对应的转发条目，即可以找到相应的应用1平面对应的SR路径。
基于上述流量报文转发方法，下面分别提出本申请的边界网关客户端、边界网关控制器和计算机可读存储介质的各个实施例。
另外，本申请的一个实施例提供了一种边界网关客户端，该边界网关客户端包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
需要说明的是，本实施例中的终端，可以对应为包括有如图1所示实施例中的存储器和处理器，能够构成图1所示实施例中的系统架构平台的一部分，两者属于相同的发明构思，因此两者具有相同的实现原理以及有益效果，此处不再详述。
实现上述实施例的终端侧的流量报文转发方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述实施例的流量报文转发方法，例如，执行以上描述的图2中的方法步骤S100至S300、图7中的方法步骤S710至S720、图10中的方法步骤S1020和步骤S1030、图12中的方法步骤S1220和步骤S1230、图14中的方法步骤S1420和步骤S1430、图16中的方法步骤S1620和步骤S1630、图17中的方法步骤S1720和步骤S1730。
另外，本申请的一个实施例提供了一种边界网关控制器，该边界网关控制器包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
需要说明的是，本实施例中的边界网关控制器，可以对应为包括有如图1所示实施例中的存储器和处理器，能够构成图1所示实施例中的系统架构平台的一部分，两者属于相同的发明构思，因此两者具有相同的实现原理以及有益效果，此处不再详述。
实现上述实施例的边界网关控制器侧的流量报文转发方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述实施例的流量报文转发方法，例如，执行以上描述的图8中的方法步骤S810、图10中的方法步骤S1010、图12中的方法步骤S1210、图14中的方法步骤S1410、图16中的方法步骤S1610、图17中的方法步骤S1710。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，当计算机可执行指令用于执行上述边界网关客户端侧的流量报文转发方法，例如，执行以上描述的图2中的方法步骤S100至S300、图7中的方法步骤S710至S720、图10中的方法步骤S1020和步骤S1030、图12中的方法步骤S1220和步骤S1230、图14中的方法步骤S1420和步骤S1430、图16中的方法步骤S1620和步骤S1630、图17中的方法步骤S1720和步骤S1730。或者，当计算机可执行指令用于执行上述边界网关控制器侧的流量报文转发方法，例如，执行以上描述的执行以上描述的图8中的方法步骤S810、图10中的方法 步骤S1010、图12中的方法步骤S1210、图14中的方法步骤S1410、图16中的方法步骤S1610、图17中的方法步骤S1710。
本申请实施例包括：接收流量报文；在所述流量报文包括分块资源标识的情况下，根据所述分块资源标识和过滤规则信息确定目标分块资源，所述过滤规则信息由边界网关控制器发送得到；采用所述目标分块资源对所述流量报文进行转发处理。根据本申请实施例的技术方案，边界网关客户端在接收到携带分块资源标识的流量报文的情况下，可以根据分块资源标识和由边界网关控制器发送得到过滤规则信息确定目标分块资源，然后采用目标分块资源对流量报文进行转发处理；采用分块资源标识能够对网络资源进行灵活切分，因此通过分块资源标识确定的目标分块资源对流量报文进行转发，能够满足客户对流量路径调整调优需求。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包括计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的若干实施方式进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的共享条件下还可作出种种等同的变形或替换，这些等同的变形或替换均包括在本申请权利要求所限定的范围内。

Claims (11)

  1. 一种流量报文转发方法，包括：
    接收流量报文；
    在所述流量报文包括分块资源标识的情况下，根据所述分块资源标识和过滤规则信息确定目标分块资源，所述过滤规则信息由边界网关控制器发送得到；
    采用所述目标分块资源对所述流量报文进行转发处理。
  2. 根据权利要求1所述的流量报文转发方法，其中，所述采用所述目标分块资源对所述流量报文进行转发处理包括：
    根据所述目标分块资源从本地映射信息确定转发条目，所述本地映射信息包括所述目标分块资源对应的资源信息和所述资源信息对应的转发条目；
    根据所述转发条目对所述流量报文进行转发处理。
  3. 根据权利要求2所述的流量报文转发方法，其中，所述流量报文包括团体属性信息，所述根据所述目标分块资源从本地映射信息确定转发条目包括：
    根据所述目标分块资源和所述团体属性信息从本地映射信息确定转发条目。
  4. 根据权利要求1至3任意一项所述的流量报文转发方法，其中，所述过滤规则信息包括匹配条件信息和执行动作信息，所述分块资源标识由所述匹配条件信息携带或者由所述执行动作信息携带。
  5. 根据权利要求1至3任意一项所述的流量报文转发方法，其中，所述分块资源标识为切片标识或者应用标识。
  6. 一种边界网关客户端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至5中任意一项所述的流量报文转发方法。
  7. 一种流量报文转发方法，包括：向边界网关客户端发送携带分块资源标识的过滤规则信息，以使所述边界网关客户端根据所述过滤规则信息确定流量报文的目标分块资源，并根据所述目标分块资源将所述流量报文进行转发处理，所述流量报文为所述边界网关客户端接收所得。
  8. 根据权利要求7所述的流量报文转发方法，其中，所述过滤规则信息包括匹配条件信息和执行动作信息，所述分块资源标识由所述匹配条件信息携带或者由所述执行动作信息携带。
  9. 根据权利要求7所述的流量报文转发方法，其中，所述分块资源标识为切片标识或者应用标识。
  10. 一种边界网关控制器，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求7至9任意一项所述的流量报文转发方法。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行权利要求1至5中任意一项所述的流量报文转发方法，或者用于执行权利要求7至9任意一项所述的流量报文转发方法。
PCT/CN2022/093301 2021-05-24 2022-05-17 流量报文转发方法、客户端、控制器及存储介质 WO2022247689A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22810416.2A EP4311311A1 (en) 2021-05-24 2022-05-17 Traffic message forwarding method, and client, controller and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110564009.5A CN115473812A (zh) 2021-05-24 2021-05-24 流量报文转发方法、客户端、控制器及存储介质
CN202110564009.5 2021-05-24

Publications (1)

Publication Number Publication Date
WO2022247689A1 true WO2022247689A1 (zh) 2022-12-01

Family

ID=84228423

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/093301 WO2022247689A1 (zh) 2021-05-24 2022-05-17 流量报文转发方法、客户端、控制器及存储介质

Country Status (3)

Country Link
EP (1) EP4311311A1 (zh)
CN (1) CN115473812A (zh)
WO (1) WO2022247689A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11870690B2 (en) * 2020-03-17 2024-01-09 Huawei Technologies Co., Ltd. Packet processing method and apparatus, device, and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110149734A1 (en) * 2009-12-21 2011-06-23 Electronics And Telecommunications Research Institute Smart border router and method for transmitting flow using the same
CN107222449A (zh) * 2016-03-21 2017-09-29 华为技术有限公司 基于流规则协议的通信方法、设备和系统
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
CN108347376A (zh) * 2017-01-24 2018-07-31 华为技术有限公司 一种调整转发路径的方法、装置及系统
CN109218201A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种生成转发表项的方法、控制器和网络设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110149734A1 (en) * 2009-12-21 2011-06-23 Electronics And Telecommunications Research Institute Smart border router and method for transmitting flow using the same
CN107222449A (zh) * 2016-03-21 2017-09-29 华为技术有限公司 基于流规则协议的通信方法、设备和系统
CN111865898A (zh) * 2016-03-21 2020-10-30 华为技术有限公司 基于流规则协议的通信方法、设备和系统
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
CN112165725A (zh) * 2016-06-15 2021-01-01 华为技术有限公司 报文处理的方法及设备
CN108347376A (zh) * 2017-01-24 2018-07-31 华为技术有限公司 一种调整转发路径的方法、装置及系统
CN109218201A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种生成转发表项的方法、控制器和网络设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11870690B2 (en) * 2020-03-17 2024-01-09 Huawei Technologies Co., Ltd. Packet processing method and apparatus, device, and storage medium

Also Published As

Publication number Publication date
EP4311311A1 (en) 2024-01-24
CN115473812A (zh) 2022-12-13

Similar Documents

Publication Publication Date Title
EP3817446B1 (en) Method and apparatus for creating network slices
CN111385206B (zh) 报文转发的方法、网络系统、相关设备及计算机存储介质
US11689452B2 (en) Method for forwarding service data, network device, and network system
US9391885B1 (en) MPLS label usage in Ethernet virtual private networks
US9178816B1 (en) Control plane messaging in all-active multi-homed ethernet virtual private networks
CN113259238B (zh) 分段标识的处理方法及设备
US11743166B2 (en) Provisioning non-colored segment routing label switched paths via segment routing policies in border gateway protocol
US9007941B1 (en) Self-organizing and scalable MPLS VPN transport for LTE
WO2017107814A1 (zh) 一种传播QoS策略的方法、装置及系统
EP2541847B1 (en) Method and system for establishing an associated bidirectional label-switched path
CN112511418A (zh) 报文指示方法、装置、设备和存储介质
US11240063B2 (en) Methods, nodes and computer readable media for tunnel establishment per slice
CN114500369A (zh) 控制路由迭代的方法、设备和系统
US9350654B1 (en) Microloop protection for multi-protocol label switching paths
US20200314016A1 (en) Tunneling inter-domain stateless internet protocol multicast packets
WO2021088561A1 (zh) 位索引显式复制网络中负载分担的方法、装置及设备
WO2023274083A1 (zh) 路由发布和转发报文的方法、装置、设备和存储介质
US20230308391A1 (en) Communication of policy changes in lisp-based software defined networks
WO2022247689A1 (zh) 流量报文转发方法、客户端、控制器及存储介质
WO2022222750A1 (zh) 报文转发方法、装置、网络设备及存储介质
US9781030B1 (en) Fast re-route protection using GRE over MPLS
WO2020114083A1 (zh) 一种ioam信息的处理方法和装置
WO2018095438A1 (zh) 等价多路径ecmp处理方法及装置
WO2022062956A1 (zh) 一种流量处理方法、装置和网络设备
CN107888501B (zh) 路由更新消息的发送方法、rr、网络设备和网络系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22810416

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022810416

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 18555925

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2022810416

Country of ref document: EP

Effective date: 20231017

NENP Non-entry into the national phase

Ref country code: DE