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 receives a first request sent by an AP, the first request being used for requesting the non-AP STA to send a PPDU on a first channel, the bandwidth of the first channel being represented by means of one or more first bandwidths, the PPDU being transmitted on a first bandwidth by means of a DRU, and the first request further being used for indicating a distribution bandwidth of the DRU. On the basis of the first request, the non-AP STA can determine the distribution bandwidth of the DRU allocated to the non-AP STA, so that the non-AP STA can send the PPDU on a corresponding distribution bandwidth, thereby implementing a DRU-based communication process.

Description

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

[0001] The present application relates to the technical field of communication, and more particularly, to a wireless communication method, a non-access point station and an access point. BACKGROUND

[0002] With the development of technology, a resource unit (RU) can have not only continuous subcarriers but also discontinuous subcarriers. An RU with continuous subcarriers can be referred to as a regular RU (RRU or rRU). An RU with discontinuous subcarriers can be referred to as a distributed RU (DRU or dRU).

[0003] SUMMARY

[0004] The present application provides a wireless communication method, a non-access point station and an access point. Each aspect of the present application is described below.

[0005] In a first aspect, a wireless communication method is provided. The method includes: a non-access point station (non-AP STA) receiving a first request sent by an access point (AP); wherein the first request is used to request the non-AP STA to send a physical layer protocol data unit (PPDU) on a first channel, the bandwidth of the first channel is represented by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by a DRU, and the first request is also used to indicate the distribution bandwidth of the DRU.

[0006] In a second aspect, a wireless communication method is provided. The method includes: an AP sending a first request to a non-AP STA; wherein the first request is used to request the non-AP STA to send a PPDU on a first channel, the bandwidth of the first channel is represented by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by a distributed resource unit (DRU), and the first request is also used to indicate the distribution bandwidth of the DRU.

[0007] In a third aspect, a non-AP STA is provided, which comprises: a receiving unit configured to receive a first request sent by an AP; wherein the first request is used to request the non-AP STA to send a PPDU on a first channel, a bandwidth of the first channel is indicated by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by a DRU, and the first request is further used to indicate a distribution bandwidth of the DRU.

[0008] In a fourth aspect, an AP is provided, which comprises: a sending unit configured to send a first request to a non-AP STA; wherein the first request is used to request the non-AP STA to send a PPDU on a first channel, a bandwidth of the first channel is indicated by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by a DRU, and the first request is further used to indicate a distribution bandwidth of the DRU.

[0009] In a fifth aspect, a non-AP STA is provided, which comprises a transceiver, a memory and a processor, the memory is configured to store a program, the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the non-AP STA performs the method in the first aspect.

[0010] In a sixth aspect, an AP is provided, which comprises a transceiver, a memory and a processor, the memory is configured to store a program, the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the AP performs the method in the second aspect.

[0011] In a seventh aspect, a communication system is provided, which comprises the communication device described above. In another possible design, the system can further include other devices interacting with the communication device in the solutions provided by the embodiments.

[0012] In an eighth aspect, a computer-readable storage medium is provided, which stores a computer program. The computer program causes a communication device to perform some or all of the steps of the methods in the aspects described above.

[0013] In a ninth aspect, a computer program product is provided, which comprises a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause a communication device to perform some or all of the steps of the methods in the aspects described above. In some implementations, the computer program product can be a software installation package.

[0014] In a tenth aspect, an embodiment of the present application provides a chip, which comprises a memory and a processor. The processor can call and run a computer program from the memory to implement part or all of the steps described in the method of each of the above aspects.

[0015] Based on the first request, the non-AP STA can determine the distribution bandwidth of the DRU allocated to itself, so that the non-AP STA can send a PPDU on the corresponding distribution bandwidth, thereby realizing the DRU-based communication process. BRIEF DESCRIPTION OF DRAWINGS

[0016] FIG. 1 is a schematic diagram of a wireless communication system to which embodiments of the present application are applied.

[0017] FIG. 2 is an example diagram of a scenario using DRU transmission.

[0018] FIG. 3 is an example diagram of the format of a trigger frame.

[0019] FIG. 4A is an example diagram of the format of a common Info field.

[0020] FIG. 4B is an example diagram of the format of a trigger dependent user Info field in a basic trigger frame.

[0021] FIG. 5 is an example diagram of the format of a special user Info field.

[0022] FIG. 6 is an example diagram of the format of a variant user Info field.

[0023] FIG. 7 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

[0024] FIG. 8 is an example diagram of the format of a variant user Info field provided by an embodiment of the present application.

[0025] FIG. 9 is an example diagram of a trigger dependent user Info subfield in a basic trigger frame provided by an embodiment of the present application.

[0026] FIG. 10 is an example diagram of the format of a common Info field provided by an embodiment of the present application.

[0027] FIG. 11 is a schematic structural diagram of a non-AP STA provided by an embodiment of the present application.

[0028] FIG. 12 is a schematic structural diagram of an AP provided by an embodiment of the present application.

[0029] FIG. 13 is a schematic structural diagram of an apparatus for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0031] Communication system

[0032] The technical solutions in the embodiments of the present application can be applied to various communication systems, for example, a wireless local area network (WLAN), a wireless fidelity (WiFi), a high performance radio local area network (HIPELAN), a wide area network (WAN), a cellular network or other communication systems, etc. For example, the technical solutions provided in the embodiments of the present application can be applied to a communication system adopting an 802.11 standard. Exemplarily, the 802.11 standard includes but is not limited to an 802.11ax standard, an 802.11be standard, a more next generation 802.11 standard, etc.

[0033] FIG. 1 shows a schematic diagram of a communication system to which the embodiments of the present application are applicable. As shown in FIG. 1, the communication devices in the communication system 100 can include an AP 111, an AP 112, a station (STA) 121 and a STA 122, wherein the STA 121 can access a network through the AP 111, and the STA 122 can access a network through the AP 112.

[0034] In some implementations, a STA can establish an association relationship with one or more APs, and then the STA and the APs having the association relationship can communicate with each other. As shown in FIG. 1, the AP 111 and the STA 121 can communicate with each other after establishing an association relationship, and the AP 112 and the STA 122 can communicate with each other after establishing an association relationship.

[0035] In some implementations, the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between non-AP STAs, or communication between a STA and a peer STA, wherein the peer STA can refer to a device communicating with the STA, for example, the peer STA can be an AP or a non-AP STA.

[0036] It should be understood that FIG. 1 exemplarily shows two AP STAs and two non-AP STAs, the communication system 100 can also include a larger number of AP STAs, or the communication system 100 can include other numbers of non-AP STAs, and embodiments of the present application do not limit this.

[0037] In addition, the above communication system can be applied to a multi-device cooperation scenario, such as a multi-AP (multiple access points, multi-AP) cooperation scenario, or a multi-site cooperation scenario.

[0038] In embodiments of the present application, the names of APs and / or STAs are not limited. In some scenarios, an AP can also be referred to as an AP STA, that is, in a certain sense, an AP is also a kind of STA. In other scenarios, a STA can also be referred to as a non-AP STA (non-AP STA).

[0039] In some scenarios, the above communication device can also be a multi-link device (multi-link device, MLD), that is, a device that can communicate through multiple communication links, where the multiple communication links can include communication links of different frequency bands, for example, can include millimeter wave frequency bands and / or low frequency frequency bands. Generally, if the multi-link device is an AP, the AP can also be referred to as a multi-link AP. If the multi-link device is a STA, the STA can also be referred to as a multi-link STA.

[0040] In embodiments of the present application, the AP can be a device in a wireless network. The AP can be a communication server, a router, a switch, a bridge, or the like, or the AP can include various forms of macro base stations, micro base stations, relay stations, etc., and of course the AP can also be a chip or circuit or processing system in these various forms of devices, thereby implementing the methods and functions of embodiments of the present application. The AP can be applied to various scenarios, such as sensor nodes in smart cities (such as smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, sound systems, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as AR, VR, etc. wearable devices), smart devices in smart offices (such as printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, some infrastructure in daily life (such as vending machines, self-service navigation stations in supermarkets, self-service checkout devices, self-service ordering machines), etc.

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

[0042] In the embodiments of the present application, the STA in the embodiments of the present application can be a device with wireless transceiving function, for example, can support 802.11 series protocols, and can communicate with an AP or other STAs. For example, the STA is any user communication device that allows a user to communicate with an AP and then communicate with a WLAN. The STA is, for example, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile terminal, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user equipment, etc.

[0043] The STA in the embodiments of the present application can also be a device providing voice / data connectivity to a user, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. For example, a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0044] By way of example and not limitation, in the embodiments of the present application, the STA can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. For example, a smart watch or smart glasses, etc., and only focus on a certain type of application function, need to be used with other devices such as a smart phone, such as various types of smart wristbands, smart jewelry, etc.

[0045] In addition, in the embodiments of the present application, the STA can also be a terminal device in an internet of things (IoT) system. The IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection. In the embodiments of the present application, the IoT technology can achieve massive connection, deep coverage and terminal power saving through, for example, narrow band (NB) technology.

