Traffic transmission control method, apparatus, and system, device, storage medium, and program product

Abstract

Disclosed in embodiments of the present application are a traffic transmission control method, apparatus, and system, a device, a storage medium, and a program product. The method comprises: in response to a traffic transmission management request for an edge node device, obtaining a plurality of pieces of traffic metadata; grouping the plurality of pieces of traffic metadata to obtain a plurality of metadata groups; on the basis of a bandwidth upper limit value of the edge node device, determining bandwidth allocation data corresponding to each metadata group among the plurality of metadata groups, wherein the bandwidth allocation data comprises the maximum bandwidth and the minimum bandwidth; and generating a traffic transmission control instruction on the basis of the plurality of metadata groups and the bandwidth allocation data, and sending the traffic transmission control instruction to the edge node device, so that the edge node device controls data traffic transmitted to an electronic device.

Description

Traffic transmission control method, device, system, equipment, storage medium and program product

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on November 21, 2023, with application number 202311563804.8 and application name “Distributed cloud-based traffic transmission control method and related devices and systems”. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a flow transmission control method, apparatus, system, device, storage medium and program product.

[0003] Background of the Invention

[0004] Distributed cloud extends the capabilities of the central cloud, aiming to provide ubiquitous cloud computing services to meet the needs of local access for edge data processing, real-time computing, and other applications. Compared to the central cloud, the distributed cloud's usability in any location and flexible application scenarios dictate its lightweight, compact size. Compared to the high-bandwidth, dedicated lines used to interconnect central cloud nodes, distributed cloud nodes are connected via the lower-cost public network. Bandwidth resources can be purchased on demand, sufficient to meet most node needs.

[0005] However, the disadvantages of public network interconnection are also obvious. Due to the small bandwidth limit, burst traffic can easily lead to congestion in the transmission channel, and the data traffic of each system in the cloud node will randomly occupy the limited bandwidth resources, which can easily lead to the failure of timely transmission of important data.

[0006] Therefore, it is urgent to solve the technical problem of poor stability of cross-node traffic transmission in existing distributed cloud scenarios.

[0007] Summary of the Invention

[0008] To solve the above technical problems, the embodiments of the present application provide a flow transmission control method, device, system, electronic device, computer-readable storage medium and computer program product.

[0009] In one aspect, an embodiment of the present application provides a flow transmission control method, which is performed by an electronic device and includes:

[0010] In response to a traffic transmission management request for an edge node device, obtaining a plurality of traffic metadata;

[0011] Grouping the plurality of traffic metadata to obtain a plurality of metadata groups;

[0012] Determining bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device, the bandwidth allocation data including a maximum bandwidth and a minimum bandwidth; and

[0013] A flow transmission control instruction is generated according to the multiple metadata groups and the bandwidth allocation data, and the flow transmission control instruction is sent to the edge node device, so that the edge node device controls the data flow transmitted to the electronic device.

[0014] On the other hand, an embodiment of the present application provides a flow transmission control device, including:

[0015] A metadata acquisition module, configured to acquire a plurality of traffic metadata in response to a traffic transmission management request for an edge node device;

[0016] a grouping module, configured to group the plurality of traffic metadata to obtain a plurality of metadata groups;

[0017] a bandwidth allocation module, configured to determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to a bandwidth upper limit value of the edge node device, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; and

[0018] The transmission control module is used to generate a traffic transmission control instruction based on the multiple metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the edge node device so that the edge node device controls the data flow transmitted to the electronic device.

[0019] On the other hand, an embodiment of the present application further provides another flow transmission control method, which is performed by an electronic device and includes:

[0020] receiving a traffic transmission control instruction sent by a central node device, wherein the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth;

[0021] In response to the traffic transmission control instruction, transmitting the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group;

[0022] Obtaining a real-time congestion detection result of a traffic transmission channel between the central node device and the electronic device; and,

[0023] Based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, the data flow transmitted to the central node device is adjusted.

[0024] On the other hand, an embodiment of the present application further provides another flow transmission control device, including:

[0025] A control instruction receiving module is configured to receive a traffic transmission control instruction sent by a central node device, wherein the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth;

[0026] an initial transmission module, configured to transmit, in response to the traffic transmission control instruction, the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group;

[0027] A speed limit implementation module is used to obtain real-time congestion detection results of the traffic transmission channel between the central node device and the electronic device; and, based on the real-time congestion detection results and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, adjust the data traffic transmitted to the central node device.

[0028] On the other hand, an embodiment of the present application further provides another traffic transmission control system, including a central node device and an edge node device, wherein a metadata management module and a gateway controller are deployed on the central node device, and a rate limit implementation module is deployed on the edge node device, wherein:

[0029] The metadata management module is configured to, in response to a traffic transmission management request for an edge node device, obtain a plurality of traffic metadata; group the plurality of traffic metadata to obtain a plurality of metadata groups; and determine bandwidth allocation data corresponding to each of the plurality of metadata groups based on a bandwidth upper limit value of the edge node device, the bandwidth allocation data including a maximum bandwidth and a minimum bandwidth;

[0030] The gateway controller is configured to generate a traffic transmission control instruction according to the plurality of metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the speed limit implementation module;

[0031] The speed limit implementation module is used to, in response to the traffic transmission control instruction, transmit the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group; obtain the real-time congestion detection result of the traffic transmission channel between the central node device and the electronic device; and, based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, adjust the data traffic transmitted to the central node device.

[0032] On the other hand, an embodiment of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the steps in the traffic transmission control method as described above.

[0033] On the other hand, an embodiment of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor of a computer, the computer executes the steps in the traffic transmission control method as described above.

[0034] On the other hand, an embodiment of the present application provides a computer program product, including a computer program, which implements the steps in the traffic transmission control method described above when executed by a processor.

[0035] BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a schematic diagram of a framework for cross-node traffic transmission in a distributed cloud scenario proposed in this application;

[0037] FIG2 is a schematic diagram of the processing flow of the metadata management module in the framework shown in FIG1 ;

[0038] FIG3 is a schematic diagram of the processing flow of the speed limit implementation module in the framework shown in FIG1 ;

[0039] FIG4 is a flow chart of a flow transmission control method shown in an exemplary embodiment of the present application;

[0040] FIG5 is a flow chart of a flow transmission control method shown in another exemplary embodiment of the present application;

[0041] FIG6 is a schematic diagram of the edge node device proposed in this application sequentially increasing the transmission bandwidth corresponding to each metadata group;

[0042] FIG7 is a block diagram of a flow transmission control device shown in an exemplary embodiment of the present application;

[0043] FIG8 is a block diagram of a flow transmission control device shown in another exemplary embodiment of the present application;

[0044] FIG9 shows a schematic structural diagram of an electronic device suitable for implementing the embodiments of the present application.

[0045] Implementation Method

