Wireless communication method and communication device

Abstract

Embodiments of the present application provide a wireless communication method and a communication device. The method comprises: a first device sends first information to a second device. The first information is used for indicating whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission. By means of the first information, the second device can acquire information about whether the first device must send the first type of PPDU. The second device can adjust a communication solution on the basis of the first information, thereby meeting communication requirements of the first device and improving the throughput of the second device.

Description

Wireless communication methods and communication devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method and a communication device. Background Technology

[0002] In some cases, the first device must send a first type of physical layer protocol data unit (PPDU) to the second device. This means that in these situations, the second device may have difficulty receiving non-first type PPDUs sent by the first device. For example, the first device in an enhanced long range (ELR) state must send an ELR PPDU to the second device.

[0003] Summary of the Invention

[0004] This application provides a wireless communication method and a communication device. The various aspects covered by this application are described below.

[0005] In a first aspect, a wireless communication method is provided. The method includes: a first device sending first information to a second device; wherein the first information is used to indicate whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

[0006] Secondly, a wireless communication method is provided. The method includes: a second device receiving first information sent by a first device; wherein the first information is used to indicate whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

[0007] Thirdly, a communication device is provided. This communication device is a first device. The communication device includes: a transmitting unit for transmitting first information to a second device; wherein the first information is used to indicate whether the first device must transmit a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

[0008] Fourthly, a communication device is provided. This communication device is a second device. The communication device includes: a receiving unit, configured to receive first information sent by a first device; wherein the first information is used to indicate whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

[0009] Fifthly, a communication device is provided, including a processor and a memory, the memory for storing one or more computer programs, the processor for calling the computer programs in the memory to enable some or all of the steps of the methods described in the preceding aspects of the communication device.

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

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

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

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

[0014] Based on the first information, the second device can determine whether the first device must send a first type of PPDU. The second device can then adjust its communication scheme according to the first information to meet the communication needs of the first device and improve its throughput. Attached Figure Description

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

[0016] Figure 2A is a format example of an aggregation control (A-control) field.

[0017] Figure 2B is an example diagram of the format of a control subfield.

[0018] Figure 2C is a format example of a control information subfield within a control subfield.

[0019] Figure 3 is an example diagram of a trigger frame format.

[0020] Figure 4A shows an example of the format of the high-efficiency (HE) variant public information field.

[0021] Figure 4B is an example diagram of the format of the public information field for the Extremely High Throughput (EHT) variant.

[0022] Figure 5A is a format example of a HE variant user Info field.

[0023] Figure 5B is an example of the format of a user information field in an EHT variant.

[0024] Figure 6A is a format example of an ELR PPDU.

[0025] Figure 6B is an example diagram of another ELR PPDU format.

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

[0027] Figure 8 is an example of a scenario to which this application applies.

[0028] Figure 9 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0029] Figure 10 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0030] Figure 11 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0031] Figure 12 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0032] Figure 13 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0033] Figure 14 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0034] Figure 15 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.

[0035] Figure 16 is a schematic diagram of the format of a public information field of a trigger frame provided in an embodiment of this application.

[0036] Figure 17 is a format example diagram of the user information field of a trigger frame provided in an embodiment of this application.

[0037] Figure 18 is an example diagram of a trigger frame format provided in an embodiment of this application.

[0038] Figure 19 is a format example diagram of an A-control field provided in an embodiment of this application.

[0039] Figure 20 is an example diagram of another format of the A-control field provided in the embodiments of this application.

[0040] Figure 21 is a schematic structural diagram of a communication device provided in an embodiment of this application.

[0041] Figure 22 is a schematic structural diagram of another communication device provided in an embodiment of this application.

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

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

[0044] Communication system

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

[0046] Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application. Referring to Figure 1, the communication devices in the communication system 100 may include access points (APs) 111 and 112, as well as stations (STAs) 121 and 122. STA 121 can access the network through AP 111, and STA 122 can access the network through AP 112.

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

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

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

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

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

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

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

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

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

[0056] In this application embodiment, the STA can also be a device that provides voice / data / image connectivity to the user, such as a handheld device, vehicle device, home device, home appliance, gaming device, etc., with wireless connection function or equipped with a wireless communication module. Examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, drones or aerial photography equipment, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN) can also be televisions, refrigerators, washing machines, kitchen appliances, door locks, fish tanks, robot vacuum cleaners, game consoles, cameras / camcorders, etc. with wireless connectivity, but this application embodiment is not limited to these.

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

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

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

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

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

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

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

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

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

[0066] A-control field

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

[0068] The HT control field typically appears in control wrapper frames. It can be present in QoS data frames, QoS null frames, and management frames. The presence of the HT control field is controlled by the +HTC subfield within the frame control field.

[0069] It should be noted that the only control frame subtype with an HT control field is the control wrapper frame. An A-control frame described as +HTC (e.g., RTS+HTC, CTS+HTC, BlockAck+HTC, or BlockAckReq+HTC frame) means that a control wrapper frame is used to carry the control frame.

[0070] Table 1 shows an example of the format of an HT control field. As shown in Table 1, the A-control field can be an HT control field when both B0 and B1 are 1.

[0071] Table 1

[0072] Figure 2A is a format example of an A-control field. The A-control field shown in Figure 2A can be a subfield of the HE variant HT control field. As shown in Figure 2A, the A-control field can include one or more of the following fields: control list and padding.

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

[0074] Table 2

[0075] The padding subfield, if present, follows the last control subfield and is set to a 0 sequence so that the length of the A-control subfield carried in the HT control field is 30 bits.

[0076] It should be noted that the ELA control subfields (with a control identifier value of 2) mentioned in Table 2 can contain parameters related to various link modulation transmission methods, used for fast adaptive control of the EHT link. The specific format of the control information subfields in the ELA control subfields can be seen in Figure 2C.

[0077] As shown in Figure 2C, the control information subfield in the ELA control subfield may include one or more of the following fields: unsolicited MCS feedback (unsolicited MFB), MCS request (MRQ) / uplink EHT triggered PPDU MFB (UL EHT TB PPDU MFB), number of spatial streams (NSS), EHT-MCS, resource unit (RU) allocation, PS160, bandwidth (BW), MCS request sequence identifier (MSI) or partial PPDU parameters (MSI / partial PPDU parameters), transmission beamforming (TX beamforming), and high-efficiency link adaptation or EHT link adaptation (HLA / ELA). The meaning and definition of each field can be found in Table 3.

[0078] Table 3

[0079] The PPDU format field indicates the format of the PPDU for estimating an unsolicited MFB. For EHT MU PPDUs, the PPDU format field can be set to 0. For EHT TB PPDUs, the PPDU format field can be set to 1.

[0080] The encoding type field contains encoding information used to estimate the PPDU of an unsolicited MFB. For binary convolutional codes (BCC), the encoding type field can be set to 0. For low-density parity-check (LDPC), the encoding type field can be set to 1.

[0081] The MFB requester can set the MRQ / UL EHT TB PPDU MFB subfield in the ELA control subfield of the frame to 1 and the Unsolicited MFB subfield to 0 to request the STA to provide link adaptive feedback. In each request, the MFB requester sets the MSI field to a value between 0 and 6.

[0082] The MFB requester needs to specify the RU or MRU index and bandwidth for the request link adaptation feedback.

[0083] When receiving an ELA Control subfield of an MRQ / UL EHT TB PPDU with the MFB subfield equal to 1 and the Unsolicited MFB subfield equal to 0, the MFB responder calculates the EHT-MCS and NSS, as well as the bandwidth, of the RU or MRU specified in the MRQ. These estimates are based on the same RU or MRU as the PPDU carrying the MRQ. The PPDU carrying the MRQ should include the RU or MRU requested by the MFB. The MFB responder marks this calculation result as the MSI value of the ELA Control subfield in the received frame with the MRQ. The MFB responder may include the received MSI value in the MSI field of the corresponding response frame. In the case of a delayed response, this allows the MFB requester to associate the MFB with the requested MRQ.

[0084] When the MFB response end sends a request for MFB, the Unsolicited MFB subfield and the MRQ / UL EHT TB PPDU MFB subfield should be set to 0 in the ELA Control subfield.

[0085] The MFB responder can send a request-response frame containing any of the following combinations of EHT-MCS, NSS, and MSI: 1) EHT-MCS = 15, NSS = 7, MSI = 0-6: The responder will not provide feedback for a request with an MSI value; 2) EHT-MCS = valid value, NSS = valid value, MSI = 0-6: The responder is providing feedback for a request with an MSI value, and the MSI value in the response frame matches the MSI value of the MRQ request.

