Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: a first station sending a first frame, wherein the first frame comprises one or more of the following information: first information, which is used for indicating the type of the first frame; second information, which is used for indicating the type of reported third information; and fourth information, which is used for indicating that resource units for random access have been allocated to the station.

Description

Communication methods and communication equipment Technical Field

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

[0002] In related technologies, a station (STA) can send an initial control frame (ICF) to report or trigger the peer device to report certain types of information (such as a buffer status report (BSR) and / or unavailability information). However, the specific design of the ICF is required, and related technologies do not provide a clear solution. Summary of the Invention

[0003] This application provides a 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, comprising: a first station sending a first frame, the first frame including one or more of the following information: first information indicating the type of the first frame; second information indicating the type of reported third information; and fourth information indicating that a resource unit for random access has been allocated to the station.

[0005] In a second aspect, a communication method is provided, comprising: a second station receiving a first frame sent by a first station, the first frame including one or more of the following information: first information indicating the type of the first frame; second information indicating the type of reported third information; and fourth information indicating that a resource unit for random access has been allocated to the station.

[0006] Thirdly, a communication device is provided, the communication device being a first station, the first station comprising: a communication module for sending a first frame, the first frame including one or more of the following information: first information for indicating the type of the first frame; second information for indicating the type of reported third information; and fourth information for indicating that a resource unit for random access has been allocated to the station.

[0007] Fourthly, a communication device is provided, the communication device being a second station, the second station comprising: a communication module for receiving a first frame sent by a first station, the first frame including one or more of the following information: first information for indicating the type of the first frame; second information for indicating the type of reported third information; and fourth information for indicating that a resource unit for random access has been allocated to the station.

[0008] Fifthly, a communication device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the communication device to perform the methods of the first or second aspect.

[0009] In a sixth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program that causes a communication device to perform the methods described in the first or second aspect above.

[0010] In a seventh aspect, a computer program product is provided, the computer program product including a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform the method of the first aspect or the second aspect.

[0011] Eighthly, a chip is provided that includes a memory and a processor, the processor being able to call and run a computer program from the memory to implement the methods described in the first or second aspect above.

[0012] The first frame mentioned above can be an ICF (Integrated Function Frame). By defining the information carried in the ICF, the ICF can better achieve its corresponding functions. Attached Figure Description

[0013] Figure 1 is a schematic diagram of a wireless communication system applicable to embodiments of this application.

[0014] Figure 2 is a schematic diagram of the frame format of the buffer status report poll (BSRP) triggered frame.

[0015] Figure 3 is a schematic diagram of the frame format of the trigger frame.

[0016] Figure 4 is a schematic diagram of the format of the HE variant Common Info field.

[0017] Figure 5 is a schematic diagram of the format of the EHT variant Common Info field.

[0018] Figure 6 is a schematic diagram of the format of the Special User Info field.

[0019] Figure 7 is a schematic diagram of the format of the HE variant User Info field.

[0020] Figure 8 is a schematic diagram of the format of the spatial stream (SS) allocation field.

[0021] Figure 9 is a schematic diagram of the format of the random access-resource unit (RA-RU) information field.

[0022] Figure 10 is a schematic diagram of the format of the Trigger Dependent User Info field.

[0023] Figure 11 is a schematic diagram of the format of the EHT variant User Info field.

[0024] Figure 12 is a schematic diagram of the format of the SS Allocation field.

[0025] Figure 13 is a schematic diagram of the frame format of a Block Acknowledgment (BA) frame.

[0026] Figure 14 is a schematic diagram of the format of the BA Control field.

[0027] Figure 15 is a schematic diagram of the format of the BA information field.

[0028] Figure 16 is a schematic diagram of the TID information (Per AID TID Info) field for AID.

[0029] Figure 17 is a schematic diagram of the format of the Per AID TID Info field.

[0030] Figure 18 is a schematic diagram of another format of the Per AID TID Info field.

[0031] Figure 19 is a schematic diagram of the format of the AID TID Info field.

[0032] Figure 20 is a schematic diagram of the format of the access category indicator bitmap (ACI Bitmap) field.

[0033] Figure 21 is a schematic diagram of the frame format of the trigger frame.

[0034] Figure 22 is a schematic diagram of the format of the User Info field.

[0035] Figure 23 is a schematic flowchart of the communication method provided in an embodiment of this application.

[0036] Figure 24 is a schematic diagram of the frame structure of the first frame provided in an embodiment of this application.

[0037] Figure 25 is a schematic diagram of another frame structure of the first frame provided in the embodiment of this application.

[0038] Figure 26 is a schematic diagram of the frame structure of the second frame provided in an embodiment of this application.

[0039] Figure 27 is an example diagram of the communication process between the AP and STA provided in an embodiment of this application.

[0040] Figure 28 is another example diagram of the communication process between the AP and STA provided in the embodiments of this application.

[0041] Figure 29 is another example diagram of the communication process between the AP and STA provided in the embodiments of this application.

[0042] Figure 30 is another example diagram of the communication process between AP and STA provided in the embodiments of this application.

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

[0044] Figure 32 is a schematic structural diagram of a communication device provided in another embodiment of this application.

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

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

[0047] Communication system

[0048] The technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLANs), wireless fidelity (WIFI), high-performance radio local area networks (HIPELANs), wide area networks (WANs), 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).

[0049] Figure 1 shows a schematic diagram of a communication system applicable to embodiments of this application. Referring to Figure 1, the communication devices in the communication system 100 may include access point (AP) 111, AP 112, and station (STA) 121 and STA 122, wherein STA 121 can access the network through AP 111, and STA 122 can access the network through AP 112.

[0050] 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. Referring to 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.

[0051] In some implementations, the communication in the communication system 100 can be communication between the AP and the Non-AP STA, or communication between the Non-AP STA and the Non-AP STA, or communication between the STA and the peer STA. The peer STA can refer to the device that communicates with the STA. For example, the peer STA may be an AP or a Non-AP STA.

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

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

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

[0055] 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), then the AP can also be called an "AP MLD." If the multi-link device is a non-AP STA, then the non-AP STA can also be called a "Non-AP MLD."

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

[0057] 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 acts as an AP.

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

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

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

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

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

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

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

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

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

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

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

[0069] In-device coexistence (IDC)

[0070] Related technology 1 (Proposal 24 / 1558r2) proposes that a STA can report unavailability information (UI) caused by an IDC (Internet Data Center). Before STA1 becomes unavailable due to an IDC, the STA communicating with STA1 (hereinafter referred to as STA2) can send an ICF (Initial Control Message) to STA1. This ICF can be used to request STA1 to send unavailability information. This unavailability information can be carried in an initial control response (ICR) frame.

[0071] Based on the above scheme, related technology 1 proposes to use BSRP trigger frames as ICF frames and multi-site block acknowledgment (M-BA) frames as ICR frames.

[0072] Depending on the scenario, a BSRP trigger frame can request a trigger-based physical layer protocol data unit (TB PPDU) as a response. Alternatively, when a single-user (SU) operation occurs and a TB PPDU format is not required, the BSRP trigger frame can request a non-TB PPDU as a response.

[0073] When a BSRP trigger frame is used as an ICF, it can request unavailability information via an M-BA frame. Furthermore, the BSRP trigger frame can indicate whether the response format is TB format or non-high-throughput (repeated) PPDU (non-HT(dup)PPDU) format.

[0074] Figure 2 is a schematic diagram of the format of a BSRP trigger frame. The BSRP trigger frame shown in Figure 2 includes a Common Info field, a Special User Info field, zero or more User Info fields, and an optional padding field.

[0075] Related technology 2 (Proposal 24 / 1550r0) also studies ICF and ICR. Related technology 2 proposes that ICF needs to open a transmission opportunity (TXOP) for traditional STAs and ultra-high reliability (UHR) STAs. ICF should support extremely high throughput enhanced multi-link single radio (EHT EMLSR) STAs. For single users, Related technology 2 proposes that ICF needs to request an ICR in non-HT(dup) PPDU format to provide network allocation vector (NAV) protection for traditional STAs. Related technology 2 points out that BSRP trigger frames are currently used to request buffer status reports (BSRs), and BSRP trigger frames can be used as ICFs to request IDC feedback (unavailable information).