[0046] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0047] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0048] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0049] In this application, "plurality" refers to two or more. "And / or" describes the relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0050] The terms "first," "second," "third," and "fourth," etc., in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. The terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0051] In the field of cloud computing, a distributed cloud is an architectural model based on the concepts of distributed computing and cloud computing. It distributes computing, storage, and network resources across different physical or virtual nodes, enabling them to work together over a network to provide high-performance, high-availability, and high-scalability services. In daily use, data transmission across cloud nodes is almost ubiquitous due to the functional and resource limitations of individual distributed cloud nodes.

[0052] However, existing cross-cloud node database transmission solutions also have the following problems:

[0053] First, channel congestion is likely to occur

[0054] The lack of bandwidth redundancy in edge node devices has become a bottleneck for cross-node data transmission. In addition, there are many systems in the cloud node, and large-scale transmission needs may occur at any time. The large-scale transmission tasks initiated by multiple systems at the same time will exhaust bandwidth resources and cause channel congestion, resulting in a series of problems such as the inability to issue control commands and loss of connection with cloud nodes. The reliability of cloud services is reduced, which in turn affects customer business.

[0055] Second, disorderly competition for bandwidth resources

[0056] In existing distributed cloud cross-node traffic transmission solutions, high-priority critical traffic such as "customer services" and "high-availability management" is mixed with lower-priority less important traffic such as "node upgrades" and "file pulls." These traffic types compete for the limited bandwidth resources of edge node devices. While in most cases, traffic demand is low, and these two types of traffic can be staggered to avoid interfering with each other, in scenarios with higher traffic demand, the lack of effective management mechanisms and random bandwidth allocation can prevent critical traffic from being transmitted in a timely and effective manner, resulting in a suboptimal product experience.

[0057] To solve the above problems, the technical solution of this application proposes to manage and control the public network bandwidth of edge node devices to avoid traffic out of control, thereby effectively improving the stability of cross-node traffic transmission in distributed cloud scenarios and improving product experience.

[0058] First, please refer to Figure 1, which is a schematic diagram of the framework for cross-node traffic transmission in the distributed cloud scenario proposed in this application. As can be seen from Figure 1, a complete cross-node traffic transmission link consists of three parts: edge node device 110 sending, public network speed-limited transmission, and central node device 120 processing. This application also sets a metadata management module 121 and a gateway controller 122 in the central node device 120, and sets a speed limit implementation module 111 in the edge node device 110. These functional modules are used to implement traffic classification, optimize traffic transmission between cloud nodes, and improve system stability.

[0059] The following is an introduction to the framework shown in Figure 1:

[0060] The edge node device 110 sends data traffic first from the internal system of the edge node device 110, passes through the virtual router, and routes the data to any gateway according to the traffic five-tuple information (source IP, destination IP, source port, destination port, communication protocol). After the gateway receives the data, it completes the encryption, compression and other operations of the data in sequence, and finally delivers the data to the public network. The edge node device 110 has many internal systems. Generally, there are thousands of internal systems inside the edge node device 110. Each system may initiate a transmission request at any time. Therefore, overall, the traffic demand of the edge node device 110 is highly uncertain.

[0061] Public network speed-limited transmission means that the public network transmission capacity is provided by the public network operator, and the operator's bandwidth resources need to be purchased in advance. Due to cost constraints, the public network bandwidth of the edge node is generally low (about 50-100mbps). The data delivered to the public network by the traffic gateway is speed-limited by the operator, and some data packets are discarded and some are transmitted normally. The public network bandwidth resources of the central node device 120 are relatively sufficient (about 10Gbps) and can receive all the arriving data. Therefore, from the asymmetry of resources on both sides of the central node device 120 and the edge node device 110, it can be seen that the bottleneck of the entire transmission system is the public network bandwidth of the edge node device 110.

[0062] Processing by the central node device 120 means that after the public network transmission is completed, the data is received by the high-performance gateway of the central node device 120. The gateway sequentially completes operations such as decompression and decryption of the data to obtain the original data. Based on the destination IP and port in the data, the data is sent to different backend system modules. Each backend system module sends data back based on the processing results, or ends the entire transmission process.

[0063] The metadata management module is responsible for managing the basic information of traffic transmitted between cloud nodes. The processing flow of the metadata management module is shown in Figure 2 and includes the following steps:

[0064] S210 , the metadata management module 200 serves as a system management portal, provides a function for entering traffic metadata, and persists the entered traffic metadata in a database.

[0065] S220, when a certain edge node device needs to be managed, the system loads traffic metadata from the database, and groups and sorts each traffic in combination with the traffic control factor to obtain metadata groups sorted by priority.

[0066] S230 : Setting a bandwidth upper limit for each metadata group according to the bandwidth upper limit of the edge node device, thereby obtaining grouping control information of the metadata group.

[0067] S240: Encapsulate the group control information into a control command and send it to the rate limit implementation module on the edge node device.

[0068] It should be noted that, since the speed limit implementation module is deployed on the traffic gateway of the edge node device, FIG2 illustrates sending the control command to the traffic gateway.

[0069] The traffic metadata mentioned in the embodiments of the present application refers to a set of information necessary for traffic transmission control, such as routing information, traffic control factors, and the upper limit of bandwidth supported by each edge node device. Routing information is, for example, the aforementioned traffic quintuple information, namely, source IP, destination IP, source port, destination port, and communication protocol. The upper limit of bandwidth supported by each edge node device is also the maximum bandwidth supported by each edge node device.

[0070] Flow control factors are factors related to data traffic transmission control strategies. Each routing information has a corresponding flow control factor. For example, to ensure the stability of the data transmission system, high-priority traffic should be transmitted first, so priority can be used as a flow control factor. For another example, traffic transmission operations triggered by customers in the system should be more important than traffic transmission operations triggered automatically by the system, so the source of the operation can also be used as a flow control factor. Exemplary flow control factors include priority, timeliness level, operation source, and expected bandwidth.

[0071] The gateway controller manages the entire lifecycle of the traffic gateway on edge devices. Directly connected to the traffic gateway, the gateway controller receives control commands from the metadata management module and sends them to the rate limit implementation module. The gateway controller maintains a heartbeat alarm with the edge nodes, providing alerting capabilities and ensuring the availability of the rate limit module on the edge gateway.

[0072] The speed limit implementation module is responsible for executing the control command of the group speed limit. The processing flow of the speed limit implementation module is shown in Figure 3. The speed limit implementation module is deployed on the traffic gateway of the edge node device. As can be seen from Figure 3, when the speed limit implementation module is working,

[0073] S310, receiving a control command from the gateway controller and initializing its own configuration;

[0074] S320, executing the speed limit logic according to the control instruction;

[0075] S330, regularly detecting the congestion status of the transmission channel;

[0076] S340, determine whether congestion currently occurs. If so, execute S350 to dynamically adjust the upper speed limit of the group according to the congestion status; otherwise, further determine whether there is any remaining bandwidth. If so, execute S370 to allocate bandwidth to high-priority groups according to a quota.