[0086] For both requested and non-requested responses, the recommended EHT-MCS and NSS subfields for the ELA control subfields should be selected from the EHT-MCS and NSS settings supported by the receiving STA.

[0087] Non-AP EHT STAs can set the Unsolicited MFB subfield in the ELA Control field sent to the AP to 1, and set the MRQ / UL EHT TB PPDU MFB to 1, to indicate that the NSS, EHT-MCS, bandwidth, and RU allocation in the ELA Control field represent the recommended MFB for subsequent EHT TB PPDUs sent by the STA that issued this recommendation. When the AP sends a trigger frame to the STA, it should not exceed the most recently received RU allocation and the recommended RU or MRU size in the PS160 subfield of the ELA Control field.

[0088] Trigger frame

[0089] In some communication standards (such as IEEE 802.11), trigger-based (TB) PPDU transmission can be implemented based on trigger frames. For example, a non-MU-RTS trigger frame allocates resources and requests the transmission of one or more TB PPDUs. The trigger frame may also carry additional information required for the STA to send an HE TB PPDU, EHT TB PPDU, Non-HT PPDU, or Non-HT Duplicate PPDU. For instance, when performing an uplink TB PPDU transmission, the AP can first send a trigger frame, and each non-AP STA can prepare and transmit a TB PPDU based on the parameters indicated by the received trigger frame.

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

[0091] As shown in Figure 3, the trigger frame may include one or more of the following fields: frame control, duration, receiver address (RA), transmission address (TA), common info, user info list, padding, and frame check sequence (FCS).

[0092] The frame control field can carry control information such as frame type.

[0093] The duration field can indicate the remaining transmission opportunity (TXOP) duration.

[0094] The RA field can indicate the station address or broadcast address of the receiving trigger frame. For example, for non-GCR MU-BAR, NFRP, or MU-RTS trigger frames, if there is a user information field and the AID12 subfield of the user information field contains the AID of a non-AP STA, then the RA field is set to the address of that STA. Similarly, for trigger frames with at least one user information field containing an AID12 subfield, the RA field is set to the broadcast address when allocating RA-RUs. Furthermore, for non-GCR MU-BAR trigger frames with multiple user information fields, the RA field is set to the broadcast address. For NFRP or MU-RTS trigger frames, the RA field is set to the broadcast address. Finally, for GCR MU-BAR trigger frames, the RA field is set to the MAC address of the group requesting reception status.

[0095] The TA field can indicate the address of the station sending the trigger frame or the basic service set identifier (BSSID). If the trigger frame is sent to a STA belonging to a single BSS, the TA field is the address of the STA sending the trigger frame. If the address of the trigger frame comes from at least two different BSSIDs in multiple BSSID sets, the TA field is the transmitted BSSID.

[0096] The following describes the public information field, user information list field, and fill field. It should be noted that the examples below use HE or EHT as examples to illustrate the various fields in the trigger frame for ease of understanding, but this is not a limitation of this application; this application can also be applied to other versions of trigger frames. For example, the public information field and user information list field in the UHR trigger frame can have the same or similar fields as those in the EHT trigger frame; simply replace "EHT" with "UHR" in the fields.

[0097] 1) Public Information Fields

[0098] The common information field primarily carries common information. The common information field can have different variants. For example, a common information field can be interpreted as an HE variant common Info field or an EHT variant common Info field. For instance, a non-EHT non-AP HE STA interprets the common information field as an HE variant common information field. For instance, if B54 and B55 in the common information field equal 1, then the non-AP EHT STA interprets the common information field as an HE variant common information field; otherwise, it interprets it as an EHT variant common information field.

[0099] Figure 4A shows an example of the format of the HE variant public information field.

[0100] As shown in Figure 4A, the HE variant common information field may include one or more of the following fields: trigger type, uplink length (UL length), more trigger frames (TF), carrier sensing required (CS), uplink bandwidth (UL BW), guard interval and HE-LTF type / trigger TXOP sharing mode (GI And HE-LTF type / trigger TXOP sharing mode), number of HE / EHT / UHR-LTF symbols and midamble periodicity, uplink space-time block coding (UL STBC), low-density parity check extra symbol segment (LDPC), AP transmit power (AP TX power), Pre-FEX padding factor (Pre-FEC padding factor), PE disambiguity, uplink spatial reuse (UL spatial reuse), Doppler, uplink HE-SIG-A2 reservation (UL HE-SIG-A2 reserved), reserved, and trigger dependent common information. info).

[0101] Figure 4B is an example diagram of the format of the public information field of the EHT variant.

[0102] As shown in Figure 4B, the EHT variant common information field may include one or more of the following fields: trigger type, uplink length, more trigger frames, carrier sensing required, uplink bandwidth, guard interval and HE / EHT-LTF type / trigger TXOP sharing mode, number of HE / EHT-LTF symbols, reserved, low-density parity extra symbol segment, AP transmit power, Pre-FEX fill factor, PE disambiguation, uplink space multiplexing, HE / EHT P160, special user info field flag, EHT reserved, and trigger dependency common information.

[0103] The trigger type field in the public information can be used to indicate a variant of the trigger frame. Variants of the trigger frame may include, for example, the basic trigger frame.

[0104] 2) User information list fields

[0105] The user information list field consists of one or more user info fields. In some types of trigger frames (such as EHT trigger frames), the user information list field includes one or more special user info fields, and / or multiple variant user info fields. Variant user info fields can be, for example, HE variant user info fields or EHT variant user info fields.

[0106] The following sections explain the special user information fields and the variant user information fields respectively.

[0107] A Special User Information field is a user information field that does not carry user-specific information but carries extended public information not provided in the public information field. If a Special User Information field exists, it is located after the public information field of the triggering frame and carries information from the U-SIG field of the requested EHT TB PPDU.

[0108] The variant user information field can carry information about non-AP STAs indicated by the AID12 subfield.

[0109] Figure 5A is a format example of the HE variant user information field. As shown in Figure 4A, the variant user information field may include one or more of the following fields: Association Identifier 12 (AID12), RU allocation, Uplink Forward Error Correction Coding Type (UL FEC coding type), Uplink HE Modulation and Coding Strategy (UL HE-MCS), Uplink Dual Carrier Modulation (UL DCM), Spatial Stream Allocation / Random Access Resource Unit Information (SS allocation / RA-RU information), Uplink Target Receive Power (UL target receive power), Trigger Dependency User Information, and Reserved.

[0110] Figure 5B is an example of the format of a user information field in an EHT variant.

[0111] As shown in Figure 5B, the EHT variant user information field may include one or more of the following: AID12, RU allocation, uplink forward error correction coding type, UL EHT-MCS, spatial stream allocation, uplink target received power, PS160, trigger-dependent user information, and reserved.

[0112] ELR

[0113] Access points (APs) typically have higher transmission power than non-AP STAs, leading to a significant difference in downlink (DL) and uplink (UL) link budgets. A DL link refers to the link from the AP to a non-AP STA, while a UL link refers to the link from a non-AP STA to the AP. In some cases, the budget difference between DL and UL links can reach 6 dB. Some communication standards (such as UHR) have proposed the need to increase transmission range to address the uplink and downlink budget imbalance.

[0114] To address the aforementioned issues or needs, some communication technologies have proposed ELR technology. ELR data rates can be around 1.5 Mbps or 3 Mbps.

[0115] Figure 6A shows an example of an ELR PPDU format. As shown in Figure 6B, an ELR PPDU can contain three parts: a legacy preamble, an ELR preamble, and an ELR data field. The addition of the ELR preamble can effectively improve the coverage of the preamble and extend the uplink communication range.

[0116] For the application frequency bands of ELR PPDU, it is possible to implement ELR PPDU in the 2.4GHz, 5GHz, and 6GHz bands. Among them, the 2.4GHz band can be used for both uplink and downlink ELR PPDU, while the 5GHz and 6GHz bands can only be used for uplink ELR PPDU.

[0117] Figure 6B is an example diagram of another ELR PPDU format.

[0118] As shown in Figure 6B, compared to non-ELR PPDUs, ELR PPDUs retain the same L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG fields. New ELR mark 1 and ELR mark 2 fields are designed to distinguish ELR PPDUs from non-ELR PPDUs through a special QBPSK modulation scheme. The sequence design of ELR-STF and ELR-LTF is the same as that of EHT-STF and EHT-LTF, but a fixed OFDM symbol length and GI are used to enhance ELR PPDU channel estimation. ELR-SIG carries information such as the modulation and coding format for demodulating ELR-DATA. To extend the transmission range of ELR PPDUs, L-STF, L-LTF, ELR-STF, and ELR-LTF employ 3dB power enhancement; ELR-Data uses BPSK and MCS0 modulation, and frequency domain replication improves bit error rate performance.

