Data traffic scheduling method and device, electronic equipment and medium

Abstract

The invention provides a data traffic scheduling method and device, electronic equipment and a medium. The method comprises the steps that for each terminal device in at least one terminal device, data traffic of the terminal device is detected, an application set is obtained, and the application set comprises applications to which the data traffic belongs; allocating a downlink resource unit (RU) to each terminal device according to the application set corresponding to each terminal device; and forwarding the downlink data traffic to each terminal device based on the distributed downlink RU.

Description

Technical Field

[0001] This specification relates to the field of communication technology, and in particular to data traffic scheduling methods, devices, electronic devices, and media. Background Art

[0002] In wireless networks, to ensure maximum utilization of wireless air interfaces and the normal operation of high-priority services, it is necessary to schedule terminal traffic and provide special protection for high-priority services.

[0003] In related technologies, APs can assign higher access priority to high-priority services through radio chip scheduling. However, AP air interface transmission still needs to follow the air interface's backoff rules, which cannot completely avoid contention. High-priority service traffic must also back off and wait before reaching the air interface, resulting in high latency for high-priority services. Summary of the Invention

[0004] To overcome the problems existing in the related art, this specification provides a data traffic scheduling method, device, electronic device and medium.

[0005] According to a first aspect of an embodiment of this specification, a data traffic scheduling method is provided, which is applied to an access point AP, and at least one terminal device accesses the AP. The method includes: for each terminal device among the at least one terminal device, detecting the data traffic of the terminal device to obtain an application set, wherein the application set includes the application to which the data traffic belongs; according to the application set corresponding to each terminal device, allocating a downlink resource unit RU to each terminal device; and forwarding the downlink data traffic to each terminal device based on the allocated downlink RU.

[0006] According to the second aspect of the embodiments of this specification, a data traffic scheduling device is provided, which is applied to an access point AP, and at least one terminal device accesses the AP. The device includes: a detection module, which is used to detect the data traffic of each terminal device in the at least one terminal device to obtain an application set, and the application set includes the application to which the data traffic belongs; a downlink allocation module, which is used to allocate a downlink resource unit RU to each terminal device according to the application set corresponding to each terminal device; and a downlink forwarding module, which is used to forward downlink data traffic to each terminal device based on the allocated downlink RU.

[0007] According to a third aspect of the embodiments of this specification, there is provided an electronic device, including:

[0008] processor;

[0009] a memory for storing processor-executable instructions;

[0010] The processor is configured to execute the data traffic scheduling method of the first aspect or any corresponding embodiment thereof.

[0011] According to the fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, characterized in that computer instructions are stored on the computer-readable storage medium, and the computer instructions are used to enable a computer to execute the data traffic scheduling method of the above-mentioned first aspect or any corresponding embodiment thereof.

[0012] The technical solutions provided by the embodiments of this specification may have the following beneficial effects:

[0013] In the embodiments of this specification, by allocating a downlink RU to each terminal device based on the application set corresponding to each terminal device, the wireless channel resource allocation can be made more reasonable, the high delay and retransmission events caused by the wireless transmission mechanism can be reduced, and the channel resource utilization rate can be improved.

[0014] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 It is a schematic diagram of a system architecture shown in this specification according to an exemplary embodiment.

[0017] Figure 2 This is a flow chart of a data traffic scheduling method according to an exemplary embodiment of this specification.

[0018] Figure 3 This is a flowchart of another data traffic scheduling method according to another exemplary embodiment of this specification.

[0019] Figure 4 This is a hardware structure diagram of the computer device where the data flow scheduling device in the embodiment of this specification is located.

[0020] Figure 5 This is a block diagram of a data traffic scheduling device according to an exemplary embodiment of the present specification. DETAILED DESCRIPTION

[0021] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring 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 this specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of this specification, as detailed in the appended claims.

[0022] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. As used in this specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0023] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information without departing from the scope of this specification. Depending on the context, the term "if" as used herein may be interpreted as "when," "when," or "in response to determining."

[0024] Next, the embodiments of this specification are described in detail.

[0025] The following combination Figure 1 The system architecture to which the data traffic scheduling method and device of the embodiment of this specification can be applied is described. It should be noted that, Figure 1 What is shown is merely an example of a system architecture to which the embodiments of this specification can be applied, to help those skilled in the art understand the technical content of this specification, but does not mean that the embodiments of this specification cannot be used in other devices, systems, environments or scenarios.

[0026] Figure 1 It is a schematic diagram of a system architecture shown in this specification according to an exemplary embodiment.