[0077] The overall speed limit control strategy of the speed limit implementation module can be summarized as follows: increasing the speed limit upper limit under low load to improve overall efficiency; reducing the upper limit of low-priority traffic under high load to avoid congestion and improve the efficiency of important data transmission, thereby achieving overall stability of traffic transmission across cloud nodes.

[0078] It should be noted that the detailed process of grouping and group speed limiting involved in FIG2 , as well as the specific content of the overall speed limit implementation strategy involved in FIG3 , can be found in the relevant records in the subsequent method embodiments and will not be repeated here.

[0079] Please refer to Figure 4, which is a flow chart of a traffic transmission control method shown in an exemplary embodiment of the present application. It should be noted that this method is applicable to the cross-cloud node traffic transmission architecture shown in Figure 1 and is executed by an electronic device, specifically, the central node device 120 in the architecture shown in Figure 1, or the metadata management module 121 in the central node device 120.

[0080] As shown in FIG4 , the exemplary flow transmission control method includes S410 to S440, which are described in detail as follows:

[0081] S410 : In response to a traffic transmission management request for an edge node device, obtain a plurality of traffic metadata.

[0082] Traffic transmission management requests for edge node devices are initiated by the public network resource manager. After the central node device and the edge node device complete the response processing for this traffic transmission management request, data traffic transmission between the central node device and the edge node device can proceed in an orderly manner, thereby ensuring the overall stability of the system. The public network resource manager refers to the network operator, but this embodiment is not limited to only network operators and can be determined based on the actual application scenario.

[0083] In response to a traffic management request from an edge node, the central node device first retrieves pre-entered traffic metadata from a database. Entry of traffic metadata into the database includes, but is not limited to, adding, updating, and deleting traffic metadata. For example, the metadata may be stored in the database as a list of traffic five-tuples.

[0084] Different traffic metadata corresponds to different data transmission scenarios. Specifically, each piece of traffic metadata indicates the parameters required for data traffic transmission within a data transmission scenario. For example, "watching TV" is one data transmission scenario, "listening to the radio" is another, and "system upgrade" is yet another. In each data transmission scenario, data traffic travels along different paths. Furthermore, different data transmission scenarios correspond to different service requirements.

[0085] S420: Group the multiple traffic metadata to obtain multiple metadata groups.

[0086] Data traffic demands in different data transmission scenarios may occur simultaneously, leading to simultaneous occupation of public network resources, resulting in channel congestion, uncompetitive bandwidth resources, and other traffic flow control issues. These traffic flow control issues often occur at edge nodes due to significant bottlenecks in public network bandwidth.

[0087] To solve this problem, the central node device first groups the multiple traffic metadata obtained. The purpose of grouping is to reduce the complexity of traffic transmission control and thus improve the efficiency of traffic control.

[0088] As mentioned earlier, in actual application scenarios, there are thousands of systems inside edge node devices, each of which corresponds to a data transmission scenario or a business scenario. If the traffic transmission of each system is controlled separately, the control complexity will be very high, which will increase the overall resource burden of the system.

[0089] Therefore, the embodiments of the present application group multiple traffic metadata and perform traffic transmission control on a metadata group basis, rather than on a per-business scenario basis. If the business scenarios of thousands of systems are divided into 50 metadata groups, and the edge node devices perform traffic transmission control on each of these 50 metadata groups, this significantly saves a significant amount of scheduling resources and improves traffic control efficiency compared to controlling the traffic flow of thousands of systems individually.

[0090] As an exemplary embodiment, given a preset number of metadata groups, multiple traffic metadata can be randomly divided into these metadata groups. For example, assuming the number of metadata groups is 50, the average amount of traffic metadata that should be contained in each metadata group can be calculated first, and then the corresponding amount of traffic metadata can be divided into each metadata group.

[0091] The amount of traffic metadata allocated to each metadata group may also be uneven, which can be selected according to actual application requirements and is not limited in this embodiment.

[0092] As another exemplary embodiment, under the premise of still presetting the number of metadata groups, it is also possible to achieve precise division of traffic metadata based on the control score of each traffic metadata. Precise division here means that the traffic metadata divided into the same metadata group have similar traffic transmission control methods.

[0093] For example, the control score of each traffic metadata can be determined based on the traffic control factors included in each traffic metadata and the weights corresponding to each traffic control factor, and then the multiple traffic metadata can be grouped according to the determined control scores to obtain multiple metadata groups.

[0094] The weight of each flow control factor is positively correlated with the degree of influence of the flow control factor on the flow transmission control strategy. The greater the influence of the flow control factor on the flow transmission control strategy, the greater the corresponding weight value.

[0095] In addition, the impact of the traffic control factor on the traffic transmission control strategy of the traffic metadata is further divided into positive and negative. The positive impact is used to improve the control score, while the negative impact is used to reduce the control score.

[0096] Taking the traffic control factors including priority, timeliness level, operation source and expected bandwidth as an example, their influence on the traffic transmission control strategy should decrease in sequence. Therefore, their corresponding weight values ​​should also decrease in sequence. It can also be said that their relevance to the control score decreases in sequence.

[0097] For example, if the control score of the traffic metadata is expressed as score, the control score can be calculated according to the following formula: score = priority * 10000 + timeliness level * 100 + operation source * 10 - expected bandwidth

[0098] The weight corresponding to priority is 10,000, the weight corresponding to timeliness level is 100, the weight corresponding to operation source is 10, and the weight corresponding to expected bandwidth is 1. It can be seen that priority, timeliness level, and operation source are positively correlated with the control score, and the correlation with the control score decreases in turn. Expected bandwidth is negatively correlated with the control score.

[0099] There are various ways to group multiple traffic metadata based on their control scores, which are not limited here. For example, a score interval corresponding to each metadata group can be pre-set, and traffic metadata with control scores in the same score interval can be grouped into the same metadata group. Another example is to first arrange multiple traffic metadata in descending or ascending order based on their control scores, and then group these traffic metadata into corresponding metadata groups.

[0100] Regardless of the classification method, traffic metadata with similar traffic transmission control methods will be grouped into the same metadata group. For example, in the aforementioned data transmission scenarios of "Watching TV" and "Listening to the Radio," since the two application scenarios are similar and their traffic transmission control methods are similar, the control scores of the corresponding traffic metadata are also similar. Therefore, the corresponding traffic metadata can be grouped into the same metadata group.

[0101] In other exemplary embodiments, the number of metadata groups may be dynamically determined based on the amount of traffic metadata recorded by the central node device in actual scenarios, rather than being pre-set. For example, a maximum number of traffic metadata contained in each metadata group may be pre-set, and traffic metadata exceeding the maximum number may be assigned to another metadata group, thereby obtaining multiple metadata groups.

[0102] In other exemplary implementations, only the priority may be considered, and the metadata groups may be directly divided according to the priority of the traffic metadata.

[0103] It should be noted that in actual application scenarios, you can choose which grouping method to use based on actual application requirements. For example, if the accuracy of the grouping is mainly considered, you can choose to use the traffic control factor to first calculate the control score of each traffic metadata, and then divide multiple traffic metadata into multiple metadata groups based on the control score.

