Traffic control method, device, system, electronic device, and storage medium

By working together with the policy server and the traffic feedback server, abnormal nodes were identified and replaced, which solved the problem that the DNS server could not accurately control the distribution of node traffic and achieved the expected distribution of traffic.

CN116260768BActive Publication Date: 2026-04-17BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD
Filing Date
2021-12-10
Publication Date
2026-04-17

AI Technical Summary

Technical Problem

DNS servers cannot accurately control node traffic allocation, resulting in a significant discrepancy between traffic allocation and expectations.

Method used

The policy server determines the initial policy based on the baseline traffic, and the traffic feedback server monitors for traffic anomalies and replaces abnormal nodes until the traffic is distributed as expected.

Benefits of technology

This improves the accuracy of DNS server traffic control at each node in the target line, ensuring that traffic is allocated as expected.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116260768B_ABST
    Figure CN116260768B_ABST
Patent Text Reader

Abstract

This application relates to a flow control method, apparatus, system, electronic device, and storage medium, applied in the field of flow control technology. The method includes: determining an initial policy based on a baseline flow in a target line; using the initial policy as a target policy; sending the target policy to a Domain Name System (DNS) server; sending the target policy to a flow feedback server, so that if the flow feedback server determines that there is a flow anomaly based on the current flow monitoring result corresponding to the node and the target flow, it sends a first flow anomaly result to a policy server; if the first flow anomaly result is received, determining the abnormal node in the target line based on the first flow anomaly result; replacing the abnormal node in the initial policy with the first target node to obtain the target policy, and returning to the step of sending the target policy to the DNS server, until there is no flow anomaly. This application can improve the accuracy of flow control by the DNS server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of flow control technology, and in particular to a flow control method, apparatus, system, electronic device and storage medium. Background Technology

[0002] In the implementation of traffic coverage for nodes in a network using a DNS (Domain Name System) server, the DNS server controls the traffic of each node to ensure that the traffic is distributed as expected. However, in some cases, the traffic distribution to each node deviates significantly from the expected distribution, causing the DNS server to be unable to accurately control the traffic of each node. Summary of the Invention

[0003] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this application provides a flow control method, apparatus, system, electronic device and storage medium.

[0004] According to a first aspect of this application, a flow control method is provided, applied to a policy server, the method comprising:

[0005] An initial strategy is determined based on the baseline traffic in the target line, wherein the initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node;

[0006] The initial strategy is taken as the target strategy;

[0007] The target policy is sent to the Domain Name System (DNS) server so that the DNS server can control the flow of the node according to the target policy;

[0008] The target policy is sent to the traffic feedback server, so that the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, and sends the first traffic anomaly result to the policy server.

[0009] If the first traffic anomaly result is received, the abnormal node in the target line is determined based on the first traffic anomaly result;

[0010] Replace the abnormal node in the initial strategy with the first target node to obtain the target strategy, and return to the step of sending the target strategy to the domain name system server until there is no traffic abnormality.

[0011] Optionally, after determining the abnormal node in the target line based on the first traffic anomaly result, the method further includes:

[0012] Obtain the current traffic in the target line;

[0013] If the current traffic in the target line is greater than or equal to the baseline traffic, execute the step of replacing the abnormal node in the initial strategy with the first target node;

[0014] If the current traffic in the target line is less than the baseline traffic, the abnormal node in the initial strategy is deleted to obtain the first strategy;

[0015] The first policy is sent to the Domain Name System (DNS) server so that the DNS server performs traffic control on the node according to the first policy.

[0016] The first policy is sent to the traffic feedback server, so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy, it will send the second traffic anomaly result to the policy server.

[0017] If the second traffic anomaly result is received, add a second target node to the first strategy to obtain the target strategy, and return to the step of sending the target strategy to the domain name system server until there is no more traffic anomaly.

[0018] Optionally, determining the abnormal node in the target line based on the first traffic anomaly result includes:

[0019] If the first traffic anomaly result includes the first traffic ratio of the current traffic monitoring result corresponding to each node in the target strategy, determine the second traffic ratio of the target traffic corresponding to each node in the target strategy;

[0020] Based on the first flow ratio and the second flow ratio, abnormal nodes in the target line are determined.

[0021] Optionally, determining abnormal nodes in the target line based on the first traffic ratio and the second traffic ratio includes:

[0022] For each node in the target line, a first traffic percentage of the node is determined based on the first traffic ratio.

[0023] The second traffic percentage of the node is determined based on the second traffic ratio.

[0024] If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is determined to be a first type of abnormal node; wherein, the first threshold is greater than 0, or,

[0025] If the difference between the first traffic percentage and the second traffic percentage is less than a second threshold, the node is determined to be a second type of abnormal node, wherein the second threshold is less than 0.

[0026] Optionally, the service capacity of the first target node is greater than the service capacity of the first type of abnormal node; or,

[0027] The network quality of the first target node is higher than that of the second type of abnormal node.

[0028] Optionally, determining the initial strategy based on the baseline traffic in the target line includes:

[0029] The number of nodes allocated in the target line is determined based on the baseline traffic in the target line.

