Data transmission method and device, computer-readable storage medium and electronic device

Abstract

The embodiments of the present disclosure provide a data transmission method, a data transmission device, a computer-readable storage medium, and an electronic device. The data transmission method includes the steps of: when an access point (AP) determines that data transmission in an enhanced distributed channel access (EDCA) mode does not meet a low latency requirement, entering an enhanced hybrid control channel access (HCCA) mode, in which the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify that all APs need to occupy a first transmission opportunity (TXOP) for data transmission; when it is determined that the AP has not completed data transmission after the first TXOP is finished, the AP repeatedly broadcasts a target frame to all STAs to notify that the AP needs to occupy another TXOP for data transmission until the AP completes data transmission; and when it is determined that the AP has completed data transmission after the first TXOP is finished, the AP enters a data transmission contention period.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to Chinese Patent Application No. 202111242438.7 filed on October 25, 2021, the entire contents of which are incorporated herein by reference. (Technical field) TECHNICAL FIELD Embodiments of the present disclosure relate to the field of communications, and in particular to a data transmission method and apparatus, a computer-readable storage medium, and an electronic device. [Background technology]

[0002] In the Enhanced distributed channel access (EDCA) random channel access mode, in the case of multi-user transmission in a complex environment, it cannot guarantee that the transmission delay is controllable. That is, in a scenario where multi-user low-latency data transmission cannot be completed within a single transmission opportunity (TXOP) time contended by an access point (AP), the random access characteristics of the EDCA random channel access mode make it impossible to control the time at which the AP re-acquires a TXOP for multi-user transmission. As a result, it may not be possible to effectively guarantee that the low-latency data transmission is completed within the specified delay requirement. Summary of the Invention [Means for solving the problem]

[0003] According to an embodiment of the present disclosure, a data transmission method is provided, including: when an access point (AP) determines that data transmission in a conventional enhanced distributed channel access (EDCA) mode does not meet a low-latency requirement, entering an enhanced hybrid control channel access (HCCA) mode; in the enhanced HCCA mode, the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify all the STAs that the AP needs to occupy a first transmission opportunity (TXOP) for data transmission; when it is determined that the AP has not completed the data transmission after the first TXOP has ended, the AP repeatedly broadcasts the target frame to all the STAs to notify all the STAs that the AP needs to occupy another TXOP for data transmission until the AP completes the data transmission; and when it is determined that the AP has completed the data transmission after the first TXOP has ended, the AP enters a data transmission contention period (CP).

[0004] According to an embodiment of the present disclosure, a data transmission device is provided, which includes: a broadcast module configured to enter an enhanced hybrid control channel access (HCCA) mode when it is determined that data transmission in a conventional enhanced distributed channel access (EDCA) mode does not meet a low-latency requirement; and in the enhanced HCCA mode, the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify all the STAs that the AP needs to occupy a first transmission opportunity (TXOP) for data transmission; and an execution module configured to, when it is determined that the AP has not completed data transmission after the first TXOP has ended, repeatedly perform the operation of broadcasting the target frame to all the STAs to notify all the STAs that the AP needs to occupy another TXOP for data transmission until the AP completes data transmission; and, when it is determined that the AP has completed data transmission after the first TXOP has ended, the AP enters a data transmission contention period.

[0005] According to an embodiment of the present disclosure, there is also provided a computer-readable storage medium having a computer program stored thereon, the computer program performing the steps of the data transmission method when executed by a processor.

[0006] According to an embodiment of the present disclosure, there is also provided an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and wherein the steps of the data transmission method are performed when the processor executes the computer program.

[0007] The drawings described herein are intended to facilitate a better understanding of the technical solution of the present disclosure and constitute a part of this application. The exemplary embodiments of the present disclosure and the description thereof are intended to interpret the technical solution of the present disclosure and do not constitute undue limitations on the technical solution of the present disclosure. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram of a hybrid control channel access (HCCA) mode in an embodiment of the present disclosure. [Figure 2] FIG. 2 is a hardware structural block diagram of a mobile terminal that executes the data transmission method of the embodiment of the present disclosure; [Figure 3] 1 is a flowchart of a data transmission method according to an embodiment of the present disclosure. [Figure 4] FIG. 1 is a schematic diagram of an enhanced HCCA mode according to an embodiment of the present disclosure. [Figure 5] FIG. 1 is a schematic diagram of a format of a buffer status report (BSR) control field in an embodiment of the present disclosure. [Figure 6] FIG. 1 is a schematic diagram of a format of a BSR control field according to an embodiment of the present disclosure. [Figure 7] FIG. 2 is a structural block diagram of a data transmission device according to an embodiment of the present disclosure; [Figure 8] 1 is a structural diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0009] In order to allow those skilled in the art to better understand the solutions of the present disclosure, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure in combination with the drawings of the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments that those skilled in the art can obtain without creative work should fall within the protection scope of the present disclosure.

[0010] It should be noted that the terms "first," "second," etc. in the specification, claims, and drawings of this disclosure are used to distinguish between similar objects and are not intended to limit a particular order or sequence. Terms used in this manner should be understood to be interchangeable where appropriate, such that the embodiments of the present disclosure described herein can be performed in orders other than those illustrated or described herein. Furthermore, the terms "comprise," "have," and any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the explicitly recited steps or units, but may include other steps or units not explicitly recited or inherent to the process, method, system, product, or apparatus.

[0011] The Hybrid Coordination Function Controlled Channel Access (HCCA) mode is divided into a contention-free period (CFP) and a contention period (CP). The contention period (CP) is similar to Enhanced Distributed Channel Access (EDCA). In the contention-free period (CFP), the AP sends a QoS CF-Poll (Contend Free Poll) unicast polling frame to designate each STA for transmission. For a given STA (Station) designated Transmit Opportunity (TXOP), the time is determined by the Access Point (AP) and is only used for single user (SU) transmission. Figure 1 is a schematic diagram of the HCCA mode of an embodiment of the present disclosure. As shown in Figure 1, 1) At the start of the contention-free period, the AP sequentially allocates and transmits transmission opportunities (TXOPs) to each STA and the AP itself (for simplicity, the TXOPs allocated by the AP to itself are not shown in Figure 1). During the time when the AP or the STA occupies the TXOP, other devices must set their own Network Allocation Vector (NAV) and cannot actively transmit data.