[0104] S430 : Determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device, where the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth.

[0105] The database records the bandwidth upper limit of each edge node device. Therefore, the bandwidth size of each metadata group can be allocated according to the bandwidth upper limit of the edge node device to obtain bandwidth allocation data corresponding to each metadata group.

[0106] For example, the overall allocation strategy can adopt the principle of efficiency and fairness, dividing all traffic of edge node devices into three parts: reserved buffer traffic, on-demand traffic, and priority traffic. Reserved buffer traffic is used for traffic not included in traffic metadata management; on-demand traffic is used as a guarantee, allowing edge node devices to respond to the traffic transmission needs of various internal systems; priority traffic is used to ensure that all traffic is transmitted normally, while giving priority to important traffic.

[0107] The allocation strategy can also be adjusted according to actual needs. For example, if the impact of traffic not included in traffic metadata management on actual applications is not considered, or the impact of traffic not included in traffic metadata management on actual applications is very small, the allocation strategy may not reserve buffer traffic. For another example, the traffic proportion of each part can be adjusted according to actual application needs.

[0108] Based on the allocation policy described above, the process of determining bandwidth allocation data for each metadata group may include the following steps:

[0109] S431: For each metadata group, determine the bandwidth share corresponding to the metadata group as the ratio of the sum of the expected bandwidths included in each traffic metadata in the metadata group to the sum of the expected bandwidths included in multiple traffic metadata (i.e., all traffic metadata acquired by the central node device);

[0110] S432, determining a buffer bandwidth of the edge node device according to a bandwidth upper limit of the edge node device;

[0111] S433: Determine the difference between the bandwidth upper limit of the edge node device and the buffer bandwidth of the edge node device as the maximum bandwidth of each metadata group, wherein the maximum bandwidth corresponding to each metadata group is the same;

[0112] S434 : For each metadata group, determine the minimum bandwidth corresponding to the metadata group according to the bandwidth proportion, buffer bandwidth, and maximum bandwidth corresponding to the metadata group.

[0113] The bandwidth ratio of each metadata group can reflect the bandwidth allocation requirements of each metadata group for edge node devices.

[0114] The allocation strategy often presets the percentage of traffic reserved for buffering, for example, 20% of the total traffic of the edge node device is reserved as a buffer. Therefore, S432 can determine the buffer bandwidth based on the bandwidth upper limit of the edge node device and this percentage data. The calculation formula is as follows: buffer = max (down_max * 20%, 20)

[0115] Among them, buffer represents the buffer bandwidth of the edge node device, down_max represents the bandwidth upper limit of the edge node device, 20% is the reserved buffer traffic ratio preset by the allocation strategy, and 20 represents the minimum limit of the buffer bandwidth.

[0116] For each metadata group, in addition to the reserved buffer traffic, all other traffic on the edge node device can be used for traffic transmission. This can be used to increase the traffic rate limit for each metadata group under low load conditions, thereby improving transmission efficiency. Therefore, S433 uses the difference between the edge node device's bandwidth upper limit and the edge node device's buffer bandwidth as the maximum bandwidth for each metadata group. It can be seen that the maximum bandwidth is also the maximum bandwidth that can be used by each metadata group.

[0117] For example, the maximum bandwidth of each metadata group can be obtained by the following formula: group_bandmax=down_max-buffer

[0118] Among them, group_bandmax represents the maximum bandwidth of the metadata group, buffer represents the buffer bandwidth of the edge node device, and down_max represents the bandwidth upper limit of the edge node device.

[0119] The minimum bandwidth for each metadata group is the bandwidth required to guarantee the minimum transmission of traffic for each metadata group. This bandwidth is used under high load conditions to ensure that all metadata groups can be transmitted concurrently at the minimum bandwidth while maintaining a healthy transmission channel. As described in S434, the minimum bandwidth for each metadata group is determined based on the buffer bandwidth of the edge node device, the bandwidth contribution of each metadata group, and the maximum bandwidth of each metadata group.

[0120] Exemplarily, the minimum bandwidth of each metadata group may be determined based on the following process:

[0121] Determine the baseline bandwidth based on the maximum bandwidth;

[0122] If the bandwidth ratio is greater than or equal to the preset ratio threshold, the minimum bandwidth is determined based on the bandwidth ratio and the baseline bandwidth;

[0123] If the bandwidth ratio is less than the ratio threshold, the minimum bandwidth is determined based on the ratio threshold and the baseline bandwidth.

[0124] In the above process, the baseline bandwidth is a benchmark value determined based on the maximum bandwidth. Subsequently, the minimum bandwidth of the metadata group will be further determined based on the bandwidth ratio of the metadata group.

[0125] The percentage threshold is used to indicate the minimum flow retained by the edge node device, and is used to ensure the health of the transmission channel when all metadata groups are transmitted concurrently.

[0126] If the bandwidth share of the metadata group is greater than or equal to the preset share threshold, the minimum bandwidth is determined based on the bandwidth share and the baseline bandwidth. If the bandwidth share is less than the share threshold, the minimum bandwidth is determined based on the share threshold and the baseline bandwidth. This ensures that at least 0.5% of the bandwidth is reserved for edge node devices.

[0127] For example, the minimum bandwidth of each metadata group can be calculated by the following formula: group_bandmin = grou_bandmax / 2 * max (band_percent, 0.5%)

[0128] Group_bandmin indicates the minimum bandwidth of the metadata group, group_bandmax indicates the maximum bandwidth of the metadata group, and band_percent indicates the bandwidth percentage of the metadata group.

[0129] It can be seen that the minimum bandwidth of the metadata group is allocated according to the bandwidth ratio after halving the maximum bandwidth, and at least 0.5% of the bandwidth is reserved. After halving the maximum bandwidth, the baseline bandwidth is obtained.

[0130] However, it should be noted that the baseline bandwidth can also be determined based on other methods rather than directly halving the maximum bandwidth. For example, a suitable baseline factor can be determined based on the number of traffic metadata in the metadata group. The baseline factor is a positive number less than 1, and the product of the maximum bandwidth and the baseline factor is used as the baseline bandwidth. If the number of traffic metadata in the metadata group is large, the baseline factor can be determined as a larger value, and the final minimum bandwidth value will also be larger; and if the number of traffic metadata in the metadata group is small, the baseline factor can be determined as a smaller value, and the final minimum bandwidth value will also be smaller. Therefore, when all traffic in the metadata group is transmitted concurrently with the minimum bandwidth, the bandwidth of the edge node device can be used to the greatest extent possible.

[0131] S440: Generate a traffic transmission control instruction based on the multiple metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the edge node device, so that the edge node device controls the data flow transmitted to the central node device.

[0132] The central node device assembles the data of multiple metadata groups and the bandwidth allocation data corresponding to each metadata group into a traffic transmission control instruction, and sends the traffic transmission control instruction to the edge node device. The purpose is to enable the edge node device to control the data flow transmitted to the central node device by executing the received traffic transmission control instruction.