[0076] Trigger Frame

[0077] A non-multi-user request to send (MU-RTS) trigger frame allocates resources and requests the transmission of one or more TB PPDUs. The trigger frame also carries additional information required in response to the STA sending an HE TB PPDU, EHT TB PPDU, Non-HT PPDU, or Non-HT Duplicate PPDU.

[0078] The format of the trigger frame is shown in Figure 3. The meanings of the fields in Figure 3 are as follows: Frame Control carries control information such as frame type. Duration indicates the remaining TXOP duration. Receiver Address (RA) indicates the address of the STA receiving the trigger frame or its broadcast address. Transmitter Address (TA) indicates the address of the STA sending the trigger frame or its basic service set identifier (BSSID). The Common Info field of the trigger frame can be interpreted in several ways. For example, a non-EHT non-AP HE STA interprets the Common Info field as an HE variant Common Info field (as shown in Figure 4). If B54 and B55 in the Common Info field are equal to 1, the non-AP EHT STA interprets the Common Info field as an HE variant Common Info field; otherwise, the non-AP EHT STA interprets the Common Info field as an EHT variant Common Info field (as shown in Figure 5).

[0079] The User Info field has three variants: Special User Info, HE variant User Info, and EHT variant User Info.

[0080] All User Info fields (including the Special User Info field) in the User Info List field of the trigger frame have the same length (unless the trigger frame is a MU-BAR trigger frame).

[0081] The User Info field sent to a non-AP STA can be either an HE variant or an EHT variant. If B39 of the User Info field is set to 0 and B54 of the Common Info field is set to 1 in the trigger frame, then the User Info field is the HE variant for a non-AP EHT STA; otherwise, the User Info field is the EHT variant. B39 of the HE variant User Info field is reserved for non-EHT HE STAs. The EHT AP sets B39 of the HE variant User Info field to 0, and it is the PS160 subfield of the EHT variant User Info field.

[0082] Table 1 defines the valid combinations of B54 and B55 in the Common Info field, B39 in the User Info field, the presence of the Special User Info field in the Trigger frame, variations of the User Info field, and the corresponding TB PPDU types.

[0083] Table 1

[0084] The format of the Special User Info field is shown in Figure 6.

[0085] The Special User Info field is a User Info field that does not carry user-specific information but carries extended public information not provided in the Common Info field. If a Special User Info field exists, it follows the Common Info field in the triggering frame and carries information from the U-SIG field of the requested EHT TB PPDU.

[0086] The AID12 field in the Special User Info field has a value of 2007, indicating that this User Info field is a Special User Info field. The PHY Version Identifier field is used to indicate the PHY version of the requested TB PPDU (non-HE TB PPDU). For EHT, the PHY Version Identifier field is set to 0, and values ​​between 1 and 7 are reserved.

[0087] The UL Bandwidth Extension field, together with the UL Bandwidth (UL BW) field in the Common Info field, indicates the bandwidth of the requested TB PPDU.

[0088] The EHT Spatial Reuse 1 field carries the value from the Spatial Reuse 1 field to be included in the U-SIG field of the EHT TB PPDU.

[0089] The EHT Spatial Reuse 2 field carries the value from the Spatial Reuse 2 subfield to be included in the U-SIG field of the EHT TB PPDU.

[0090] The U-SIG Disregard And Validate field carries the values ​​from the Ignore and Validate fields to be included in the U-SIG field of the requested EHT TB PPDU.

[0091] The presence and length of the Trigger Dependent User Info field in the Special User Info field depend on the variant of the trigger frame. When present, the length and subfields of the Trigger Dependent User Info field are specified as follows: a length of one octet, with all subfields retained in both the Basic Trigger frame and the BFRP Trigger frame; or a length of four octets, with all subfields except the BAR type subfield retained in the MU-BAR trigger frame. The BAR type subfield is set to indicate the compressed BAR in the MU-BAR trigger frame.

[0092] If the Special User Info field is included in other trigger frame variants, then the Trigger Dependent User Info subfield does not exist in the Special User Info field.

[0093] The format of the HE variant User Info field is shown in Figure 7.

[0094] Referring to Figure 7, the AID12 in the HE variant User Info field is used to indicate the association ID (AID) of an associated site or a non-associated site.

[0095] The RU Allocation field, together with the UL BW field in the Common Info field, identifies the size and location of the RU.

[0096] The uplink forward error correction coding type (UL FEC Coding Type) field indicates the coding type of the requested HE TB PPDU. A UL FEC Coding Type field set to 0 indicates binary convolutional code (BCC), and a UL FEC Coding Type field set to 1 indicates low-density parity check (LDPC).

[0097] The uplink high efficiency modulation and coding scheme (UL HE-MCS) field indicates the HE-MCS requested for the HE TB PPDU.

[0098] The uplink dual carrier modulation (UL DCM) field indicates the DCM of the requested HE TB PPDU. A UL DCM field set to 1 indicates that DCM is used in the requested HE TB PPDU. A UL DCM field set to 0 indicates that DCM is not used in the requested HE TB PPDU. If the uplink space-time block coding (UL STBC) field in the Common Info field is set to 1, then the UL DCM field is set to 0.

[0099] The SS Allocation field indicates the spatial stream of the requested HE TB PPDU, as shown in Figure 8. The Starting Spatial Stream field indicates the starting spatial stream, and its value is set to the starting spatial stream minus 1. The Number Of Spatial Streams field indicates the number of spatial streams, and its value is set to the number of spatial streams minus 1.

[0100] The RA-RU Information field represents RA-RU information, and its specific format is shown in Figure 9. The Number Of RA-RU field indicates the number of consecutive RUs allocated for uplink OFDMA-based random access (UORA). The value of the Number Of RA-RU field is equal to the number of consecutive RA-RUs minus 1.

[0101] The More RA-RU field is set to 1 to indicate that the RA-RU indicated by the AID12 subfield in this HE variant's User Information field will be allocated in subsequent trigger frames until the target wake time service period (TWT SP) of the trigger frame carrying this field ends. Otherwise, the More RA-RU field is set to 0. If the More TF field in the Common Info field is set to 0, the More RA-RU field is retained.

[0102] The UL Target Receive Power field indicates the power level of the uplink signal that the AP expects to receive from the STA. This power is measured at the AP's antenna connector and averaged across the assigned RU.

[0103] For the Trigger Dependent User Info field, the format of the Trigger Dependent User Info differs in different trigger frames. The format of the Trigger Dependent User Info in the Basic Trigger frame is shown in Figure 10.

[0104] Referring to Figure 10, the MPDU MU Spacing Factor field is used to calculate the value multiplied by the minimum MPDU starting interval. The TID Aggregation Limit field indicates the number of medium access control protocol data units (MPDUs) allowed in the A-MPDU carried in the HE TB PPDU, and the maximum number of traffic identifiers (TIDs) that the STA can aggregate in the aggregate (A)-MPDU.

[0105] The preferred access category (Preferred AC) field indicates the lowest AC recommended for aggregating the MPDU in the A-MPDU contained in the response to the trigger frame.

[0106] The format of the EHT variant User Info field is shown in Figure 11.

[0107] Referring to Figure 11, the AID12 field is used to indicate the AID of an associated STA or a non-associated STA. The RU Allocation field, together with the UL BW field in the Common Info field, the UL BW Extension field in the Special User Info field, and the PS160 field in the EHT variant User Info field, identifies the size and location of the RU or Multi-RU (MRU).

[0108] The UL FEC Coding Type field indicates the encoding type of the requested EHT TB PPDU. A UL FEC Coding field setting of 0 indicates BCC, and a setting of 1 indicates LDPC.

[0109] The UL EHT-MCS field indicates the EHT-MCS for the requested EHT TB PPDU.

[0110] The SS Allocation field indicates the spatial stream of the requested EHT TB PPDU, as shown in Figure 12. The Starting Spatial Stream field represents the starting spatial stream. The value of the Starting Spatial Stream field is set to the starting spatial stream minus 1, and the maximum value of the Starting Spatial Stream field is 7. Values ​​above 7 in the Starting Spatial Stream field are reserved for STAs. If no corresponding RU or MRU has been allocated for multi-user multiple-input multiple-output (MU-MIMO), the Starting Spatial Stream subfield is set to 0.

