Dispatching system for data center outlet flow

Abstract

The invention provides a data center outlet flow scheduling system. The system comprises an intelligent management and control device used for obtaining traffic exit information and generating a traffic exit strategy of each terminal device based on the traffic exit information; the terminal equipment performs first encapsulation processing on the message data to be exported based on the acquired flow export strategy to generate a message data packet; the node equipment in the data center basic network is used for receiving the message data packet, performing second encapsulation processing on to-be-exported message data based on a path in the routing extension head, generating a target message data packet and forwarding the target message data packet; and the exit gateway equipment decapsulates the target message data packet by adopting the routing extension head, determines the target address information of the target message data packet, and sends the to-be-exported message data based on the target address information. According to the data center outlet flow scheduling system, the refinement degree of data center outlet flow scheduling is increased, and the flexibility of flow scheduling is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a scheduling system for data center egress traffic. Background Art

[0002] SRv6 technology is usually used in bearer networks and data center backbone networks. It is designed based on the concept of source routing. SRv6 inserts a routing extension header (Segment Routing Header, SRH for short) into the IPv6 message, pushes an explicit IPv6 address stack into the SRH, and the intermediate nodes continuously update the destination address and offset address stack to complete hop-by-hop forwarding. With the continuous expansion of network scale and the emergence of new services such as 5G services and smart cities, SRv6 technology has received strong attention and wide application in the operator field due to its advantages such as simple protocol, scalability, programmability, and strong compatibility, but its application and attention in the data center field are still relatively small.

[0003] The existing data center egress traffic scheduling methods are mainly based on the principles of basic network protocols such as the Border Gateway Protocol (BGP) and the Open Shortest Path First (OSPF) protocol. They control the device routing rules to forward the egress traffic and regulate the path based on the IP address. They can also control the publication of routes and the routing of traffic through isolation routing tables (VPN technology) to regulate the egress traffic to the designated data center traffic egress.

[0004] However, the existing data center export traffic scheduling method requires a large amount of routing calculations and requires artificial deployment of terminals with the same requirements on the same path or location during construction. It cannot meet the requirements of flexible expansion of data centers, flexible traffic and accurate scheduling.

[0005] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0006] The present application provides a data center egress traffic scheduling system to solve the technical problem that the data center egress traffic scheduling method in the prior art cannot meet the requirements of flexible capacity expansion of the data center and flexible traffic scheduling.

[0007] In a first aspect, the present application provides a scheduling system for data center egress traffic, the system comprising: an intelligent management and control device, for obtaining traffic egress information, and generating a traffic egress policy for each terminal device based on the traffic egress information, wherein the traffic egress information includes the egress information of each egress gateway in the multiple egress gateways scheduled by the scheduling system; a terminal device, for performing a first encapsulation process on egress message data to be exported based on the traffic egress policy obtained from the intelligent management and control device, and generating a message data packet, wherein the message data packet comprises: message data to be exported and a routing extension header, and the routing extension header is used to indicate a path of the message data; a node device in a data center infrastructure network, for receiving the message data packet, and performing a second encapsulation process on the message data to be exported based on the path in the routing extension header, generating a target message data packet and forwarding the target message data packet, wherein the target message data packet comprises: message data to be exported and a new routing extension header; an egress gateway device, for decapsulating the target message data packet using the routing extension header, determining the target address information of the target message data packet, and sending the egress message data packet based on the target address information.

[0008] Optionally, as in the above-mentioned scheduling system, the above-mentioned traffic export information specifically includes the export load and export quality of each export gateway among the multiple export gateways scheduled by the above-mentioned scheduling system; the above-mentioned intelligent management and control device is specifically used to obtain the traffic service requirements of each terminal device; based on the above-mentioned traffic service requirements and the export load and export quality of each export gateway, traffic path orchestration processing is performed to generate the above-mentioned traffic export strategy.

[0009] Optionally, as in the above-mentioned scheduling system, the above-mentioned intelligent management and control device is specifically used to: obtain the traffic delay and traffic demand size according to the above-mentioned traffic service requirements; obtain the matching candidate export gateway device according to the above-mentioned traffic demand size and the export load of each export gateway; obtain the target export gateway device according to the above-mentioned traffic delay and the export quality of the candidate export gateway; perform traffic path orchestration processing according to the network topology relationship of the above-mentioned target export gateway device to generate the above-mentioned traffic export strategy.