[0133] The data traffic transmitted from the edge node device to the central node device is the data traffic indicated by the routing information contained in the metadata of each traffic, and is the business data that matches the business needs.

[0134] The process in which the edge node device executes the traffic transmission control instruction and controls the data traffic transmitted to the central node device is also the execution process of the speed limit implementation module in the structure shown in Figure 1. For detailed execution details, please refer to the records in the subsequent embodiments, which will not be repeated in this embodiment.

[0135] It should be noted that the technical solution proposed in this embodiment can solve the problem of poor stability of traffic transmission across node devices in existing distributed cloud scenarios by generating traffic transmission control instructions for different metadata groups on the central node device and performing specific traffic transmission control in response to the traffic transmission control instructions on the edge node device.

[0136] Please continue to refer to Figure 5, which is a flow chart of a traffic transmission control method shown in another exemplary embodiment of the present application. It should be noted that this method is applicable to the cross-cloud node device traffic transmission architecture shown in Figure 1 and is executed by an electronic device, specifically the edge node device 110 in the architecture shown in Figure 1, and the method is specifically executed by the speed limit implementation module 111 in the edge node device 110.

[0137] As shown in FIG5 , in an exemplary embodiment, the flow transmission control method includes S510 to S530, which are described in detail as follows:

[0138] S510: Receive a traffic transmission control instruction sent by a central node device, where the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, where the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth.

[0139] The detailed process of the central node device sending the traffic transmission control instruction to the edge node device can be found in the description of the previous embodiment, which will not be repeated here in this embodiment.

[0140] S520 , in response to the traffic transmission control instruction, transmit the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group.

[0141] In response to the traffic transmission control instructions sent by the central node device, the edge node device will first perform initialization configuration according to the traffic transmission control instructions. The initialization configuration also includes, in accordance with the control information carried by the traffic transmission control instructions, creating metadata groups in sequence, configuring multiple traffic five-tuples in each metadata group, and setting the expected bandwidth of the metadata group to the minimum bandwidth to ensure that the traffic transmission channel will not be congested in the initial situation.

[0142] After completing the initialization configuration, the edge node device will implement speed limits on each metadata group according to the minimum bandwidth corresponding to each metadata group. For example, the edge node device can use a traffic controller to implement speed limits on each metadata group in turn, and all five-tuple information groups in each metadata group will share the bandwidth limit of the edge node device. After the internal traffic of the edge node device is speed-limited and rectified, it is delivered to the public network and transmitted to the central node device, thereby achieving the transmission of the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group.

[0143] S530 , adjusting the data traffic transmitted to the central node device according to the real-time congestion detection result of the traffic transmission channel between the central node device and the edge node device and based on the minimum bandwidth and maximum bandwidth corresponding to each metadata group.

[0144] A heartbeat packet is periodically initiated between the central node device and the edge node device. The heartbeat packet can be sent from the central node device to the edge node device or from the edge node device to the central node device. This embodiment does not limit this.

[0145] Heartbeat packets have the highest priority, ensuring they are always transmitted first on the traffic transmission channel between central and edge nodes. High heartbeat packet latency or even packet loss indicates congestion in the public network transmission between cloud nodes. Therefore, a timed heartbeat mechanism can be used to detect congestion in the traffic transmission channel between central and edge nodes.

[0146] If the heartbeat packet is sent from the central node device to the edge node device, the central node device can detect the transmission status data of the heartbeat packet. The transmission status data of the heartbeat packet includes, for example, delay duration, packet loss, etc., and based on the transmission status data, determine the real-time congestion detection result of the traffic transmission channel between the central node device and the edge node device.

[0147] Real-time congestion detection results include messages indicating whether congestion has occurred or not. The central node device promptly feeds these results back to the edge node devices, enabling them to adjust the data flow to the central node device based on the real-time congestion detection results. This helps prevent congestion-related issues and improves system stability.

[0148] If the heartbeat packet is sent from the edge node device to the central node device, the edge node device can detect the transmission status data of the heartbeat packet, and based on the transmission status data, determine the real-time congestion detection result of the traffic transmission channel between the central node device and the edge node device, and perform the next step of processing based on the obtained real-time congestion detection result.

[0149] Exemplarily, the process of the edge node device adjusting the data flow transmitted to the central node device according to the real-time congestion detection result is as follows:

[0150] S531, if the real-time congestion detection result indicates that the traffic transmission channel is not congested, the transmission bandwidth corresponding to each metadata group is increased in sequence according to the maximum bandwidth and the priority of each metadata group;

[0151] S532: If the real-time congestion detection result indicates that the traffic transmission channel is congested, the data traffic corresponding to each metadata group is retransmitted to the central node device according to the minimum bandwidth corresponding to each metadata group.

[0152] In the above control process, if the real-time congestion detection result indicates that the traffic transmission channel is not congested, it means that the overall system load is light. In order to avoid the waste of bandwidth resources caused by the low speed limit of the metadata group in the edge node device, the transmission bandwidth corresponding to each metadata group can be increased in turn according to the priority of each metadata group.

[0153] If real-time congestion detection results indicate congestion in the traffic transmission channel, this indicates a heavy system load. For example, if multiple metadata groups in the traffic transmission channel are running at high traffic volumes and all have high traffic transmission requirements, the total bandwidth exceeds the bandwidth limit of the edge node device. To resolve this issue, data traffic for each metadata group must be re-controlled according to its minimum bandwidth. This means resetting the speed limit for each group to the minimum bandwidth to ensure that the congestion is resolved and the system is restored to normal condition.

[0154] It's important to note that because congestion detection is performed in real time, edge nodes dynamically adjust the data flow to the central node based on the real-time congestion detection results. The entire edge node adjustment process can be described as follows: during low loads, the rate limit for each metadata group is increased to improve overall transmission efficiency; during high loads, the rate limit for each metadata group is reduced to avoid congestion and improve system stability.

[0155] It should also be noted that for data traffic corresponding to traffic metadata not included in multiple metadata groups, the edge node device directly determines the expected bandwidth in the buffer bandwidth based on its expected bandwidth size to transmit the corresponding data traffic to the central node device. In other words, the edge node device does not perform rate limiting processing on traffic metadata not included in the metadata group.

[0156] In an exemplary embodiment, when the real-time congestion detection result indicates that the traffic transmission channel is not congested, the edge node device sequentially increases the transmission bandwidth corresponding to each metadata group according to the priority of each metadata group as follows:

[0157] Preset the incremental bandwidth for a single upgrade and use the metadata group with the highest current priority as the target metadata group;

[0158] Calculate the sum of the current transmission bandwidth and the incremental bandwidth of the target metadata group;

[0159] If the sum does not exceed the maximum bandwidth corresponding to the target metadata group, the transmission bandwidth of the target metadata group is increased to the sum;

[0160] If the sum exceeds the maximum bandwidth corresponding to the target metadata group, the transmission bandwidth of the target metadata group is increased to the maximum bandwidth, wherein the difference between the sum and the maximum bandwidth is used to increase the transmission bandwidth corresponding to the metadata group of the next priority.

