Wireless communication method and communication device

By carrying multiple feedback information in the wireless communication frame, the problems of low accuracy and efficiency in the transmission process in the prior art are solved, dynamic unavailability operation and link adaptation are optimized, and a more efficient communication process is achieved.

WO2026232335A1PCT designated stage Publication Date: 2026-11-12GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/093205
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication frames lack an effective feedback mechanism during transmission, resulting in low accuracy and efficiency, especially in dynamic unavailability operations and link adaptation, where there is room for improvement.

Method used

By carrying unavailable feedback information, internal error feedback information, transmission parameter feedback information, OBSS feedback information, buffer status feedback information, and power mode feedback information in the frame, the frequency of information feedback between devices is increased and signaling overhead is reduced, thus optimizing the subsequent transmission process.

Benefits of technology

It improves the accuracy and efficiency of wireless communication, especially in dynamic unavailability operation and link adaptation, and reduces signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025093205_12112026_PF_FP_ABST
    Figure CN2025093205_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a wireless communication method and a communication device. The method comprises: a first device sending a first frame to a second device, wherein the first frame carries first information, and the first information comprises one or more of the following: unavailability feedback information; internal-error feedback information; transmission parameter feedback information; OBSS feedback information; buffer state feedback information; power mode feedback information; and restricted-operation feedback information. Subsequent frame exchange between a first device and a second device can be guided by means of first information, such that the accuracy and efficiency of a subsequent transmission process are higher. For example, a TXOP holder can acquire multiple state parameters of a TXOP responder on the basis of a first frame, thereby not only improving the frequency of information feedback, but also reducing signaling overheads.
Need to check novelty before this filing date? Find Prior Art

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 communication device. Background Technology

[0002] Related technologies have proposed several frames. For example, data frames can be used to transmit data; control frames can be used to manage wireless communication processes, such as channel access and acknowledgment; and trigger frames can be used to schedule and synchronize user transmissions. Exemplarily, a block acknowledge (BA) frame is a control frame used to perform batch acknowledgment of medium access control service data units (MSDUs). The inventors of this application have found that some frames have room for improvement. Summary of the Invention

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

[0004] In a first aspect, a communication method is provided. The method includes: a first device sending a first frame to a second device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; overlapping basic service set (OBSS) feedback information; buffer status feedback information; power mode feedback information; and restricted operation feedback information.

[0005] Secondly, a wireless communication method is provided. The method includes: a second device receiving a first frame transmitted by a first device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; OBSS feedback information; buffer status feedback information; power mode feedback information; and restricted operation feedback information.

[0006] Thirdly, a communication device is provided, which is a first device, comprising: a transmitting unit for transmitting a first frame to a second device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; OBSS feedback information; buffer status feedback information; power mode feedback information; and restricted operation feedback information.

[0007] Fourthly, a communication device is provided, which is a second device. The communication device includes: a receiving unit for receiving a first frame sent by a first device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; OBSS feedback information; buffer status feedback information; power mode feedback information; and restricted operation feedback information.

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

[0009] 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.

[0010] 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.

[0011] 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.

[0012] 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.

[0013] The first frame provides information that guides subsequent frame exchanges between the first and second devices, improving the accuracy and efficiency of subsequent transmissions. For example, based on the first frame, the transmission opportunity (TXOP) holder can obtain various status parameters of the TXOP responder, increasing the frequency of information feedback and reducing signaling overhead. Attached Figure Description

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

[0015] Figure 2 is a sample format diagram of the traffic identifier (TID) information (Per AID TID Info) subfield for each association identifier (AID).

[0016] Figure 3 is an example of another format for the Per AID TID Info subfield.

[0017] Figure 4 is an example of the format of a feedback field.

[0018] Figure 5 is an example diagram of a communication process.

[0019] Figure 6 is an example of another format for the Per AID TID Info subfield.

[0020] Figure 7 shows an example format of a user information feedback field.

[0021] Figure 8 is an example of the format of a feedback information field.

[0022] Figure 9 is an example of the format of an ELA control subfield.

[0023] Figure 10 is an example of the format of a subfield of an MCS request sequence identifier (MSI) / partial PPDU parameters.

[0024] Figure 11 is an example diagram of a BA frame format.

[0025] Figure 12 is a sample format diagram of the BA control field.

[0026] Figure 13 is an example of the format of the BA information field in a compressed BA frame.

[0027] Figure 14 is a sample diagram of the format of the BA information field in an M-BA frame.

[0028] Figure 15A is an example of another format for the Per AID TID Info subfield.

[0029] Figure 15B is an example of another format for the Per AID TID Info subfield.

[0030] Figure 15C is an example diagram of the format of the AID TID Info field.

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

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

[0033] Figure 17B is an example of a format for a control subfield.

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

[0035] Figure 19A is an example diagram of a trigger frame format provided in an embodiment of this application.

[0036] Figure 19B is a sample format diagram of the feedback information field.

[0037] Figures 20A to 20G are example diagrams of the format of a multi-STA block acknowledge (M-BA) frame provided in the embodiments of this application.

[0038] Figure 21A is a format example diagram of a first frame provided in an embodiment of this application.

[0039] Figure 21B is an example of the format of the ultra-high reliability (UHR) link feedback (ULFB) information field.

[0040] Figure 22 is an example diagram of a communication process provided in an embodiment of this application.

[0041] Figure 23 is an example diagram of another communication process provided in an embodiment of this application.

[0042] Figure 24 is an example diagram of another communication process provided in an embodiment of this application.

[0043] Figure 25 is an example diagram of the format of a second frame provided in an embodiment of this application.

[0044] Figure 26 is an example diagram of another trigger frame format provided in an embodiment of this application.

[0045] Figure 27 is an example diagram of another second frame format provided in an embodiment of this application.

[0046] Figure 28 is an example diagram of another second frame format provided in an embodiment of this application.

[0047] Figure 29 is an example diagram of the communication process provided in Example 1.

[0048] Figure 30 is an example diagram of the communication process provided in Embodiment 2.

[0049] Figure 31 is an example diagram of the communication process provided in Embodiment 3.

[0050] Figure 32 is a schematic structural diagram of a communication device 3200 provided in an embodiment of this application.

[0051] Figure 33 is a schematic structural diagram of a communication device 3300 provided in an embodiment of this application.

[0052] Figure 34 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. Detailed Implementation

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

[0054] Communication system

[0055] 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).

[0056] 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.

[0057] 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.

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

[0059] 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.

[0060] 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.

[0061] 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.

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

[0063] 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.).

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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).

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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).

[0075] 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.

[0076] Dynamic unavailability operation (DUO)

[0077] The related technology achieves the feedback of DUO information by modifying the M-BA frame.

[0078] The AID11 subfield carries the 11 least significant bits (LSBs) of the AID of the non-AP STA, which is associated with the Per AID TID Info subfield. The format of the Per AID TID Info subfield depends on the value of the AID11 subfield. If a multi-site BA frame is sent to an AP (Access Point), the AID11 subfield is set to 0. A value of 2045 in the AID11 subfield is used as an identifier for any unassociated STA. If the AID11 subfield is set to 2045, the Ack Type subfield and the Transport Identifier (TID) subfield are set to 0 and 15, respectively. The value 2008 in the AID11 subfield identifies a Per AID TID Info field that carries feedback applicable to all receiving UHR STAs. This feedback is related to the DUO mode.

[0079] If the value of the AID11 subfield in the AID TID Info subfield is not 2045, and if the combination of the Ack Type subfield and the TID subfield is not equal to 0 and 13, then the format of the Per AID TID Info subfield is as shown in Figure 2. As shown in Figure 2, the Per AID TID Info subfield includes the following fields: AID TID Info, block Ack starting sequence control, and block Ack bitmap.

[0080] If the value of the AID11 subfield in the AID TID Info subfield is not 2045, and if the Ack Type subfield is equal to 0 and the TID subfield is equal to 13, then the format of the Per AID TID Info subfield is as shown in Figure 3. As shown in Figure 3, the Per AID TID Info subfield includes the following fields: AID TID Info, Block Acknowledgment Start Sequence Control, and Feedback.

[0081] If the Ack Type subfield of a Per AID TID Info field is equal to 0 and the TID subfield is equal to 13, then the Per AID TID Info field can satisfy the following three conditions.

[0082] 1. It contains feedback information, not confirmation status (see Related Techniques: What is the content of the Per AID TID Info subfield if the value of the AID11 subfield is not 2045, and the existence of optional subfields).

[0083] 2. The AID11 subfield in the AID TID Info subfield is set to the AID of the UHR STA receiving the feedback information, or 2008 if the feedback information is for all receiving UHR STAs.

[0084] 3. The Per AID TID Info field includes a feedback subfield instead of the block acknowledgment bitmap subfield. The feedback subfield contains feedback information, not the acknowledgment status. The format of the feedback subfield is shown in Figure 4. The unavailability target start time subfield indicates the TSF[15:7] value when the STA (the station sending multi-STA BA frames) becomes unavailable. The unavailability duration subfield indicates the length of time the STA is unavailable during the transmission of multi-STA block acknowledgment frames, in 64 microseconds.

[0085] In some scenarios, the unavailability period of a STA may overlap with certain PPDUs, leading to errors. As shown in Figure 5, the unavailability period overlaps with a portion of the duration in the DL PPDU. In this case, it would be very useful if the STA could indicate to the AP that these errors are caused by internal factors. As shown in Figure 5, an M-BA frame can indicate that the error is caused by an internal factor.

[0086] M-BA frames can be used to transmit control feedback information, which can be carried in the block acknowledgment bit diagram in the Per AID TID Info field.

[0087] Since there are many types of feedback information that need to be reported, a "feedback type" field can be included in the Per AID TID Info field to indicate the type of control information contained in that field.

[0088] Figure 6 is a format example diagram of a Per AID TID Info field provided in an embodiment of this application.

[0089] As shown in Figure 6, the length of the feedback type field can be set to 4 bits. The feedback type field can be included in the last four bits of the block acknowledgment start sequence control field, i.e., B12 to B15. The rest of the "starting sequence number" field can be reserved.

[0090] For example, a value of 0 in the "Feedback Type" field can indicate that the control information carried in the block acknowledgment bit map is DUO unavailability information, namely the unavailability target start time and unavailability duration shown in Figure 6.

[0091] In some embodiments, the DUO's feedback information can be carried in a trigger frame. The trigger frame may include a feedback user information field. This feedback user information field is a user information field that does not carry specific user information, but rather carries general feedback information.

[0092] The feedback user information field is identified by an AID12 value of 2008 and may optionally appear in a buffer status report poll (BSRP) trigger frame or a BSRP GI3 trigger frame generated by the UHR STA.

[0093] It should be noted that UHR AP will not use the value 2008 as the AID of any STA associated with it.

[0094] Figure 7 shows an example format of a user information feedback field.

[0095] If the "Feedback Type" field is set to 0, it indicates that the feedback field is unavailable. Figure 8 shows an example format of a feedback field.

[0096] Link adaptation

[0097] Link adaptation technology can optimize the performance of wireless communication links by dynamically adjusting the modulation and coding scheme (MCS), the number of spatial streams (NSS), and other parameters. The following section uses EHT Link Adaptation (ELA) as an example to introduce some fields related to link adaptation.

[0098] The control information subfield in the ELA control subfield contains information related to the ELA process. Figure 9 shows an example of the format of the ELA control subfield. The following is a description of each field in the ELA control subfield.