[0010] Optionally, as in the above-mentioned scheduling system, the above-mentioned traffic export strategy includes the export gateway address information and key path node address information of traffic forwarding; the above-mentioned terminal device is specifically used to perform message header encapsulation processing for the above-mentioned message data to be exported based on the above-mentioned traffic export strategy obtained from the above-mentioned intelligent management and control device, and generate the above-mentioned routing extension header, wherein the above-mentioned routing extension header encapsulates scheduling information, and the above-mentioned scheduling information includes the export gateway device address information, destination address information and key path node address information; according to the above-mentioned routing extension header and the above-mentioned message data packet, the above-mentioned message data packet is generated.

[0011] Optionally, as in the above-mentioned scheduling system, the node device in the above-mentioned data center infrastructure network is specifically used to: receive the above-mentioned message data packet; obtain the above-mentioned export gateway device address information and the above-mentioned key path node address information in the above-mentioned routing extension header in the above-mentioned message data packet; perform a second encapsulation processing on the above-mentioned message data packet to be exported based on the above-mentioned export gateway device address information, the above-mentioned destination address information and the above-mentioned key path node address information, generate a target message data packet and forward it until it is forwarded to the above-mentioned export gateway device.

[0012] Optionally, as in the above-mentioned scheduling system, the above-mentioned export gateway device is specifically used to: receive the above-mentioned target message data packet; decapsulate the above-mentioned target message data packet based on the above-mentioned routing extension header to obtain the above-mentioned destination address information; convert the above-mentioned destination address information from the intranet address to the external network address based on the preset address conversion requirement; and send and process the export message data based on the above-mentioned external network address.

[0013] Optionally, in the scheduling system described above, the message data packet is an SRV6 message, and the routing extension header is an SRH routing extension header.

[0014] Optionally, as in the above-mentioned scheduling system, the above-mentioned scheduling information is encapsulated after the header field of the SRH and before the variable-length TLV part.

[0015] Optionally, as in the above-mentioned dispatching system, the above-mentioned intelligent management and control device is also used to: interact with each exit device to obtain the exit information of each of the above-mentioned exit devices.

[0016] Optionally, as in the above-mentioned scheduling system, the above-mentioned data center basic network includes multiple node devices, and the above-mentioned multiple node devices are used to connect terminal devices and multiple distributedly deployed export gateway devices.

[0017] The data center egress traffic scheduling system provided in the present application is used to obtain egress traffic information through an intelligent management and control device, and to generate a traffic egress strategy for each terminal device based on the egress traffic information, wherein the egress traffic information includes the egress information of each egress gateway in the multiple egress gateways scheduled by the scheduling system; the terminal device is used to perform a first encapsulation process on the egress message data to be processed based on the egress traffic strategy obtained from the intelligent management and control device, and generate a message data packet, wherein the message data packet includes: the message data to be processed and a routing extension header, wherein the routing extension header is used to indicate the path of the message data; the nodes in the basic network of the data center The device is used to receive the above-mentioned message data packet, and perform a second encapsulation process on the above-mentioned message data to be exported based on the path in the above-mentioned routing extension header, generate a target message data packet and forward it, wherein the above-mentioned target message data packet includes: message data to be exported and a new routing extension header; the export gateway device is used to use the above-mentioned routing extension header to decapsulate the above-mentioned target message data packet, determine the target address information of the above-mentioned target message data packet, and send the message data to be exported based on the above-mentioned target address information. The scheduling system of the data center export traffic of the present invention increases the refinement of the data center export traffic mobilization and improves the flexibility of traffic mobilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0019] Figure 1 A schematic diagram of the structure of a data center egress traffic scheduling system provided in this application;

[0020] Figure 2 A schematic diagram of a routing extension header (SRH) encapsulation format provided in this application.

[0021] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0022] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0023] In the prior art, the data center egress scheduling method is mainly based on the configuration and optimization of the network protocol based on the local IP address (Native IP). The current data center egress scheduling includes the following methods: Method 1: The data center egress device uses the Border Gateway Protocol (BGP) to send the default route to the data center network, and the egress traffic selects the nearest egress in the network according to the BGP routing principle; Method 2: The data center egress device uses the BGP protocol to send the default route and AS_PATH list to the data center network, and adjusts the routing priority of a certain egress gateway in the data center network through the AS_PATH list, and dispatches some traffic with a slightly longer route distance to a specific egress; Method 3: Import part of the traffic into a VPN, send the default route in the form of VPNv4 to the VPN through the designated gateway device, and dispatch the egress traffic of the network devices and servers deployed in the VPN to the designated gateway device.

