Wireless communication method, non-access point station, and access point

Abstract

Provided are a wireless communication method, a non-access point station (non-AP STA), and an access point (AP). The method comprises: a non-AP STA sends first information to an AP, wherein the first information is used for requesting or advising the non-AP STA to use a DRU. In the related art, a DRU is mainly applied to a TB PPDU for uplink transmission, and an AP determines whether a non-AP STA can use the DRU, and performs instruction in a trigger frame. That is, the non-AP STA can only passively use the DRU on the basis of the instruction of the AP. In the present application, the non-AP STA can use the first information to actively notify the AP that the non-AP STA advises or requests to use the DRU, so that the non-AP STA can actively use the DRU. The non-AP STA actively uses the DRU, so that the non-AP STA can adaptively request or advise to use the DRU according to actual communication scenarios or requirements, thereby using the DRU more flexibly to give full play to the advantages of the DRU.

Description

Wireless communication methods, non-access point sites and access points Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method, a non-access point site, and an access point. Background Technology

[0002] With technological advancements, resource units (RUs) can now have both continuous and discontinuous subcarriers. RUs with continuous subcarriers are called regular RUs (RRUs or rRUs). RUs with discontinuous subcarriers are called distributed RUs (DRUs or dRUs).

[0003] Summary of the Invention

[0004] This application provides a wireless communication method, a non-access point site, and an access point. The various aspects covered by this application are described below.

[0005] In a first aspect, a wireless communication method is provided. The method includes: a non-access point station (non-AP STA) sending first information to an access point (AP); wherein the first information is used to request or suggest that the non-AP STA use a DRU.

[0006] In a second aspect, a wireless communication method is provided, the method comprising: an AP receiving first information transmitted by a non-AP STA; wherein the first information is used to request or suggest that the non-AP STA use a DRU.

[0007] Thirdly, a non-AP STA is provided, comprising: a transmitting unit for sending first information to the AP; wherein the first information is used to request or suggest that the non-AP STA use DRU.

[0008] Fourthly, an AP is provided, comprising: a receiving unit for receiving first information sent by a non-AP STA; wherein the first information is used to request or suggest that the non-AP STA use a DRU.

[0009] Fifthly, a communication device is provided, which is a non-access point site or an access point. The communication device includes a processor and a memory, the memory for storing one or more computer programs, and the processor for invoking the computer programs in the memory to perform some or all of the steps of the methods described in the preceding aspects of the communication device.

[0010] Sixthly, embodiments of this application provide a communication system that includes the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0011] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0012] Eighthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0013] Ninthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0014] In related technologies, DRUs are mainly applied to trigger-based (TB) physical layer protocol data units (PPDUs) in uplink (UL) transmissions. The AP determines whether a non-AP STA can use the DRU and indicates this in the trigger frame. That is, a non-AP STA can only passively use the DRU according to the AP's instructions. Based on this application, a non-AP STA can actively inform the AP of its suggestion or request to use the DRU through a first message, thus enabling the non-AP STA to actively use the DRU. Active use of the DRU by a non-AP STA allows it to adaptively request or suggest the use of the DRU based on the actual communication scenario or needs, thereby using the DRU more flexibly and fully leveraging its advantages. Attached Figure Description

[0015] Figure 1 is a schematic diagram of the wireless communication system used in the embodiments of this application.

[0016] Figure 2 is a schematic diagram of a DRU application scenario.

[0017] Figure 3 is an example diagram of a medium access control (MAC) frame.

[0018] Figure 4A is a format example of an aggregated control (A-control) field.

[0019] Figure 4B is an example of a control field format.

[0020] Figure 4C is an example of the format of the control information subfield in the control subfield of a bandwidth query report (BQR).

[0021] Figure 4D is an example of the format of the control information subfield in the control subfield of an EHT link adaptation (ELA) system.

[0022] Figure 4E is an example of the format of an MCS request (MRQ) sequence identifier (MSI) / partial PPDU parameters field.

[0023] Figure 4F shows a format example of the control information field in the EHT operating mode (EHT OM) control field.

[0024] Figure 5 is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0025] Figure 6 is a schematic diagram of a wireless transmission process provided in Embodiment 1 of this application.

[0026] Figure 7 is a schematic diagram of a wireless transmission process provided in Embodiment 2 of this application.

[0027] Figure 8 is a schematic diagram of a wireless transmission process provided in Embodiment 3 of this application.

[0028] Figure 9 is a format example diagram of a BQR control field provided in an embodiment of this application.

[0029] Figure 10 is a schematic diagram of a wireless transmission process provided in Embodiment 4 of this application.

[0030] Figure 11 is a format example diagram of an ELA control field provided in an embodiment of this application.

[0031] Figure 12 is a schematic diagram of a wireless transmission process provided in Embodiment 5 of this application.

[0032] Figure 13 is a schematic diagram of the format of an EHT OM control field provided in an embodiment of this application.

[0033] Figure 14 is a schematic diagram of a wireless transmission process provided in Embodiment 6 of this application.

[0034] Figure 15 is a schematic diagram of the format of a DRU recommendation control field provided in an embodiment of this application.

[0035] Figure 16 is a format example diagram of a BQR control field provided in an embodiment of this application.

[0036] Figure 17 is a schematic structural diagram of a non-AP STA provided in an embodiment of this application.

[0037] Figure 18 is a schematic structural diagram of an AP provided in an embodiment of this application.

[0038] Figure 19 is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0039] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0040] Communication system

[0041] The technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), high-performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For example, the technical solutions provided in this application can be applied to communication systems using the 802.11 standard. Exemplarily, the 802.11 standard includes, but is not limited to, the 802.11ax standard, the 802.11be standard, and next-generation 802.11 standards.

[0042] Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application. Referring to Figure 1, the communication devices in the communication system 100 may include AP111, AP112, and station (STA) 121 and STA122, wherein STA121 can access the network through AP111, and STA122 can access the network through AP112.

[0043] In some implementations, a STA can establish an association with one or more APs, after which the associated STAs and APs can communicate with each other. As shown in Figure 1, AP 111 and STA 121 can communicate after establishing an association, and AP 112 and STA 122 can communicate after establishing an association.

[0044] In some implementations, the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA. Here, a peer STA can refer to a device that communicates with the STA's counterpart. For example, a peer STA may be an AP or a non-AP STA.

[0045] It should be understood that Figure 1 exemplarily shows two AP STAs and two non-AP STAs. The communication system 100 may also include more AP STAs, or the communication system 100 may include other numbers of non-AP STAs. This application embodiment does not limit this.

[0046] In addition, the above-mentioned communication system can be applied to scenarios involving multi-device collaboration, such as multi-AP (multi-access points) collaboration or multi-site collaboration.

[0047] In the embodiments of this application, the names of AP and / or STA are not limited. In some scenarios, AP can also be called AP STA, that is, in a sense, AP is also a type of STA. In other scenarios, STA can be called non-AP STA.

[0048] In some scenarios, the aforementioned communication equipment can also be a "multi-link device (MLD)," meaning a device that can communicate through multiple communication links. These multiple communication links can include communication links in different frequency bands, such as millimeter-wave bands and / or low-frequency bands. Typically, if the multi-link device is an access point (AP), it can also be called a "multi-link AP." If the multi-link device is a stand-alone device (STA), it can also be called a "multi-link STA."

[0049] In this application embodiment, the AP can be a device in a wireless network. The AP can be a communication server, router, switch, bridge, or other communication entity. Alternatively, the AP can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP can also be a chip, circuit, or processing system within these various forms of devices, thereby implementing the methods and functions of this application embodiment. APs can be applied in various scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.).

[0050] In some implementations, the role of the STA in the communication system is not absolute; in some scenarios, the STA can act as an AP. For example, in a scenario where a mobile phone connects to a router, the mobile phone can be a non-AP STA, while when the mobile phone acts as a hotspot for other mobile phones, it takes on the role of an AP.

[0051] In the embodiments of this application, the STA can be a device with wireless transceiver capabilities, such as one that supports the 802.11 series of protocols and can communicate with the AP or other STAs. For example, an STA is any user communication device that allows users to communicate with the AP and thus with the WLAN. STAs include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0052] In this application embodiment, the STA can also be a device that provides voice / data connectivity to the user, such as a handheld device or vehicle-mounted device with wireless connectivity. Examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0053] By way of example and not limitation, in this embodiment, the STA can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Examples include smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require cooperation with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0054] Furthermore, in this embodiment, the STA can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network for human-machine interconnection and object-to-object interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).

[0055] Furthermore, in this embodiment, the STA can be a device in a vehicle-to-everything (V2X) system. The communication methods in a V2X system are collectively referred to as V2X (where X represents anything). For example, V2X communication includes: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0056] In addition, in the embodiments of this application, the STA may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal devices), receiving control information and downlink (DL) data from the AP, and sending electromagnetic waves to transmit data to the AP.

[0057] In addition, the AP in this application embodiment can be a device for communicating with the STA. The AP can be a network device in a wireless local area network, and the AP can be used to communicate with the STA through the wireless local area network.

[0058] From the perspective of the communication standards supported by the AP, in some implementations, the AP can be a device that supports the 802.11be standard. The AP can also be a device that supports various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0059] From the perspective of the communication standards supported by the STA, in some implementations, non-AP STAs can support the 802.11be standard. Non-AP STAs can also support various current and future 802.11 family of wireless local area networks (WLAN) standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0060] In this application embodiment, the frequency bands supported by WLAN technology are not limited. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 45GHz, 60GHz).

[0061] It should be understood that the specific forms of STA and AP are not specifically limited in the embodiments of this application, and are merely illustrative examples.

[0062] DRU