[0099] The Unsolicited MFB field is used to indicate an unsolicited MFB. It is set to 1 if the ELA control subfield is an unsolicited MFB. It is set to 0 if the ELA control subfield is a Modulation and Coding Scheme Request (MRQ) or a requested MFB.

[0100] The MRQ / UL EHT TB PPDU MFB field is used to indicate an ELA feedback request / indicate a UL EHT TB PPDU MFB. Setting it to 1 and the unsolicited MFB subfield to 0 indicates a request for ELA feedback. Setting it to 0 and the unsolicited MFB subfield to 0 indicates a response to an ELA request. If the unsolicited MFB subfield is equal to 1, a value of 1 in this subfield indicates that the NSS, EHT-MCS, BW, PS160, and RU Allocation subfields represent the suggested MFB for a subsequent EHT TB PPDU sent by the STA that issued this recommendation. If the unsolicited MFB subfield is 1 and the MRQ / UL EHT TB PPDU MFB is equal to 0, the NSS, EHT-MCS, PS160, RU Allocation, and BW subfields represent the suggested values ​​for a subsequent EHT MU PPDU sent to the STA that issued this recommendation.

[0101] The NSS field is used to indicate the suggested number of space streams. If the unsolicited MFB subfield is equal to 1 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 0, or if the unsolicited MFB subfield is equal to 0 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 0, the NSS subfield indicates the suggested number of space streams (NSS) sent to the STA that issued this suggestion for subsequent EHT MU PPDUs, and is set to NSS–1. If the unsolicited MFB subfield is equal to 1 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 1, the NSS subfield indicates the suggested number of space streams (NSS) sent by the STA that sent this suggestion for subsequent EHT TB PPDUs, and is set to NSS–1. Otherwise, this subfield is reserved.

[0102] The EHT-MCS field is used to indicate the proposed EHT-MCS. If the unsolicited MFB subfield is equal to 1 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 0, or if the unsolicited MFB subfield is equal to 0 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 0, then the EHT-MCS subfield indicates the proposed EHT-MCS for subsequent EHT MU PPDUs sent to the STA that issued this proposal, and is set to the EHT-MCS index. If the unsolicited MFB subfield is equal to 1 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 1, then the EHT-MCS subfield indicates the recommended EHT-MCS for the EHT TB PPDU sent from the STA, and is set to the EHT-MCS index. Otherwise, this subfield is reserved.

[0103] For the PS160 field, if the size of the RU or MRU is less than or equal to 2 × 996 subcarriers, it indicates the primary or secondary 160MHz channel to which the RU or MRU allocation applies. Otherwise, the PS160 subfield is used together with the RU Allocation subfield to indicate the RU or MRU index. If the unsolicited MFB subfield is equal to 1, or the unsolicited MFB subfield is equal to 0 and the MRQ / ULEHT TB PPDU MFB subfield is equal to 1, the PS160 subfield is set to 0 to indicate the primary 160MHz channel and set to 1 to indicate the secondary 160MHz channel (for RU or MRU sizes less than or equal to 2 × 996 subcarriers); for RU or MRU sizes greater than 2 × 996 subcarriers, the PS160 subfield is used together with the RU Allocation subfield to indicate the RU or MRU index. Otherwise, this subfield is reserved.

[0104] The RU allocation field associates the RU or MRU with the proposed EHT-MCS / RU or MRU for which the MFB requester has requested feedback. If the unsolicited MFB subfield equals 1 and the MRQ / UL EHT TB PPDU MFB subfield equals 0, then the RU Allocation subfield and PS160 together indicate the RU or MRU of the applicable proposed EHT-MCS, as defined in 35.19 (EHT Link Adaptation with ELA Control Subfield). If the unsolicited MFB subfield equals 0 and the MRQ / UL EHT TB PPDU MFB subfield equals 1, then the RU Allocation subfield and PS160 together indicate the RU or MRU for which the MFB requester has requested feedback. If the unsolicited MFB subfield is equal to 1, and the MRQ / UL EHT TB PPDU MFB subfield is equal to 1, then the RU Allocation subfield and PS160 together indicate the RU or MRU to which the proposed EHT-MCS applies, as defined in 35.19 (EHT Link Adaptation using ELA Control Subfields). The RU Allocation subfield and PS160 subfield are interpreted together with the BW subfield to specify the RU or MRU. The RU or MRU index encoding is defined in Table 9-461 (Encoding of PS160 and RU Allocation Subfields in EHT Variant User Information Fields). Otherwise, this subfield is reserved.

[0105] The BW field relates to the bandwidth requested by the EHTMCS / MFB requester for feedback. If the unrequested MFB subfield is equal to 1, the BW subfield indicates the bandwidth applicable to the proposed EHT-MCS, as defined in 35.19 (EHT Link Adaptation with ELA Control Subfield). If the unrequested MFB subfield is equal to 0 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 1, the BW subfield indicates the PPDU bandwidth requested by the MFB requester: 20MHz set to 0, 40MHz set to 1, 80MHz set to 2, 160MHz set to 3, and 320MHz set to 4. Values ​​5, 6, and 7 are reserved. Otherwise, this subfield is reserved.

[0106] MSI / Partial PPDU Parameters: Partial parameters of the PPDU / MRQ sequence identifier under test. If the unsolicited MFB subfield is equal to 0 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 1, the MSI / Partial PPDU Parameters subfield contains a sequence number in the range of 0 to 6 to identify a specific EHT-MCS feedback request. If the unsolicited MFB subfield is equal to 0 and the MRQ / UL EHT TB PPDU MFB subfield is equal to 0, the MSI / Partial PPDU Parameters subfield contains a sequence number in the range of 0 to 6 to respond to a specific solicited EHT-MCS feedback request. If the unsolicited MFB subfield is equal to 1, the MSI / Partial PPDU Parameters subfield contains PPDU format and coding type subfields, as shown in Figure 10.

[0107] The PPDU format subfield indicates the format of the PPDU for estimating the unsolicited MFB. Set to 0 for EHT MU PPDU and 1 for EHT TB PPDU.

[0108] The encoding type subfield contains encoding information used to estimate the PPDU of the unsolicited MFB. For BCC, set to 0. For LDPC, set to 1.

[0109] The Transmit Beamforming (Tx beamforming) field indicates the transmission type of the PPDU under test. If the Unrequested MFB subfield is equal to 1 and the MRQ / UL HE TB PPDU MFB subfield is equal to 0, then the Tx Beamforming subfield indicates whether the PPDU with the estimated Unrequested MFB is beamformed. For non-beamformed PPDUs, set to 0. For beamformed PPDUs, set to 1. Otherwise, this subfield is reserved.

[0110] The HLA / ELA field is used to indicate HE / EHT link adaptation. If the control information subfield is an ELA control subfield, it is set to 1. If the control information subfield is an HLA control subfield, it is set to 0.

[0111] The M-BA frame described above is a variant of the BA frame. The following provides an example of a BA frame.

[0112] BA frame

[0113] The BA frame is a control frame used to perform batch acknowledgments of the MSDU.

[0114] Figure 11 is a sample diagram of the BA frame format.

[0115] The frame control field is used to carry control information such as frame type.

[0116] The duration field indicates the remaining TXOP duration.

[0117] The receiver address (RA) is used to indicate the MAC address of the site receiving the BA frame.

[0118] The transmission address (TA) is used to indicate the MAC address of the site that sent the BA frame.

[0119] Figure 12 is a sample format diagram of the BA control field. The following is an explanation of each field in the BA control field.

[0120] The BA type field indicates a variant of the BA frame. The correspondence between the values ​​of the BA type field and the variants is shown in Table 1. Specifically, see Table x.

[0121] Table 1

[0122] An EDMG STA can set the No Memory Kept subfield to 1 to indicate that the free memory space indicated in the last RBUFCAP subfield may not be reserved at the beginning of the next frame exchange sequence; otherwise, if set to 0, the receiver reserves the free memory space indicated by the RBUFCAP subfield for the next frame exchange sequence of the corresponding TID. If transmitted by a non-EDMG STA, the No Memory Kept subfield is reserved.

[0123] For EDMG STAs, the Memory Configuration Tag subfield indicates one of the two memory configurations indicated by the Memory Configuration Tag field in the receiver's EDMG flow control extended configuration element. This subfield is reserved for other STA types.

[0124] The Management Ack subfield is set to 1, indicating that frames whose management type and subtype are not Action No Ack are acknowledged. This subfield is retained if the BA variant used is not the EDMG Multi-TID BlockAck variant.

[0125] The meaning of the TID_INFO subfield of the BA control field depends on the BA frame variant type.

[0126] The meaning of the BA Information field depends on the BA frame variant type.

[0127] The following explanation uses the compressed BA variant and the M-BA variant as examples.

[0128] The TID_INFO subfield of the BA control field of a compressed BA frame contains the TID that sent this BA frame.

[0129] Figure 13 is a sample format diagram of the BA information fields in a compressed BA frame. The following is a description of each field.

[0130] The Block Ack Starting Sequence Control field indicates the sequence number of the first MSDU or A-MSDU acknowledged in this BA frame.

[0131] Each bit in the Block Ack Bitmap field indicates whether the corresponding MSDU or A-MSDU was successfully received; a value of 1 indicates success, and a value of 0 indicates failure.

[0132] The TID_INFO subfield of the BA control field in the M-BA frame is preserved.

[0133] The BA information field of an M-BA frame contains one or more Per AID TID Info subfields. Figure 14 is an example of the format of the BA information field of an M-BA frame. As shown in Figure 14, the Per AID TID Info subfield is for each<AID,TID> For repeated (Repeated for each)<AID,TID> tuple).

[0134] Figure 15A is an example of the format of the Per AID TID Info field when the AID TID Info subfield is not 2045.

[0135] Figure 15B is an example of the format of the Per AID TID Info field when the AID TID Info subfield equals 2045.

[0136] Figure 15C is an example diagram of the format of the AID TID Info field.

[0137] A-control field

[0138] 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.

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

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

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

[0142] Table 2

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

[0144] A control list field can contain one or more control subfields. Figure 17B shows an example format of a control subfield. As shown in Figure 17B, 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 a specific A-control subfield. Table 3 illustrates the possible values ​​and meanings of the control ID subfield.

[0145] Table 3

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

[0147] The method shown in Figure 18 can be performed 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 includes a non-AP STA, and the second device includes an AP. Alternatively, the first device may include an AP, and the second device may include a non-AP STA.

[0148] The method shown in Figure 18 may include step S1810.

[0149] S1810, the first device sends the first frame to the second device.

[0150] The first frame may carry first information. The first information may include one or more of the following: unavailability feedback (UFB); internal error feedback; transmission parameter feedback; OBSS feedback (OFB); buffer status feedback (BFB); power mode feedback; and restricted operation feedback.

[0151] Alternatively, the first information can also be called feedback information.

[0152] The first frame provides information that guides subsequent frame exchanges between the first and second devices, improving the accuracy and efficiency of subsequent transmissions. For example, based on the first frame, the TXOP owner can obtain various status parameters of the TXOP responder, increasing the frequency of information feedback and reducing signaling overhead.

[0153] The following is a detailed explanation of each piece of information contained in the first piece of information.

[0154] Unavailability feedback information can be used to indicate the unavailability of the first device. This unavailability can include DUO-related information. In other words, unavailability feedback information can be used to indicate information related to the DUO.

[0155] In some embodiments, the unavailability period of the first device is a first time period. The first time period may also be referred to as an unavailability period. Unavailability feedback information may include information related to the first time period. For example, unavailability feedback information may include one or more of the following: the start time of the first time period; the end time of the first time period; the duration of the first time period; the transmission error being caused by an internal error of the first device; the first time period being earlier or later than the transmission time of the first frame.

