Flow traction control method and device, flow diversion device, and flow traction system

By analyzing SRv6 data packets in metropolitan network routers and urging traffic based on service orchestration information, the problems of poor tunnel support and insufficient PBR flexibility are solved, and flexible traffic drainage for the rapid deployment of VAS in edge cloud MECs are achieved, reducing the Equipment burden and ecological construction difficulty improve forwarding efficiency.

CN114157612BActive Publication Date: 2024-11-22CHINA TELECOM CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111500250.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-09
Publication Date
2024-11-22
Estimated Expiration
2041-12-09

AI Technical Summary

Technical Problem

The metropolitan area network routers have poor support for tunnels, which increases CPU burden and cost. The PBR method lacks flexibility and is difficult to control backhaul traffic. The SFC support for VAS services is low and it is difficult to deploy commercially.

Method used

By analyzing the SRH after receiving the SRv6 data packet, identifying the current SID, stripping the SRH to obtain the load traffic, querying the forwarding path information based on the preset service orchestration information, pulling the load traffic to the corresponding value-added service module, realizing traffic traction, and After the load traffic traction is completed, the SRH is encapsulated to generate the packet to be forwarded.

Benefits of technology

It reduces the difficulty of building a VAS ecosystem, improves forwarding efficiency, reduces the protocol complexity requirements for devices, supports flexible drainage organizations between multiple VAS, and simplifies the rapid deployment of VAS for edge cloud MECs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114157612B_ABST
    Figure CN114157612B_ABST
Patent Text Reader

Abstract

The present disclosure provides a flow traction control method and device, a flow diversion device, and a flow traction system. The flow traction control method includes: after receiving an SRv6 data packet, parsing the SRH of the SRv6 data packet to identify the current SID in the SID list; if the locator of the current SID is a local locator, stripping the SRH of the SRv6 data packet to obtain the load flow; querying the forwarding path information associated with the current SID according to the preset service arrangement information; sequentially traction the load flow to the corresponding value-added service module according to the interface identifier included in the forwarding path information to achieve load flow traction; after the load flow traction is completed, encapsulating the SRH for the load flow, and subtracting 1 from the number of remaining segments in the SRH to generate data to be forwarded; forwarding the data packet to be forwarded according to the next SID in the SID list.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of network technology, and in particular to a flow traction control method and device, a flow diversion device, and a flow traction system. Background Art

[0002] In related technologies, in order to achieve traffic traction, it is necessary to configure a diversion tunnel or PBR (Policy Based Routing) on ​​the metropolitan area network router to migrate user traffic to the VAS (Value Added Service) of the edge cloud. Summary of the invention

[0003] The inventors noticed that the metropolitan area network router equipment currently has poor support for tunnels, and the router supports tunnel modes such as IPsec (Internet Protocol Security) / VXLAN (Virtual extensible LAN) which will increase the CPU burden of the device and increase costs, while the PBR method lacks flexibility and is difficult to control return traffic.

[0004] In addition, if the user's service loading needs require flexible organization between multiple VAS, the edge cloud VAS needs to support SFC (Service Function Chain). Currently, the SFC support of VAS services is still very low, making it difficult to deploy commercially.

[0005] To this end, the present disclosure provides a traffic traction control solution that can enable operators to quickly deploy VAS in the edge cloud MEC (Mobile Edge Computing) connected to the metropolitan area network.

[0006] According to a first aspect of an embodiment of the present disclosure, a traffic traction control method is provided, comprising: after receiving an SRv6 data packet, parsing the SRH of the SRv6 data packet to identify a current SID in a SID list; if the locator of the current SID is a local locator, stripping the SRH of the SRv6 data packet to obtain load traffic; querying forwarding path information associated with the current SID according to preset service orchestration information; sequentially traction of the load traffic to a corresponding value-added service module according to an interface identifier included in the forwarding path information to implement load traffic traction; after the load traffic traction is completed, encapsulating the SRH for the load traffic, and subtracting 1 from the number of remaining segments in the SRH to generate data to be forwarded; and forwarding the data packet to be forwarded according to the next SID in the SID list.