[0111] The Number Of Spatial Streams field indicates the number of spatial streams, and its value is set to the number of spatial streams minus 1. The maximum value of the Number Of Spatial Streams field is 3.

[0112] The UL Target Receive Power field indicates the power level of the uplink signal that the AP expects to receive from the STA. This power is measured at the AP's antenna connector and averaged across the assigned RU.

[0113] If the size of the RU or MRU is less than or equal to 2 × 996 subcarriers, the PS160 subfield is set to 0 to indicate that the RU or MRU allocation applies to the primary 160MHz channel. The PS160 subfield is set to 1 to indicate that the RU or MRU allocation applies to the secondary 160MHz channel. Otherwise, the PS160 subfield is used together with the RU allocation field to indicate the RU or MRU index.

[0114] The Trigger Dependent User Info field is the same as the Trigger Dependent User Info in the HE variant User Info.

[0115] Block acknowledgment (BlockAck) frame

[0116] The BlockAck frame is a control frame used to perform batch acknowledgments of MAC service data units (MSDUs), and its frame format is shown in Figure 13.

[0117] Referring to Figure 13, the Frame Control field carries control information such as frame type. The Duration field indicates the remaining TXOP duration. The RA field indicates the MAC address of the STA receiving the BlockAck frame. The TA field indicates the MAC address of the STA sending the BlockAck frame. The format of the BA Control field is shown in Figure 14. The BA Type indicates a variant of the BlockAck frame, as shown in Table 2.

[0118] Table 2 Encoding of BlockAck Frame Variants

[0119] The EDMG STA sets the No Memory Kept field to 1 to indicate that the free storage space indicated in the last receiver buffer capacity (RBUFCAP) field may not be reserved at the beginning of the next frame exchange sequence; otherwise, if the No Memory Kept field is set to 0, the receiver reserves the free storage space indicated by the RBUFCAP field for the next frame exchange sequence of the corresponding TID. If transmitted by a non-EDMG STA, the No Memory Kept field is reserved.

[0120] For EDMG STAs, the Memory Configuration Tag field indicates one of 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.

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

[0122] The meaning of the TID_INFO subfield of the BA Control field depends on the BlockAck frame variant type.

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

[0124] The TID_INFO subfield of the BA Control field of a Compressed BlockAck frame contains the TID that sent this BlockAck frame.

[0125] The format of the BA Information field in a Compressed BlockAck frame is shown in Figure 15. The Block Ack Starring Sequence Control indicates the sequence number of the first MSDU or A-MSDU acknowledged in this BlockAck frame. Each bit in the BlockAck Bitmap indicates whether the corresponding MSDU or A-MSDU was successfully received; a value of 1 indicates success, and a value of 0 indicates failure. The TID_INFO subfield of the BA Control field in a Multi-STA BlockAck frame is reserved. The BA Information field of a Multi-STA BlockAck frame contains one or more Per AID TID Info fields, the definitions of which are shown in Figure 16.

[0126] When the AID TID Info field is not equal to 2045, the format of the Per AID TID Info field is shown in Figure 17.

[0127] When the AID TID Info field equals 2045, the format of the Per AID TID Info field is shown in Figure 18.

[0128] The format of the AID TID Info field is shown in Figure 19.

[0129] Buffer status report (BSR)

[0130] Referring to Figure 20, the access category indicator bitmap (ACI Bitmap) field indicates the access category of the reported cache status.

[0131] The Delta TID, along with the value of the ACI Bitmap field, indicates the number of TIDs for the cached state that the STA is reporting.

[0132] The ACI High field indicates the ACI of the AC of the BSR as indicated in the Queue Size High field.

[0133] The Scaling Factor field indicates the unit of the Queue Size High and Queue Size High fields, in octet bytes.

[0134] The Queue Size High field, in units of Scaling Factor, indicates the amount of buffered data sent to the AC identified by the ACI High field at the STA identified by the frame receive address (a frame containing the BSR Control subfield).

[0135] The Queue Size All field, in units of Scaling Factor, indicates the amount of buffered data sent to the AC, identified by the ACI Bitmap field, to the STA identified by the frame receive address (a frame containing the BSR Control subfield).

[0136] Non-AP STAs send BSRs to assist their APs in allocating UL MU resources. Non-AP STAs can send BSRs implicitly (unsolicited BSRs) in the Quality of Service (QoS) control field or the BSR control subfield of any frame transmitted to the AP, or explicitly in any frame sent to the AP in response to a BSRP trigger frame (requested BSR). The buffer status reported in the QoS control field consists of the queue size value for a given TID (see 9.2.4.5.6 (Queue Size Subfield)). The buffer status reported in the BSR control field consists of the ACI bitmap, incremental TID, high-priority AC, and two queue sizes (see 9.2.4.7.4 (BSR Control)).

[0137] The AP can also request its BSR from one or more associated non-AP STAs by sending a BSRP trigger frame (see 9.3.1.22.6 (BSRP Trigger Frame Format)). The way a non-AP STA responds to a requested BSR can be defined as follows: If the trigger frame contains the 12 least significant bits (LSB) of the non-AP STA's AID in any user information field, the non-AP STA receiving the BSRP trigger frame should generate an HE TB PPDU according to the rules defined in 26.5.2.3 (UL MU Operation Behavior of Non-AP STAs); otherwise, if the non-AP STA's buffer is not empty and the non-AP STA supports the UORA procedure, it can access the RA-RU according to the rules defined in 26.5.4 (Based on UORA) and generate an HE TB PPDU when the trigger frame contains one or more RA-RUs.

[0138] RA-RU Indication

[0139] Figure 21 shows the format of the trigger frame. This trigger frame includes a User Info field. The format of this User Info field is shown in Figure 22. The AID12 value in the User Info field can be 0 or 2045 to indicate the RA-RU, as shown in Table 3.

[0140] Table 3 AID12 Field Encoding

[0141] In related technologies, ICF can be used to report or trigger the peer device to report certain types of information, such as the unavailability information and / or BSR mentioned above (e.g., using a BSRP trigger frame as an ICF). However, the specific design of ICF is required, and related technologies do not provide a clear solution. Furthermore, while related technologies mention using a BSRP trigger frame as an ICF frame to request unavailability information from the peer device, they do not consider compatibility issues with traditional STAs in UORA scenarios.

[0142] For example, in many scenarios, compared to allocating a designated RU and allowing the STA to send ICR frames in a non-contention-based manner, the AP allocating a RA-RU and allowing the STA to send ICR frames in a contention-based manner offers a gain.

[0143] For example, in the following scenario, the AP allocates RA-RUs to allow STAs to send ICR frames in a contention-based manner, which has a significant gain:

[0144] The number of STAs in the BSS is relatively large, and the resources for uplink TB transmission are relatively limited. The AP needs to send trigger frames two or more times to traverse all STAs.

[0145] The AP has insufficient knowledge of the STA's status. For example, when the AP sends an ICF frame, some STAs are in a dormant state and some are in an active state. When the AP sends an ICF frame, some STAs are ready (or have) unavailable information and some STAs are not ready (or do not have) unavailable information. When the AP sends an ICF frame, some STAs are on the BSS primary channel and some STAs are on the non-primary channel access (NPCA) primary channel. When the AP sends an ICF frame, some STAs are within the BSS coverage area and some STAs have left the BSS coverage area.

[0146] When the AP requests unavailable information from some STAs in a TB manner, it gives other STAs the opportunity to proactively report it, which helps reduce internal interference and ensures fairness for STAs.