[0046] In addition, in the embodiments of the present application, the STA can be a device in a vehicle-to-everything (V2X) system. The communication mode in the V2X system is collectively referred to as V2X (X represents anything). For example, the 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.

[0047] In addition, in the embodiments of the present application, the STA can also include a smart printer, a train detector, a gas station sensor, and the like, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the AP, and transmitting electromagnetic waves to transmit data to the AP.

[0048] In addition, the AP in the embodiments of the present application 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 for communicating with the STA through the wireless local area network.

[0049] From the perspective of the communication mode supported by the AP, in some implementation manners, the AP can be a device supporting the 802.11be mode. The AP can also be a device supporting multiple current and future WLAN modes of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

[0050] From the perspective of the communication mode supported by the STA, in some implementation manners, the non-AP STA can support the 802.11be mode. The non-AP STA can also support multiple current and future WLAN modes of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

[0051] In the embodiments of the present application, the frequency bands supported by the WLAN technology are not limited. In some implementations, the frequency bands supported by the WLAN technology can include, but are not limited to, low frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz), high frequency bands (such as 45 GHz, 60 GHz).

[0052] It should be understood that the specific forms of the STA and the AP in the embodiments of the present application are not specially limited, and are only exemplary described herein.

[0053] DRU

[0054] With the development of technology, the limit of power spectral density (PSD) is becoming more and more strict. For example, in the 6 GHz frequency band, the PSD limit for a non-AP STA in a low power indoor frequency band is -1 dBm / MHz.

[0055] The RRU has continuous subcarriers. The transmission power of each subcarrier of the RRU is low. This is because the PSD limit is defined per MHz and per STA, and the subcarriers in the RRU are continuous, so the number of subcarriers in each MHz is large, and according to the PSD limit, the transmission power of each subcarrier is low.

[0056] The DRU has discontinuous subcarriers. For the case of the DRU, the number of subcarriers in each MHz is small, and even there is only one subcarrier in each MHz, so compared with the RRU, the subcarriers in the DRU can be transmitted at a higher power. For example, for a 52-tone DRU distributed in 80 MHz, there can be only one subcarrier in each MHz. But for a 52-tone RRU, there are about 13 subcarriers in each MHz. In the 6 GHz low power indoor frequency band, the PSD limit is -1 dBm / MHz. Therefore, for a 52-tone RU (about 4 MHz), the maximum transmission power allowed using the RRU is only about 6 dBm, and using the DRU can increase the transmission power by 11 dB. This significant increase in transmission power can achieve a higher modulation and coding scheme (MCS) or achieve a longer transmission distance.

[0057] As shown in FIG. 2, STA1, STA2 and STA3 can all use DRU to increase their transmission power. Compared with using the same size of RRU, all the subcarriers obtain higher transmission power, so the overall spectrum efficiency is significantly improved.

[0058] 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".

[0059] DRU distributed bandwidth

[0060] For non-punctured 80MHz channels to which DRUs are applied, some implementations allow for diverse distributed bandwidth.

[0061] For example, a distributed bandwidth of 80MHz is reasonable in terms of power boosting gain and data rate. Alternatively, a distributed bandwidth of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz can support devices that can only operate with a narrow bandwidth (e.g., 20MHz).

[0062] Trigger frame

[0063] The technical solution proposed in this application is related to the trigger frame. Therefore, the trigger frame will be described below.

[0064] In some communication standards (such as IEEE 802.11), uplink trigger-based (TB) PPDU transmission can be implemented based on trigger frames. When performing uplink TB PPDU transmission, the AP can first send a trigger frame, and each non-AP STA can prepare and transmit the TB PPDU according to the parameters indicated by the received trigger frame.

[0065] Figure 3 is an example diagram of the trigger frame format.

[0066] As shown in FIG. 3, the trigger frame can include one or more of the following fields: frame control, duration, receiver address (RA), transmission address (TA), common info, user info list, padding, frame check sequence (FCS). The common info field, the user info list field, and the padding field among them are described below.

[0067] 1) Common info field

[0068] The common info field mainly carries common information. FIG. 4A is an example diagram of the format of the common info field.

[0069] As shown in FIG. 4A, the common info field can include one or more of the following fields: trigger type, UL length, more TF, CS required, UL BW, GI and HE / EHT / UHR-LTF type / trigger TXOP sharing mode, number of HE / EHT / UHR-LTF symbols, LDPC extra symbol segment, AP TX power, Pre-FEC padding factor, PE disambiguity, UL spatial reuse, HE / EHT / UHR P160, special user info field flag, EHT reserved, trigger dependent common info, reserved.

[0070] The trigger type field in the common info can be used to indicate a variant of the trigger frame. The variant of the trigger frame may, for example, include a basic trigger frame. The value of the trigger type field being a first value can represent the basic trigger frame. The first value may, for example, be 0 or 1.

[0071] The trigger dependent public info field is related to the variant of the trigger frame. The trigger dependent public info field can be used to indicate the public information in the corresponding variant trigger frame that is different from other variant trigger frames (i.e., the public information specific to this variant trigger frame). It is noted that the trigger dependent public info field can not exist in some variant trigger frames. For example, the trigger dependent public info field can not exist in the basic trigger frame.

[0072] Similar to the trigger dependent public info field, the trigger dependent user info field in the trigger frame is related to the variant type of the trigger frame. The trigger dependent user info field can be used to indicate the user information in the corresponding variant trigger frame that is different from other variant trigger frames (i.e., the user information specific to this variant trigger frame). It is noted that the trigger dependent user info field can not exist in some variant trigger frames.

[0073] FIG. 4B is an example diagram of the format of the trigger dependent user info field in the basic trigger frame. As shown in FIG. 4B, the trigger dependent user info field in the basic trigger frame can include one or more of the following fields: MPDU MU spacing factor, TID aggregation limit, preferred AC, and reserved.

[0074] 2) User info list field

[0075] The user info list field is composed of one or more user info fields. In some types of trigger frames (e.g., UHR trigger frame or EHT trigger frame), the user info list field includes one or more special user info fields and / or multiple variant user info fields. Among them, the variant user info field can be, for example, a UHR variant user info field or an EHT variant user info field. The special user info field and the variant user info field are described below, respectively.

[0076] The special user info field can carry the necessary universal signal field (U-SIG) subfield of the requested PPDU. The special user info field can be located after the common info field in the trigger frame. FIG. 5 is an example diagram of the format of the special user info field. As shown in FIG. 5, the special user info field can include one or more of the following fields: association identifier 12 (AID 12), physical layer version identifier, uplink bandwidth extension (UL BW extension), spatial reuse 1, spatial reuse 2, U-SIG disregard and validate, trigger dependent user info, and reserved.

[0077] It should be noted that the AID 12 subfield of each special user info field should be set to a different fixed value. The fixed value can be, for example, 2007.

[0078] The variant user info field can carry the information of the non-AP STA indicated by the AID 12 subfield. Thus, the AID 12 subfield in the variant user info field is different from the content indicated by the AID 12 subfield of the special user info field.

[0079] FIG. 6 is an example diagram of the format of the variant user info field. As shown in FIG. 6, the variant user info field can include one or more of the following fields: association identifier 12 (AID 12), RU allocation, uplink forward error correction coding type (UL FEC coding type), uplink UHR modulation and coding strategy (UL UHR-MCS), spatial stream allocation / random access resource unit information (SS allocation / RA-RU information), uplink target received signal strength indication (UL target RSSI), PS 160, trigger dependent user info, and reserved.

[0080] The resource unit allocation subfield in the variant user info field can be jointly used with the UL BW subfield in the common info field, the UL BW scalable field in the special user info field, and the PS160 subfield in the variant user info field to indicate the size and location of the RUs or MRUs. For example, the mapping of B7-B1 of the RU Allocation subfield along with the settings of B0 of the RU Allocation subfield and the PS160 subfield in the EHT variant User Info field is defined in Table 9-461 in IEEE 802.11 draft D6.0.

[0081] Table 1 is an example of encoding of the PS 160 subfield and the resource unit allocation subfield. When PS 160 subfield = 0 and the RU / MRU size is smaller than or equal to 996 tones, B0 of the resource unit allocation subfield is set to 0 to indicate that the RU / MRU allocation applies to the primary 80MHz channel (Table 1 by P80); B0 of the resource unit allocation subfield is set to 1 to indicate that the RU / MRU allocation applies to the secondary 80MHz (Table 1 by S180) channel of the primary 160MHz (Table 1 by P160). When PS 160 subfield = 1 and the RU / MRU size is smaller than or equal to 996 tones, B0 of the resource unit allocation subfield is set to 0 to indicate that the RU / MRU allocation applies to the lower 80MHz (Table 1 by S280) in the secondary 160MHz; B0 of the resource unit allocation subfield is set to 1 to indicate that the RU / MRU allocation applies to the upper 80MHz (Table 1 by S380) in the secondary 160MHz. (B0 of the RU Allocation subfield is set to 0 to indicate that the RU or MRU allocation applies to the primary 80MHz channel and set to 1 to indicate that the RU allocation applies to the secondary 80MHz channel in the primary 160MHz, if PS160 subfield is equal to 0 and the RU or MRU size is smaller than or equal to 996 tones. B0 of the RU Allocation subfield is set to 0 to indicate that the RU or MRU allocation applies to the lower 80MHz in the secondary 160MHz and is set to 1 to indicate that the RU or MRU allocation applies to upper 80MHz in the secondary 160MHz, if PS160 subfield is equal to 1 and the RU or MRU size is smaller than or equal to 996 tones.)