[0027] like Figure 1 As shown, the system architecture may include, for example, a terminal device (terminal for short), an AP (Access Point) and an AC (Access Controller).

[0028] The AC centrally controls and manages APs. APs provide connection and access services to terminal devices. Terminal devices access the network and network resources through APs.

[0029] The AC and the AP may be connected directly or through a device such as a switch. The switch includes but is not limited to a Poe (Power Over Ethernet) switch.

[0030] For example, in this embodiment, the APs may include AP1 and AP2, and the terminal devices may include STA1, STA2, ..., STAn, where n is a positive integer. The AC and APs may support Wi-Fi 7.

[0031] The data flow scheduling method provided in the embodiments of this specification is described in detail below. Figure 2 As shown, Figure 2 This is a flowchart of a data traffic scheduling method according to an exemplary embodiment of this specification. The method is applied to an AP. The data traffic scheduling method provided in the embodiment of this specification may include the following steps.

[0032] In step 210, for each terminal device in at least one terminal device, the data traffic of the terminal device is detected to obtain an application set, where the application set includes the application to which the data traffic belongs.

[0033] According to embodiments of this specification, an AP can, for example, use Deep Packet Inspection (DPI) to inspect data traffic and determine the application to which the data traffic belongs. For example, in this embodiment, the AP can analyze the header and payload of each packet in the data traffic to obtain signature information. The AP then identifies the application that matches the signature information as the application to which the data traffic belongs.

[0034] According to an embodiment of the present specification, the detected data traffic may include uplink traffic and / or downlink traffic of the terminal device.

[0035] In step 220, a downlink RU (Resource Unit) is allocated to each terminal device according to the application set corresponding to each terminal device.

[0036] According to an embodiment of this specification, an AP may be pre-configured with an application bandwidth requirement list, which records at least one preset application and the number of downlink RUs corresponding to each preset application. The preset applications in the application bandwidth requirement list can be set according to actual needs. For example, in this embodiment, high-priority services (hereinafter referred to as high-priority services) can be used as preset applications in the application bandwidth requirement list.

[0037] Based on this, the AP can determine, for each terminal device, the target application in the application bandwidth requirement list in the application set corresponding to the terminal device, and the number of downlink RUs corresponding to each target application in the application bandwidth requirement list; then calculate the sum of the number of downlink RUs corresponding to each target application to obtain the first target number; and allocate the first target number of downlink RUs to the terminal device.

[0038] For example, the applications listed in the application bandwidth requirement list may include conferencing and live streaming applications. Tencent Meeting corresponds to one RU, and live streaming corresponds to two RUs, requiring a total of three RUs for conferencing and live streaming applications. If the data traffic of a terminal device belongs to both conferencing and live streaming applications, three RUs can be allocated to the terminal device.

[0039] In step 230 , based on the allocated downlink RU, the downlink data traffic is forwarded to each terminal device.

[0040] According to the embodiments of this specification, by allocating a downlink RU to each terminal device based on the application set corresponding to each terminal device, the allocation of wireless channel resources can be made more reasonable, reducing high latency and retransmission events caused by the wireless transmission mechanism, and improving channel resource utilization.

[0041] In addition, the AP uses standard wireless protocol interaction when allocating downlink RUs to terminal devices. The terminal devices do not need to perform special compatibility adaptation. Only the wireless network device side needs to perform algorithm adaptation, which improves compatibility.

[0042] Optionally, the AP may also determine the user level corresponding to each terminal device and determine the order in which downlink RUs are allocated to each terminal device based on the user level corresponding to each terminal device, wherein a terminal device with a higher user level is allocated an earlier downlink RU in the order in which the terminal device is allocated.

[0043] For example, user levels may include VIP (VIP) and ordinary. When allocating downlink RUs, VIP users are allocated first, and then ordinary users are allocated.

[0044] like Figure 3 FIG. 1 is a flow chart of another data traffic scheduling method according to an exemplary embodiment. This embodiment, based on the previous embodiment, describes a process for allocating downlink RUs, including the following steps:

[0045] In step 310, the uplink RU requirement of at least one terminal device is determined.

[0046] According to an embodiment of the present specification, the uplink RU demand may be actively reported by the terminal device, or the uplink RU demand may be reported by the terminal device based on a notification from the AP.

[0047] For example, in this embodiment, the AP can send a BSRP (Buffer Status Report Packet) to the terminal device to request the terminal device's buffer information. The buffer information may include the amount of data to be sent by the terminal device. After receiving the BSRP, the terminal device responds to the AP with a BSR message containing buffer information. After receiving the BSR message, the AP can determine the terminal device's uplink RU requirement based on the buffer information contained in the BSR message.