[0063] With the development of technology, the limitations on power spectral density (PSD) are becoming increasingly stringent. For example, in the 6 GHz band, the PSD limit for non-AP STA in low-power indoor bands is -1 dBm / MHz.

[0064] An RRU has consecutive subcarriers. For example, both RUs with consecutive subcarriers as defined in 11ax and 11be can be called RRUs. The transmission power of each subcarrier in an RRU is lower. This is because the PSD limit is defined per MHz and per STA, while the subcarriers in an RRU are consecutive, resulting in a larger number of subcarriers per MHz, and therefore, lower transmission power per subcarrier according to the PSD limit.

[0065] DRUs have discontinuous subcarriers. In the case of DRUs, the number of subcarriers per MHz is small, sometimes even only one. Therefore, subcarriers in DRUs can transmit at higher power compared to RRUs. For example, for a 52-tone DRU distributed over 80MHz, there may only be one subcarrier per MHz. However, for a 52-tone RRU, there are approximately 13 subcarriers per MHz. In the 6GHz low-power indoor band, the PSD is limited to -1dBm / MHz. Therefore, for a 52-tone RU (approximately 4MHz), the maximum allowed transmission power using an RRU is only about 6dBm, while using a DRU can increase the transmit power by 11dB. This significant increase in transmit power allows for higher modulation and coding schemes (MCS) or longer transmission distances.

[0066] As shown in Figure 2, STA1, STA2, and STA3 can all utilize DRUs to increase their transmit power. Compared to using RRUs of the same size, all subcarriers achieve higher transmit power, thus significantly improving overall spectral efficiency.

[0067] It should be noted that an MRU can also have discontinuous subcarriers, i.e., a DMRU. The DRU-related technical solutions provided in this application can also be applied to a DMRU. For ease of description, the following description uses only a DRU as an example. If you need to apply the embodiments described below to a DMRU, simply replace "DRU" with "DMRU".

[0068] It should be noted that some communication standards (such as IEEE 802.11bn) require support for TB PPDU transmission using DRU.

[0069] A-control field

[0070] The A-control field can be a high throughput (HT) control field. To facilitate understanding of the A-control field, we will first introduce the HT control field.

[0071] QoS data frames, QoS null frames, and management frames can all contain the HT control field. The presence of the HT control field is controlled by the +HTC subfield in the frame control field.

[0072] Figure 3 shows an example of a MAC frame. Figure 3 illustrates the possible locations of the HT control field within the MAC frame. As shown in Figure 3, the HT control field is located within the MAC header. A MAC frame may also include one or more of the following fields: Frame Control, Duration / ID, Address 1, Address 2, Address 3, Sequence Control, Address 4, QoS Control, Frame Body, and FCS.

[0073] There are three variations of the HT control field, and Table 1 shows examples of the HT control field format. As shown in Table 1, the A-control field can be an HT control field when both B0 and B1 are 1.

[0074] Table 1

[0075] Figure 4A is a format example of an A-control field. As shown in Figure 4A, an A-control field may include one or more of the following fields: control list and padding.

[0076] A control list field can contain one or more control subfields. Figure 4B shows an example format of a control subfield. As shown in Figure 4B, a control subfield can include one or more of the following subfields: control ID and control information. The control ID subfield can indicate the type of the specific A-control subfield. Table 2 illustrates the possible values ​​and meanings of the control ID subfield.

[0077] Table 2

[0078] The following is an explanation of some of the fields involved in Table 2.

[0079] (1) BQR control field

[0080] The Control Information subfield in a BQR control subfield contains the bandwidth query report (BQR) used for bandwidth query report operation to assist HE MU transmission (see 26.5.2 (UL MU operation)).

[0081] Figure 4C is an example diagram of the format of the control information subfield in the BQR control subfield.

[0082] As shown in Figure 4C, the control information subfield in the BQR control subfield may include one or more of the following fields: available channel bitmap, reserved.

