Flow scheduling system

Abstract

The invention provides a traffic scheduling system, and relates to the technical field of traffic scheduling, and the system comprises an analysis module which is used for analyzing a scheduling strategy file of a target service, generating a deployment strategy file and a traffic scheduling rule file of the target service, and recording the scheduling strategy file, a scheduling strategy for scheduling the first access request to the target geographic area; the deployment module is used for deploying the target service to the target node according to the deployment strategy file and then storing the traffic scheduling rule file to the scheduling module; and the scheduling module is used for performing scheduling control on the first access request according to the geographic area of the source of the first access request and the scheduling rule recorded by the scheduling rule file. The scheduling strategy recorded in the scheduling strategy file can be flexibly configured according to different business requirements of the target service, and the deployment module can accurately and efficiently deploy the target service to a required area according to the deployment strategy file to meet the business requirements.

Description

Technical Field

[0001] This application relates to the technical field of traffic scheduling, and particularly to a traffic scheduling system. Background Art

[0002] In the modern Internet environment, with the continuous development of the Internet and the increasing demand for the Internet by people, the performance and quality of network services have attracted more and more attention. Since the Internet is global, when users in different geographical locations access the same website, there may be differences in their network connection quality and latency. Therefore, it is necessary to perform corresponding traffic scheduling according to the geographical location of the user access request source to improve service quality.

[0003] To solve the problem of traffic scheduling based on the geographical location of the access request source, in the prior art, the request IP address in the user access request is encoded and converted according to a certain rule, and the first three digits of the converted IP class are matched with the request IP address. If the match is successful, traffic scheduling is performed through the region information and operator information corresponding to the IP class.

[0004] However, the above prior art has the following problems: First, since the matching only performs the first three-digit matching, if the match is the same, traffic scheduling can be performed, and if it is different, scheduling cannot be performed, which lacks flexibility; second, different scheduling strategies cannot be set for different services, and the scheduling method is single; third, it cannot meet the hierarchical traffic scheduling of regions. For example, when the service at the city level is abnormal or the service is not deployed, the traffic cannot be automatically scheduled to the provincial level. Summary of the Invention

[0005] This application provides a traffic scheduling system to solve the following technical problems in the prior art: First, since the matching only performs the first three-digit matching, if the match is the same, traffic scheduling can be performed, and if it is different, scheduling cannot be performed, which lacks flexibility; second, different scheduling strategies cannot be set for different services, and the scheduling method is single; third, it cannot meet the hierarchical traffic scheduling of regions.

[0006] This application provides a traffic scheduling system, and the system includes:

[0007] A parsing module, used for:

[0008] Parse the scheduling policy file of the target service to generate the deployment policy file and traffic scheduling rule file of the target service. The scheduling policy file records: a scheduling policy for scheduling the first access request to the target geographical area according to the geographical area of the source of the first access request to the target service. The deployment policy file records the deployment policy for deploying the target service to the target node corresponding to the target geographical area. The traffic scheduling rule file records: a scheduling rule for scheduling the first access request to the target node according to the geographical area of the source of the first access request.

[0009] A deployment module, configured to:

[0010] After deploying the target service to the target node according to the deployment policy file, store the traffic scheduling rule file in the scheduling module.

[0011] The scheduling module is configured to: after receiving the first access request sent by the client, perform scheduling control on the first access request according to the geographical area of the source of the first access request and the scheduling rule recorded in the scheduling rule file.

[0012] In the above preferred technical solution of a traffic scheduling system, the deployment policy file records the administrative coding information of the target geographical area, the IP address information of the target node, and the deployment quantity of the target service on the target node. The deployment module is specifically configured to:

[0013] Deploy the target service to the target node according to the administrative coding information of the target geographical area and the IP address information of the target node according to the deployment quantity.

[0014] In the above preferred technical solution of a traffic scheduling system, the deployment module is specifically configured to:

[0015] Deploy the container image of the target service to the target node according to the deployment quantity.

[0016] In the above preferred technical solution of a traffic scheduling system, the traffic scheduling rule file records: the public network access IP address information of the target node, and a plurality of target administrative coding information corresponding to the public network access IP address information of the target node. The deployment module is further configured to:

[0017] Store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node in the scheduling module.

[0018] In the above preferred technical solution of a traffic scheduling system, the scheduling module is specifically configured to:

[0019] After receiving the first access request sent by the client, obtain the egress IP address information of the first access request;