[0082] Table 1

[0083] 3) Padding field

[0084] The padding field can be present in the trigger frame to extend the frame length of the trigger frame. The frame length extension is to give the STA receiving the trigger frame enough time to prepare a response PPDU for transmission after receiving the trigger frame a short interframe space (SIFS). The length of the padding field can be variable.

[0085] FIG. 7 is a schematic flow chart of a method of wireless communication provided by an embodiment of the present application. The method shown in FIG. 7 can be performed by a non-AP STA and an AP. For example, the AP can be a UHR AP. For another example, the non-AP STA can be a UHR non-AP STA.

[0086] The method shown in FIG. 7 can include step S710.

[0087] At step S710, the non-AP STA can receive a first request sent by the AP. The first request is used for the AP to request the non-AP STA to send a PPDU on a first channel. The PPDU can be an uplink PPDU. For example, the first request can be carried in the trigger frame described above. In the case that the first request is carried in the trigger frame, the PPDU can be a TB PPDU. For example, the PPDU can be a UHR TB PPDU.

[0088] The first channel can be represented by one or more first bandwidths. Alternatively, it can also be said that the first channel includes one or more first bandwidth segments. For example, the first bandwidth can be 80MHz. That is, the first channel can be represented by one or more 80MHz. That is, the first channel can include one or more 80MHz segments. For example, in the case that the bandwidth of the first channel is 80MHz, the first channel can be represented by 1 first bandwidth. For another example, in the case that the bandwidth of the first channel is 160MHz, the first channel can be represented by 2 first bandwidths, i.e., the first channel can include 2 80MHz segments. For another example, in the case that the bandwidth of the first channel is 320MHz, the first channel can be represented by 4 first bandwidths, i.e., the first channel can include 4 80MHz segments.

[0089] It should be noted that the first bandwidth can be a non-punctured bandwidth. The first channel can be a non-punctured channel.

[0090] The PPDU transmitted by the non-AP STA on the first channel on the first bandwidth can be transmitted through the DRU. For example, the data in the PPDU is transmitted through the DRU.

[0091] Optionally, in the case where the bandwidth of the first channel is represented by a plurality of first bandwidths, all the first bandwidths can be transmitted through the DRU. Alternatively, part of the first bandwidths are transmitted through the DRU, and part of the first bandwidths are transmitted through the RRU. For example, for a first channel of 160MHz, the primary 80MHz can be transmitted through the DRU, and the secondary 80MHz can be transmitted through the RRU.

[0092] In some embodiments, the first request can be used to indicate the distribution bandwidth of the DRU. In the case where the first request is carried in the trigger frame, the trigger frame can be used to indicate the distribution bandwidth of the DRU.

[0093] Optionally, in the case where the bandwidth of the first channel is represented by a plurality of first bandwidths, the first request can be used to indicate the distribution bandwidth of the DRU for each of the plurality of first bandwidths. For example, if the bandwidth of the first channel is 160MHz or 320MHz, the first request can indicate the distribution bandwidth of the DRU for each 80MHz segment. Wherein the distribution bandwidth of the DRU for each 80MHz segment can be the same.

[0094] Optionally, if the bandwidth of the first channel can only be represented by one first bandwidth, the first request can be used to indicate the distribution bandwidth of the DRU for the first bandwidth, i.e. the first request is used to indicate the distribution bandwidth of the DRU for the first channel. The first request can not be used to indicate the distribution bandwidth of the DRU for other bandwidths other than the first bandwidth.

[0095] Based on the first request, the non-AP STA can determine the distribution bandwidth of the DRU allocated by the AP to the non-AP STA, so that the non-AP STA can transmit the PPDU on the corresponding distribution bandwidth, thereby realizing the DRU-based communication process.

[0096] In some embodiments, the first request can directly indicate the distribution bandwidth of the DRU. For example, the first request can indicate one or more of the following: the number of sub-channels in the distribution bandwidth, the bandwidth of the sub-channels, the arrangement of the sub-channels, etc.

[0097] In some embodiments, the first request can indicate the mode (e.g. the first mode or the second mode described below) of the distribution bandwidth of the DRU, thereby indicating the distribution bandwidth of the DRU. Wherein different distribution bandwidths can correspond to different modes.

[0098] In possible implementations, the distribution bandwidth of the DRU can satisfy the first mode or the second mode.

[0099] In the first mode, the distribution bandwidth of the DRU is the first bandwidth. For example, in the case where the first bandwidth is 80 MHz, the distribution bandwidth of the DRU is 80 MHz. Alternatively, the first bandwidth is 80 MHz, and the distribution bandwidth mode in which the distribution bandwidth of the DRU is 80 MHz can be referred to as mode 0.

[0100] In the second mode, the distribution bandwidth of the DRU can include one or more second bandwidths. The second bandwidths can be smaller than the first bandwidth. For example, in the case where the first bandwidth is 80 MHz, the second bandwidths can include 20 MHz or 40 MHz. That is, in the case where the first bandwidth is 80 MHz, the distribution bandwidth of the DRU can include one or more 20 MHz bandwidths and / or one or more 40 MHz bandwidths.

[0101] In some embodiments, the first bandwidth is 80 MHz, and in the second mode, the distribution bandwidth of the DRU can include two 20 MHz bandwidths and one 40 MHz bandwidth. The present application does not limit the frequency domain positions of the two 20 MHz bandwidths and the one 40 MHz bandwidth. For example, the frequency of the one 40 MHz bandwidth can be smaller than the frequencies of the two 20 MHz bandwidths. That is, in the order of increasing frequency, the distribution bandwidths are 40 MHz + 20 MHz + 20 MHz, respectively. Alternatively, the frequency of the one 40 MHz bandwidth can be greater than the frequencies of the two 20 MHz bandwidths. That is, in the order of increasing frequency, the distribution bandwidths are 20 MHz + 20 MHz + 40 MHz, respectively.

[0102] Alternatively, the first bandwidth is 80 MHz, and in the order of increasing frequency, the distribution bandwidths are 20 MHz + 20 MHz + 40 MHz, respectively, which can be referred to as mode 1. The first bandwidth is 80 MHz, and in the order of increasing frequency, the distribution bandwidths are 40 MHz + 20 MHz + 20 MHz, respectively, which can be referred to as mode 2.

[0103] The subcarrier plan of the first bandwidth in the second mode can be a first subcarrier plan, and the present application provides a determination manner of the first subcarrier plan.

[0104] In some embodiments, the tone index of the second bandwidth in the first subcarrier plan can be obtained by shifting the tone index in a second subcarrier plan. The subcarrier plan of the second bandwidth is the second subcarrier plan. The following is an example in which the first bandwidth is 80 MHz and the distribution bandwidth satisfies the second mode.

[0105] As described above, in the second mode, the distributed bandwidth of the DRU can be either mode 1 (20MHz+20MHz+40MHz) or mode 2 (40MHz+20MHz+20MHz). The first subcarrier plan can be an 80MHz bandwidth DRU tone plan, and the second subcarrier plan can include a 20MHz and / or 40MHz bandwidth DRU tone plan. In either mode 1 or mode 2, the 80MHz bandwidth DRU tone plan can be shifted from the 20MHz and / or 40MHz bandwidth DRU tone plan. To facilitate understanding, the following shifting schemes are provided.

[0106] Scheme 1, for a 20MHz DRU tone plan, if shifted to the first 20MHz of the 80MHz in order of increasing frequency, the lowest boundary of the 20MHz DRU tone plan can be aligned with the lowest boundary of the 242-tone RRU 1 in the 80MHz. For example, if the lowest boundary tone index of the 20MHz DRU tone plan is -120 and the lowest boundary tone index of the 80MHz DRU tone plan is -500, the shift value is -380. As another example, if the lowest boundary tone index of the 20MHz DRU tone plan is -120 and the lowest boundary tone index of the 80MHz DRU tone plan is -499, the shift value is -379.

[0107] Scheme 2, for a 20MHz DRU tone plan, if shifted to the fourth 20MHz of the 80MHz in order of increasing frequency, the highest boundary of the 20MHz DRU tone plan can be aligned with the highest boundary of the 242-tone RRU 4 in the 80MHz. For example, if the highest boundary tone index of the 20MHz DRU tone plan is 120 and the highest boundary tone index of the 80MHz DRU tone plan is 500, the shift value is +380.