[0083] The Available Channel Bitmap subfield contains a bitmap indicating the subchannels available at the STA transmitting the BQR. Each bit in the bitmap corresponds to a 20MHz subchannel within the operating channel width of the BSS in which the STA is associated, with the LSB corresponding to the lowest numbered operating subchannel of the BSS. A bit at position X in the bitmap is set to 1 to indicate that subchannel X+1 is idle; otherwise, it is set to 0 to indicate that the subchannel is busy or unavailable. The availability of each 20MHz subchannel is based on ED-based CCA and is reported in the operating channel of the reporting STA when the radio medium is idle. (The bit in position X in the bitmap is set to 1 to indicate that the subchannel

[0084] A non-AP STA can assist its AP in allocating DL MU and UL MU resources by sending BQRs. A non-AP STA can implicitly send BQRs in the BQR Control subfield of a frame transmitted to the AP (unsolicited BQRs) or explicitly send BQRs in a frame sent to the AP in response to a BQRP Trigger frame (solicited BQRs).

[0085] When there is one BQR control subfield in an A-control subfield, the Available Channel Bitmap subfield is applied to: the operating channel width when the operating channel width is no more than 160MHz; and the primary 160MHz when the operating channel width is 320MHz.

[0086] The A-control field can include two BQR control subfields. When the A-control subfield includes two BQR control subfields, the Available Channel Bitmap subfield is applied to the primary 160MHz and the secondary 160MHz respectively in the first and second BQR control subfields.

[0087] (2) ELA control fields

[0088] The Control Information subfield in an ELA Control subfield contains information related to the EHT link adaptation (ELA) procedure. The specific format of the Control Information subfield in the ELA Control subfield is shown in Figure 4D.

[0089] As shown in Figure 4D, the control information subfield in the ELA control subfield may include one or more of the following fields: unsolicited MCS feedback (unsolicited MFB), MCS request (MRQ) / uplink EHT triggered PPDU MFB (UL EHT TB PPDU MFB), number of spatial streams (NSS), UHR-MCS, RU allocation, PS160, bandwidth (BW), MSI / partial PPDU parameters, transmission beamforming (TX beamforming), high-efficiency link adaptation / ultra-high throughput link adaptation (HLA / ELA).

[0090] Figure 4E shows an example of the format of the MSI / partial PPDU parameter field. As shown in Figure 4E, the MSI / partial PPDU parameter field may include one or more of the following fields: Reserved, PPDU format, and encoding type.

[0091] (3) EHT OM control field

[0092] A HE STA can change its operating mode setting using either the operating mode notification or the operating mode indication (OMI) procedure.

[0093] The Control Information subfield in an EHT OM control subfield contains information related to the OM changes for the 320MHz bandwidth, the Tx NSTS extension, and the Rx NSS extension for the STA transmitting the frame containing this information.

[0094] Figure 4F shows an example of the format of the control information field in the EHT OM control field. As shown in Figure 4F, the control information field in the EHT OM control field may include one or more of the following fields: Rx NSS extension, channel width extension, Tx NSTS extension, MCS15 disable, and reserved.

[0095] This application proposes an improved technical solution for DRU. Figure 5 is a schematic flowchart of a wireless communication method provided by an embodiment of this application. The method shown in Figure 5 can be performed by a non-AP STA and an AP.

[0096] The method shown in Figure 5 may include step S510.

[0097] In step S510, the non-AP STA sends the first message to the AP.

[0098] In some embodiments, the first information can be used to request or suggest that a non-AP STA use a DRU. That is, based on the first information, a non-AP STA can inform the AP that it requests or suggests using a DRU in a subsequent transmission.

[0099] It should be noted that this application does not limit the name of the first information. For example, the first information can also be called a DRU recommendation indication.

[0100] In some embodiments, if the first information is used to request a non-AP STA to use the DRU, the AP needs to provide a corresponding response to the request in the first information. For example, the AP may respond with: confirmation (or agreement) that the non-AP STA uses the DRU, or rejection of the non-AP STA's use of the DRU.

[0101] In some embodiments, if the first information is used to suggest that a non-AP STA use a DRU, the AP may not need to provide feedback regarding the first information. For example, the AP may directly perform the corresponding operation based on the first information without sending feedback information corresponding to the first information.

[0102] In some embodiments, the AP can determine whether to allocate a DRU to a non-AP STA based on the first information. For example, once the AP receives the first information, it can allocate a DRU to the non-AP STA based on the first information. Alternatively, if the AP receives the first information, it can accept the request or suggestion in the first information to allocate a DRU to the non-AP STA, or it can refuse the request or suggestion in the first information, i.e., not allocate a DRU to the non-AP STA (for example, the AP can allocate an RRU to the non-AP STA).

[0103] In some embodiments, the AP may determine whether to allocate a DRU to a non-AP STA based solely on the first information. For example, if the AP receives the first information, the AP needs to allocate a DRU to the non-AP STA based on the request in the first information, without considering other factors.

[0104] In some embodiments, the AP can combine first information with other information to determine whether to allocate a DRU to a non-AP STA. This other information may include one or more of the following: Receive Signal Strength Indicator (RSSI), Buffer Status Report (BSR), Sounding Signal-to-Noise Ratio (SNR) results, etc. For example, if the AP receives the first information, it can combine it with other information to determine whether to accept the request or suggestion in the first information and allocate a DRU to the non-AP STA.

[0105] In related technologies, DRUs are mainly used in uplink transmission TB PPDUs, where the AP determines whether a non-AP STA can use the DRU and indicates this in the trigger frame. That is, non-AP STAs can only passively use the DRU according to the AP's instructions. Based on this application, non-AP STAs can actively inform the AP of their suggestion or request to use the DRU through a first message, thus enabling them to actively use the DRU. Active use of the DRU by non-AP STAs allows them to adaptively request or suggest its use based on actual communication scenarios or needs, thus using the DRU more flexibly and fully leveraging its advantages.

[0106] In some embodiments, the first information may be carried in a first field. Optionally, the first field may also be referred to as a DRU recommendation field.

[0107] As one implementation method, both the AP and the non-AP STA can send the first field carrying the first information. That is, the first field sent by both the AP and the non-AP STA can be used to indicate the first information.

[0108] As an alternative implementation, the first field sent by the non-AP STA can be used to indicate the first information. The first field sent by the AP can be reserved. Alternatively, the first field sent by the AP can be used to indicate other information besides the first information.

[0109] In some embodiments, the first information can be used to request or suggest that, after sending the first information, the non-AP STA uses the DRU to send one or more PPDUs. The first information requesting the use of one or more PPDUs from the DRU can be an uplink PPDU.

[0110] Optionally, the first information suggestion or request sent using the DRU may include the next PPDU sent after the non-AP STA sends the first information. That is, the first information can be used for a request or suggestion: after sending the first information, the non-AP STA sends the next PPDU using the DRU. In other words, the PPDU for the first information request or suggestion to use the DRU and the PPDU carrying the first information are sent consecutively for the non-AP STA.

[0111] It is understood that if the first message is used to request or suggest that a non-AP STA send one or more PPDUs using a DRU after sending the first message, then the suggestion or request in the first message can be effective immediately. That is, after the first message requests or suggests using a DRU, the non-AP STA may be able to immediately use a DRU to send PPDUs. This application refers to this scheme as the "immediacy scheme".

[0112] Understandably, in an immediate approach, the first piece of information takes effect quickly. Therefore, an immediate approach allows non-AP STAs to begin using DRUs as early as possible.

[0113] For example, if the first message is sent within the AP's TXOP, it can be used to request or suggest that a non-AP STA use the DRU to send the next PPDU after sending the first message. In other words, if a non-AP STA requests or suggests using the DRU within the AP's TXOP, an immediate approach can be used. Here, the AP's TXOP can be understood as the holder of that TXOP being the AP.

[0114] Optionally, the first information suggesting or requesting the use of one or more PPDUs transmitted by the DRU may not include the next PPDU after the non-AP STA transmits the first information. In other words, the PPDU that suggests or requests the use of the DRU and the PPDU containing the first information are not transmitted consecutively for the non-AP STA (there may be one or more PPDUs in between). Alternatively, the non-AP STA may use the DRU some time after (not immediately after) the first information is transmitted, by requesting or suggesting the use of the DRU. Therefore, in this case, the suggestion or request of the first information is not immediately effective; hence, this application refers to this approach as a "non-immediate approach."

[0115] In some embodiments, the first information may be used to request or suggest that a non-AP STA send one or more PPDUs using a DRU within the AP's TXOP.

[0116] If the first message is used for a request or suggestion: If a non-AP STA uses DRU to send one or more PPDUs within the AP's TXOP, the next PPDU sent by the non-AP STA after the first message may not be able to use DRU for transmission because it is not within the AP's TXOP; that is, the first message may not take effect immediately. For example, if the first message can be sent within the non-AP STA's TXOP, the next PPDU sent after the first message may also be sent within the non-AP STA's TXOP. In this case, the next PPDU cannot be transmitted using DRU and must wait until the AP's TXOP begins before the non-AP STA can use DRU. In this scheme, the first message needs to wait until at least the start of the AP's TXOP to take effect. Therefore, this scheme can also be called a "non-instantaneous scheme".

[0117] Optionally, if the first message is sent within the TXOP of a non-AP STA, the first message can be used to request or suggest that the non-AP STA send one or more PPDUs using a DRU within the AP's TXOP. For example, a non-AP STA can send the first message within its own TXOP (i.e., the TXOP is held by the non-AP STA). After the AP acquires the TXOP, the AP can, based on the first message, instruct the non-AP STA to send one or more PPDUs using a DRU.

[0118] In some embodiments, the first information can be used to request or suggest that a non-AP STA use DRU when transmitting a PPDU. That is, the first information may only apply to one PPDU. If a non-AP STA requests or suggests that multiple PPDUs use DRU, the non-AP STA may send the first information multiple times accordingly. For example, a non-AP STA may send the first information N times for each of N PPDUs to request that another N PPDUs use DRU transmission.

[0119] In some embodiments, the first information can be used to request or suggest that a non-AP STA use a DRU when sending Q PPDUs. That is, the first information can be effective for Q PPDUs. Here, Q can be a positive number greater than 1. Q can satisfy one or more of the following: indicated by the non-AP STA, determined by the AP, defined by the protocol, etc.

[0120] In some embodiments, the first information can be used to request or suggest that a non-AP STA use the DRU within a first time period. In other words, the first information can take effect within the first time period. That is, within the first time period, the AP can determine or instruct a non-AP STA to use the DRU based on the first information; outside the first time period, the AP may not determine or instruct a non-AP STA to use the DRU based on the first information.

[0121] It should be noted that this application does not limit the number of PPDUs requested or suggested by the first information to be sent by the non-AP STA using the DRU within the first time period. For example, the first information can be used to request or suggest that the non-AP STA send one PPDU using the DRU within the first time period. Alternatively, the first information can be used to request or suggest that the non-AP STA send M PPDUs using the DRU within the first time period. Here, M can be a positive integer. The value of M is unrestricted. Alternatively, M can satisfy one or more of the following: indicated by the non-AP STA, determined by the AP, defined by the protocol, etc.

[0122] It is understandable that the first information is used to request or suggest a technical solution for non-AP STAs to use DRU within the first time period, which can be either an immediate solution or a non-immediate solution as described above.

[0123] In some embodiments, the first time period may satisfy one or more of the following: the first time period belongs to the TXOP of the AP; the start time of the first time period is determined based on the transmission time of the first information; the end time of the first time period is determined based on the second information transmitted by the non-AP STA.

[0124] As one implementation, the first time period can belong to the AP's TXOP. For example, the start time of the first time period can be determined based on the start time of the AP's TXOP. Exemplarily, the start time of the first time period can be the same as the start time of the AP's TXOP. In other words, the first information can request or suggest that non-AP STAs use DRU starting from the start time of the AP's TXOP. Similarly, the end time of the first time period can be determined based on the end time of the AP's TXOP. Exemplarily, the end time of the first time period can be the same as the end time of the AP's TXOP. In other words, the first information can request or suggest that non-AP STAs use DRU until the end time of the AP's TXOP.

[0125] As one implementation, the start time of the first time period can be determined based on the first information. For example, the start time of the first time period can be determined based on the transmission time of the first information. In other words, the first information can request or suggest that non-AP STAs use DRUs starting from the transmission time of the first information. Alternatively, the start time of the first time period can be indicated by the first information. Exemplarily, the PPDU, frame, or field carrying the first information can include a field indicating the start time of the first time period.

[0126] As one implementation, the end time of the first time period can be determined based on second information sent by the non-AP STA. This second information can be used to request or suggest that the non-AP STA use the DRU. For example, the end time of the first time period can be determined based on the sending time of the second information. Exemplarily, the end time of the first time period can be the sending time of the second information. In other words, the first information can be used to request or suggest that the non-AP STA use the DRU before the second information is sent. Alternatively, the end time of the first time period can be indicated by the second information. Exemplarily, the PPDU, frame, or field carrying the second information can include a field indicating the end time of the first time period.

[0127] As one approach, the first time period can be determined by combining the aforementioned information.

[0128] For example, the first time period belongs to the AP's TXOP, and the start time of the first time period is determined based on the first message. For example, if the first message is sent within the AP's TXOP, the first time period can be from the time the first message is sent to the time the AP's TXOP ends. Alternatively, if the first message is sent within the AP's TXOP, then the start time of the first time period is the time the first message is sent.

[0129] For example, the start time of the first time period can be determined based on the sending time of the first message, and the end time of the first time period can be determined based on the sending time of the second message. In other words, the first message can be used for a request or suggestion: non-AP STAs use DRU after the first message is sent and before the second message is sent.

[0130] For example, the first time period can belong to the AP's TXOP, and the start time of the first time period is determined based on the first information, and the end time of the first time period is determined based on the second information. For instance, the first time period can be the time occupied by the AP's TXOP between the time the first information is sent and the time the second information is sent.

[0131] In some embodiments, a non-AP STA may send a second message to the AP. As described above, the second message may be used to withdraw a request or to recommend that the non-AP STA use a DRU.

[0132] It is understandable that the second message can be implemented in conjunction with the first message. That is, typically, after a non-AP STA sends the first message requesting the non-AP STA to use DRU, the non-AP STA may send the second message to revoke the request or suggestion in the first message.

[0133] In some embodiments, the first information and the second information can be stored in the same field. For example, both the first information and the second information can be stored in the first field. It is understood that storing the first information and the second information in the same field simplifies implementation.

[0134] Optionally, different values ​​of the first field can correspond to first information or second information. For example, the first field can occupy 1 bit. For instance, a value of 1 in the first field can represent first information, meaning a value of 1 in the first field can request or suggest that a non-AP STA use DRU; a value of 0 in the first field can represent second information, meaning a value of 0 in the first field can withdraw the request or suggestion that a non-AP STA use DRU. Similarly, a value of 0 in the first field can represent first information, meaning a value of 0 in the first field can request or suggest that a non-AP STA use DRU; a value of 1 in the first field can represent second information, meaning a value of 1 in the first field can withdraw the request or suggest that a non-AP STA use DRU.

[0135] Optionally, the first field can take a first value, which can indicate that the first field carries first information or second information. The first value can be 0 or 1. The first field can take a second value, which can indicate that the first field does not carry first or second information. The second value is different from the first value. For example, the first field taking a first value for the first time can indicate that the first field carries first information. Similarly, if the first field previously took a first value indicating first information, then taking a first value this time can indicate second information; and if the first field previously took a first value indicating second information, then taking a first value this time can indicate first information. Between the moment the first field previously took a first value and the moment it now takes a first value, the first field can take a second value.

[0136] For example, if a non-AP STA requests or suggests that it use the DRU, it can send a first field with a first value. If the non-AP STA wishes to use the DRU for a period of time, the first field can have a second value during that period. If the non-AP STA withdraws its request or suggestion to use the DRU, it can send the first field with the first value again. That is, between the two times the non-AP STA sends the first field with the first value, the non-AP STA requests or suggests that it use the DRU.

[0137] In some embodiments, the AP may send a first trigger frame to a non-AP STA. The first trigger frame can be used to trigger the non-AP STA to send a first PPDU. The first trigger frame is determined based on first information. Optionally, the first trigger frame may also be determined based on the second information described above.

[0138] Optionally, the first trigger frame may indicate the RU type assigned to the non-AP STA. The RU type may include, for example, an RRU or a DRU. This application proposes that, based on the first information, the RU type used by the first PPDU triggered by the first trigger frame can be determined.

[0139] For example, if a non-AP STA requests or suggests the use of a DRU via a first message, the first trigger frame may indicate that the RU type is DRU, meaning the first trigger frame can be used to trigger the non-AP STA to send the first PPDU using a DRU. If a non-AP STA withdraws its request or suggests the use of a DRU via a second message, the first trigger frame may indicate that the RU type is RRU, meaning the first trigger frame can be used to trigger the sending of the first PPDU using an RRU.

[0140] For example, if the AP accepts the request or suggestion for the first message, the first trigger frame can be used to trigger a non-AP STA to send the first PPDU using the DRU. If the AP does not accept the request or suggestion for the first message, the first trigger frame can be used to trigger a non-AP STA to send the first PPDU using the RRU.

[0141] It should be noted that the first PPDU can be a trigger-based (TB) PPDU. That is, the first message can request or suggest that a TB PPDU sent by a non-AP use DRU transmission.

[0142] In some embodiments, a non-AP STA may send the first information to the AP if a first condition is met. In other words, a non-AP STA may or may send the first information to the AP only if certain conditions are met.

[0143] Optionally, the first condition may be related to one or more of the following: the result of the data unit received by the AP, the status of the sub-channel used by the non-AP STA, the throughput of the non-AP STA, the data volume of the non-AP STA, the MCS of the non-AP STA, etc. These will be explained below.

[0144] The results of data units received by the AP can be used to indicate the success rate of data unit reception. These results can be carried in feedback frames sent by the AP. Feedback frames may include, for example, block acknowledgement (BA) frames.

[0145] It should be noted that the data units received by the AP may include one or more of the following: medium access control service data unit (MPDU), aggregated-medium access control service data unit (A-MPDU), and PPDU.

[0146] In some embodiments, the first condition may include: the AP's data unit reception result is poor. Poor reception result can manifest as a low success rate in receiving data units. For example, poor reception result may include: the AP reporting that it has not received any data units, or the AP reporting that the number of data units it has received is less than or equal to a first quantity threshold. The first quantity threshold can be a positive integer. In other words, the first condition may include: the AP reporting that it has not received any data units or that the number of received data units is less than the first quantity threshold.

[0147] The data units received by the AP are those sent to the AP by non-AP STAs. Based on the results of the data units received by the AP, the reception success rate of the data units sent by non-AP STAs can be determined. If the reception success rate of the data units sent by non-AP STAs is low, the non-AP STA may send a first message requesting or suggesting that DRU be used by non-AP STAs to improve the reception success rate and thus improve the quality of uplink transmission.

[0148] The subchannels used by a non-AP STA can be in a busy or idle state. A non-AP STA can perform clear channel assessment (CCA) on one or more subchannels within its operating bandwidth to determine the subchannel's state. The bandwidth of a single subchannel can be 20MHz.

[0149] In some embodiments, the first condition may include: one or more sub-channels used by the non-AP STA are busy. That is, if one or more sub-channels used by the non-AP STA are busy, the non-AP STA may request or suggest that it use a DRU (Distributed Novel Receiver). For example, if the non-AP STA finds one or more sub-channels to be busy, it may request or suggest that it use a DRU (i.e., send the first message). Similarly, if the non-AP STA finds that the number of busy sub-channels is greater than or equal to a second quantity threshold, it may request or suggest that it use a DRU. The second quantity threshold can be a positive integer.

[0150] In some embodiments, the first condition may include: the throughput of the non-AP STA needs to be increased. For example, the first condition may include: the throughput of the non-AP STA is less than or equal to a first throughput threshold. The first throughput threshold can be a positive number. That is, if the throughput of the non-AP STA is less than or equal to the first throughput threshold, the non-AP STA may request or suggest that the non-AP STA use DRU.

[0151] Understandably, based on the first condition related to throughput, non-AP STAs can improve MCS and increase throughput by sending a first information request or suggesting that non-AP STAs use DRU.

[0152] In some embodiments, the first condition may include: the amount of data from the non-AP STA is greater than or equal to a first data volume threshold. The first data volume threshold can be a positive number. That is, if the amount of data from the non-AP STA is greater than or equal to the first data volume threshold, the non-AP STA may request or suggest that the non-AP STA use DRU.

[0153] Understandably, based on the first condition related to data volume, non-AP STAs can improve MCS and increase throughput to transmit larger amounts of data by sending a first information request or suggesting that non-AP STAs use DRU.

[0154] In some embodiments, the first condition may include: the MCS of the non-AP STA is less than or equal to a first MCS threshold. The first MCS threshold may be a value representing the MCS level. That is, if the MCS of the non-AP STA is less than or equal to the first MCS threshold, the non-AP STA may request or suggest that the non-AP STA use DRU.

[0155] Understandably, based on the first condition related to MCS, non-AP STAs can improve MCS and thus increase throughput by sending a first information request or suggesting that non-AP STAs use DRU.

[0156] It should be noted that the first condition may include multiple conditions described above. For example, the first condition may include one or more of the following: the AP reports that it has not received any data units or the number of data units received is less than a first quantity threshold; one or more sub-channels used by the non-AP STA are busy; the throughput of the non-AP STA is less than or equal to a first throughput threshold; the data volume of the non-AP STA is greater than or equal to a first data volume threshold; the MCS of the non-AP STA is less than or equal to a first MCS threshold.

[0157] For ease of understanding, the technical solution provided in this application will be illustrated below through implementations 1-3.

[0158] Example 1

[0159] Example 1 pertains to the wireless communication process within the TXOP of the AP. Figure 6 is an example diagram of a wireless communication process provided in Example 1. The method shown in Figure 6 can be performed by one or more non-AP STAs or the AP. Any one of the one or more non-AP STAs can be a non-AP STA in this application. In Figure 6, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0160] The communication process shown in Figure 6 may include steps S610 to S640.