[0012] 2) At the end of the contention-free period, when the AP completes polling and is about to terminate the CFP, the AP actively transmits a QoS CF-Poll frame, in which the RA address is set to the AP itself and the Duration / ID field is set to 0. After receiving this QoS CF-Poll frame, all STAs set their NAV to 0, enter EDCA mode, and start competing for transmission opportunities (TXOPs).

[0013] 3),In the contention period phase, in the EDCA mode, the AP can also perform polling transmission according to the contention-free period mode after contending for the TXOP.

[0014] However, since the 802.11AX network focuses on multi-user transmission scenarios in high-density environments, when there are too many users, the HCCA mode cannot complete polling scheduling for all STAs within one beacon period, and as the number of users increases, the overhead of user scheduling processing at the AP increases significantly, so the above function is not implemented in multi-user transmission in the 802.11AX network.

[0015] The method according to the embodiment of the present application may be implemented in a mobile terminal, a computer terminal, or a similar computing device. Taking the method according to the embodiment of the present disclosure as an example, FIG. 2 is a hardware structural block diagram of a mobile terminal that executes the data transmission method according to the embodiment of the present disclosure. As shown in FIG. 2, the mobile terminal may include one or more (only one is shown in FIG. 2) processors 202 (the processors 202 may include, but are not limited to, processing devices such as microprocessors (MCUs) or programmable logic devices (FPGAs)) and memory 204 for storing data. In some embodiments, the mobile terminal may further include a transmission device 206 and an input / output device 208 for communication functions. Those skilled in the art will appreciate that the structure shown in FIG. 2 is merely exemplary and is not intended to limit the structure of the mobile terminal. For example, the mobile terminal may include more or fewer components than those shown in FIG. 2, or may have a different configuration than that shown in FIG. 2.

[0016] The memory 204 can be used to store computer programs, such as software programs and modules of application software, such as a computer program corresponding to the data transmission method of an embodiment of the present disclosure. The processor 202 executes the computer programs stored in the memory 204 to perform various functional applications and data processing, i.e., to realize the above-described method. The memory 204 can include high-speed random access memory and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some embodiments, the memory 204 can further include memory located remotely from the processor 202, which can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0017] The transmission device 206 is used to receive or transmit data over a network. A specific example of the network mentioned above may include a wireless network provided by a communication provider of the mobile terminal. In some embodiments, the transmission device 206 includes a network interface controller (NIC) that can connect to other network devices via a base station and communicate with the Internet. In some embodiments, the transmission device 206 may be a radio frequency (RF) device for wirelessly communicating with the Internet.

[0018] In this embodiment, a data transmission method is provided, and FIG. 3 is a flowchart of the data transmission method according to the embodiment of the present disclosure. As shown in FIG. 3, the data transmission method includes the following steps S302 and S304.

[0019] In step S302, if the access point (AP) determines that data transmission in the enhanced distributed channel access (EDCA) mode does not meet the low latency requirement, it enters the enhanced hybrid control channel access (HCCA) mode, in which the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify all the STAs that the AP needs to occupy a first transmission opportunity (TXOP) for data transmission.

[0020] In step S304, if it is determined that the AP has not completed data transmission after the first TXOP ends, the AP repeatedly broadcasts the target frame to all the STAs to notify all the STAs that the AP needs to occupy another TXOP for data transmission until the AP completes data transmission; if it is determined that the AP has completed data transmission after the first TXOP ends, the AP enters a data transmission contention period (CP).

[0021] If the above steps determine that data transmission in EDCA mode does not meet the low-latency requirement, the access point (AP) switches to an enhanced hybrid control channel access (HCCA) mode. In the enhanced HCCA mode, the AP broadcasts a target frame to all STAs to inform them that the AP needs to occupy a first TXOP for data transmission. If it is determined that the AP will not complete the data transmission after the first TXOP ends, the AP repeatedly broadcasts a target frame to all STAs to inform them that the AP needs to occupy another TXOP for data transmission until the AP completes the data transmission. By repeatedly broadcasting the target frame to all STAs, the AP can continuously obtain TXOPs for data transmission multiple times, thereby ensuring the low-latency user's transmission latency requirement. This achieves the effect of improving data transmission efficiency.

[0022] The execution body of the above steps may be an access point, for example, an access point in an 802.11AX network, or the execution body of the above steps may be, but is not limited to, other processing devices or processing units with similar processing capabilities. Hereinafter, the above operations will be described as being performed by an access point (this is only an illustrative description, and in actual operation, the above operations may be performed by other devices or modules).

[0023] In the above steps, if the access point (AP) determines that the data transmission in the EDCA mode does not meet the low-latency requirement, it enters the enhanced HCCA mode. For example, in the EDCA mode, if the multi-user low-latency data transmission cannot be completed within the time of one TXOP contended by the AP, due to the random access characteristics of the EDCA random channel access mode, the time when the AP re-acquires the TXOP for multi-user transmission cannot be controlled, and as a result, it may not be possible to effectively guarantee that the low-latency data transmission is completed within the predetermined latency requirement. After entering the enhanced HCCA mode, the AP broadcasts a target frame to all stations (STAs) included in the target base station subsystem (BSS), for example, during the contention-free period of the enhanced HCCA mode, thereby achieving improved QoS. The AP notifies all STAs of this BSS through a CF-Poll frame, thereby notifying all STAs that the AP needs to occupy the first transmission opportunity TXOP for data transmission. If it is determined that the AP will not complete the data transmission after the first TXOP ends, the AP broadcasts a target frame to all STAs to notify all STAs that the AP needs to occupy another TXOP for data transmission until the AP completes the data transmission. That is, the AP can invoke the improved QoS CF-Poll frame multiple times to achieve multiple TXOP occupancy. If it is determined that the AP has completed the data transmission after the first TXOP ends, the AP enters a data transmission contention period (CP). The embodiment of the present disclosure can achieve the goal of continuously obtaining TXOPs for data transmission multiple times, thereby achieving the effect of controllable multi-user transmission delay.