[0156] The start time of the first time period can be carried by the unavailability period start time field. The unavailability period start time field can indicate the TSF[15:7] value of the start time of the first time period. The unit of the unavailability period start time field can be 64μs.

[0157] The end time of the first time period can be carried by the unavailability period end time field. The unavailability period end time field can indicate the TSF[15:7] value of the end time of the first time period. The unit of the unavailability period end time field can be 64μs.

[0158] The duration of the first time period can be conveyed through the unavailability period duration field. The unit for the unavailability period duration field can be 64 μs.

[0159] It is understandable that the first time period can be determined by at least two of the following: the start time, the end time, and the duration.

[0160] Transmission errors can include transmission errors of MSDU or A-MSDU. For example, a transmission error can include a transmission error of MSDU or A-MSDU indicated in the block acknowledgment bitmap field of part or all of the Per AID TID Info field in the M-BA frame. If the transmission error is caused by an internal error of the first device, then the transmission error is not caused by deterioration of channel conditions.

[0161] The "error occurred" field indicates whether the transmission error was caused by an internal error in the first device. The "error occurred" field can occupy 1 bit, for example. A first value in the "error occurred" field indicates that the transmission error was caused by an internal error in the first device. A second value in the "error occurred" field indicates that the transmission error was not caused by an internal error in the first device.

[0162] In this application, the first value and the second value can be different values. For example, the first value can be 1 and the second value can be 0. Or, the first value can be 0 and the second value can be 1.

[0163] For example, a value of 1 in the error occurrence field indicates that the transmission error was caused by an internal error of the first device, and a value of 0 indicates that the transmission error was not caused by an internal error of the first device. Alternatively, a value of 0 in the error occurrence field indicates that the transmission error was caused by an internal error of the first device, and a value of 1 indicates that the transmission error was not caused by an internal error of the first device.

[0164] The first time period that is earlier than the first frame transmission time may include one or more of the following: the start time of the first time period is earlier than the transmission time of the first frame, and the end time of the first time period is earlier than the transmission time of the first frame.

[0165] The first time period that is later than the first frame transmission time may include one or more of the following: the start time of the first time period is later than the transmission time of the first frame, and the end time of the first time period is later than the transmission time of the first frame.

[0166] The first field can indicate whether the first time period is earlier or later than the transmission time of the first frame. For example, the first field can indicate whether the time range (i.e., the range of the first time period) jointly indicated by the unavailable time period start time field and the unavailable time period duration field is earlier or later than the transmission time of the first frame in which the first field is located. For instance, a first value for the first field can indicate that the first time period is earlier than the transmission time of the first frame; a second value for the first field can indicate that the first time period is later than the transmission time of the first frame.

[0167] For example, the first value can be 1 and the second value can be 0. That is, a value of 1 in the first field can indicate that the first time period is earlier than the transmission time of the first frame; a value of 0 in the first field can indicate that the first time period is later than the transmission time of the first frame.

[0168] This application does not limit the name of the first field. For example, the first field can also be called the error occurrence field. In conjunction with the embodiments described above, the error occurrence field can indicate whether the first time period is earlier or later than the transmission time of the first frame, or the error occurrence field can indicate whether the transmission error is caused by an internal error of the first device.

[0169] Therefore, it can be seen that the transmission error is caused by an internal error of the first device, and the relevant information can be indicated by the unavailable feedback information. That is, the information on whether the transmission error is caused by an internal error of the first device can be indicated by the same type of feedback information (i.e., unavailable feedback information) as the unavailable information.

[0170] In some embodiments, internal feedback information is used to indicate that the transmission error is caused by an internal error of the first device. In this embodiment, information regarding whether the transmission error is caused by an internal error of the first device can be reported separately, i.e., it can be indicated in different types of feedback information along with unavailability information.

[0171] Alternatively, internal error feedback information can also be referred to as error feedback (EFB) information.

[0172] In some embodiments, the transmission parameter feedback information is used to indicate one or more of the following: the transmission parameter feedback information is used to suggest transmission parameters for a PPDU sent by a first device after the first frame; the transmission parameter feedback information is used to suggest transmission parameters for a PPDU sent by a second device after the first frame; and the value of the transmission parameter.

[0173] For example, the TB PPDU MFB field can be used to indicate: transmission parameter feedback information used to suggest transmission parameters for a PPDU sent by a first device after the first frame; or, transmission parameter feedback information used to suggest transmission parameters for a PPDU sent by a second device after the first frame. For instance, a first value for the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for a PPDU sent by a first device after the first frame; a second value for the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for a PPDU sent by a second device after the first frame.

[0174] For example, a value of 1 in the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for PPDUs sent by the first device after the first frame; a value of 0 in the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for PPDUs sent by the second device after the first frame. Alternatively, a value of 0 in the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for PPDUs sent by the first device after the first frame; a value of 1 in the TB PPDU MFB field can indicate that transmission parameter feedback information is used to suggest transmission parameters for PPDUs sent by the second device after the first frame.

[0175] Optionally, the transmission parameter feedback information can be referred to as MCS feedback (MFB) information.

[0176] In some embodiments, the transmission parameters include one or more of the following: MCS, NSS, RU size, RU location, bandwidth, transmit beamforming, PPDU format, coding type, RU type, interference cancellation pilot type, and modulation mode corresponding to multiple spatial streams. That is, the transmission parameter feedback information can indicate or suggest values ​​for one or more of the above transmission parameters. These will be explained below.

[0177] The UHR-MCS field can be used to indicate the proposed MCS. The MCS may include the modulation scheme and / or code rate. Table 4 shows examples of values ​​for the UHR-MCS field.

[0178] Table 4

[0179] It should be noted that Table 4 is for illustrative purposes only. Some parts of Table 4 can be implemented independently. Some parts of Table 4 can be deleted.

[0180] The NSS field can be used to indicate the suggested NSS. The value of the NSS field can be one less than the indicated number of space streams.

[0181] The RU allocation field can be used to indicate the size and / or location of the proposed RU.

[0182] The BW field can be used to indicate the suggested bandwidth (i.e., the bandwidth of the PPDU). Table 5 shows an example of a BW field value.

[0183] Table 5

[0184] It should be noted that Table 5 is for illustrative purposes only. Some parts of Table 5 can be implemented independently. Some parts of Table 5 can be deleted.

[0185] The Transmit Beamforming (Tx) field indicates whether transmit beamforming is recommended. For example, a first value indicates that transmit beamforming is recommended, while a second value indicates that transmit beamforming is not recommended.

[0186] For example, a value of 1 for the transmit beamforming field indicates that transmit beamforming is recommended, while a value of 0 indicates that transmit beamforming is not recommended. Alternatively, a value of 0 for the transmit beamforming field indicates that transmit beamforming is recommended, while a value of 1 indicates that transmit beamforming is not recommended.

[0187] The PPDU format can include, for example, the type of PPDU. PPDU formats can include, for example, UHR MU PPDU, UHR ER PPDU.

[0188] The PPDU format field can be used to indicate the PPDU format. For example, a PPDU format value of 0 can represent UHR MU PPDU, and a PPDU format value of 1 can represent UHR ER PPDU; other values ​​for the PPDU format can be reserved. For instance, a PPDU format value of 0 can represent UHR MU PPDU, a PPDU format value of 1 can represent UHR ER PPDU, and other values ​​can be reserved.

[0189] The coding type field can be used to indicate the recommended coding type. Channel coding methods can include one or more of the following: BCC coding, LDPC coding.

[0190] For example, a first value for the encoding type can represent BCC encoding. A second value for the encoding type can represent LDPC encoding. Other values ​​for this field can be reserved. For instance, an encoding type value of 0 can represent BCC encoding, an encoding type value of 1 can represent LDPC encoding, and other values ​​can be reserved.

[0191] RU types can include regular RU (RRU) and / or distributed RU (DRU).

[0192] The RU type field can be used to indicate the RU type. For example, a first value for the RU type field indicates an RRU. A second value for the RU type field indicates a DRU. For instance, a value of 0 for the RU type field indicates an RRU; a value of 1 for the RU type field indicates a DRU.

[0193] The types of interference cancellation pilots can include one or more of the following: no interference cancellation pilot, conventional interference cancellation pilot, and interference cancellation pilot without energy.

[0194] The interference management pilot (IM pilot) field can be used to indicate the type of interference management pilot. For example, an IM pilot value of the third value indicates that there is no interference management pilot; an IM pilot value of the fourth value indicates a regular interference management pilot; an IM pilot value of the fifth value indicates an interference management pilot without energy; other values ​​can be reserved.

[0195] In this application, the third, fourth, and fifth values ​​are different values. For example, the third value is 0, the fourth value is 1, and the fifth value is 2. Or, the third value is 1, the fourth value is 2, and the fifth value is 0.

[0196] For example, a value of 0 for IM pilot indicates that no interference cancellation pilot is included; a value of 1 for IM pilot indicates a regular interference cancellation pilot; a value of 3 for IM pilot indicates an interference cancellation pilot without energy; other values ​​are reserved.

[0197] The modulation modes corresponding to multiple spatial streams can indicate the individual modulation schemes of each spatial stream. The modulation schemes of the multiple spatial streams can be different.

[0198] The modulation patterns of multiple spatial streams can be indicated by the modulation pattern field. Table 6 provides an example of the values ​​for the NSS and modulation pattern fields. In Table 6, 's' represents the value of the MCS field.

[0199] Table 6

[0200] It should be noted that Table 6 is for illustrative purposes only. Some parts of Table 6 can be implemented independently. Some parts of Table 6 can be deleted.

[0201] In some embodiments, OBSS feedback information is used to indicate OBSS information for one or more links. For example, OBSS feedback information may be used to indicate one or more of the following: the identifier of one or more links corresponding to the OBSS feedback information; the number of one or more links; and NAV information for one or more links.

[0202] The identifier of one or more links corresponding to OBSS feedback information can be represented by a first bit map. The first bit map may include one or more bits. One or more bits may include the first bit. The first bit may correspond to a first link. For example, the first bit may be bit i, and the first link may be the link with link identifier i. A first value for the first bit indicates that OBSS information for the first link is being fed back; a second value for the first bit indicates that OBSS information for the first link is not being fed back.

[0203] For example, in the first bit diagram, a value of 1 for bit i indicates that OBSS information of link i is being fed back, while a value of 0 indicates that OBSS information of link i is not being fed back. Similarly, in the first bit diagram, a value of 0 for bit i indicates that OBSS information of link i is being fed back, while a value of 1 indicates that OBSS information of link i is not being fed back.

[0204] The first bitmap can be carried in the link bitmap field.

[0205] The OBSS NAV number field can be used to indicate the number of one or more links corresponding to OBSS feedback information. In other words, the OBSS NAV number field indicates the number of links that have provided feedback OBSS information, i.e., the number of links that have provided feedback.

[0206] One or more OBSS NAV fields can indicate NAV information for one or more links. The NAV information can be the NAV information on the main channel of that link or the NAV information on the NPCA main channel.

[0207] In some embodiments, cache status feedback information can be used to indicate information related to cache status. For example, cache status feedback information can indicate one or more of the following: the access category of the reported cache status; the number of TIDs of the reported cache status; the amount of cached data corresponding to the access category of the reported cache status; the unit of the amount of cached data; the presence of low-latency data in the cache; a high-priority access category; and the amount of cached data corresponding to the high-priority access category.