[0161] In step S610, the AP sends a trigger frame to trigger one or more non-AP STAs to perform UL TB PPDU transmission using the RRU.

[0162] In step S620, in response to the trigger frame, one or more non-AP STAs send a TB PPDU.

[0163] In step S630, one or more non-AP STAs receive a BA frame fed back by the AP.

[0164] If a non-AP STA finds that the result indicating successful reception of A-MPDU in the BA frame is poor, the non-AP STA can consider using DRU to transmit TB PPDU, thereby improving the quality of UL transmission.

[0165] In step S640, one or more non-AP STAs, in the TB PPDU transmission immediately following the receipt of the BA frame, carry a DRU recommendation instruction to the AP suggesting or requesting the use of DRU, and suggest or request the AP to use DRU transmission in the next TB PPDU.

[0166] After receiving the signaling instruction in step S640, the AP may instruct one or more non-AP STAs to use DRU in the subsequent trigger frame requesting TB PPDU.

[0167] Example 2

[0168] Example 2 pertains to the wireless communication process within the TXOP of the AP. Figure 7 is an example diagram of a wireless communication process provided in Example 2. The method shown in Figure 7 can be performed by one or more non-AP STAs or the AP. Any one of the one or more non-AP STAs can be a non-AP STA in this application. In Figure 7, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0169] The communication process shown in Figure 7 may include steps S710 to S720.

[0170] In step S710, the AP sends a trigger frame to trigger one or more non-AP STAs to perform UL TB PPDU transmission using the RRU.

[0171] One or more non-AP STAs have a large amount of data and want to improve MCS by using DRU, thereby increasing throughput.

[0172] In step S720, in response to the trigger frame, one or more non-AP STAs send a TB PPDU.

[0173] A non-AP STA can carry a DRU recommendation instruction in its TB PPDU transmission, suggesting or requesting the AP to use a DRU transmission in the next TB PPDU. After receiving this signaling instruction, the AP may instruct one or more non-AP STAs to use a DRU in the trigger frame of the subsequent request TB PPDU.

[0174] Example 3

[0175] Example 3 pertains to the wireless communication process within the TXOP of a non-AP STA. Figure 8 is an example diagram of a wireless communication process provided in Example 3. The method shown in Figure 8 can be performed by a non-AP STA and an AP. In Figure 8, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0176] The communication process shown in Figure 8 may include step S810.

[0177] A non-AP STA performs a CCA on each 20MHz subchannel of its operating bandwidth and finds that a certain 20MHz subchannel is busy, reducing available spectrum resources. Since the non-AP STA wants to further increase throughput, it actively suggests or requests the AP to use DRU to transmit TB PPDU within a certain AP's TXOP.

[0178] In step S810, the non-AP STA sends a TB PPDU.