[0030] Based on the baseline traffic and the service capabilities of each node, the target traffic corresponding to each node is determined.

[0031] Optionally, the current traffic monitoring result is obtained by the traffic monitoring server and sent to the traffic feedback server by the traffic monitoring server.

[0032] According to a second aspect of this application, a flow control device is provided, applied to a policy server, the device comprising:

[0033] An initial strategy determination module is used to determine an initial strategy based on the baseline traffic in the target line, wherein the initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node;

[0034] A target strategy determination module is used to use the initial strategy as the target strategy.

[0035] The first sending module is used to send the target policy to the domain name system server, so that the domain name system server performs traffic control on the node according to the target policy;

[0036] The second sending module is used to send the target policy to the traffic feedback server, so that the traffic feedback server, based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, determines that there is a traffic anomaly and sends the first traffic anomaly result to the policy server.

[0037] An abnormal node determination module is used to determine abnormal nodes in the target line based on the first traffic abnormality result if the first traffic abnormality result is received.

[0038] The target policy update module is used to replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return it to the first sending module until there is no traffic abnormality.

[0039] Optionally, the flow control device further includes:

[0040] The current traffic acquisition module is used to acquire the current traffic in the target line;

[0041] The target policy update module is specifically used to execute the step of replacing the abnormal node in the initial policy with the first target node if the current traffic in the target line is greater than or equal to the baseline traffic.

[0042] The first strategy determination module is used to delete the abnormal node in the initial strategy if the current traffic in the target line is less than the baseline traffic, thereby obtaining the first strategy;

[0043] The first sending module is further configured to send the first policy to the domain name system server, so that the domain name system server performs traffic control on the node according to the first policy;

[0044] The second sending module is further configured to send the first policy to the traffic feedback server, so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy, it will send a second traffic anomaly result to the policy server.

[0045] The target policy update module is further configured to, if the second traffic anomaly result is received, add a second target node to the first policy to obtain the target policy, and return it to the first sending module until there is no traffic anomaly.

[0046] Optionally, the abnormal node determination module is specifically used to determine a second traffic ratio of the target traffic corresponding to each node in the target policy if the first traffic abnormality result is received and the first traffic abnormality result includes a first traffic ratio of the current traffic monitoring result corresponding to each node in the target policy; and determine the abnormal node in the target line based on the first traffic ratio and the second traffic ratio.

[0047] Optionally, the abnormal node determination module is specifically used to determine abnormal nodes in the target line based on the first traffic ratio and the second traffic ratio through the following steps:

[0048] For each node in the target line, a first traffic percentage of the node is determined based on the first traffic ratio.

[0049] The second traffic percentage of the node is determined based on the second traffic ratio.

[0050] If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is determined to be a first type of abnormal node; wherein, the first threshold is greater than 0, or,

[0051] If the difference between the first traffic percentage and the second traffic percentage is less than a second threshold, the node is determined to be a second type of abnormal node, wherein the second threshold is less than 0.

[0052] Optionally, the service capacity of the first target node is greater than the service capacity of the first type of abnormal node; or,

[0053] The network quality of the first target node is higher than that of the second type of abnormal node.

[0054] Optionally, the initial strategy determination module is specifically used to determine the number of nodes allocated in the target line based on the baseline traffic in the target line; and to determine the target traffic corresponding to each node based on the baseline traffic and the service capacity of each node.

[0055] Optionally, the current traffic monitoring result is obtained by the traffic monitoring server and sent to the traffic feedback server by the traffic monitoring server.

[0056] According to a third aspect of this application, a flow control system is provided, the system comprising:

[0057] The policy server is used to determine an initial policy based on the baseline traffic in the target line, use the initial policy as the target policy, and send the target policy to the domain name system server and the traffic feedback server.

[0058] The initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node;

[0059] The Domain Name System server is used to control the flow of the node according to the target policy;

[0060] The traffic feedback server is used to send a first traffic anomaly result to the policy server when it is determined that there is a traffic anomaly, based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy.

[0061] The policy server is further configured to, if it receives the first traffic anomaly result, determine the abnormal node in the target line based on the first traffic anomaly result; replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return to the step of sending the target policy to the domain name system server, until there is no traffic anomaly.

[0062] Optionally, the policy server is further configured to obtain the current traffic in the target line; if the current traffic in the target line is greater than or equal to the baseline traffic, the step of replacing the abnormal node in the initial policy with the first target node is executed;

[0063] If the current traffic in the target line is less than the baseline traffic, the abnormal node in the initial strategy is deleted to obtain the first strategy, and the first strategy is sent to the domain name system server and the traffic feedback server.

[0064] The Domain Name System server is also used to perform traffic control on the node in accordance with the first strategy;

[0065] The traffic feedback server is also used to send a second traffic anomaly result to the policy server if it is determined that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy.

[0066] The policy server is further configured to, if it receives the second traffic anomaly result, add a second target node to the first policy to obtain a target policy, and return to the step of sending the target policy to the domain name system server, until there is no more traffic anomaly.