[0108] Scheme 3, for a 20MHz DRU tone plan, if shifted to the second 20MHz in the 80MHz in the order of increasing frequency, the highest boundary of the 20MHz DRU tone plan can be aligned with the highest boundary of the 242-tone RRU 2 in the 80MHz. For example, the highest boundary tone index of the 20MHz DRU tone plan is 120, and the highest boundary tone index of the 242-tone RRU 2 in the 80MHz is -12, then the shift value is -132.

[0109] Scheme 4, for a 20MHz DRU tone plan, if shifted to the third 20MHz in the 80MHz in the order of increasing frequency, the lowest boundary of the 20MHz DRU tone plan can be aligned with the lowest boundary of the 242-tone RRU 3 in the 80MHz. For example, the lowest boundary tone index of the 20MHz DRU tone plan is -120, and the lowest boundary tone index of the 242-tone RRU 3 in the 80MHz is 12, then the shift value is 132.

[0110] Scheme 5, for a 40MHz DRU tone plan, if shifted to the first 40MHz in the 80MHz in the order of increasing frequency, the lowest boundary of the 40MHz DRU tone plan can be aligned with the lowest boundary of the 484-tone RRU 1 in the 80MHz. For example, the lowest boundary tone index of the 40MHz DRU tone plan is -244, and the lowest boundary tone index of the 484-tone RRU 1 in the 80MHz is -500, then the shift value is -256. For another example, the lowest boundary tone index of the 40MHz DRU tone plan is -244, and the lowest boundary tone index of the 484-tone RRU 1 in the 80MHz is -499, then the shift value is -255.

[0111] Scheme 6, for a 40MHz DRU tone plan, if shifted to the second 40MHz in the 80MHz in the order of increasing frequency, the highest boundary of the 40MHz DRU tone plan can be aligned with the highest boundary of the 484-tone RRU 2 in the 80MHz. For example, the highest boundary tone index of the 40MHz DRU tone plan is 244, and the highest boundary tone index of the 484-tone RRU 2 in the 80MHz is 500, then the shift value is +256.

[0112] Optionally, the schemes 1, 3, 6 can constitute the 80MHz PPDU DRU tone plan of mode 1 (20MHz+20MHz+40MHz). The schemes 2, 4, 5 can constitute the 80MHz PPDU DRU tone plan of mode 2 (40MHz+20MHz+20MHz).

[0113] In some embodiments, in case the bandwidth of the first channel is represented by a plurality of first bandwidths, the subcarrier plan of the bandwidth of the first channel in the second mode can be a third subcarrier plan. The subcarrier indices of the first bandwidth of the third subcarrier plan can be obtained by shifting the subcarrier indices in the first subcarrier plan. For example, in case the bandwidth of the first channel is 160 / 320MHz, the bandwidth of the first channel can be represented by 2 / 4 80MHz bandwidths, the 80MHz tone plan for the 160 / 320MHz PPDU using DRU transmission can be obtained by shifting the DRU tone plan of the 80MHz PPDU in mode 1 and mode 2. For the convenience of understanding, the following shifting schemes are provided.

[0114] Scheme 7, in the 160MHz UHR PPDU, in the order of increasing frequency, if the 1st 80MHz segment uses DRU transmission, and the 80MHz segment uses the distributed bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, the DRU tone plan of the 1st 80MHz segment can be constituted by the tone index of the 80MHz tone plan of mode 1 or mode 2 proposed in this application minus 512.

[0115] Scheme 8, when the 160MHz UHR PPDU uses mixed transmission of DRU and RRU, in the order of increasing frequency, if the 2nd 80MHz segment uses DRU transmission, and the 80MHz segment uses the distributed bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, the DRU tone plan of the 2nd 80MHz segment can be constituted by the tone index of the 80MHz tone plan of mode 1 or mode 2 proposed in this application plus 512.

[0116] Scheme 9, when 320MHz UHR PPDU uses DRU and RRU mixed transmission, in the order of increasing frequency, if the 1st 80MHz segment uses DRU transmission, and the 80MHz segment uses distribution bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, then the DRU tone plan of the 1st 80MHz segment can be the tone index of the mode 1 or mode 2 80MHz tone plan proposed in this application minus 1536.

[0117] Scheme 10, when 320MHz UHR PPDU uses DRU and RRU mixed transmission, in the order of increasing frequency, if the 2nd 80MHz segment uses DRU transmission, and the 80MHz segment uses distribution bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, then the DRU tone plan of the 2nd 80MHz segment can be the tone index of the mode 1 or mode 2 80MHz tone plan proposed in this application minus 512.

[0118] Scheme 11, when 320MHz UHR PPDU uses DRU and RRU mixed transmission, in the order of increasing frequency, if the 3rd 80MHz segment uses DRU transmission, and the 80MHz segment uses distribution bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, then the DRU tone plan of the 3rd 80MHz segment can be the tone index of the mode 1 or mode 2 80MHz tone plan proposed in this application plus 512.

[0119] Scheme 12, when 320MHz UHR PPDU uses DRU and RRU mixed transmission, in the order of increasing frequency, if the 4th 80MHz segment uses DRU transmission, and the 80MHz segment uses distribution bandwidth mode of 20MHz+20MHz+40MHz or 40MHz+20MHz+20MHz in the order of increasing frequency, then the DRU tone plan of the 4th 80MHz segment can be the tone index of the mode 1 or mode 2 80MHz tone plan proposed in this application plus 1536.

[0120] The application also provides a method for determining the number of DRUs in a tone plan and DRU index.

[0121] In the 80MHz UHR PPDU, if the distributed bandwidth is 20MHz+20MHz+40MHz in increasing order of frequency, the different sizes of DRUs and the number can be: 36 26-tone DRUs, the DRU index can be 1~37, wherein 26-tone DRU 19 is not defined; 16 52-tone DRUs, the DRU index can be 1~16; 8 106-tone DRUs, the DRU index can be 1~8; 2 242-tone DRUs, the DRU index can be 3~4, wherein 242-tone DRU 1~2 is not defined. In addition, 26-tone DRU 1~9, 52-tone DRU 1~4, 106-tone DRU 1~2 can be in the first 20MHz subchannel; 26-tone DRU 10~18, 52-tone DRU 5~8, 106-tone DRU 3~4 can be in the second 20MHz subchannel; 26-tone DRU 20~37, 52-tone DRU 9~16, 106-tone DRU 5~8, 242-tone DRU 3~4 can be in the higher 40MHz subchannel (or the second 40MHz subchannel).

[0122] In 80MHz PPDUs, if the distributed bandwidth is 40MHz + 20MHz + 20MHz in increasing frequency order, the different sizes of DRUs and the number can be: 36 26-tone DRUs, DRU index can be 1~37, wherein 26-tone DRU 19 is undefined; 16 52-tone DRUs, DRU index can be 1~16; 8 106-tone DRUs, DRU index can be 1~8; 2 242-tone DRUs, DRU index can be 1~2, wherein 242-tone DRU 3~4 is undefined. In addition, 26-tone DRU 1~18, 52-tone DRU 1~8, 106-tone DRU 1~4, 242-tone DRU 1~2 can be in the lower 40MHz subchannel (or the first 40MHz subchannel); 26-tone DRU 20~28, 52-tone DRU 9~12, 106-tone DRU 5~6 can be in the third 20MHz subchannel (the first 20MHz in 40MHz + 20MHz + 20MHz); 26-tone DRU 29~37, 52-tone DRU 13~16, 106-tone DRU 7~8 can be in the fourth 20MHz subchannel (the second 20MHz in 40MHz + 20MHz + 20MHz).

[0123] It should be noted that if the 20MHz operating non-AP STA does not establish subchannel selective transmission (SST) operation with the AP on a non-primary 20MHz channel, the AP will not allocate DRUs or DMRS outside the primary 20MHz to the 20MHz operating non-AP STA in the 40MHz, 80MHz, 160MHz or 320MHz TB PPDU.

[0124] In some embodiments, the first request can be used to indicate the first information. The first information can be used to indicate whether the PPDU is transmitted by the DRU. That is, the first information can be used to indicate whether the PPDU transmitted by the non-AP STA is transmitted by the DRU or the RRU. Or, it can also be said that the first information can be used to indicate the RU type. Wherein the RU type can include DRU or RRU.

[0125] Optionally, in case the first information indicates that the PPDU is transmitted through a DRU, the first request can be used to indicate the distributed bandwidth of the DRU. In case the first information indicates that the PPDU is not transmitted through a DRU, the first request can not be used to indicate the distributed bandwidth of the DRU.

[0126] In some embodiments, for the non-AP STA receiving the first request, a corresponding behavior can be performed according to the indication of the first information.

[0127] For example, if the first information indicates that the PPDU is transmitted through a DRU, the non-AP STA can parse one or more of the following fields: a field indicating the distributed bandwidth of the DRU, a field indicating the index of the DRU, a field indicating the size of the DRU, a field indicating the location of the DRU; if the first information indicates that the PPDU is transmitted through a RRU, the non-AP STA can not parse or ignore one or more of the following fields: a field indicating the distributed bandwidth of the DRU, a field indicating the index of the DRU, a field indicating the size of the DRU, a field indicating the location of the DRU. It can be understood that the non-AP STA does not parse or ignore certain fields, which can reduce the processing complexity of the non-AP STA.