[0208] The access category of the reported cache state can be indicated by a second bitmap. The second bitmap may include one or more bits. Each of the one or more bits may correspond to one or more access categories. For example, the one or more bits may include a second bit. The second bit may correspond to a first access category. A first value for the second bit may indicate that the cache state of the first access category should be reported. A second value for the second bit may indicate that the cache state of the first access category should not be reported.

[0209] The second bitmap can be carried in the ACI Bitmap field. The ACI Bitmap field can be used to indicate the access category of the reported cache status.

[0210] The number of TIDs in the reported cache state can be carried by the Delta TID field. For example, the Delta TID, together with the value of the ACI bitmap subfield, indicates the number of TIDs that the STA is reporting in the cache state.

[0211] The amount of cached data corresponding to the access category of the reported cache status can be indicated by the queue size all field. The queue size all field indicates the amount of cached data for the AC, as identified by the ACI bitmap subfield.

[0212] High-priority access categories can be indicated by the ACI High field. For example, the ACI High field indicates the ACI of the AC that indicates the BSR in the Queue Size High subfield.

[0213] The unit for cached data size can be octets. The unit of cached data size can be indicated by the scaling factor field. For example, the scaling factor field can indicate the unit for the Queue Size High and Queue Size All subfields.

[0214] The amount of cached data corresponding to high-priority access categories can be represented by the Queue Size High field. The Queue Size High field can be indicated by the Scaling Factor field, which specifies the amount of cached data for the AC identified by the ACI High subfield.

[0215] The LL Indication field can be used to indicate the presence of low-latency data in the cache. For example, a first value for the LL Indication field indicates the presence of low-latency data in the cache. A second value for the LL Indication field indicates the absence of low-latency data in the cache.

[0216] For example, a value of 0 for the LL indicator field indicates that low-latency data exists in the cache; a value of 1 for the LL indicator field indicates that low-latency data does not exist in the cache. Alternatively, a value of 1 for the LL indicator field indicates that low-latency data exists in the cache; a value of 0 for the LL indicator field indicates that low-latency data does not exist in the cache.

[0217] In some embodiments, power mode feedback information can be used to indicate information related to energy saving. For example, power mode feedback information can be used to indicate information related to DPS (Power Performance Per Second).

[0218] Alternatively, power mode feedback information can also be referred to as power feedback (PFB) information.

[0219] For example, power mode feedback information can be used to indicate one or more of the following: first indication information, second indication information, and third indication information. These will be explained below.

[0220] The first indication information is used to indicate that one or more links are in power-saving mode. The first indication information can be indicated by a third bitmap. The third bitmap may include one or more bits. One or more bits may correspond to one or more links. One or more bits may include a third bit. The third bit may correspond to a first link. For example, the third bit may be bit i in the third bitmap, and the first link may be the link identified as i. A first value for the third bit may indicate that the first link is in power-saving mode. A second value for the third bit may indicate that the first link is not in power-saving mode (e.g., in active mode).

[0221] For example, a value of 0 for bit i in the third bit diagram indicates that link i is in power-saving mode, while a value of 1 for bit i in the third bit diagram indicates that link i is in active mode. Similarly, a value of 1 for bit i in the third bit diagram indicates that link i is in power-saving mode, while a value of 0 for bit i in the third bit diagram indicates that link i is in active mode.

[0222] The third bitmap can be carried in the link power saving mode status bitmap field.

[0223] The second indication information is used to indicate whether one or more links need to change their capability mode by receiving ICF frames. The second indication information can be indicated by a fourth bitmap. The fourth bitmap may include one or more bits. One or more bits may correspond to one or more links. One or more bits may include a fourth bit. The fourth bit may correspond to a first link. For example, the fourth bit may be bit i in the fourth bitmap, and the first link may be the link identified as i. A first value for the fourth bit indicates that the first link needs to change its capability mode by receiving ICF frames. A second value for the fourth bit indicates that the first link does not need to change its capability mode by receiving ICF frames.

[0224] For example, a value of 0 for bit i in the fourth bit diagram indicates that link i needs to change its capability mode by receiving an ICF frame; a value of 1 for bit i in the fourth bit diagram indicates that link i does not need to change its capability mode by receiving an ICF frame. Similarly, a value of 1 for bit i in the fourth bit diagram indicates that link i needs to change its capability mode by receiving an ICF frame; a value of 0 for bit i in the fourth bit diagram indicates that link i does not need to change its capability mode by receiving an ICF frame.

[0225] The fourth bitmap can be carried in the DPS ICF Required Bitmap field.

[0226] The third indication information is used to indicate the first indication information and / or the second indication information to indicate the power mode of the first device, or to indicate the first indication information and / or the second indication information to request setting the power mode of the second device.

[0227] The third type of instruction information can be carried in the set / feedback field. For example, the set / feedback field can indicate to the Link PS Status Bitmap field whether to request setting the power-saving mode on one or more links of the peer site (i.e., the second device), or to provide feedback on the power-saving mode on one or more links of the local site (i.e., the first device). As another example, the set / feedback field can indicate to the DPS ICF Required Bitmap field whether to request setting the capability mode on one or more links of the peer site that requires receiving ICF frames, or to provide feedback on whether the capability mode on one or more links of the local site requires receiving ICF frames.

[0228] For example, a first value in the setting / feedback field can indicate that first and / or second indication information is used to indicate the power mode of the first device. A second value in the setting / feedback field can be used to request setting the power mode of the second device. For example, a value of 0 in the setting / feedback field can indicate that first and / or second indication information is used to indicate the power mode of the first device; a value of 1 in the setting / feedback field can be used to request setting the power mode of the second device. For example, a value of 1 in the setting / feedback field can indicate that first and / or second indication information is used to indicate the power mode of the first device; a value of 0 in the setting / feedback field can be used to request setting the power mode of the second device.

[0229] Limitation feedback information can be used to indicate information related to a limited mode. Limitation feedback information is also known as limitation feedback (LFB) information.

[0230] For example, the restricted operation feedback information is used to indicate one or more of the following: the maximum PPDU duration that the first device can receive in restricted mode; the maximum PPDU duration that the first device can transmit in restricted mode; the maximum receive MCS that the first device can support in restricted mode; the maximum transmit MCS that the first device can support in restricted mode; whether the first device can receive LDPC-encoded PPDUs in restricted mode; whether the first device can transmit LDPC-encoded PPDUs in restricted mode; whether the HT-immediate BA protocol is activated in restricted mode; information on one or more sub-channels that the first device has enabled in restricted mode; and information on one or more sub-channels that the first device has disabled in restricted mode.

[0231] The maximum PPDU duration field indicates the maximum PPDU duration that the first device can receive and / or transmit in restricted mode. The unit of this field can be microseconds.

[0232] The maximum MCS field can be used to indicate the maximum MCS that the first device can receive and / or transmit in restricted mode.

[0233] The LDPC mode field indicates whether the first device can receive and / or transmit LDPC-encoded PPDUs in restricted mode.

[0234] The HT-Immediate BA field can be used to indicate whether the HT-immediate BA protocol is active or inactive in the first device under restricted mode.

[0235] The disabled subchannel bitmap field indicates which one or more subchannels (e.g., a 20MHz subchannel) are enabled or disabled by the first device in restricted mode. This field can also indicate a fifth bitmap. The fifth bitmap may include one or more bits. These bits may correspond to one or more subchannels. For example, the fifth bitmap may include a fifth bit. This fifth bit may correspond to the first subchannel. A first value for the fifth bit indicates that the first device enables the first subchannel in restricted mode. A second value for the fifth bit indicates that the first device disables the first subchannel in restricted mode.

[0236] The first frame may include a feedback type field, which indicates the type of feedback information contained in the first frame. The type of feedback information may include one or more of the following: unavailable feedback; internal error feedback; transmission parameter feedback; OBSS feedback; buffer status feedback; power mode feedback; and restricted operation feedback. For example, if the first frame includes feedback information of the first type, the first frame may include a field indicating the type of feedback information. The first type may, for example, be any of the feedback information types mentioned above.

[0237] In some embodiments, the first frame includes one or more of the following: BA frame, trigger frame, data frame, and management frame.

[0238] Therefore, based on this application, feedback parameters can be reported directly while transmitting data, management frames, or control frames, which helps the TXOP owner understand various status parameters of the TXOP responder. This not only increases the frequency of information feedback but also reduces signaling overhead.

[0239] The following explanation uses the first frame, including the trigger frame, as an example.

[0240] As one implementation method, the first information is carried in the UHR special user information field in the user information list of the trigger frame.

[0241] For example, this application proposes a newly defined UHR special user information field. This newly defined UHR special user information field may be referred to as the UHR link feedback special user Info field.

[0242] Figure 19A is an example diagram of a trigger frame format provided in an embodiment of this application.

[0243] As shown in Figure 19A, the special user information fields of UHR may include: trigger type, UL length, AID12 field, type field, and feedback information field. These will be explained below.

[0244] The trigger type field can be used to indicate the type of trigger frame. For example, the trigger frame can be a BSRP trigger frame. The trigger type field can have a value of 4, indicating that the trigger frame is a BSRP trigger frame.

[0245] The UL length field can be used to indicate the duration of the transmission of the response frame of the trigger frame.

[0246] The AID12 field can be set to a first specific value to indicate that the user information field is a UHR-specific user information field. For example, the AID12 field can be set to a first specific value to indicate that the user information field is a UHR link feedback-specific user information field.

[0247] As one implementation, the first specific value can be a reserved value in the related art. For example, the first specific value can be any value among 2008 to 2044 or 2047 to 4094 (inclusive), such as 2009.

[0248] A type field (or feedback type field) can be used to indicate the type of feedback information carried by a UHR-specific user information field. For example, a type field can be used to indicate the type of feedback information carried by a feedback information field within a UHR-specific user information field.

[0249] The type field can be 1, 2, 3, or 4 bits long. The type field can take the value of a different positive integer greater than 0. For example, a type field value of 1 represents UBF, 2 represents EFB, 3 represents MFB, 4 represents OFB, 5 represents BFB, 6 represents PFB, and 7 represents LFB.

[0250] Figure 19B is a sample format diagram of the feedback information field.

[0251] As shown in Figure 19B, the feedback information field can contain one or more of the following feedback information types: UFB, EFB, MFB, OFB, BFB, PFB, and LFB. The various feedback information types are explained below.

[0252] When the type field indicates that the feedback information type is UFB, the feedback information field may contain one or more of the following subfields.

[0253] • Unavailability Period Start Time: The TSF[15:7] value, in units of 64μs, indicates the start time of the unavailability period for the STA that sent this frame.

[0254] • Unavailability Period Duration: Indicates the duration of the unavailability period for the STA that sent this frame, in units of 64μs.

[0255] • Error Occurred: In one embodiment, this field indicates that the transmission error MSDU or A-MSDU indicated in the Block Ack Bitmap field of at least one or all of the Per AID TID Info fields in the M-BA frame is due to an error within the receiving station, rather than due to deterioration of channel conditions. For example, a value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no. In another embodiment, this field indicates whether the time range jointly indicated by the Unavailability Period Start Time field and the Unavailability Period Duration field is earlier or later than the transmission time of the M-BA frame in which this field is located. For example, a value of 1 indicates earlier, and a value of 0 indicates later; or, a value of 0 indicates earlier, and a value of 1 indicates later.

[0256] When the type field indicates that the feedback information type is UFB, the feedback information field may contain the following subfields.