[0179] Non-AP STAs can carry a DRU recommendation instruction in their TB PPDU transmission, suggesting or requesting the AP to use DRU transmission within the AP's TXOP. Upon receiving this signaling instruction, the AP may instruct the non-AP STA to use DRU in the trigger frame of the request TB PPDU within the AP's TXOP.

[0180] The following example illustrates the signaling related to the first information.

[0181] In some embodiments, the first information may be carried in the MAC frame header and / or PPDU.

[0182] It should be noted that this application does not limit the type of PPDU when the first information is carried in the PPDU. For example, the PPDU carrying the first information may include a TB PPDU or a non-TB PPDU. For example, when the first information is transmitted within the TXOP of an AP, the PPDU carrying the first information may be a TB PPDU. When the first information is transmitted within the TXOP of a non-AP STA, the PPDU carrying the first information may be a non-TB PPDU.

[0183] It should be noted that, when the first information is carried in the MAC frame header, this application does not limit the type of the corresponding MAC frame. For example, a MAC frame may include one or more of the following: Quality of Service (QoS) data frame, QoS null frame, and management frame.

[0184] When the first information is carried in the MAC frame header, it can be carried in the A-control field. For example, the first information can be carried in one or more of the following fields: BQR control field, link adaptation control field, and OM control field. In other words, the first field carrying the first information can be a subfield of one or more of the following fields: BQR control field, link adaptation control field, and OM control field.

[0185] The following sections explain how the first information is carried in different A-control fields.

[0186] In some embodiments, the first information may be carried in a BQR control field. That is, the first field may be a subfield of the BQR control field. The first field may occupy one bit in the BQR control field. For example, the first field may occupy one of bits B8-B9 in the BQR control field.

[0187] Figure 9 is an example diagram of a BQR control field format provided in an embodiment of this application. As shown in Figure 9, the first field occupies B8 in the BQR control field.

[0188] Regarding Figure 9, a value of 0 in B8 of the BQR control field indicates that DRU is requested or recommended; a value of 1 in B8 of the BQR control field indicates that DRU is not requested or recommended. Alternatively, a value of 1 in B8 of the BQR control field indicates that DRU is requested or recommended; a value of 0 in B8 of the BQR control field indicates that DRU is not requested or recommended.

[0189] In some embodiments, the MAC frame header may include multiple BQR control fields. In this case, first information is carried in one or all of the multiple BQR control fields. That is, one or all of the multiple BQR control fields may contain the first field. Optionally, when the first information is carried in all of the multiple BQR control fields, the value of the first field in the multiple BQR control fields may be the same. For example, the first information may be carried in the BQR control field indicating the primary 160MHz channel, and / or, the first information may be carried in the BQR control field indicating a non-primary 160MHz channel.

[0190] As one possible implementation, the first field exists in both the BQR control field indicating the primary 160MHz channel and the BQR control field indicating the non-primary 160MHz channel. When the operating bandwidth (BW) of the non-AP STA is greater than 160MHz, the first field in the two transmitted BQR controls can be set to the same value.

[0191] As another possible implementation, the first field exists only in the BQR control field indicating the primary 160MHz channel, while the first field in the BQR control field indicating a non-primary 160MHz channel is reserved or indicates other information.

[0192] Optionally, if the unsolicited BQR transmitted by the non-AP STA is in response to a specific trigger frame (e.g., a trigger frame other than a null data PPDU feedback report poll (NFRP) frame, a multi-user request to send (MU-RTS) frame, and a bandwidth query report poll (BQRP) frame), or if the non-AP STA transmits an unsolicited BQR, it may indicate that the non-AP STA is suggesting or requesting the AP to use a DRU immediately following the transmission of a TB PPDU after issuing the unsolicited BQR.

[0193] Optionally, if a non-AP STA transmits an unrequested BQR after accessing the radio medium using enhanced distributed channel access (EDCA), it can indicate that the non-AP STA is suggesting or requesting the AP that, after issuing the unrequested BQR, the non-AP STA use a DRU when transmitting a TB PPDU during the subsequent TXOP of the AP.

[0194] The following implementation 4 illustrates the technical solution of carrying the first information in the BQR control field.

[0195] Example 4

[0196] In Example 4, a value of 0 in the DRU Recommendation field indicates a request or recommendation to use DRU; otherwise, the DRU Recommendation field is set to a value of 1.

[0197] Example 4 pertains to the wireless communication process within the TXOP of the AP. Figure 10 is an example diagram of a wireless communication process provided in Example 4. The method shown in Figure 10 can be performed by non-AP STAs 1 to 4 (represented as STA1 to 4 in the figure) and the AP. In Figure 10, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0198] The communication process shown in Figure 10 may include steps S1010 to S1040.

[0199] In step S1010, the AP requests TB PPDUs from non-AP STAs 1 to 4, and all requested TB PPDUs are transmitted using RRU.

[0200] In step S1020, non-AP STA1 to 4 use RRU to send TB PPDU to AP.

[0201] Non-AP STA 1 and non-AP STA 2 want to use DRU in the next TB PPDU. Therefore, the DRU recommendation subfield in the BQR control field of the MAC frame carried by this TB PPDU is set to 0, indicating that the AP is recommended or requested to use DRU.

[0202] For non-AP STA 3 and non-AP STA 4, since DRU is not intended to be used, the DRU recommendation subfield in the BQR control field of the MAC frame carried by the TB PPDU is set to 1.

[0203] In step S1030, based on the DRU recommendation field in the TB PPDU, the AP sends a trigger frame.

[0204] The trigger frame in step S1030 is used to trigger the next transmission of TB PPDU using DRU for non-AP STA 1 and non-AP STA 2 after step S1020.

[0205] In step S1040, non-AP STA 1 and non-AP STA 2 use DRU to send TB PPDU.

[0206] It should be noted that for non-AP STA 3 and non-AP STA 4, the AP can trigger them to send TB PPDUs using RRUs via the trigger frame in step S1030. That is, a single trigger frame can trigger non-AP STAs 1-4 to send TB PPDUs, and different TB PPDUs can use different RU types. Alternatively, the AP can send another trigger frame after step S1030 to trigger non-AP STA 3 and non-AP STA 4 to send TB PPDUs using RRUs.

[0207] In some embodiments, the first information may be carried in a link adaptation control field. The link adaptation control field may include link adaptation control fields corresponding to one or more protocols. For example, the link adaptation control field may include an ELA control field.

[0208] Figure 11 is a format example diagram of an ELA control field provided in an embodiment of this application. As shown in Figure 11, the first field carrying the first information can occupy the first bit in the MSI / partial PPDU parameter subfield of the ELA control field.

[0209] For example, if the unsolicited MFB field is 1 and the MRQ / UL EHT TB PPDU MFB field is 1, then for the first field, a value of 0 indicates that the non-AP STA requests or recommends the use of DRU, and a value of 1 indicates that the non-AP STA does not request or recommend the use of DRU; otherwise, the first field can be reserved.

[0210] For example, if the non-requested MFB field is 1 and the MRQ / UL EHT TB PPDU MFB field is 1, then for the first field, a value of 1 indicates that the non-AP STA requests or recommends the use of DRU, and a value of 0 indicates that the non-AP STA does not request or recommend the use of DRU; otherwise, the first field can be reserved.

[0211] In some embodiments, if the ELA control field is transmitted by the UHR AP, the first field may be reserved.

[0212] In other embodiments, the ELA control field can be transmitted by the UHR AP and / or the UHR non-AP STA. That is, the first field in the ELA control field transmitted by the UHR AP and / or the UHR non-AP STA is not reserved and can be used to indicate first information.

[0213] In some embodiments, the link adaptation control field may include a UHR link adaptation control field. A first field may be added to the UHR link adaptation control field. This application does not restrict the position of the first field in the UHR link adaptation control field.

[0214] For example, if the UHR link adaptation control field is transmitted by a non-AP STA and its content indicates a request or suggestion regarding subsequent TB PPDUs, then for the first field, a value of 0 indicates that the non-AP STA sending this first field requests or suggests using DRU for subsequent TB PPDU transmissions; a value of 1 indicates that the non-AP STA sending this first field does not request or suggest using DRU for subsequent TB PPDU transmissions. Otherwise, the first field can be reserved.

[0215] For example, if the UHR link adaptation control field is transmitted by a non-AP STA and its content indicates a request or suggestion regarding subsequent TB PPDUs, then for the first field, a value of 1 indicates that the non-AP STA sending this first field requests or suggests the use of DRUs for subsequent TB PPDU transmissions; a value of 0 indicates that the non-AP STA sending this first field does not request or suggest the use of DRUs for subsequent TB PPDU transmissions. Otherwise, the first field can be reserved.

[0216] In some embodiments, if the UHR link adaptation control field is transmitted by the UHR AP, the first field may be reserved.

[0217] In other embodiments, the UHR link adaptation control field can be transmitted by the UHR AP and / or the UHR non-AP STA. That is, the first field in the UHR link adaptation control field transmitted by the UHR AP and / or the UHR non-AP STA is not reserved and can be used to indicate first information.

[0218] The technical solution of carrying the first information in the link adaptation control field is described in detail below through Example 5.

[0219] Example 5

[0220] In Example 5, a value of 0 in the DRU Recommendation field indicates a request or recommendation to use DRU; otherwise, the DRU Recommendation field is set to a value of 1.

[0221] Example 5 pertains to the wireless communication process within the TXOP of the AP. Figure 12 is an example diagram of a wireless communication process provided in Example 5. The method shown in Figure 12 can be performed by non-AP STA1-2 (denoted as STA1-2 in the figure) and the AP. In Figure 12, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0222] The communication process shown in Figure 12 may include steps S1210 to S1240.

[0223] In step S1210, the AP requests TB PPDU from non-AP STA 1 and 2 and transmits it using RRU.