[0007] In some embodiments, pulling the load traffic to the corresponding value-added service module in sequence according to the interface identifiers included in the forwarding path information includes: using the first interface in the forwarding path information as the current outbound interface and the second interface as the current inbound interface; sending the load traffic to the corresponding value-added service module according to the current outbound interface; after the current inbound interface receives the load traffic, determining whether the current inbound interface is the last interface in the forwarding path information; if the current inbound interface is the last interface in the forwarding path information, determining that the load traffic pulling is complete.

[0008] In some embodiments, if the current inbound interface is not the last interface in the forwarding path information, the next interface bridged with the current inbound interface is used as the current outbound interface, and the next interface of the current outbound interface is used as the current inbound interface; then the step of sending the load traffic to the corresponding value-added service module according to the current outbound interface is executed.

[0009] According to a second aspect of an embodiment of the present disclosure, a traffic traction control device is provided, comprising: a first processing module, configured to parse the SRH of the SRv6 data packet to identify the current SID in the SID list after receiving the SRv6 data packet; a second processing module, configured to strip the SRH of the SRv6 data packet if the locator of the current SID is a local locator to obtain load traffic; a third processing module, configured to query forwarding path information associated with the current SID according to preset service orchestration information; a fourth processing module, configured to traction the load traffic to the corresponding value-added service module according to the interface identifier included in the forwarding path information in turn to achieve load traffic traction; a fifth processing module, configured to encapsulate the load traffic with SRH after the load traffic traction is completed, and subtract 1 from the number of remaining segments in the SRH to generate data to be forwarded, and forward the data packet to be forwarded according to the next SID in the SID list.

[0010] In some embodiments, the fourth processing module is configured to use the first interface in the forwarding path information as the current outbound interface and the second interface as the current inbound interface, and send the load traffic to the corresponding value-added service module based on the current outbound interface. After the current inbound interface receives the load traffic, it is determined whether the current inbound interface is the last interface in the forwarding path information. If the current inbound interface is the last interface in the forwarding path information, it is determined that the load traffic traction is completed.

[0011] In some embodiments, the fourth processing module is configured to use the next interface bridged with the current inbound interface as the current outbound interface if the current inbound interface is not the last interface in the forwarding path information, and use the next interface of the current outbound interface as the current inbound interface, and then execute the step of sending the load traffic to the corresponding value-added service module according to the current outbound interface.

[0012] According to a third aspect of an embodiment of the present disclosure, a flow traction control device is provided, comprising: a memory configured to store instructions; a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on the instructions stored in the memory.

[0013] According to a fourth aspect of an embodiment of the present disclosure, a drainage device is provided, comprising a flow traction control device as described in any of the above embodiments.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a traffic traction system is provided, comprising: a traffic diversion device as described in any of the above embodiments; and an SRv6 controller configured to configure business orchestration information for the traffic diversion device.

[0015] According to a sixth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any of the above embodiments is implemented.

[0016] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0018] Figure 1 A flow chart of a flow traction control method according to an embodiment of the present disclosure;

[0019] Figure 2 It is a structural schematic diagram of a flow traction control device according to an embodiment of the present disclosure;

[0020] Figure 3 It is a structural schematic diagram of a flow traction control device according to another embodiment of the present disclosure;

[0021] Figure 4This is a schematic structural diagram of a drainage device according to an embodiment of the present disclosure;

[0022] Figure 5 This is a schematic structural diagram of a drainage device according to another embodiment of the present disclosure;

[0023] Figure 6 A schematic diagram of the structure of a flow traction system according to an embodiment of the present disclosure;

[0024] Figure 7 A schematic diagram of the structure of a flow traction system according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0026] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0027] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0028] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0029] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0030] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0031] Figure 1 FIG. 1 is a flow chart of a flow traction control method according to an embodiment of the present disclosure. In some embodiments, the following flow traction control method is executed by a flow traction control device.

[0032] In step 101, after receiving a SR (Segment Routing) v6 data packet, an SRH (Segment Routing Header) of the SRv6 data packet is parsed to identify a current SID in a SID (Segment Identifier) ​​list.