[0020] According to the egress IP address information, determine the administrative code of the geographical area where the first access request originates;

[0021] Verify whether the administrative code of the source geographical area matches one of the administrative codes in the target administrative codes. If so, schedule the first access request to the target node.

[0022] In the above preferred technical solution of a traffic scheduling system, the scheduling module is specifically used for:

[0023] If the administrative code of the source geographical area matches one of the administrative codes in the target administrative codes, send the public network access IP address information of the target node and the port number information to the client.

[0024] In the above preferred technical solution of a traffic scheduling system, the target node includes a first target node and a second target node. The traffic scheduling rule file records: the public network access IP address information of the first target node, the public network access IP address information of the second target node, and several first target administrative code information corresponding to the public network access IP address information of the first target node. The deployment module is further used for:

[0025] Store the public network access IP address information of the first target node, the public network access IP address information of the second target node, the first target administrative code information, the port number information of the target service deployed on the first target node, and the port number information of the target service deployed on the second target node into the scheduling module.

[0026] In the above preferred technical solution of a traffic scheduling system, the scheduling module is specifically used for:

[0027] If the administrative code of the source geographical area matches one of the first target administrative codes, determine whether the target service deployed on the first target node has a fault:

[0028] If so, send the public network access IP address information of the second target node and the port number information of the target service deployed on the second target node to the client;

[0029] If not, send the public network access IP address information of the first target node and the port number information of the target service deployed on the first target node to the client.

[0030] In the above preferred technical solution of a traffic scheduling system, the scheduling module includes a DNS server, and the deployment module is specifically configured to store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node into the DNS server.

[0031] In the above preferred technical solution of a traffic scheduling system, the scheduling module is further configured to:

[0032] After receiving the microservice access request sent by the client, according to the microservice access request, obtain the target access domain name information of the microservice access request;

[0033] If the target access domain name information matches the domain name information of the target service, determine the microservice access request as the first access request.

[0034] For a traffic scheduling system provided by this application, the scheduling policies recorded in the scheduling policy file can be flexibly configured according to different business requirements of the target service, and can better meet the traffic scheduling requirements of actual business compared with the prior art. And because the scheduling policy file can set the target geographical area to which the access request is scheduled to a geographical area level different from the geographical area where the access request comes from. For example, set the target geographical area to a provincial administrative region and the source geographical area to a municipal administrative region, so as to achieve cross-geographical area level traffic scheduling. However, the prior art cannot achieve cross-geographical area level traffic scheduling because no corresponding scheduling policy file is configured; the traffic scheduling system parses and generates a deployment policy file according to the pre-configured scheduling policy file. Since the deployment policy file records the target nodes to which the target service needs to be deployed, the deployment module can accurately and efficiently deploy the target service to the required area according to the deployment policy file, so that the deployment location of the target service can meet the business requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application.

[0036] Figure 1 is a schematic diagram of a traffic scheduling system provided by an embodiment of this application;

[0037] Figure 2 is a schematic diagram of cross-geographical area level access request scheduling provided by an embodiment of this application;

[0038] Figure 3 is a schematic diagram of access request scheduling based on the principle of proximity provided by an embodiment of this application;

[0039] Figure 4It is a flowchart of a method for a scheduling module to perform scheduling control on a first access request according to a traffic scheduling rule file provided by an embodiment of the present application;

[0040] Figure 5 It is a flowchart of a method for a scheduling module to perform scheduling control on a microservice access request according to a traffic scheduling rule file provided by an embodiment of the present application.

[0041] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept 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. Specific Embodiments

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

[0043] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0044] First, the nouns appearing in the present application are explained:

[0045] Traffic scheduling: The process of dispatching a large number of concurrent request packets from customers to different service - side program instances according to specific policies;

[0046] Container: A container contains a complete running environment for a microservice. In addition to the microservice application itself, all dependencies, class libraries, other binary files, configuration files, etc. required by this application are uniformly packaged into a package called a container image. By containerizing the application itself and its dependencies, differences caused by operating system distribution versions and other basic environments are abstracted, making it more flexible to transplant and deploy the image from one environment to another.

[0047] DNS Server: Domain Name Server. A domain name server is a server that performs the conversion between domain names and their corresponding IP addresses. A DNS server stores a table of domain names and their corresponding IP addresses to resolve the domain names of messages. A domain name is the name of a computer or a group of computers on the Internet, used to identify the electronic location (sometimes also referring to the geographical location) of the computer during data transmission. A domain name is composed of a string of names separated by dots, usually including the organization name, and always including a suffix of two to three letters to indicate the type of the organization or the country / region where the domain is located.