[0067] Optionally, the policy server is specifically configured to determine the abnormal nodes in the target line based on the first traffic anomaly result through the following steps:

[0068] If the first traffic anomaly result includes the first traffic ratio of the current traffic monitoring result corresponding to each node in the target strategy, determine the second traffic ratio of the target traffic corresponding to each node in the target strategy;

[0069] Based on the first flow ratio and the second flow ratio, abnormal nodes in the target line are determined.

[0070] Optionally, the policy server is specifically configured to determine abnormal nodes in the target line based on the first traffic ratio and the second traffic ratio through the following steps:

[0071] For each node in the target line, a first traffic percentage of the node is determined based on the first traffic ratio.

[0072] The second traffic percentage of the node is determined based on the second traffic ratio.

[0073] If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is determined to be a first type of abnormal node; wherein, the first threshold is greater than 0, or,

[0074] If the difference between the first traffic percentage and the second traffic percentage is less than a second threshold, the node is determined to be a second type of abnormal node, wherein the second threshold is less than 0.

[0075] Optionally, the service capability of the first target node is greater than that of the first type of abnormal node; or, the network quality of the first target node is higher than that of the second type of abnormal node.

[0076] Optionally, the policy server is specifically used to determine the initial policy based on the baseline traffic in the target line through the following steps:

[0077] The number of nodes allocated in the target line is determined based on the baseline traffic in the target line.

[0078] Based on the baseline traffic and the service capabilities of each node, the target traffic corresponding to each node is determined.

[0079] Optionally, the flow control system further includes:

[0080] A traffic monitoring server is used to monitor the traffic of nodes in the target policy, obtain the current traffic monitoring result, and send the current traffic monitoring result to the traffic feedback server.

[0081] According to a fourth aspect of this application, an electronic device is provided, comprising: a processor configured to execute a computer program stored in a memory, wherein the computer program, when executed by the processor, implements the method described in the first aspect.

[0082] According to a fifth aspect of this application, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0083] According to a sixth aspect of this application, a computer program product is provided that, when the computer program product is run on a computer, causes the computer to perform the method described in the first aspect.

[0084] The technical solution provided in this application has the following advantages compared with the prior art:

[0085] This application monitors traffic allocation via a traffic feedback server. When the traffic feedback server detects abnormal traffic, it sends the first abnormal traffic result to the policy server. The policy server can identify the abnormal nodes in the target line and replace them until the traffic anomalies cease. Since changing the node combination can achieve the desired traffic allocation, replacing the abnormal node with the first target node changes the node combination in the target line, ensuring that traffic is allocated to each node as expected, thus improving the accuracy of the DNS server's traffic control over each node in the target line. Attached Figure Description

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

[0087] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0088] Figure 1 A schematic diagram of a system architecture for an exemplary application environment that can be applied to the flow control method of the embodiments of this application is shown;

[0089] Figure 2 This is a flowchart of a flow control method in an embodiment of this application;

[0090] Figure 3 This is another flowchart of the flow control method in the embodiments of this application;

[0091] Figure 4 This is a schematic diagram of a flow control device in one embodiment of this application;

[0092] Figure 5 This is a schematic diagram of a flow control system in one embodiment of this application;

[0093] Figure 6 This is a schematic diagram of the structure of an electronic device in an embodiment of this application. Detailed Implementation

[0094] To better understand the above-mentioned objectives, features, and advantages of this application, the solution of this application will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.

[0095] Many specific details are set forth in the following description in order to provide a full understanding of this application, but this application may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some embodiments of this application, and not all embodiments.

[0096] Figure 1 A schematic diagram of a system architecture for an exemplary application environment that can be applied to the flow control method of the embodiments of this application is shown.

[0097] like Figure 1 As shown, the system architecture 100 may include a policy server 101, a traffic feedback server 102, a traffic monitoring server 103, a DNS server 104, and nodes 105, 106, 107, and 108 in the target line, as well as the network (in... Figure 1 (Not shown in the diagram). The network serves as a medium for providing communication links between policy server 101 and DNS server 104, between policy server 101 and traffic feedback server 102, between traffic feedback server 102 and traffic monitoring server 103, and between DNS server 104 and nodes 105, 106, 107, and 108. The network can include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0098] It should be understood that Figure 1 The number of policy servers, traffic feedback servers, traffic monitoring servers, DNS servers, and nodes shown is merely illustrative. Depending on implementation needs, any number of policy servers, traffic feedback servers, traffic monitoring servers, DNS servers, and nodes can be used. For example, policy server 101 could be a server cluster composed of multiple servers.

[0099] The traffic control method provided in this application embodiment is generally executed by the policy server 101, and correspondingly, the traffic control device can be set in the policy server 101. For example, the policy server 101 can determine an initial policy based on the baseline traffic in the target line and send the initial policy to the DNS server 104. The DNS server 104 can perform traffic control on nodes 105, 106, 107, and 108 in the target line according to the initial policy. The traffic monitoring server 103 can monitor the traffic of nodes 105, 106, 107, and 108 in real time and send the current traffic monitoring results to the traffic feedback server 102. The traffic feedback server 102 determines whether there is a traffic anomaly based on the initial policy sent by the policy server 101 and the current traffic monitoring results sent by the traffic monitoring server 103. If there is a traffic anomaly, the first traffic anomaly result is sent to the policy server 101.