[0161] In this way, the transmission bandwidth improvement process is performed on the metadata group with the highest current priority based on the incremental bandwidth in a loop until the transmission bandwidth improvement process has been completed for all metadata groups.

[0162] It should be noted that the metadata group with the highest current priority refers to the metadata group with the highest priority among the metadata groups that have not yet undergone transmission bandwidth improvement processing. The priority of a metadata group is determined based on the priority of the traffic metadata contained therein. For example, it can be the average priority or the maximum priority, which is not restricted here. When the priority of the traffic metadata in a metadata group is higher, the priority of the metadata group is obviously higher. Conversely, when the priority of the traffic metadata in a metadata group is lower, the priority of the metadata group is obviously lower.

[0163] Therefore, each transmission bandwidth increase is targeted at the metadata group with the highest current priority, thus preventing congestion caused by repeated speed increases. Furthermore, this embodiment limits the amount of bandwidth increase (i.e., incremental bandwidth) for each transmission bandwidth increase, thus avoiding congestion caused by excessive speed increases.

[0164] To further facilitate understanding of the speed-up process proposed in this embodiment, the following is a more detailed description of the process in which the edge node device increases the transmission bandwidth corresponding to each metadata group in turn according to the priority of each metadata group using the process illustrated in Figure 7. As shown in Figure 6, the speed-up process includes the following steps:

[0165] S610, obtaining a preset incremental bandwidth;

[0166] S620, taking the metadata group with the highest current priority as the target metadata group;

[0167] S630, calculating the sum of the current transmission bandwidth and the incremental bandwidth of the target metadata group;

[0168] S640, determining whether the sum value exceeds the maximum bandwidth of the target metadata group;

[0169] S650, increasing the transmission bandwidth of the target metadata group to a sum value;

[0170] S660: After the transmission bandwidth of the target metadata group is increased to the maximum bandwidth, the transmission bandwidth corresponding to the metadata group of the next priority is increased using the remaining bandwidth in the incremental bandwidth (i.e., the difference between the sum and the maximum bandwidth);

[0171] S670, determine whether all metadata groups have been accelerated, if not, jump to S620; if yes, end the process.

[0172] As can be seen from the above process, if the current transmission bandwidth of the target metadata group does not exceed the maximum bandwidth of the target metadata group after increasing the incremental bandwidth, the current transmission bandwidth of the target metadata group is directly increased by the incremental bandwidth, that is, the sum of the current transmission bandwidth and the incremental bandwidth of the target metadata group in S630. If the current transmission bandwidth of the target metadata group exceeds the maximum bandwidth of the target metadata group after increasing the incremental bandwidth, this is obviously not allowed. In this case, the transmission bandwidth of the target metadata group is first increased to the maximum bandwidth, and then the remaining bandwidth of the incremental bandwidth is used as the bandwidth increase amount of the metadata group with the next priority. After that, a determination is made as to whether all metadata groups have completed the speed increase. If all metadata groups have completed the speed increase, it means that the bandwidth upper limit configured for all metadata groups has reached the maximum bandwidth. Therefore, if the judgment is yes, it means that there are no metadata groups that can be accelerated, so the process ends directly; if the judgment is no, the process jumps to S620 to continue the next transmission bandwidth increase process.

[0173] It can be seen from the above that in the process of adjusting the bandwidth limit value of each metadata group, this embodiment gradually approaches the maximum value of the speed limit (i.e., the maximum bandwidth), and increases the bandwidth quantitatively each time. The high-priority metadata group is allocated speed increase first, and the low-priority metadata group is allocated speed increase later, which can ensure that high-priority packet traffic can be transmitted first until channel congestion occurs.

[0174] It's also important to emphasize that after the edge node device initially executes the traffic control instruction, that is, after transmitting the data traffic corresponding to each metadata group to the central node device according to the corresponding minimum bandwidth, real-time congestion detection and rate limiting based on the real-time congestion detection results are performed simultaneously. Throughout the traffic transmission process, the edge node device continuously and dynamically adjusts the rate limit bandwidth for each metadata group based on the real-time congestion detection results.

[0175] Therefore, the embodiments of the present application can significantly reduce channel congestion, node loss, and other problems caused by large-scale traffic transmission between distributed cloud nodes by executing packet speed limiting, real-time congestion detection, channel self-healing and other processes, and can effectively improve the stability of cloud nodes.

[0176] As a test of the effectiveness of the technical solution, statistics were collected on the number of abnormal alarms from distributed cloud nodes. The average number of alarms per cloud node decreased from 5 to 0.4 per month, a reduction of over 90%, significantly reducing the pressure on node operation and maintenance. Furthermore, with the improvement of traffic metadata recording, the number of abnormal alarms has gradually approached zero.

[0177] The embodiments of this application can also effectively improve the transmission efficiency of important traffic. Specifically, in an idle state, each service can be transmitted at the maximum bandwidth without being affected. In a congested state, high-priority important traffic is transmitted first, and low-priority traffic is transmitted later according to traffic priority. Taking an edge node device with a 100mbps public network bandwidth as an example, test results show that under congested conditions, the average transmission speed of high-priority traffic increases from 52mbps to 76mbps, a speed increase of approximately 46%.

[0178] Another exemplary embodiment of the present application further proposes a traffic transmission control system, including a central node device and an edge node device, wherein a metadata management module and a gateway controller are deployed on the central node device, and a rate limit implementation module is deployed on the edge node device, wherein:

[0179] The metadata management module obtains a plurality of traffic metadata in response to a traffic transmission management request for an edge node device, groups the plurality of traffic metadata to obtain a plurality of metadata groups, and determines bandwidth allocation data corresponding to each metadata group according to a bandwidth upper limit value of the edge node device, the bandwidth allocation data including a maximum bandwidth and a minimum bandwidth;

[0180] The gateway controller generates a traffic transmission control instruction according to the plurality of metadata groups and the bandwidth allocation data corresponding to each metadata group, and sends the traffic transmission control instruction to the speed limit implementation module;

[0181] The speed limit implementation module responds to the traffic transmission control instruction and transmits the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group, and adjusts the data traffic transmitted to the central node device based on the real-time congestion detection result of the traffic transmission channel between the central node device and the edge node device, and based on the minimum bandwidth and maximum bandwidth corresponding to each metadata group.

[0182] It should be noted that the execution process of each part of the system has been described in detail in the aforementioned embodiments, and will not be repeated here in this embodiment.

[0183] Please refer to FIG7 , which is a block diagram of a flow transmission control device 700 according to an exemplary embodiment of the present application. The device 700 is configured on a central node device. The device 700 includes:

[0184] The metadata acquisition module 710 is configured to acquire a plurality of traffic metadata in response to a traffic transmission management request for an edge node device;

[0185] A grouping module 720 is configured to group the plurality of traffic metadata to obtain a plurality of metadata groups;