[0119] Related technologies suggest that the AP can notify the non-AP STA of the modulation order and encoding format used when transmitting ELR PPDUs in the future through hard configuration or soft indication, so that the AP can parse the ELR PPDUs sent by the non-AP STA.

[0120] For communication devices supporting ELR technology, the device can dynamically switch between ELR and non-ELR states. A communication device in ELR state needs to send an ELR PPDU. Alternatively, a communication device in ELR state must send an ELR PPDU. When a communication device is in ELR state, if it sends a non-ELR PPDU, the other end may not receive the PPDU. When the communication device is not in ELR state (i.e., in a non-ELR state), it can send either an ELR PPDU or a non-ELR PPDU. The format of the ELR PPDU can be as shown in Figure 6A or Figure 6B.

[0121] For example, if the first device and the second device are far apart (e.g., the first device is in the coverage edge area of ​​the second device), the first device is in ELR state and must send an ELR PPDU to the second device. Conversely, if the first device and the second device are close together, the first device is not in ELR state and can send either an ELR PPDU or a non-ELR PPDU to the second device.

[0122] It should be noted that whether a communication device is in an ELR state can change over time. For example, a first device may be in an ELR state at a certain moment, and may not be in an ELR state after a period of time. For instance, if the first device or a second device communicating with the first device is moving, the first device can switch from an ELR state to a non-ELR state when the distance between the first device and the second device gradually approaches, and can switch from a non-ELR state to an ELR state when the distance between the first device and the second device gradually increases.

[0123] As mentioned above, the preamble designs for ELR PPDU and non-ELR PPDU differ significantly, thus preventing simultaneous transmission of ELR PPDU and non-ELR PPDU at different frequency points. If the AP is unaware that the STA is in an ELR state requiring uplink transmission using ELR PPDU, the AP may require all non-AP STAs to send non-ELR TB PPDUs in OFDMA scheduling. This could lead to communication failure for STAs in ELR state due to insufficient power, preventing the AP from parsing their signals, thus hindering uplink transmission via non-ELR PPDUs. Furthermore, ELR PPDUs are incompatible with non-ELR PPDUs, preventing STAs in ELR state from selecting ELR TB PPDUs for uplink transmission. In conclusion, if the AP is unaware of the STA's state, some users may experience transmission failures during multi-user scheduling, reducing system transmission efficiency and time-frequency resource utilization.

[0124] Figure 7 is a schematic flowchart of a wireless communication method provided in an embodiment of this application to solve the above-mentioned problems. The method shown in Figure 7 can be executed by a first device and a second device. Both the first device and the second device can be the communication devices described above. For example, the first device may include a non-AP STA, and the second device may include an AP.

[0125] The method shown in Figure 7 may include step S710.

[0126] S710, the first device sends the first information to the second device.

[0127] The first information is used to indicate whether the first device must send a first type of PPDU at a first moment.

[0128] The first type of PPDU supports enhanced long-distance transmission. For example, the first type of PPDU can be an ELR PPDU. In this application, the second type of PPDU may not support enhanced long-distance transmission. For example, the second type of PPDU can be a non-ELR PPDU.

[0129] The first device can be a device that supports sending the first type of PPDU. That is, the first device is capable of sending the first type of PPDU or the first device has the capability to send the first type of PPDU.

[0130] As mentioned above, if the first device must or needs to send a first type of PPDU, then the first device is in an ELR state. Therefore, the first information can be used to indicate whether the first device is in an ELR state at a given moment. Thus, the first information can also be called ELR status information. The frame carrying the first information can be called an ELR status frame.

[0131] In some embodiments, the first moment may include the current moment. That is, the first information may be used to indicate whether the first device is currently in an ELR state. In this case, the first information may be used to indicate the real-time ELR state of the first device.

[0132] In some embodiments, the first moment may include a future moment. That is, the first information can be used to indicate whether the first device will be in an ELR state at a future moment; that is, the first device can use the first information to predict that it will be in an ELR state. For example, when the first device moves away from the second device, the first device can estimate, based on its speed, that it is at the coverage edge of the second device at the first moment, and send the first information to the second device before the first moment to indicate that it will be in an ELR state at that moment. In this case, the first information can be used to indicate the predicted ELR state of the first device.

[0133] In some embodiments, the first moment may belong to a first time period. Based on this, the first information can indicate whether the first device must send a first type of PPDU within the first time period. One or more of the duration, start time, and end time of the first time period can satisfy: protocol predefined, reported by the first device, or configured by the network.

[0134] By using the first information, the first device can send information to the second device regarding whether it must send a first type of PPDU. This allows the second device to adaptively or specifically adjust its communication strategy based on the first information. For example, if the first device includes non-AP STAs and the second device includes an AP, the non-AP STAs can indicate to the AP whether they are in an ELR state by reporting the first information. The AP can then design a targeted multi-user scheduling strategy in subsequent transmissions based on the first information. For instance, if some or all of the multiple non-AP STAs are in an ELR state, the AP can instruct all non-AP STAs to uniformly use ELR PPDUs. Similarly, if some or all of the multiple non-AP STAs are in an ELR state, the AP can allocate narrower bandwidth PPDUs to the non-APs in the ELR state to improve signal reception success rate. For example, if some or all of multiple non-AP STAs are in ELR state, the AP can instruct non-AP STAs in ELR state to simultaneously send ELR PPDUs, and non-AP STAs in non-ELR state to simultaneously send non-ELR PPDUs, but non-AP STAs in ELR state and non-AP STAs in non-ELR state do not send PPDUs simultaneously. Alternatively, if all of multiple non-AP STAs are in non-ELR state, the AP can instruct all non-AP STAs to use non-ELR PPDUs.

[0135] The following explanation uses the scenario shown in Figure 8 as an example.

[0136] In Figure 8, the first device may include STA1, STA2, STA3, or STA4. The second device includes the AP. STA4 is in an ELR state, while STA1 through STA3 are in a non-ELR state. In Figure 8, if the AP is unaware of whether STA1 through STA4 are in an ELR state, it may instruct STA1 through STA4 to send data using a non-ELR PPDU. Since STA4 is in an ELR state, the UL data sent by STA4 via the non-ELR PPDU is highly unlikely to be received by the AP. This results in STA4 failing to send data.

[0137] Based on this application, in the scenario shown in Figure 8, STA1 to STA4 can indicate to the AP whether they are in an ELR state by reporting the first information. The AP can determine from the first information that STA4 is in an ELR state, while STA1 to STA3 are in a non-ELR state. Therefore, when scheduling STA1 to STA4 using OFDMA, the AP can instruct the use of ELR PPDUs, allowing STA4 to send data to the AP via ELR PPDUs with a longer propagation distance. Furthermore, since STA1 to STA3 and STA4 use the same PPDU format, the AP can parse the PPDUs sent by STA1 to STA4.

[0138] In some embodiments, the first device may receive a first request message sent by the second device. The first request message may be used to request the acquisition or collection of first information from one or more of the first devices. That is, the first request message has an ELR status collection function. Based on this, the first request message may be called an ELR status request message or an ELR status collection request message. The frame carrying the first request may also be called a frame with ELR status collection function. Correspondingly, the frame carrying the first information may be called an ELR status feedback frame.

[0139] Therefore, the transmission of the first message can be based on a request. In response to receiving a first request message from the second device, the first device can send the first message.

[0140] Optionally, the first request information can be carried in a trigger frame. The trigger frame can be used to trigger one or more first devices to send a PPDU indicating the first information to a second device. In other words, the trigger frame can be used to request one or more first devices to send the first information to the second device. In this case, the trigger frame can be called a trigger frame with ELR status collection functionality. In this case, the first information can be carried in the A-control field.

[0141] It is understandable that when the first request information is carried in the trigger frame, the PPDU indicating the first information is a TB PPDU.

[0142] Taking a first device including a non-AP STA and a second device including an AP as an example, the AP can send a trigger frame after competing to obtain the channel, and send a trigger frame to one or more non-AP UHR STAs with unknown ELR status. The triggered non-AP UHR STAs use UL OFDMA to report their first information.

[0143] It is understandable that when the first request information is carried in the trigger frame, the first information can be reported in the form of multi-user triggering, thereby reducing the latency introduced by multiple first devices competing for the channel separately and realizing real-time and efficient collection of the first information.

[0144] The following explanation uses Figure 9 as an example.

[0145] In Figure 9, the first device includes any one of STA1 to STA n, and the second device includes the AP. In step S910, the AP sends a trigger frame. This trigger frame may include first request information. The first request information can be used to request STA1 to STA k to send first information, where k is a positive integer. In step S920, in response to the trigger frame in step S910, STA1 to STA k send back first information. The first information sent by STA1 to STA k indicates whether each is in an ELR state.