[0024] However, in the first method, the data center egress device uses the BGP protocol to send the default route to the data center network, and the egress traffic can only leave the data center at the nearest egress, which cannot meet the requirements of flexible traffic adjustment, fast fault convergence, and egress traffic migration. In the second method, the AS_PATH list is used to adjust the routing priority of a certain egress in the data center network, and dispatch some traffic with a slightly longer routing distance to a specific egress. It is still based on the routing principle of the BGP protocol, and the network protocol length from the terminal to the egress is manually calculated to control the traffic routing to a specific egress. In the scenario of distributed data centers, there may be scenarios where the traffic of multiple data centers needs to go to different egresses, or even the traffic on adjacent servers in the same data center needs to go to different egresses. Using a simple AS_PATH list cannot meet these high-precision egress scheduling requirements. In the third method, traffic is regulated through VPN technology, and VPN traffic must be iterated to the tunnel before it can be forwarded. The tunnel technology configuration is complex and has high technical requirements for intermediate equipment, which will introduce additional network equipment purchase, transformation and operation and maintenance costs. In addition, in ultra-large data centers, the egress equipment needs to maintain many VPN routing tables and corresponding routing protocol relationships, and performance will also become a bottleneck in the application process.

[0025] The specific application scenario of this application is the egress traffic scheduling of data centers. SRv6 technology has received strong attention and wide application in the operator field due to its advantages such as simple protocol, scalability, programmability, and strong compatibility, but its application and attention in the data center field are relatively small.

[0026] The data center egress traffic scheduling system provided in this application is intended to solve the above technical problems in the prior art.

[0027] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0028] Figure 1 This is a schematic diagram of the structure of a data center egress traffic scheduling system provided in this application. Figure 1 As shown, the scheduling system for the data center egress traffic may include: an intelligent management and control device 10, a terminal device 20, a node device 30 in the data center infrastructure network, and an egress gateway device 40.

[0029] In an embodiment of the present application, an intelligent management and control device 10 is used to obtain traffic export information and generate a traffic export policy for each terminal device based on the above-mentioned traffic export information; a terminal device 20 is used to perform a first encapsulation processing on the to-be-exported message data based on the above-mentioned traffic export policy obtained from the above-mentioned intelligent management and control device to generate a message data packet, wherein the above-mentioned message data packet includes: to-be-exported message data and a routing extension header; a node device 30 in a data center infrastructure network is used to receive the above-mentioned message data packet, and perform a second encapsulation processing on the to-be-exported message data based on the path in the above-mentioned routing extension header, generate a target message data packet and forward it, wherein the above-mentioned target message data packet includes: to-be-exported message data and a new routing extension header; an export gateway device 40 is used to use the above-mentioned routing extension header to decapsulate the above-mentioned target message data packet, determine the target address information of the above-mentioned target message data packet, and send the to-be-exported message data packet based on the above-mentioned target address information.

[0030] It should be noted that the above-mentioned traffic export information includes the export information of each export gateway among the multiple export gateways scheduled by the above-mentioned scheduling system, and the above-mentioned traffic export information also includes the export load and export quality of each export gateway among the multiple export gateways scheduled by the above-mentioned scheduling system; the above-mentioned routing extension header is used to indicate the path of the above-mentioned message data.

[0031] It should also be noted that the above message data packet is an SRV6 message, and the above routing extension header is an SRH routing extension header. SRv6 inserts a routing extension header SRH into the IPv6 message, and pushes an explicit IPv6 address stack into the SRH, and the intermediate node continuously updates the destination address and offset address stack to complete hop-by-hop forwarding.