[0100] Based on the first traffic anomaly result, policy server 101 identifies the abnormal node in the target line. Assuming the abnormal node is node 107, it can be replaced with another node. Subsequently, traffic monitoring server 103 monitors the traffic of nodes 105, 106, 108, and other nodes in real time, obtaining the current traffic monitoring result, and sends it to traffic feedback server 102. Traffic feedback server 102 further determines whether there is a traffic anomaly. If no traffic anomaly is found, the process ends; if a traffic anomaly still exists, the process continues to replace nodes until no further anomalies are found. Through this method, the traffic of each node in the target line can be made to meet expectations, improving the accuracy of traffic control for each node.

[0101] The flow control method of this application embodiment will be described in detail below.

[0102] See Figure 2 , Figure 2 This is a flowchart of a flow control method in an embodiment of this application, applied to a policy server, and may include the following steps:

[0103] Step S210: Determine the initial strategy based on the baseline traffic in the target line.

[0104] In this embodiment, the target line can be a line belonging to a specific operator in a certain region, for example, the target line is a line belonging to operator B in province A. The baseline traffic in the target line can be the highest traffic volume of the target line in the most recent historical time period. Since traffic volume usually varies across different time periods, the baseline traffic volume corresponding to different time periods will also be different, and correspondingly, the initial strategy for different time periods will also be different.

[0105] The initial strategy includes the number of nodes allocated in the target line and the target traffic for each node. The nodes allocated in the target line can be IDC (Internet Data Center) nodes or data center nodes.

[0106] Optionally, the number of nodes to be allocated on the target line can be determined first based on the baseline traffic. Then, based on the baseline traffic and the service capacity of each node, the target traffic for each node can be determined. It's understandable that the higher the baseline traffic value, the more nodes can be allocated. A node's service capacity is an inherent attribute; the higher the service capacity, the more traffic it can handle. Therefore, after determining the number of nodes, the target traffic for each node is determined based on its service capacity.

[0107] Assuming the base traffic is 10,000 IP (Internet Protocol) addresses, and the nodes in the target line are Node 1, Node 2, Node 3, and Node 4, with corresponding service capacities of 2G, 4G, 6G, and 8G respectively, then the target traffic for Node 1, Node 2, Node 3, and Node 4 can be 1,000 IP addresses, 2,000 IP addresses, 3,000 IP addresses, and 4,000 IP addresses respectively.

[0108] Step S220: Use the initial policy as the target policy.

[0109] In this embodiment of the application, the target strategy is the loop variable in the following loop process. Here, the initial strategy is used as the target strategy to assign an initial value to the loop variable.

[0110] Step S230: Send the target policy to the Domain Name System (DNS) server so that the DNS server can perform traffic control on the node according to the target policy.

[0111] After determining the target policy, it can be sent to the Domain Name System (DNS) server, which can then control the traffic of the nodes according to the policy. In most cases, traffic is distributed based on the number of DNS IPs; for example, the traffic ratio for nodes 1, 2, 3, and 4 is 1:2:3:4. However, in some situations (such as network anomalies), the traffic ratio between nodes can be severely unbalanced; for example, the traffic ratio for nodes 1, 2, 3, and 4 is 7:1:1:1. Therefore, in this embodiment, a traffic feedback server can be used to assist the DNS server in controlling the traffic of each node.

[0112] Step S240: The target policy is sent to the traffic feedback server so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, it will send the first traffic anomaly result to the policy server.

[0113] The policy server can send target policies to the traffic feedback server, enabling the traffic feedback server to monitor for any abnormal traffic. Optionally, the current traffic monitoring results corresponding to the nodes in the target policy can be obtained by the traffic monitoring server and then sent to the traffic feedback server. Alternatively, the traffic feedback server itself can monitor the traffic of each node to obtain the current traffic monitoring results.

[0114] The traffic feedback server can determine whether there is traffic anomaly based on the current traffic monitoring results corresponding to the nodes in the target policy, and the target traffic corresponding to the nodes in the target policy. For example, based on the target traffic corresponding to each node, the traffic ratio of each node can be determined. Based on this traffic ratio and the total traffic actually monitored, the expected traffic for each node can be obtained. Comparing the expected traffic with the current traffic monitoring results actually monitored yields the difference between the two. The larger the difference, the more likely there is a traffic anomaly.

[0115] Optionally, if there are nodes with a non-zero difference value, traffic anomalies can be considered to exist. Alternatively, if there are nodes with a difference value to total traffic ratio greater than a preset threshold, traffic anomalies can also be considered to exist. The traffic feedback server can send the current traffic monitoring results for all nodes with non-zero differences to the policy server, or it can send the current traffic monitoring results for nodes with a larger difference value to total traffic ratio to the policy server. Alternatively, the traffic feedback server can also send the ratio of the current traffic monitoring results for each node to the policy server. If no traffic anomalies are found, the traffic feedback server can leave it alone, and the process ends.