[0146] The first request message requests one or more first devices that may be some or all of the non-AP STAs within the coverage area of ​​the second device. Taking the second device as an example, the first request message requests one or more first devices that may be some or all of the non-AP STAs associated with that AP. If sending a first request message once can only request some of all the first devices, the second device can send the first request message multiple times to cover more first devices, so that more first devices can respond with the first message.

[0147] Continuing with Figure 9 as an example, if the trigger frame sent in step S910 does not cover all STA1 to STA n, the AP can add one or more trigger frames as needed. For example, the AP can execute step S930, i.e., send the trigger frame again. The first request information included in the trigger frame in step S930 can be used to request STA k+1 to STA n to provide first information. In step S940, in response to the trigger frame in step S930, STA k+1 to STA n provide first information. The first information sent by STA k+1 to STA n indicates whether they are in the ELR state.

[0148] In some embodiments, the first request information may be carried in a non-triggering frame. In other words, the first information may be sent based on a request in a non-triggering frame. In this case, the frame carrying the first request information may be called an ELR status request frame.

[0149] For example, after the second device competes for and acquires the channel, it can send a first request message to a single first device via an ELR status request frame. Upon receiving the first request message, the first device can compete for and acquire the channel, and then send first information to the second device. For instance, the first request message can be carried in the A-control field sent by the second device. The first information can also be carried in the A-control field sent by the first device. This will be explained below with reference to Figure 10.

[0150] In Figure 10, the first device includes a STA, and the second device includes an AP. In step S1010, the AP competes for the channel and sends an ELR status request frame. In step S1020, after receiving the ELR status request frame, the STA competes for the channel and sends an ELR status frame.

[0151] It should be noted that if the first request information is carried in a trigger frame, the inter-frame interval between the frame indicating the first information and the trigger frame needs to meet the requirements of the relevant technology regarding the inter-frame interval of the trigger frame. For example, the inter-frame interval between the trigger frame and the frame indicating the first information needs to be SIFS. Continuing with Figure 9 as an example, the inter-frame interval between the trigger frame in step S910 and the frame in step S920 needs to be SIFS. If the first request information is sent through a non-trigger frame, the inter-frame interval between the frame indicating the first information and the non-trigger frame is not strictly required. Continuing with Figure 10 as an example, the inter-frame interval between the frame in step S1010 and the frame in step S1020 is not strictly required.

[0152] The following technical solution details how one or more devices respond with the first information when the second device requests to obtain the first information from one or more first devices through the first request information.

[0153] In some embodiments, one or more first devices indicate the first information via a first type of PPDU. That is, the first devices can be required to respond to the first information using a uniform first type of PPDU.

[0154] As one possible implementation, one or more first devices indicate the first information via an ELR PPDU. Continuing with Figure 9 as an example, as shown in Figure 9, in step S920 or S940, STA1 to STAn all need to feed back the first information via an ELR TB PPDU.

[0155] Whether the first device is in ELR state or not, it can send ELR PPDUs if it supports ELR functionality. For the first device in ELR state, sending the first information via ELR PPDUs increases the success rate of the second device receiving the first information. Furthermore, if the first device sends the first information via PPDUs of the same format (first type of PPDU), the second device can successfully receive the PPDUs sent by each first device and achieve symbol alignment.

[0156] In some embodiments, some or all of the one or more first devices indicate the first information via a second type of PPDU with a bandwidth less than or equal to a first bandwidth threshold. For example, all of the one or more first devices may indicate the first information via a second type of PPDU with a smaller bandwidth.

[0157] It should be noted that the first bandwidth threshold is a positive number. For example, the first bandwidth threshold is equal to 20MHz. Exemplarily, the bandwidth of the second type of PPDU indicating the first information can be 26-tone, 52-tone, or 106-tone.

[0158] As one possible implementation, the second type of PPDU can be a non-ELR PPDU. For example, the second type of PPDU can include a UHR PPDU.

[0159] For a first device in ELR state, if the first device directly sends a non-ELR PPDU, the second device is highly unlikely to receive it. This application improves the success rate of the second device receiving non-ELR PPDUs by limiting the bandwidth, i.e., by reducing the signal bandwidth, thereby increasing the signal strength of each subcarrier. Furthermore, when all first devices indicate the first information using second-type PPDUs, sending the first information using PPDUs of the same format (i.e., second-type PPDUs) allows the second device to successfully receive the non-ELR PPDUs sent by each first device and achieve symbol alignment.

[0160] The following description is provided with reference to Figure 11. In Figure 11, the first device includes any STA from STA1 to STAn. The second device includes the AP. The method shown in Figure 11 may include steps S1110 to S1120. Steps S1130 and S1140 are optional.

[0161] In step S1110, the AP sends a trigger frame. This trigger frame is used to request STA1 to STAk to send their respective first messages. The AP restricts all non-AP UHR STAs to reply using a narrow bandwidth UHR TB PPDU (non-ELR PPDU) format of less than 20MHz. For example, the bandwidth of the UHR TB PPDU sent by each user is limited to 26-tone, 52-tone, or 106-tone.

[0162] In step S1120, STA1 to STAk use the allocated frequency domain resources to reply with a UHR TB PPDU carrying the first information after triggering frame SIFS.

[0163] If a single trigger fails to cover all non-AP STAs, the AP can attach one or more trigger frames with first information collection functionality as needed to continue collecting ELR status information for other non-AP STAs. For example, the AP, STA k+1 to STA n can execute steps S1130 and S1140.

[0164] In some embodiments, the first request information is used to trigger some or all of the one or more devices to indicate first information via a second type of PPDU greater than or equal to a second bandwidth threshold. For example, the first request information may be used to trigger all of the one or more devices to indicate first information via a second type of PPDU greater than or equal to the second bandwidth threshold. In these embodiments, the first information can be determined by whether a second device receives a second type of PPDU.

[0165] Optionally, if the second device does not receive a second type of PPDU sent by the first device, the second device can infer that the first device must send a first type of PPDU, i.e., it is in an ELR state. If the second device receives a second type of PPDU sent by the first device, the second device can infer that the first device is not required to send a first type of PPDU, i.e., it is in a non-ELR state. For example, if the second device sends trigger frames to K first devices and receives second type PPDUs sent by M first devices, the second device can infer that M first devices are in a non-ELR state, and the remaining KM first devices are in an ELR state.

[0166] It should be noted that the second bandwidth threshold is a positive number. For example, the second bandwidth threshold is equal to 20MHz. That is to say, the bandwidth of the second type of PPDU indicating the first information sent by the first device can be greater than or equal to 20MHz.

[0167] As mentioned above, the second type of PPDU can include non-ELR PPDUs. For a first device in an ELR state, if the bandwidth of the non-ELR PPDU sent by the first device is large, the second device is likely not to receive the non-ELR PPDU. In this application, if the second device receives a non-ELR PPDU, it can be inferred that the first device that sent the non-ELR PPDU is in a non-ELR state; if the second device does not receive a non-ELR PPDU, it can be inferred that the first device that is expected to send the non-ELR PPDU is in an ELR state. In addition, when all first devices indicate the first information through the second type of PPDU, the first devices sending the first information through PPDUs of the same format (i.e., the second type of PPDU) can enable the second device to successfully receive the non-ELR PPDUs sent by each first device and achieve symbol alignment.

[0168] The following description is based on Figure 12. In Figure 12, the first device includes any STA from STA1 to STAn. The second device includes the AP. The method shown in Figure 12 may include steps S1210 to S1220. Steps S1230 and S1240 are optional.

[0169] In step S1210, the AP sends a trigger frame. This trigger frame is used to request STA1 to STAk to send their respective first messages. The AP requires all non-AP UHR STAs to reply using a UHR TB PPDU format with a wider bandwidth of 20MHz or greater.

[0170] In step S1220, STA1 to STAk use the allocated frequency domain resources to reply with a UHR TB PPDU carrying the first information after triggering frame SIFS.

[0171] If the AP receives a UHR TB PPDU in the corresponding frequency band, it determines that the non-AP UHR STA is in a non-ELR state; if the AP does not receive a UHR TB PPDU in the corresponding frequency band, it determines that the non-AP UHR STA is in an ELR state.

[0172] If a single trigger fails to cover all non-AP STAs, the AP can attach one or more trigger frames with first information collection functionality as needed to continue collecting ELR status information for other non-AP STAs. For example, the AP, STA k+1 to STA n can execute steps S1230 and S1240.

[0173] In some embodiments, the PPDU indicating the first information may further include a data frame. For example, after receiving a trigger frame carrying first request information, the first device may use the frequency domain resources allocated by the trigger frame to reply with a data frame carrying the first information. This technical solution can send data while sending the first information, which can improve the utilization of communication resources and also improve data transmission efficiency.