[0032] As an optional embodiment, the intelligent management and control device 10 is responsible for collecting the load conditions and export quality of each gateway export gateway device 40, and allocating the terminal traffic export strategy based on the collected data, and sending the export strategy to the terminal device 20 and the export gateway device 40 of the data center; the terminal device 20, as the initiator of the export traffic, needs to send the traffic to the external network of the data center to meet business needs, and can encapsulate the SRv6 message header for the export traffic according to the strategy issued by the intelligent management and control device 10; the node device 30 in the data center basic network serves as the basis of the data center, connecting each terminal and multiple distributed data centers and export gateway devices; the export gateway device 40 is responsible for SRH decapsulation of the export traffic, converting the internal and external network addresses, etc., and finally sending the export message data based on the converted address for processing.

[0033] In an optional embodiment, the data center infrastructure network includes a plurality of node devices, and the plurality of node devices are used to connect terminal devices and a plurality of distributedly deployed egress gateway devices.

[0034] Through the embodiments of the present application, the software defined network (SDN) method and SRv6 technology are used to program and manage the message path, without any modification and adaptation of the network equipment, and the gateway device does not need to maintain any protocol relationship. Only a simple decapsulation of the message is required to realize the use of SRv6 to carry key forwarding nodes, egress gateway devices and final destination addresses, thereby achieving the technical effect of refined scheduling and flexible scheduling of data center egress traffic.

[0035] In an optional embodiment, the above-mentioned intelligent management and control device is specifically used to obtain the traffic service requirements of each terminal device; based on the above-mentioned traffic service requirements and the export load and export quality of each export gateway, the traffic path orchestration processing is performed to generate the above-mentioned traffic export strategy.

[0036] As an optional embodiment, the above-mentioned intelligent management and control device orchestrates the traffic path according to the traffic service requirements of each terminal device obtained, and the export load and export quality conditions in the export information of each export gateway device obtained, obtains the orchestration processing result, and generates the above-mentioned traffic export strategy based on the above-mentioned orchestration processing result.

[0037] In an optional embodiment, the above-mentioned intelligent management and control device is specifically used to: obtain the traffic delay and traffic demand size according to the above-mentioned traffic service demand; obtain the matching candidate export gateway device according to the above-mentioned traffic demand size and the export load of each export gateway; obtain the target export gateway device according to the above-mentioned traffic delay and the export quality of the candidate export gateway; perform traffic path orchestration processing according to the network topology relationship of the above-mentioned target export gateway device to generate the above-mentioned traffic export strategy.

[0038] As an optional embodiment, in the scheduling system of the data center egress traffic, the above-mentioned intelligent management and control device can be used to obtain the traffic service demand in real time, determine the traffic delay and traffic demand size in the above-mentioned traffic service demand, and use the above-mentioned intelligent management and control device to obtain the egress load of each egress gateway in real time, and match the appropriate candidate egress gateway device based on the traffic demand size in the traffic service demand. For example: After the above-mentioned intelligent management and control device obtains the traffic service demand, it first determines the traffic demand size in the traffic service demand, and obtains the egress load of each egress gateway at the same time. When the egress load condition meets the preset requirements, the candidate egress gateway device is determined based on the above-mentioned traffic demand size.

[0039] Optionally, it is also necessary to determine the target egress gateway device based on the traffic delay in the business requirements and the egress quality of the candidate egress gateway devices. For example, traffic services with smaller traffic delay can be preferentially allocated to egress gateway devices with lower egress quality but meeting the egress quality requirements, and traffic services with larger traffic delay can be preferentially allocated to egress gateway devices with higher egress quality.

[0040] Optionally, after determining the target egress gateway device, the traffic path orchestration processing is performed according to the network topology relationship of the target egress gateway device to obtain the orchestration processing result, and the traffic egress strategy is generated based on the orchestration processing result. The traffic egress information obtained by the intelligent management and control device and the traffic egress strategy generated for each terminal device can realize the refined scheduling of the data center egress traffic without maintaining numerous VPN routing tables and corresponding routing protocol relationships, and also avoids manually calculating the network protocol length from the terminal to the egress to control the traffic routing to a specific egress.

[0041] It should be noted that the above-mentioned process of matching the egress gateway device and the process of allocating traffic services are only examples, and in actual application, they can be adjusted or changed according to the actual situation.

[0042] In an optional embodiment, the above-mentioned traffic export strategy includes the export gateway address information and key path node address information of traffic forwarding; the above-mentioned terminal device is specifically used to perform message header encapsulation processing for the above-mentioned message data to be exported based on the above-mentioned traffic export strategy obtained from the above-mentioned intelligent management and control device, generate the above-mentioned routing extension header, and generate the above-mentioned message data packet based on the above-mentioned routing extension header and the above-mentioned message data to be exported.