[0224] In step S1220, non-AP STA 1 wants to use DRU in the next TB PPDU and sets the DRU recommendation field in the UHR link adaptation control field of the MAC frame carried by this TB PPDU to 0, in order to recommend or request the AP that subsequent TB PPDU transmissions use DRU after the UHR link adaptation control field is sent.

[0225] Since non-AP STA 2 does not want to use DRU, the DRU recommendation field in the UHR link adaptation control field of the MAC frame carried by the TB PPDU is set to 1.

[0226] In step S1230, after receiving the TB PPDU from step S1220, the AP requests the TB PPDU from non-AP STA 1 in the next trigger frame and transmits it using DRU.

[0227] In step S1240, based on the trigger frame of step S1230, non-AP STA1 sends a TB PPDU using DRU.

[0228] In some embodiments, the first information may be carried in the OM control field. The link adaptation control field may include OM control fields corresponding to one or more protocols. For example, the OM control field may include the EHT OM control field.

[0229] Optionally, the first field carrying the first information may occupy one of the bits B4-B5 in the EHT OM control field. Figure 13 is a schematic diagram of the format of an EHT OM control field provided in an embodiment of this application. As shown in Figure 13, the first field occupies bit B4 in the EHT OM control field.

[0230] In some embodiments, a value of 0 for B4 in the EHT OM control field can indicate a request or recommendation to use DRU; a value of 1 for B4 in the EHT OM control field can indicate no request or recommendation to use DRU. Alternatively, a value of 1 for B4 in the EHT OM control field can indicate a request or recommendation to use DRU; a value of 0 for B4 in the EHT OM control field can indicate no request or recommendation to use DRU.

[0231] In some embodiments, if the EHT OM control field is transmitted by the AP, the first field may be reserved.

[0232] In other embodiments, the EHT OM control field can be transmitted by the AP and / or non-AP STA. That is, the first field in the EHT OM control field transmitted by the AP and / or non-AP STA is not reserved and can be used to indicate first information.

[0233] In some embodiments, the OM control field may include a UHR OM control field. A first field may be added to the UHR OM control field. This application does not restrict the position of the first field in the UHR OM control field.

[0234] For example, a value of 0 in the first field of the UHR OM control field can indicate that DRU is requested or recommended; a value of 1 in the first field of the UHR OM control field can indicate that DRU is not requested or recommended. Alternatively, a value of 1 in the first field of the UHR OM control field can indicate that DRU is requested or recommended; a value of 0 in the first field of the UHR OM control field can indicate that DRU is not requested or recommended.

[0235] In some embodiments, if the UHR OM control field is transmitted by the UHR AP, the first field may be reserved.

[0236] In other embodiments, the UHR OM control field can be transmitted by the UHR AP and / or the UHR non-AP STA. That is, the first field in the UHR OM control field transmitted by the UHR AP and / or the UHR non-AP STA is not reserved and can be used to indicate first information.

[0237] The following describes in detail the technical solution of carrying the first information in the OM control field through Example 6.

[0238] Example 6

[0239] In Example 6, a value of 0 in the DRU Recommendation field indicates a request or recommendation to use DRU; otherwise, the DRU Recommendation field is set to a value of 1.

[0240] Example 6 pertains to the wireless communication process within the TXOP of a non-AP STA. Figure 14 is an example diagram of a wireless communication process provided in Example 6. The method shown in Figure 14 can be performed by a non-AP STA. In Figure 14, DL represents the transmission from the AP to the non-AP STA, and UL represents the transmission from the non-AP STA to the AP.

[0241] The communication process shown in Figure 14 may include steps S1410 to S1440.

[0242] In step S1410, when the non-AP STA is the TXOP holder, the non-AP STA actively suggests or requests the AP that if the AP triggers the non-AP STA to perform UL TB PPDU transmission, DRU transmission can be used.

[0243] In step S1410, the non-AP STA sets the DRU recommendation field in the UHR OM control field of the MAC frame carried by this TB PPDU to 0, indicating that it suggests or requests the AP that after issuing the UHR OM control, the non-AP STA can use DRU for subsequent TB PPDU transmissions.

[0244] In step S1420, during the TXOP of a certain AP, the AP requests a TB PPDU to the non-AP STA for DRU transmission in the trigger frame.

[0245] In some embodiments, the first information can be carried through a new A-control field. That is, compared with related technologies, this application proposes a new variant of the A-control field. This new variant of the A-control field can be used to carry the first information. The new A-control field can be referred to as the DRU recommended control field.

[0246] It should be noted that the DRU recommended control field can appear in QoS data frames, QoS empty frames, or management frames.

[0247] Figure 15 is a schematic diagram of the format of a DRU recommendation control field provided in an embodiment of this application.

[0248] As shown in Figure 15, the DRU recommended control fields may include a control identifier field and a control information field. The control information field may include a first field.

[0249] The control identifier field can indicate a variant type of A-control. In the DRU recommended control field proposed in this application, the value of the control identifier field can be any integer between 10 and 14. For example, a control identifier field value of 10 can indicate that the A-control is a DRU recommended control field.

[0250] In some embodiments, a value of 0 in the first field of the DRU recommendation control field may indicate a request or recommendation for non-AP STAs to use DRUs; a value of 1 in the first field of the DRU recommendation control field may indicate that non-AP STAs are not requested or recommended to use DRUs. Alternatively, a value of 1 in the first field of the DRU recommendation control field may indicate a request or recommendation for non-AP STAs to use DRUs; a value of 0 in the first field of the DRU recommendation control field may indicate that non-AP STAs are not requested or recommended to use DRUs.

[0251] It should be noted that the control information field shown in Figure 15 may also include other fields besides the first field, and this application does not impose any restrictions. Furthermore, this application does not restrict the position of the first field within the control information field.

[0252] In one embodiment, if the DRU recommendation control field is transmitted by the UHR AP, the first field is reserved.

[0253] In another embodiment, the DRU recommendation control field can be transmitted by the UHR AP and / or the UHR non-AP STA. That is, the first field in the DRU recommendation control field transmitted by the UHR AP and / or the UHR non-AP STA is not reserved and can be used to indicate first information.

[0254] In some embodiments, a non-AP STA may send third information to the AP. This third information may be used to request or suggest the DRU distributed bandwidth to be used by the non-AP STA.

[0255] Optionally, the third piece of information may indicate that the DRU distributed bandwidth used by the non-AP STA is less than the operating bandwidth (BW) of that non-AP STA.

[0256] For example, within the TXOP of a non-AP STA, if the non-AP STA performs a CCA on some or all of its sub-channels within its operating bandwidth and finds that a certain sub-channel is busy, the non-AP STA will proactively suggest or request the AP that if the AP requests the non-AP STA to use DRU to transmit TB PPDU in the next TXOP, the distributed bandwidth of the DRU used should be less than the operating bandwidth of the non-AP STA.

[0257] In some embodiments, the third information may be carried in the MAC frame header and / or PPDU. Exemplarily, the third information may be carried in the same MAC frame header and / or the same PPDU as the first information.

[0258] When third-party information is carried in the MAC frame header, it can be carried in the A-control field. For example, third-party information can be carried in one or more of the following fields: BQR control field, link adaptation control field, and OM control field.

[0259] For example, the third information can be carried in the second field. The second field can also be called the DRU distributed BW reduction field. The second field can be a subfield of one or more of the following fields: BQR control field, link adaptation control field, and OM control field.

[0260] For example, the second field can occupy one of bits B8-B9 in the BQR control field to indicate third information. Figure 16 is an example diagram of the format of a BQR control field provided in an embodiment of this application. As shown in Figure 16, B9 in the BQR control field can be the second field.

[0261] It should be noted that if a non-AP STA transmits a non-requested BQR in response to a specific trigger frame (e.g., a trigger frame other than NFRP, MU-RTS, and BQRP), or if a non-AP STA transmits a non-requested BQR, it indicates that the non-AP STA is suggesting or requesting the AP to use a DRU immediately following the non-AP STA's next TB PPDU transmission after issuing the non-requested BQR.

[0262] It should be noted that if a non-AP STA transmits a non-requested BQR after accessing the radio medium via EDCA, it means that the non-AP STA is suggesting or requesting the AP to use a DRU when transmitting TB PPDUs in the subsequent TXOP of the AP after issuing the non-requested BQR.

[0263] For example, the second field can occupy one of the bits B4-B5 in the EHT OM control field to indicate third information. For instance, the second field can occupy bit B5 in the EHT OM control field.

[0264] For example, the second field can be carried within the DRU recommendation control field.

[0265] In some embodiments, if the first field indicates a recommendation or request for a non-AP STA to use a DRU, a value of 0 in the second field may indicate that the distributed bandwidth of the DRU allocated to it is less than the operating bandwidth of the non-AP STA; if the first field indicates a recommendation or request for a non-AP STA to use a DRU, a value of 1 in the second field may indicate that the distributed bandwidth of the DRU allocated to it is not recommended or requested to be less than the operating bandwidth of the non-AP STA. If the first field indicates that the use of a DRU by a non-AP STA is not recommended or requested, the second field may be reserved.

[0266] In some embodiments, if the first field indicates a recommendation or request for a non-AP STA to use a DRU, a value of 1 in the second field may indicate that the distributed bandwidth of the DRU allocated to it is less than the operating bandwidth of the non-AP STA; if the first field indicates a recommendation or request for a non-AP STA to use a DRU, a value of 0 in the second field may indicate that the distributed bandwidth of the DRU allocated to it is not recommended or requested to be less than the operating bandwidth of the non-AP STA. If the first field indicates that the use of a DRU by a non-AP STA is not recommended or requested, the second field may be reserved.