[0174] The following description is based on Figure 13. In Figure 13, the first device includes any STA from STA1 to STAn. The second device includes the AP. The method shown in Figure 13 may include steps S1310 to S1320. Steps S1330 and S1340 are optional.

[0175] In step S1310, the AP sends a trigger frame. This trigger frame is used to request STA1 to STAk to send their respective first information.

[0176] In step S1320, STA1 to STAk use the allocated frequency domain resources to reply with a TB PPDU carrying the first information and data after triggering frame SIFS.

[0177] If a single trigger fails to cover all non-AP STAs, the AP can attach one or more trigger frames with first information collection functionality as needed to continue collecting ELR status information for other non-AP STAs. For example, the AP, STA k+1 to STA n can execute steps S1330 and S1340.

[0178] As one possible implementation, the size of the data frame contained in the PPDU indicating the first information is less than or equal to a first data threshold. The first data threshold can be a positive number. That is, in some embodiments, the size of the data frame contained in the PPDU indicating the first information is limited. By limiting the size or length of the data frame, the second device can receive the first information earlier, thereby improving the real-time performance of the first information collection.

[0179] It should be noted that the PPDU carrying the data frame and indicating the first information can be any PPDU described above. For example, the PPDU carrying the data frame and indicating the first information can be a first type of PPDU. Alternatively, the PPDU carrying the data frame and indicating the first information can be a second type of PPDU with a bandwidth less than a first bandwidth threshold. Or, the PPDU carrying the data frame and indicating the first information can be a second type of PPDU with a bandwidth greater than or equal to a second bandwidth threshold.

[0180] It should be noted that the above embodiments can be implemented individually or in combination. For example, the first request information can be used to trigger one or more first devices to indicate the first information via a second type of PPDU. Some of the first devices can indicate the first information via a second type of PPDU less than or equal to a first bandwidth threshold, while others can indicate the first information via a second type of PPDU greater than a second bandwidth threshold. The first bandwidth threshold and the second bandwidth threshold can be equal.

[0181] In some embodiments, the first device may report the first information itself. In this case, the first information may be carried in the A-control field. As shown in Figure 14, the first device includes a STA and the second device includes an AP. The STA may compete for the channel and send an ELR status frame unilaterally to the AP to indicate the first information.

[0182] As one possible implementation, the first device can periodically report the first information. The period at which the first device reports the first information can be predefined and network-configured.

[0183] As one possible implementation, the first device may report first information when a first condition is met. Optionally, the first condition may include: a change in the ELR state of the first device. For example, the first device may send first information when switching from an ELR state to a non-ELR state. For example, the first device may send first information when switching from a non-ELR state to an ELR state.

[0184] In some embodiments, the second device may send an acknowledgment (Ack) message to the first device. The acknowledgment message can be used to determine that the second device has received the first information. In this case, the frame format including the first information is a frame format requiring acknowledgment.

[0185] If the first device does not receive an acknowledgment after sending the first message, it can resend the first message to ensure that the second device successfully receives it. In other words, the first device can send the first message multiple times before receiving an acknowledgment. If the number of times the first device sends or resends the first message exceeds a certain threshold, the first device can stop sending the first message.

[0186] As shown in Figure 15, the first device includes a STA, and the second device includes an AP. The STA can compete for the channel and send an ELR status frame to the AP. The ELR status frame has a frame format that requires acknowledgment. The AP needs to reply with acknowledgment information to complete the reporting process of the first information.

[0187] In some embodiments, confirmation information may be carried in the A-control field.

[0188] In some embodiments, the frame format including the first information can be a frame format that does not require confirmation. That is, the reporting of the first information is completed without the need for confirmation from a second device.

[0189] The format of the signaling involved in this application is described below.

[0190] In some embodiments, the field carrying the first request information may be a first field. The first field can be used to indicate whether first information needs to be collected, i.e., whether to request the first device to send first information. The first field may occupy 1 bit. For example, a value of 1 for the first field indicates that first information is not collected, and a value of 0 for the first field indicates that first information is collected. Alternatively, a value of 0 for the first field indicates that first information is not collected, and a value of 1 for the first field indicates that first information is collected. In some embodiments, the first field may also be called an ELR field.

[0191] In some embodiments, when the second device sends the first request information, the second device may indicate third information. The third information is used to indicate the type of the PPDU carrying the first information. For example, the third information may be carried in a second field. The second field may occupy one bit. For example, a value of 1 in the second field may indicate that the PPDU carrying the first information is a first type of PPDU; a value of 0 in the second field may indicate that the PPDU carrying the first information is a second type of PPDU. Similarly, a value of 0 in the second field may indicate that the PPDU carrying the first information is a first type of PPDU; a value of 1 in the second field may indicate that the PPDU carrying the first information is a second type of PPDU. In some embodiments, the second field may also be called a PPDU type field.

[0192] In some embodiments, the field carrying the first information can be a third field. The third field can be used to indicate whether the first device is required to send a first type of PPDU at the first moment. For example, the third field can occupy 1 bit. For instance, a value of 1 in the third field can indicate that the first device is required to send a first type of PPDU at the first moment; a value of 0 in the third field can indicate that the first device is not required to send a first type of PPDU at the first moment. Similarly, a value of 0 in the third field can indicate that the first device is required to send a first type of PPDU at the first moment; a value of 1 in the third field can indicate that the first device is not required to send a first type of PPDU at the first moment. In some embodiments, the third field can also be called an ELR status field.

[0193] As mentioned above, the first request information can be carried in a trigger frame. The trigger frame provided in this application is described below.

[0194] Optionally, the trigger frame carrying the first request information can be a trigger frame type already defined in the relevant art. For example, the trigger frame carrying the first request information may include one or more of trigger frames such as BSRP, BQRP, and NFRP.

[0195] In some embodiments, the first request information may be carried in the public information field and / or user information field of the trigger frame. Exemplarily, the first request information may be carried in a reserved field within the public information field and / or user information field defined in related technologies. Examples 1 and 2 are provided below for illustration.

[0196] Example 1

[0197] The trigger frame in Example 1 can be a specific trigger frame such as BSRP, BQRP, or NFRP. In Example 1, this application modifies the public information field format already defined in related technologies so that the public information field includes a first field. For example, B22, B26, B53, or B63 in the public information field of the trigger frame can be defined as the first field. B22, B26, B53, or B63 in the public information field of the trigger frame can be defined as the second field.

[0198] Figure 16 is a format example diagram of a common information field in a trigger frame provided by an embodiment of this application. As shown in Figure 16, B22 in the common information field of the trigger frame is defined as the first field, and B26 is defined as the second field. As shown in Figure 4B, in related technologies, B22 and B26 in the common information field are both reserved bits.

[0199] As shown in Figure 16, the common information field in the trigger frame defined in this application embodiment may include one or more of the following fields: trigger type, uplink length, more trigger frames, carrier sensing required, uplink bandwidth, guard interval and HE / EHT / UHR-LTF type / trigger TXOP sharing mode, HE / EHT / UHR-LTF symbol count, reservation, and low-density parity check extra symbol segment. In addition to the fields shown in Figure 16, the common information field may also include one or more of the following: AP transmit power, Pre-FEX fill factor, PE disambiguation, uplink space multiplexing, HE / EHT / UHR P160, special user information field indication, EHT / UHR reservation, and trigger-dependent common information. The meaning of each field can be consistent with the definitions in related technologies, and will not be repeated here.

[0200] The first device that receives the trigger frame shown in Figure 16 needs to reply with a response frame in the format required by the trigger frame (indicated by the value of B26), and decide whether to reply with the first information based on the value of B22 in the common information field.

[0201] Example 2

[0202] The trigger frame in Example 2 can be a specific trigger frame such as BSRP, BQRP, or NFRP. In Example 2, this application modifies the user information field format already defined in related technologies so that the user information field includes a first field. For example, B25 in the user information field of the trigger frame can be defined as the first field.

[0203] Figure 17 is a format example diagram of a user information field in a trigger frame provided by an embodiment of this application. As shown in Figure 17, B25 in the user information field of the trigger frame is defined as the first field. As shown in Figure 5B, in related technologies, B25 in the user information field is a reserved bit.

[0204] As shown in Figure 17, the user information field in the trigger frame defined in this application embodiment may include one or more of the following fields: AID12, RU allocation, uplink forward error correction coding type, UL UHR-MCS, spatial stream allocation, uplink target received power, PS160, and trigger-dependent user information. The meaning of each field can be consistent with the definitions in related technologies, and will not be repeated here.