[0116] Step S250: If a first traffic anomaly result is received, determine the abnormal node in the target line based on the first traffic anomaly result.

[0117] In cases of abnormal traffic, it is usually caused by a subset of nodes. Therefore, based on the initial abnormal traffic results, the nodes causing the abnormal traffic, i.e., the abnormal nodes, can be identified.

[0118] Optionally, if the first traffic anomaly result includes the first traffic ratio of the current traffic monitoring results for each node in the target policy, the second traffic ratio of the target traffic for each node in the target policy can be determined. Based on the first and second traffic ratios, the abnormal nodes in the target line are identified. That is, abnormal nodes are determined based on the actual and expected traffic ratios. If the first and second traffic ratios differ but are generally consistent, the traffic anomaly can be considered within an acceptable range, and the policy server may not take any action. For example, if the first traffic ratio for nodes one, two, three, and four is 3:4:6:7, and the second traffic ratio is 1:2:3:4, the policy server can further determine that there are no abnormal nodes and no action is required.

[0119] If the first flow ratio and the second flow ratio differ significantly, an abnormal node can be considered to exist. For example, the first flow ratio of nodes one, two, three, and four is 7:1:1:1, and the second flow ratio is 1:2:3:4. Since the flow corresponding to node one is significantly higher than expected, it can be determined that the flow imbalance among the four nodes is caused by node one.

[0120] Optionally, abnormal nodes in the target line can be identified in the following ways:

[0121] For each node in the target line, a first traffic percentage is determined based on a first traffic ratio, which refers to the ratio of the node's current traffic monitoring result to the total traffic. A second traffic percentage is determined based on a second traffic ratio, which refers to the expected traffic percentage. If the difference between the first and second traffic percentages is greater than a first threshold, it indicates that the node's traffic is significantly higher than expected, and the node is identified as a first-type abnormal node; where the first threshold is greater than 0. Alternatively, if the difference between the first and second traffic percentages is less than the second threshold, it indicates that the node's traffic is significantly lower than expected, and the node is identified as a second-type abnormal node; where the second threshold is less than 0.

[0122] In step S260, the abnormal node in the initial strategy is replaced with the first target node to obtain the target strategy, and the process returns to step S230 until there is no more abnormal traffic.

[0123] In practical traffic shaping experience, changing the node combination can achieve a proportional scheduling effect when traffic is not allocated proportionally. Therefore, abnormal nodes can be replaced with the primary target node, and the traffic to each node can be controlled by adjusting the node combination in the target line. After replacing the node, the above process is repeated until the traffic to each node in the target line meets expectations. During this loop, the target strategy is continuously updated as the loop variable. This loop can be executed once or multiple times; that is, the node replacement operation can be performed once or multiple times.

[0124] Optionally, when replacing a first-type abnormal node, the service capacity of the first target node can be greater than that of the first-type abnormal node. This avoids being unable to handle high traffic and improves the overall service capacity of the target line. Alternatively, when replacing a second-type abnormal node, since the traffic of the second-type abnormal node is significantly lower than expected, the network quality of the first-type abnormal node may be poor. Therefore, the network quality of the first target node can be higher than that of the second-type abnormal node. For example, the first target node may have a better network environment, lower latency, and lower packet loss rate. In addition, when selecting the first target node, the node's coverage relationship can also be considered, i.e., whether there is any previous caching on the node. If there is no caching, the node can be used as the first target node.

[0125] The traffic control method in this application can monitor traffic allocation through a traffic feedback server. When the traffic feedback server detects traffic anomalies, it sends a first traffic anomaly result to a policy server. The policy server can identify abnormal nodes in the target line and replace them until the traffic anomalies cease. Since changing the node combination can achieve the effect of allocating traffic as expected, replacing abnormal nodes with the first target node can change the node combination in the target line, ensuring that the traffic of each node in the target line is allocated as expected, thus improving the accuracy of the DNS server's traffic control over each node in the target line. When replacing nodes, nodes with better service capabilities or better network quality can be selected to improve the overall service capability of the target line.

[0126] See Figure 3 , Figure 3 This is another flowchart of the flow control method in the embodiments of this application, applied to a policy server, and may include the following steps:

[0127] Step S302: Determine the initial strategy based on the baseline traffic in the target line. The initial strategy includes the number of nodes allocated in the target line and the target traffic corresponding to each node.

[0128] Step S304: Use the initial policy as the target policy.

[0129] Step S306: Send the target policy to the Domain Name System (DNS) server so that the DNS server can perform traffic control on the node according to the target policy.

[0130] Step S308: The target policy is sent to the traffic feedback server so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, it will send the first traffic anomaly result to the policy server.

[0131] Step S310: If a first traffic anomaly result is received, determine the abnormal node in the target line based on the first traffic anomaly result.

[0132] It should be noted that steps S302 to S310 above are the same as... Figure 2 Steps S210 to S250 are the same in the embodiment; see details below. Figure 2 The descriptions in the embodiments are sufficient and will not be repeated here.

[0133] Step S312: Obtain the current traffic in the target line and determine whether the current traffic is less than the baseline traffic.