[0128] For another example, if the first information indicates that the PPDU is transmitted through a DRU, the non-AP STA can consider that the RU allocation subfield in the variant user info field together with the UL BW subfield in the common info field, the UL BW extension subfield in the special user info field, and the PS160 subfield in the UHR variant user info field indicate the size, location and index of the DRU or DMRU; if the first information indicates that the PPDU is transmitted through a RRU, the non-AP STA can consider that the RU allocation subfield in the UHR variant user info field together with the UL BW subfield in the common info field, the UL BW extension subfield in the special user info field, and the PS160 subfield in the UHR variant user info field indicate the size, location and index of the RRU or RMRU.

[0129] In some embodiments, the first information can be carried in an RU type field.

[0130] Optionally, the RU type field can be represented by 1 bit. For example, the value of the 1 bit is 0 can represent a RRU, and the value of 1 can represent a DRU. For another example, the value of the 1 bit is 1 can represent a RRU, and the value of 0 can represent a DRU.

[0131] The RU type field can be implemented by reusing the reserved field in the related art. For example, B25 of the variant user info field shown in FIG. 6 and / or B5 in the trigger dependent user info subfield of the basic trigger frame shown in FIG. 4B can be used to carry the RU type field.

[0132] In some embodiments, the distribution bandwidth can be indicated by a field indicating non-AP STA specific information. The field indicating non-AP STA specific information may, for example, include the variant user info field. Specifically, how to indicate the distribution bandwidth by the variant user info field is described above and will not be repeated here.

[0133] By indicating the distribution bandwidth by the field indicating non-AP STA specific information, the corresponding distribution bandwidth can be indicated for different non-AP STAs, thereby improving the flexibility of indication.

[0134] Optionally, the distribution bandwidth can be indicated by the variant user info field. For example, for a non-AP STA transmitting a RRU PPDU, the corresponding variant user info field can not indicate the distribution bandwidth. For another example, for a non-AP STA transmitting a DRU PPDU, the corresponding variant user info field can indicate the distribution bandwidth of the corresponding DRU.

[0135] In some embodiments, the distribution bandwidth can be indicated by one or more fields. For example, the distribution bandwidth is indicated by multiple fields jointly. For example, the multiple fields can include a first field and a second field, and part or all of the bits in the first field and part or all of the bits in the second field can be jointly used to indicate the distribution bandwidth. Illustratively, the multiple fields can include the PS160 field in the UHR variant user info field and the RU allocation field. That is, the PS160 field in the UHR variant user info field and the RU allocation field can be jointly used to indicate the distribution bandwidth.

[0136] Optionally, in the case where the first channel is 80MHz bandwidth, when the trigger frame indicates that a DRU is allocated to a non-AP STA identified by the AID 12 subfield, the PS160 field (1 bit) in the variant user info field and B0 (1 bit) of the RU allocation field can be used to indicate the mode of the distribution bandwidth. The mode of the distribution bandwidth can include one or more of the following: mode 0, mode 1 or mode 2. Three of the four values composed of the above two bits can be used to indicate the three modes of the distribution bandwidth.

[0137] For example, when the PS160 subfield is 0 and the B0 of the RU allocation subfield is 0, it can indicate that the distribution bandwidth of the 80MHz PPDU is 80MHz; when the PS160 subfield is 0 and the B0 of the RU allocation subfield is 1, it can indicate that the distribution bandwidth of the 80MHz PPDU is 20MHz+20MHz+40MHz in the order of increasing frequency; when the PS160 subfield is 1 and the B0 of the RU allocation subfield is 0, it can indicate that the distribution bandwidth of the 80MHz PPDU is 40MHz+20MHz+20MHz. For another example, when the PS160 subfield is 0 and the B0 of the RU allocation subfield is 0, it can indicate that the distribution bandwidth of the 80MHz PPDU is 80MHz; when the PS160 subfield is 0 and the B0 of the RU allocation subfield is 1, it can indicate that the distribution bandwidth of the 80MHz PPDU is 40MHz+20MHz+20MHz in the order of increasing frequency; when the PS160 subfield is 1 and the B0 of the RU allocation subfield is 0, it can indicate that the distribution bandwidth of the 80MHz PPDU is 20MHz+20MHz+40MHz.

[0138] As described above, in the related art, the PS160 subfield and the B0 of the RU allocation subfield are used to indicate the channel condition of RU / MRU allocation when the bandwidth of the first channel is 160MHz or above. Therefore, in the related art, when the bandwidth of the first channel is 80MHz, the PS160 subfield and the B0 of the RU allocation subfield do not have corresponding indication information defined. The present application proposes that the distribution bandwidth can be indicated by the PS160 subfield and the B0 of the RU allocation subfield when the bandwidth of the first channel is 80MHz, which can make full use of these fields, thereby realizing the indication of the distribution bandwidth with less modification to the related art.

[0139] Optionally, the size and index of the DRU or DMRU can be indicated by the B1-B7 of the RU allocation subfield. For example, the RU allocation subfield in the UHR variant user information, together with the UL BW subfield in the common information field, the UL BW extension subfield in the special user information field, and the PS160 subfield in the UHR variant user information field, indicates the size, position and index of the DRU or DMRU. Exemplarily, the indication manner of the size, position and index of the DRU or DMRU can be the same as that defined in Table 9-461 of IEEE 802.11be D6.0.

[0140] The indication of the distribution bandwidth will be described in detail below by way of embodiment 1.

[0141] Embodiment 1

[0142] In embodiment 1, the RU type field is carried by the reserved bits in the UHR variant user info field in the related art. The position of the RU type field can be shown in FIG. 8. The value of the RU type field being 0 can represent an RRU, and the value of the RU type field being 1 can represent a DRU.

[0143] In embodiment 1, the mode of the distributed bandwidth of the 80MHz PPDU is indicated by the joint of the PS160 subfield and the B0 of the RU allocation subfield. The encoding of the mode of the distributed bandwidth can be shown in Table 2.

[0144] Table 2

[0145] It should be noted that part of the content in Table 2 can be implemented separately. The correspondence between the value and the description of each field in Table 2 can be adjusted. For example, PS160 being 0 and the B0 of the RU allocation subfield being 1 can represent a reservation.

[0146] The AP can request one 80MHz UHR TB PPDU using DRU from 6 non-AP STAs. The AID12 of the non-AP STAs 1-6 is equal to 1-6 respectively. The distributed bandwidth is 20MHz+20MHz+40MHz in the order of increasing frequency. The DRU of the non-AP STAs 1-2 is 106-tone DRU 1-2, and the distributed bandwidth is the first 20MHz in the order of increasing frequency. The DRU of the non-AP STAs 3-4 is 106-tone DRU 3-4, and the distributed bandwidth is the second 20MHz in the order of increasing frequency. The DRU of the non-AP STAs 5-6 is 242-tone DRU 3-4, and the distributed bandwidth is the higher 40MHz.

[0147] In the trigger frame, the AID12 of the UHR variant user info field pointing to the 6 non-AP STAs is equal to 1-6 respectively. The indication of each field can be shown in Table 3.

[0148] Table 3

[0149] In some embodiments, the distributed bandwidth and the first information can be jointly indicated by one or more fields. That is, the one or more fields can be used to indicate both the distributed bandwidth and the first information. For example, part of the values corresponding to the one or more fields can be used to indicate the distributed bandwidth, and part of the values can be used to indicate the first information. For another example, the values corresponding to the one or more fields can indicate the combination of the distributed bandwidth and the first information.

[0150] It can be understood that the joint indication of the distribution bandwidth and the first information through one or more fields can make the number of bits occupied by the field carrying the two information as few as possible, thereby reducing the number of bits occupied by the field carrying the distribution bandwidth and the first information.

[0151] Optionally, the distribution bandwidth and the first information can be jointly indicated through reserved bits in multiple fields. For example, the distribution bandwidth and the first information can be jointly indicated through the following fields: a subfield in the UHR variant user Info field, a subfield in the trigger dependent user Info subfield in the basic trigger frame.

[0152] For example, 1 reserved bit (e.g., B25) in the UHR variant user Info field in the trigger frame and 1 reserved bit (e.g., B5) in the trigger dependent user Info field in the basic trigger frame in the related art can be used to jointly indicate the mode of the distribution bandwidth of the 80MHz PPDU. In the present application, the two reserved bits can be defined as the RU type subfield and the 80MHz segment distributed mode subfield, respectively.