[0048] In step 320, it is determined whether the number of available uplink RUs is less than the sum of the uplink RU requirements of the at least one terminal device.

[0049] If the number of available uplink RUs is greater than or equal to the sum of the uplink RU requirements of the at least one terminal device, execute step 330. If the number of available uplink RUs is less than the sum of the uplink RU requirements of the at least one terminal device, execute step 340.

[0050] In step 330, an uplink RU is allocated to each terminal device according to the uplink RU requirement of each terminal device.

[0051] In step 340, an uplink RU is allocated to each terminal device according to the application set corresponding to each terminal device.

[0052] According to an embodiment of the present disclosure, for example, for each terminal device, the target applications in the application bandwidth requirement list and the number of uplink RUs corresponding to each target application in the application bandwidth requirement list can be determined from the application set corresponding to the terminal device. The sum of the number of uplink RUs corresponding to each target application is then calculated to obtain a second target number. The second target number of uplink RUs is then allocated to the terminal device.

[0053] According to an embodiment of the present specification, after an uplink RU is allocated to a terminal device, the uplink data traffic of the terminal device can be transmitted based on the allocated RU.

[0054] According to the embodiments of this specification, by allocating an uplink RU to each terminal device based on the application set corresponding to each terminal device, the allocation of wireless channel resources can be made more reasonable, reducing high latency and retransmission events caused by the wireless transmission mechanism, and improving channel resource utilization.

[0055] In addition, the AP uses standard wireless protocol interaction when allocating uplink RUs to terminal devices. The terminal devices do not need to perform special compatibility adaptation. Only the wireless network device side needs to perform algorithm adaptation, which improves compatibility.

[0056] Optionally, during the execution of step 330, the AP may also determine the order of allocating uplink RUs to each terminal device based on the user level corresponding to each terminal device, wherein the higher the user level of the terminal device, the earlier the order of allocating uplink RUs to the terminal device.

[0057] For example, user levels may include VIP and common. When allocating uplink RUs, VIP users are allocated first, and then common users are allocated.

[0058] Optionally, in this embodiment, a portion of RUs can be reserved as scheduling resources for low-priority users. High-priority users and high-priority services can be preferentially allocated RU resources. The AP can allocate RU resources of different sizes based on the built-in application bandwidth requirement list to ensure bandwidth and low latency for high-priority users and high-priority services. Non-high-priority users and non-high-priority services can take turns to obtain RU reserved resources and the remaining RU resources of high-priority users and high-priority services, ensuring that high-priority users and high-priority services are protected while non-high-priority users and non-high-priority services are not starved.

[0059] For example, if there are 8 RUs, 7 of them can be used as RU resources for high-priority users and high-priority services, and 1 RU can be reserved as a scheduling resource for non-high-priority users and non-high-priority services.

[0060] When high-priority users or high-priority services are present, they are preferentially allocated RU resources from the seven RUs. Non-high-priority users and non-high-priority services can alternately access the one RU reserved for them and the remaining RU resources from the other seven RUs. Based on this, downlink RUs can be divided into a first RU set and a second RU set, with the first RU set being larger than the second RU set.

[0061] Based on this, for a first terminal device among at least one terminal device whose user level is greater than or equal to the level threshold, a downlink RU can be allocated to the first terminal device based on the first RU set. The level threshold can be set according to actual needs.

[0062] For a second terminal device among at least one terminal device whose user level is less than a level threshold, if the available RUs in the first RU set are less than a resource threshold, a downlink RU can be allocated to the second terminal device based on the second RU set. The resource threshold can be set according to actual needs.

[0063] Similarly, the uplink RUs can also be divided into a third RU set and a fourth RU set, and the third RU set is larger than the fourth RU set.

[0064] Based on this, for a first terminal device whose user level is greater than or equal to the level threshold among the at least one terminal device, an uplink RU can be allocated to the first terminal device based on the third RU set;

[0065] For a second terminal device among at least one terminal device whose user level is less than the level threshold, when the available RUs in the fourth RU set are less than the resource threshold, an uplink RU can be allocated to the second terminal device based on the fourth RU set.

[0066] Optionally, the AP can also send messages to negotiate RU allocation with the currently connected terminal device in real time, so that the AP and the terminal can achieve two-way traffic forwarding guarantee and reasonable allocation of channel resources.

[0067] For example, when an AP sends a message to a terminal device, the AP's scheduling module allocates RUs based on the bandwidth required by each terminal device and then sends an MU-RTS message to reserve a channel and inform the terminal of the allocated RU resources. The AP and the terminal device then transmit data.