[0205] Upon receiving the trigger frame shown in Figure 17, the non-AP STA needs to reply with a response frame in the required format, and decide whether to reply with the first message based on the value of B25 in the user information field.

[0206] Optionally, the first request information can be carried in a newly defined trigger frame. For example, the newly defined trigger frame can be used to indicate information related to the first type. In some embodiments, the newly defined trigger frame in this application can also be referred to as an ELR status poll (ESP) trigger frame.

[0207] An ESP trigger frame can be distinguished from trigger frames already defined in related technologies by the value of the trigger type field in the public information field. For example, a trigger frame includes a trigger type field, and the value of the trigger type field in an ESP trigger frame is a first value. The first value indicates that the type of the trigger frame is related to the first type. In other words, if the trigger type field in the public information field of a trigger frame has a first value, the trigger frame can be an ESP trigger frame.

[0208] The first value can be any value other than the trigger type field value corresponding to the trigger frame type defined in the related technologies. For example, in the related technologies, the trigger type field value of 0-8 corresponds to a defined trigger frame type. The trigger type field value corresponding to the ESP trigger frame defined in this application can be any value from 9-15. For example, a trigger type field value of 9 can indicate that the trigger frame is an ESP trigger frame.

[0209] In some embodiments, the first field may belong to the public information field and / or the user information field in the ESP trigger frame. The second field may belong to the public information field and / or the user information field in the ESP trigger frame.

[0210] In the ESP trigger frame, the AID12 field of the user information field in the user information list field can identify the STA that needs to report the ELR status. If the specified AP replies with an ELR TB PPDU, the RU allocation, UL FEC encoding type, UL UHR-MCS, SS allocation, and other fields in this trigger frame should meet the transmission requirements of the ELR PPDU.

[0211] Optionally, the ESP trigger frame may not contain part or all of the content in the trigger dependency public information field and / or trigger dependency user information field.

[0212] Figure 18 is a format example diagram of the ESP trigger frame provided in an embodiment of this application.

[0213] As shown in Figure 18, the common information fields of the ESP trigger frame include the trigger type field. The correspondence between the values ​​of the trigger type field and the trigger frame variants is shown in Table 4.

[0214] The meanings of the other fields included in the trigger frame shown in Figure 18 can be found in relevant technologies, and will not be elaborated here.

[0215] As mentioned above, the first information or first request information can be indicated through the A-control field. The following provides an example of the A-control field.

[0216] In some embodiments, the first information or the first request information may be carried in a first link adaptation field. Exemplarily, the first link adaptation field may be a UHR link adaptation (ULA) field. Similar to the ELA field, the ULA field can be used to indicate information related to link adaptation in UHR communication. In this application, the ULA field may carry the first information or the first request information. That is, the ULA field can be used to indicate information related to link adaptation in UHR communication as well as the first information (or the first request information).

[0217] The first link adaptive field can take any value from 10 to 14 in Table 2 to distinguish it from other A-control fields defined in Table 2.

[0218] The following describes the format related to the first information in the first link adaptive field.

[0219] As one possible implementation, the first link adaptation field may include the third field described above. For example, a separate third field indicating the first information can be set in the first link adaptation field. Exemplarily, the third field may occupy one or more reserved bits in the first link adaptation field as defined in related technologies.

[0220] As another possible implementation, the fields in the first link adaptation field that indicate the first information can be reused to indicate other information. For example, the MCS field and / or NSS field in the first link adaptation field can be used to indicate the first information.

[0221] The MCS field is used to indicate the recommended MCS. The value of the MCS field can be the indicated MCS index minus 1. The value range of the MCS field is 0-17. The name of the MCS field is for illustrative purposes only; this field can have other names, such as the UHR MCS field.

[0222] The NSS field is used to indicate the recommended number of spatial flows. The value of the NSS field can be the number of spatial flows minus 1. The value range of the NSS field is 0-3. The name of the NSS field is for illustrative purposes only; this field can have other names.

[0223] Optionally, the MCS field can be used to indicate first information. For example, when the MCS field has a special value, it can indicate first information; or, when the MCS field has a special value, it indicates that the first device must send a first type of PPDU at the first moment, and when the MCS field has a non-special value, it indicates that the first device is not required to send a first type of PPDU at the first moment. The special value can be, for example, any value from 16 to 31. For example, the special value can be 16 or 17.

[0224] In addition to indicating the first information, the MCS field can also indicate the recommended MCS. That is, while the MCS field indicates that the first device must use the first type of PPDU, it can also indicate the recommended MCS for the first type of PPDU. The MCS for the first type of PPDU can be an MCS with an index of 0 or 1 (i.e., MCS0 or MCS1). For example, when the MCS field has a special value, it indicates that the first device must send the first type of PPDU at the first moment, and the MCS is MCS0 or MCS1. When the MCS field has a non-special value, it indicates that the first device is not required to send the first type of PPDU at the first moment.

[0225] Therefore, when the first device is in ELR state, this application can simultaneously indicate the modulation and coding information adopted by the first device through the MCS field, so that the second device can adaptively configure ELR-related information based on the indication of the MCS field.

[0226] The values ​​of the MCS field and their corresponding meanings are shown in Table 5.

[0227] Table 5

[0228] As shown in Table 5, the value of MCS field 16 or 17 indicates that the first device is in ELR state. A value of 16 indicates that the STA is in ELR state and the recommended MCS is MCS0. A value of 17 indicates that the first device is in ELR state and the recommended MCS is MCS1.

[0229] Optionally, the MCS and NSS fields can jointly indicate the first information. For example, when the combination of the MCS and NSS fields has a special value, the MCS field can indicate the first information; or, when the combination of the MCS and NSS fields has a special value, it indicates that the first device must send a first type of PPDU at the first moment, and when the combination of the MCS and NSS fields has a special value, it indicates that the first device is not required to send a first type of PPDU at the first moment. Here, a special value can refer to an NSS field value of 3 and an MCS field value of any value between 14 and 31. The values ​​of the MCS and NSS fields and their corresponding meanings are shown in Table 6.

[0230] Furthermore, while the MCS and NSS fields can jointly indicate the first information, they can also jointly indicate the MCS. That is, when the MCS and NSS fields jointly indicate that the first device must use a first type of PPDU, the MCS and / or NSS fields can also indicate the MCS of the first type of PPDU. The MCS of the first type of PPDU can be an MCS with an index of 0 or 1 (i.e., MCS0 or MCS1). For example, when the MCS and NSS fields have special values, it indicates that the first device must send a first type of PPDU at the first moment, and the MCS is MCS0 or MCS1. When the MCS and NSS fields have non-special values, they indicate that the first device is not required to send a first type of PPDU at the first moment.

[0231] Table 6

[0232] As shown in Table 6, a value of 3 for the NSS field and a value of 14 or 15 for the MCS field indicate that the first device is in ELR state. A value of 14 for the MCS field indicates that the STA is in ELR state and the recommended MCS is MCS0. A value of 15 for the MCS field indicates that the first device is in ELR state and the recommended MCS is MCS1.

[0233] The following describes the format of the first link adaptive field related to the first request information.

[0234] The first link adaptation field may include one or more indicator fields. The indicator fields are used to indicate whether the first link adaptation field carries first information or first request information. For example, if the value of the indicator field is a first specific value, the first link adaptation field is used by the first device to send first information to the second device; if the value of the indicator field is a second specific value, the first link adaptation field is used by the second device to send first request information to the first device.

[0235] For example, one or more indication fields in the first link adaptation field may include: the Unsolicited MFB field and the MRQ / UL EHT TB PPDU MFB field. If the Unsolicited MFB field is 0 and the MRQ / UL EHT TB PPDU MFB field is 1, the second device can send a first request message to the STA; if the Unsolicited MFB field is 0 and the MRQ / UL EHT TB PPDU MFB field is 0, the second device can send first information back to the AP.

[0236] In some embodiments, the first link adaptation field may include a first field. For example, a separate first field may be set in the first link adaptation field to indicate first request information. Exemplarily, the first field may occupy one or more reserved bits in the first link adaptation field defined in related technologies.

[0237] In some embodiments, the first link adaptation field may include a second field. For example, the first link adaptation field may be configured with a separate second field to indicate the type of PPDU carrying the first information. Exemplarily, the second field may occupy one or more reserved bits in the first link adaptation field as defined in related technologies.

[0238] Figure 19 is a format example diagram of a ULA field provided in an embodiment of this application. As shown in Figure 19, the ULA field may include one or more of the following fields: Unrequested MFB, MRQ / UL EHT TB PPDU MFB, NSS, UHR MCS, RU allocation, PS160, BW, MSI / partial PPDU parameters, transmission beamforming, and reservation. The meanings of the RU allocation, PS160, BW, MSI / partial PPDU parameters, and transmission beamforming fields can be found in the corresponding field meanings in the ELA field.