[0153] The RU type subfield is 0 and the 80MHz segment distributed mode subfield is 0, indicating RRU; the RU type subfield is 0 and the 80MHz segment distributed mode subfield is 1, indicating DRU, and the distribution bandwidth is the PPDU bandwidth; the RU type subfield is 1 and the 80MHz segment distributed mode subfield is 0, indicating DRU, and the distribution bandwidth of 80MHz is 20MHz+20MHz+40MHz in the order of increasing frequency; and the RU type subfield is 1 and the 80MHz segment distributed mode subfield is 1, indicating DRU, and the distribution bandwidth of 80MHz is 40MHz+20MHz+20MHz in the order of increasing frequency.

[0154] Optionally, the size and index of the DRU or DMRU can be indicated by B1-B7 of the RU allocation subfield. For example, the RU allocation subfield in the UHR variant user Info field, together with the UL BW subfield in the common information field, the UL BW extension subfield in the special user information field, and the PS160 subfield in the UHR variant user Info field, indicates the size, location, and index of the DRU or DMRU. Exemplarily, the indication manner of the size, location, and index of the DRU or DMRU can be the same as that defined in Table 9-461 of IEEE 802.11be D6.0.

[0155] For the convenience of understanding, the joint indication of the first information and the distribution bandwidth is explained in detail through Embodiment 2-1 and Embodiment 2-2.

[0156] Embodiment 2-1

[0157] In Embodiment 2-1, B25 of the UHR variant user info field is used to represent the RU type subfield (as shown in FIG. 8), and B5 of the trigger dependent user info subfield in the UHR basic trigger frame is used to represent the 80MHz segmentation distribution mode subfield (as shown in FIG. 9).

[0158] The RU type subfield and the 80MHz segmentation distribution mode subfield can be used to indicate the distribution bandwidth of the DRU for each 80MHz in the 80MHz / 160MHz / 320MHz, etc. bandwidth.

[0159] The meanings of the RU type subfield and the 80MHz segmentation distribution mode subfield can be as shown in Table 4.

[0160] Table 4

[0161] It should be noted that part of the content in Table 4 can be implemented alone. The correspondence between the values and the descriptions of the various fields in Table 4 can be adjusted. For example, the RU type field is 0, and the 80MHz segmentation distribution mode field is 1, which can represent the RRU.

[0162] Exemplarily, the AP requests a 160MHz UHR TB PPDU to 7 non-AP STAs. Among them, the primary 80MHz (lower) uses DRU transmission, and the secondary 80MHz (higher) in the primary 160MHz uses RRU transmission. The AIDs of the non-AP STAs 1-7 are 1-7 respectively.

[0163] For the lower 80MHz (i.e. the primary 80MHz), in the order of increasing frequency, the distribution bandwidth is 40MHz+20MHz+20MHz. Among them, the DRU of the non-AP STAs 1-2 is 242-tone DRU 1-2, and the distribution bandwidth is the first 40MHz of the lower 80MHz; the DRU of the non-AP STAs 3-4 is 106-tone DRU 5-6, and the distribution bandwidth is the third 20MHz (the first 20MHz in the distribution bandwidth) of the lower 80MHz; the DRU of the non-AP STAs 5-6 is 106-tone DRU 7-8, and the distribution bandwidth is the fourth 20MHz (the second 20MHz in the distribution bandwidth) of the lower 80MHz.

[0164] For higher 80MHz, the RRU of non-AP STA 7 is 996-tone RRU2.

[0165] In the trigger frame, the AID12 of the UHR variant user info field pointing to 7 non-AP STAs is equal to 1-7 respectively. The indication of RU allocation field and the like field can be shown as table 5.

[0166] Table 5

[0167] Embodiment 2-2

[0168] Embodiment 2-2 indicates the DRU distribution bandwidth in the case of the first channel bandwidth being 80MHz.

[0169] In embodiment 2-2, B25 in UHR variant user info field is used to represent RU type subfield (as shown in figure 8), and B5 in trigger dependent user info subfield in UHR basic trigger frame is used to represent 80MHz segmented distribution mode subfield (as shown in figure 9).

[0170] The meaning of RU type subfield and 80MHz segmented distribution mode subfield can be shown as table 6.

[0171] Table 6

[0172] It should be noted that part of the content in table 6 can be implemented separately. The correspondence between the value and description of each field in table 6 can be adjusted. For example, RU type field being 0 and 80MHz segmented distribution mode field being 1 can represent RRU.

[0173] Exemplarily, the AP requests an 80MHz UHR TB PPDU using DRU to 6 non-AP STAs. Among them, the AID12 of non-AP STAs 1-6 is equal to 1-6 respectively. The distribution bandwidth is in the order of increasing frequency: 20MHz+20MHz+40MHz. Among them, the DRU of non-AP STAs 1-2 is 106-tone DRU 1-2, and the distribution bandwidth is the first 20MHz; the DRU of non-AP STAs 3-4 is 106-tone DRU 3-4, and the distribution bandwidth is the second 20MHz; the DRU of non-AP STAs 5-6 is 242-tone DRU 3-4, and the distribution bandwidth is the higher 40MHz.

[0174] In the trigger frame, the AID12 of the UHR variant user info field pointing to 6 non-AP STAs is equal to 1-6 respectively. The indication of RU allocation field and the like field can be shown as table 7.

[0175] Table 7

[0176] In some embodiments, the distribution bandwidth can be indicated by a field indicating information common to one or more non-AP STAs. For example, in related art, a reserved bit in the field indicating information common to one or more non-AP STAs can be used to indicate the distribution bandwidth, thereby facilitating the implementation of the present application in combination with related art. In addition, since there are more reserved bits in the field indicating information common to one or more non-AP STAs (compared to the field indicating private information of a non-AP STA), the flexibility of using the reserved bits to indicate the distribution bandwidth is higher.

[0177] In some embodiments, the distribution bandwidth can be indicated by a common information field and / or a special user information field. For example, the distribution bandwidth can be indicated by one or more of the following bits: B22, B26, B53, B56-B62, B63 in the common information field. For another example, the distribution bandwidth can be indicated by one or more of the following bits: B25-B36, B37-B39 in the special user information field.

[0178] Exemplarily, the distribution bandwidth can be indicated by an 80MHz segment distribution mode field. The 80MHz segment distribution mode field can occupy 2 bits. The 80MHz segment distribution mode field can be two bits in B22, B26, B53, B56-B62, B63 in the common information field. Alternatively, the 80MHz segment distribution mode field can be two bits in B25-B36, B37-B39 in the special user information field.

[0179] For example, the value of 00 of the 80MHz segmentation distribution mode subfield can indicate that the distribution bandwidth is the PPDU bandwidth; the value of 01 of the 80MHz segmentation distribution mode subfield can indicate DRU and the distribution bandwidth of 80MHz is 20MHz+20MHz+40MHz in the order of increasing frequency; the value of 10 of the 80MHz segmentation distribution mode subfield can indicate DRU and the distribution bandwidth of 80MHz is 40MHz+20MHz+20MHz in the order of increasing frequency; the value of 11 of the 80MHz segmentation distribution mode subfield can indicate reserved. For another example, the value of 01 of the 80MHz segmentation distribution mode subfield can indicate that the distribution bandwidth is the PPDU bandwidth; the value of 00 of the 80MHz segmentation distribution mode subfield can indicate DRU and the distribution bandwidth of 80MHz is 20MHz+20MHz+40MHz in the order of increasing frequency; the value of 11 of the 80MHz segmentation distribution mode subfield can indicate DRU and the distribution bandwidth of 80MHz is 40MHz+20MHz+20MHz in the order of increasing frequency; the value of 10 of the 80MHz segmentation distribution mode subfield can indicate reserved.

[0180] FIG. 10 is an example of a format of a common information field according to an embodiment of the present application. In FIG. 10, B56-B57 represent an 80MHz segmentation distribution mode subfield.

[0181] In the case that the distribution bandwidth is indicated by the field indicating the information common to one or more non-AP STAs, the first information can be indicated by the field indicating the private information of the non-AP STA. For example, the first information can be carried in an RU type field. The RU type field can occupy 1 bit. The 1 bit can be the reserved bit in the UHR variant user information field in the related art. The value of 0 of the RU type field can indicate RRU, and the value of 1 can indicate DRU. Alternatively, the value of 1 of the RU type field can indicate RRU, and the value of 0 can indicate DRU.

[0182] Optionally, the non-AP STA can only parse the field indicating the distribution bandwidth in the common information field and / or the special user information field when the RU allocated to the non-AP STA is DRU; otherwise, the non-AP STA can not parse the field indicating the distribution bandwidth.

[0183] Embodiment 3

[0184] In Embodiment 3, B56-B57 of the common information field represent an 80MHz segmentation distribution mode subfield (as shown in FIG. 10).

[0185] The detailed meaning of the 80MHz segmentation distribution mode subfield can be as shown in Table 8.

[0186] Table 8

[0187] It should be noted that part of the content in Table 8 can be implemented separately. The correspondence between the value and the description of the 8th field in Table 8 can be adjusted. For example, the 80MHz segmentation distribution mode 10 can be reserved.