[0267] The method embodiments of this application have been described in detail above. The apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0268] Figure 17 is a schematic structural diagram of a non-AP STA 1700 provided in an embodiment of this application. The non-AP STA 1700 may include a transmitting unit 1710.

[0269] The sending unit 1710 is used to send first information to the AP; wherein the first information is used to request or suggest that non-AP STAs use DRU.

[0270] In an optional embodiment, the transmitting unit 1710 may be a transceiver 1930. The non-AP STA 1700 may also include a processor 1910 and a memory 1920, as shown in FIG19.

[0271] In this embodiment, the non-AP STA 1700 described above can be used to execute some or all of the method steps performed by the non-AP STA in the above method embodiments. The non-AP STA 1700 includes units or modules for executing the method steps corresponding to the foregoing figures. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing figures can be incorporated into this embodiment and correspond to the modules in the non-AP STA 1700.

[0272] Figure 18 is a schematic structural diagram of an AP 1800 provided in an embodiment of this application. The AP 1800 may include a receiving unit 1810.

[0273] The receiving unit 1810 is used to receive first information sent by a non-AP STA; wherein the first information is used to request or suggest that the non-AP STA use DRU.

[0274] In an optional embodiment, the receiving unit 1810 may be a transceiver 1930. The AP 1800 may also include a processor 1910 and a memory 1920, as shown in FIG19.

[0275] In this embodiment, AP 1800 can be used to execute some or all of the method steps executed by AP in the above method embodiments. AP 1800 includes units or modules for executing the method steps corresponding to the foregoing figures. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing figures can be incorporated into this embodiment and correspond to the modules in AP 1800.

[0276] Figure 19 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 19 indicate that the unit or module is optional. The apparatus 1900 can be used to implement the methods described in the above method embodiments. The apparatus 1900 can be a chip or a communication device. The communication device can be an AP or a non-AP STA.

[0277] Apparatus 1900 may include one or more processors 1910. The processor 1910 may support apparatus 1900 in implementing the methods described in the preceding method embodiments. The processor 1910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0278] The apparatus 1900 may further include one or more memories 1920. The memories 1920 store a program that can be executed by the processor 1910, causing the processor 1910 to perform the methods described in the preceding method embodiments. The memories 1920 may be independent of the processor 1910 or integrated within the processor 1910.

[0279] The device 1900 may also include a transceiver 1930. The processor 1910 can communicate with other devices or chips via the transceiver 1930. For example, the processor 1910 can send and receive data with other devices or chips via the transceiver 1930.

[0280] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0281] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0282] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0283] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0284] In the embodiments of this application, a "field" may also be referred to as a "domain", "subfield", or "subfield". A field may occupy one or more bytes (byte / octet), or a field may occupy one or more bits (bit).

[0285] The field names defined in the embodiments of this application are merely examples, and the field may have other names.

[0286] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0287] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0288] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0289] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including AP and STA). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0290] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0291] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".

[0292] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0293] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the WiFi protocol and related protocols applied to future WiFi communication systems, and this application does not limit it.

[0294] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0295] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0296] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0297] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0298] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of wireless communication, the method comprising: Comprising: a non-AP station (non-AP STA) sends first information to an AP; wherein the first information is used to request or suggest that the non-AP STA uses distributed resource units (DRUs).

2. The method of claim 1, wherein, The first information is used to request or suggest that: the non-AP STA uses a DRU to transmit a next physical layer protocol data unit (PPDU) after transmitting the first information; and / or the non-AP STA uses DRUs to transmit one or more PPDUs within a transmission opportunity (TXOP) of the AP.

3. The method of claim 2, wherein: if the first information is transmitted within a TXOP of the AP, the first information is used to request or suggest that the non-AP STA uses a DRU to transmit a next PPDU after transmitting the first information; and / or if the first information is transmitted within a TXOP of the non-AP STA, the first information is used to request or suggest that the non-AP STA uses DRUs to transmit one or more PPDUs within a TXOP of the AP.

4. The method according to any one of claims 1-3, characterized in that, The first information is used to request or suggest that the non-AP STA uses DRUs within a first time period.

5. The method of claim 4, wherein, The first time period satisfies one or more of: the first time period belongs to a TXOP of the AP; a start time of the first time period is determined based on a transmission time of the first information; an end time of the first time period is determined based on second information transmitted by the non-AP STA, the second information being used to revoke the request or suggestion that the non-AP STA uses DRUs.

6. The method according to any one of claims 1-5, characterized in that, The method further comprises: the non-AP STA transmits second information to the AP; wherein the second information is used to revoke the request or suggestion that the non-AP STA uses DRUs.

7. The method of claim 6, wherein, The first information and the second information are carried in a same field.

8. The method according to any one of claims 1-7, characterized in that, The method further comprises: the non-AP STA receives a first trigger frame transmitted by the AP; wherein the first trigger frame is used to trigger the non-AP STA to transmit a first PPDU, the first trigger frame being determined based on the first information.

9. The method of claim 8, wherein: in a case where the AP accepts the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to transmit the first PPDU using DRUs; and / or in a case where the AP does not accept the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to transmit the first PPDU using regular resource units (RRUs). The first PPDU is a trigger-based PPDU.

10. The method according to claim 8 or 9, characterized in that, The non-AP STA transmitting the first information to the AP comprises:

11. The method according to any one of claims 1-10, characterized in that, in a case where a first condition is satisfied, the non-AP STA transmits the first information to the AP; wherein the first condition is related to one or more of: a result of a data unit received by the AP; ​ a state of sub-channels used by the non-AP STA; a throughput of the non-AP STA; a modulation and coding scheme (MCS) of the non-AP STA; a data amount of the non-AP STA.

12. The method of claim 11, wherein, The first condition comprises one or more of: the AP feeds back that the AP does not receive data units or a number of received data units is less than a first number threshold; one or more sub-channels used by the non-AP STA is in a busy state; a throughput of the non-AP STA is less than or equal to a first throughput threshold; a data amount of the non-AP STA is greater than or equal to a first data amount threshold; a MCS of the non-AP STA is less than or equal to a first MCS threshold.

13. The method according to any one of claims 1-12, characterized in that, The first information is carried in a medium access control (MAC) frame header and / or a physical protocol data unit (PPDU).

14. The method of claim 13, wherein, In a case that the first information is carried in the MAC frame header, the first information is carried in an aggregation control field.

15. The method of claim 14, wherein, The first information is carried in one or more of: a bandwidth query report (BQR) control field; a link adaptation control field; an operation mode (OM) control field.

16. The method of claim 15, wherein, In a case that the first information is carried in the BQR control field and the MAC frame header comprises a plurality of BQR control fields, the first information is carried in one or all of the plurality of BQR control fields.

17. The method of any one of claims 1-16, wherein, The method further comprises: the non-AP STA sends third information to the AP; wherein the third information is used to request or suggest a DRU distribution bandwidth used by the non-AP STA.

18. A method of wireless communication, the method comprising: comprises: an access point (AP) receives first information sent by a non-AP station (non-AP STA); wherein the first information is used to request or suggest a distributed resource unit (DRU) used by the non-AP STA.

19. The method of claim 18, wherein, The first information is used to request or suggest: the non-AP STA uses a DRU to transmit a next physical layer protocol data unit (PPDU) after transmitting the first information; and / or the non-AP STA uses a DRU to transmit one or more PPDUs within a transmission opportunity (TXOP) of the AP.

20. The method of claim 19, wherein, if the first information is transmitted within a TXOP of the AP, the first information is used to request or suggest that the non-AP STA uses a DRU to transmit a next PPDU after transmitting the first information; and / or, if the first information is transmitted within a TXOP of the non-AP STA, the first information is used to request or suggest that the non-AP STA uses a DRU to transmit one or more PPDUs within a TXOP of the AP.

21. The method of any one of claims 18-20, wherein, The first information is used to request or suggest that the non-AP STA uses a DRU within a first time period.

22. The method of claim 21, wherein, The first time period satisfies one or more of: the first time period belongs to a TXOP of the AP; a start time of the first time period is determined based on a transmission time of the first information; and / or an end time of the first time period is determined based on a transmission time of the first information. An end time of the first time period is determined based on second information transmitted by the non-AP STA, the second information being used for revoking a request or suggesting the non-AP STA to use DRU.

23. The method of any one of claims 18-22, wherein, The method further comprises: The AP receives second information transmitted by the non-AP STA; The second information is used for revoking a request or suggesting the non-AP STA to use DRU.

24. The method of claim 23, wherein, The first information and the second information are carried in a same field.

25. The method of any one of claims 18-24, wherein, The method further comprises: The AP transmits a first trigger frame to the non-AP STA; The first trigger frame is used for triggering the non-AP STA to transmit the first PPDU, and the first trigger frame is determined based on the first information.

26. The method of claim 25, wherein, In a case where the AP accepts the request or suggestion of the first information, the first trigger frame is used for triggering the non-AP STA to transmit the first PPDU using DRU; and / or, In a case where the AP does not accept the request or suggestion of the first information, the first trigger frame is used for triggering the non-AP STA to transmit the first PPDU using regular resource unit (RRU).

27. The method of claim 25 or 26, wherein, The first PPDU is a trigger-based PPDU.

28. The method of any one of claims 18-27, wherein, The AP receiving first information transmitted by the non-AP STA comprises: In a case where a first condition is met, the AP receives the first information transmitted by the non-AP STA; The first condition is related to one or more of the following: a result of data units received by the AP; a status of a sub-channel used by the non-AP STA; a throughput of the non-AP STA; a modulation and coding scheme (MCS) of the non-AP STA; a data amount of the non-AP STA.