[0033] In step 102, if the locator of the current SID is a local locator, the SRH of the SRv6 data packet is stripped to obtain the load flow.

[0034] In step 103, forwarding path information associated with the current SID is queried according to preset service arrangement information.

[0035] In some embodiments, the service orchestration information is configured by an SRv6 controller.

[0036] In step 104, the load traffic is pulled to the corresponding value-added service module according to the interface identifiers included in the forwarding path information in turn, so as to realize load traffic pulling.

[0037] In some embodiments, the first interface in the forwarding path information is used as the current outgoing interface, and the second interface is used as the current incoming interface. According to the current outgoing interface, the load flow is sent to the corresponding value-added service module. After the current incoming interface receives the load flow, it is determined whether the current incoming interface is the last interface in the forwarding path information. If the current incoming interface is the last interface in the forwarding path information, it is determined that the load flow traction is completed.

[0038] For example, the forwarding path includes interfaces P1 and P2, and interface P1 is used to send the load flow to the corresponding value-added service module. After interface P2 receives the load flow, it is determined that the load flow pulling is completed. That is, this embodiment corresponds to a scenario of a value-added service module.

[0039] In some embodiments, the first interface in the forwarding path information is used as the current outbound interface, and the second interface is used as the current inbound interface. According to the current outbound interface, the load traffic is sent to the corresponding value-added service module. After the current inbound interface receives the load traffic, it is determined whether the current inbound interface is the last interface in the forwarding path information. If the current inbound interface is not the last interface in the forwarding path information, the next interface bridged with the current inbound interface is used as the current outbound interface, and the next interface of the current outbound interface is used as the current inbound interface, and then the step of sending the load traffic to the corresponding value-added service module according to the current outbound interface is repeated. If the current inbound interface is the last interface in the forwarding path information, it is determined that the load traffic traction is completed.

[0040] For example, the forwarding path includes interfaces P1, P2, P3, and P4, and interface P1 is used to send the load traffic to the corresponding value-added service module 1. After interface P2 receives the load traffic, interface P3 bridged with interface P2 is used to send the load traffic to the corresponding value-added service module 2. After interface P4 receives the load traffic, it is determined that the load traffic pulling is completed. That is, this embodiment corresponds to the scenario of two value-added service modules.

[0041] In step 105, after the load flow is pulled, the load flow is encapsulated in SRH, and the number of remaining segments (Segment Left, SL for short) in the SRH is reduced by 1 to generate data to be forwarded.

[0042] In step 106, the data packet to be forwarded is forwarded according to the next SID in the SID list.

[0043] Figure 2 FIG. 1 is a schematic diagram of the structure of a flow traction control device according to an embodiment of the present disclosure. Figure 2 As shown, the flow traction control device includes a first processing module 21 , a second processing module 22 , a third processing module 23 , a fourth processing module 24 and a fifth processing module 25 .

[0044] The first processing module 21 is configured to parse the SRH of the SRv6 data packet to identify the current SID in the SID list after receiving the SRv6 data packet.

[0045] The second processing module 22 is configured to strip the SRH of the SRv6 data packet to obtain the load flow if the locator of the current SID is a local locator.

[0046] The third processing module 23 is configured to query the forwarding path information associated with the current SID according to the preset service arrangement information.

[0047] In some embodiments, the service orchestration information is configured by an SRv6 controller.

[0048] The fourth processing module 24 is configured to pull the load traffic to the corresponding value-added service module in turn according to the interface identifier included in the forwarding path information, so as to realize load traffic pulling.

[0049] In some embodiments, the fourth processing module 24 uses the first interface in the forwarding path information as the current outbound interface and the second interface as the current inbound interface, and sends the load traffic to the corresponding value-added service module based on the current outbound interface. After the current inbound interface receives the load traffic, it determines whether the current inbound interface is the last interface in the forwarding path information. If the current inbound interface is the last interface in the forwarding path information, it is determined that the load traffic traction is completed.