[0239] The unrequested MFB and MRQ / UL EHT TB PPDU MFB together indicate the meaning of this A-Control field: If the unrequested MFB is 1 and the MRQ / UL EHT TB PPDU MFB is 1, it indicates unrequested modulation and coding feedback, including the STA's recommendations for parameters such as NSS and MCS to be used in subsequent PPDUs (e.g., UHR TB PPDU); if the unrequested MFB is 1 and the MRQ / UL EHT TB PPDU MFB is 0, it indicates unrequested modulation and coding feedback, including the STA's recommendations for parameters such as NSS and MCS to be used in subsequent PPDUs (e.g., UHR MU PPDU); if the unrequested MFB is 0 and the MRQ / UL EHT TB PPDU MFB is 1, it indicates that this ULA Control is a feedback field for modulation and coding requests; if the unrequested MFB is 0 and the MRQ / UL EHT TB PPDU MFB is 0, it indicates that this ULA Control is for modulation and coding requests.

[0240] In some embodiments, a first-format A-control field may be defined to indicate first information or first request information. The first-format A-control field may be a new A-control field defined in this application. The first-format A-control field may be used to indicate information related to a first type. Alternatively, the first-format A-control field may be associated with a first type. Alternatively, the first-format A-control field may be used to indicate information related to an ELR status.

[0241] In some embodiments, the A-control field of the first format may be referred to as the ELR status feedback (ESF) field.

[0242] The first format A-control field can be distinguished from A-control fields already defined in related technologies by the value of the control identifier field. For example, the value of the control identifier field of the first format A-control field is a second value, which indicates that the type of the A-control field is related to the first type (i.e., the first format A-control field defined in this application). The second value can, for example, be a reserved value of the control identifier field in related technologies. For example, the second value can be any value between 10 and 14. For example, the second value can be 10. The correspondence between the values ​​and meanings of the control identifier field can be shown in Table 7.

[0243] Table 7

[0244] In some embodiments, the A-control field of the first format may further include one or more of the spectrum field, power field, and MCS field.

[0245] The spectrum field can be used to indicate the available frequency domain location of a first type of PPDU. Optionally, the spectrum field can be indicated using a bitmap. For example, the bitmap can be P bits (P being a positive integer). Each bit can correspond to a first bandwidth, and the P bits correspond to a bandwidth range of the first bandwidth multiplied by P. The bitmap can represent the available spectrum within this bandwidth range, from low frequency to high frequency or from high frequency to low frequency, in units of the first bandwidth. A 1 in the bitmap indicates that the first bandwidth corresponding to the first bit is available for transmitting a first type of PPDU, and a 0 in the first bit indicates that the first bandwidth corresponding to the first bit is not available for transmitting a first type of PPDU. Alternatively, a 0 in the bitmap indicates that the first bandwidth corresponding to the first bit is available for transmitting a first type of PPDU, and a 1 in the first bit indicates that the first bandwidth corresponding to the first bit is not available for transmitting a first type of PPDU.

[0246] Let's take a first bandwidth of 20MHz and P=16 as an example. The bit diagram of the spectrum field can be 16 bits. 16 bits correspond to the available spectrum from low frequency to high frequency in 20MHz units within a 320MHz bandwidth range. Any bit set to 1 indicates that the corresponding 20MHz bandwidth can be used to transmit the first type of PPDU.

[0247] It should be noted that the spectrum field is merely an example name for this field. For example, the spectrum field could also be called the available channel bitmap field, etc.

[0248] The power field can be used to indicate the signal power received by the first device from the second device. The first device's transmit power field can help the second device determine the expected received signal power of different devices transmitting TB PPDUs in multi-user scheduling.

[0249] It should be noted that the power field is merely an example name for this field. For instance, the power field could also be called the received power field, etc.

[0250] The MCS field can be used to indicate the MCS of the recommended first type of PPDU. For example, an MCS value of 0 indicates that MCS0 is recommended, and a value of 1 indicates that MCS1 is recommended.

[0251] It should be noted that the MCS field is simply a name instance of the field. For example, the MCS field can also be called the UHR MCS field, etc.

[0252] In some embodiments, when the first device is in an ELR state, one or more of the spectrum field, power field, and MCS field included in the A-control field of the first format indicate valid information; when the first device is in a non-ELR state, one or more of the spectrum field, power field, and MCS field included in the A-control field of the first format can be reserved values.

[0253] Figure 20 is a format example diagram of an ESF field provided in an embodiment of this application.

[0254] As shown in Figure 20, the ESF field may include one or more of the following fields: Control Identifier, ELR Status, MCS, Available Channel Bitmap, Receive Power, and Reserved. Details of each field are provided above and will not be repeated here.

[0255] It should be noted that the first information was indicated above via the MAC layer. The first information can also be indicated in other ways. For example, the first device can indicate its first information via the physical layer, in addition to the trigger frame. For instance, the first device can send an ELR PPDU carrying any frame to the second device to indicate that it is in an ELR state, and send a non-ELR PPDU carrying any frame to the AP to indicate that it is in a non-ELR state.

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

[0257] Figure 21 is a schematic structural diagram of a communication device 2100 provided in an embodiment of this application. The communication device 2100 is a first device and includes a transmitting unit 2110.

[0258] The sending unit 2110 is used to send first information to the second device; wherein the first information is used to indicate whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

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

[0260] In an optional embodiment, the transmitting unit 2110 may be a transceiver 2330. The communication device 2100 may also include a processor 2310 and a memory 2320, as shown in FIG23.

[0261] Figure 22 is a schematic structural diagram of a communication device 2200 provided in an embodiment of this application. The communication device 2200 is a second device. The communication device 2200 includes a receiving unit.

[0262] The receiving unit 2200 is used to receive first information sent by the first device; wherein the first information is used to indicate whether the first device must send a first type of PPDU at a first moment, the first type of PPDU supporting enhanced long-distance transmission.

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

[0264] In an optional embodiment, the receiving unit 2210 may be a transceiver 2330. The communication device 2200 may also include a processor 2310 and a memory 2320, as shown in FIG23.

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

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

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

[0268] The device 2300 may also include a transceiver 2330. The processor 2310 can communicate with other devices or chips via the transceiver 2330. For example, the processor 2310 can send and receive data with other devices or chips via the transceiver 2330.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A wireless communication method, characterized in that, include: The first device sends the first information to the second device; The first information is used to indicate whether the first device must send a first type of physical layer protocol data unit (PPDU) at a first moment, and the first type of PPDU supports enhanced long-distance transmission.

2. The method according to claim 1, characterized in that, Also includes: The first device receives the first request information sent by the second device; The first request information is used to request the acquisition of first information from one or more first devices.

3. The method according to claim 2, characterized in that, The one or more first devices all indicate first information via the first type of PPDU.

4. The method according to claim 2, characterized in that, Some or all of the one or more first devices indicate first information via a second type of PPDU less than or equal to a first bandwidth threshold, where the first bandwidth threshold is a positive number.

5. The method according to claim 2 or 4, characterized in that, The first request information is used to trigger some or all of the one or more first devices to indicate the first information via a second type of PPDU greater than or equal to a second bandwidth threshold. The first information is determined by whether the second device receives the second type of PPDU.

6. The method according to any one of claims 2-5, characterized in that, The PPDU indicating the first information also includes a data frame.

7. The method according to any one of claims 2-6, characterized in that, The first request information is carried in a trigger frame, which is used to trigger the one or more first devices to send a PPDU indicating the first information to the second device.

8. The method according to claim 6, characterized in that, The first request information is carried in the public information field and / or user information field of the trigger frame.

9. The method according to claim 7 or 8, characterized in that, The trigger frame includes a trigger type field, the value of which is a first value, which indicates that the type of the trigger frame is related to the first type.

10. The method according to any one of claims 1-9, characterized in that, The first information is contained in the aggregation control A-control field.

11. The method according to claim 10, characterized in that, The first information is carried in the first link adaptive field.

12. The method according to claim 11, characterized in that, The first link adaptive field includes the modulation and coding scheme (MCS) field and / or the spatial stream number (NSS) field; The MCS field is used to indicate the MCS and the first information; or, The NSS field and the MCS field together indicate the MCS and the first information.

13. The method according to claim 10, characterized in that, The A-control field includes a control identifier field, the value of which is a second value, which indicates that the type of the A-control field is related to the first type.

14. The method according to claim 13, characterized in that, The A-control field further includes a spectrum field and / or a power field, wherein the spectrum field is used to indicate the available spectrum location for the first device to transmit a first type of PPDU, and the power field is used to indicate the signal power received by the first device from the second device.