[0024] In some embodiments, the data transmission method further includes, before the AP broadcasts the target frame to all stations (STAs) included in a target base station subsystem (BSS), the AP determines whether data transmission in EDCA mode meets the low-latency requirement in the following manner: the AP determines whether uplink data transmission meets the low-latency requirement, or the AP determines whether downlink data transmission meets the low-latency requirement. That is, the AP can determine whether data transmission in EDCA mode meets the low-latency requirement by determining whether uplink data transmission meets the low-latency requirement or by determining whether downlink data transmission meets the low-latency requirement. The above embodiments can achieve the purpose of determining whether data transmission in EDCA mode meets the low-latency requirement.

[0025] In some embodiments, the step of the AP determining that the uplink data transmission does not meet the low-latency requirement includes the steps of the AP obtaining a first Buffer Status Report (BSR) frame transmitted by a first STA included in all the STAs, and determining that the uplink data transmission does not meet the low-latency requirement if the AP determines that the first BSR frame includes a target field and the value of the target field is a first value. That is, the AP obtains the first BSR frame transmitted by the STA and determines whether the uplink data transmission meets the low-latency requirement based on whether the value of the target field included in the first BSR frame is a first value. For example, the AP can add a target field to a BSR control field and determine that the uplink data transmission does not meet the low-latency requirement if the value of the target field is 1, 0, or another value. The above embodiment achieves the objective of determining whether the uplink data transmission meets the low-latency requirement based on the value of the new target field in the BSR frame.

[0026] In some embodiments, the step of the AP determining that the uplink data transmission does not meet the low-latency requirement includes performing the following operations in one evaluation cycle: the AP records the data amount of low-latency transmissions completed by second STAs included in all the STAs when triggering uplink multi-user (UL MU) data transmission within each TXOP time; and the AP determines that the uplink data transmission does not meet the low-latency requirement if it determines that the total data amount of uplink low-latency transmissions completed by the second STAs within a predetermined number of consecutive TXOP times is less than the buffered low-latency data amount initially reported by the second STA to the AP. In the above embodiment, in one evaluation cycle, the AP records the data amount of low-latency transmissions completed by the STA when triggering UL MU data transmission (e.g., UL-OFDMA and UL-MU MIMO) within each TXOP time, and the AP determines the total data amount of uplink low-latency transmissions completed by the STA in a predetermined number of consecutive TXOPs, where the predetermined number may be N times (e.g., 3 times, 5 times, or other times). If it is determined that the total data amount of uplink low-latency transmissions completed by the STA is less than the buffered low-latency data amount initially reported by the STA to the AP, it can determine that the uplink data transmission does not meet the low-latency requirement. In practical applications, the AP can collect low-latency information in advance. For example, the STA can explicitly notify the AP of buffered low-latency data information, such as the transmission time M (e.g., in milliseconds) and data size required for the low-latency data, and the AP buffers the low-latency data information to be transmitted to each STA in a transmission queue.

[0027] The above embodiment achieves the purpose of determining whether uplink data transmission meets the low latency requirement by evaluating the data volume of uplink low latency transmission in one evaluation cycle.

[0028] In some embodiments, the step of the AP determining that the uplink data transmission does not meet the low-latency requirement includes the step of the AP determining that the uplink data transmission does not meet the low-latency requirement if the AP determines that the uplink data transmission does not meet the low-latency requirement in multiple consecutive evaluation cycles. In the above embodiments, if the AP determines that the uplink data transmission does not meet the low-latency requirement in multiple consecutive evaluation cycles, for example, if the AP determines that the uplink data transmission does not meet the low-latency requirement in three, five, or other consecutive evaluation cycles, it can determine that the consecutive data transmissions do not meet the low-latency requirement. In practical applications, if it is determined in one evaluation cycle that the uplink data transmission does not meet the low-latency requirement, it can be determined that the burst data transmission does not meet the low-latency requirement; if it is determined in multiple consecutive evaluation cycles that the uplink data transmission does not meet the low-latency requirement, it can be determined that the consecutive data transmissions do not meet the low-latency requirement, and the scenario in which the burst data transmission may not meet the low-latency requirement can be eliminated. The above embodiment can achieve the purpose of improving the accuracy of determining whether the data transmission meets the low-latency requirement.

[0029] In some embodiments, the step of the AP determining that the downlink data transmission does not meet the low-latency requirement includes performing the following operations in one evaluation cycle: the AP records the data amount of the low-latency transmissions completed by the AP when triggering downlink multi-user (DL MU) data transmission within each TXOP time; and the AP determines that the downlink data transmission does not meet the low-latency requirement if it determines that the total data amount of the downlink low-latency transmissions completed by the AP within a predetermined number of consecutive TXOP times is less than the amount of downlink low-latency data buffered by the AP for the first time. In the above embodiment, in one evaluation cycle, the AP records the data amount of low-latency transmissions completed by the AP when triggering DL MU data transmission (e.g., DL-OFDMA and DL-MU MIMO) within each TXOP time, and the AP determines the total data amount of downlink low-latency transmissions completed by the AP in a predetermined number of consecutive TXOPs, where the predetermined number may be N (e.g., 3, 5, or other times). If it is determined that the total data amount of downlink low-latency transmissions completed by the AP is less than the amount of downlink low-latency data buffered by the AP for the first time, it can be determined that the downlink data transmission does not meet the low-latency requirement. In practical applications, the AP can collect low-latency information in advance. For example, the STA can explicitly notify the AP of buffered low-latency data information, such as the transmission time M (e.g., in milliseconds) and data size required for the low-latency data. The AP buffers the low-latency data information to be transmitted to each STA in a transmission queue. The above embodiment achieves the purpose of determining whether downlink data transmission meets the low latency requirement by evaluating the data amount of low latency transmission in one evaluation cycle.