[0257] • Error Occurred: This field indicates that the transmission error MSDU or A-MSDU indicated in the Block Ack Bitmap field of at least one or all of the Per AID TID Info fields in the M-BA frame was caused by an error within the receiving station, rather than by deterioration of channel conditions. For example, a value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0258] When the type field indicates that the feedback information type is MFB, the feedback information field may contain one or more of the following subfields:

[0259] • TB PPDU MFB: A value of 1 indicates that at least one of the following fields—UHR-MCS, NSS, RU Allocation, BW, Tx Beamforming, PPDU Format, Coding Type, RU Type, IM Pilot, and Modulation Pattern—is a transmission parameter used to suggest the subsequent UHT TB PPDU that the STA sending the frame should send to the STA receiving the frame. A value of 0 indicates that at least one of the following fields—UHR-MCS, NSS, RU Allocation, BW, Tx Beamforming, PPDU Format, Coding Type, RU Type, IM Pilot, and Modulation Pattern—is a transmission parameter used to suggest the subsequent UHT MU / ER PPDU that the STA receiving the frame should send to the STA sending the frame.

[0260] • UHR-MCS: Indicator of recommended UHR-MCS. See Table 4 for the meaning of specific values.

[0261] • NSS: Indicates the number of suggested space flows. The value is the number of space flows minus one.

[0262] • RU Allocation: Indicates the location of the suggested resource unit size.

[0263] • BW: Indicates the recommended bandwidth of the PPDU. See Table 5 for specific values.

[0264] • Tx Beamforming: Indicates whether transmitter beamforming is recommended. For example, a value of 1 indicates yes, and a value of 0 indicates no. Alternatively, a value of 0 indicates yes, and a value of 1 indicates no.

[0265] • PPDU Format: Indicates the type of PPDU to be proposed. A value of 0 indicates a UHR MU PPDU, a value of 1 indicates a UHR ER PPDU, and other values ​​are reserved.

[0266] • Coding Type: Indicates the recommended channel coding method. A value of 0 indicates BCC coding, a value of 1 indicates LDPC coding, and other values ​​are reserved.

[0267] • RU Type: Indicates the type of the proposed resource unit. A value of 0 indicates RRU, and a value of 1 indicates DRU.

[0268] •IM Pilot: Indicates the type of interference cancellation pilot to be suggested. A value of 0 indicates no interference cancellation pilot, a value of 1 indicates a conventional interference cancellation pilot, a value of 2 indicates a non-energy interference cancellation pilot, and other values ​​are reserved.

[0269] • Modulation Pattern: Indicates the suggested different modulation patterns. See Table 6 for specific values.

[0270] When the type field indicates that the feedback information type is OFB, the feedback information field may contain one or more of the following subfields:

[0271] • Link Bitmap: Indicates the link that is fed back, where each bit indicates a link. Bit i with a value of 1 indicates that OBSS information of link i is fed back, and bit i with a value of 0 indicates that OBSS information of link i is not fed back.

[0272] • Number of OBSS NAV: Indicates the number of feedback links, and also the number of subsequent OBSS NAV fields.

[0273] •OBSS NAV 1~n: One or more OBSS NAV fields containing NAV information on the main channel of a link or on the NPCA main channel.

[0274] When the type field indicates that the feedback information type is BFB, the feedback information field may contain one or more of the following subfields:

[0275] • ACI Bitmap: Indicates the access category of the reported cache status.

[0276] Delta TID: Together with the value of the ACI Bitmap subfield, it indicates the number of TIDs that the STA is reporting in cached state.

[0277] • ACI High: Indicates the ACI of the AC of the BSR in the Queue Size High subfield.

[0278] • Scaling Factor: Indicates the unit of the Queue Size High and Queue Size All subfields, in octet units.

[0279] • Queue Size High: Indicates the amount of cached data for the AC, as identified by the ACI High subfield, in units of Scaling Factor.

[0280] •Queue Size All: Indicates the amount of cached data for the AC, as identified by the ACI Bitmap subfield, in units of Scaling Factor.

[0281] • LL Indication: Indicates whether low-latency data exists in the cache. For example, a value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0282] When the type field indicates that the feedback information type is PFB, the feedback information field may contain one or more of the following subfields:

[0283] • Link PS Status Bitmap: Bit i indicates the power saving mode of link i. For example, a value of 1 indicates power saving mode, and a value of 0 indicates active mode. Alternatively, a value of 0 indicates power saving mode, and a value of 1 indicates active mode.

[0284] • DPS ICF Required Bitmap: Bit i indicates whether link i needs to change its capability mode by receiving ICF frames. For example, a value of 1 indicates yes, and a value of 0 indicates no. Or, a value of 0 indicates yes, and a value of 1 indicates no.

[0285] • Set / Feedback: Indicates whether the Link PS Status Bitmap field in this PFB is used to request setting the power-saving mode on one or more links of the peer site, or to provide feedback on the power-saving mode on one or more links of this site. The DPS ICF Required Bitmap field is used to request setting whether the capability mode needs to be changed by receiving ICF frames on one or more links of the peer site, or to provide feedback on whether the capability mode needs to be changed by receiving ICF frames on one or more links of this site. For example, a value of 1 indicates a request to set the peer site's power-saving mode, and a value of 0 indicates feedback to this site; or, a value of 0 indicates feedback to this site, and a value of 1 indicates a request to set the peer site's power-saving mode.

[0286] When the type field indicates that the feedback information type is LFB, the feedback information field may contain one or more of the following subfields:

[0287] • Maximum PPDU Duration: Indicates the maximum PPDU duration that a site can receive and / or send in restricted mode, measured in microseconds.

[0288] • Maximum MCS: Indicates the maximum number of MCS that a site can receive and / or transmit in restricted mode.

[0289] • LDPC Mode: Indicates whether the site can receive and / or send LDPC-encoded PPDUs in restricted mode.

[0290] •HT-Immediate BA: Indicates whether the HT-immediate BA protocol is active or inactive in restricted mode.

[0291] •Disabled Subchannel Bitmap: Indicates one or more 20MHz subchannels that are enabled or disabled by the site in restricted mode.

[0292] The following explanation uses the first frame, including the BA frame, as an example.

[0293] As one implementation method, the first information is carried in the BA information field of the BA frame.

[0294] When the first frame includes a BA frame, the first information can be carried through the BA frame to provide suggestions or guidance for subsequent transmissions, thereby improving transmission efficiency and accuracy.

[0295] BA frames may include, for example, M-BA frames. Exemplarily, the format of M-BA frames in related technologies may be improved to indicate first information.

[0296] For example, the BA information field includes at least one Per AID TID Info field with Ack Type = 0 and TID = 13. This Per AID TID Info field includes a feedback type field and a feedback field.

[0297] The feedback type field can be 1, 2, 3, or 4 bits long, and can occupy any bit in the block acknowledgment start sequence control field except for bits B0 and B1. This field indicates the feedback type carried in the feedback field of the M-BA frame. For example, it can take different positive integers greater than 0; exemplarily, a value of 0 represents UBF, a value of 1 represents EFB, a value of 2 represents MFB, a value of 3 represents OFB, a value of 4 represents BFB, a value of 5 represents PFB, and a value of 6 represents LFB.

[0298] Figures 20A to 20G are example diagrams of the format of the M-BA frame provided in the embodiments of this application.

[0299] When the feedback type field indicates that the feedback information type is UFB, the M-BA frame format is shown in Figure 20A. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in UFB mentioned above, and will not be repeated here.

[0300] As shown in Figure 20A, the error occurred field can be a subfield of any of the following fields: BA control, block confirmation start sequence control, and feedback.

[0301] When the feedback type field indicates that the feedback information type is EFB, the M-BA frame format is shown in Figure 20B. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in EFB above, and will not be repeated here.

[0302] As shown in Figure 20B, the error occurred field can be a subfield of any of the following fields: BA control, block confirmation start sequence control, and feedback.

[0303] When the feedback type field indicates that the feedback information type is MFB, the M-BA frame format is shown in Figure 20C. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in MFB above, and will not be repeated here.

[0304] When the feedback type field indicates that the feedback information type is OFB, the M-BA frame format is shown in Figure 20D. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in OFB mentioned above, and will not be repeated here.

[0305] When the feedback type field indicates that the feedback information type is BFB, the M-BA frame format is shown in Figure 20E. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in BFB mentioned above, and will not be repeated here.

[0306] When the feedback type field indicates that the feedback information type is PFB, the M-BA frame format is shown in Figure 20F. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in PFB above, and will not be repeated here.

[0307] When the feedback type field indicates that the feedback information type is LFB, the M-BA frame format is shown in Figure 20G. The meanings of the subfields contained in the feedback information field are the same as the meanings of the corresponding fields in LFB mentioned above, and will not be repeated here.

[0308] In some embodiments, the first information may be carried in the A-control field. For example, the first information may be carried in the A-control field of a data frame. As another example, the first information may be carried in the A-control field of a management frame.

[0309] The type of the A-control field carrying the first information can be a newly defined subtype. For example, the newly defined subtype can be called a UHR link feedback control (ULBF Control) subtype. When the value of the control ID in the A-control field is a second specific value, the type of the A-control field is also a newly defined subtype. Exemplarily, the second specific value can be a reserved value in related technologies. For example, the second specific value can be any integer between 10 and 14 (inclusive), such as 11.

[0310] Figure 21A is an example diagram of the format of a first frame provided in an embodiment of this application. The first frame in Figure 21A is a data frame or a management frame. Some fields in Figure 21A are described below.

[0311] The Control ID field takes the value of any integer between 10 and 14, such as 11, indicating that the type of the A-Control field is the ULBF Control subtype.

[0312] The type field (also known as the feedback type field) can be 1, 2, 3, or 4 bits long. The type field indicates the type of feedback information carried by the ULBF Control field. For example, it can take different positive integer values ​​greater than 0. Exemplarily, a value of 1 represents UBF, a value of 2 represents EFB, a value of 3 represents MFB, a value of 4 represents OFB, a value of 5 represents BFB, a value of 6 represents PFB, and a value of 7 represents LFB.

[0313] The ULFB Information field contains the specific feedback information. The ULFB Information field can include one or more of the following feedback information types: UFB, EFB, MFB, OFB, BFB, PFB, and LFB.

[0314] Figure 21B is an example of the format of the ULFB information field. Figure 21B shows the format of the field carrying UFB, EFB, MFB, OFB, BFB, PFB, and LFB feedback information. For explanations of the relevant fields, please refer to the previous text; they will not be repeated here.

[0315] In some embodiments, the first device may actively send a first frame. In this case, the first frame may include a data frame, a management frame, or a trigger frame.

[0316] The following explanation uses Figure 22 as an example.

[0317] In Figure 22, the first device includes STA1, and the second device includes STA2.

[0318] As shown in Figure 22, STA 1 sends a third PPDU to STA 2. The third PPDU contains at least one data frame, management frame, or control frame (i.e., the first frame) with feedback information.

[0319] The feedback information in the data frame or management frame is in the format of a ULFB Control field with a value > 0 as described above for the type field.

[0320] The format of the feedback information in the control frame can be the UHR link feedback special user information field in the trigger frame described above.

[0321] Optionally, after the SIFS time interval, STA 2 replies to STA 1 with a fourth PPDU. Alternatively, STA 2 may not reply to STA 1 with a fourth PPDU.

[0322] In some embodiments, the method shown in FIG18 may further include step S1805.

[0323] In step S1805, the first device may receive a second frame sent by the second device. The second frame carries second information. The second information may be used to configure the first information, and / or may be used to request the first frame to carry the first information. In other words, the second frame may be used to configure the first information, and / or the second frame may be used to trigger the transmission of the first information.