[0043] As an optional embodiment, the terminal device receives the traffic scheduling configuration from the intelligent management and control device, performs SRH message header encapsulation for the export traffic according to the configuration, and generates the above-mentioned routing extension header, wherein the above-mentioned routing extension header encapsulates scheduling information, and the above-mentioned scheduling information includes export gateway device address information, destination address information and key path node address information.

[0044] Optional, such as Figure 2 As shown in the schematic diagram of the SRH encapsulation format, SRv6 inserts a Segment Routing Header (SRH) into the IPv6 message, pushes an explicit IPv6 address stack into the SRH, and the intermediate nodes continuously update the destination address and offset address stack to complete hop-by-hop forwarding. In order to achieve the ability to adjust the data center egress traffic, the terminal device (which can be a server) that sends the traffic encapsulates an SRv6 message header for the original message according to the actual needs of the traffic, and encapsulates the egress information and the key node information that must be passed to reach the corresponding egress into the SRH.

[0045] Optional, still as Figure 2 As shown, the next header can also be represented by next header, the last entry can also be represented by last entry, the header extension length can also be represented by hdr etx len, the Flags attribute can also be represented by the Flags attribute in the programming language (VB), the routing type can also be represented by routing type, the remaining segments can also be represented by segments left, the label can also be represented by tag, and the variable length TLV part can also be represented by optional tlv objects. Through the format and field definition of the SRv6 scheduling message, the SRv6 message data carries the key forwarding node, the egress gateway device and the final destination address, thereby realizing the refined scheduling of the data center egress traffic. By using the programmable space in the ipv6 message header, the SDN method and SRv6 related technologies are used to program and manage the message path, without any modification and adaptation of the network equipment, and the gateway device does not need to maintain any protocol relationship, and only needs to perform simple decapsulation processing on the message, which reduces the manual workload and improves work efficiency.

[0046] It should be noted that the above scheduling information is encapsulated after the header field of the SRH and before the variable-length TLV part.

[0047] In an optional embodiment, the node device in the above-mentioned data center infrastructure network is specifically used to: receive the above-mentioned message data packet; obtain the above-mentioned export gateway device address information and the above-mentioned key path node address information in the above-mentioned routing extension header in the above-mentioned message data packet; perform a second encapsulation processing on the above-mentioned message data packet to be exported based on the above-mentioned export gateway device address information, the above-mentioned destination address information and the above-mentioned key path node address information, generate a target message data packet and forward it until it is forwarded to the above-mentioned export gateway device.

[0048] As an optional embodiment, the encapsulated data message (the above-mentioned message data packet) enters the node device in the data center infrastructure network, and the node device re-encapsulates the above-mentioned message data packet to be exported according to the above-mentioned export gateway device address information, the above-mentioned destination address information and the above-mentioned key path node address information indicated by the SRH, and forwards it based on the above-mentioned export gateway device address information and the above-mentioned key path node address information to enter the export gateway device.

[0049] In an optional embodiment, the above-mentioned export gateway device is specifically used to: receive the above-mentioned target message data packet; decapsulate the above-mentioned target message data packet based on the above-mentioned routing extension header to obtain the above-mentioned destination address information; convert the above-mentioned destination address information from the intranet address to the external network address based on the preset address conversion requirement; and send and process the export message data based on the above-mentioned external network address.

[0050] As an optional embodiment, after receiving a data packet containing a re-encapsulated SRH header, the export gateway device decapsulates the SRH header and converts the actual destination IP carried in the SRH header into the destination IP of the final export message, performs source address conversion according to the preset requirements of the intelligent management and control device, determines the converted address as the final export message source IP, and sends it based on the above export message source IP.

[0051] In an optional embodiment, the intelligent management and control device is further used to: interact with each exit device to obtain exit information of each exit device.

[0052] In an embodiment of the present application, based on the format and field definition of the SRv6 scheduling message, the SRv6 message carries the key forwarding nodes, the export gateway device and the final destination address, and based on the traffic export information obtained by the intelligent management and control device and the traffic export policy generated for each terminal device, the refined scheduling of the data center export traffic is realized.