[0134] In this embodiment of the application, the current traffic volume can also be used as a reference to determine how to change the node combination in the target line. For example, if the current traffic volume in the target line is greater than or equal to the baseline traffic volume, step S314 can be executed; if the current traffic volume in the target line is less than the baseline traffic volume, step S316 can be executed.

[0135] Step S314: Replace the abnormal node in the initial strategy with the first target node to obtain the target strategy, and return to step S306 until there is no more abnormal traffic.

[0136] Step S316: Delete the abnormal nodes in the initial strategy to obtain the first strategy.

[0137] Step S318: The first policy is sent to the Domain Name System (DNS) server so that the DNS server performs traffic control on the node according to the first policy.

[0138] Step S320: The first policy is sent to the traffic feedback server so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy, it will send the second traffic anomaly result to the policy server.

[0139] The processing steps S318 to S320 above are the same as Figure 2 Steps S230 to S240 in the embodiment are similar; see details below. Figure 2 The descriptions in the embodiments are sufficient and will not be repeated here.

[0140] Step S322: If a second traffic anomaly result is received, add a second target node to the first strategy to obtain the target strategy, and return to step S306 until there is no more traffic anomaly.

[0141] It should be noted that if the policy server receives a second traffic anomaly result from the traffic feedback server, since the abnormal node has already been deleted based on the initial policy, and traffic may change at different times, a new second target node can be added directly to ensure the service capacity of the target line. The selection method for the second target node is the same as that for the first target node. After adding the second target node, if traffic anomalies still exist, the abnormal node can be replaced.

[0142] The flow control method of this application embodiment, in the event of abnormal flow, can determine how to change the node combination in the target line by referring to the current flow in the target line. Specifically, compared with the baseline flow, if the current flow has not decreased, the abnormal node in the target line can be replaced; if the current flow has decreased, the abnormal node can be deleted first. If the abnormal flow still exists after deletion, a new node can be added. In this way, the node combination in the target line can be changed more flexibly without affecting the service of the target line, thereby improving the flexibility of flow control.

[0143] Corresponding to the above method embodiments, this application also provides a flow control device, see [link to relevant documentation]. Figure 4 The flow control device 400 includes:

[0144] The initial strategy determination module 410 is used to determine an initial strategy based on the baseline traffic in the target line. The initial strategy includes the number of nodes allocated in the target line and the target traffic corresponding to each node.

[0145] The target policy determination module 420 is used to use the initial policy as the target policy.

[0146] The first sending module 430 is used to send the target policy to the domain name system server so that the domain name system server can control the flow of the node according to the target policy;

[0147] The second sending module 440 is used to send the target policy to the traffic feedback server, so that the traffic feedback server, based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, determines that there is a traffic anomaly and sends the first traffic anomaly result to the policy server.

[0148] The abnormal node determination module 450 is used to determine the abnormal node in the target line based on the first traffic abnormality result if the first traffic abnormality result is received.

[0149] The target policy update module 460 is used to replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return to the first sending module to execute the step of sending the target policy to the domain name system server until there is no more traffic abnormality.

[0150] Optionally, the flow control device 400 also includes:

[0151] The current traffic acquisition module is used to acquire the current traffic in the target line;

[0152] The target policy update module is specifically used to replace the abnormal node in the initial policy with the first target node if the current traffic in the target line is greater than or equal to the baseline traffic.

[0153] The first strategy determination module is used to delete the abnormal nodes in the initial strategy if the current traffic in the target line is less than the baseline traffic, and obtain the first strategy.

[0154] The first sending module 430 is also used to send the first policy to the domain name system server so that the domain name system server performs flow control on the node in accordance with the first policy.

[0155] The second sending module 440 is further configured to send the first policy to the traffic feedback server, so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy, it will send the second traffic anomaly result to the policy server.

[0156] The target policy update module 460 is also used to add a second target node to the first policy if a second traffic anomaly result is received, obtain the target policy, and return to the first sending module until there is no more traffic anomaly.

[0157] Optionally, the abnormal node determination module 450 is specifically used to determine the second traffic ratio of the target traffic corresponding to each node in the target policy if a first traffic abnormality result is received, and the first traffic abnormality result includes the first traffic ratio of the current traffic monitoring result corresponding to each node in the target policy; and determine the abnormal node in the target line based on the first traffic ratio and the second traffic ratio.

[0158] Optionally, the abnormal node determination module 450 is specifically used to determine abnormal nodes in the target line based on a first flow ratio and a second flow ratio through the following steps:

[0159] For each node in the target line, determine the first traffic percentage of the node based on the first traffic ratio;

[0160] Determine the second traffic percentage of the node based on the second traffic ratio;

[0161] If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is identified as a first-type abnormal node; where the first threshold is greater than 0, or...

[0162] If the difference between the first traffic percentage and the second traffic percentage is less than the second threshold, the node is determined to be a second type of abnormal node, where the second threshold is less than 0.

[0163] Optionally, the service capacity of the first target node is greater than the service capacity of the first type of abnormal node; or,

