WO2022073512A1

WO2022073512A1 - Scheduling method and apparatus, and electronic device

Info

Publication number: WO2022073512A1
Application number: PCT/CN2021/122872
Authority: WO
Inventors: 陈飞; 樊双; 周一新
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-10-10
Filing date: 2021-10-09
Publication date: 2022-04-14
Also published as: CN114338558A

Abstract

The embodiments of the present application relate to the field of communications, and in particular relate to a scheduling method and apparatus, and an electronic device. The scheduling method comprises: acquiring scheduling information and service data of a service, wherein the scheduling information comprises a service delay requirement, user types, an EDCA parameter and a data structure parameter of the service; acquiring a service delay parameter, a scheduling period and a service priority according to the service delay requirement; acquiring an airtime of the service according to the data structure parameter of the service; acquiring, according to the service priority, an MAC protocol data unit (MPDU) queue corresponding to the service data; acquiring an initial scheduling scheme according to the scheduling period, the airtime, the number of user types and the MPDU queue; and adjusting the initial scheduling scheme according to the EDCA parameter, and sending the service data according to the adjusted scheduling scheme.

Description

A scheduling method, device and electronic device

cross reference

This application is based on the Chinese patent application with the application number "202011079583.3" and the application date is October 10, 2020, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference. Apply.

technical field

The embodiments of the present application relate to the field of communications, and in particular, to a scheduling method, apparatus, and electronic device.

Background technique

Traditional WIFI uses carrier sense multiple access/collision avoidance mechanism to schedule multiple stations (Station, STA). The process of the carrier sense multiple access/collision avoidance mechanism is: the device that needs to send information listens to whether the channel is idle, and if the channel is idle, it waits for a Distributed Inter-frame Spacing (DIFS), otherwise it continues to detect Listen; if there is data transmission on the channel during the waiting process, the device that needs to send information resumes listening. If the channel is always idle during the waiting process, the device that needs to send information occupies the channel to transmit data after waiting.

However, with the growth of services with low traffic but low latency requirements such as game acceleration, low latency has become a core quality of service, but the carrier sense multiple access/collision avoidance mechanism is used for multiple devices. The low-latency requirements of users are not considered during scheduling.

Application content

Embodiments of the present application provide a scheduling method, including: acquiring service scheduling information and service data, wherein the scheduling information includes service delay requirements, user types, EDCA parameters, and service data structure parameters; according to the Obtaining the service delay parameter, scheduling period and service priority according to the service delay requirement; obtaining the air interface time Airtime of the service according to the data structure parameter of the service; obtaining the MAC protocol data unit MPDU corresponding to the service data according to the service priority queue; obtain the initial scheduling scheme according to the scheduling period, the Airtime, the user type and the MPDU queue; adjust the initial scheduling scheme according to the EDCA parameters, and send the service data according to the adjusted scheduling scheme .

Embodiments of the present application further provide a scheduling device, comprising: an information acquisition module for acquiring service scheduling information and service data, wherein the scheduling information includes service delay requirements, user types, EDCA parameters, service data structure parameters; an Airtime acquisition module, used for acquiring service delay parameters, scheduling period and service priority according to the service delay requirements, and obtaining the air interface time Airtime of the service according to the data structure parameters of the service; a scheduling module, used for The MAC protocol data unit MPDU queue corresponding to the service data is obtained according to the service priority, the initial scheduling scheme is obtained according to the scheduling period, the Airtime, the user type and the MPDU queue, and adjusted according to the EDCA parameter the initial scheduling scheme, and the service data is sent according to the adjusted scheduling scheme.

Embodiments of the present application also provide an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores data executable by the at least one processor The instructions are executed by the at least one processor to enable the at least one processor to perform the scheduling method described above.

Description of drawings

One or more embodiments are exemplified by the pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments.

FIG. 1 is a flowchart of the scheduling method provided by the first embodiment of the present application;

2 is a flowchart of a scheduling method provided by a second embodiment of the present application;

Fig. 3 is a flowchart of step 206 and step 207 in the scheduling method provided by the second embodiment of the present application shown in Fig. 2;

4 is a schematic structural diagram of a scheduling device provided by a third embodiment of the present application;