[0030] In some embodiments, the step of the AP determining that the downlink data transmission does not meet the low-latency requirement includes the step of the AP determining that the downlink data transmission does not meet the low-latency requirement if the AP determines that the downlink data transmission does not meet the low-latency requirement in multiple consecutive evaluation cycles. In the above embodiments, if the AP determines that the downlink data transmission does not meet the low-latency requirement in multiple consecutive evaluation cycles, for example, if the AP determines that the downlink data transmission does not meet the low-latency requirement in three, five, or other consecutive evaluation cycles, it can determine that the consecutive data transmissions do not meet the low-latency requirement. In practical applications, if it is determined in one evaluation cycle that the downlink data transmission does not meet the low-latency requirement, it can be determined that the burst data transmission does not meet the low-latency requirement; if it is determined in multiple consecutive evaluation cycles that the downlink data transmission does not meet the low-latency requirement, it can be determined that the consecutive data transmissions do not meet the low-latency requirement, and the scenario in which the burst data transmission may not meet the low-latency requirement can be eliminated. The above embodiment can achieve the purpose of improving the accuracy of determining whether the data transmission meets the low-latency requirement.

[0031] In some embodiments, the predetermined number of times is determined by determining the transmission time M required for the low-latency data notified to the AP by the second STA and the time length T of the maximum TXOP on the AP side, and rounding up the ratio between the transmission time M and the time length T to obtain the predetermined number of times. In the above embodiments, the predetermined number of times can be obtained by first determining the transmission time M required for the low-latency data notified to the AP by the second STA and the time length T of the maximum TXOP on the AP side, and then rounding up the ratio between the transmission time M and the time length T, and the above embodiments achieve the purpose of determining the predetermined number of times.

[0032] In some embodiments, the data transmission method further includes determining that data transmission in EDCA mode can meet the low-latency requirement, and switching from the enhanced HCCA mode to the EDCA mode and performing data transmission in the EDCA mode. In the above embodiment, if it is determined that data transmission in EDCA mode can meet the low-latency requirement, the AP switches from the enhanced HCCA mode to the conventional EDCA mode. In a practical application, if it is determined that uplink data transmission and downlink data transmission in EDCA mode simultaneously meet the low-latency requirement and it is determined that switching to EDCA mode is possible, after the current transmission in the enhanced HCCA mode is completed and the CP phase is entered, a QoS CF-Poll frame can be omitted and the system enters EDCA mode. The above embodiment achieves the objective of enabling switching from the enhanced HCCA mode to the EDCA mode.

[0033] In some embodiments, determining whether data transmission in EDCA mode can meet the low-latency requirement includes the AP determining whether uplink data transmission in EDCA mode can meet the low-latency requirement, and the AP determining whether downlink data transmission in EDCA mode can meet the low-latency requirement. In the above embodiments, if the AP determines that both uplink data transmission and downlink data transmission in conventional EDCA mode can meet the low-latency requirement, it can determine that data transmission in EDCA mode can meet the low-latency requirement. The above embodiments achieve the purpose of determining whether data transmission in EDCA mode can meet the low-latency requirement.

[0034] In some embodiments, the step of the AP determining that uplink data transmission in the EDCA mode can meet the low-latency requirement includes the steps of the AP obtaining a second Buffer Status Report (BSR) frame transmitted by a third STA among all the STAs, and determining that the second BSR frame includes a target field and that the uplink data transmission in the EDCA mode can meet the low-latency requirement if the value of the target field is a second value. In the above embodiments, the AP obtains the second BSR frame transmitted by the STA and determines whether the uplink data transmission meets the low-latency requirement based on whether the value of the target field included in the second BSR frame is the second value. For example, the AP may add a target field to a BSR control field and determine that the uplink data transmission meets the low-latency requirement if the value of the target field is 0, 1, or another value. In practical applications, the AP may be configured to determine that the uplink data transmission can meet the low-latency requirement if the second value is 0, and determine that the uplink data transmission cannot meet the low-latency requirement if the second value is 1. The above embodiment achieves the goal of determining whether uplink data transmission meets the low latency requirement based on the value of the new target field in the BSR frame.

[0035] In some embodiments, the step of the AP determining that uplink data transmission in the EDCA mode can meet the low-latency requirement includes the steps of the AP determining a maximum amount of data successfully transmitted in the uplink direction over multiple consecutive evaluation cycles in the EDCA mode and determining this maximum as a first maximum value, and determining that uplink data transmission in the EDCA mode can meet the low-latency requirement if the AP determines that the amount of uplink buffered data over multiple consecutive evaluation cycles in the enhanced HCCA mode is not greater than the first maximum value. For example, the AP may record a maximum amount of data successfully transmitted in the uplink direction over multiple consecutive evaluation cycles in the EDCA mode (e.g., three, five, or other times) and determine this maximum as a first maximum value; and may consider that the EDCA mode can support transmission of the current uplink buffered data if it is subsequently determined that the amount of uplink buffered data over multiple consecutive evaluation cycles in the enhanced HCCA mode (e.g., three, five, or other times) is not greater than the first maximum value. The above embodiment achieves the purpose of determining whether the EDCA mode can support the transmission of uplink buffered data.

[0036] In some embodiments, the step of the AP determining that downlink data transmission in the EDCA mode can meet the low-latency requirement includes the steps of the AP determining a maximum amount of data successfully transmitted in the downlink direction over multiple consecutive evaluation cycles in the EDCA mode and determining this maximum as a second maximum value, and determining that downlink data transmission in the EDCA mode can meet the low-latency requirement if the AP determines that the amount of downlink buffered data over multiple consecutive evaluation cycles in the enhanced HCCA mode is not greater than the second maximum value. For example, the AP may record a maximum amount of data successfully transmitted in the downlink direction over multiple consecutive evaluation cycles in the EDCA mode (e.g., three, five, or other times), determine this maximum as a second maximum value, and consider that the EDCA mode can support transmission of the current downlink buffered data if it is subsequently determined that the amount of downlink buffered data over multiple consecutive evaluation cycles in the enhanced HCCA mode (e.g., three, five, or other times) is not greater than the second maximum value. The above embodiment achieves the purpose of determining whether the EDCA mode can support the transmission of downlink buffered data.