[0147] However, when a UHR AP allocates one or more RA-RUs in a BSRP trigger frame, allowing STAs to compete for the channel in response to ICR frames via UORA, if the UHR AP still uses a value of 0 or 2045 in the AID12 subfield to indicate the RA-RU (see Table 3 above), it can mislead traditional STAs (such as HE / EHT STAs) within the same BSS. This is because traditional STAs can still successfully identify the BSRP trigger frame and the User Info field with a value of 0 or 2045 in the AID12 subfield. In this situation, traditional STAs will mistakenly believe that the AP allocated RA-RUs to request BSR feedback, so they will compete for RA-RU resources via UORA to send a BSR to the AP. This can lead to traditional STAs preempting RA-RU resources, and UHR STAs may not be able to acquire the RUs, thus failing to respond to ICR frames in a timely manner. The UHR AP, which originally requested an ICR frame carrying unavailability information, ultimately receives a QoS Null frame carrying a BSR.

[0148] To address at least one of the aforementioned problems, embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0149] Figure 23 is a schematic flowchart of the communication method provided in an embodiment of this application. The method shown in Figure 23 is described from the perspective of the interaction between the first STA and the second STA. The first STA mentioned here can be, for example, an AP, and the second STA can be a non-AP STA. As an example, the second STA is a UHR STA. Of course, the second STA can also be a traditional STA, such as an EHT STA, an HT STA, etc. Alternatively, in some implementations, the first STA can be a non-AP STA, and the second STA can be an AP.

[0150] Referring to Figure 23, in step S2310, the first STA sends the first frame.

[0151] In some implementations, the first frame can be used to trigger one or more second STAs to transmit third information (such as a BSR and / or unavailability information). Accordingly, upon receiving the first frame, the second STA can send a response frame to the first STA. This response frame may include the third information (such as a BSR and / or unavailability information). For example, the first STA can be an AP, and the second STA can be a non-AP STA. The AP can send the first frame to the non-AP STA to trigger the non-AP STA to send the third information (such as a BSR and / or unavailability information).

[0152] In some implementations, the first frame can be used to report third information (such as BSR and / or unavailability information). For example, the first STA can be a non-AP STA, the second STA can be an AP, and the non-AP STA can send third information (such as BSR and / or unavailability information) to the AP.

[0153] This application does not specifically limit the type of third information in its embodiments. In some implementations, the third information may include BSR and / or unavailability information. The unavailability information mentioned here may refer to IDC-related unavailability information, that is, unavailability information caused by IDC. Unavailability information may indicate the unavailability time of the STA (e.g., unavailability time caused by IDC). For example, unavailability information is used to indicate the STA's Unavailability Target Start Time (which may be carried in the Unavailability Target Start Time field) and / or Unavailability Duration (which may be carried in the Unavailability Duration field). The Unavailability Target Start Time may be defined as the timing synchronization function (TSF) time when the STA is unavailable.

[0154] In some implementations, the first frame can be an ICF (Initial Frame Frame). This application does not specifically limit the type of ICF; for example, it can be a BSRP trigger frame (i.e., using a BSRP trigger frame as an ICF).

[0155] The first frame mentioned above may include one or more of the following: first information (information related to the type of the first frame), second information (information related to the type of the third information), and fourth information (information related to the resource element used for random access). The above information will be described in detail below. It should be noted that the first frame may include one of the first, second, and fourth information, or two of the first, second, and fourth information (such as including both the second and fourth information simultaneously, or both the first and second information simultaneously, or both the first and fourth information simultaneously), or all of the first, second, and fourth information simultaneously.

[0156] I. The first frame includes the first information.

[0157] First information can be used to indicate the type of the first frame. In some implementations, the first information may include multiple values ​​(or multiple candidate values), with different values ​​corresponding to different types of the first frame. For example, the first information may include one or more of a first value, a second value, and a third value. The first value indicates that the first frame is used to request information of a first type, or in other words, the first value indicates that the first frame is a frame that requests information of the first type. The second value indicates that the first frame is used to request information of a second type, or in other words, the second value indicates that the first frame is a frame that requests information of the second type. The third value indicates that the first frame is used to request information of multiple types, including information of the first type and information of the second type, or in other words, the third value indicates that the first frame is a frame that requests information of all these multiple types. As an example, the first information includes a first value and a third value, where the first value is 0 and the third value is 1, or the first value is 1 and the third value is 0.

[0158] This application embodiment does not specifically limit the first type of information and the second type of information mentioned above, and can set them according to actual needs. In some implementations, the first type of information includes BSR, and the second type of information includes unavailable information. In this case, the first information can be used to indicate that the first frame is one of the following: a frame for requesting BSR, a frame for requesting unavailable information, a frame for requesting BSR or unavailable information, or a frame for requesting both BSR and unavailable information. For example, the first information includes a value 1 (e.g., 0 or 1) and a value 2 (e.g., 1 or 0), where value 1 indicates that the first information is used to request BSR, and value 2 indicates that the first information is used to request unavailable information and / or BSR.

[0159] Some implementations mentioned earlier suggest that the first frame can be an ICF (Independent Frame Request). In these implementations, the first information can be used to indicate the type of the ICF. For example, the first information can be used to indicate that the first frame is one of the following: an ICF for requesting a BSR (Browser Request Request), an ICF for requesting unavailable information, an ICF for requesting either a BSR or unavailable information, or an ICF for requesting both a BSR and unavailable information. For example, the first information includes a value 1 (e.g., 0 or 1) and a value 2 (e.g., 1 or 0), where value 1 indicates that the first information is an ICF for requesting a BSR, and value 2 indicates that the first information is an ICF for requesting both unavailable information and / or a BSR.

[0160] Some implementations mentioned earlier suggest that the first frame can be a BSRP trigger frame. In these implementations, the first information can be used to indicate the type of the BSRP trigger frame. For example, the first information can be used to indicate that the BSRP trigger frame is one of the following: a BSRP trigger frame for requesting a BSR, a BSRP trigger frame for requesting unavailable information, a BSRP trigger frame for requesting either a BSR or unavailable information, or a BSRP trigger frame for requesting both a BSR and unavailable information. For example, the first information includes a value 1 (e.g., 0 or 1) and a value 2 (e.g., 1 or 0), where value 1 indicates that the first information is a BSRP trigger frame for requesting a BSR, and value 2 indicates that the first information is a BSRP trigger frame for requesting both unavailable information and / or a BSR.

[0161] Some implementations mentioned earlier suggest that the first frame can be a BSRP trigger frame used as an ICF. In these implementations, the first information can be used to indicate the type of BSRP trigger frame when used as an ICF. For example, the first information can be used to indicate that the BSRP trigger frame is one of the following: a BSRP trigger frame for requesting a BSR, a BSRP trigger frame for requesting unavailable information, a BSRP trigger frame for requesting either a BSR or unavailable information, or a BSRP trigger frame for requesting both a BSR and unavailable information.

[0162] This application does not specifically limit the location of the first information in the first frame. For example, the first information can be located in the Common Info field of the first frame. Figures 24 and 25 show two examples of the frame format of the first frame. Referring to Figure 24 or Figure 25, the first frame is an ICF, which is derived from the trigger frame shown in Figure 2. Referring to Figure 24 or Figure 25, the Common Info field of this ICF includes an ICF type field, which can be used to carry the first information mentioned above. The ICF type field indicates different frame types when the BSRP trigger frame is used as an ICF frame, and the specific values ​​are shown in Table 4.

[0163] Table 4 ICF Types

[0164] II. The first frame includes the second information.

[0165] The second information can be used to indicate the type of third information to be reported. For example, if the first frame is used to trigger one or more second STAs to report third information, the second information can be used to indicate the type of third information that the one or more second STAs need to report. Similarly, the second information can indicate the type of third information that the first STA actively reports.

[0166] For example, the second information indicates that the type of the third information includes one of the following: BSR, unavailable information, or BSR and unavailable information. Therefore, the embodiments of this application can achieve simultaneous reporting of unavailable information and BSR, thereby reducing signaling overhead. Taking the first frame as a BSRP trigger frame, and this BSRP trigger frame as an ICF, for example, the BSRP trigger frame can carry the second information, thereby achieving simultaneous reporting of unavailable information and BSR.

[0167] Alternatively, the second information can be used to indicate a variant frame type of the first frame. For example, the second information can be used to indicate that the first frame is a frame used to trigger the reporting of a BSR, a frame used to trigger the reporting of unavailable information, or a frame used to trigger both the reporting of a BSR and unavailable information.