[0164] The network quality of the first target node is higher than that of the second type of abnormal node.

[0165] Optionally, the initial strategy determination module is specifically used to determine the number of nodes allocated in the target line based on the baseline traffic in the target line; and to determine the target traffic corresponding to each node based on the baseline traffic and the service capacity of each node.

[0166] Optionally, the current traffic monitoring results are obtained by the traffic monitoring server and sent to the traffic feedback server.

[0167] The specific details of each module or unit in the above-mentioned device have been described in detail in the corresponding methods, so they will not be repeated here.

[0168] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0169] See Figure 5 , Figure 5 This is a schematic diagram of a flow control system in an embodiment of this application. The flow control system 500 includes:

[0170] Policy server 510 is used to determine an initial policy based on the baseline traffic in the target line, use the initial policy as the target policy, and send the target policy to domain name system server 520 and traffic feedback server 530.

[0171] The initial strategy includes: the number of nodes allocated in the target line and the target traffic for each node;

[0172] Domain Name System server 520 is used to control the flow of nodes according to the target policy;

[0173] Traffic feedback server 530 is used to send the first traffic anomaly result to policy server 510 when it is determined that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy.

[0174] The policy server 510 is also used to, if a first traffic anomaly result is received, determine the abnormal node in the target line based on the first traffic anomaly result; replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return to the step of sending the target policy to the domain name system server, until there is no more traffic anomaly.

[0175] Optionally, the policy server 510 is also used to obtain the current traffic in the target line; if the current traffic in the target line is greater than or equal to the baseline traffic, the step of replacing the abnormal node in the initial policy with the first target node is executed.

[0176] If the current traffic in the target line is less than the baseline traffic, the abnormal node in the initial policy is deleted to obtain the first policy, and the first policy is sent to the Domain Name System server 520 and the traffic feedback server 530.

[0177] Domain Name System server 520 is also used to perform traffic control on nodes according to the first policy;

[0178] The traffic feedback server 530 is also used to send a second traffic anomaly result to the policy server when it is determined that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy.

[0179] Policy server 510 is also used to add a second target node to the first policy if a second traffic anomaly result is received, obtain the target policy, and return to the step of sending the target policy to the domain name system server until there is no more traffic anomaly.

[0180] Optionally, the policy server 510 is specifically used to determine the abnormal nodes in the target line based on the first traffic anomaly result through the following steps:

[0181] If the first traffic anomaly result includes the first traffic ratio of the current traffic monitoring result corresponding to each node in the target policy, determine the second traffic ratio of the target traffic corresponding to each node in the target policy;

[0182] Based on the first flow ratio and the second flow ratio, identify the abnormal nodes in the target line.

[0183] Optionally, the policy server 510 is specifically used to determine abnormal nodes in the target line based on the first traffic ratio and the second traffic ratio through the following steps:

[0184] For each node in the target line, determine the first traffic percentage of the node based on the first traffic ratio;

[0185] Determine the second traffic percentage of the node based on the second traffic ratio;

[0186] If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is identified as a first-type abnormal node; where the first threshold is greater than 0, or...

[0187] If the difference between the first traffic percentage and the second traffic percentage is less than the second threshold, the node is determined to be a second type of abnormal node, where the second threshold is less than 0.

[0188] Optionally, the service capacity of the first target node is greater than that of the first type of abnormal node; or, the network quality of the first target node is higher than that of the second type of abnormal node.

[0189] Optionally, the policy server 510 is specifically used to determine the initial policy based on the baseline traffic in the target line through the following steps:

[0190] Determine the number of nodes to be allocated in the target line based on the baseline traffic in the target line;

[0191] Based on the baseline traffic and the service capabilities of each node, the target traffic for each node is determined.

[0192] Optionally, the flow control system 500 also includes:

[0193] The traffic monitoring server is used to monitor the traffic of nodes in the target policy, obtain the current traffic monitoring results, and send the current traffic monitoring results to the traffic feedback server.

[0194] In an exemplary embodiment of this application, an electronic device is also provided, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the flow control method described in this exemplary embodiment.

[0195] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. It should be noted that... Figure 6 The electronic device 600 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0196] like Figure 6 As shown, the electronic device 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for system operation. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0197] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a local area network (LAN) card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0198] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit 601, it performs the various functions defined in the apparatus of this application.

[0199] In this embodiment of the application, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the above-described flow control method.

[0200] It should be noted that the computer-readable storage medium shown in this application can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, radio frequency, etc., or any suitable combination thereof.

[0201] In this embodiment of the application, a computer program product is also provided, which, when run on a computer, causes the computer to execute the above-described flow control method.

[0202] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0203] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A flow control method, characterized in that, Applied to a policy server, the method includes: An initial strategy is determined based on the baseline traffic in the target line, wherein the initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node; The initial strategy is taken as the target strategy; The target policy is sent to the Domain Name System (DNS) server so that the DNS server can control the flow of the node according to the target policy; The target policy is sent to the traffic feedback server, so that the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, and sends the first traffic anomaly result to the policy server. If the first traffic anomaly result is received, the abnormal node in the target line is determined based on the first traffic anomaly result; Replace the abnormal node in the initial strategy with the first target node to obtain the target strategy, and return to the step of sending the target strategy to the domain name system server until there is no traffic abnormality.