[0186] The bandwidth allocation module 730 is configured to determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth;

[0187] The transmission control module 740 is used to generate a traffic transmission control instruction based on the multiple metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the edge node device so that the edge node device controls the data flow transmitted to the electronic device.

[0188] In another exemplary embodiment, the traffic metadata includes a traffic control factor corresponding to a data transmission scenario; and the grouping module 720 includes:

[0189] a score calculation unit, configured to determine a control score of each flow metadata in the plurality of flow metadata according to the flow control factor and a weight corresponding to the flow control factor;

[0190] A score processing unit is configured to group the plurality of traffic metadata according to the control scores to obtain the plurality of metadata groups.

[0191] In another exemplary embodiment, the traffic control factor includes at least one of priority, timeliness level, operation source and expected bandwidth, wherein the priority, the timeliness level and the operation source are positively correlated with the control score, and the correlation with the control score decreases successively; the expected bandwidth is negatively correlated with the control score.

[0192] In another exemplary embodiment, the bandwidth allocation module 730 includes:

[0193] a bandwidth share calculation unit configured to determine, for each metadata group, a ratio of a sum of expected bandwidths included in each flow metadata in the metadata group to a sum of expected bandwidths included in the plurality of flow metadata as a bandwidth share corresponding to the metadata group;

[0194] a buffer bandwidth calculation unit, configured to determine a buffer bandwidth of the edge node device according to a bandwidth upper limit value of the edge node device;

[0195] an upper bandwidth calculation unit, configured to determine a difference between the bandwidth upper limit value and the buffer bandwidth as the maximum bandwidth, wherein the maximum bandwidth corresponding to each metadata group is the same;

[0196] The lower-limit bandwidth calculation unit is configured to determine, for each metadata group, the minimum bandwidth corresponding to the metadata group according to the bandwidth proportion corresponding to the metadata group, the buffer bandwidth, and the maximum bandwidth.

[0197] In another exemplary embodiment, the lower bandwidth calculation unit is configured to:

[0198] Determining a reference bandwidth according to the maximum bandwidth;

[0199] When the bandwidth ratio is greater than or equal to a preset ratio threshold, determining the minimum bandwidth according to the bandwidth ratio and the reference bandwidth;

[0200] When the bandwidth ratio is less than the ratio threshold, the minimum bandwidth is determined according to the ratio threshold and the reference bandwidth. In another exemplary embodiment, the apparatus 700 further includes a congestion detection module 750, which is configured to:

[0201] Sending a heartbeat packet to the edge node device at regular intervals, wherein the heartbeat packet has the highest priority;

[0202] Detecting transmission status data of the heartbeat packet, and determining a real-time congestion detection result of a traffic transmission channel between the electronic device and the edge node device based on the transmission status data;

[0203] Feedback the real-time congestion detection result to the edge node device.

[0204] Please refer to FIG8 , which is a block diagram of a flow transmission control device 800 according to another exemplary embodiment of the present application. The device 800 is configured on an edge node device. The device 800 includes:

[0205] A control instruction receiving module 810 is configured to receive a traffic transmission control instruction sent by a central node device, wherein the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth;

[0206] The initial transmission module 820 is configured to transmit the data traffic corresponding to each metadata group to the central node device in response to the traffic transmission control instruction according to the minimum bandwidth corresponding to each metadata group;

[0207] The speed limit implementation module 830 is configured to adjust the data flow transmitted to the central node device based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group.

[0208] In another exemplary embodiment, the speed limit implementation module 830 includes:

[0209] a speed-up processing unit, configured to, when the real-time congestion detection result indicates that the traffic transmission channel is not congested, sequentially increase the transmission bandwidth corresponding to each metadata group according to the maximum bandwidth and the priority of each metadata group;

[0210] The reset processing unit is configured to retransmit the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group when the real-time congestion detection result indicates that the traffic transmission channel is congested.

[0211] In another exemplary embodiment, the speed-up processing unit is configured to:

[0212] Preset the incremental bandwidth for a single upgrade and use the metadata group with the highest current priority as the target metadata group;

[0213] Calculating a sum of a current transmission bandwidth of the target metadata group and the incremental bandwidth;

[0214] If the sum does not exceed the maximum bandwidth corresponding to the target metadata group, increasing the transmission bandwidth of the target metadata group to the sum;

[0215] If the sum exceeds the maximum bandwidth corresponding to the target metadata group, the transmission bandwidth of the target metadata group is increased to the maximum bandwidth, wherein the difference between the sum and the maximum bandwidth is used to increase the transmission bandwidth corresponding to the metadata group of the next priority.

[0216] In another exemplary embodiment, the apparatus 800 further includes a buffer flow processing module 840, and the buffer flow processing module 840 is configured to:

[0217] For traffic metadata not included in the plurality of metadata groups,

[0218] Obtaining the expected bandwidth included in the traffic metadata;

[0219] The expected bandwidth is determined in the buffer bandwidth of the electronic device to transmit the data traffic corresponding to the traffic metadata to the central node device.

[0220] It should be noted that the flow transmission control device provided in the above embodiment and the flow transmission control method provided in the above embodiment are based on the same concept. The specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here. In actual applications, the flow transmission control device provided in the above embodiment can, as needed, allocate the above functions to different functional modules, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0221] An embodiment of the present application also provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs. When the one or more programs are executed by the one or more processors, the electronic device implements the traffic transmission control method provided in the above-mentioned embodiments.

[0222] Figure 9 shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing an embodiment of the present application. It should be noted that the computer system 1000 of the electronic device shown in Figure 9 is only an example and should not bring any limitation to the functions and scope of use of the embodiment of the present application.

[0223] As shown in Figure 9, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 902 or the program loaded from the storage part 908 into the random access memory (RAM) 903, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 903. The CPU 901, ROM 902 and RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0224] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, and the like; an output section 907 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. Removable media 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like, are installed in the drive 910 as needed, so that computer programs read therefrom can be installed into the storage section 908 as needed.

[0225] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from a removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the various functions defined in the system of the present application are executed.

[0226] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. The computer program contained in the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0227] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0228] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0229] Another aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the aforementioned flow transmission control method. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently and not be incorporated into the electronic device.

[0230] Another aspect of the present application provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the traffic transmission control method provided in each of the above embodiments.

[0231] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. Ordinary technicians in this field can easily make corresponding changes or modifications based on the main ideas and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

[0232] In the specific implementation of this application, related data such as traffic metadata and bandwidth upper limit are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

Claims

1. A flow transmission control method, executed by an electronic device, comprising: In response to a traffic transmission management request for an edge node device, obtaining a plurality of traffic metadata; Grouping the multiple traffic metadata to obtain multiple metadata groups; Determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; and, A flow transmission control instruction is generated according to the multiple metadata groups and the bandwidth allocation data, and the flow transmission control instruction is sent to the edge node device, so that the edge node device controls the data flow transmitted to the electronic device.