[0168] This application does not specifically limit the scope of the second information in its embodiments. In some implementations, the first frame includes one or more User Info fields, and the second information can correspond to all STAs indicated by those one or more User Info fields. That is, the second information can indicate the type of third information that each second STA triggered by the first frame needs to report. In other implementations, the second information can correspond to one second STA indicated by those one or more User Info fields. That is, the second information can indicate the type of third information that a second STA triggered by the first frame needs to report.

[0169] In some implementations, the first frame may include a Common Info field, and the second information may be located in that Common Info field.

[0170] Taking the first frame as an example of the ICF shown in Figure 24, the common information fields of this first frame include the Report Type field. This Report Type field is used to indicate the variant frame type of the BSRP trigger frame, or to indicate the type of information that the STA needs to report, as indicated by AID12 in all user information fields of the User Info List. The specific values ​​are shown in Table 5.

[0171] Table 5 Reporting Types

[0172] In addition to being carried in the Common Info field, in some implementations, the first frame may include the User Info field, and the second information may be located in the User Info field.

[0173] Taking the first frame of the ICF shown in Figure 25 as an example, the user information field of this first frame includes a reporting type field. This reporting type field is used to indicate the type of information that a specific STA needs to report, as indicated by the AID12 field in the User Info field containing this field. A value of 1 in this reporting type field indicates reporting unavailable information, and a value of 0 indicates reporting both unavailable information and BSR; or, a value of 0 in this reporting type field indicates reporting unavailable information, and a value of 1 indicates reporting both unavailable information and BSR.

[0174] III. The first frame includes the fourth information.

[0175] The fourth piece of information indicates that a resource unit (RU) for random access has been allocated to the STA. The STA mentioned here can be some or all of the one or more second STAs triggered by the first frame. The RU for random access can include one or more RUs. Further, in some implementations, the RU for random access can be one or more consecutive RUs.

[0176] The fourth information may be used to indicate that an RU for random access has been assigned to an associated STA of the first STA; and / or, the fourth information may be used to indicate that an RU for random access has been assigned to a non-associated STA of the first STA.

[0177] In some implementations, the first frame may include a User Info field, and the fourth information may indicate that the User Info field has assigned a RU for random access to the STA (associated STA and / or unassociated STA).

[0178] The fourth piece of information can be an AID. For example, the first frame may include a User Info field, which may include an AID12 field, and the fourth piece of information may be carried in the AID12 field.

[0179] As mentioned earlier, if the value of the association identifier is 0 and / or 2045, traditional STAs may be misled into thinking that the first frame is used to trigger the STA to report BSR via UORA. Therefore, the value of AID provided in this application embodiment can be different from 0 and / or 2045, thereby avoiding the above-mentioned misunderstanding.

[0180] In some implementations, the value of AID can include any value other than 0 and 2045 from 0 to 4095. In some implementations, the value of AID can be 1 to 2007, 2008 to 2044, or 2047 to 4094.

[0181] The AID can have a fourth value and / or a fifth value. The fourth value indicates that a RU for random access has been assigned to an associated STA of the first STA. The fifth value indicates that a RU for random access has been assigned to a non-associated STA of the first STA. The fourth value can be 1 to 2007, 2008 to 2044, or 2047 to 4094; and / or, the fifth value can be 1 to 2007, 2008 to 2044, or 2047 to 4094. For example, the fourth value can be 2008 and the fifth value can be 2044. Alternatively, the fourth value can be 2009 and the fifth value can be 2047.

[0182] In some implementations, the fourth information can be located in the User Info field. For example, the fourth information can be carried in the AID field (such as the AID12 field) of the User Info field. Accordingly, the fourth value mentioned above can indicate that the User Info field has allocated a RU for random access to an associated STA of the first STA, and the fifth value can indicate that the User Info field has allocated a RU for random access to a non-associated STA of the first STA.

[0183] Furthermore, in some implementations, the fourth and / or fifth values ​​can be used when the first frame is an ICF (such as a BSPR trigger frame). That is, when the first frame is an ICF, the fourth value can be used to indicate that the User Info field has allocated a RU for random access to an associated STA of the first STA, and the fifth value can be used to indicate that the User Info field has allocated a RU for random access to a non-associated STA of the first STA. Additionally, in some implementations, the fourth value can be a reserved value when the first frame is not an ICF; and / or, the fifth value can be a reserved value when the first frame is not an ICF.

[0184] In addition to the fourth and fifth values, in some implementations, the AID field may also include a sixth and / or a seventh value. The sixth value is used to indicate that the User Info field has assigned a RU for random access to an associated STA of the first STA when the first frame is not an ICF. The seventh value is used to indicate that the User Info field has assigned a RU for random access to a non-associated STA of the first STA when the first frame is not an ICF. For example, the sixth value is 0; and / or, the seventh value is 2045. Furthermore, in some implementations, the sixth value (e.g., 0) can be a reserved value when the first frame is an ICF; and / or, the seventh value (e.g., 2045) can be a reserved value when the first frame is an ICF.

[0185] Furthermore, in some implementations, it can be specified that when the first frame is ICF, the value of the AID field is not equal to the sixth and / or seventh value. For example, when the first frame is ICF, the value of the AID field is not equal to 0 and / or 2045.

[0186] The following explanation uses the ICF (BSRP Trigger Frame) shown in Figure 24 or Figure 25 as an example. The ICF shown in Figure 24 or Figure 25 includes a User Info field, which includes an AID12 field. One or more specific values ​​can be selected from the range of values ​​for the AID12 field, and these specific values ​​can be defined with special meanings. For example, an integer value (e.g., 2008) can be selected from the values ​​1–2007, 2008–2044, or 2047–4094. This value instructs the User Info field containing the AID12 field to allocate one or more consecutive RA-RUs to the associated STA for requesting unavailability information from the peer STA via the BSRP trigger frame (or a variant of the BSRP trigger frame). (Unavailability information can be carried in an M-BA frame.) And / or, an integer value (e.g., 2044) can be selected from the values ​​1–2007, 2008–2044, or 2047–4094. This value indicates that the User Info field containing the AID12 field allocates one or more consecutive RA-RUs to the non-associated STA for requesting unavailability information from the peer STA via a BSRP trigger frame (or a variant of the BSRP trigger frame) (the unavailability information can be carried in an M-BA frame).

[0187] As an example, the AID12 field can be defined using the definition method shown in Table 6.

[0188] Table 6. Encoding Method of AID12 Field

[0189] As mentioned above, after sending the first frame to one or more second STAs, the first STA can receive a response frame to the first frame sent by the second STA, thereby receiving the third information reported by the second STA (such as BSR and / or unavailability information). The second frame can be called an ICR frame. The format and / or content of the second frame are illustrated in detail below.

[0190] In some implementations, the second frame can be an M-BA frame. Of course, the second frame can also be other types of response frames.

[0191] In some implementations, the second frame may contain fifth and / or sixth information. The fifth information can be used to indicate whether the second frame is an ICF response frame (i.e., whether the second frame is an ICR frame). The sixth information can be used to indicate the type of the third information. For example, the sixth information can be used to indicate that the type of the third information includes one of the following: BSR, unavailable information, or BSR and unavailable information.

[0192] Figure 26 shows an example of the frame format of the second frame (ICR frame). This ICR frame is modified from the M-BA frame, and compared to the traditional M-BA frame, the ICR frame adds the ICR field, the Report Type field, and the BSR field.

[0193] The ICR field is used to indicate whether the M-BA frame is used as an ICR frame. A value of 1 in the ICR field indicates that the M-BA frame is used as an ICR frame, and a value of 0 indicates that the M-BA frame is not used as an ICR frame. Alternatively, a value of 0 in the ICR field indicates that the M-BA frame is used as an ICR frame, and a value of 1 indicates that the M-BA frame is not used as an ICR frame.

[0194] The Report Type field indicates the type of reported data carried in the BlockAck Bitmap field within the Per AID TID Info field. Specific values ​​are shown in Table 7.

[0195] Table 7 Report Type