[0048] In the modern Internet environment, with the continuous development of the Internet and the increasing demand of people for the Internet, the performance and quality of network services have attracted more and more attention. Since the Internet is global, when users in different geographical locations access the same website, there may be differences in the quality of their network connections and latency times. Therefore, it is necessary to perform corresponding traffic scheduling according to the geographical location of the source of the user access request to improve the service quality.

[0049] To solve the problem of traffic scheduling according to the geographical location of the access request source, in the prior art, the request IP address in the user access request is encoded and converted according to a certain rule, and the first three digits of the converted IP class are matched with the request IP address. If the match is successful, traffic scheduling is performed based on the regional information and operator information corresponding to the IP class.

[0050] However, the above prior art has the following problems: First, since the matching only performs the first three-digit matching, if the match is the same, traffic scheduling can be performed, and if it is different, scheduling cannot be performed, lacking flexibility; second, different scheduling strategies cannot be set for different services, and the scheduling method is single; third, it cannot meet the hierarchical traffic scheduling of regions. For example, when the service at the city level is abnormal or not deployed, the traffic cannot be automatically scheduled to the provincial level.

[0051] A traffic scheduling system provided by the present application aims to solve the above technical problems in the prior art. Its technical concept is as follows: The parsing module of the traffic scheduling system generates a deployment policy file and a traffic scheduling rule file for the target service according to the scheduling policy file of the target service. The scheduling policy file records the scheduling policy of scheduling the first access request to the target geographical area according to the geographical area of the source of the first access request to the target service. The deployment policy file records the deployment policy of deploying the target service to the target node corresponding to the target geographical area. The traffic scheduling rule file records the scheduling rule of scheduling the first access request to the target node according to the geographical area of the source of the first access request. After the deployment module of the traffic scheduling system deploys the target service to the target node according to the deployment policy file, it stores the traffic scheduling rule file in the scheduling module. When the scheduling module receives an access request from a user to access the target service, it performs scheduling control on the access request according to the geographical area of the source of the access request and the scheduling rule file.

[0052] The following uses specific embodiments to elaborate in detail on the technical solution of the present application and how the technical solution of the present application solves the above technical problems. These several specific embodiments below 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 with reference to the accompanying drawings.

[0053] In a possible embodiment of the present application, a traffic scheduling system is provided. Figure 1 It is a schematic diagram of a traffic scheduling system provided by an embodiment of the present application. As Figure 1 shown, the system includes:

[0054] A parsing module 101, configured to:

[0055] Parse the scheduling policy file of the target service, and generate a deployment policy file and a traffic scheduling rule file for the target service. The scheduling policy file records: the scheduling policy of scheduling the first access request to the target geographical area according to the geographical area of the source of the first access request to the target service. The deployment policy file records the deployment policy of deploying the target service to the target node corresponding to the target geographical area. The traffic scheduling rule file records: the scheduling rule of scheduling the first access request to the target node according to the geographical area of the source of the first access request.

[0056] In this embodiment, the scheduling policy file of the target service can be registered with the scheduling system so that the scheduling system can obtain the scheduling policy file. The scheduling policy file of the target service can be pre-compiled according to the specific business rules of the target service. For example, for a certain target service, the scheduling policy recorded in its scheduling policy file can be: cross-regional hierarchical access request scheduling, scheduling access requests from different counties in the same city to the municipal node. If the municipal node cannot provide services, the access request will be scheduled to the provincial node; access request scheduling based on the principle of proximity, scheduling access requests from several geographical regions to the nodes in the central region of these geographical regions.

[0057] Figure 2 is a schematic diagram of cross-regional hierarchical access request scheduling provided by an embodiment of the present application. As Figure 2 shown, County 1 to County 4 are different subordinate counties of the city, and the lengths of the lines between the city and the counties represent the distances between the city and the counties. In actual business, there will be a need to schedule access requests from each secondary administrative region under a certain administrative region to that administrative region. For example Figure 2 shown, scheduling access requests from the counties under the city to the city, and the provincial node serves as a redundant node to provide services to each county when the municipal node cannot provide services.

[0058] Figure 3 is a schematic diagram of access request scheduling based on the principle of proximity provided by an embodiment of the present application. As Figure 3 shown, County 1 to County 3 belong to Province 1, and County 4 to County 6 belong to Province 2. The access requests from County 1 to County 6 can be scheduled across provinces to the central region.