[0324] The second information can also be called control information.

[0325] For example, the second information can be used to configure whether the first information is carried in the first frame or not. Alternatively, the second information can be used to configure whether the first frame carries one or more types of feedback information. Another example is that the second information can be used to request the first information to be carried in the first frame. Yet another example is that the second information can be used to request the first frame to carry one or more types of feedback information.

[0326] For example, the second information may include one or more of the following: enabling unrequested unavailability feedback information in the first frame, disabling unrequested unavailability feedback information in the first frame, enabling unrequested internal error feedback information in the first frame, disabling unrequested internal error feedback information in the first frame, enabling unrequested transmission parameter feedback information in the first frame, disabling unrequested transmission parameter feedback information in the first frame, enabling unrequested OBSS feedback information in the first frame, disabling unrequested OBSS feedback information in the first frame, enabling unrequested buffer status feedback information in the first frame, disabling unrequested buffer status feedback information in the first frame, enabling unrequested power mode feedback information in the first frame, disabling unrequested power mode feedback information in the first frame, enabling unrequested restricted operation feedback information in the first frame, and disabling unrequested restricted operation feedback information in the first frame.

[0327] For example, the second information may include one or more of the following: whether to request the first frame to carry unavailable feedback information, whether to request the first frame to carry internal error feedback information, whether to request the first frame to carry transmission parameter feedback information, whether to request the first frame to carry OBSS feedback information, whether to request the first frame to carry buffer status feedback information, whether to request the first frame to carry power mode feedback information, and whether to request the first frame to carry restricted operation feedback information.

[0328] In some embodiments, a frame carrying first information or second information may include a type field. The type field can be used to indicate whether the frame carries first information or second information. For example, a first value in the type field indicates that the frame carries second information. A value other than the first value indicates that the frame carries first information. For example, a first value of 0 indicates that the frame carries second information. A value greater than 0 indicates that the frame carries first information.

[0329] The interaction process based on the first and second frames will be illustrated below using Figures 23 and 24.

[0330] In Figure 23, the first device includes STA2 and the second device includes STA1.

[0331] As shown in Figure 23, STA 1 sends the first PPDU to STA 2.

[0332] The first PPDU contains at least one data frame, management frame, or control frame (i.e., the second frame) with control information. The control information in the first PPDU is used to control the type of feedback information in the second PPDU.

[0333] After the SIFS interval, STA 2 sends a second PPDU back to STA 1.

[0334] The second PPDU contains at least one M-BA frame (i.e., the first frame) with feedback information. The format of the feedback information in the M-BA frame can be the bolded field of the M-BA frame in the above embodiment.

[0335] In Figure 24, the first device includes STA2 and / or STA3, and the second device includes STA1.

[0336] As shown in Figure 24, STA 1 sends the first PPDU to STA 2 and STA 3.

[0337] The first PPDU contains at least one data frame, management frame, or control frame (i.e., the second frame) with control information. The control information in the first PPDU is used to control the type of feedback information in the second PPDU.

[0338] The format of control information in data frames or management frames will be described in detail below.

[0339] After the SIFS interval, STA 2 and STA 3 reply to STA 1 with a second PPDU.

[0340] The second PPDU contains at least one M-BA frame (i.e., the first frame) with feedback information. The format of the feedback information in the M-BA frame can be the bolded field of the M-BA frame in the above embodiment.

[0341] The format of the second frame will be explained below.

[0342] In some embodiments, the second frame includes one or more of the following: a trigger frame, a data frame, and a management frame.

[0343] Therefore, this application can request or allow the peer to report multiple feedback parameters in the first frame of the immediate response (e.g., M-BA frame) while transmitting data, management frames, or control frames. This helps the TXOP owner to understand the various status parameters of the TXOP responder, which can not only increase the frequency of information feedback but also reduce signaling overhead.

[0344] The following explanation uses the second frame, including the trigger frame, as an example.

[0345] As one implementation, the second information is carried in one or more of the following fields in the trigger frame: the public information field, the UHR special user information field in the user information list field.

[0346] In some embodiments, the second information may be carried in a public information field and / or a special user information field. For example, the second information may be carried in one or more reserved fields of the public information field and / or the special user information field as defined in the relevant technology.

[0347] Figure 25 is an example of the format of a second frame. In Figure 25, the second frame is a BSRP trigger frame.

[0348] In Figure 25, the trigger type field can have a value of 4, indicating a BSRP trigger frame.

[0349] The UL length field indicates the duration of the transmission of the response frame for the trigger frame. The value of this field should ensure that the length of the requested PPDU (e.g., UHR TB PPDU) is long enough to carry one or more feedback messages in the first frame.

[0350] As shown in Figure 25, the reserved fields defined in the related technologies can be used to carry second information.

[0351] The second information is carried through one or more of the following fields: unsolicited UFB enable / disable, unsolicited EFB enable / disable, unsolicited MFB enable / disable, unsolicited OFB enable / disable, unsolicited BFB enable / disable, unsolicited PFB enable / disable, unsolicited LFB enable / disable, solicited UFB (solicited UFB), solicited EFB (solicited EFB), solicited MFB (solicited MFB), solicited OFB (solicited OFB), solicited BFB (solicited BFB), solicited PFB (solicited PFB), and solicited LFB (solicited LFB). These fields are explained below.

[0352] The unsolicited UFB enable / disable field indicates whether to enable or disable carrying unsolicited unavailability feedback information in the second frame (i.e., the first frame, such as an M-BA frame). A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0353] The unsolicited EFB enable / disable field indicates whether to enable or disable carrying unsolicited internal error feedback information in the second frame requested to be sent. A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0354] The unsolicited MFB enable / disable field indicates whether to enable or disable the transmission of unsolicited MCS feedback information in the second frame requested to be sent. A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0355] The unsolicited OFB enable / disable field indicates whether to enable or disable the transmission of unsolicited OBSS feedback information in the second frame requested to be sent. A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0356] The `enable / disable` field of the unsolicited BFB indicates whether to enable or disable the carrying of unsolicited cached state feedback information in the frame sent in the second frame request. A value of 1 indicates enabled, and a value of 0 indicates disabled; or, a value of 0 indicates enabled, and a value of 1 indicates disabled.

[0357] The unsolicited PFB enable / disable field indicates whether to enable or disable the transmission of unsolicited power mode feedback information in the second frame requested for transmission. A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0358] The unsolicited LFB enable / disable field indicates whether to enable or disable the transmission of unsolicited restricted operation feedback information in the second frame requested to be sent. A value of 1 indicates enable, and a value of 0 indicates disable; or, a value of 0 indicates enable, and a value of 1 indicates disable.

[0359] The solicit UFB field indicates whether to request that an unavailable feedback message be included in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0360] The `solicit EFB` field indicates whether to request that internal error feedback information be included in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0361] The solicit MFB field indicates whether to request that the MCS feedback information be carried in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0362] The solicit OFB field indicates whether to request that OBSS feedback information be included in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0363] The `solicit BFB` field indicates whether to request that buffer status feedback information be included in the frame sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0364] The solicit PFB field indicates whether to request that power mode feedback information be carried in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0365] The solicit LFB field indicates whether to request that restricted operation feedback information be carried in the frame to be sent in the second frame. A value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no.

[0366] In some embodiments, the second information may be carried in a UHR-specific user information field within a user information list field. For example, the second information may be carried in a UHR link feedback-specific user information field.

[0367] Figure 26 is an example diagram of another trigger frame format provided in an embodiment of this application. Some fields in Figure 26 will be described below.

[0368] The trigger type field in Figure 26 can take the value 4, indicating a BSRP trigger frame.

[0369] The UL length indicates the duration of transmission of the response frame for the trigger frame. For example, the value of the UL length field should ensure that the length of the requested UHR TB PPDU is long enough to carry one or more feedback messages in the M-BA frame.

[0370] The user information list includes a special user information field for UHR link feedback. This special user information field contains at least one of the following fields: AID12, type, unsolicited UFB enable / disable, unsolicited EFB enable / disable, unsolicited MFB enable / disable, unsolicited OFB enable / disable, unsolicited BFB enable / disable, unsolicited PFB enable / disable, unsolicited LFB enable / disable, solicited UFB, solicited EFB, solicited MFB, solicited OFB, solicited BFB, solicited PFB, and solicited LFB.

[0371] The AID12 field can be used to identify this user information field as a special user information field for UHR link feedback. The value of the AID12 field can be any value from 2008 to 2044 or from 2047 to 4094, for example, 2009.

[0372] The type field can be 1, 2, 3, or 4 bits long. The type field can indicate that the UHR link is feeding back a special user information field used to carry control information; for example, a value of 0.

[0373] unsolicited UFB enable / disable, unsolicited EFB enable / disable, unsolicited MFB enable / disable, unsolicited OFB enable / disable, unsolicited BFB enable / disable, unsolicited PFB enable / disable, unsolicited LFB enable / disable, solicitit UFB, solicitit EFB, solicitit MFB, solicitit OFB, solicitit BFB, solicitit The meanings of PFB and solicitit LFB are as mentioned above and will not be repeated here.

[0374] In some embodiments, the second information may be carried in the A-control field. For example, the second information may be carried in the A-control field of a data frame. As another example, the second information may be carried in the A-control field of a management frame.

[0375] Figure 27 is an example diagram of another second frame format provided in an embodiment of this application.

[0376] In Figure 27, the Control ID field takes any integer value between 10 and 14, such as 11, indicating that the type of the A-Control field is a ULBF Control subtype. The type field can be 1, 2, 3, or 4 bits long, indicating that the ULBF Control field is used to carry control information; for example, a value of 0. The meanings of unsolicited UFB enable / disable, unsolicited EFB enable / disable, unsolicited MFB enable / disable, unsolicited OFB enable / disable, unsolicited BFB enable / disable, unsolicited PFB enable / disable, unsolicited LFB enable / disable, solicited UFB, solicited EFB, solicited MFB, solicited OFB, solicited BFB, solicited PFB, and solicited LFB are explained above and will not be repeated here.

[0377] Figure 28 is an example diagram of another second frame format provided in an embodiment of this application.

[0378] In Figure 28, the Control ID field takes any integer value between 10 and 14, such as 11, indicating that the type of the A-Control field is a ULBF Control subtype. The type field can be 1, 2, 3, or 4 bits long, indicating that the ULBF Control field is used to carry control information; for example, a value of 0.

[0379] In Figure 28, the unsolicited xFB enable / disable field indicates whether the type of unsolicited xFB feedback information carried in the first frame is enabled or disabled. For example, a value of 0 represents UBF, a value of 1 represents EFB, a value of 2 represents MFB, a value of 3 represents OFB, a value of 4 represents BFB, a value of 5 represents PFB, and a value of 6 represents LFB.

[0380] In Figure 28, the `solicit xFB` field can indicate the type of feedback information requested to be carried in the first frame. For example, a value of 0 represents UBF, a value of 1 represents EFB, a value of 2 represents MFB, a value of 3 represents OFB, a value of 4 represents BFB, a value of 5 represents PFB, and a value of 6 represents LFB.

[0381] For ease of understanding, the present application will be illustrated in detail below through Examples 1 to 3.

[0382] Example 1

[0383] Figure 29 is an example diagram of the communication process provided in Embodiment 1. In Figure 29, the first device includes a STA; the second device includes an AP.

[0384] In Example 1, AP is the owner of TXOP and STA is the responder of TXOP.