[0068] Corresponding to the embodiments of the aforementioned method, this specification also provides embodiments of a data traffic scheduling device and a terminal to which it is applied.

[0069] The embodiments of the data flow scheduling device in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented through software, hardware, or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor in which it is located reading the corresponding computer program instructions in the non-volatile memory into the memory and running them. From the hardware level, if Figure 4 The figure is a hardware structure diagram of the computer device where the data flow scheduling device of the embodiment of this specification is located, except Figure 4 In addition to the processor 410, memory 430, network interface 420, and non-volatile memory 440 shown, the server or electronic device where the device 431 is located in the embodiment may also include other hardware according to the actual function of the computer device, which will not be described in detail.

[0070] like Figure 5 As shown, Figure 5 This is a block diagram of a data traffic scheduling device according to an exemplary embodiment of this specification. The device can be applied to an AP. At least one terminal device is connected to the AP. The device includes:

[0071] A detection module 510 is configured to detect data traffic of each terminal device in at least one terminal device to obtain an application set, where the application set includes an application to which the data traffic belongs;

[0072] A downlink allocation module 520 is configured to allocate a downlink resource unit RU to each terminal device according to an application set corresponding to each terminal device;

[0073] The downlink forwarding module 530 is used to forward downlink data traffic to each terminal device based on the allocated downlink RU.

[0074] Optionally, the downlink allocation module may include:

[0075] A first determination submodule is configured to determine, for each terminal device, a target application in an application bandwidth requirement list from an application set corresponding to the terminal device, and a number of downlink RUs corresponding to each target application in the application bandwidth requirement list;

[0076] A first calculation submodule is configured to calculate the sum of the number of downlink RUs corresponding to each target application to obtain a first target number;

[0077] The first allocation submodule is used to allocate a first target number of downlink RUs to the terminal device.

[0078] Optionally, the device may further include:

[0079] A first level determination module is used to determine the user level corresponding to each terminal device;

[0080] The first order determination module is used to determine the order of allocating downlink RUs to each terminal device according to the user level corresponding to each terminal device, wherein the higher the user level of the terminal device, the higher the order of allocating downlink RUs to the terminal device.

[0081] Optionally, the downlink RUs are divided into a first RU set and a second RU set, where the first RU set is larger than the second RU set; and the downlink allocation module may include:

[0082] A second allocation submodule is configured to allocate a downlink RU to a first terminal device among at least one terminal device whose user level is greater than or equal to the level threshold based on the first RU set;

[0083] The third allocation submodule is used to allocate a downlink RU to a second terminal device whose user level is less than the level threshold in at least one terminal device based on the second RU set when the available RU in the first RU set is less than the resource threshold.

[0084] Optionally, the device may further include:

[0085] An uplink demand determination module, configured to determine an uplink RU requirement of at least one terminal device;

[0086] The uplink allocation module is used to allocate an uplink RU to each terminal device according to the application set corresponding to each terminal device if the number of available uplink RUs is less than the sum of the uplink RU requirements of at least one terminal device.

[0087] Optionally, the uplink allocation module may include:

[0088] A second determination submodule is configured to determine, for each terminal device, a target application in the application bandwidth requirement list from the application set corresponding to the terminal device, and the number of uplink RUs corresponding to each target application in the application bandwidth requirement list;

[0089] A second calculation submodule is configured to calculate the sum of the number of uplink RUs corresponding to each target application to obtain a second target number;

[0090] The fourth allocation submodule is used to allocate the second target number of uplink RUs to the terminal device.

[0091] Optionally, the device may further include:

[0092] A second level determination module is used to determine the user level corresponding to each terminal device;

[0093] The second order determination module is used to determine the order of allocating uplink RUs to each terminal device according to the user level corresponding to each terminal device, wherein the higher the user level of the terminal device, the earlier the order of allocating uplink RUs to the terminal device.

[0094] Optionally, the uplink RUs are divided into a third RU set and a fourth RU set, where the third RU set is larger than the fourth RU set; and the uplink allocation module may include:

[0095] A fifth allocation submodule, configured to allocate an uplink RU to a first terminal device whose user level is greater than or equal to the level threshold among the at least one terminal device based on a third RU set;

[0096] The sixth allocation submodule is used to allocate an uplink RU to a second terminal device whose user level is less than the level threshold among at least one terminal device, based on the fourth RU set, when the available RU in the fourth RU set is less than the resource threshold.