29. The method of claim 28, wherein, The first condition comprises one or more of the following: the AP feeding back that the AP has not received data units or a number of received data units is less than a first number threshold; one or more sub-channels used by the non-AP STA are in a busy state; a throughput of the non-AP STA is less than or equal to a first throughput threshold; a data amount of the non-AP STA is greater than or equal to a first data amount threshold; a MCS of the non-AP STA is less than or equal to a first MCS threshold.

30. The method of any one of claims 18-29, wherein, The first information is carried in a MAC frame header and / or a PPDU.

31. The method of claim 30, wherein, In a case where the first information is carried in the MAC frame header, the first information is carried in an aggregation control field.

32. The method of claim 31, wherein, The first information is carried in one or more of the following fields: a bandwidth query report (BQR) control field; a link adaptation control field; an operation mode (OM) control field.

33. The method of claim 32, wherein, In a case where the first information is carried in the BQR control field and the MAC frame header comprises a plurality of BQR control fields, the first information is carried in one or all of the plurality of BQR control fields.

34. The method of any one of claims 18-33, wherein, The method further comprises: The AP receives third information sent by the non-AP STA; The third information is used to request or suggest a DRU distribution bandwidth used by the non-AP STA.

35. A non-access point station non-AP STA, characterized in that, The non-AP STA comprises: A sending unit configured to send first information to an access point (AP); The first information is used to request or suggest a distributed resource unit (DRU) used by the non-AP STA.

36. The non-AP STA of claim 35, wherein, The first information is used to request or suggest: The non-AP STA uses a DRU to send a next physical layer protocol data unit (PPDU) after sending the first information; and / or The non-AP STA uses a DRU to send one or more PPDUs within a transmission opportunity (TXOP) of the AP.

37. The non-AP STA of claim 36, wherein: If the first information is sent within the TXOP of the AP, the first information is used to request or suggest that the non-AP STA uses a DRU to send a next PPDU after sending the first information; and / or If the first information is sent within the TXOP of the non-AP STA, the first information is used to request or suggest that the non-AP STA uses a DRU to send one or more PPDUs within the TXOP of the AP.

38. The non-AP STA of any one of claims 35-37, wherein, The first information is used to request or suggest that the non-AP STA uses a DRU within a first time period.

39. The non-AP STA of claim 38, wherein, The first time period satisfies one or more of the following: The first time period belongs to the TXOP of the AP; A start time of the first time period is determined based on a sending time of the first information; An end time of the first time period is determined based on second information sent by the non-AP STA, the second information being used to revoke the request or suggestion that the non-AP STA uses a DRU.

40. The non-AP STA of any one of claims 35-39, wherein, The non-AP STA is further configured to: send second information to the AP; The second information is used to revoke the request or suggestion that the non-AP STA uses a DRU.

41. The non-AP STA of claim 40, wherein, The first information and the second information are carried in a same field.

42. The non-AP STA of any one of claims 35-41, wherein, The non-AP STA is further configured to: receive a first trigger frame sent by the AP; The first trigger frame is used to trigger the non-AP STA to send a first PPDU, and the first trigger frame is determined based on the first information.

43. The non-AP STA of claim 42, wherein: In a case where the AP accepts the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to use a DRU to send the first PPDU; and / or In a case where the AP does not accept the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to use a regular resource unit (RRU) to send the first PPDU. The first PPDU is a trigger-based PPDU.

44. The non-AP STA of claim 42 or 43, wherein, The non-AP STA sending the first information to the AP comprises:

45. The non-AP STA of any one of claims 35-44, wherein, ​ in a case where the first condition is met, the non-AP STA sends the first information to the AP; wherein the first condition relates to one or more of: a result of a data unit received by the AP; a state of a subchannel used by the non-AP STA; a throughput of the non-AP STA; a modulation coding scheme (MCS) of the non-AP STA; a data amount of the non-AP STA.

46. The non-AP STA of claim 45, wherein, the first condition comprises one or more of: the AP feeds back that the AP does not receive a data unit or a number of data units received is less than a first number threshold; one or more subchannels used by the non-AP STA is in a busy state; the throughput of the non-AP STA is less than or equal to a first throughput threshold; the data amount of the non-AP STA is greater than or equal to a first data amount threshold; the MCS of the non-AP STA is less than or equal to a first MCS threshold.

47. The non-AP STA of any one of claims 35-46, wherein, the first information is carried in a medium access control (MAC) frame header and / or a physical protocol data unit (PPDU).

48. The non-AP STA of claim 47, wherein, in a case where the first information is carried in the MAC frame header, the first information is carried in an aggregate control field.

49. The non-AP STA of claim 48, wherein, the first information is carried in one or more of: a bandwidth query report (BQR) control field; a link adaptation control field; an operation mode (OM) control field.

50. The non-AP STA of claim 49, wherein, in a case where the first information is carried in the BQR control field and the MAC frame header comprises a plurality of BQR control fields, the first information is carried in one or all of the plurality of BQR control fields.

51. The non-AP STA of any one of claims 35-50, wherein, the non-AP STA is further configured to: send third information to the AP; wherein the third information is used to request or suggest a DRU distribution bandwidth used by the non-AP STA.

52. An access point (AP) comprising: comprises: a receiving unit, configured to receive first information sent by a non-access point station (non-AP STA); wherein the first information is used to request or suggest a distributed resource unit (DRU) used by the non-AP STA.

53. The AP of claim 52, wherein, the first information is used to request or suggest: the non-AP STA to use a DRU to send a next physical layer protocol data unit (PPDU) after sending the first information; and / or the non-AP STA to use a DRU to send one or more PPDUs within a transmission opportunity (TXOP) of the AP.

54. The AP of claim 53, wherein, if the first information is sent within a TXOP of the AP, the first information is used to request or suggest the non-AP STA to use a DRU to send a next PPDU after sending the first information; and / or, if the first information is sent within a TXOP of the non-AP STA, the first information is used to request or suggest the non-AP STA to use a DRU to send one or more PPDUs within a TXOP of the AP.

55. The AP of any one of claims 52-54, wherein, the first information is used to request or suggest the non-AP STA to use a DRU within a first time period.

56. The AP of claim 55, wherein, The first time period satisfies one or more of the following: The first time period belongs to a TXOP of the AP; A start time of the first time period is determined based on a sending time of the first information; An end time of the first time period is determined based on second information sent by the non-AP STA, the second information being used for a revocation request or suggesting the non-AP STA to use a DRU.

57. The AP of any one of claims 52-56, wherein, The AP is further configured to: receive second information sent by the non-AP STA; wherein the second information is used for a revocation request or suggesting the non-AP STA to use a DRU.

58. The AP of claim 57, wherein, The first information and the second information are carried in a same field.

59. The AP of any one of claims 52-58, wherein, The AP is further configured to: send a first trigger frame to the non-AP STA; wherein the first trigger frame is used to trigger the non-AP STA to send a first PPDU, and the first trigger frame is determined based on the first information.

60. The AP of claim 59, wherein, in a case where the AP accepts the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to send the first PPDU using a DRU; and / or, in a case where the AP does not accept the request or suggestion of the first information, the first trigger frame is used to trigger the non-AP STA to send the first PPDU using a regular resource unit (RRU).

61. The AP of any one of claims 59 or 60, wherein, The first PPDU is a trigger-based PPDU.

62. The AP of any one of claims 52-61, wherein, The AP receiving first information sent by a non-AP STA comprises: in a case where a first condition is satisfied, the AP receiving the first information sent by the non-AP STA; wherein the first condition is related to one or more of the following: a result of data units received by the AP; a status of a subchannel used by the non-AP STA; a throughput of the non-AP STA; a modulation and coding scheme (MCS) of the non-AP STA; a data amount of the non-AP STA.

63. The AP of claim 62, wherein, The first condition comprises one or more of the following: the AP feeding back that the AP has not received data units or a number of received data units is less than a first number threshold; one or more subchannels used by the non-AP STA are in a busy state; the throughput of the non-AP STA is less than or equal to a first throughput threshold; the data amount of the non-AP STA is greater than or equal to a first data amount threshold; the MCS of the non-AP STA is less than or equal to a first MCS threshold.

64. The AP of any one of claims 52-63, wherein, The first information is carried in a medium access control (MAC) frame header and / or a PPDU.

65. The AP of claim 64, wherein, In a case where the first information is carried in a MAC frame header, the first information is carried in an aggregation control field.

66. The AP of claim 65, wherein, The first information is carried in one or more of the following fields: a bandwidth query report (BQR) control field; a link adaptation control field; an operation mode (OM) control field.

67. The AP of claim 66, wherein, In a case that the first information is carried in the BQR control field and the MAC frame header includes a plurality of BQR control fields, the first information is carried in one or all of the plurality of BQR control fields.

68. The AP of any one of claims 52-67, wherein, The AP is further configured to: receive third information sent by the non-AP STA; wherein the third information is used to request or suggest a DRU distribution bandwidth used by the non-AP STA.

69. A communications device, characterized by A communication device comprising a transceiver, a memory, and a processor, the memory configured to store a program, the processor configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method according to any one of claims 1-34.

70. An apparatus comprising: A device comprising a processor configured to invoke a program from a memory, so that the device performs the method according to any one of claims 1-34.

71. A chip, comprising: A chip comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method according to any one of claims 1-34.

72. A computer-readable storage medium, comprising, A computer program product having stored thereon a program, the program causing a computer to perform the method according to any one of claims 1-34.

73. A computer program product, characterized in that, A computer program product having stored thereon a program, the program causing a computer to perform the method according to any one of claims 1-34.

74. A computer program characterised in that, A computer program product having stored thereon a program, the program causing a computer to perform the method according to any one of claims 1-34.

Images