[0385] As shown in Figure 29, the AP sends a PPDU to the STA using MCS=6, where the A-MPDU carries two data frames. Each data frame's MAC header contains the same ULFB control field, where the type field is set to 0, indicating that the ULFB Control field is used to carry control information. The solicit MFB field is set to 1, indicating a request for the peer station to carry MFB feedback information in the immediate response M-BA frame.

[0386] After SIFS, the STA replies with an M-BA frame, which carries a feedback type field with a value of 2, indicating the MFB feedback type. The Feedback field carries a UHR-MCS field with a value of 2, indicating that the AP is advised to use the modulation and coding scheme of MCS=2 in subsequent PPDUs sent to the STA.

[0387] When the AP sends the A-MPDU containing the data frame to the STA, the MCS of the PPDU is adjusted to MCS=2.

[0388] Example 2

[0389] Figure 30 is an example diagram of the communication process provided in Embodiment 2. In Figure 30, the first device includes STA1 and STA2; the second device includes AP.

[0390] In Example 2, AP is the owner of TXOP and STA is the responder of TXOP.

[0391] The difference from Example 1 is that the A-MPDU sent by the AP contains a data frame and a trigger frame. The data frame does not contain the ULFB control field, but the trigger frame contains control information, such as solicit MFB=1, which instructs STA 1 and STA 2 to report MFB feedback information in the M-BA frame that responds immediately.

[0392] After SIFS, STA 1 and STA 2 each reply with an M-BA frame in the TB PPDU, which carries a Feedback Type field with a value of 2, indicating the MFB feedback type. The Feedback field also carries a UHR-MCS field with a value of 2, indicating that the AP should use the modulation and coding scheme with MCS=2 in subsequent PPDUs sent to the STA.

[0393] When the AP sends the A-MPDU containing data frames to STA 1 and STA 2, the MCS of the PPDU used is adjusted to MCS=2.

[0394] Example 3

[0395] Figure 31 is an example diagram of the communication process provided in Embodiment 3. In Figure 31, the first device includes a STA; the second device includes an AP.

[0396] Initially, STA was the owner of TXOP, and AP was the responder of TXOP.

[0397] The STA sends a data frame carrying the ULFB Control field, but the Type field is set to 2, indicating that the ULFB Control field is used to carry MFB feedback information. Furthermore, UHR-MCS=3, suggesting that the AP should use modulation and coding scheme with MCS=3 for subsequent PPDUs transmitted to the STA.

[0398] Subsequently, the AP becomes the owner of the TXOP, and the STA becomes the TXOP responder. Based on the MFB feedback information in the ULFB Control field mentioned above, the AP preferentially selects to send the PPDU containing the data frame to the STA using the modulation and coding scheme of MCS=3.

[0399] It should be noted that the frame format or field format in the figures provided in this application are merely examples. The format in the figures can be modified. For example, some fields can be deleted or added to the figures.

[0400] 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.

[0401] Figure 32 is a schematic structural diagram of a communication device 3200 provided in an embodiment of this application. The communication device 3200 can be a first device. The communication device 3200 includes a transmitting unit 3210.

[0402] The sending unit 3210 is used to send a first frame to the second device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; OBSS feedback information; buffer status feedback information; power mode feedback information; restricted operation feedback information.

[0403] In this embodiment, the communication device 3200 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 3200 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 3200.

[0404] In an optional embodiment, the transmitting unit 3210 may be a transceiver 3430. The communication device 3200 may also include a processor 3410 and a memory 3420, as shown in FIG34.

[0405] Figure 33 is a schematic structural diagram of a communication device 3300 provided in an embodiment of this application. The communication device 3300 can be a second device. The communication device 3300 includes a receiving unit 3310.

[0406] The receiving unit 3310 is used to receive a first frame sent by the first device; wherein the first frame carries first information, the first information including one or more of the following: unavailability feedback information; internal error feedback information; transmission parameter feedback information; OBSS feedback information; buffer status feedback information; power mode feedback information; restricted operation feedback information.

[0407] In this embodiment, the communication device 3300 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 3300 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 3300.

[0408] In an optional embodiment, the receiving unit 3310 may be a transceiver 3430. The communication device 3300 may also include a processor 3410 and a memory 3420, as shown in FIG34.

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

[0410] Apparatus 3400 may include one or more processors 3410. The processor 3410 may support apparatus 3400 in implementing the methods described in the preceding method embodiments. The processor 3410 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.

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

[0412] The device 3400 may also include a transceiver 3430. The processor 3410 can communicate with other devices or chips via the transceiver 3430. For example, the processor 3410 can send and receive data with other devices or chips via the transceiver 3430.

[0413] 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.

[0414] 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.

[0415] 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.

[0416] 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.

[0417] 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).

[0418] Unless otherwise stated, this application does not restrict the position of each field, that is, the position of each field can be adjusted.

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

[0420] 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.

[0421] 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.

[0422] 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.

[0423] 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.

[0424] 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.

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

[0426] 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.

[0427] 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.

[0428] 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.

[0429] 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.

[0430] 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.

[0431] 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.

[0432] 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 frame to the second device; The first frame carries first information, which includes one or more of the following: Feedback information is unavailable; Internal error feedback information; Transmission parameter feedback information; Overlapping basic service set OBSS feedback information; Cache status feedback information; Power mode feedback information; Feedback information regarding restricted operations.

2. The method according to claim 1, characterized in that, The unavailability period of the first device is a first time period, and the unavailability feedback information includes one or more of the following: The start time of the first time period; The end time of the first time period; The duration of the first time period; The transmission error was caused by an internal error in the first device; The first time period is earlier or later than the transmission time of the first frame.

3. The method according to claim 1 or 2, characterized in that, The internal feedback information is used to indicate that the transmission error is caused by an internal error in the first device.

4. The method according to any one of claims 1-3, characterized in that, The transmission parameter feedback information is used to indicate one or more of the following: The transmission parameter feedback information is used to suggest transmission parameters for the Physical Layer Protocol Data Unit (PPDU) sent by the first device after the first frame. The transmission parameter feedback information is used to suggest transmission parameters for the PPDU sent by the second device after the first frame; The values ​​of the transmission parameters.

5. The method according to claim 4, characterized in that, The transmission parameters include one or more of the following: modulation and coding scheme (MCS), number of spatial streams (NSS), size of resource unit (RU), location of RU, bandwidth, transmit beamforming, PPDU format, coding type, type of RU, type of interference cancellation pilot, and modulation mode corresponding to multiple spatial streams.

6. The method according to any one of claims 1-5, characterized in that, The OBSS feedback information is used to indicate one or more of the following: The OBSS feedback information corresponds to the identifier of one or more links; The number of the one or more links; Network allocation vector (NAV) information for one or more links.

7. The method according to any one of claims 1-6, characterized in that, The cache status feedback information is used to indicate one or more of the following: The access category of the reported cache state; The number of business identifiers (TIDs) in the reported cache status; The amount of cached data corresponding to the access category of the cache status reported; The unit for the amount of cached data; Low-latency data exists in the cache; High-priority access categories; The amount of cached data corresponding to the high-priority access category.

8. The method according to any one of claims 1-7, characterized in that, The power mode feedback information is used to indicate one or more of the following: The first indication information is used to indicate that one or more links are in power-saving mode; The second indication information is used to indicate whether one or more links need to change their capability mode by receiving ICF frames; The third indication information is used to indicate that the first indication information and / or the second indication information are used to indicate the power mode of the first device, or to indicate that the first indication information and / or the second indication information are used to request setting the power mode of the second device.

9. The method according to any one of claims 1-8, characterized in that, The restricted operation feedback information is used to indicate one or more of the following: The maximum PPDU duration that the first device can receive in restricted mode; The maximum PPDU duration that the first device can send in restricted mode; The maximum number of received MCS that the first device can support in restricted mode; The maximum number of transmission MCS that the first device can support in restricted mode; Whether the first device can receive PPDU encoded with low-density parity-check code (LDPC) in restricted mode; Whether the first device can send LDPC-encoded PPDUs in restricted mode; The first device in constrained mode immediately confirms whether the HT-immediate BA protocol is activated; Information about one or more sub-channels enabled by the first device in restricted mode; Information about one or more sub-channels that the first device shuts down in restricted mode.

10. The method according to any one of claims 1-9, characterized in that, The first frame includes one or more of the following: BA frame, trigger frame, data frame, management frame.

11. The method according to claim 10, characterized in that, The first information is carried in the Ultra-High Reliability UHR Special User Information field in the user information list of the trigger frame.

12. The method according to claim 10, characterized in that, The first information is carried in the BA information field of the BA frame.

13. The method according to claim 10, characterized in that, The first information is carried in the A-Control field of the data frame.

14. The method according to claim 10, characterized in that, The first information is carried in the A-Control field of the management frame.

15. The method according to any one of claims 1-14, characterized in that, The method further includes: The first device receives the second frame sent by the second device; The second frame carries second information, which is used to configure the first information, and / or the second information is used to request the first frame to carry the first information.

16. The method according to claim 15, characterized in that, The second frame includes one or more of the following: a trigger frame, a data frame, and a management frame.

17. The method according to claim 16, characterized in that, The second information is carried in one or more of the following fields in the trigger frame: the public information field, the UHR special user information field in the user information list field.

18. The method according to claim 16, characterized in that, The second information is carried in the A-Control field of the data frame.

19. The method according to claim 16, characterized in that, The second information is carried in the A-Control field of the management frame.

20. A wireless communication method, characterized in that, include: The second device receives the first frame sent by the first device; The first frame carries first information, which includes one or more of the following: Feedback information is unavailable; Internal error feedback information; Transmission parameter feedback information; Overlapping basic service set OBSS feedback information; Cache status feedback information; Power mode feedback information; Feedback information regarding restricted operations.

21. The method according to claim 20, characterized in that, The unavailability period of the first device is a first time period, and the unavailability feedback information includes one or more of the following: The start time of the first time period; The end time of the first time period; The duration of the first time period; The transmission error was caused by an internal error in the first device; The first time period is earlier or later than the transmission time of the first frame.

22. The method according to claim 20 or 21, characterized in that, The internal feedback information is used to indicate that the transmission error is caused by an internal error in the first device.

23. The method according to any one of claims 20-22, characterized in that, The transmission parameter feedback information is used to indicate one or more of the following: The transmission parameter feedback information is used to suggest transmission parameters for the Physical Layer Protocol Data Unit (PPDU) sent by the first device after the first frame. The transmission parameter feedback information is used to suggest transmission parameters for the PPDU sent by the second device after the first frame; The values ​​of the transmission parameters.

24. The method according to claim 23, characterized in that, The transmission parameters include one or more of the following: modulation and coding scheme (MCS), number of spatial streams (NSS), size of resource unit (RU), location of RU, bandwidth, transmit beamforming, PPDU format, coding type, type of RU, type of interference cancellation pilot, and modulation mode corresponding to multiple spatial streams.

25. The method according to any one of claims 20-24, characterized in that, The OBSS feedback information is used to indicate one or more of the following: The OBSS feedback information corresponds to the identifier of one or more links; The number of the one or more links; Network allocation vector (NAV) information for one or more links.

26. The method according to any one of claims 20-25, characterized in that, The cache status feedback information is used to indicate one or more of the following: The access category of the reported cache state; The number of business identifiers (TIDs) in the reported cache status; The amount of cached data corresponding to the access category of the cache status reported; The unit for the amount of cached data; Low-latency data exists in the cache; High-priority access categories; The amount of cached data corresponding to the high-priority access category.