[0059] As Figure 2 , Figure 3 shown, the scheduling policy in this embodiment can be flexibly configured according to the actual business needs of the target service, and its flexibility is higher than the method in the prior art of matching the first three digits of the IP class with the access request IP address and performing scheduling if they match.

[0060] The deployment module 102 is used for:

[0061] After deploying the target service to the target node according to the deployment policy file, storing the traffic scheduling rule file in the scheduling module 103;

[0062] In this embodiment, the target node can be one or more target servers, and the deployment policy file can be in the following form: the IP address of the target node, the number of target service deployments corresponding to the IP address of the target node. It should be noted that there can be multiple target nodes. Referring to Figure 2 , the target node can be a municipal node and a provincial node. And the number of target service deployments on different target nodes can be different.

[0063] Optionally, the deployment policy file records the administrative coding information of the target geographical area, the IP address information of the target node, and the number of deployments of the target service on the target node. The deployment module 102 is specifically configured to:

[0064] According to the administrative coding information of the target geographical area and the IP address information of the target node, deploy the target service to the target node according to the number of deployments.

[0065] The deployment module 102 can locate the position of the target node according to the administrative coding information of the target geographical area and the IP address information of the target node, so as to deploy the target service to the target node. The deployment module 102 can deploy the container image of the target service to the target node according to the number of deployments. In this embodiment, the deployment module 102 sends the container image of the target service and the template file of the container image to the target node, and the target node completes the deployment of the container image according to the template file.

[0066] The scheduling module 103 is configured to: after receiving the first access request sent by the client, perform scheduling control on the first access request according to the geographical area where the first access request comes from and the scheduling rules recorded in the scheduling rule file.

[0067] In this embodiment, the scheduling rules recorded in the scheduling rule file may be in the following form: the public network access IP address of the target node, and the public network access IP address of the target node corresponds to a number of geographical area identification information. After receiving the first access request, the scheduling module 103 can identify the geographical area identification information of the geographical area where the first access request comes from. If the geographical area identification information of the geographical area where the first access request comes from matches one of the geographical area identification information corresponding to the public network access IP address of the target node, the scheduling module 103 schedules the first access request to the target node. The above-mentioned geographical area identification information may be an administrative code or an identification code of a geographical area. When the geographical area identification information is an administrative code, it can be used for cross-regional hierarchical traffic scheduling. The application scenario where the geographical area identification information is the identification code of a geographical area is that a specific geographical area, such as a county, can be divided into several sub-areas, and the sub-areas have different identification codes, and the first access request is scheduled to the target node by identifying these identification codes.

[0068] The technical effects of this embodiment are as follows: The scheduling policies recorded in the scheduling policy file can be flexibly configured according to the different business requirements of the target service, and can better meet the traffic scheduling requirements of actual business compared with the prior art. Moreover, since the scheduling policy file can set the target geographical area to which the access request is scheduled to a geographical area level different from the geographical area where the access request comes from. For example, the target geographical area is set to a provincial administrative region, and the source geographical area is set to a municipal administrative region, so that cross-geographical area level traffic scheduling can be achieved. However, due to the lack of configuration of the corresponding scheduling policy file in the prior art, cross-geographical area level traffic scheduling cannot be achieved. The traffic scheduling system parses and generates a deployment policy file according to the pre-configured scheduling policy file. Since the deployment policy file records the target nodes to which the target service needs to be deployed, the deployment module 102 can accurately and efficiently deploy the target service to the required area according to the deployment policy file, so that the deployment location of the target service can meet the business requirements.

[0069] In a possible embodiment of the present application, the traffic scheduling rule file records: the public network access IP address information of the target node, and a plurality of target administrative coding information corresponding to the public network access IP address information of the target node. The deployment module 102 is further configured to:

[0070] Store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node into the scheduling module 103. Optionally, the scheduling module 103 includes a DNS server. Specifically, the deployment module 102 is configured to: store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node into the DNS server.

[0071] In this embodiment, a method for the scheduling module to perform scheduling control on the first access request according to the traffic scheduling rule file is provided. The specific execution subject of this method can be the above-mentioned DNS server. Figure 4 It is a flowchart of a method for the scheduling module to perform scheduling control on the first access request according to the traffic scheduling rule file provided by an embodiment of the present application. As Figure 4 shown, this method includes:

[0072] S401. After receiving the first access request sent by the client, obtain the exit IP address information of the first access request;