[0097] Accordingly, this specification also provides an electronic device, which includes a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to: for each terminal device in at least one terminal device, detect the data traffic of the terminal device to obtain an application set, the application set including the application to which the data traffic belongs; according to the application set corresponding to each terminal device, allocate a downlink resource unit RU to each terminal device; based on the allocated downlink RU, forward the downlink data traffic to each terminal device.

[0098] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0099] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0100] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0101] Other embodiments of the present invention will readily occur to those skilled in the art upon consideration of the present invention and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present invention being indicated by the following claims.

[0102] It should be understood that the present description is not limited to the exact structure that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0103] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A data traffic scheduling method, applied to an access point AP, characterized in that: At least one terminal device accesses the AP, and the method includes: For each terminal device among the at least one terminal device, detect data traffic of the terminal device to obtain an application set, where the application set includes an application to which the data traffic belongs; Allocate a downlink resource unit RU to each terminal device according to the application set corresponding to each terminal device; Based on the allocated downlink RU, forward downlink data traffic to each terminal device.

2. The method according to claim 1, characterized in that The allocating a downlink resource unit RU to each terminal device according to the application set corresponding to each terminal device includes: For each terminal device, Determine, in the application set corresponding to the terminal device, a target application in the application bandwidth requirement list, and the number of downlink RUs corresponding to each target application in the application bandwidth requirement list; Calculate the sum of the number of downlink RUs corresponding to each target application to obtain a first target number; Allocate the first target number of downlink RUs to the terminal device.

3. The method according to claim 1 or 2, characterized in that Also includes: Determining a user level corresponding to each terminal device; According to the user level corresponding to each terminal device, the order of allocating downlink RU to each terminal device is determined, wherein the higher the user level of the terminal device, the earlier the order of allocating downlink RU to the terminal device.

4. The method according to claim 3, characterized in that The downlink RUs are divided into a first RU set and a second RU set, where the first RU set is larger than the second RU set; and the allocating a downlink resource unit RU to each terminal device according to the application set corresponding to each terminal device includes: For a first terminal device among the at least one terminal device, whose user level is greater than or equal to a level threshold, allocating a downlink RU to the first terminal device based on the first RU set; For a second terminal device among the at least one terminal device whose user level is less than the level threshold, when the available RUs in the first RU set are less than the resource threshold, a downlink RU is allocated to the second terminal device based on the second RU set.

5. The method according to claim 1, wherein The method further comprises: Determining an uplink RU requirement of the at least one terminal device; If the number of available uplink RUs is less than the sum of the uplink RU requirements of the at least one terminal device, an uplink RU is allocated to each terminal device according to the application set corresponding to each terminal device.

6. The method according to claim 5, characterized in that The allocating an uplink RU to each terminal device according to the application set corresponding to each terminal device includes: For each terminal device, Determine, in the application set corresponding to the terminal device, a target application in the application bandwidth requirement list, and the number of uplink RUs corresponding to each target application in the application bandwidth requirement list; Calculate the sum of the number of uplink RUs corresponding to each target application to obtain a second target number; Allocate the second target number of uplink RUs to the terminal device.

7. The method according to claim 5 or 6, characterized in that Also includes: Determining a user level corresponding to each terminal device; According to the user level corresponding to each terminal device, the order of allocating uplink RUs to each terminal device is determined, wherein the higher the user level of the terminal device, the earlier the order of allocating uplink RUs to the terminal device.

8. The method according to claim 7, characterized in that The uplink RUs are divided into a third RU set and a fourth RU set, the third RU set being larger than the fourth RU set; and allocating the uplink RUs to each terminal device according to the application set corresponding to each terminal device includes: For a first terminal device whose user level is greater than or equal to a level threshold among the at least one terminal device, allocating an uplink RU to the first terminal device based on the third RU set; For a second terminal device among the at least one terminal device whose user level is less than the level threshold, when the available RUs in the fourth RU set are less than the resource threshold, an uplink RU is allocated to the second terminal device based on the fourth RU set.

9. A data traffic scheduling device, applied to an access point AP, characterized in that: At least one terminal device accesses the AP, and the apparatus includes: a detection module, configured to detect, for each terminal device among the at least one terminal device, data traffic of the terminal device, and obtain an application set, where the application set includes an application to which the data traffic belongs; A downlink allocation module, configured to allocate a downlink resource unit RU to each terminal device according to an application set corresponding to each terminal device; The downlink forwarding module is used to forward downlink data traffic to each terminal device based on the allocated downlink RU.

10. An electronic device comprising: processor; a memory for storing processor-executable instructions; The processor is configured to execute the data traffic scheduling method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the data traffic scheduling method according to any one of claims 1 to 8.

Images