[0196] When the Report Type field is 0, the BlockAck Bitmap field contains the BSR field, but not the Unavailability Period Start Time and Unavailability Period Duration fields. When the Report Type field is 1, the BlockAck Bitmap field does not contain the BSR field, but contains the Unavailability Period Start Time and Unavailability Period Duration fields. When the Report Type field is 2, the BlockAck Bitmap field contains the BSR field, the Unavailability Period Start Time, and the Unavailability Period Duration fields. The meanings of the other fields in the BSR field can be found in the previous "BSR" section.

[0197] The embodiments of this application are described in more detail below with specific examples. It should be noted that the examples in Figures 27 to 30 are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific numerical values ​​or scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or variations based on the examples in Figures 27 to 30, and such modifications or variations also fall within the scope of the embodiments of this application.

[0198] Example 1:

[0199] As shown in Figure 27, Example 1 involves the interaction between a UHR AP and two associated UHR Non-AP STAs (AID12=1, AID12=2). The ICF frames sent by the UHR AP use the frame format shown in Figure 24.

[0200] In the first BSRP trigger frame sent by the UHR AP, ICF Type = 1, indicating that the frame is an ICF frame used to request Unavailability Info and / or BSR, and Report Type = 1, indicating that the frame requests to report Unavailability Info. Additionally, the UHR AP allocates two uplink resources, RU1 and RU2, in the ICF frame. The AID12 of the User Info field associated with RU1 is 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1. The AID12 of the User Info field associated with RU2 is 2, indicating that RU2 is allocated to the associated UHR Non-AP STA 2. Therefore, accordingly, STA1 and STA2 reply to the UHR AP with an ICR frame (based on the M-BA frame) carrying Unavailability Info, using RU1 and RU2 respectively.

[0201] In the second BSRP Trigger frame sent by the UHR AP, ICF Type = 1, indicating that this frame is an ICF frame used to request Unavailability Info and / or BSR, and Report Type = 0, indicating that this frame requests to report a BSR. Additionally, the UHR AP allocates two uplink resources, RU1 and RU2, in the ICF frame. The AID12 of the User Info field associated with RU1 is 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1. The AID12 of the User Info field associated with RU2 is 2, indicating that RU2 is allocated to the associated UHR Non-AP STA 2. Therefore, accordingly, STA1 and STA2 reply to the UHR AP with an ICR frame (based on the M-BA frame) carrying a BSR, using RU1 and RU2 respectively.

[0202] In the third BSRP Trigger frame sent by the UHR AP, ICF Type = 1, indicating that this frame is an ICF frame used to request Unavailability Info and / or BSR, and Report Type = 2, indicating that this frame requests to report BSR and Unavailability Info. Additionally, the UHR AP allocates two uplink resources, RU1 and RU2, in the ICF frame. The AID12 of the User Info field associated with RU1 is 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1. The AID12 of the User Info field associated with RU2 is 2, indicating that RU2 is allocated to the associated UHR Non-AP STA 2. Therefore, accordingly, STA1 and STA2 reply to the AP with an ICR frame (based on the M-BA frame) carrying BSR and UI, respectively, using RU1 and RU2.

[0203] Example 2:

[0204] The scenario in Example 2 is the same as that in Example 1. The difference is that the ICF frames sent by the UHR AP use the frame format shown in Figure 25.

[0205] Referring to Figure 28, in the first BSRP Trigger frame sent by the UHR AP, ICF Type = 1, indicating that this frame is an ICF frame used to request Unavailability Info and / or BSR. Additionally, the UHR AP allocates two uplink resources, RU1 and RU2, in the ICF frame. The User Info field associated with RU1 has AID12 = 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1, and Report Type = 1, indicating a request to report Unavailability Info. The User Info field associated with RU2 has AID12 = 2, indicating that RU2 is allocated to the associated UHR Non-AP STA 2, and Report Type = 0, indicating a request to report BSR. Therefore, accordingly, STA1 uses RU1 to reply with an ICR frame carrying the UI (based on the M-BA frame) to the UHR AP; STA2 uses RU2 to reply with an ICR frame carrying the BSR (based on the M-BA frame) to the UHR AP.

[0206] In the second BSRP Trigger frame sent by the UHR AP, ICF Type = 1, indicating that this frame is an ICF frame used to request Unavailability Info and / or BSR. Additionally, the UHR AP allocates two uplink resources, RU1 and RU2, in the ICF frame. The User Info field associated with RU1 has AID12 = 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1, and Report Type = 1, indicating a request to report Unavailability Info. The User Info field associated with RU2 has AID12 = 2, indicating that RU2 is allocated to the associated UHR Non-AP STA 2, and Report Type = 2, indicating a request to report BSR and Unavailability Info. Therefore, accordingly, STA1 uses RU1 to reply with an ICR frame carrying the UI (based on the M-BA frame) to the UHR AP; STA2 uses RU2 to reply with an ICR frame carrying both BSR and UI (based on the M-BA frame) to the UHR AP.

[0207] Example 3:

[0208] As shown in Figure 29, Example 3 involves the interaction of a UHR AP, two associated UHR Non-AP STAs (AID12=1, AID12=2), and an associated conventional Non-AP STA (AID12=3). The ICF frames sent by the UHR AP use the frame format defined in Figure 24.

[0209] The UHR AP first sends a MU-RTS trigger frame to three Non-AP STAs. The three Non-AP STAs reply with a CTS frame, and the UHR AP obtains a TXOP.

[0210] The ICF Type=1 in the BSRP trigger frame sent by the UHR AP indicates that the frame is an ICF frame used to request Unavailability Info and / or BSR, and the Report Type=1 indicates a request to report Unavailability Info. Additionally, the ICF frame allocates two resources, RU1 and RU2. The AID12 of the User Info field associated with RU1 is 1, indicating that RU1 is allocated to the associated UHR Non-AP STA 1; the AID12 of the User Info field associated with RU2 is 2008, indicating that RU2 is a RA-RU allocated to the associated STA in the ICF frame for use in a UORA-based manner.

[0211] Subsequently, the associated UHR Non-AP STA 1 identifies RU1 as the uplink transmission resource assigned to it, so it can directly use RU1 to reply with an M-BA frame carrying the STA's Unavailability Info without contention. The associated UHR Non-AP STA 2 does not identify the RU resource assigned to it, but it identifies RU2 indicated by AID=2008 as a RA-RU. Therefore, it can contentionably preempt RU2 based on the UORA mechanism and then use RU2 to reply with an ICR carrying the STA's Unavailability Info. The associated legacy Non-AP STA neither identifies the RU resource assigned to it nor recognizes RU2 indicated by AID=2008 as a RA-RU (this is because the standard specification followed by legacy STAs defines AID12=2008 as Reserved). Therefore, the associated legacy Non-AP STA cannot identify any available RU resources at this time and thus cannot reply with the BSRP trigger frame.

[0212] Example 4:

[0213] As shown in Figure 30, Example 4 involves a UHR AP, two unassociated UHR Non-AP STAs (unassociated UHR Non-AP STA 1 and unassociated UHR Non-AP STA 2), and one unassociated conventional Non-AP STA. The ICF frames transmitted by the UHR AP use the frame format defined in Figure 24.

[0214] The UHR AP sends an ICF frame triggered by a BSRP frame. The ICF frame has ICF Type=1, indicating it's an ICF frame used to request Unavailability Info and / or BSR, and Report Type=1, indicating a request to report Unavailability Info. Additionally, the ICF frame allocates three resources, RU1, RU2, and RU3. The AID12 of the User Info field associated with these three RUs is 2044, indicating that RU2 is a RA-RU allocated to a non-associated site for use in a UORA manner.

[0215] Both non-associative UHR Non-AP STA 1 and non-associative UHR Non-AP STA 2 can identify the RA-RUs (Reserved RUs) assigned to the non-associative STAs for transmitting Unavailability Info as indicated by AID12=2044. Therefore, based on the UORA mechanism, they randomly select RU1 and RU2 to reply with an ICR frame carrying Unavailability Info to the AP. However, non-associative traditional Non-AP STAs cannot identify RU1, RU2, and RU3 indicated by AID=2044 as RA-RUs (in the standard specifications followed by traditional sites, AID12=2044 means Reserved). Therefore, non-associative traditional Non-AP STAs cannot identify any available RU resources at this time and thus cannot reply with any frames.

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