[0037] In some embodiments, the data transmission method further includes the step of, after the AP enters a data transmission contention period (CP), if the AP contends for a second TXOP in the CP, the AP broadcasts the target frame to all the STAs to notify all the STAs that the AP needs to occupy the second TXOP for data transmission. In the above embodiment, after the AP enters a data transmission contention period (CP), if the AP contends for a second TXOP in the CP, the AP broadcasts a target frame to all STAs to notify all the STAs that the AP needs to occupy the second TXOP for data transmission. In practical applications, to ensure controllability of delays in multi-user transmissions, an AP does not perform SU transmissions in a CFP period, but can perform SU transmissions (to achieve backward compatibility) when it contends for a TXOP in a CP period.

[0038] Obviously, the above-described embodiments are only a part of the embodiments of the present disclosure, but not all of the embodiments. The present disclosure will be specifically described below with reference to specific examples.

[0039] FIG. 4 is a schematic diagram of an extended HCCA mode according to an embodiment of the present disclosure. As shown in FIG. 4, by combining the HCCA mode function of controlling and scheduling TXOPs during contention-free periods with multi-user transmission in an 802.11AX network, we propose an extended HCCA mode with the following four main features:

[0040] 1),In the contention-free period, the AP notifies all STAs of this BSS through the improved QoS CF-Poll frame (corresponding to the above target frame) that it will occupy the TXOP for transmission. After the TXOP ends, the AP can invoke the improved QoS CF-Poll frame again to achieve multiple TXOP occupancies.

[0041] 2) Perform multi-user transmission supported by 802.11AX networks, including UL / DL MU-MIMO and UL / DL OFDMA, within the TXOP time occupied by the AP.

[0042] 3),To ensure the controllability of delay in multi-user transmission, the AP can not perform SU transmission during the contention period, but can perform SU transmission when contending for TXOP during the CP period (backward compatibility).

[0043] 4) Since multi-user transmission is triggered by the AP during the contention-free period, there are no problems that exist in multi-user scenarios (for example, 802.11AX networks focus on multi-user transmission scenarios in high-density environments, and when the number of users is too large, HCCA cannot complete the polling scheduling of all STAs in one beacon cycle, or as the number of users increases, the overhead of user scheduling processing at the AP increases significantly).

[0044] The following describes switching between the EDCA mode and the enhanced HCCA mode in an embodiment of the present disclosure.

[0045] Specific example 1 is a flowchart for switching from the EDCA mode to the enhanced HCCA mode.

[0046] The following will explain three aspects: collection of low-delay information, criteria for judging the transmission status, and mode for judging the transmission status.

[0047] 1) Collection of low-latency information In the uplink direction, the STA can explicitly notify the AP of buffered low-latency data information (transmission time M (for example, in milliseconds) and data size required for the low-latency data).

[0048] In the downlink direction, at the AP, a transmit queue buffers low latency data information to be transmitted to each STA.

[0049] 2) Criteria for determining low-latency transmission conditions Judgment criteria 1 In the uplink direction, the amount of data of low-latency transmissions completed by the STA when triggering UL MU transmission (including UL-OFDMA and UL-MU MIMO) within one TXOP time is recorded. If the total amount of data of uplink low-latency transmissions completed by the STA in N consecutive TXOPs (corresponding to the above-mentioned predetermined number of consecutive TXOPs) is smaller than the buffered low-latency data amount initially reported to the AP, it is considered that the current STA uplink transmission does not meet the low-latency requirement.

[0050] Similarly, in the downlink direction, the total amount of low-latency data for downlink transmissions in N consecutive TXOPs is recorded, and compared with the amount of downlink low-latency data buffered initially at the AP. If the recorded total amount of data is less than the amount of buffered data, it is considered that the current downlink transmission to the STA does not meet the delay requirement.

[0051] Note that N=ceiling(M / Tmax), where ceiling() represents the rounding up operation (the maximum TXOP time on the AP side is Tmax, and in a complex user scenario, if low-latency data transmission cannot be completed within N TXOP transmission intervals, it is considered that the low-latency requirement is not met). N consecutive TXOPs function as one evaluation cycle.

[0052] If the condition in either the uplink direction or the downlink direction in Criterion 1 is not met, it is determined that the burst data transmission does not meet the low latency requirement.

[0053] Judgment criteria 2 In Criterion 1, there may be a scenario in which burst data transmission does not meet the low latency requirement. To eliminate this scenario, the following Criterion 2 is proposed.

[0054] According to the judgment criterion 1, the data volume status of the uplink transmission and downlink transmission in the most recent three evaluation cycles (corresponding to the above-mentioned consecutive times) is recorded, and if the total transmission volume in either the uplink direction or the downlink direction is less than the buffered data volume for three consecutive times according to the judgment criterion 1, it is determined that the consecutive data transmissions do not satisfy the low latency requirement.

[0055] 3) Transmission status judgment mode 1. Independent decision by AP The uplink and downlink directions are evaluated by the AP according to criterion 2.

[0056] 2. Comprehensive decision by AP and STA To reduce the overhead on the AP side, the uplink direction is handled by the STA side.

[0057] In the uplink direction, the STA evaluates the uplink direction according to Criterion 2, and if the requirement for continuous low-latency data transmission is not met, it notifies the AP by adding an RFEH field to the BSR control field in the subsequent frame.

[0058] Specifically, setting the Request For Enhanced HCCA (RFEH) field to 1 indicates that the STA has determined that the current uplink continuous low-latency data transmission does not meet the low-latency requirements and recommends switching to the enhanced HCCA mode; setting it to 0 indicates that the low-latency requirements are met and recommends switching to the EDCA mode; and the absence of this RFEH field indicates that the STA has no recommendation.