FIG. 5 is a schematic structural diagram of an electronic device provided by a fourth embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present application more clear, each embodiment of the present application will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can understand that, in each embodiment of the present application, many technical details are provided for the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present application, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The first embodiment of the present application relates to a scheduling method, which is applied in a wireless local area network. The process is shown in FIG. 1 , including:

Step 101: Acquire scheduling information and service data of the service, where the scheduling information includes service delay requirements, user types, EDCA parameters, and service data structure parameters.

In this embodiment, the user type is the type of the supportable protocol or mechanism negotiated between the basic service centralized device and the AP, such as SU, MU-AX/AC, OFDMA, Legacy, TWT and the like. The data structure parameter of the service. The data structure is the parameter of the data structure designed by the data path. The lower line is the actual value, and the upper line is the length of the TID Buffer allocated after the ADDBA respond frame structure is confirmed. The service data is the data required for the service provided by the device to the user.

Step 102: Acquire a service delay parameter, a scheduling period and a service priority according to the service delay requirement.

In this embodiment, the service delay parameter includes an average delay parameter and a maximum delay parameter, wherein the average delay parameter is commonly used. The service priority is the information carried in the service delay requirement, and the priority is defined in accordance with the IEEE802.11ax protocol. Among them, priority 15 is the highest and priority 0 is the lowest. Compatible with four types of AC (access classification) of traditional standards: AC_VO (voice service), AC_VI (video service), AC_BE (best effort), AC_BK (background traffic). It also applies to some custom business priorities (such as game operations, game commands, game voice, game video, etc.), and can also be used as a management signaling channel (highest priority).

Step 103: Acquire the air interface time Airtime of the service according to the data structure parameter of the service.

Step 104: Acquire the MPDU queue of the MAC protocol data unit corresponding to the service data according to the service priority.

In this embodiment, the content of the MPDU queue is service data, but the service and equipment corresponding to the service data are not limited, which may be part of the service of a single device, or service data of multiple devices.

Step 105: Acquire an initial scheduling scheme according to the scheduling period, Airtime, user type and MPDU queue.

Step 106: Adjust the initial scheduling scheme according to the EDCA parameters, and send service data according to the adjusted scheduling scheme.

In this embodiment, when the service data is sent, the MPDUA frame in the MPDU queue is sent.

The scheduling method of the embodiment of the present application can obtain service data, service delay requirements, user types, EDCA parameters, and service data structure parameters, and then obtain service delay parameters, scheduling period and service priority according to the service delay requirements; The data structure parameter of the service obtains the air interface time Airtime of the service, and obtains the MPDU queue of the MAC protocol data unit corresponding to the service data according to the service priority. The initial scheduling scheme is obtained from the data and MPDU queues, and the initial scheduling scheme is adjusted according to the EDCA parameters. When the hardware conditions are met, the scheduling scheme that is closest to the user's delay requirement is guaranteed. Finally, the service data is sent according to the adjusted scheduling scheme. It solves the problem that the user's low-latency requirements are not considered in the scheduling process. Due to the introduction of service delay requirements and service priorities in the process of obtaining the scheduling scheme, the services with higher priorities are transmitted first, and the services with higher priorities generally have higher delay requirements, reducing the number of users who require less delay. requirements, so that the obtained scheduling method can meet the user's delay requirements.

The second embodiment of the present application relates to a scheduling method, which is applied in a wireless local area network. The process is shown in FIG. 2 , including:

Step 201: Acquire a service delay requirement and a service delay parameter configured on a user interface or an APP.

In this embodiment, the following parameter table can be obtained from the main content of the user interface or APP configuration:

Among them, the device and service ID (TID) can be designed as a data structure in the form of "device_TID" through the data path. In this embodiment, the maximum supported number of devices is 256, and the maximum supported number of TIDs is 16. The Length field is the data structure parameter of "device_TID", which is the actual value in the process of data downlink transmission. In the process of data uplink transmission, it is the length of the buffer allocated to the service after the response frame is confirmed, and CW is the contention window defined by the standard. , the minimum value CWmin, the maximum value CWmax. Latency_tag is a service delay parameter. aSlotTime is a standard-defined air interface time slot, which is 9us under the OFDM mechanism and 20us under the HR/DSSS mechanism. aSIFSTime is a standard-defined short interval frame, which is 16us under the OFDM mechanism and 10us under the HR/DSSS mechanism. In the actual use process, the service delay parameter will be saved in the descriptor generated according to a certain format, and the service delay parameter will be transmitted through the descriptor during the use process. It should be noted that since the descriptor generator is sensitive to delay, it needs to be generated in the Cache that runs faster.

Step 202, determining a scheduling period.

In this embodiment, the method for determining the scheduling period may be to select the maximum delay requirement min (Latency_tag1, ...Latency_tag n) of all TID targets configured by the user; it may also be to directly select a Beacon period. When the user input delay Latency_tag requires less than one Beacon period, the minimum Beacon period can be used. When the wireless access point AP has multiple SSIDs, the Beacon cycle is complicated, and the minimum Beacon cycle can still be used.

Step 203: Obtain the minimum air interface time Airtime required by each service according to the data structure parameter.

In this embodiment, Airtime=length*rate, where rate is the theoretical rate value of the scheduling period of the standard provision TID.

Step 204, build an MSDU queue according to the service priority.

In this embodiment, the data in the MSDU frame in the MSDU queue is service data, one service corresponds to one MSDU frame, and each descriptor generated according to the service delay parameter corresponds to one MSDU frame. The MSDU queue is a plurality of queues obtained by classifying all MSDUs, but the classification method is not limited in this embodiment. The MSDU frames of the same device can be divided into one class to form a queue, or different devices can be divided into one. The same business is divided into one category to form a queue. It should be noted that, in this embodiment, the order in which the MSDU frames enter the queue to construct the MSDU queue is determined according to the service priority.

Step 205: Determine whether the service supports the OFDMA mechanism and/or the MU-MIMO mechanism according to the user type.

In this embodiment, the user type is a type of a protocol or mechanism that can be supported by the device and the wireless access point AP after negotiation in the basic service set BBS, such as SU, MU-AX/AC, OFDMA, Legacy, TWT and other types. Therefore, whether to support the OFDMA mechanism and/or the MU-MIMO mechanism can be directly determined according to the user type.

Step 206, aggregate MSDU/MPDU based on the service.

In this embodiment, for the data transmission process that can use the OFDMA mechanism and/or the MU-MIMO mechanism, the consideration of whether the service belongs to the same user can be weakened, and the delay requirement can be prioritized, and the service data with similar delay requirements can be considered. Aggregate, so that the needs of services with high latency requirements can be shortened as much as possible in advance and better meet the needs of users. Step 207: Aggregate MSDU/MPDU based on users.

In this embodiment, since different user types use different mechanisms or protocol types in the communication process, for example, when the user type is Legacy, the service data cannot be spatially multiplexed in the transmission process, because the legacy mechanism requires exclusive channel. Therefore, it is necessary to aggregate according to users at this time. In this embodiment, the MSDU is actually aggregated first to obtain the A-MSDU subframe, and then the A-MSDU subframe is obtained after the A-MSDU subframe is aggregated, and the A-MSDU subframe is obtained after the A-MSDU is processed by the physical layer. frame, and then the A-MSDU subframes are aggregated to finally obtain the MPDU frame.

Specifically, the flow of step 206 or step 207 is shown in Figure 3:

Step 301: Acquire the initial token number of the service according to the service delay parameter.

In this embodiment, the initial token number of the service can be based on the expression:

Token_tag is the number of initial tokens of the service, M=max( _{Latency_tag} ₁ , . In this embodiment, according to the data in the above table, it can be calculated that the TID with the smallest delay requirement can obtain 9 tokens, and the TID with the largest delay requirement can obtain 2 tokens.

Step 302: Start a timer according to the original token count of the service, update the token count of the service, and obtain the count value of the timer.

In this embodiment, when the number of tokens of the service is not 0, one token can be consumed to enable the timer, and the timer starts timing. The approximate number of bytes that can be transmitted in the Airtime time into the MSDU queue.

Step 303: Acquire the transmission opportunity TXOP according to the count value of the timer.

Step 304: Aggregate the MSDUs according to the TXOP to obtain an A-MSDU subframe queue.

Specifically, when the token is available, the enabled MSDU queue is entered into the A-MSDU queue when the timer expires. Terminates when Airtime matches the approximate number of bytes in the A-MSDU queue. The number of tokens of the corresponding service is decreased by one, and the update of the number of tokens is completed.

Step 305: Acquire the A-MPDU subframe queue according to the A-MSDU subframe queue.

Step 306: Aggregate the A-MPDU subframes in the A-MPDU subframe queue according to the number of tokens of the service, the antenna information and the RU allocation result, and obtain the MPDU queue.

It should be noted that, in this embodiment, the influence of the channel and the RU allocation result needs to be considered in the aggregation process of the MPDU, which is different from the aggregation process of the MSDU. Moreover, the resource unit RU allocation result is the output result of the resource allocator, including the currently available RU and the current most matching RU allocation scheme. The RU allocator can make the configuration into different profiles according to the frequency band for calling. The state is refreshed on the next scheduling cycle.

Specifically, for example, the TID0 delay Latency_tag of a certain STA 1 is required to be 5ms, the Latency_max is 20ms, and the TIDs of other STAs are all more than 50ms, then the scheduling period 302 at this time will be reduced to 5ms, and the priority is the TID0 of STA 1 It is aggregated into A-MSDU alone, and the minimum air interface time Airtime2 is allocated (it may not be aggregated depending on the length of the TID). For example, if STA 1 is an HE terminal that supports UL-OFDMA, and most of the other STA n also support UL-OFDMA at this time, the TID0 of STA 1 will be aggregated with other TID1-15 and allocated into a Trigger frame. At this time, the Trigger frame The TXOP of STA 1 will always give priority to the TID0 message of STA 1.

It should be noted that the services that can support the OFDMA mechanism and/or the MU-MIMO mechanism can share the window. Before the AP has obtained the air interface, it needs to obtain the TXOP based on the EDCA method. When the AP has the air interface, you can configure the STA's EDCAF parameters to achieve related The service that cannot support the OFDMA mechanism and/or the MU-MIMO mechanism needs an exclusive window, and needs to obtain the TXOP based on the EDCA method. Therefore, the steps for obtaining MPDUs from MSDU aggregation are not exactly the same. When the AP has an air interface, the services that can support the OFDMA mechanism and/or the MU-MIMO mechanism do not need to acquire TXOPs through tokens to compete for transmission, but use the EDCA mechanism. EDCAF parameters are used to compete for transmission; due to the different performances of the two in the common window, the aggregation methods will be different, that is, one is based on user aggregation, and the other is based on service aggregation.

Step 208, obtain Airtime1.

In this embodiment, Airtime1 is the air time for the Trigger frame. The air interface time of the Trigger frame is relatively determined. Because after the user is associated, UL-OFDMA random access can be performed through the UORA procedure. Therefore, Airtime1 can be roughly estimated based on the number of users, user types, and bandwidth requested by users.

Step 209, obtain Airtime2.

In this embodiment, Airtime2 is the air time for the EDCA frame. Mainly used for devices in the basic service set that cannot support OFDMA mechanism and/or MU-MIMO mechanism. These devices also have TIDs with high latency requirements. It needs to be reflected in the scheduling timing. For the TID of such devices, the main strategy is to ensure the delay and take into account the bandwidth. Airtime2 can be roughly estimated based on the number of users, user types, and bandwidth requested by users. Given that Airtime2 has fewer users and lower bandwidth, it may not be necessary to allocate each scheduling period (refer to user delay configuration).

Step 210, normalize Airtime1 and Airtime2, obtain an initial scheduling scheme, adjust the initial scheduling scheme according to the obtained EDCA parameters, and send MPDUs.

In this embodiment, the normalization is to simplify the subsequent calculation, and convert the dimensioned Airtime1 and Airtime2 into dimensionless scalar data. A specific normalization method is to express Airtime1 and Airtime2 with a scheduling period, for example, Airtime1=13T, Airtime2=15T, that is, Airtime=nT, and T is the scheduling period. Because the initial scheduling period is an ideal scheduling scheme at the software level, and hardware limitations need to be considered, so fine-tuning is performed according to the EDCA parameters.

It should be noted that synchronization needs to be performed before sending the MPDU, and a synchronization method for reference is to perform synchronization according to the standard 1PPS per second and Beacon frames specified by the precise clock synchronization protocol of the network measurement and control system. Of course, the above is only an example, and in actual situations, it can be any synchronization method that can realize synchronization.

It should be noted that, in this embodiment, considering the bit error rate and other issues, the adjusted parameter may also be a channel quality indicator CQI parameter to further improve the correctness of the transmitted data.

In the actual scheduling process, with the release of air interface time of legacy users, the Airtime obtained by users supporting OFDMA and/or MU-MIMO mechanism will be refreshed to a larger value. details as follows:

If there is one user STA1_TID7 that supports OFDMA and/or MU-MIMO, the others are users that do not support OFDMA and/or MU-MIMO. The scheduling period T=10ms. The QOS delay requirement of STA5_TID7 is up to 10ms, the delay requirement of STA4_TID5 is 20ms, the delay requirement of STA3_TID5 is 30ms, and the delay requirement of STA2_TID3 is 40ms. Through air interface time estimation, TXOP can be obtained. Through token issuance, in the first scheduling cycle T1, all users will be allocated a TXOP. In the second scheduling period T2, STA2_TID3 cannot acquire TXOP because the token is exhausted. In the third scheduling period T3, the STA3_TID5 token is exhausted and the TXOP cannot be acquired. In the fourth scheduling period T3, the STA4_TID5 token is exhausted and TXOP cannot be acquired. When all Legacy user tokens are exhausted, the tokens of each STA_TID are refreshed to the initial value until a new user joins the schedule.

The second embodiment of the present application, on the basis of achieving the beneficial effects brought by the first embodiment, aggregates service data, acquires MPDU frames, and transmits data by transmitting MPDU frames, thus increasing the effectiveness of the transmission process. The bandwidth guarantees the channel bandwidth during transmission. On the basis of guaranteeing the delay, the channel bandwidth is further guaranteed. Moreover, in the whole scheduling process, multiple services of multiple users are scheduled to ensure the performance of multiple users.

The third embodiment of the present application relates to a scheduling device, the process of which is shown in FIG. 4 , including:

The information acquisition module 401 is used to acquire the scheduling information and service data of the service, wherein the scheduling information includes service delay requirements, user types, EDCA parameters, beacon interval time slots, service data structure parameters, antenna information and resource unit RU The allocation result, the service delay is required to carry the service priority;

The Airtime obtaining module 402 is configured to obtain service delay parameters and scheduling period according to service delay requirements, and obtain the air interface time Airtime of the service according to the data structure parameters of the service;

The scheduling module 403 is configured to obtain the MAC protocol data unit MPDU queue according to the service data, obtain the initial scheduling scheme according to the scheduling period, Airtime, the number of user types and the MPDU queue, adjust the initial scheduling scheme according to EDCA parameters, and send according to the adjusted scheduling scheme business data.

For the specific implementation method of the technical solution provided by this embodiment, reference may be made to the information processing methods provided by the first and second embodiments above, and details are not described herein again.

The fourth embodiment of the present application relates to an electronic device, as shown in FIG. 5 , including:

at least one processor 501; and,

memory 502 in communication with at least one processor 501; wherein,

The memory 502 stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor 501 to enable the at least one processor 501 to execute the scheduling methods of the first and second embodiments of the present application.

The memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory. The bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface between the bus and the transceiver. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor.

The processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data used by the processor in performing operations. Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific examples for realizing the present application, and in practical applications, various changes can be made in form and details without departing from the spirit and the spirit of the present application. scope.

Claims

A scheduling method, applied to a wireless local area network, includes:

Obtaining the scheduling information and service data of the service, wherein the scheduling information includes service delay requirements, user types, EDCA parameters, and data structure parameters of the service;

Acquiring service delay parameters, scheduling period and service priority according to the service delay requirement;

Obtain the minimum air interface time Airtime of the service according to the data structure parameter of the service;

Acquire the MAC protocol data unit MPDU queue corresponding to the service data according to the service priority;

Obtain an initial scheduling scheme according to the scheduling period, the Airtime, the user type and the MPDU queue;

The initial scheduling scheme is adjusted according to the EDCA parameter, and the service data is sent according to the adjusted scheduling scheme.
The method according to claim 1, wherein the obtaining the scheduling period comprises:

Get the beacon interval time slot Bacon parameter;

Use the Bacon parameter as the scheduling period; or,

The minimum value of the delay parameters is used as the scheduling period.
The method according to claim 1 or 2, wherein the obtaining the air interface time Airtime of the service according to the data structure parameter of the service comprises:

Get the rate of the service scheduling period;

The Airtime is acquired according to the service scheduling period and the structural parameters of the service.
The method according to any one of claims 1 to 3, wherein the obtaining an initial scheduling scheme according to the scheduling period, the Airtime, the user type and the MPDU queue comprises:

Determine whether the service supports the OFDMA mechanism and/or the MU-MIMO mechanism according to the user type;

When the service supports the OFDMA mechanism and/or the MU-MIMO mechanism, the Airtime of the service is the first type of Airtime;

When the service does not support the OFDMA mechanism and does not support the MU-MIMO mechanism, the Airtime of the service is the second type of Airtime;

Summing up the first type of Airtime and the second type of Airtime respectively to obtain Airtime1 and Airtime2;

Normalize the Airtime1 and the Airtime2 according to the scheduling period;

The initial scheduling scheme is acquired according to the normalized Airtime1, the normalized Airtime2 and the MPDU queue.
The method according to any one of claims 1 to 4, wherein the acquiring the MAC protocol data unit MPDU queue corresponding to the service data according to the service delay priority comprises:

Acquire the MAC service data unit MSDU according to the service data;

Acquire the MSDU queue according to the service delay priority and the MSDU;

Obtain the initial token number of the service according to the service delay parameter;

Determine the aggregation method according to the user type;

Obtain antenna information and RU resource allocation results;

The MSDU queue is aggregated in the aggregation manner according to the initial token number of the service, the antenna information and the RU allocation result, and the MPDU queue is obtained.
The method according to claim 5, wherein the MSDU is aggregated according to the aggregation mode according to the initial token number of the service, the antenna information and the resource unit allocation result, and the MPDU is acquired Queue, including:

Start a timer according to the original number of tokens of the service and update the number of tokens of the service, and obtain the count value of the timer;

Obtain the transmission opportunity TXOP according to the count value of the timer;

Aggregate the MSDU queue according to the TXOP and the user type to obtain an A-MSDU subframe queue;

Acquire an A-MPDU subframe queue according to the A-MSDU subframe queue;

The A-MPDU subframes in the A-MPDU subframe queue are aggregated according to the aggregation mode according to the number of tokens of the service, the antenna information and the RU allocation result to obtain the MPDU queue.
The method of any one of claims 1 to 6, further comprising:

Obtain the channel quality indicator CQI parameter;

The initial scheduling scheme is adjusted according to the CQI parameter.
The method according to any one of claims 1 to 7, wherein before the data transmission according to the adjusted scheduling scheme, comprises:

The synchronization is performed according to the standard second pulse 1PPS and Beacon frame stipulated by the precise clock synchronization protocol of the network measurement and control system.
A scheduling device, comprising:

an information acquisition module, configured to acquire scheduling information and service data of services, wherein the scheduling information includes service delay requirements, user types, EDCA parameters, and data structure parameters of services;

The Airtime obtaining module is used to obtain the service delay parameter, scheduling period and service priority according to the service delay requirement, and obtain the air interface time Airtime of the service according to the data structure parameter of the service;

A scheduling module, configured to obtain the MAC protocol data unit MPDU queue corresponding to the service data according to the service priority, obtain an initial scheduling scheme according to the scheduling period, the Airtime, the user type and the MPDU queue, and according to the The EDCA parameter adjusts the initial scheduling scheme, and sends the service data according to the adjusted scheduling scheme.
An electronic device comprising:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the execution of any one of claims 1 to 8 the scheduling method described.