[0217] Figure 31 is a schematic structural diagram of a communication device 3100 provided in an embodiment of this application. The communication device 3100 is a first STA, which includes a communication module 3110. The communication module 3110 is used to send a first frame, which includes one or more of the following information: first information indicating the type of the first frame; second information indicating the type of reported third information; and fourth information indicating that a resource unit for random access has been allocated to the station.

[0218] In this embodiment, the communication device 3100 can be used to execute some or all of the method steps performed by the first STA in the above method embodiments. The communication device 3100 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 3100.

[0219] In an optional embodiment, the communication module 3110 may be a transceiver 3330. The communication device 3100 may also include a processor 3310 and a memory 3320, as shown in FIG33.

[0220] Figure 32 is a schematic structural diagram of a communication device 3200 provided in an embodiment of this application. The communication device 3200 is a second STA, and the second STA includes a communication module 3210. The communication module 3210 is used to receive a first frame sent by a first station. The first frame includes one or more of the following information: first information, used to indicate the type of the first frame; second information, used to indicate the type of reported third information; and fourth information, used to indicate that resource units for random access have been allocated to the station.

[0221] In this embodiment, the communication device 3200 can be used to execute some or all of the method steps performed by the second STA 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.

[0222] In an optional embodiment, the communication module 3210 may be a transceiver 3330. The communication device 3200 may also include a processor 3310 and a memory 3320, as shown in FIG33.

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

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

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

[0226] The device 3300 may also include a transceiver 3330. The processor 3310 can communicate with other devices or chips via the transceiver 3330. For example, the processor 3310 can send and receive data with other devices or chips via the transceiver 3330.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0240] 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. This application does not limit this.

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

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

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

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

[0245] 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 communication method, characterized in that, include: The first station sends a first frame, which includes one or more of the following information: First information, used to indicate the type of the first frame; The second piece of information is used to indicate the type of the third piece of information to be reported; The fourth piece of information is used to indicate that resource units for random access have been allocated to the site.

2. The method according to claim 1, characterized in that, The third information includes one or more of the following: Buffer status report; Unavailable.

3. The method according to claim 1 or 2, characterized in that, The first frame includes a public information field, and the first information is located in the public information field.

4. The method according to any one of claims 1 to 3, characterized in that, The first information includes one or more of the following: The first value indicates that the first frame is used to request information of the first type; The second value indicates that the first frame was used to request a second type of information; The third value indicates that the first frame is used to request multiple types of information, including information of the first type and information of the second type.

5. The method according to claim 4, characterized in that: The first type of information includes buffer status reports; and / or, The second type of information includes unavailable information.

6. The method according to any one of claims 1 to 5, characterized in that, The first frame includes a public information field, and the second information is located in the public information field.

7. The method according to any one of claims 1 to 5, characterized in that, The first frame includes a user information field, and the second information is located in the user information field.

8. The method according to any one of claims 1 to 7, characterized in that, The second information is used to indicate that the type of the third information includes one of the following: Buffer status report; Unavailable information; Buffer status report and unavailability information.

9. The method according to any one of claims 1 to 8, characterized in that, The fourth piece of information is the association identifier.

10. The method according to claim 9, characterized in that, The fourth piece of information is located in the associated identifier field of the user information field.

11. The method according to claim 10, characterized in that, The value of the association identifier includes one or more of the following: The fourth value is used to indicate that, in the case that the first frame is an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The fifth value is used to indicate, when the first frame is an initial control frame, that the user information field has allocated resource units for random access to non-associated sites of the first site.

12. The method according to claim 11, characterized in that: The fourth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094; and / or, The fifth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094.

13. The method according to any one of claims 10 to 12, characterized in that, The association identifier field includes one or more of the following values: The sixth value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The seventh value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to non-associated sites of the first site.

14. The method according to claim 13, characterized in that, The third value is 0; and / or, the fourth value is 2045.

15. The method according to any one of claims 10 to 14, characterized in that, When the first frame is the initial control frame, the value of the associated identifier field is not equal to 0 and / or 2045.

16. The method according to any one of claims 1 to 15, characterized in that, The method further includes: The first station receives a response frame of the first frame sent by the second station, and the response frame contains the third information.

17. The method according to claim 16, characterized in that, The second frame is a multi-site block confirmation frame.

18. The method according to claim 16 or 17, characterized in that, The second frame includes one or more of the following information: The fifth piece of information is used to indicate whether the second frame is a response frame to the initial control frame; The sixth piece of information is used to indicate the type of the first piece of information.

19. The method according to any one of claims 1 to 18, characterized in that: The first frame is used to trigger one or more second stations to report the third information; or, The first frame is used to report the third information.

20. The method according to any one of claims 1 to 19, characterized in that, The first frame is the initial control frame.

21. The method according to any one of claims 1 to 20, characterized in that, The first frame is the BSRP (Block Buffer Status Report) polling trigger frame.

22. The method according to any one of claims 1 to 21, characterized in that, The first site is an access point (AP), and the second site is a non-AP site.

23. The method according to claim 22, characterized in that, The second site is an ultra-high reliability site.

24. A communication method, characterized in that, include: The second station receives a first frame sent by the first station, the first frame including one or more of the following information: First information, used to indicate the type of the first frame; The second piece of information is used to indicate the type of the third piece of information to be reported; The fourth piece of information is used to indicate that resource units for random access have been allocated to the site.

25. The method according to claim 24, characterized in that, The third information includes one or more of the following: Buffer status report; Unavailable.

26. The method according to claim 24 or 25, characterized in that, The first frame includes a public information field, and the first information is located in the public information field.

27. The method according to any one of claims 24 to 26, characterized in that, The first information includes one or more of the following: A first value is used to indicate that the first frame is used to request information of a first type; The second value is used to indicate that the first frame is used to request information of the second type; The third value is used to indicate that the first frame is used to request multiple types of information, including information of the first type and information of the second type.

28. The method according to claim 27, characterized in that: The first type of information includes buffer status reports; and / or, The second type of information includes unavailable information.

29. The method according to any one of claims 24 to 28, characterized in that, The first frame includes a public information field, and the second information is located in the public information field.

30. The method according to any one of claims 24 to 28, characterized in that, The first frame includes a user information field, and the second information is located in the user information field.

31. The method according to any one of claims 24 to 30, characterized in that, The second information is used to indicate that the type of the third information includes one of the following: Buffer status report; Unavailable information; Buffer status report and unavailability information.

32. The method according to any one of claims 24 to 31, characterized in that, The fourth piece of information is the association identifier.

33. The method according to claim 32, characterized in that, The fourth piece of information is located in the associated identifier field of the user information field.

34. The method according to claim 33, characterized in that, The value of the association identifier includes one or more of the following: The fourth value is used to indicate that, in the case that the first frame is an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The fifth value is used to indicate, when the first frame is an initial control frame, that the user information field has allocated resource units for random access to non-associated sites of the first site.

35. The method according to claim 34, characterized in that: The fourth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094; and / or, The fifth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094.

36. The method according to any one of claims 33 to 35, characterized in that, The association identifier field includes one or more of the following values: The sixth value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The seventh value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to non-associated sites of the first site.

37. The method according to claim 36, characterized in that, The third value is 0; and / or, the fourth value is 2045.

38. The method according to any one of claims 33 to 37, characterized in that, When the first frame is the initial control frame, the value of the associated identifier field is not equal to 0 and / or 2045.

39. The method according to any one of claims 24 to 38, characterized in that, The method further includes: The second station sends a response frame of the first frame to the first station, and the response frame contains the third information.

40. The method according to claim 39, characterized in that, The second frame is a multi-site block confirmation frame.

41. The method according to claim 39 or 40, characterized in that, The second frame includes one or more of the following information: The fifth piece of information is used to indicate whether the second frame is a response frame to the initial control frame; The sixth piece of information is used to indicate the type of the first piece of information.

42. The method according to any one of claims 24 to 41, characterized in that: The first frame is used to trigger one or more second stations to report the third information; or, The first frame is used to report the third information.