15. The method according to any one of claims 1-14, characterized in that, Also includes: The first device receives the confirmation information sent by the second device; The confirmation information is used to confirm that the second device has received the first information.

16. The method according to any one of claims 1-15, characterized in that, The first device includes a non-AP STA (non-access point site), and the second device includes an access point (AP).

17. A wireless communication method, characterized in that, include: The second device receives the first information sent by the first device; The first information is used to indicate whether the first device must send a first type of physical layer protocol data unit (PPDU) at a first moment, and the first type of PPDU supports enhanced long-distance transmission.

18. The method according to claim 17, characterized in that, Also includes: The second device sends a first request message to the first device; The first request information is used to request the acquisition of first information from one or more first devices.

19. The method according to claim 18, characterized in that, The one or more first devices all indicate first information via the first type of PPDU.

20. The method according to claim 18, characterized in that, Some or all of the one or more first devices indicate first information via a second type of PPDU less than or equal to a first bandwidth threshold, where the first bandwidth threshold is a positive number.

21. The method according to claim 18 or 20, characterized in that, The first request information is used to trigger some or all of the one or more first devices to indicate the first information via a second type of PPDU greater than or equal to a second bandwidth threshold. The first information is determined by whether the second device receives the second type of PPDU.

22. The method according to any one of claims 18-21, characterized in that, The PPDU indicating the first information also includes a data frame.

23. The method according to any one of claims 18-22, characterized in that, The first request information is carried in a trigger frame, which is used to trigger the one or more first devices to send a PPDU indicating the first information to the second device.

24. The method according to claim 23, characterized in that, The first request information is carried in the public information field and / or user information field of the trigger frame.

25. The method according to claim 23 or 24, characterized in that, The trigger frame includes a trigger type field, the value of which is a first value, which indicates that the type of the trigger frame is related to the first type.

26. The method according to any one of claims 17-25, characterized in that, The first information is contained in the aggregation control A-control field.

27. The method according to claim 26, characterized in that, The first information is carried in the first link adaptive field.

28. The method according to claim 27, characterized in that, The first link adaptive field includes the modulation and coding scheme (MCS) field and / or the spatial stream number (NSS) field; The MCS field is used to indicate the MCS and the first information; or, The NSS field and the MCS field together indicate the MCS and the first information.

29. The method according to claim 26, characterized in that, The A-control field includes a control identifier field, the value of which is a second value, which indicates that the type of the A-control field is related to the first type.

30. The method according to claim 29, characterized in that, The A-control field further includes a spectrum field and / or a power field, wherein the spectrum field is used to indicate the available spectrum location for the first device to transmit a first type of PPDU, and the power field is used to indicate the signal power received by the first device from the second device.

31. The method according to any one of claims 17-30, characterized in that, Also includes: The second device sends a confirmation message to the first device; The confirmation information is used to confirm that the second device has received the first information.

32. The method according to any one of claims 17-31, characterized in that, The first device includes a non-AP STA (non-access point site), and the second device includes an access point (AP).

33. A communication device, characterized in that, The communication device is a first device, and the communication device includes: The sending unit is used to send first information to the second device; The first information is used to indicate whether the first device must send a first type of physical layer protocol data unit (PPDU) at a first moment, and the first type of PPDU supports enhanced long-distance transmission.

34. The communication device according to claim 33, characterized in that, Also used for: Receive the first request information sent by the second device; The first request information is used to request the acquisition of first information from one or more first devices.

35. The communication device according to claim 34, characterized in that, The one or more first devices all indicate first information via the first type of PPDU.

36. The communication device according to claim 34, characterized in that, Some or all of the one or more first devices indicate first information via a second type of PPDU less than or equal to a first bandwidth threshold, where the first bandwidth threshold is a positive number.

37. The communication device according to claim 34 or 36, characterized in that, The first request information is used to trigger some or all of the one or more first devices to indicate the first information via a second type of PPDU greater than or equal to a second bandwidth threshold. The first information is determined by whether the second device receives the second type of PPDU.

38. The communication device according to any one of claims 34-37, characterized in that, The PPDU indicating the first information also includes a data frame.

39. The communication device according to any one of claims 34-38, characterized in that, The first request information is carried in a trigger frame, which is used to trigger the one or more first devices to send a PPDU indicating the first information to the second device.

40. The communication device according to claim 39, characterized in that, The first request information is carried in the public information field and / or user information field of the trigger frame.

41. The communication device according to claim 39 or 40, characterized in that, The trigger frame includes a trigger type field, the value of which is a first value, which indicates that the type of the trigger frame is related to the first type.

42. The communication device according to any one of claims 33-41, characterized in that, The first information is contained in the aggregation control A-control field.

43. The communication device according to claim 42, characterized in that, The first information is carried in the first link adaptive field.

44. The communication device according to claim 43, characterized in that, The first link adaptive field includes the modulation and coding scheme (MCS) field and / or the spatial stream number (NSS) field; The MCS field is used to indicate the MCS and the first information; or, The NSS field and the MCS field together indicate the MCS and the first information.

45. The communication device according to claim 42, characterized in that, The A-control field includes a control identifier field, the value of which is a second value, which indicates that the type of the A-control field is related to the first type.

46. ​​The communication device according to claim 45, characterized in that, The A-control field further includes a spectrum field and / or a power field, wherein the spectrum field is used to indicate the available spectrum location for the first device to transmit a first type of PPDU, and the power field is used to indicate the signal power received by the first device from the second device.

47. The communication device according to any one of claims 33-46, characterized in that, Also used for: Receive confirmation information sent by the second device; The confirmation information is used to confirm that the second device has received the first information.

48. The communication device according to any one of claims 33-47, characterized in that, The first device includes a non-AP STA (non-access point site), and the second device includes an access point (AP).

49. A communication device, characterized in that, The communication device is a second device, and the communication device includes: The receiving unit is used to receive the first information sent by the first device; The first information is used to indicate whether the first device must send a first type of physical layer protocol data unit (PPDU) at a first moment, and the first type of PPDU supports enhanced long-distance transmission.

50. The communication device according to claim 49, characterized in that, Also used for: Send a first request message to the first device; The first request information is used to request the acquisition of first information from one or more first devices.

51. The communication device according to claim 50, characterized in that, The one or more first devices all indicate first information via the first type of PPDU.

52. The communication device according to claim 50, characterized in that, Some or all of the one or more first devices indicate first information via a second type of PPDU less than or equal to a first bandwidth threshold, where the first bandwidth threshold is a positive number.

53. The communication device according to claim 50 or 52, characterized in that, The first request information is used to trigger some or all of the one or more first devices to indicate the first information via a second type of PPDU greater than or equal to a second bandwidth threshold. The first information is determined by whether the second device receives the second type of PPDU.

54. The communication device according to any one of claims 50-53, characterized in that, The PPDU indicating the first information also includes a data frame.

55. The communication device according to any one of claims 50-54, characterized in that, The first request information is carried in a trigger frame, which is used to trigger the one or more first devices to send a PPDU indicating the first information to the second device.

56. The communication device according to claim 55, characterized in that, The first request information is carried in the public information field and / or user information field of the trigger frame.

57. The communication device according to claim 55 or 56, characterized in that, The trigger frame includes a trigger type field, the value of which is a first value, which indicates that the type of the trigger frame is related to the first type.

58. The communication device according to any one of claims 49-57, characterized in that, The first information is contained in the aggregation control A-control field.

59. The communication device according to claim 58, characterized in that, The first information is carried in the first link adaptive field.

60. The communication device according to claim 59, characterized in that, The first link adaptive field includes the modulation and coding scheme (MCS) field and / or the spatial stream number (NSS) field; The MCS field is used to indicate the MCS and the first information; or, The NSS field and the MCS field together indicate the MCS and the first information.

61. The communication device according to claim 58, characterized in that, The A-control field includes a control identifier field, the value of which is a second value, which indicates that the type of the A-control field is related to the first type.

62. The communication device according to claim 61, characterized in that, The A-control field further includes a spectrum field and / or a power field, wherein the spectrum field is used to indicate the available spectrum location for the first device to transmit a first type of PPDU, and the power field is used to indicate the signal power received by the first device from the second device.

63. The communication device according to any one of claims 49-62, characterized in that, Also used for: Send confirmation information to the first device; The confirmation information is used to confirm that the second device has received the first information.

64. The communication device according to any one of claims 49-63, characterized in that, The first device includes a non-AP STA (non-access point site), and the second device includes an access point (AP).

65. A communication device, characterized in that, The device 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 transmit signals so that the communication device performs the method as described in any one of claims 1-32.

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

67. 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-32.

68. 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-32.

69. 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-32.

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

Images