2. The method according to claim 1, wherein: The traffic metadata includes a traffic control factor corresponding to a data transmission scenario; and the plurality of traffic metadata are grouped to obtain a plurality of metadata groups, including: Determining a control score for each of the plurality of traffic metadata according to the traffic control factor and a weight corresponding to the traffic control factor; The multiple traffic metadata are grouped according to the control scores to obtain the multiple metadata groups.

3. The method according to claim 2, wherein: The flow control factor includes at least one of priority, timeliness level, operation source and expected bandwidth, wherein: The priority, the timeliness level and the operation source are positively correlated with the control score, and the correlation with the control score decreases in sequence; The expected bandwidth is negatively correlated with the control score.

4. The method according to any one of claims 1 to 3, wherein: The step of determining bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device includes: For each metadata group, a ratio of a sum of expected bandwidths included in each flow metadata in the metadata group to a sum of expected bandwidths included in the plurality of flow metadata is determined as a bandwidth proportion corresponding to the metadata group; Determine the buffer bandwidth of the edge node device according to the bandwidth upper limit value of the edge node device, and determine the difference between the bandwidth upper limit value and the buffer bandwidth as the maximum bandwidth, wherein the maximum bandwidth corresponding to each metadata group is the same; For each metadata group, the minimum bandwidth corresponding to the metadata group is determined according to the bandwidth proportion corresponding to the metadata group, the buffer bandwidth, and the maximum bandwidth.

5. The method according to claim 4, wherein: The determining the minimum bandwidth corresponding to the metadata group according to the bandwidth proportion corresponding to the metadata group, the buffer bandwidth, and the maximum bandwidth includes: Determining a reference bandwidth according to the maximum bandwidth; When the bandwidth proportion is greater than or equal to a preset proportion threshold, determining the minimum bandwidth according to the bandwidth proportion and the reference bandwidth; When the bandwidth proportion is less than the proportion threshold, the minimum bandwidth is determined according to the proportion threshold and the reference bandwidth.

6. The method according to any one of claims 1 to 5, further comprising: Sending a heartbeat packet to the edge node device at a regular interval, wherein the heartbeat packet has the highest priority; Detecting transmission status data of the heartbeat packet, and determining a real-time congestion detection result of a traffic transmission channel between the electronic device and the edge node device based on the transmission status data; Feedback the real-time congestion detection result to the edge node device.

7. A flow transmission control method, executed by an electronic device, comprising: Receiving a traffic transmission control instruction sent by a central node device, wherein the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; In response to the traffic transmission control instruction, the data traffic corresponding to each metadata group is transmitted to the central node device according to the minimum bandwidth corresponding to each metadata group; Obtaining a real-time congestion detection result of a traffic transmission channel between the central node device and the electronic device; and, Based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, the transmission to the The data flow of the central node device is adjusted.

8. The method according to claim 7, wherein: The adjusting the data flow transmitted to the central node device based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group includes: When the real-time congestion detection result indicates that the traffic transmission channel is not congested, the transmission bandwidth corresponding to each metadata group is increased in turn according to the maximum bandwidth and the priority of each metadata group; When the real-time congestion detection result indicates that congestion occurs in the traffic transmission channel, the data traffic corresponding to each metadata group is retransmitted to the central node device according to the minimum bandwidth corresponding to each metadata group.

9. The method according to claim 8, wherein: The step of sequentially increasing the transmission bandwidth corresponding to each metadata group according to the maximum bandwidth and the priority of each metadata group includes: Preset the incremental bandwidth for a single boost, and use the metadata group with the highest current priority as the target metadata group; Calculating a sum of a current transmission bandwidth of the target metadata group and the incremental bandwidth; If the sum value does not exceed the maximum bandwidth corresponding to the target metadata group, increasing the transmission bandwidth of the target metadata group to the sum value; If the sum exceeds the maximum bandwidth corresponding to the target metadata group, the transmission bandwidth of the target metadata group is increased to the maximum bandwidth, wherein the difference between the sum and the maximum bandwidth is used to increase the transmission bandwidth corresponding to the metadata group of the next priority.

10. The method according to any one of claims 7 to 9, further comprising: For the traffic metadata not included in the plurality of metadata groups, Obtaining the expected bandwidth included in the traffic metadata; The expected bandwidth is determined in the buffer bandwidth of the electronic device to transmit the data traffic corresponding to the traffic metadata to the central node device.

11. A traffic transmission control system, comprising a central node device and an edge node device, wherein a metadata management module and a gateway controller are deployed on the central node device, and a speed limit implementation module is deployed on the edge node device, wherein: The metadata management module is used to obtain a plurality of traffic metadata in response to a traffic transmission management request for an edge node device; Grouping the multiple traffic metadata to obtain multiple metadata groups; Determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to the bandwidth upper limit value of the edge node device, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; The gateway controller is used to generate a traffic transmission control instruction according to the multiple metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the speed limit implementation module; The speed limit implementation module is used to transmit the data traffic corresponding to each metadata group to the central node device according to the minimum bandwidth corresponding to each metadata group in response to the traffic transmission control instruction; Obtaining a real-time congestion detection result of a traffic transmission channel between the central node device and the electronic device; And, based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, the data flow transmitted to the central node device is adjusted.

12. A flow transmission control device, comprising: A metadata acquisition module, configured to acquire a plurality of traffic metadata in response to a traffic transmission management request for an edge node device; A grouping module, used for grouping the plurality of traffic metadata to obtain a plurality of metadata groups; A bandwidth allocation module, configured to determine bandwidth allocation data corresponding to each metadata group in the plurality of metadata groups according to a bandwidth upper limit value of the edge node device, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; and, The transmission control module is used to generate a traffic transmission control instruction according to the multiple metadata groups and the bandwidth allocation data, and send the traffic transmission control instruction to the edge node device so that the edge node device controls the data flow transmitted to the electronic device.

13. A flow transmission control device, comprising: A control instruction receiving module, used to receive a traffic transmission control instruction sent by a central node device, wherein the traffic transmission control instruction carries bandwidth allocation data corresponding to each metadata group in a plurality of metadata groups, wherein the bandwidth allocation data includes a maximum bandwidth and a minimum bandwidth; An initial transmission module, configured to transmit the data traffic corresponding to each metadata group to the central node device in response to the traffic transmission control instruction according to the minimum bandwidth corresponding to each metadata group; and, The speed limit implementation module is used to obtain the real-time congestion detection result of the traffic transmission channel between the central node device and the electronic device; and based on the real-time congestion detection result and the minimum bandwidth and the maximum bandwidth corresponding to each metadata group, the transmission The data flow to the central node device is adjusted.

14. An electronic device comprising: one or more processors; A memory for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the traffic transmission control method as described in any one of claims 1-6 or 7-10.

15. A computer-readable storage medium having computer-readable instructions stored thereon, which, when executed by a processor of a computer, enables the computer to execute the flow transmission control method according to any one of claims 1-6 or 7-10.

16. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the flow transmission control method according to any one of claims 1-6 or 7-10 is implemented.

Images