[0050] If the current inbound interface is not the last interface in the forwarding path information, the fourth processing module 24 will use the next interface bridged to the current inbound interface as the current outbound interface, and the next interface of the current outbound interface as the current inbound interface, and then execute the operation of sending the load traffic to the corresponding value-added service module according to the current outbound interface.

[0051] The fifth processing module 25 is configured to encapsulate SRH for the load flow after the load flow is pulled, and subtract 1 from the number of remaining segments in the SRH to generate data to be forwarded, and forward the data packet to be forwarded according to the next SID in the SID list.

[0052] Figure 3 FIG. 1 is a schematic diagram of the structure of a flow traction control device according to another embodiment of the present disclosure. Figure 3 As shown, the flow traction control device includes a memory 31 and a processor 32 .

[0053] The memory 31 is used to store instructions. The processor 32 is coupled to the memory 31. The processor 32 is configured to execute the instructions stored in the memory to implement the following. Figure 1 The method of any one of the embodiments.

[0054] like Figure 3 As shown, the network flow traction control device also includes a communication interface 33 for information exchange with other devices. At the same time, the flow traction control device also includes a bus 34, through which the processor 32, the communication interface 33, and the memory 31 communicate with each other.

[0055] The memory 31 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. The memory 31 may also be a memory array. The memory 31 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0056] In addition, the processor 32 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.

[0057] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, which are executed by a processor to implement the following Figure 1 The method of any one of the embodiments.

[0058] Figure 4 FIG. 1 is a schematic diagram of the structure of a drainage device according to an embodiment of the present disclosure. Figure 4As shown, the drainage device 40 includes a flow traction control device 41. The flow traction control device 41 is Figure 2 or Figure 3 A flow traction control device according to any one of the embodiments.

[0059] like Figure 4 As shown, the flow diversion device 40 further includes a WAN (Wide Area Network) interface 42 for flow entering and exiting the flow diversion device 40. The flow diversion device 40 further includes a plurality of interfaces P1-Pn so that the flow enters the corresponding value-added service module.

[0060] As an example, in Figure 5 In the figure, the drainage device is provided with interfaces P1, P2, P3 and P4, of which P2 and P3 are bridged. Interfaces P1 and P2 are connected to VAS1, and interfaces P3 and P4 are connected to VAS2. The bold line in the figure indicates the direction of traffic transmission.

[0061] Figure 6 FIG. 1 is a schematic diagram of the structure of a flow traction system according to an embodiment of the present disclosure. Figure 6 As shown, the flow traction system includes a flow diversion device 61 and an SRv6 controller 62. The flow diversion device 61 is Figure 4 and Figure 5 The drainage device involved in any embodiment.

[0062] The SRv6 controller 62 is configured to configure service orchestration information for the traffic diversion device 61 .

[0063] The present disclosure is described below by using a specific example.

[0064] Figure 7 This is a schematic diagram of the structure of a flow traction system according to another embodiment of the present disclosure. As an example, four interfaces P1-P4 are provided in the flow diversion device.

[0065] like Figure 7 As shown in Table 1, in the direction from the client to the Internet, the corresponding SID is SID1. In the direction from the Internet to the client, the corresponding SID is SID2. The specific contents are shown in Table 1.

[0066] SID Customer ID Drainage direction Forwarding Path SID1 A Client to Internet P1→P2→P3→P4 SID2 A Internet to Customer P4→P3→P2→P1

[0067] Table 1

[0068] For example, in the direction from the customer to the Internet, the traffic diversion device uses interface P1 to send the load traffic to the corresponding VAS1. After interface P2 receives the load traffic, the traffic diversion device uses interface P3 bridged with interface P2 to send the load traffic to the corresponding VAS2. After interface P4 receives the load traffic, it determines that the load traffic diversion is completed.

[0069] For another example, in the direction from the Internet to the customer, the traffic diversion device uses interface P4 to send the load traffic to the corresponding VAS2. After interface P3 receives the load traffic, the traffic diversion device uses interface P2 bridged with interface P3 to send the load traffic to the corresponding VAS1. After interface P1 receives the load traffic, it determines that the load traffic diversion is completed.