[0053] Through the embodiments of the present application, software-defined network methods and SRv6 technology are used to program and manage message paths. There is no need for any modification or adaptation of network devices, and gateway devices do not need to maintain any protocol relationships. Only simple decapsulation of the messages is required to implement the use of SRv6 to carry key forwarding nodes, egress gateway devices, and final destination addresses, thereby achieving the technical effect of refined scheduling and flexible scheduling of data center egress traffic.

[0054] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

[0055] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0056] It should be further noted that, although the various steps in the flow chart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flow chart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0057] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0058] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0059] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not specifically stated, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not specifically stated, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0060] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0061] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0062] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0063] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A data center egress traffic scheduling system, characterized in that: The system comprises: An intelligent management and control device, used to obtain traffic egress information and generate a traffic egress policy for each terminal device based on the traffic egress information, wherein the traffic egress information includes egress information of each egress gateway in the plurality of egress gateways scheduled by the scheduling system; The terminal device is used to perform a first encapsulation process on the message data to be exported based on the traffic export policy obtained from the intelligent management and control device to generate a message data packet, wherein the message data packet includes: the message data to be exported and a routing extension header, and the routing extension header is used to indicate the path of the message data; A node device in a data center infrastructure network, configured to receive the message data packet, and perform a second encapsulation process on the message data to be exported based on the path in the routing extension header, generate a target message data packet and forward it, wherein the target message data packet includes: the message data to be exported and a new routing extension header; The egress gateway device is used to use the routing extension header to decapsulate the target message data packet, determine the target address information of the target message data packet, and perform sending processing on the egress message data based on the target address information.

2. The dispatching system according to claim 1, characterized in that: The traffic egress information specifically includes the egress load and egress quality of each egress gateway among the multiple egress gateways scheduled by the scheduling system; The intelligent management and control device is specifically used to obtain the traffic service requirements of each terminal device; Based on the traffic service demand and the egress load and egress quality of each egress gateway, traffic path orchestration processing is performed to generate the traffic egress strategy.

3. The dispatching system according to claim 2, characterized in that: The intelligent management and control device is specifically used for: According to the traffic service demand, obtain the traffic delay and traffic demand size; According to the traffic demand size and the egress load of each egress gateway, obtaining a matching candidate egress gateway device; Acquire a target egress gateway device according to the traffic delay and the egress quality of the candidate egress gateway; According to the network topology of the target egress gateway device, traffic path orchestration processing is performed to generate the traffic egress strategy.

4. The dispatching system according to claim 1, characterized in that: The traffic egress strategy includes the egress gateway address information and key path node address information of the traffic forwarding; The terminal device is specifically used to perform message header encapsulation processing on the message data to be exported based on the traffic export policy obtained from the intelligent management and control device, and generate the routing extension header, wherein the routing extension header encapsulates scheduling information, and the scheduling information includes export gateway device address information, destination address information and key path node address information; The message data packet is generated according to the routing extension header and the message data to be exported.

5. The dispatching system according to claim 4, characterized in that: The node device in the data center basic network is specifically used for: Receiving the message data packet; Acquire the egress gateway device address information and the key path node address information in the routing extension header in the message data packet; The to-be-emitted message data packet is subjected to second encapsulation processing based on the egress gateway device address information, the destination address information and the key path node address information, and a target message data packet is generated and forwarded until it is forwarded to the egress gateway device.

6. The dispatching system according to claim 5, characterized in that: The egress gateway device is specifically used for: Receiving the target message data packet; Decapsulate the target message data packet based on the routing extension header to obtain the destination address information; Convert the destination address information from an intranet address to an extranet address based on a preset address conversion requirement; The outbound message data is sent and processed based on the external network address.

7. The dispatching system according to claim 4, characterized in that: The message data packet is an SRV6 message, and the routing extension header is an SRH routing extension header.

8. The dispatching system according to claim 7, characterized in that: The scheduling information is encapsulated after the header field of the SRH and before the variable-length TLV part.

9. The dispatching system according to claim 1, characterized in that: The intelligent management and control device is also used to interact with each exit device to obtain exit information of each exit device.

10. The dispatching system according to any one of claims 1 to 9, characterized in that: The data center basic network includes multiple node devices, and the multiple node devices are used to connect terminal devices and multiple distributed deployed egress gateway devices.

Images