27. The method according to any one of claims 20-26, characterized in that, The power mode feedback information is used to indicate one or more of the following: The first indication information is used to indicate that one or more links are in power-saving mode; The second indication information is used to indicate whether one or more links need to change their capability mode by receiving ICF frames; The third indication information is used to indicate that the first indication information and / or the second indication information are used to indicate the power mode of the first device, or to indicate that the first indication information and / or the second indication information are used to request setting the power mode of the second device.

28. The method according to any one of claims 20-27, characterized in that, The restricted operation feedback information is used to indicate one or more of the following: The maximum PPDU duration that the first device can receive in restricted mode; The maximum PPDU duration that the first device can send in restricted mode; The maximum number of received MCS that the first device can support in restricted mode; The maximum number of transmission MCS that the first device can support in restricted mode; Whether the first device can receive PPDU encoded with low-density parity-check code (LDPC) in restricted mode; Whether the first device can send LDPC-encoded PPDUs in restricted mode; The first device in constrained mode immediately confirms whether the HT-immediate BA protocol is activated; Information about one or more sub-channels enabled by the first device in restricted mode; Information about one or more sub-channels that the first device shuts down in restricted mode.

29. The method according to any one of claims 20-28, characterized in that, The first frame includes one or more of the following: BA frame, trigger frame, data frame, management frame.

30. The method according to claim 29, characterized in that, The first information is carried in the Ultra-High Reliability UHR Special User Information field in the user information list of the trigger frame.

31. The method according to claim 29, characterized in that, The first information is carried in the BA information field of the BA frame.

32. The method according to claim 29, characterized in that, The first information is carried in the A-Control field of the data frame.

33. The method according to claim 29, characterized in that, The first information is carried in the A-Control field of the management frame.

34. The method according to any one of claims 20-33, characterized in that, The method further includes: The second device sends a second frame to the first device; The second frame carries second information, which is used to configure the first information, and / or the second information is used to request the first frame to carry the first information.

35. The method according to claim 34, characterized in that, The second frame includes one or more of the following: a trigger frame, a data frame, and a management frame.

36. The method according to claim 35, characterized in that, The second information is carried in one or more of the following fields in the trigger frame: the public information field, the UHR special user information field in the user information list field.

37. The method according to claim 35, characterized in that, The second information is carried in the A-Control field of the data frame.

38. The method according to claim 35, characterized in that, The second information is carried in the A-Control field of the management frame.

39. 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 the first frame to the second device; The first frame carries first information, which includes one or more of the following: Feedback information is unavailable; Internal error feedback information; Transmission parameter feedback information; Overlapping basic service set OBSS feedback information; Cache status feedback information; Power mode feedback information; Feedback information regarding restricted operations.

40. The communication device according to claim 39, characterized in that, The unavailability period of the first device is a first time period, and the unavailability feedback information includes one or more of the following: The start time of the first time period; The end time of the first time period; The duration of the first time period; The transmission error was caused by an internal error in the first device; The first time period is earlier or later than the transmission time of the first frame.

41. The communication device according to claim 39 or 40, characterized in that, The internal feedback information is used to indicate that the transmission error is caused by an internal error in the first device.

42. The communication device according to any one of claims 39-41, characterized in that, The transmission parameter feedback information is used to indicate one or more of the following: The transmission parameter feedback information is used to suggest transmission parameters for the Physical Layer Protocol Data Unit (PPDU) sent by the first device after the first frame. The transmission parameter feedback information is used to suggest transmission parameters for the PPDU sent by the second device after the first frame; The values ​​of the transmission parameters.

43. The communication device according to claim 42, characterized in that, The transmission parameters include one or more of the following: modulation and coding scheme (MCS), number of spatial streams (NSS), size of resource unit (RU), location of RU, bandwidth, transmit beamforming, PPDU format, coding type, type of RU, type of interference cancellation pilot, and modulation mode corresponding to multiple spatial streams.

44. The communication device according to any one of claims 39-43, characterized in that, The OBSS feedback information is used to indicate one or more of the following: The OBSS feedback information corresponds to the identifier of one or more links; The number of the one or more links; Network allocation vector (NAV) information for one or more links.

45. The communication device according to any one of claims 39-44, characterized in that, The cache status feedback information is used to indicate one or more of the following: The access category of the reported cache state; The number of business identifiers (TIDs) in the reported cache status; The amount of cached data corresponding to the access category of the cache status reported; The unit for the amount of cached data; Low-latency data exists in the cache; High-priority access categories; The amount of cached data corresponding to the high-priority access category.

46. ​​The communication device according to any one of claims 39-45, characterized in that, The power mode feedback information is used to indicate one or more of the following: The first indication information is used to indicate that one or more links are in power-saving mode; The second indication information is used to indicate whether one or more links need to change their capability mode by receiving ICF frames; The third indication information is used to indicate that the first indication information and / or the second indication information are used to indicate the power mode of the first device, or to indicate that the first indication information and / or the second indication information are used to request setting the power mode of the second device.

47. The communication device according to any one of claims 39-46, characterized in that, The restricted operation feedback information is used to indicate one or more of the following: The maximum PPDU duration that the first device can receive in restricted mode; The maximum PPDU duration that the first device can send in restricted mode; The maximum number of received MCS that the first device can support in restricted mode; The maximum number of transmission MCS that the first device can support in restricted mode; Whether the first device can receive PPDU encoded with low-density parity-check code (LDPC) in restricted mode; Whether the first device can send LDPC-encoded PPDUs in restricted mode; The first device in constrained mode immediately confirms whether the HT-immediate BA protocol is activated; Information about one or more sub-channels enabled by the first device in restricted mode; Information about one or more sub-channels that the first device shuts down in restricted mode.

48. The communication device according to any one of claims 39-47, characterized in that, The first frame includes one or more of the following: BA frame, trigger frame, data frame, management frame.

49. The communication device according to claim 48, characterized in that, The first information is carried in the Ultra-High Reliability UHR Special User Information field in the user information list of the trigger frame.

50. The communication device according to claim 48, characterized in that, The first information is carried in the BA information field of the BA frame.

51. The communication device according to claim 48, characterized in that, The first information is carried in the A-Control field of the data frame.

52. The communication device according to claim 48, characterized in that, The first information is carried in the A-Control field of the management frame.

53. The communication device according to any one of claims 39-52, characterized in that, The communication device is also used for: Receive the second frame sent by the second device; The second frame carries second information, which is used to configure the first information, and / or the second information is used to request the first frame to carry the first information.

54. The communication device according to claim 53, characterized in that, The second frame includes one or more of the following: a trigger frame, a data frame, and a management frame.

55. The communication device according to claim 54, characterized in that, The second information is carried in one or more of the following fields in the trigger frame: the public information field, the UHR special user information field in the user information list field.

56. The communication device according to claim 54, characterized in that, The second information is carried in the A-Control field of the data frame.

57. The communication device according to claim 54, characterized in that, The second information is carried in the A-Control field of the management frame.

58. 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 frame sent by the first device; The first frame carries first information, which includes one or more of the following: Feedback information is unavailable; Internal error feedback information; Transmission parameter feedback information; Overlapping basic service set OBSS feedback information; Cache status feedback information; Power mode feedback information; Feedback information regarding restricted operations.

59. The communication device according to claim 58, characterized in that, The unavailability period of the first device is a first time period, and the unavailability feedback information includes one or more of the following: The start time of the first time period; The end time of the first time period; The duration of the first time period; The transmission error was caused by an internal error in the first device; The first time period is earlier or later than the transmission time of the first frame.

60. The communication device according to claim 58 or 59, characterized in that, The internal feedback information is used to indicate that the transmission error is caused by an internal error in the first device.

61. The communication device according to any one of claims 58-60, characterized in that, The transmission parameter feedback information is used to indicate one or more of the following: The transmission parameter feedback information is used to suggest transmission parameters for the Physical Layer Protocol Data Unit (PPDU) sent by the first device after the first frame. The transmission parameter feedback information is used to suggest transmission parameters for the PPDU sent by the second device after the first frame; The values ​​of the transmission parameters.

62. The communication device according to claim 61, characterized in that, The transmission parameters include one or more of the following: modulation and coding scheme (MCS), number of spatial streams (NSS), size of resource unit (RU), location of RU, bandwidth, transmit beamforming, PPDU format, coding type, type of RU, type of interference cancellation pilot, and modulation mode corresponding to multiple spatial streams.

63. The communication device according to any one of claims 58-62, characterized in that, The OBSS feedback information is used to indicate one or more of the following: The OBSS feedback information corresponds to the identifier of one or more links; The number of the one or more links; Network allocation vector (NAV) information for one or more links.

64. The communication device according to any one of claims 58-63, characterized in that, The cache status feedback information is used to indicate one or more of the following: The access category of the reported cache state; The number of business identifiers (TIDs) in the reported cache status; The amount of cached data corresponding to the access category of the cache status reported; The unit for the amount of cached data; Low-latency data exists in the cache; High-priority access categories; The amount of cached data corresponding to the high-priority access category.

65. The communication device according to any one of claims 58-64, characterized in that, The power mode feedback information is used to indicate one or more of the following: The first indication information is used to indicate that one or more links are in power-saving mode; The second indication information is used to indicate whether one or more links need to change their capability mode by receiving ICF frames; The third indication information is used to indicate that the first indication information and / or the second indication information are used to indicate the power mode of the first device, or to indicate that the first indication information and / or the second indication information are used to request setting the power mode of the second device.

66. The communication device according to any one of claims 58-65, characterized in that, The restricted operation feedback information is used to indicate one or more of the following: The maximum PPDU duration that the first device can receive in restricted mode; The maximum PPDU duration that the first device can send in restricted mode; The maximum number of received MCS that the first device can support in restricted mode; The maximum number of transmission MCS that the first device can support in restricted mode; Whether the first device can receive PPDU encoded with low-density parity-check code (LDPC) in restricted mode; Whether the first device can send LDPC-encoded PPDUs in restricted mode; The first device in constrained mode immediately confirms whether the HT-immediate BA protocol is activated; Information about one or more sub-channels enabled by the first device in restricted mode; Information about one or more sub-channels that the first device shuts down in restricted mode.

67. The communication device according to any one of claims 58-66, characterized in that, The first frame includes one or more of the following: BA frame, trigger frame, data frame, management frame.

68. The communication device according to claim 67, characterized in that, The first information is carried in the Ultra-High Reliability UHR Special User Information field in the user information list of the trigger frame.

69. The communication device according to claim 67, characterized in that, The first information is carried in the BA information field of the BA frame.

70. The communication device according to claim 67, characterized in that, The first information is carried in the A-Control field of the data frame.

71. The communication device according to claim 67, characterized in that, The first information is carried in the A-Control field of the management frame.

72. The communication device according to any one of claims 58-71, characterized in that, The communication device is also used for: Send the second frame to the first device; The second frame carries second information, which is used to configure the first information, and / or the second information is used to request the first frame to carry the first information.

73. The communication device according to claim 72, characterized in that, The second frame includes one or more of the following: a trigger frame, a data frame, and a management frame.

74. The communication device according to claim 72, characterized in that, The second information is carried in one or more of the following fields in the trigger frame: the public information field, the UHR special user information field in the user information list field.

75. The communication device according to claim 72, characterized in that, The second information is carried in the A-Control field of the data frame.

76. The communication device according to claim 72, characterized in that, The second information is carried in the A-Control field of the management frame.

77. 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-38.

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

79. 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-38.

80. 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-38.

81. 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-38.

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