[0188] Exemplarily, the AP requests 80MHz UHR TB PPDU to 2 non-AP STAs. The AID 12 of the non-AP STAs 1-2 is respectively equal to 1-2. The non-AP STA 1 transmits the PPDU using DRU, and the non-AP STA 2 transmits the PPDU using RRU. The distribution bandwidth of the DRU is 20MHz+20MHz+40MHz in the ascending order of frequency. In the trigger frame, the value of the 80MHz segmentation distribution mode subfield in the common information field is 01. The AID 12 of the UHR variant user information field pointing to the 2 non-AP STAs is respectively equal to 1-2. The RU type field of the UHR variant user information field AID 12 equal to 1 indicates DRU. In the trigger frame, the RU type field of the UHR variant user information field AID 12 equal to 2 indicates RRU.

[0189] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the method embodiments.

[0190] FIG. 11 is a schematic structural diagram of a non-AP STA 1100 according to an embodiment of the present application. The non-AP STA 1100 comprises a receiving unit 1110.

[0191] The receiving unit 1110 is configured to receive a first request sent by an AP. The first request is used to request the non-AP STA to transmit a PPDU on a first channel, the bandwidth of the first channel is represented by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by DRU, and the first request is further used to indicate the distribution bandwidth of the DRU.

[0192] In the embodiments of the present application, the non-AP STA 1100 described above can be used to perform part or all of the method steps performed by the non-AP STA in the method embodiments described above. The method flow has been described in detail in the foregoing embodiments, and the modules in the present embodiment have the same function or perform the same steps, which will not be described here. However, as a person skilled in the art should know that the corresponding textual description of the foregoing embodiments can be introduced into the present embodiment, which corresponds to the modules in the non-AP STA 1100.

[0193] In an optional embodiment, the receiving unit 1110 can be a transceiver 1330. The non-AP STA 1100 can further include a processor 1310 and a memory 1320, as shown in FIG. 13.

[0194] FIG. 12 is a schematic structural diagram of an AP 1200 according to an embodiment of the present application. The AP 1200 can include a sending unit 1210.

[0195] The sending unit 1210 is configured to send a first request to a non-AP STA; wherein the first request is used to request the non-AP STA to send a PPDU on a first channel, a bandwidth of the first channel is represented by one or more first bandwidths, the PPDU is transmitted on the first bandwidth by a DRU, and the first request is further used to indicate a distribution bandwidth of the DRU.

[0196] In the embodiments of the present application, the AP 1200 described above can be used to perform part or all of the method steps performed by the AP in the above-mentioned method embodiments. The modules in the present embodiment have the same functions or perform the same steps as those described in the foregoing embodiments, and will not be described here. However, as a person skilled in the art should know, the corresponding textual description of the foregoing embodiments can be introduced into the present embodiment, and the modules in the AP 1200 correspond thereto.

[0197] In an optional embodiment, the sending unit 1210 can be a transceiver 1330. The AP 1200 can further include a processor 1310 and a memory 1320, as shown in FIG. 13.

[0198] FIG. 13 is a schematic structural diagram of an apparatus for communication according to an embodiment of the present application. The dashed line in FIG. 13 indicates that the unit or module is optional. The apparatus 1300 can be used to implement the methods described in the above-mentioned method embodiments. The apparatus 1300 can be a chip or a communication device.

[0199] The apparatus 1300 can include one or more processors 1310. The processor 1310 can support the apparatus 1300 to implement the methods described in the foregoing method embodiments. The processor 1310 can be a general processor or a special-purpose processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general processor can be a microprocessor or the processor can also be any conventional processor.

[0200] The apparatus 1300 can also include one or more memories 1320. The memory 1320 stores programs, which can be executed by the processor 1310, so that the processor 1310 performs the methods described in the foregoing method embodiments. The memory 1320 can be independent of the processor 1310 or integrated in the processor 1310.

[0201] The apparatus 1300 can also include a transceiver 1330. The processor 1310 can communicate with other devices or chips through the transceiver 1330. For example, the processor 1310 can perform data transceiving with other devices or chips through the transceiver 1330.

[0202] The embodiments of the present application also provide a computer readable storage medium for storing programs. The computer readable storage medium can be applied to the communication device provided by the embodiments of the present application, and the programs make the computer execute the methods performed by the communication device in the embodiments of the present application.

[0203] The embodiments of the present application also provide a computer program product. The computer program product includes programs. The computer program product can be applied to the communication device provided by the embodiments of the present application, and the programs make the computer execute the methods performed by the communication device in the embodiments of the present application.

[0204] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided by the embodiments of the present application, and the computer program makes the computer execute the methods performed by the communication device in the embodiments of the present application.

[0205] It should be understood that the terms "system" and "network" can be used interchangeably in this application. In addition, the terms used in this application are only used to explain the specific embodiments of the application, and are not intended to limit the application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the application and the drawings are used to distinguish different objects, and are not used to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0206] In embodiments of the present application, a "field" can also be referred to as a "domain", a "subfield" or a "subdomain". A field can occupy one or more bytes (octets), or a field can occupy one or more bits.

[0207] The field names defined in embodiments of the present application are only examples, and the fields can have other names.

[0208] In embodiments of the present application, "indication" can be direct indication, indirect indication, or can indicate an associated relationship. For example, A indicates B, which can mean that B can be obtained directly through A; or it can mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or it can mean that A and B have an associated relationship.

[0209] In embodiments of the present application, "B corresponding to A" means that B is associated with A and can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0210] In embodiments of the present application, the term "corresponding" can mean a direct or indirect corresponding relationship between the two, or can mean an associated relationship between the two, or can mean an indication and being indicated, configuration and being configured, etc.

[0211] In embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other ways that can be used to indicate related information in devices (for example, including AP and STA), and the specific implementation of the present application is not limited. For example, predefinition can mean definition in a protocol.

[0212] In embodiments of the present application, the term "and / or" is only a description of the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally means that the associated objects before and after are in an "or" relationship.

[0213] In the embodiments of the present application, the "comprising" can mean directly comprising or indirectly comprising. Alternatively, the "comprising" mentioned in the embodiments of the present application can be replaced by "indicating" or "for determining". For example, A comprising B can be replaced by A indicating B, or A for determining B.

[0214] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0215] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, it can include WiFi protocol and related protocols applied to future WiFi communication systems, which are not limited in the present application.

[0216] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the above-described device embodiments are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0217] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiments of the present application.

[0218] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0219] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented 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 the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0220] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that, The method includes: The non-AP STA receives the first request sent by the access point AP; Wherein, the first request is used to request a non-AP STA to send a Physical Layer Protocol Data Unit (PPDU) on a first channel, the bandwidth of the first channel being represented by one or more first bandwidths, the PPDU being transmitted on the first bandwidth via a Distributed Resource Unit (DRU), and the first request is also used to indicate the distributed bandwidth of the DRU.

2. The method according to claim 1, characterized in that, The distributed bandwidth satisfies: In the first mode, the distributed bandwidth is the first bandwidth; or, In the second mode, the distributed bandwidth includes one or more second bandwidths, which are less than the first bandwidth.

3. The method according to claim 2, characterized in that, The first bandwidth is 80MHz. In the second mode, the distributed bandwidth includes two 20MHz bandwidths and one 40MHz bandwidth; wherein the frequency of the one 40MHz bandwidth is less than the frequency of the two 20MHz bandwidths, or the frequency of the one 40MHz bandwidth is greater than the frequency of the two 20MHz bandwidths.

4. The method according to claim 2 or 3, characterized in that, The subcarrier planning of the first bandwidth in the second mode is the first subcarrier planning, and the subcarrier planning of the second bandwidth is the second subcarrier planning. The subcarrier index of the second bandwidth in the first subcarrier planning is obtained by shifting the subcarrier index in the second subcarrier planning.

5. The method according to claim 4, characterized in that, When the bandwidth of the first channel is represented by multiple first bandwidths, the subcarrier planning of the bandwidth of the first channel in the second mode is a third subcarrier planning, and the subcarrier index of the first bandwidth in the third subcarrier planning is obtained by shifting the subcarrier index in the first subcarrier planning.

6. The method according to any one of claims 1-5, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU. If the first information indicates that the PPDU is transmitted via DRU, the first request is also used to indicate the distributed bandwidth of the DRU.

7. The method according to any one of claims 1-6, characterized in that, The distributed bandwidth is indicated by a combination of multiple fields.

8. The method according to claim 7, characterized in that, The multiple fields include: The PS160 field in the UHR variant user information fields; and, Resource unit allocation field.

9. The method according to any one of claims 1-6, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU, and the distributed bandwidth and the first information are jointly indicated by one or more fields.

10. The method according to claim 9, characterized in that, The one or more fields include: subfields in the UHR variant user information field and subfields in the trigger dependency user information field in the basic trigger frame.

11. The method according to any one of claims 1-6, characterized in that, The distributed bandwidth is indicated by a public information field and / or a special user information field.

12. The method according to any one of claims 1-11, characterized in that, When the bandwidth of the first channel is represented by a plurality of first bandwidths, the first request is used to indicate the distributed bandwidth of the DRU for each of the plurality of first bandwidths.