[0073] S402. Determine the administrative coding of the geographical area where the first access request comes from according to the exit IP address information;

[0074] S403. Check whether the administrative coding of the source geographical area matches one of the target administrative codings. If so, schedule the first access request to the target node.

[0075] In step S403, if the scheduling module 103 identifies that one of the administrative codes of the source geographical area matches the target administrative code, it sends the public network access IP address information and port number information of the target node to the client, thereby completing the scheduling of the first access request to the target node.

[0076] In this embodiment, the traffic scheduling rule file records the public network access IP address information of the target node and several target administrative code information corresponding to the public network access IP address information of the target node. After storing the traffic scheduling rule file in the scheduling module 103, the scheduling module 103 can, according to the traffic scheduling rules recorded in the traffic scheduling rule file, identify the administrative code of the geographical area where the first access request originates after receiving the first access request. If the administrative code of the geographical area where the first access request originates matches one of the target administrative codes, the first access request is scheduled to the target node.

[0077] The traffic scheduling rules recorded in the traffic scheduling rule file match the above-mentioned preset scheduling strategy. For example, if the above-mentioned preset scheduling strategy is to schedule access requests from different counties in the same city to the municipal node, the traffic scheduling rules recorded in the traffic scheduling rule file are: the public network access IP address information of the municipal target node and several county-level administrative codes corresponding to the public network access IP address information of the municipal target node. When a first access request is sent from a county under the city, the egress IP address information of the first access request can be identified, and the county-level administrative code is identified from the egress IP address information. If it matches one of the several county-level administrative codes in the traffic scheduling rules, the first access request is scheduled to the municipal node. Different scheduling strategy files correspond to different traffic scheduling rules. Through the above example, it can be shown that in this embodiment, the scheduling module 103 can flexibly schedule the first access request according to the preset scheduling strategy file.

[0078] In a possible embodiment of the present application, a method for a scheduling module to schedule and control microservice access requests according to a traffic scheduling rule file is provided. The specific execution entity of this method can be a DNS server. Figure 5 It is a flowchart of a method for a scheduling module to schedule and control microservice access requests according to a traffic scheduling rule file provided by an embodiment of the present application. As Figure 5 shown, the method includes:

[0079] S501. After receiving the microservice access request sent by the client, obtain the target access domain name information of the microservice access request according to the microservice access request;

[0080] Specifically, the target access domain name information of the microservice access request is the domain name information of the microservice to be accessed by the microservice access request.

[0081] S502. If the target access domain name information matches the domain name information of the target service, determine the microservice access request as the first access request;

[0082] It should be noted that the deployment module 102 can store the domain name information of the target service, such as the alias domain name information, in the DNS server, so that the DNS server can identify the target access domain name information of the microservice access request according to the domain name information of the target service.

[0083] S503. Obtain the egress IP address information of the first access request;

[0084] S504. Determine the administrative code of the geographical area where the first access request originates according to the egress IP address information;

[0085] S505. Verify whether the administrative code of the source geographical area matches one of the administrative codes in the target administrative codes. If so, schedule the first access request to the target node.

[0086] In step S505, if the scheduling module 103 identifies that the administrative code of the source geographical area matches one of the administrative codes in the target administrative codes, it sends the public network access IP address information and port number information of the target node to the client, thereby completing the scheduling of the first access request to the target node.

[0087] Through the above method in this embodiment, the technical problem of identifying the microservice access request sent by the client as the first access request for accessing the target service is specifically solved.

[0088] In a possible embodiment of the present application, the target node includes a first target node and a second target node. The traffic scheduling rule file records: the public network access IP address information of the first target node, the public network access IP address information of the second target node, and several first target administrative code information corresponding to the public network access IP address information of the first target node. The deployment module 102 is further configured to:

[0089] Store the public network access IP address information of the first target node, the public network access IP address information of the second target node, the first target administrative code information, the port number information of the target service deployed on the first target node, and the port number information of the target service deployed on the second target node in the scheduling module 103. In a specific application scenario, the first target node can be the target node for regular scheduling, and the second target node can be the redundant node. Refer to Figure 2 , the first target node can be the municipal-level node, and the second target node can be the provincial-level node.

[0090] In this embodiment, optionally, the scheduling module 103 is specifically configured to:

[0091] If the administrative code of the source geographical area matches one of the administrative codes in the first target administrative code, determine whether there is a fault in the target service deployed on the first target node:

[0092] If so, send the public network access IP address information of the second target node and the port number information of the target service deployed on the second target node to the client;

[0093] If not, send the public network access IP address information of the first target node and the port number information of the target service deployed on the first target node to the client.

[0094] In this embodiment, the function executed by the scheduling module 103 can be executed by the above DNS server. By adding the step of determining whether there is a fault in the target service deployed on the first target node, this embodiment realizes that when the target service of the first target node fails and cannot provide services, the first access request is scheduled to the redundant node, improving the stability of the service.

[0095] It should be noted that, without special instructions, in each embodiment of the present application, each functional unit / module can be integrated in one unit / module, or each unit / module can exist physically alone, or two or more units / module can be integrated together. The above integrated unit / module can be implemented in the form of hardware or in the form of a software program module.

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

[0097] When an 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, in essence, 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. This computer software product is stored in a memory and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs.

[0098] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as within the scope described in this specification.

[0099] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include the common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and the embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0100] It should be understood that the present application is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A traffic scheduling system, characterized in that, The system includes: A parsing module, configured to: Parse the scheduling policy file of the target service to generate a deployment policy file of the target service and a traffic scheduling rule file. The scheduling policy file records a scheduling policy for scheduling a first access request to the target service to a target geographical area according to the geographical area of the source of the first access request to the target service. The deployment policy file records a deployment policy for deploying the target service to a target node corresponding to the target geographical area. The traffic scheduling rule file records a scheduling rule for scheduling the first access request to the target node according to the geographical area of the source of the first access request; A deployment module, configured to: After deploying the target service to the target node according to the deployment policy file, store the traffic scheduling rule file in the scheduling module; The scheduling module is configured to: After receiving the first access request sent by the client, perform scheduling control on the first access request according to the geographical area of the source of the first access request and the scheduling rule recorded in the scheduling rule file.

2. The system according to claim 1, characterized in that The deployment policy file records the administrative coding information of the target geographical area, the IP address information of the target node, and the deployment quantity of the target service on the target node. Specifically, the deployment module is configured to: Deploy the target service to the target node according to the administrative coding information of the target geographical area and the IP address information of the target node according to the deployment quantity.

3. The system according to claim 2, wherein Specifically, the deployment module is configured to: Deploy the container image of the target service to the target node according to the deployment quantity.

4. The system according to claim 1, wherein The traffic scheduling rule file records the public network access IP address information of the target node and a plurality of target administrative coding information corresponding to the public network access IP address information of the target node. The deployment module is further configured to: Store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node in the scheduling module.

5. The system according to claim 4, characterized in that, Specifically, the scheduling module is configured to: After receiving the first access request sent by the client, obtain the egress IP address information of the first access request; Determine the administrative coding of the geographical area of the source of the first access request according to the egress IP address information; Verify whether the administrative coding of the source geographical area matches one of the target administrative codings. If so, schedule the first access request to the target node.

6. The system according to claim 5, wherein Specifically, the scheduling module is configured to: If the administrative coding of the source geographical area matches one of the target administrative codings, send the public network access IP address information of the target node and the port number information to the client.

7. The system according to claim 6, wherein The target nodes include a first target node and a second target node. The traffic scheduling rule file records: the public network access IP address information of the first target node, the public network access IP address information of the second target node, and several first target administrative coding information corresponding to the public network access IP address information of the first target node. The deployment module is further configured to: Store the public network access IP address information of the first target node, the public network access IP address information of the second target node, the first target administrative coding information, the port number information of the target service deployed on the first target node, and the port number information of the target service deployed on the second target node into the scheduling module.

8. The system according to claim 7, wherein The scheduling module is specifically configured to: If the administrative coding of the source geographical area matches one of the administrative codings in the first target administrative coding, determine whether the target service deployed on the first target node has a fault: If so, send the public network access IP address information of the second target node and the port number information of the target service deployed on the second target node to the client; If not, send the public network access IP address information of the first target node and the port number information of the target service deployed on the first target node to the client.

9. The system according to claim 4, wherein The scheduling module includes a DNS server. The deployment module is specifically configured to: store the public network access IP address information of the target node, the target administrative coding information, and the port number information of the target service deployed on the target node into the DNS server.

10. The system according to any one of claims 1-9, characterized in that, The scheduling module is further configured to: After receiving the microservice access request sent by the client, obtain the target access domain name information of the microservice access request according to the microservice access request; If the target access domain name information matches the domain name information of the target service, determine the microservice access request as the first access request.

Images