43. The method according to any one of claims 24 to 42, characterized in that, The first frame is the initial control frame.

44. The method according to any one of claims 24 to 43, characterized in that, The first frame is the BSRP (Block Buffer Status Report) polling trigger frame.

45. The method according to any one of claims 24 to 44, characterized in that, The first site is an access point (AP), and the second site is a non-AP site.

46. ​​The method according to claim 45, characterized in that, The second site is an ultra-high reliability site.

47. A communication device, characterized in that, The communication device is a first station, and the first station includes: A communication module is configured to send a first frame, the first frame including one or more of the following information: First information, used to indicate the type of the first frame; The second piece of information is used to indicate the type of the third piece of information to be reported; The fourth piece of information is used to indicate that resource units for random access have been allocated to the site.

48. The communication device according to claim 47, characterized in that, The third information includes one or more of the following: Buffer status report; Unavailable.

49. The communication device according to claim 47 or 48, characterized in that, The first frame includes a public information field, and the first information is located in the public information field.

50. The communication device according to any one of claims 47 to 49, characterized in that, The first information includes one or more of the following: A first value is used to indicate that the first frame is used to request information of a first type; The second value is used to indicate that the first frame is used to request information of the second type; The third value is used to indicate that the first frame is used to request multiple types of information, including information of the first type and information of the second type.

51. The communication device according to claim 50, characterized in that: The first type of information includes buffer status reports; and / or, The second type of information includes unavailable information.

52. The communication device according to any one of claims 47 to 51, characterized in that, The first frame includes a public information field, and the second information is located in the public information field.

53. The communication device according to any one of claims 47 to 51, characterized in that, The first frame includes a user information field, and the second information is located in the user information field.

54. The communication device according to any one of claims 47 to 53, characterized in that, The second information is used to indicate that the type of the third information includes one of the following: Buffer status report; Unavailable information; Buffer status report and unavailability information.

55. The communication device according to any one of claims 47 to 54, characterized in that, The fourth piece of information is the association identifier.

56. The communication device according to claim 55, characterized in that, The fourth piece of information is located in the associated identifier field of the user information field.

57. The communication device according to claim 56, characterized in that, The value of the association identifier includes one or more of the following: The fourth value is used to indicate that, in the case that the first frame is an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The fifth value is used to indicate, when the first frame is an initial control frame, that the user information field has allocated resource units for random access to non-associated sites of the first site.

58. The communication device according to claim 57, characterized in that: The fourth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094; and / or, The fifth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094.

59. The communication device according to any one of claims 56 to 58, characterized in that, The association identifier field includes one or more of the following values: The sixth value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The seventh value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to non-associated sites of the first site.

60. The communication device according to claim 59, characterized in that, The third value is 0; and / or, the fourth value is 2045.

61. The communication device according to any one of claims 56 to 60, characterized in that, When the first frame is the initial control frame, the value of the associated identifier field is not equal to 0 and / or 2045.

62. The communication device according to any one of claims 47 to 61, characterized in that, The communication module is also used for: The system receives a response frame to the first frame sent by the second station, and the response frame contains the third information.

63. The communication device according to claim 62, characterized in that, The second frame is a multi-site block confirmation frame.

64. The communication device according to claim 62 or 63, characterized in that, The second frame includes one or more of the following information: The fifth piece of information is used to indicate whether the second frame is a response frame to the initial control frame; The sixth piece of information is used to indicate the type of the first piece of information.

65. The communication device according to any one of claims 47 to 64, characterized in that: The first frame is used to trigger one or more second stations to report the third information; or, The first frame is used to report the third information.

66. The communication device according to any one of claims 47 to 65, characterized in that, The first frame is the initial control frame.

67. The communication device according to any one of claims 47 to 66, characterized in that, The first frame is the BSRP (Block Buffer Status Report) polling trigger frame.

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

69. The communication device according to claim 68, characterized in that, The second site is an ultra-high reliability site.

70. A communication device, characterized in that, The communication device is a second station, and the second station includes: The communication module is configured to receive a first frame sent by a first station, the first frame including one or more of the following information: First information, used to indicate the type of the first frame; The second piece of information is used to indicate the type of the third piece of information to be reported; The fourth piece of information is used to indicate that resource units for random access have been allocated to the site.

71. The communication device according to claim 70, characterized in that, The third information includes one or more of the following: Buffer status report; Unavailable.

72. The communication device according to claim 70 or 71, characterized in that, The first frame includes a public information field, and the first information is located in the public information field.

73. The communication device according to any one of claims 70 to 72, characterized in that, The first information includes one or more of the following: A first value is used to indicate that the first frame is used to request information of a first type; The second value is used to indicate that the first frame is used to request information of the second type; The third value is used to indicate that the first frame is used to request multiple types of information, including information of the first type and information of the second type.

74. The communication device according to claim 73, characterized in that: The first type of information includes buffer status reports; and / or, The second type of information includes unavailable information.

75. The communication device according to any one of claims 70 to 74, characterized in that, The first frame includes a public information field, and the second information is located in the public information field.

76. The communication device according to any one of claims 70 to 74, characterized in that, The first frame includes a user information field, and the second information is located in the user information field.

77. The communication device according to any one of claims 70 to 76, characterized in that, The second information is used to indicate that the type of the third information includes one of the following: Buffer status report; Unavailable information; Buffer status report and unavailability information.

78. The communication device according to any one of claims 70 to 77, characterized in that, The fourth piece of information is the association identifier.

79. The communication device according to claim 78, characterized in that, The fourth piece of information is located in the associated identifier field of the user information field.

80. The communication device according to claim 79, characterized in that, The value of the association identifier includes one or more of the following: The fourth value is used to indicate that, in the case that the first frame is an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The fifth value is used to indicate, when the first frame is an initial control frame, that the user information field has allocated resource units for random access to non-associated sites of the first site.

81. The communication device according to claim 80, characterized in that: The fourth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094; and / or, The fifth value belongs to 1 to 2007, 2008 to 2044, or 2047 to 4094.

82. The communication device according to any one of claims 79 to 81, characterized in that, The association identifier field includes one or more of the following values: The sixth value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to the associated sites of the first site. The seventh value is used to indicate that, in the case that the first frame is not an initial control frame, the user information field has allocated resource units for random access to non-associated sites of the first site.

83. The communication device according to claim 82, characterized in that, The third value is 0; and / or, the fourth value is 2045.

84. The communication device according to any one of claims 79 to 83, characterized in that, When the first frame is the initial control frame, the value of the associated identifier field is not equal to 0 and / or 2045.

85. The communication device according to any one of claims 70 to 84, characterized in that, The communication module is also used for: A response frame to the first frame is sent to the first station, and the response frame contains the third information.

86. The communication device according to claim 85, characterized in that, The second frame is a multi-site block confirmation frame.

87. The communication device according to claim 85 or 86, characterized in that, The second frame includes one or more of the following information: The fifth piece of information is used to indicate whether the second frame is a response frame to the initial control frame; The sixth piece of information is used to indicate the type of the first piece of information.

88. The communication device according to any one of claims 70 to 87, characterized in that: The first frame is used to trigger one or more second stations to report the third information; or, The first frame is used to report the third information.

89. The communication device according to any one of claims 70 to 88, characterized in that, The first frame is the initial control frame.

90. The communication device according to any one of claims 70 to 89, characterized in that, The first frame is the BSRP (Block Buffer Status Report) polling trigger frame.

91. The communication device according to any one of claims 70 to 90, characterized in that, The first site is an access point (AP), and the second site is a non-AP site.

92. The communication device according to claim 91, characterized in that, The second site is an ultra-high reliability site.

93. 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 to 23 or the method as described in any one of claims 24 to 46.

94. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as claimed in any one of claims 1 to 23 or the method as claimed in any one of claims 24 to 46.

95. 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 claimed in any one of claims 1 to 23 or the method as claimed in any one of claims 24 to 46.

96. 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 to 23 or the method as described in any one of claims 24 to 46.

97. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as claimed in any one of claims 1 to 23 or the method as claimed in any one of claims 24 to 46.

98. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 23 or the method as described in any one of claims 24 to 46.

Images