[0059] FIG. 5 is a schematic diagram of a format of a BSR control field in an embodiment of the present disclosure. As shown in FIG. 5, an 802.11AX network identifies various QoS access categories through an ACI High field and feedbacks specific buffer information through a Queue Size High field. An 802.11AX network terminal can also report the buffer status of multiple QoS categories, which is fed back through an ACI Bitmap field, a TID variable (Delta TID) field, and an all queue size (Queue Size All) field of FIG. 5. The ACI Bitmap field and the Delta TID field identify multiple QoS access categories, the all queue size (Queue Size All) field indicates the corresponding buffer status, and the scaling factor field represents a scaling factor and is used to indicate the unit size of the buffer. FIG. 6 is a schematic diagram of a format of a BSR control field according to an embodiment of the present disclosure. As shown in FIG. 6, a delay tag (delay When the delay tag field is set to 1, it indicates that the buffered data is low latency data, and when the delay tag field is set to 0, it indicates that the buffered data is non-low latency data. The delay time field is the maximum time required by the STA to complete transmission of the buffered low latency data, in milliseconds. When the delay tag field is set to 0, the delay time field is not valid.

[0060] In the uplink direction, the AP side evaluates the downlink direction according to criterion 2.

[0061] Note that the buffer information described by the RFEH field, delay tag field, and delay time field is not necessarily related, i.e., the RFEH field indicates that the STA does not make a mode switch request for current buffer information, but makes a mode switch request for history buffer information.

[0062] According to the above embodiment, if the requirement for continuous low latency data transmission in the uplink or downlink is not met, the channel access mode is switched from the EDCA mode to the enhanced HCCA mode.

[0063] Specific example 2 is a flowchart for switching from the enhanced HCCA mode to the EDCA mode.

[0064] The following will explain two aspects: the criteria for determining the transmission state and the mode for determining the transmission state. 1) Criteria for determining low-latency transmission conditions Criterion 3 In the uplink direction, the amount of data successfully transmitted in the uplink direction in the last three evaluation cycles in EDCA mode (corresponding to the consecutive number of times mentioned above) is recorded, and the maximum value is set as the uplink multi-user data threshold (UL MU threshold) (corresponding to the first maximum value mentioned above). Thereafter, if the amount of uplink buffered data in three consecutive evaluation cycles in extended HCCA mode is not greater than the uplink multi-user data threshold (UL MU threshold), it is considered that the EDCA mode can support the transmission of the current uplink buffered data.

[0065] In the downlink direction, the amount of data successfully transmitted in the downlink direction in the last three evaluation cycles in EDCA mode is recorded, and the maximum value is set as the downlink multi-user data threshold (corresponding to the DL MU threshold value). Thereafter, if the amount of downlink buffered data in three consecutive evaluation cycles in extended HCCA mode is not greater than the downlink multi-user data threshold (DL MU threshold1) (corresponding to the second maximum value above), it is considered that the EDCA mode can support the transmission of the current downlink buffered data.

[0066] 2) Transmission status judgment mode 1. Independent decision by AP The AP side evaluates the uplink and downlink directions according to criterion 3.

[0067] 2. Comprehensive decision by AP and STA The AP side evaluates the downlink direction according to criterion 3.

[0068] The STA evaluates the uplink direction according to Criterion 3 and notifies the AP of the evaluation result in the RFEH field.

[0069] In the above embodiment, if it is determined that the uplink data transmission and the downlink data transmission in the EDCA mode simultaneously satisfy the low latency requirement and it is determined that switching to the EDCA mode is possible, after the current transmission in the extended HCCA mode is completed and the system enters the CP phase, the QoS CF-Poll frame cannot be called and the system enters the EDCA mode.

[0070] Note that the judgment criteria in the disclosed embodiments are applied to all STAs by default, i.e., if there are a total of n STAs, STA1 to STAn, transmitting low-latency data, and at least one STA satisfies judgment criterion 2, the AP must switch to enhanced HCCA mode; similarly, the AP can switch to EDCA mode only if all of these n STAs satisfy judgment criterion 3.

[0071] According to the embodiment of the present disclosure, an improved QoS CF-Poll frame is introduced in HCCA mode, allowing the AP to obtain TXOP multiple times in succession for multi-user transmission. In terms of channel access, scheduling is controlled by the AP, so that the transmission delay requirements of low-latency users are guaranteed. At the same time, the problem that when the number of users is too large in a multi-user transmission scenario, the HCCA mode cannot complete polling scheduling for all STAs in one beacon cycle, and as the number of users increases, the overhead of user scheduling processing at the AP increases significantly is avoided.

[0072] From the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be realized by combining software with a general hardware platform, or of course, by hardware alone, and in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present disclosure, or a part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk, etc.) and includes several instructions for causing a terminal device (such as a mobile phone, a computer, a server, or a network device) to execute the method described in the present disclosure.

[0073] In an embodiment of the present disclosure, a data transmission device is also provided, which may be applied to an access point (AP). This device is used to realize the above-mentioned embodiments, and the content already described will not be described again. As used below, the term "module" can be realized as a combination of software and / or hardware having a predetermined function. The device described in the following embodiment is preferably realized in software, but it is also possible to realize it in hardware or a combination of software and hardware.

[0074] FIG. 7 is a structural block diagram of a data transmission device according to an embodiment of the present disclosure, which may be applied to an access point (AP). As shown in FIG. 7, the device includes a broadcast module 702 and an execution module 704.

[0075] The broadcast module 702 is configured to enter an enhanced HCCA mode when it is determined that data transmission in an enhanced distributed channel access (EDCA) mode does not meet a low latency requirement, and in the enhanced hybrid control channel access (HCCA) mode, the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify all the STAs that the AP needs to occupy a first transmission opportunity (TXOP) for data transmission.

[0076] The execution module 704 is configured to, if it is determined that the AP has not completed data transmission after the first TXOP has ended, repeatedly perform the operation of the AP broadcasting the target frame to all the STAs to notify all the STAs that the AP needs to occupy another TXOP for data transmission until the AP completes data transmission; and, if it is determined that the AP has completed data transmission after the first TXOP has ended, the AP enters a data transmission contention period (CP).