2. The method according to claim 1, characterized in that, After determining the abnormal node in the target line based on the first traffic anomaly result, the method further includes: Obtain the current traffic in the target line; If the current traffic in the target line is greater than or equal to the baseline traffic, execute the step of replacing the abnormal node in the initial strategy with the first target node; If the current traffic in the target line is less than the baseline traffic, the abnormal node in the initial strategy is deleted to obtain the first strategy; The first policy is sent to the Domain Name System (DNS) server so that the DNS server performs traffic control on the node according to the first policy. The first policy is sent to the traffic feedback server, so that if the traffic feedback server determines that there is a traffic anomaly based on the current traffic monitoring result corresponding to the node in the first policy and the target traffic corresponding to the node in the first policy, it will send the second traffic anomaly result to the policy server. If the second traffic anomaly result is received, add a second target node to the first strategy to obtain the target strategy, and return to the step of sending the target strategy to the domain name system server until there is no more traffic anomaly.

3. The method according to claim 1 or 2, characterized in that, The step of determining the abnormal node in the target line based on the first traffic anomaly result includes: If the first traffic anomaly result includes a first traffic ratio of the current traffic monitoring results corresponding to each node in the target strategy, a second traffic ratio of the target traffic corresponding to each node in the target strategy is determined; wherein, the first traffic ratio of the current traffic monitoring results corresponding to each node in the target strategy is the ratio of the traffic values ​​of the current traffic monitoring of each node in the target strategy, and the second traffic ratio of the target traffic corresponding to each node in the target strategy is the ratio of the target traffic values ​​of each node in the target strategy. Based on the first flow ratio and the second flow ratio, abnormal nodes in the target line are determined.

4. The method according to claim 3, characterized in that, Determining abnormal nodes in the target line based on the first flow ratio and the second flow ratio includes: For each node in the target line, a first traffic percentage of the node is determined based on the first traffic ratio. The second traffic percentage of the node is determined based on the second traffic ratio. If the difference between the first traffic percentage and the second traffic percentage is greater than a first threshold, the node is determined to be a first type of abnormal node; wherein, the first threshold is greater than 0, or, If the difference between the first traffic percentage and the second traffic percentage is less than a second threshold, the node is determined to be a second type of abnormal node, wherein the second threshold is less than 0.

5. The method according to claim 4, characterized in that, The service capacity of the first target node is greater than the service capacity of the first type of abnormal node; or, The network quality of the first target node is higher than that of the second type of abnormal node.

6. The method according to claim 1, characterized in that, The step of determining the initial strategy based on the baseline traffic in the target line includes: The number of nodes allocated in the target line is determined based on the baseline traffic in the target line. Based on the baseline traffic and the service capabilities of each node, the target traffic corresponding to each node is determined.

7. The method according to claim 1, characterized in that, The current traffic monitoring result is obtained by the traffic monitoring server and sent to the traffic feedback server by the traffic monitoring server.

8. A flow control device, characterized in that, The apparatus, used in a policy server, includes: An initial strategy determination module is used to determine an initial strategy based on the baseline traffic in the target line, wherein the initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node; A target strategy determination module is used to use the initial strategy as the target strategy. The first sending module is used to send the target policy to the domain name system server, so that the domain name system server performs traffic control on the node according to the target policy; The second sending module is used to send the target policy to the traffic feedback server, so that the traffic feedback server, based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy, determines that there is a traffic anomaly and sends the first traffic anomaly result to the policy server. An abnormal node determination module is used to determine abnormal nodes in the target line based on the first traffic abnormality result if the first traffic abnormality result is received. The target policy update module is used to replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return it to the first sending module until there is no traffic abnormality.

9. A flow control system, characterized in that, The system includes: The policy server determines an initial policy based on the baseline traffic in the target line, uses this initial policy as the target policy, and sends the target policy to the Domain Name System server and the traffic feedback server. The initial strategy includes: the number of nodes allocated in the target line and the target traffic corresponding to each node; The Domain Name System server is used to control the flow of the node according to the target policy; The traffic feedback server is used to send a first traffic anomaly result to the policy server when it is determined that there is a traffic anomaly, based on the current traffic monitoring result corresponding to the node in the target policy and the target traffic corresponding to the node in the target policy. The policy server is further configured to, if it receives the first traffic anomaly result, determine the abnormal node in the target line based on the first traffic anomaly result; replace the abnormal node in the initial policy with the first target node to obtain the target policy, and return to the step of sending the target policy to the domain name system server, until there is no traffic anomaly.

10. An electronic device, characterized in that, include: A processor for executing a computer program stored in a memory, wherein the computer program, when executed by the processor, implements the steps of the method according to any one of claims 1-7.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1-7.

Citation Information

Patent Citations

  • Abnormal domain name determination method, abnormal flow processing method, device and system

    CN109951426A

  • Multi-target logistics scheduling method and device, logistics system and computer readable medium

    CN110097231A