13. A wireless communication method, characterized in that, The method includes: The access point (AP) sends a first request to the non-AP STA (non-access point site); Wherein, the first request is used to request a non-AP STA to send a Physical Layer Protocol Data Unit (PPDU) on a first channel, the bandwidth of the first channel being represented by one or more first bandwidths, the PPDU being transmitted on the first bandwidth via a Distributed Resource Unit (DRU), and the first request is also used to indicate the distributed bandwidth of the DRU.

14. The method according to claim 13, characterized in that, The distributed bandwidth satisfies: In the first mode, the distributed bandwidth is the first bandwidth; or, In the second mode, the distributed bandwidth includes one or more second bandwidths, which are less than the first bandwidth.

15. The method according to claim 14, characterized in that, The first bandwidth is 80MHz. In the second mode, the distributed bandwidth includes two 20MHz bandwidths and one 40MHz bandwidth; wherein the frequency of the one 40MHz bandwidth is less than the frequency of the two 20MHz bandwidths, or the frequency of the one 40MHz bandwidth is greater than the frequency of the two 20MHz bandwidths.

16. The method according to claim 14 or 15, characterized in that, The subcarrier planning of the first bandwidth in the second mode is the first subcarrier planning, and the subcarrier planning of the second bandwidth is the second subcarrier planning. The subcarrier index of the second bandwidth in the first subcarrier planning is obtained by shifting the subcarrier index in the second subcarrier planning.

17. The method according to claim 16, characterized in that, When the bandwidth of the first channel is represented by multiple first bandwidths, the subcarrier planning of the bandwidth of the first channel in the second mode is a third subcarrier planning, and the subcarrier index of the first bandwidth in the third subcarrier planning is obtained by shifting the subcarrier index in the first subcarrier planning.

18. The method according to any one of claims 13-17, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU. If the first information indicates that the PPDU is transmitted via DRU, the first request is also used to indicate the distributed bandwidth of the DRU.

19. The method according to any one of claims 13-18, characterized in that, The distributed bandwidth is indicated by a combination of multiple fields.

20. The method according to claim 19, characterized in that, The multiple fields include: The PS160 field in the UHR variant user information fields; and, Resource unit allocation field.

21. The method according to any one of claims 13-18, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU, and the distributed bandwidth and the first information are jointly indicated by one or more fields.

22. The method according to claim 21, characterized in that, The one or more fields include: subfields in the UHR variant user information field and subfields in the trigger dependency user information field in the basic trigger frame.

23. The method according to any one of claims 13-18, characterized in that, The distributed bandwidth is indicated by a public information field and / or a special user information field.

24. The method according to any one of claims 13-23, characterized in that, When the bandwidth of the first channel is represented by a plurality of first bandwidths, the first request is used to indicate the distributed bandwidth of the DRU for each of the plurality of first bandwidths.

25. A non-AP STA (non-access point site), characterized in that, The non-AP STA includes: The receiving unit is used to receive the first request sent by the access point (AP). Wherein, the first request is used to request a non-AP STA to send a Physical Layer Protocol Data Unit (PPDU) on a first channel, the bandwidth of the first channel being represented by one or more first bandwidths, the PPDU being transmitted on the first bandwidth via a Distributed Resource Unit (DRU), and the first request is also used to indicate the distributed bandwidth of the DRU.

26. The non-AP STA according to claim 25, characterized in that, The distributed bandwidth satisfies: In the first mode, the distributed bandwidth is the first bandwidth; or, In the second mode, the distributed bandwidth includes one or more second bandwidths, which are less than the first bandwidth.

27. The non-AP STA according to claim 26, characterized in that, The first bandwidth is 80MHz. In the second mode, the distributed bandwidth includes two 20MHz bandwidths and one 40MHz bandwidth; wherein the frequency of the one 40MHz bandwidth is less than the frequency of the two 20MHz bandwidths, or the frequency of the one 40MHz bandwidth is greater than the frequency of the two 20MHz bandwidths.

28. The non-AP STA according to claim 26 or 27, characterized in that, The subcarrier planning of the first bandwidth in the second mode is the first subcarrier planning, and the subcarrier planning of the second bandwidth is the second subcarrier planning. The subcarrier index of the second bandwidth in the first subcarrier planning is obtained by shifting the subcarrier index in the second subcarrier planning.

29. The non-AP STA according to claim 28, characterized in that, When the bandwidth of the first channel is represented by multiple first bandwidths, the subcarrier planning of the bandwidth of the first channel in the second mode is a third subcarrier planning, and the subcarrier index of the first bandwidth in the third subcarrier planning is obtained by shifting the subcarrier index in the first subcarrier planning.

30. The non-AP STA according to any one of claims 25-29, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU. If the first information indicates that the PPDU is transmitted via DRU, the first request is also used to indicate the distributed bandwidth of the DRU.

31. The non-AP STA according to any one of claims 25-30, characterized in that, The distributed bandwidth is indicated by a combination of multiple fields.

32. The non-AP STA according to claim 31, characterized in that, The multiple fields include: The PS160 field in the UHR variant user information fields; and, Resource unit allocation field.

33. The non-AP STA according to any one of claims 25-30, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU, and the distributed bandwidth and the first information are jointly indicated by one or more fields.

34. The non-AP STA according to claim 33, characterized in that, The one or more fields include: subfields in the UHR variant user information field and subfields in the trigger dependency user information field in the basic trigger frame.

35. The non-AP STA according to any one of claims 25-30, characterized in that, The distributed bandwidth is indicated by a public information field and / or a special user information field.

36. The non-AP STA according to any one of claims 25-35, characterized in that, When the bandwidth of the first channel is represented by a plurality of first bandwidths, the first request is used to indicate the distributed bandwidth of the DRU for each of the plurality of first bandwidths.

37. An access point (AP), characterized in that, The AP includes: The sending unit is used to send a first request to a non-AP STA; Wherein, the first request is used to request a non-AP STA to send a Physical Layer Protocol Data Unit (PPDU) on a first channel, the bandwidth of the first channel being represented by one or more first bandwidths, the PPDU being transmitted on the first bandwidth via a Distributed Resource Unit (DRU), and the first request is also used to indicate the distributed bandwidth of the DRU.

38. The AP according to claim 37, characterized in that, The distributed bandwidth satisfies: In the first mode, the distributed bandwidth is the first bandwidth; or, In the second mode, the distributed bandwidth includes one or more second bandwidths, which are less than the first bandwidth.

39. The AP according to claim 38, characterized in that, The first bandwidth is 80MHz. In the second mode, the distributed bandwidth includes two 20MHz bandwidths and one 40MHz bandwidth; wherein the frequency of the one 40MHz bandwidth is less than the frequency of the two 20MHz bandwidths, or the frequency of the one 40MHz bandwidth is greater than the frequency of the two 20MHz bandwidths.

40. The AP according to claim 38 or 39, characterized in that, The subcarrier planning of the first bandwidth in the second mode is the first subcarrier planning, and the subcarrier planning of the second bandwidth is the second subcarrier planning. The subcarrier index of the second bandwidth in the first subcarrier planning is obtained by shifting the subcarrier index in the second subcarrier planning.

41. The AP according to claim 40, characterized in that, When the bandwidth of the first channel is represented by multiple first bandwidths, the subcarrier planning of the bandwidth of the first channel in the second mode is a third subcarrier planning, and the subcarrier index of the first bandwidth in the third subcarrier planning is obtained by shifting the subcarrier index in the first subcarrier planning.

42. The AP according to any one of claims 37-41, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU. If the first information indicates that the PPDU is transmitted via DRU, the first request is also used to indicate the distributed bandwidth of the DRU.

43. The AP according to any one of claims 37-42, characterized in that, The distributed bandwidth is indicated by a combination of multiple fields.

44. The AP according to claim 43, characterized in that, The multiple fields include: The PS160 field in the UHR variant user information fields; and, Resource unit allocation field.

45. The AP according to any one of claims 37-42, characterized in that, The first request is also used to indicate first information, which indicates whether the PPDU is transmitted via DRU, and the distributed bandwidth and the first information are jointly indicated by one or more fields.

46. ​​The AP according to claim 45, characterized in that, The one or more fields include: subfields in the UHR variant user information field and subfields in the trigger dependency user information field in the basic trigger frame.

47. The AP according to any one of claims 37-42, characterized in that, The distributed bandwidth is indicated by a public information field and / or a special user information field.

48. The AP according to any one of claims 37-47, characterized in that, When the bandwidth of the first channel is represented by a plurality of first bandwidths, the first request is used to indicate the distributed bandwidth of the DRU for each of the plurality of first bandwidths.

49. A non-AP STA (non-access point site), characterized in that, It includes a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or send signals so that the non-AP STA performs the method as described in any one of claims 1-12.

50. An access point (AP), characterized in that, The AP includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the AP performs the method as described in any one of claims 13-24.

51. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-24.

52. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-24.

53. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-24.

54. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-24.

55. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-24.

Images