[0077] In some embodiments, the data transmission device further includes a first determination module configured to determine that data transmission in EDCA mode does not meet the low latency requirement by determining that uplink data transmission does not meet the low latency requirement or by determining that downlink data transmission does not meet the low latency requirement before the AP broadcasts the target frame to all stations (STAs) included in a target base station subsystem (BSS).

[0078] In some embodiments, the first determination module can determine that the uplink data transmission does not meet the low latency requirement by obtaining a first Buffer Status Report (BSR) frame transmitted by a first STA included in all the STAs, and determining that the first BSR frame includes a target field and that the value of the target field is a first value, thereby determining that the uplink data transmission does not meet the low latency requirement.

[0079] In some embodiments, the first determination module can determine that the uplink data transmission does not meet the low latency requirement in the following manner: in one evaluation cycle, record the amount of low latency transmission data completed by second STAs included in all the STAs when triggering uplink multi-user (UL MU) data transmission within each TXOP time; and if it determines that the total amount of uplink low latency transmission data completed by the second STAs within a predetermined number of consecutive TXOP times is less than the buffered low latency data amount initially reported by the second STA to the AP, perform an operation of determining that the uplink data transmission does not meet the low latency requirement.

[0080] In some embodiments, the first determination module can determine that the uplink data transmission does not meet the low latency requirement in the following manner: if it is determined that the uplink data transmission does not meet the low latency requirement in multiple consecutive evaluation cycles, it determines that the uplink data transmission does not meet the low latency requirement.

[0081] In some embodiments, the first determination module can determine that the downlink data transmission does not meet the low-latency requirement by the following manner: in one evaluation cycle, record the amount of low-latency transmission data completed by the AP when triggering downlink multi-user (DL MU) data transmission within each TXOP time; and if it determines that the total amount of downlink low-latency transmission data completed by the AP within a predetermined number of consecutive TXOP times is less than the amount of downlink low-latency data buffered by the AP for the first time, determine that the downlink data transmission does not meet the low-latency requirement.

[0082] In some embodiments, the first determination module can determine that the downlink data transmission does not meet the low latency requirement in the following manner: if it is determined that the downlink data transmission does not meet the low latency requirement in multiple consecutive evaluation cycles, it determines that the downlink data transmission does not meet the low latency requirement.

[0083] In some embodiments, the predetermined number of times is determined by determining the transmission time M required for the low-latency data notified to the AP by the second STA and the time length T of the maximum TXOP on the AP side, and rounding up the ratio of the transmission time M to the time length T to obtain the predetermined number of times.

[0084] In some embodiments, the data transmission device further includes a second determination module configured to determine that data transmission in EDCA mode can meet a low latency requirement, and a switching module configured to switch from the enhanced HCCA mode to the EDCA mode and perform data transmission in the EDCA mode.

[0085] In some embodiments, the second determination module includes: a first determination unit configured to determine that uplink data transmission in the EDCA mode can meet a low-latency requirement; and a second determination unit configured to determine that downlink data transmission in the EDCA mode can meet a low-latency requirement.

[0086] In some embodiments, the first determination unit includes a first acquisition subunit configured to acquire a second buffer status report (BSR) frame transmitted by a third STA included in all of the STAs, and a first determination subunit configured to determine that the second BSR frame includes a target field and that uplink data transmission in the EDCA mode can meet a low latency requirement if the value of the target field is determined to be a second value.

[0087] In some embodiments, the first determination unit includes: a second determination subunit configured to determine a maximum value of the amount of data successfully transmitted in the uplink direction in a plurality of consecutive evaluation cycles in the EDCA mode and determine this maximum value as a first maximum value; and a third determination subunit configured to determine that uplink data transmission in the EDCA mode can meet the low latency requirement if it is determined that the amount of uplink buffered data in a plurality of consecutive evaluation cycles in the enhanced HCCA mode is not greater than the first maximum value.

[0088] In some embodiments, the second determination unit includes: a fourth determination subunit configured to determine a maximum value of the amount of data successfully transmitted in the downlink direction in a plurality of consecutive evaluation cycles in the EDCA mode and determine this maximum value as a second maximum value; and a fifth determination subunit configured to determine that downlink data transmission in the EDCA mode can meet a low latency requirement if it is determined that the amount of downlink buffered data in a plurality of consecutive evaluation cycles in the extended HCCA mode is not greater than the second maximum value.

[0089] In some embodiments, the data transmission device further includes a processing module configured to broadcast the target frame to all the STAs when the AP contends for a second TXOP in the CP after entering a data transmission contention period (CP) to notify all the STAs that the AP needs to occupy the second TXOP for data transmission.

[0090] Each of the above modules may be implemented in software or hardware. In the case of hardware, they may be implemented in the following manner (but not limited to this): all of the above modules may be located in the same processor, or each of the above modules may be located in different processors in any combination.

[0091] An embodiment of the present disclosure further provides a computer-readable storage medium having a computer program stored thereon, the computer program performing the steps of the above data transmission method when executed by a processor.

[0092] In some embodiments, the computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0093] An embodiment of the present disclosure further provides an electronic device, as shown in FIG. 8, including a memory 801 and a processor 802, in which a computer program is stored in the memory 801, and in which the steps of the above-described data transmission method are performed when the processor 802 executes the computer program.

[0094] In some embodiments, the electronic device may further include a transmission device and an input / output device, the transmission device being connected to the processor 802 and the input / output device being connected to the processor 802.

[0095] For specific examples, reference can be made to the examples described in the above examples and exemplary embodiments, and a description thereof will be omitted here.