[0070] By implementing the above embodiments of the present disclosure, the following beneficial effects can be obtained:

[0071] 1. This disclosure does not require the VAS service to support SFC or SRv6, which can reduce the difficulty of building a VAS ecosystem.

[0072] 2. The present disclosure can replace the VAS service / service set subscribed by a single customer with a SID on the network side, and use the SRv6 single protocol stack to connect the application and the network. Compared with the tunnel and PBR modes, it increases the forwarding efficiency and reduces the protocol complexity requirements for the network side devices.

[0073] In some embodiments, the functional unit module described above can be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components or any appropriate combination thereof for performing the functions described in the present disclosure.

[0074] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0075] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A flow traction control method, comprising: After receiving the SRv6 data packet, parsing the SRH of the SRv6 data packet to identify the current SID in the SID list; If the locator of the current SID is a local locator, stripping the SRH of the SRv6 data packet to obtain the load flow; According to the preset service arrangement information, query the forwarding path information associated with the current SID; Pulling the load flow to the corresponding value-added service module according to the interface identifier included in the forwarding path information in turn, so as to realize load flow pulling; After the load flow is pulled, the load flow is encapsulated in SRH, and the number of remaining segments in the SRH is reduced by 1 to generate data to be forwarded; Forwarding the data packet to be forwarded according to the next SID in the SID list; Wherein, sequentially according to the interface identifiers included in the forwarding path information, pulling the load flow to the corresponding value-added service module includes: Using the first interface in the forwarding path information as the current outgoing interface and using the second interface as the current incoming interface; According to the current outgoing interface, the load traffic is sent to a corresponding value-added service module; After the current inbound interface receives the load flow, determining whether the current inbound interface is the last interface in the forwarding path information; If the current inbound interface is not the last interface in the forwarding path information, the next interface bridged with the current inbound interface is used as the current outbound interface, and the next interface of the current outbound interface is used as the current inbound interface; Then, the load traffic is sent to a corresponding value-added service module according to the current outgoing interface.

2. The method according to claim 1, wherein: Pulling the load flow to the corresponding value-added service module according to the interface identifier included in the forwarding path information includes: If the current inbound interface is the last interface in the forwarding path information, it is determined that the load flow pulling is completed.

3. A flow traction control device, comprising: A first processing module is configured to, after receiving the SRv6 data packet, parse the SRH of the SRv6 data packet to identify the current SID in the SID list; The second processing module is configured to strip the SRH of the SRv6 data packet to obtain the load flow if the locator of the current SID is a local locator; A third processing module is configured to query forwarding path information associated with the current SID according to preset service arrangement information; A fourth processing module is configured to pull the load traffic to the corresponding value-added service module in turn according to the interface identifier included in the forwarding path information to realize load traffic pulling, wherein the first interface in the forwarding path information is used as the current egress interface, and the second interface is used as the current ingress interface, and the load traffic is sent to the corresponding value-added service module according to the current egress interface. After the current ingress interface receives the load traffic, it is determined whether the current ingress interface is the last interface in the forwarding path information. If the current ingress interface is not the last interface in the forwarding path information, the next interface bridged with the current ingress interface is used as the current egress interface, and the next interface of the current egress interface is used as the current ingress interface, and then the operation of sending the load traffic to the corresponding value-added service module according to the current egress interface is performed; The fifth processing module is configured to encapsulate SRH for the load flow after the load flow is pulled, and subtract 1 from the number of remaining segments in the SRH to generate data to be forwarded, and forward the data packet to be forwarded according to the next SID in the SID list.

4. The device according to claim 3, wherein: The fourth processing module is configured to determine that load flow pulling is finished if the current inbound interface is the last interface in the forwarding path information.

5. A flow traction control device, comprising: a memory configured to store instructions; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 1 to 2 based on instructions stored in the memory.

6. A drainage device, comprising the flow traction control device according to any one of claims 3 to 5.

7. A flow traction system, comprising: The drainage device according to claim 6; The SRv6 controller is configured to configure service orchestration information for the traffic diversion device.

8. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 2 is implemented.