[0096] Obviously, those skilled in the art should understand that each module or step of the present disclosure above may be implemented by a general-purpose computing device, may be centralized in a single computing device, or may be distributed across a network of multiple computing devices, may be implemented in program code executable by a computing device, and thus may be stored in a storage device and executed on a computing device, and in some cases, the steps shown or described in the present disclosure may be executed in an order different from that shown or described in the present disclosure, or may be implemented in respective integrated circuit modules, or multiple modules or steps thereof may be implemented in a single integrated circuit module. The present disclosure is not limited to any particular combination of hardware and software.

[0097] The above are only some of the embodiments of the present disclosure, and are not intended to limit the present disclosure, and those skilled in the art can make various modifications and changes to the present disclosure. Any modifications, equivalent replacements and improvements made within the principle of the present disclosure should be included in the protection scope of the present disclosure.

Claims

1. 1. A data transmission method, comprising: When an access point (AP) determines that data transmission in an enhanced distributed channel access (EDCA) mode does not meet a low latency requirement, it enters an enhanced hybrid control channel access (HCCA) mode, in which the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS) to notify all the STAs that the AP needs to occupy a first transmission opportunity (TXOP) for data transmission; If it is determined that the AP has not completed data transmission after the first TXOP ends, the AP repeatedly broadcasts the target frame to all the STAs to notify all the STAs that the AP needs to occupy another TXOP for data transmission until the AP completes data transmission; and after the first TXOP ends, if it is determined that the AP has completed data transmission, the AP enters a data transmission contention period (CP); Before the AP broadcasts a target frame to all stations (STAs) included in a target base station subsystem (BSS), The data transmission method further includes a step of determining that data transmission in EDCA mode does not meet the low-latency requirement by the AP determining that uplink data transmission does not meet the low-latency requirement or determining that downlink data transmission does not meet the low-latency requirement.

2. The step of the AP determining that the uplink data transmission does not meet the low latency requirement includes: The AP acquires a first Buffer Status Report (BSR) frame sent by a first STA included in all the STAs; and determining that the uplink data transmission does not meet a low latency requirement if it is determined that the first BSR frame includes a target field and the value of the target field is a first value.

3. The step of the AP determining that the uplink data transmission does not meet the low latency requirement comprises: Recording a data amount of low latency transmission completed by a second STA included in all the STAs when the AP triggers uplink multi-user (UL MU) data transmission within each TXOP time; 2. The method of claim 1, further comprising: performing an operation of determining that the uplink data transmission does not meet a low-latency requirement when the AP determines that the total amount of data of uplink low-latency transmissions completed by the second STA within a predetermined number of consecutive TXOP times is less than the amount of buffered low-latency data initially reported to the AP by the second STA.

4. The step of the AP determining that the uplink data transmission does not meet the low latency requirement includes:

4. The method of claim 3, further comprising: determining that the uplink data transmission does not meet the low latency requirement when the AP determines that the uplink data transmission does not meet the low latency requirement in multiple consecutive evaluation cycles.

5. The step of the AP determining that the downlink data transmission does not meet the low latency requirement comprises: Recording a data amount of low latency transmission completed by the AP when the AP triggers downlink multi-user (DL MU) data transmission within each TXOP time; 2. The method of claim 1, further comprising: performing an operation of determining that the downlink data transmission does not meet a low-latency requirement when the AP determines that the total amount of data of downlink low-latency transmissions completed by the AP within a predetermined number of consecutive TXOP times is less than the amount of downlink low-latency data buffered by the AP for the first time.

6. The step of the AP determining that the downlink data transmission does not meet the low latency requirement includes:

6. The method of claim 5, further comprising: determining, by the AP, that the downlink data transmission does not meet the low latency requirement if it is determined that the downlink data transmission does not meet the low latency requirement in multiple consecutive evaluation cycles.

7. The predetermined number of times is Determine a transmission time M required for the low-latency data notified to the AP by the second STA and a time length T of the maximum TXOP on the AP side; 6. The method according to claim 3 or 5, wherein the predetermined number of times is determined by rounding up the ratio of the transmission time M to the time length T.

8. determining whether data transmission in EDCA mode can meet low latency requirements; 2. The method of claim 1, further comprising: switching from the enhanced HCCA mode to the EDCA mode; and performing data transmission in the EDCA mode.

9. The step of determining that data transmission in EDCA mode can meet the low latency requirement includes:

9. The method of claim 8, comprising: the AP determining that uplink data transmission in the EDCA mode can meet a low latency requirement; and the AP determining that downlink data transmission in the EDCA mode can meet a low latency requirement.

10. The step of the AP determining that the uplink data transmission in the EDCA mode can meet the low latency requirement includes: The AP acquires a second Buffer Status Report (BSR) frame transmitted by a third STA included in all the STAs; determining that the second BSR frame includes a target field, and if the value of the target field is a second value, determining that the uplink data transmission in the EDCA mode can meet a low latency requirement; Or, determining a maximum value of the amount of data successfully transmitted in the uplink direction in a plurality of consecutive evaluation cycles in the EDCA mode by the AP, and determining the maximum value as a first maximum value; and determining, by the AP, that uplink data transmission in the EDCA mode can meet the low latency requirement if the amount of uplink buffered data in multiple consecutive evaluation cycles in the extended HCCA mode is not greater than the first maximum value.

11. The step of the AP determining that the downlink data transmission in the EDCA mode can meet a low latency requirement includes: determining a maximum value of the amount of data successfully transmitted in the downlink direction in a plurality of consecutive evaluation cycles in the EDCA mode by the AP, and determining the maximum value as a second maximum value; and determining, by the AP, that downlink data transmission in the EDCA mode can meet a low latency requirement if the amount of downlink buffered data in multiple consecutive evaluation cycles in the extended HCCA mode is not greater than the second maximum value.

12. 2. The method of claim 1, further comprising: after the AP enters a data transmission contention period (CP), if the AP contends for a second TXOP in the CP, broadcasting the target frame to all the STAs to notify all the STAs that the AP needs to occupy the second TXOP for data transmission.

13. A computer-readable storage medium having a computer program stored therein, the computer program implementing the data transmission method of claim 1 when executed by a processor.

14. 10. An electronic device comprising a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the data transmission method of claim 1.

Images