Wireless communication method and device

Abstract

Embodiments of the present application provide a wireless communication method and a device. A first STA reserves m1 frequency domain units in a first uplink transmission, and one or more other STAs having uplink delay-sensitive data to be transmitted report cache information of delay-sensitive data on the m1 frequency domain units, so that an AP can obtain the cache information of the uplink delay-sensitive data of the one or more other STAs in a TXOP obtained by the first STA by means of contention or a TXOP obtained by the AP by means of contention, thereby implementing timely transmission of event-driven uplink delay-sensitive data. The wireless communication method comprises: a first STA reserves m1 frequency domain units in a first uplink transmission, wherein the m1 frequency domain units are used for one or more other STAs having uplink delay-sensitive data to be transmitted to report cache information of delay-sensitive data, and m1 is a positive integer.

Description

Method and device for wireless communication TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication, and more particularly, to a method and device for wireless communication. BACKGROUND

[0002] In a wireless local area network (WLAN), for event-driven latency-sensitive traffic (which can also be referred to as low-latency traffic), the traffic is unpredictable and thus cannot be transmitted by pre-scheduling appropriate resources, how to improve the transmission performance of the latency-sensitive traffic is a problem to be solved.

[0003] SUMMARY

[0004] Embodiments of the present application provide a method and device for wireless communication, a first STA reserves m1 frequency domain units in a first uplink transmission, one or more other STAs that have uplink latency-sensitive data to be transmitted report buffer information of the latency-sensitive data on the m1 frequency domain units, so that the AP can obtain the buffer information of the uplink latency-sensitive data of the one or more other STAs in a TXOP contended by the first STA or a TXOP contended by the AP, and then the timely transmission of the event-driven uplink latency-sensitive data can be realized.

[0005] In a first aspect, a method for wireless communication is provided, the method comprising:

[0006] a first STA reserving m1 frequency domain units in a first uplink transmission; wherein the m1 frequency domain units are used for one or more other STAs that have uplink latency-sensitive data to be transmitted to report buffer information of the latency-sensitive data, and m1 is a positive integer.

[0007] In a second aspect, a method for wireless communication is provided, the method comprising:

[0008] a second STA reporting buffer information of latency-sensitive data on m1 frequency domain units.

[0009] wherein the m1 frequency domain units are frequency domain units reserved by a first STA in a first uplink transmission, and m1 is a positive integer.

[0010] In a third aspect, a method for wireless communication is provided, the method comprising:

[0011] an access point (AP) receiving a first uplink transmission of a first station (STA);

[0012] The first STA reserves m1 frequency domain units in the first uplink transmission, the m1 frequency domain units are used for one or more other STAs having uplink delay-sensitive data to report buffer information of delay-sensitive data, and m1 is a positive integer.

[0013] In a fourth aspect, a STA is provided, which is a first STA, configured to perform the method in the first aspect.

[0014] In particular, the STA comprises function modules for performing the method in the first aspect.

[0015] In a fifth aspect, a STA is provided, which is a second STA, configured to perform the method in the second aspect.

[0016] In particular, the STA comprises function modules for performing the method in the second aspect.

[0017] In a sixth aspect, an AP is provided, configured to perform the method in the third aspect.

[0018] In particular, the AP comprises function modules for performing the method in the third aspect.

[0019] In a seventh aspect, a STA is provided, which is a first STA, comprising a processor and a memory; the memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, so that the STA performs the method in the first aspect.

[0020] In an eighth aspect, a STA is provided, which is a second STA, comprising a processor and a memory; the memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, so that the STA performs the method in the second aspect.

[0021] In a ninth aspect, an AP is provided, comprising a processor and a memory; the memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, so that the AP performs the method in the third aspect.

[0022] In a tenth aspect, an apparatus is provided, configured to implement the method in any one of the first aspect to the third aspect.

[0023] In particular, the apparatus comprises a processor configured to invoke and run a computer program from a memory, so that a device installed with the apparatus performs the method in any one of the first aspect to the third aspect.

[0024] In an eleventh aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method in any one of the first aspect to the third aspect.

[0025] In a twelfth aspect, a computer program product is provided, comprising computer program instructions, which cause a computer to execute the method in any one of the first aspect to the third aspect.

[0026] In a thirteenth aspect, a computer program is provided, which, when running on a computer, causes the computer to execute the method in any one of the first aspect to the third aspect.

[0027] Through the above technical solution, the first STA reserves m1 frequency domain units in the first uplink transmission, and one or more other STAs with to-be-transmitted uplink latency-sensitive data report the cache information of the latency-sensitive data on the m1 frequency domain units, so that the AP can obtain the cache information of the uplink latency-sensitive data of the one or more other STAs in the TXOP competed by the first STA or the TXOP competed by the AP, and then the timely transmission of the event-driven uplink latency-sensitive data can be realized. BRIEF DESCRIPTION OF DRAWINGS

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

[0029] FIG. 2 is a schematic diagram of a subchannel puncturing provided by the present application.

[0030] FIG. 3 is a schematic diagram of a BSRP trigger frame provided by the present application.

[0031] FIG. 4 is a schematic diagram of a QoS null frame provided by the present application.

[0032] FIG. 5 is a schematic diagram of an NFRP trigger frame provided by the present application.

[0033] FIG. 6 is a schematic diagram of an NDP Feedback Report parameter set element provided by the present application.

[0034] FIG. 7 is a schematic diagram of an HE TB feedback NDP format provided by the present application.

[0035] FIG. 8 is a schematic flowchart of a method of wireless communication provided according to an embodiment of the present application.

[0036] FIGS. 9 to 15 are schematic diagrams of a first trigger frame provided according to an embodiment of the present application, respectively.

[0037] Figure 16 is a schematic diagram of carrying a transmission opportunity preemption indication in a BA frame according to an embodiment of the present application.

[0038] Figures 17 to 22 are schematic diagrams of the second trigger frame provided according to the embodiments of this application.

[0039] Figure 23 is a schematic diagram of an NDP provided according to an embodiment of this application.

[0040] Figures 24 to 33 are schematic diagrams of uplink transmission and reserved frequency domain units provided according to embodiments of this application.

[0041] Figure 34 is a schematic block diagram of an STA provided according to an embodiment of this application.

[0042] Figure 35 is a schematic block diagram of another STA provided according to an embodiment of this application.

[0043] Figure 36 is a schematic block diagram of an AP provided according to an embodiment of this application.

[0044] Figure 37 is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0045] Figure 38 is a schematic block diagram of an apparatus provided according to an embodiment of this application.

[0046] Figure 39 is a schematic block diagram of a communication system provided according to an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0048] The technical solutions of this application embodiment can be applied to various communication systems, such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems.

[0049] Please refer to Figure 1, which shows a schematic diagram of a wireless communication system provided in one embodiment of this application. As shown in Figure 1, the wireless communication system may include an access point (AP) and a station (STA).

[0050] In some scenarios, an AP can be called an AP STA, meaning that in a sense, an AP is also a type of STA. In other scenarios, a STA can be called a non-AP STA.

[0051] In some embodiments, a STA may include an AP STA and a Non-AP STA. Communication in the communication system can be between an AP and a Non-AP STA, between two Non-AP STAs, or between a STA and a peer STA. A peer STA can refer to a device communicating with the STA's counterpart. For example, a peer STA may be an AP or a Non-AP STA.

[0052] An access point (AP) acts as a bridge connecting wired and wireless networks. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. AP devices can be terminal devices (such as mobile phones) or network devices (such as routers) with wireless-fidelity (Wi-Fi) chips.

[0053] It should be understood that the role of a STA in a communication system is not absolute. For example, in some scenarios, when a mobile phone connects to a router, it is a Non-AP STA; when the mobile phone acts as a hotspot for other mobile phones, it plays the role of an AP.

[0054] AP and Non-AP STA can be devices used in vehicle networking, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0055] In some embodiments, the Non-AP STA can support the 802.11be standard. The Non-AP STA can also support various current and future 802.11 family of wireless LAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0056] In some embodiments, 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.

[0057] In the embodiments of this application, STA can be a mobile phone, tablet, computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, set-top box, wireless device in self-driving, vehicle communication device, wireless device in remote medical care, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city or smart home, wireless communication chip, ASIC (Application Specific Integrated Circuit), SOC (System on Chip), etc., that support WLAN / WIFI technology.

[0058] WLAN technology can support frequency bands including but not limited to: low frequency bands (2.4GHz, 5GHz, 6GHz) and high frequency bands (45GHz, 60GHz).

[0059] One or more links exist between the site and the access point. In some embodiments, the site and the access point support multi-band communication. For example, communication can occur simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands, or simultaneously on different channels within the same (or different) bands, improving communication throughput and / or reliability between devices. Such devices are commonly referred to as multi-band devices, or multi-link devices (MLDs), and sometimes also as multi-link entities or multi-band entities. A multi-link device can be an access point device or a site device. If the multi-link device is an access point device, it contains one or more access points (APs); if the multi-link device is a site device, it contains one or more non-AP STAs.

[0060] A multi-link device that includes one or more access points (APs) can be called an Access Point Multi-Link Device (AP MLD), while a multi-link device that includes one or more non-AP STAs can be called a Non-AP Multi-Link Device (Non-AP MLD).

[0061] In this embodiment of the application, an AP may include multiple APs, and a Non-AP may include multiple STAs. Multiple links may be formed between the APs in the AP and the STAs in the Non-AP, and data communication may be performed between the APs in the AP and the corresponding STAs in the Non-AP through the corresponding links.

[0062] An access point (AP) is a device deployed in a wireless local area network (WLAN) to provide wireless communication functionality to a station (STA). A station can include: User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication equipment, user agent, or user device. Optionally, a station can also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication functionality, computing device, or other processing device connected to a wireless modem, vehicle-mounted device, or wearable device; this application embodiment is not limited to these categories.

[0063] Optionally, both the site and access point support the IEEE 802.11 standard.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0065] It should be understood that the term "instruction" mentioned in the embodiments of this application 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.

[0066] The terminology used in the embodiments section of this application is for the purpose of explaining specific embodiments of this application only, and is not intended to limit this 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. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0067] It should be understood that "at least one or more" mentioned in the embodiments of this application can mean "one or more", and "positive integer" mentioned in the embodiments of this application can mean "values ​​such as 1, 2, 3, etc". "Non-negative integer" mentioned in the embodiments of this application can mean "values ​​such as 0, 1, 2, 3, etc". "Integer" mentioned in the embodiments of this application can mean "..., -3, -2, -1, 0, 1, 2, 3, ... etc". These can be replaced with any possible values ​​based on the requirements of the embodiments.

[0068] It should be understood that the figures and / or tables shown in the embodiments of this application are merely examples. Specifically, in some cases, some information contained in the figures and / or tables shown in the embodiments of this application may constitute an optional embodiment on its own. For example, each row or column in the table may constitute an optional embodiment on its own. This application does not limit this.

[0069] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0070] 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 STA and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

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

[0072] To facilitate a better understanding of the embodiments of this application, the resources reserved for low-latency transmission related to this application will be described.

[0073] Resources can be reserved for low-latency (LL) transmissions using a method similar to preamble puncturing. To handle low-latency traffic in a way that avoids collisions or interference and prevents waiting for transmission opportunities at other sites, specific scheduling methods can be employed: allocating resources under specific conditions and indicating that resource allocation information. An AP can indicate whether its subchannels are punctured or non-punctured within its operating bandwidth. Scheduling low-latency traffic to punctured channels is one approach; that is, using a defined punctured channel for event-driven low-latency (LL) traffic avoids collisions with ongoing non-low-latency (Non-LL) traffic.

[0074] To facilitate a better understanding of the embodiments of this application, the uplink orthogonal frequency division multiple access-based random access (UORA) mechanism related to this application will be described.

[0075] The AP should indicate the range of the Orthogonal Frequency Division Multiple Access (OFDMA) contention window (OCW) in the UORA parameter set elements so that the Non-AP STA can initiate random access after the trigger frame transmission.

[0076] Non-AP High Efficiency STAs (Non-AP HE STAs) should maintain an internal OCW (Open Channel Warp) and an internal Orthogonal Frequency Division Multiple Access (OFDMA) random access backoff (OBO) counter. The OCW is... min To OCW max Integers within the range.

[0077] The size of all random access (RA) resource units (RUs) in the set should be the same as the size of the random access resource unit (RA-RU) indicated by the RU allocation subfield in the user information field. For non-AP HE STAs, the total number of eligible RA-RUs in the consecutive set should be determined based on the number of RA-RU subfields in the user information field corresponding to eligible RA-RUs, excluding RA-RUs not within their operating bandwidth.

[0078] If a High Efficiency STA (HE STA) has pending frames for the AP when it receives a trigger frame containing at least one qualified RA-RU, and if the HE STA's OBO counter is not greater than the number of qualified RA-RUs in the trigger frame from the AP, then the HE STA sets its OBO counter to zero and randomly selects one of the qualified RA-RUs to consider sending. Otherwise, the HE STA decrements its OBO counter by the number of qualified RA-RUs in the trigger frame.

[0079] For HE STA or HE AP, the maximum number and types of RUs that can be used at each bandwidth are shown in Table 1 below.

[0080] Table 1

[0081] For Extremely High Throughput (EHT) STAs or EHT APs, the maximum number and types of RUs that can be used at each bandwidth are shown in Table 2 below. The tone plan for EHT at 80MHz is different from that of HE.

[0082] Table 2

[0083] It should be noted that the "tone" in Tables 1 and 2 above can also be called a subcarrier, and they can be used interchangeably.

[0084] To facilitate a better understanding of the embodiments of this application, the Buffer Status Report (BSR) related to this application will be explained.

[0085] Access Points (APs) send BSR Polling (BSRP) trigger frames to retrieve Buffer Status Reports (BSRs) from multiple Non-AP STAs. Each STA indicates the amount of data in its buffer queue corresponding to at least one Traffic Identifier (TID) in at least one frame (e.g., a QoS Null frame) within a responsive Physical Layer Protocol Data Unit (PPDU). In at least one QoS Null frame, the STA also indicates the amount of data in its buffer queue corresponding to at least one Access Category (AC) in the BSR Control subfield of the High-efficiency (HE) variant of the High-throughput (HT) Control field.

[0086] For example, a BSRP trigger frame can be shown in Figure 2. The general information fields in the BSRP trigger frame include the following fields: trigger frame type (=4) (4 bits), uplink length (12 bits), whether there are more trigger frames (1 bit), whether channel measurement is required (1 bit), uplink bandwidth (2 bits), guard interval (GI) and high efficiency long training field (HE-LTF) type / trigger transmission opportunity sharing mode (2 bits), HE-LTF symbol count and intermediate code period (3 bits), low-density parity check (LDPC) extra symbol segmentation (1 bit), AP transmit power (6 bits), pre-forward error correction (Pre-FEC) fill factor (2 bits), and packet extension. Extension (PE) disambiguation (1 bit), uplink space multiplexing (16 bits), HE / EHT Primary 160 (P160) (1 bit), special user information field identifier (1 bit), EHT reserved (7 bits).

[0087] For example, a QoS null frame can be shown in Figure 3. The Media Access Control (MAC) header in a QoS null frame includes a QoS control field and an HT control field. The QoS control field includes the following fields: Traffic Identifier (TID) (4 bits), End of Service Period (EOSP) (=1) (1 bit), Ack Policy Indicator (2 bits), and Queue Size (8 bits). The HT control field includes the following fields: Very High Throughput (VHT) (1 bit), HE (1 bit), and Aggregate Control (30 bits). The control list field in the Aggregate Control field includes the Control Information (BSR) field, which includes the following fields: Access Category Index (ACI) bitmap, Delta TID, High Priority Access Type (ACI High), Scaling Factor, High Priority Queue Size (Queue Size High), and All Queue Size (Queue Size All).

[0088] To facilitate a better understanding of the embodiments of this application, the Null Data Physical Protocol Data Unit feedback report (NFR) related to this application will be explained.

[0089] The access point sends a Null Data Physical Protocol Data Unit feedback report polling (NFRP) trigger frame to obtain NFRP feedback from multiple stations. Upon receiving the NFRP trigger frame, a station transmits an NDP (or High Efficiency Trigger Based Feedback Null Data Physical Protocol Data Unit, HETB feedback NDP) as a response. When the number of bytes of data it has buffered is greater than or equal to the resource request buffer threshold indicated by the access point, the station's feedback status (FEEDBACK_STATUS) (this transmission variable will be used to modulate the subcarrier of the long training field (LTF) of the transmitted NDP) is set to 1; otherwise, the station's FEEDBACK_STATUS is set to 0. The resource request cache threshold is indicated by the access point in the NDP Feedback Report Parameter Set element in the Beacon and / or Probe Response and / or Association Response and / or Reassociation Response frames, or, if no such indication is received, the resource request cache threshold is a default value of 256 bytes.

[0090] Specifically, the NFRP trigger frame can be shown in Figure 4. The general information fields include the following: trigger frame type (=4) (4 bits), uplink length (12 bits), whether there are more trigger frames (1 bit), whether channel measurement is required (1 bit), uplink bandwidth (2 bits), GI and HE-LTF type (=2) (2 bits), Multiple Users Multiple-In-Multiple-Output (MU-MIMO) HE-LTF mode (1 bit), HE-LTF symbol count and intermediate code period (=1) (3 bits), AP transmit power (6 bits), and uplink high efficiency signal field A2 (HE-SIG-A2) reservation (9 bits). The user information list fields include the following: Association Identifier (AID), feedback type, uplink target receive power, and number of spatially multiplexed users.

[0091] Specifically, the NDP Feedback Report Parameter Set element can be seen in Figure 5.

[0092] Specifically, the HE TB feedback NDP includes the following fields: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signal (L-SIG), repeat legacy signal (RL-SIG), high efficiency signal A (HE-SIG-A), high efficiency short training field (HE-STF), high efficiency long training field (HE-LTF), and packet extension (PE).

[0093] As shown in Figure 10, there are two 4x HE-LTF symbols, each with a length of 16 μs.

[0094] Specifically, the NDP format uses the HE TB PPDU format, but it lacks a data field. The PE field duration is 0 microseconds (μs), and there are two symbols of type 4x HE-LTF, using a protection interval (GI) of 3.2 microseconds. The duration of the 1x HE-LTF symbol is 3.2 microseconds, the 2x HE-LTF symbol is 6.4 microseconds, and the 4x HE-LTF symbol is 12.8 microseconds; the durations do not include the protection interval.

[0095] Specifically, the different RU pass set indexes (RU_TONE_SET_INDEX) in the HE-LTF field are used to identify the AID and feedback information (FEEDBACK_STATUS) of different Non-AP STAs. Here, pass (TONE) can also be referred to as a subcarrier. The HE-LTF subcarrier mapping relationship in the HE TB feedback NDP is shown in Table 3.

[0096] Table 3

[0097] In simple terms, when the Number of Spatially Multiplexed Users field in the NFRP Trigger frame is 0, each RU_TONE_SET_INDEX corresponds to one Non-AP STA (AID). When the BW is 20MHz, for a Non-AP STA using RU_TONE_SET_INDEX = 1, a feedback information FEEDBACK_STATUS = 1 corresponds to subcarriers –113, –77, –41, 6, 42, and 78 in the HE-LTF having energy, while other subcarriers have no energy; a feedback information FEEDBACK_STATUS = 0 corresponds to subcarriers –112, –76, –40, 7, 43, and 79 in the HE-LTF having energy, while other subcarriers have no energy. When the BW is 40MHz or 80MHz, the 20MHz subcarrier mapping is extended by a factor of 1 and 3 respectively, thus allowing mapping of more Non-AP STAs (AIDs). The start association flag in the NFRP Trigger frame corresponds to the RU_TONE_SET_INDEX value 1. For example, if the start association flag is 6, then a non-AP STA with an AID value of 6 corresponds to RU_TONE_SET_INDEX value 1, a non-AP STA with an AID value of 7 corresponds to RU_TONE_SET_INDEX value 2, and so on.

[0098] When the Number of Spatially Multiplexed Users field in the NFRP Trigger frame is set to 1, each RU_TONE_SET_INDEX corresponds to two Non-AP STAs (AIDs). These two Non-AP STAs are distinguished by different pre-allocated precoding matrices. The start association flag in the NFRP Trigger frame corresponds to the RU_TONE_SET_INDEX value of 1. For example, if the start association flag is 6, then the two non-AP STAs with AID values ​​of 6 and 7 correspond to RU_TONE_SET_INDEX value 1, the two non-AP STAs with AID values ​​of 8 and 9 correspond to RU_TONE_SET_INDEX value 2, and so on.

[0099] To facilitate understanding of the technical solutions of the embodiments of this application, the problems solved by this application will be described below.

[0100] For event-driven (also known as unpredictable or difficult-to-predict) low-latency traffic transmission, reserving channels directly for low-latency data transmission has the following problems: reserving too many channels can lead to waste, while reserving too few channels may result in only a small number of stations with low-latency traffic being able to complete low-latency data transmission after UORA contention; when a station uses multi-user (MU) physical layer protocol data unit (PPDU) transmission for single-user (SU) transmission, other stations cannot predict the length of the MU PPDU, making it difficult to achieve alignment with the MU PPDU when transmitting low-latency data.

[0101] Event-driven (also known as unpredictable or difficult-to-predict) low-latency traffic, such as traffic generated by user instant messaging interactions or sensor-generated traffic, is unpredictable and therefore cannot be transmitted by pre-scheduling appropriate resources. When it is generated, the site needs to wait for a transmission opportunity before it can be transmitted, resulting in the low-latency traffic not being transmitted in a timely manner. Therefore, there is an urgent need for a method that can achieve low-latency transmission.

[0102] Low-latency traffic: This generally refers to traffic identified by a restricted target wake time (R-TWT) traffic identifier (TID) or a stream classification service identifier (SCS ID).

[0103] Non-low latency traffic: Traffic that is not identified by the restricted target wake time traffic identifier (R-TWT TID) or the stream classification service identifier (SCS ID).

[0104] Based on the above problems, this application proposes an uplink transmission scheme. In the first uplink transmission, the first STA reserves m1 frequency domain units. One or more other STAs with uplink delay-sensitive data to be transmitted report the buffer information of the delay-sensitive data on the m1 frequency domain units. Thus, the AP can obtain the buffer information of the uplink delay-sensitive data of one or more other STAs in the transmission opportunity (TXOP) or the TXOP obtained by the first STA, thereby realizing the timely transmission of event-driven uplink delay-sensitive data.

[0105] It should be noted that since the AP itself cannot receive data during downlink transmission, the reserved resources in the access point's downlink transmission are useless. Therefore, this application mainly designs a system to reserve resources during uplink transmission (data frames, management frames, or control frames) for other sites to report latency-sensitive data (also known as low-latency uplink data) to the AP, in order to meet the transmission requirements of low-latency traffic. This reserved resource information needs to be known not only by the site itself but also by the other sites; therefore, this information is generally indicated in advance by the access point.

[0106] This application does not directly perform uplink low-latency data transmission in reserved sub-channels or resource units (RUs). Instead, it uses the null data physical layer transport protocol data unit feedback (NDP feedback report), which can avoid the alignment problem with the MU PPDU when the site uses MU PPDU single-user transmission (SU transmission) for uplink.

[0107] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0108] Figure 8 is a schematic flowchart of a wireless communication method 200 according to an embodiment of this application. As shown in Figure 8, the wireless communication method 200 may include at least some of the following:

[0109] S210, the first STA reserves m1 frequency domain units in the first uplink transmission; wherein, the m1 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data containing uplink delay-sensitive data to be transmitted, and m1 is a positive integer;

[0110] S220, the AP receives the first uplink transmission from the first STA; wherein, the first STA reserves m1 frequency domain units in the first uplink transmission, and the m1 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data containing uplink delay-sensitive data to be transmitted;

[0111] S230, the second STA reports the buffer information of delay-sensitive data on m1 frequency domain units; wherein, the m1 frequency domain units are the frequency domain units reserved by the first STA in the first uplink transmission;

[0112] S240, the AP receives the buffer information of the delay-sensitive data reported by the second STA on m1 frequency domain units; wherein, the m1 frequency domain units are the frequency domain units reserved by the first STA in the first uplink transmission, and the m1 frequency domain units are used for the buffer information of one or more other STAs that have uplink delay-sensitive data to be transmitted to report delay-sensitive data.

[0113] It should be understood that Figure 8 illustrates the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and other operations or variations of the various operations in Figure 8 may also be performed in the embodiments of this application.

[0114] In the embodiments of this application, S230 and S240 are optional steps. For example, S230 and S240 are performed when the second STA has uplink delay-sensitive data to be transmitted. As another example, S230 and S240 are performed when the second STA has more than a quantity x (x is a positive number or 0) of uplink delay-sensitive data to be transmitted.

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

[0116] In this embodiment, the second STA can be another STA belonging to the same WLAN network as the first STA. Specifically, the operation of other STAs besides the second STA can be referred to that of the second STA, and will not be repeated here.

[0117] The term TONE as used in the embodiments of this application may also be referred to as a subcarrier, or the term TONE as used in the embodiments of this application may also be referred to as a subcarrier; the two terms can be used interchangeably.

[0118] It should be noted that latency-sensitive data can also be called low-latency (LL) data, but this application does not limit the scope of the embodiments.

[0119] In this embodiment of the application, before other STAs report the cached information of latency-sensitive data, the AP does not need to send an NFRP trigger frame, which allows for more flexible reporting of the cached information of latency-sensitive data and avoids the signaling overhead caused by sending an NFRP trigger frame.

[0120] In some embodiments, other STAs that report cached information for latency-sensitive data support the function of reporting the amount of latency-sensitive data. Specifically, since legacy STAs do not support the function of reporting latency-sensitive data, they will not report cached information for latency-sensitive data on the reserved frequency domain units.

[0121] In some embodiments, the cache information of latency-sensitive data reported by other STAs may be a Buffer Status Report (BSR) or other information, and this application embodiment does not limit this.

[0122] In some embodiments, the frequency domain units among the m1 frequency domain units are resource units (RUs). That is, the m1 RUs are used to cache information of one or more other STAs reporting latency-sensitive data that contains uplink latency-sensitive data to be transmitted.

[0123] For example, when m1 ≥ 2, m1 frequency domain units (i.e., RUs) can be located in one subchannel. As another example, when m1 ≥ 2, m1 frequency domain units (i.e., RUs) can be located in multiple subchannels, where these subchannels can be continuous or discontinuous. Yet another example is that the m1 frequency domain units (i.e., RUs) constitute a complete subchannel (e.g., a 20MHz subchannel).

[0124] Specifically, in this embodiment, when the frequency domain unit in m1 frequency domain units is RU, frequency domain resources can be reserved at the RU granularity. Compared with frequency domain resource reservation at the sub-channel or channel granularity, the granularity of resource reservation is smaller, the waste of resources is smaller, and frequency domain resources can be utilized more fully.

[0125] In some embodiments, the frequency domain units in the m1 frequency domain units are sub-channels (such as 20MHz sub-channels). That is, the m1 sub-channels are used for buffering information of one or more other STAs reporting delay-sensitive data that contains uplink delay-sensitive data to be transmitted.

[0126] In some embodiments, the first uplink transmission is an uplink transmission (such as a data frame and / or a management frame) performed by the first STA after acquiring the TXOP. For example, the first uplink transmission is an uplink data transmission performed by the first STA after acquiring the TXOP.

[0127] In some embodiments, the first uplink transmission is an uplink transmission (such as a data frame and / or management frame) triggered by the AP after acquiring the TXOP. For example, the first uplink transmission is an uplink data transmission performed by the first STA after being triggered by the AP.

[0128] In some embodiments, the first uplink transmission is an uplink response or uplink acknowledgment to a downlink transmission (such as a data frame and / or a management frame) performed by the AP after acquiring the TXOP. For example, the uplink response or uplink acknowledgment can be performed via a management frame and / or an acknowledgment (Ack) frame and / or a block acknowledgment (BA) frame.

[0129] That is, in the embodiments of this application, in the TXOP that the first STA or AP competes for, the AP can obtain the buffer information of one or more uplink delay-sensitive data reported by other STAs on the m1 frequency domain units reserved by the first STA in the first uplink transmission, thereby enabling timely transmission of event-driven uplink delay-sensitive data.

[0130] In some embodiments, the m1 frequency domain units are agreed upon by a protocol, or the m1 frequency domain units are configured by the AP (semi-static or dynamic configuration), or the m1 frequency domain units are configured by the physical AP MLD to which the AP belongs (semi-static or dynamic configuration), or the m1 frequency domain units are configured by the virtual AP MLD to which the AP belongs (semi-static or dynamic configuration).

[0131] In some embodiments, the first STA receives a first trigger frame before performing the first uplink transmission;

[0132] The first trigger frame includes a first field;

[0133] The first field is used to indicate that the first STA reserves frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0134] The first field is used to indicate that the first STA reserves a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

[0135] Specifically, before the first STA performs the first uplink transmission, the first STA receives the first trigger frame sent by the AP.

[0136] In some embodiments, the first TXOP is the TXOP acquired by the first STA. That is, the first field is used to indicate the frequency domain unit reserved by the first STA in the uplink transmission of the TXOP acquired by the first STA for reporting delay-sensitive data.

[0137] In some embodiments, the first TXOP is the TXOP obtained by the AP. That is, the first field is used to indicate the frequency domain unit reserved by the first STA in the uplink transmission of the TXOP obtained by the AP for reporting delay-sensitive data.

[0138] In some embodiments, the at least one uplink transmission may be indicated by the AP through other fields in the first trigger frame, or the at least one uplink transmission may be indicated by the AP through other frames, or the at least one uplink transmission may be indicated by the AP through the first field.

[0139] In some embodiments, the first TXOP may be indicated by the AP through other fields in the first trigger frame, or the first TXOP may be indicated by the AP through other frames, or the first TXOP may be indicated by the AP through the first field.

[0140] In some embodiments, the first field may occupy one bit; wherein, a value of 0 indicates that the first STA reserves a frequency domain unit for reporting delay-sensitive data cache information in at least one uplink transmission, or a value of 0 indicates that the first STA reserves a frequency domain unit for reporting delay-sensitive data cache information in the uplink transmission of the first TXOP; or, a value of 1 indicates that the first STA reserves a frequency domain unit for reporting delay-sensitive data cache information in at least one uplink transmission, or a value of 1 indicates that the first STA reserves a frequency domain unit for reporting delay-sensitive data cache information in the uplink transmission of the first TXOP.

[0141] In some embodiments, the first field may be located in the general information field of the first trigger frame. For example, the AP may use a reserved bit in the general information field of the first trigger frame as the first field to indicate that the STA triggered by the first trigger frame reserves frequency domain units (such as sub-channels or resource units) for reporting delay-sensitive data buffer information in uplink transmission. The specific frequency domain unit (such as sub-channel or resource unit) information has been set in advance.

[0142] For example, the first trigger frame can be as shown in Figure 9, where, in the general information field, the first field is located after the GI and HE-LTF type / trigger transmission opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields.

[0143] For example, the first trigger frame can be as shown in Figure 10, where in the general information field, the first field is located after the HE-LTF symbol number and intermediate code period fields, and before the LDPC extra symbol segment field.

[0144] For example, the first trigger frame can be as shown in Figure 11, where, in the general information field, the first field is located after the uplink space multiplexing field and before the HE / EHT P160 field.

[0145] For example, the first trigger frame can be as shown in Figure 12, where the first field in the general information field is located after the EHT reserved field.

[0146] As shown in Figures 9 to 12, the general information field in the first trigger frame also includes the following fields: trigger frame type (4 bits), uplink length (12 bits), whether there are more trigger frames (1 bit), whether channel measurement is required (1 bit), uplink bandwidth (2 bits), guard interval (GI) and high efficiency long training field (HE-LTF) type / trigger transmission opportunity sharing mode (2 bits), HE-LTF symbol number and intermediate code period (3 bits), low density parity check (LDPC) extra symbol segmentation (1 bit), AP transmit power (6 bits), pre-forward error correction (Pre-FEC) fill factor (2 bits), packet spreading (PE) disambiguation (1 bit), uplink space multiplexing (16 bits), HE / EHT P160 (1 bit), special user information field identifier (1 bit), and EHT reservation (7 bits).

[0147] In some embodiments, the first trigger frame further includes a second field; wherein the second field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0148] For example, the AP can use four reserved bits from the first trigger frame (such as the four reserved bits in the special user information field) as the second field to indicate the number of the reserved frequency domain unit (such as a sub-channel). Within the current BSS operating bandwidth, sub-channels are numbered either by center frequency from smallest to largest, or by center frequency from largest to smallest, or according to other predefined methods. Specifically, a sub-channel corresponding to the main channel cannot be used as a reserved sub-channel.

[0149] For example, the AP can use eight reserved bits from the special user information field (where the value of its AID12 field is a special value 2007) in the first trigger frame as the second field to indicate the reserved resource units (RUs). The numbering method of the resource units is consistent with the method used in the resource unit allocation field.

[0150] For example, the first trigger frame can be as shown in Figure 13, wherein in the general information field, the first field is located after the GI and HE-LTF type / triggering opportunity sharing mode fields, and the first field is located before the HE-LTF symbol number and intermediate code period fields; and in the special user information field of the user information list, the second field (occupying 4 bits) can be located in the user information field related to the trigger frame subclass.

[0151] For example, the first trigger frame can be as shown in Figure 14, wherein in the general information field, the first field is located after the GI and HE-LTF type / triggering opportunity sharing mode fields, and the first field is located before the HE-LTF symbol number and intermediate code period fields; and in the special user information field of the user information list, the second field (occupying 8 bits) can be located in the user information field related to the trigger frame subclass.

[0152] As shown in Figures 13 and 14, the special user information fields in the first trigger frame also include the following fields: AID12 (=2007), physical layer version flag, uplink bandwidth extension, EHT space multiplexing 1, EHT space multiplexing 2, user signal (U-SIG) ignoring and verification, and user information related to the trigger frame subclass.

[0153] As shown in Figures 9 to 14, the user information fields in the first trigger frame include the following fields: AID12, resource unit allocation, uplink forward error correction (FEC) coding type, uplink EHT modulation / demodulation and coding category, spatial stream allocation or random access resource unit information, uplink target received power, primary / secondary 160, and user information related to the trigger frame subclass. Among these, the user information fields related to the trigger frame subclass include the following fields: Multi-User Media Access Control Protocol Data Unit (MPDU) slot factor, TID aggregation limit, and preferred access category.

[0154] In some embodiments, the first trigger frame further includes a third field; wherein the third field is used to indicate parameter information for the other STA to provide feedback on Null Data Physical Protocol Data Unit (NDP).

[0155] In some embodiments, the parameter information fed back by the NDP includes, but is not limited to, at least one of the following: Association Identifier (AID), Starting AID, Feedback Type, Uplink Target Received Power, and Number of Spatially Multiplexed Users.

[0156] For example, the third field can be the Special User Information 2 field. Specifically, the first trigger frame can be as shown in Figure 15, where, in the general information field, the first field is located after the GI and HE-LTF type / triggering opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields; and in the Special User Information 1 field of the user information list, the second field (occupying 8 bits) can be located in the user information field related to the trigger frame subclass; in addition, the user information list also includes the Special User Information 2 field (i.e., the third field), where the Special User Information 2 field includes the following fields: AID12 (=2008), starting AID, feedback type, uplink target received power, and number of spatially multiplexed users.

[0157] In some embodiments, if the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP, and one or more other STAs have reported buffer information of delay-sensitive data on the m1 frequency domain units, the first STA receives a preemption indication message sent by the AP, wherein the preemption indication message is used to instruct the AP to preempt the TXOP acquired by the first STA.

[0158] In some embodiments, the preemption indication information is carried in a block acknowledgment (BA) frame corresponding to the first uplink transmission, or the preemption indication information is carried in a management frame.

[0159] In some embodiments, when the preemption indication information is carried through the block acknowledgment frame corresponding to the first uplink transmission, the block acknowledgment control (BA Control) field in the block acknowledgment frame corresponding to the first uplink transmission includes a field for instructing the AP to preempt the TXOP acquired by the first STA.

[0160] For example, as shown in Figure 16, the AP uses a reserved bit in the Block Acknowledgment Control (BA Control) field of the block acknowledgment frame to indicate that the AP will preempt the TXOP field acquired by the first STA.

[0161] In some embodiments, after learning that the first STA or AP has enabled the delay-sensitive transmission priority mode (also known as the low-latency transmission priority mode), other STAs (such as the second STA) determine that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data buffer information.

[0162] For example, after other STAs (such as the second STA) learn that the first STA or AP has enabled the delay-sensitive transmission priority mode (also known as the low-latency transmission priority mode), they determine that the first STA has reserved frequency domain units for reporting delay-sensitive data buffer information in at least one uplink transmission, and the at least one uplink transmission includes the first uplink transmission.

[0163] For example, after other STAs (such as the second STA) learn that the first STA or AP has enabled the delay-sensitive transmission priority mode (also known as the low-latency transmission priority mode), they determine that the first STA has reserved frequency domain units in the uplink transmission of the first TXOP for reporting delay-sensitive data, and the first uplink transmission is the uplink transmission in the first TXOP.

[0164] In some embodiments, when the first STA has enabled the delay-sensitive transmission priority mode, other STAs (such as the second STA) can learn that the first STA has enabled the delay-sensitive transmission priority mode through beacon frames or management frames sent by the AP.

[0165] For example, the first STA performs a mode switch in advance (i.e., enables delay-sensitive transmission priority mode (also known as low-latency transmission priority mode)). The AP broadcasts in the beacon frame that the first STA has enabled delay-sensitive transmission priority mode (the mode switch of the first STA takes effect after at least one beacon frame transmission). The specific reserved frequency domain units (i.e., m1 frequency domain units) can be predefined or indicated in the beacon frame. After the first STA enables delay-sensitive transmission priority mode, it reserves frequency domain units for reporting buffer information of delay-sensitive data in at least one uplink transmission, or it reserves frequency domain units for reporting buffer information of delay-sensitive data in the uplink transmission of the first TXOP.

[0166] For example, the first STA performs a mode switch in advance (i.e., enables delay-sensitive transmission priority mode (also known as low-latency transmission priority mode)). The AP sends a newly defined management frame to announce that the first STA has enabled delay-sensitive transmission priority mode. The specific reserved frequency domain units (i.e., m1 frequency domain units) can be predefined or indicated in the newly defined management frame. After the first STA enables delay-sensitive transmission priority mode, it reserves frequency domain units for reporting buffer information of delay-sensitive data in at least one uplink transmission, or it reserves frequency domain units for reporting buffer information of delay-sensitive data in the uplink transmission of the first TXOP.

[0167] In some embodiments, the latency-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, or the latency-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

[0168] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

[0169] Specifically, for example, the AP can send a management frame to at least one STA to request the activation of delay-sensitive transmission priority mode (also known as low-latency transmission priority mode). Optionally, the management frame can further indicate the following information: the activation duration of the delay-sensitive transmission priority mode, and / or, the specific frequency domain units reserved (i.e., m1 frequency domain units). When the delay-sensitive transmission priority mode is activated, the STA can reserve frequency domain units (sub-channels or RUs) for buffering information of other STAs reporting delay-sensitive data to the AP during uplink transmission in its own acquired TXOP, and the AP can preempt the transmission time in the TXOP acquired by the at least one STA for uplink and / or downlink delay-sensitive data transmission with other STAs. Specifically, for example, the AP can also send a management frame to the at least one STA to request the deactivation of the delay-sensitive transmission priority mode.

[0170] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

[0171] Specifically, for example, a STA can send a management frame to the AP to notify it to enable delay-sensitive transmission priority mode (also known as low-latency transmission priority mode). Optionally, this management frame can further indicate the following information: the duration of the delay-sensitive transmission priority mode, and / or, the specific frequency domain units reserved (i.e., m1 frequency domain units). The AP responds with a management frame, which can further confirm or instruct modification of the reserved specific frequency domain units (i.e., m1 frequency domain units). When delay-sensitive transmission priority mode is enabled, the STA can reserve frequency domain units (sub-channels or RUs) for buffering information of other STAs reporting delay-sensitive data to the AP during uplink transmission in its own acquired TXOP. Furthermore, the AP can preempt the transmission time in the TXOP acquired by at least one STA for uplink and / or downlink delay-sensitive data transmission with other STAs. Specifically, for example, a STA can also send a management frame to the AP to notify it to disable delay-sensitive transmission priority mode.

[0172] In some embodiments, when the AP has enabled delay-sensitive transmission priority mode, other STAs (such as a second STA) learn that the AP has enabled delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: Beacon frame, Probe Response frame, Association Response frame, Reassociation Response frame, Opearation Mode Notification frame, and newly defined management frame.

[0173] In some embodiments, the AP indicates at least one of the following while indicating that it has enabled the delay-sensitive transmission priority mode: the duration of the delay-sensitive transmission priority mode enabled for the AP, and the m1 frequency domain units.

[0174] In some embodiments, the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

[0175] Specifically, for example, the AP can enable a delay-sensitive transmission priority mode (also known as a low-latency transmission priority mode). When the delay-sensitive transmission priority mode is enabled, the AP can request STAs to reserve frequency domain units (sub-channels or RUs) in its acquired TXOPs for buffering information when other STAs report delay-sensitive data to the AP during uplink transmission. For example, the AP can send a management frame (e.g., a Beacon frame and / or a Probe Response frame and / or an Association Response frame and / or a Reassociation Response frame and / or an Opearation Mode Notification frame) to inform STAs of the enabling of the delay-sensitive transmission priority mode; optionally, the management frame can further indicate the following information: the duration of the delay-sensitive transmission priority mode, and / or the specific frequency domain units reserved (i.e., m1 frequency domain units). For example, the AP can send a management frame (such as a Beacon frame and / or Probe Response frame and / or Association Response frame and / or Reassociation Response frame and / or Opearation Mode Notification frame) to inform the STA that delay-sensitive transmission priority mode is turned off.

[0176] In some embodiments, after learning that the first STA has reserved frequency domain units for reporting delay-sensitive data in the TXOP it has won, other STAs (such as the second STA) determine that the first STA has reserved frequency domain units for reporting delay-sensitive data in each uplink transmission in the TXOP.

[0177] In some embodiments, other STAs (such as the second STA) learn from the request to send (RTS) frame sent by the first STA that the first STA has reserved frequency domain units in the TXOP it has competed for for reporting latency-sensitive data.

[0178] In this RTS frame, the unicast or multicast bits in the Receiver Addresses (RA) are used to indicate whether the first STA has reserved frequency domain units for reporting delay-sensitive data in this TXOP.

[0179] Specifically, for example, the first STA may indicate in the transmitted RTS frame whether it has reserved frequency domain units for buffering information to report delay-sensitive data. For instance, setting the unicast or multicast (Individual / Group) bit in the Receiver Addresses (RA) of the RTS frame to 1 indicates that the first STA has reserved frequency domain units for buffering information to report delay-sensitive data in this Transmission Opportunity (TXOP), while setting it to 0 indicates that the first STA has not reserved frequency domain units for buffering information to report delay-sensitive data in this Transmission Opportunity. The specific reserved frequency domain unit information can be predefined or indicated by the access point in a previous beacon frame.

[0180] In some embodiments, other STAs (such as the second STA) learn through the second trigger frame sent by the AP that the first STA has reserved frequency domain units for reporting delay-sensitive data cache information in the first uplink transmission.

[0181] In some embodiments, the second trigger frame includes a fourth field;

[0182] The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data buffer information in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0183] The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

[0184] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or, the first TXOP is the TXOP obtained by the AP.

[0185] For example, the second trigger frame can be as shown in Figure 17, where, in the general information field, the fourth field is located after the GI and HE-LTF type / trigger transmission opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields.

[0186] For example, the second trigger frame can be as shown in Figure 18, where in the general information field, the fourth field is located after the HE-LTF symbol number and intermediate code period fields, and before the LDPC extra symbol segment field.

[0187] For example, the second trigger frame can be as shown in Figure 19, where in the general information field, the fourth field is located after the uplink space multiplexing field and before the HE / EHT P160 field.

[0188] For example, the second trigger frame can be as shown in Figure 20, where the fourth field in the general information field is located after the EHT reserved field.

[0189] In some embodiments, the second trigger frame includes a fifth field; wherein the fifth field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0190] For example, the second trigger frame can be as shown in Figure 21, where, in the general information field, the fourth field is located after the GI and HE-LTF type / trigger transmission opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields; and in the special user information field of the user information list, the fifth field (occupying 4 bits) can be located in the user information field related to the trigger frame subclass.

[0191] For example, the second trigger frame can be as shown in Figure 22, where, in the general information field, the fourth field is located after the GI and HE-LTF type / triggering opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields; and in the special user information field of the user information list, the fifth field (occupying 8 bits) can be located in the user information field related to the trigger frame subclass.

[0192] In some embodiments, other STAs (such as the second STA) use some or all of the frequency domain units in the m1 frequency domain units to report cached information of delay-sensitive data; or, other STAs (such as the second STA) report cached information of delay-sensitive data on the frequency domain units available in the m1 frequency domain units obtained by the UORA mechanism.

[0193] For example, if the second STA has uplink delay-sensitive data to be transmitted, the second STA reports the buffer information of the delay-sensitive data on some or all of the frequency domain units in the m1 frequency domain units.

[0194] For example, if the second STA has uplink delay-sensitive data to be transmitted, the second STA reports the buffer information of the delay-sensitive data on the available frequency domain units in the m1 frequency domain units obtained by the UORA mechanism.

[0195] In some embodiments, when other STAs (such as a second STA) report cached information of delay-sensitive data on available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of delay-sensitive data reported on the available frequency domain units is carried through a QoS null frame.

[0196] In some embodiments, the first STA reserves m2 frequency domain units in the second uplink transmission; wherein, the m2 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data, and m2 is a positive integer.

[0197] For example, the second STA reports the buffer information of delay-sensitive data on m2 frequency domain units; where the m2 frequency domain units are the frequency domain units reserved by the first STA in the second uplink transmission, and m2 is a positive integer.

[0198] In some embodiments, the frequency domain units in the m2 frequency domain units are RUs; or, the frequency domain units in the m2 frequency domain units are sub-channels.

[0199] In some embodiments, the frequency domain units in the m1 frequency domain units are the same as the frequency domain units in the m2 frequency domain units. For example, the frequency domain units in the m1 frequency domain units and the frequency domain units in the m2 frequency domain units are all the same RU, or the frequency domain units in the m1 frequency domain units and the frequency domain units in the m2 frequency domain units are all the same sub-channels.

[0200] In some embodiments, the frequency domain units in the m1 frequency domain units are different from those in the m2 frequency domain units. For example, the frequency domain units in the m1 frequency domain units are RUs, and the frequency domain units in the m2 frequency domain units are sub-channels. Another example is that the frequency domain units in the m1 frequency domain units are sub-channels, and the frequency domain units in the m2 frequency domain units are RUs. Yet another example is that the frequency domain units in the m1 and m2 frequency domain units are RUs located at different frequency positions. Yet another example is that the frequency domain units in the m1 and m2 frequency domain units are sub-channels located at different frequency positions.

[0201] In some embodiments, the first uplink transmission and the second uplink transmission may belong to the same TXOP, or the first uplink transmission and the second uplink transmission may belong to different TXOPs.

[0202] In some embodiments, the first uplink transmission is one uplink transmission in a periodic uplink transmission, and / or the second uplink transmission is one uplink transmission in a periodic uplink transmission.

[0203] In some embodiments, one or more other STAs with more than a number x of uplink latency-sensitive data to be transmitted report cached information of latency-sensitive data via NDP or QoS empty frames, where x is 0 or a positive number.

[0204] For example, if the amount of uplink latency-sensitive data to be transmitted exceeds x, the second STA reports the buffer information of the latency-sensitive data through NDP or QoS empty frames, where x is 0 or a positive number.

[0205] In some embodiments, the NDP can be an HE TB feedback NDP, or the NDP can be a newly defined NDP. Of course, the NDP can also be other NDPs, and this application embodiment does not limit this.

[0206] In some embodiments, the value of x is determined by the protocol, or the value of x is configured or indicated by the AP in a beacon frame or trigger frame.

[0207] In some embodiments, when other STAs (such as a second STA) report cached information of latency-sensitive data through the NDP, the pass set index or subcarrier set index used by the Ultra High Reliability long training field (UHR-LTF) in the NDP indicates the AID information of the STA that sent the NDP.

[0208] In some embodiments, the AID information of each STA transmitting NDP is associated with a pass set index or a subcarrier set index.

[0209] In some embodiments, the bandwidth used by the UHR-LTF in the NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, or 320MHz.

[0210] In some embodiments, the bandwidth used by the UHR-LTF in this NDP is one of the following: 26-tone, 52-tone, or 106-tone. 242-tone is equivalent to a 20MHz subchannel. Larger bandwidths can be formed using combinations of 26-tone, 52-tone, 106-tone, and 242-tone.

[0211] In some embodiments, each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6.

[0212] In some embodiments, each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

[0213] Specifically, when the reserved frequency domain unit is one or more 20MHz sub-channels, the HE TB feedback NDP format can be adopted. In this case, the RU_TONE_SET_INDEX mapping in the HE-LTF field can be optimized. In the mapping shown in Table 2, each AID corresponds to one set of subcarriers when the feedback information (FEEDBACK_STATUS) is 0, and another set of subcarriers when the feedback information (FEEDBACK_STATUS) is 1. In the embodiments of this application, STAs without delay-sensitive data do not need to transmit NDP, that is, they do not need to use the 0 value of the feedback information (FEEDBACK_STATUS). Therefore, the subcarriers corresponding to them can be used to correspond to the 1 value of the feedback information (FEEDBACK_STATUS) of other AIDs. For example, in the mapping shown in Table 2, if the initial AID is 6, the subcarrier groups {–113,–77,–41,6,42,78} and {–112,–76,–40,7,43,79} under a 20MHz bandwidth correspond to the feedback information (FEEDBACK_STATUS) values ​​of 1 and 0 for the STA with initial AID 6, respectively. In this embodiment, {–113,–77,–41,6,42,78} and {–112,–76,–40,7,43,79} can be changed to correspond to the feedback information values ​​of 1 for stations with AIDs 6 and 7, respectively, and so on.

[0214] It should be noted that the HE TB feedback NDP format can only be transmitted on one or more complete 20MHz subchannels. When it is necessary to transmit NDP on a smaller resource unit (RU), a new NDP format needs to be defined, which mainly involves defining the subcarrier mapping of the resource unit channel set index (RU_TONE_SET_INDEX) in the UHR-LTF field as shown in Figure 23.

[0215] In some embodiments, the subcarrier mapping of RU_TONE_SET_INDEX is shown in Table 4 below.

[0216] Table 4

[0217] In some embodiments, the subcarrier mapping of RU_TONE_SET_INDEX can also be such that every 5 or 4 subcarriers correspond to one RU_TONE_SET_INDEX, which can increase the number of stations that can participate in the feedback each time.

[0218] In some embodiments, the subcarrier mapping of RU_TONE_SET_INDEX can also be designed differently for 52-tone RUs and / or 106-tone RUs than for 26-tone RUs, distributing each group of 6 subcarriers evenly throughout the 52-tone RU and / or 106-tone RU. For example, the subcarrier group corresponding to a feedback value of 1 when RU_TONE_SET_INDEX is 1 in a 52-tone RU could be {S+1, S+9, S+17, S+25, S+33, S+41}.

[0219] In some embodiments, for uplink transmission of frequency domain units that reserve cache information for reporting delay-sensitive data, the duration of the PPDU for uplink data transmission by the first STA is less than or equal to a preset value.

[0220] In some embodiments, the preset value is negatively correlated with the number of frequency domain units reserved by the first STA in uplink transmission for reporting delay-sensitive data cache information.

[0221] In some embodiments, the preset value is 700 microseconds or 3400 microseconds.

[0222] For example, in existing methods that poll before each transmission, approximately 180 microseconds of additional time is consumed. This embodiment does not have this additional time consumption; however, reserving sub-channels in the uplink transmission reduces the data transmission bandwidth, increasing data transmission time. Therefore, this embodiment consumes less time than existing solutions when the duration of the PPDU for each data transmission is less than or equal to a preset value (e.g., 700 microseconds).

[0223] For example, in existing methods that poll before each transmission, approximately 180 microseconds of additional time is consumed. This embodiment of the application does not have this additional time consumption. However, reserving resource units (RUs) in the uplink transmission reduces the data transmission bandwidth, increasing data transmission time. Therefore, this embodiment of the application consumes less time than existing solutions when the duration of the PPDU for each data transmission is less than or equal to a preset value (the fewer the reserved resource units, the larger the preset value; for example, 3400 microseconds for a 26-tone RU and 700 microseconds for a 242-tone RU).

[0224] Therefore, in this embodiment of the application, the first STA reserves m1 frequency domain units in the first uplink transmission. One or more other STAs with uplink delay-sensitive data to be transmitted report the buffer information of the delay-sensitive data on the m1 frequency domain units. Thus, the AP can obtain the buffer information of the uplink delay-sensitive data of one or more other STAs in the TXOP that the first STA has won or the TXOP that the AP has won, thereby enabling timely transmission of event-driven uplink delay-sensitive data.

[0225] The technical solution of this application is described in detail below through specific embodiments.

[0226] In Example 1, when a STA performs uplink transmission, it can reserve at least one sub-channel in its operating bandwidth for other STAs to report latency-sensitive data (also known as low-latency data) to the AP as buffer information. The AP can indicate the reserved sub-channel in the beacon frame, and / or, the AP can also indicate the reserved sub-channel when the latency-sensitive priority transmission mode is enabled, and / or, the AP can also indicate the reserved sub-channel in the trigger frame. The specific process can be shown in Figure 24. Station 1 obtains a transmission opportunity (i.e., obtains a transmission opportunity through the request to send (RTS) frame and clear to send (CTS) frame), and Station 1 reserves at least one sub-channel when performing at least one uplink transmission with the access point. If at least one other station generates uplink low-latency data to be sent before this uplink transmission, the other station can use the reserved sub-channel to send a null data physical layer transport protocol data unit feedback (NDP feedback report) during this uplink transmission, which is used to indicate to the access point that other stations have uplink latency-sensitive data to be sent and / or the specific amount of data. Upon receiving the instruction, the access point indicates in its response or acknowledgment to station 1 that it will preempt the transmission opportunity. Upon receiving this preemption instruction, station 1 will cease actively transmitting uplink data. After preempting the transmission opportunity, the access point will use the existing trigger frame-based uplink transmission procedure to trigger uplink transmission from each station (including the other stations and / or station 1). As shown in Figure 24, the time interval between different frames is greater than or equal to the Short Interframe Space (SIFS).

[0227] The uplink transmission between Station 1 and the access point can be data frames and / or management frames. The NDP can be in HE TB feedback NDP format or the NDP format newly defined in this application. The response or acknowledgment from the access point to Station 1 can be a management frame and / or an acknowledgment frame (Ack) and / or a block acknowledgment frame (Block Ack, BA), wherein the uplink transmission triggered by the trigger frame sent by the access point to each station does not reserve sub-channels or resource units; alternatively, the trigger frame newly defined in this application can be used, which carries an indication of reserved sub-channels or resource units, meaning that the uplink transmission triggered by this trigger frame also reserves sub-channels or resource units.

[0228] In this scenario, there are three possible methods for the other stations to determine whether station 1 has reserved a sub-channel or not:

[0229] Method 1: Station 1 performs a mode switch in advance (i.e., enables low-latency transmission priority mode), and the access point broadcasts in the beacon frame that station 1 has enabled low-latency transmission priority mode (in this method, the mode switch of the first station takes effect after at least one beacon frame transmission). The specific sub-channel information reserved can be predefined or indicated in the beacon frame. After the first station enables low-latency transmission priority mode, it always reserves the sub-channel in its acquired transmission opportunities.

[0230] Method 2: Site 1 performs a mode switch in advance (i.e., activates the low-latency transmission priority mode). The access point sends a newly defined management frame to announce that Site 1 has activated the low-latency transmission priority mode. The specific sub-channel information reserved can be predefined or indicated in the newly defined management frame. After Site 1 activates the low-latency transmission priority mode, it always reserves the sub-channel in its acquired transmission opportunities.

[0231] Method 3: Station 1 indicates in the RTS frame sent to the access point that, for example, the unicast or multicast (Individual / Group) bit in the Receiver Addresses (RA) of the frame is set to 1 to indicate that the first station has reserved a sub-channel in this Transmission Opportunity (TXOP), and set to 0 to indicate that the first station has not reserved a sub-channel in this transmission opportunity. The specific sub-channel information reserved can be predefined or indicated by the access point in a previous beacon frame.

[0232] In the transmission opportunity at site 1, the legacy STA does not support the low-latency data volume reporting function and will not transmit the null data physical layer transport protocol data unit feedback.

[0233] During the transmission opportunity at the first site, the access point received the null data physical layer transport protocol data unit feedback without sending an NFRP trigger frame, thus reducing the network load caused by the NFRP trigger frame.

[0234] In Example 2, when a STA performs uplink transmission, it can reserve at least one sub-channel in its operating bandwidth for buffering information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The AP can indicate the reserved sub-channel in the beacon frame, and / or, the AP can also indicate the reserved sub-channel when the latency-sensitive priority transmission mode is enabled, and / or, the AP can also indicate the reserved sub-channel in the trigger frame. The specific process can be shown in Figure 25. The access point obtains a transmission opportunity, and the access point performs at least one downlink transmission with station 1. When station 1 responds or acknowledges to the access point uplink, it reserves at least one sub-channel. If at least one other station generates uplink low-latency data to be sent before the uplink response or acknowledgment, the other station can use the reserved sub-channel to send a null data physical layer transport protocol data unit feedback (NDP feedback report) during the uplink response or acknowledgment, to indicate to the access point that the other station has uplink low-latency data to be sent and / or the specific amount of data. Upon receiving the instruction, the access point will use the uplink transmission procedure based on the trigger frame to trigger each station (including the other stations and / or station 1) to perform uplink transmission.

[0235] The downlink transmission between the access point and station 1 can be data frames and / or management frames. The NDP can be in HE TB feedback NDP format or the NDP format newly defined in this application. The uplink response or acknowledgment of station 1 can be a management frame and / or an acknowledgment frame (Ack) and / or a block acknowledgment frame (Block Ack, BA). The uplink transmission triggered by the trigger frame sent by the access point to each station does not reserve sub-channels or resource units; alternatively, the trigger frame newly defined in this application can be used, carrying an indication of reserved sub-channels or resource units, meaning that the uplink transmission triggered by this trigger frame also reserves sub-channels or resource units.

[0236] In Example 2, the method by which other stations determine whether station 1 has reserved a sub-channel or not is similar to that in Example 1. The difference is that in Method 3, the access point indicates this in the RTS frame sent to station 1.

[0237] In Example 3, when a STA performs uplink transmission, it can reserve at least one sub-channel in its operating bandwidth for buffering information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The AP can indicate the reserved sub-channel in the beacon frame, and / or, the AP can also indicate the reserved sub-channel when the latency-sensitive priority transmission mode is enabled, and / or, the AP can also indicate the reserved sub-channel in the trigger frame. The specific process can be shown in Figure 26. When the access point obtains a transmission opportunity, the access point triggers station 1 to perform at least one uplink transmission, and station 1 reserves at least one sub-channel during the uplink transmission. If at least one other station generates uplink low-latency data to be sent before the uplink transmission, the other station can use the reserved sub-channel to send a null data physical layer transport protocol data unit feedback (NDP feedback report) during the uplink transmission, which is used to indicate to the access point that the other station has uplink low-latency data to be sent and / or the specific amount of data. Upon receiving the instruction, the access point will use the uplink transmission procedure based on the trigger frame to continue triggering uplink transmission for each station (including the other stations and / or station 1).

[0238] When an access point triggers uplink transmission at station 1, it can use a trigger frame (i.e., a reserved sub-channel that is pre-defined or negotiated in the uplink transmission of station 1), or it can use the newly defined trigger frame in this application to carry a reserved sub-channel indication. The NDP can be in the HE TB feedback NDP format or the newly defined NDP format in this application. The uplink transmission at station 1 can be a data frame and / or a management frame and / or an acknowledgment frame (Ack) and / or a block acknowledgment frame (Block Ack, BA). The uplink transmission triggered by the trigger frame sent by the access point to each station does not reserve sub-channels or resource units; alternatively, the newly defined trigger frame in this application can be used, carrying a reserved sub-channel or resource unit indication, meaning that the uplink transmission triggered by this trigger frame also reserves sub-channels or resource units.

[0239] In Embodiment 3, the method for other stations to determine whether station 1 has reserved a sub-channel or not is: to indicate it in the trigger frame of the access point, or to indicate it in the RTS frame using method three in Embodiment 2.

[0240] In existing methods that poll before each transmission, an additional 180 microseconds of time is incurred. This scheme eliminates this additional time consumption; however, reserving sub-channels reduces the data transmission bandwidth, increasing data transmission time. Therefore, this scheme consumes less time than existing schemes when the duration of the PPDU for each data transmission is less than a predefined value (e.g., 700 microseconds).

[0241] In Example 4, when a STA performs uplink transmission, it can reserve at least one sub-channel in its operating bandwidth for buffering information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The AP can indicate the reserved sub-channel in the beacon frame, and / or, the AP can also indicate the reserved sub-channel when the latency-sensitive priority transmission mode is enabled, and / or, the AP can also indicate the reserved sub-channel in the trigger frame. The specific process can be shown in Figure 27. Similar to Example 3, after the access point obtains a transmission opportunity, the access point triggers multiple first stations (i.e., station 1 and station 2 in Figure 27) to perform at least one uplink transmission.

[0242] In Embodiment 4, the method by which other stations determine whether the first station has reserved a sub-channel or not is: to indicate in the access point's trigger frame, or similar to Method 3 in Embodiment 2, to indicate in the multi-user RTS (MU-RTS) trigger frame.

[0243] In Example 5, when a STA performs uplink transmission, it can reserve at least one sub-channel in its operating bandwidth for buffering information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The AP can indicate the reserved sub-channel in the beacon frame, and / or, the AP can also indicate the reserved sub-channel when the latency-sensitive priority transmission mode is enabled, and / or, the AP can also indicate the reserved sub-channel in the trigger frame. Similar to Example 4, after the access point obtains a transmission opportunity, the access point triggers at least one second station to perform at least one uplink transmission while simultaneously performing at least one downlink transmission to at least one first station, wherein the first station may be the same as or different from the second station. The specific process can be shown in Figure 28. In Example 5, the method by which other stations determine whether a sub-channel has been reserved or not is the same as in Example 4.

[0244] In Example 6, when a station performs uplink transmission, it can reserve at least one resource unit (RU) in its operating bandwidth for caching information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The access point can indicate the reserved resource unit in the beacon frame, and / or, the access point can also indicate the reserved resource unit when the low-latency priority transmission mode is enabled, and / or, the access point can also indicate the reserved resource unit in the trigger frame.

[0245] Similar to Example 1, the first station may use any PPDU format it supports, other than the TB PPDU, when transmitting uplink with the access point. In this case, other stations cannot predict the preamble signal of the PPDU and cannot transmit the NDP using only an RU that does not occupy a complete 20MHz subchannel. On the same 20MHz subchannel, if the sender sends different PPDU preambles, it will cause interference, causing the receiver to fail to receive the PPDU correctly. Therefore, the method of reserving RUs is limited in this scenario; only RUs occupying a complete 20MHz subchannel can be reserved, which is essentially the same as the method of reserving subchannels.

[0246] Similar to Example 2, when the first station responds or acknowledges to the access point uplink, it may use any PPDU format it supports, other than the TB PPDU. Similarly, the method of reserving RUs is limited in this scenario; only RUs occupying the entire 20MHz subchannel can be reserved, which is essentially the same as the method of reserving subchannels.

[0247] In Example 7, when a station performs uplink transmission, it can reserve at least one resource unit (RU) in its operating bandwidth for caching information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The access point can indicate the reserved resource unit in the beacon frame, and / or, the access point can also indicate the reserved resource unit when the low-latency priority transmission mode is enabled, and / or, the access point can also indicate the reserved resource unit in the trigger frame.

[0248] Similar to Embodiment 3, as shown in Figure 29; and / or, similar to Embodiment 4, as shown in Figure 30; and / or, similar to Embodiment 5, as shown in Figure 31. Specifically, at least one RU in its operating bandwidth can be reserved. All stations can anticipate the preamble of the TB PPDU to be transmitted uplink by receiving the trigger frame sent by the access point, so the transmission of NDP using the same preamble by other stations on at least one RU will not cause interference. However, the difference is that the NDP needs to adopt the newly defined NDP format in this case, because the HE TB feedback NDP format can only be transmitted on one or more complete 20MHz subchannels. The HE TB feedback NDP format can be used when the reserved RU occupies a complete 20MHz subchannel.

[0249] Existing methods that poll before each transmission incur an additional time consumption of approximately 180 microseconds. This scheme eliminates this additional time consumption; however, reserving resource units reduces the data transmission bandwidth, increasing data transmission time. Therefore, this scheme consumes less time than existing schemes when the duration of each transmitted PPDU is less than a predefined value (this predefined value increases with fewer reserved resource units, e.g., 3400 microseconds for a 26-tone RU and 700 microseconds for a 242-tone RU).

[0250] In Example 8, when a station performs uplink transmission, it can reserve at least one resource unit (RU) in its operating bandwidth for caching information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. The access point can indicate the reserved resource unit in the beacon frame, and / or, the access point can also indicate the reserved resource unit when the low-latency priority transmission mode is enabled, and / or, the access point can also indicate the reserved resource unit in the trigger frame.

[0251] Example 9, similar to Example 8, as shown in Figure 32, allows other stations to compete for reserved RUs via the UORA mechanism to report low-latency data cache information using frames carrying BSR information (e.g., QoS Null frames). Although BSR information is more accurate than that in NDP, UORA contention may fail, so this method is more advantageous when the number of stations in the BSS is small.

[0252] In Example 10, when a station performs uplink transmission, it can reserve at least one sub-channel and resource unit (RU) in its operating bandwidth for buffering information of latency-sensitive data (also known as low-latency data) reported by other STAs to the AP. As shown in Figure 33, the access point can indicate the reserved sub-channel in the beacon frame, and / or, the access point can also indicate the reserved sub-channel when the low-latency priority transmission mode is enabled, and / or, the access point can also indicate the reserved sub-channel in the trigger frame. As shown in Figure 33, the access point can indicate the reserved RU through the trigger frame.

[0253] The method embodiments of this application have been described in detail above with reference to Figures 8 to 33. The device embodiments of this application have been described in detail below with reference to Figures 34 to 39. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.

[0254] Figure 34 shows a schematic block diagram of a site STA 300 according to an embodiment of this application. The STA 300 is a first STA, and as shown in Figure 34, the STA 300 includes:

[0255] The processing unit 310 is used to reserve m1 frequency domain units in the first uplink transmission; wherein the m1 frequency domain units are used for buffering information of one or more other STA-reported delay-sensitive data containing uplink delay-sensitive data to be transmitted, and m1 is a positive integer.

[0256] In some embodiments, the frequency domain units among the m1 frequency domain units are resource units RU; or...

[0257] The frequency domain units in the m1 frequency domain units are sub-channels.

[0258] In some embodiments, the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP; or,

[0259] The first uplink transmission is the uplink transmission triggered by the access point (AP) after acquiring the TXOP; or,

[0260] The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

[0261] In some embodiments, prior to the first STA performing the first uplink transmission, the STA 300 further includes:

[0262] Communication unit 320 is used to receive the first trigger frame;

[0263] The first trigger frame includes a first field;

[0264] The first field is used to indicate that the first STA reserves frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0265] The first field is used to indicate that the first STA reserves a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first transmission opportunity (TXOP), and the first uplink transmission is the uplink transmission in the first TXOP.

[0266] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or,

[0267] The first TXOP is the TXOP obtained by the access point (AP).

[0268] In some embodiments, the first trigger frame further includes a second field; wherein the second field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0269] In some embodiments, the first trigger frame further includes a third field; wherein the third field is used to indicate parameter information for the other STA to perform null data physical protocol data unit (NDP) feedback.

[0270] In some embodiments, the parameter information fed back by the NDP includes at least one of the following: association identifier AID, starting AID, feedback type, uplink target received power, and number of users spatially multiplexed.

[0271] In some embodiments, if the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP, and one or more other STAs have reported buffer information for delay-sensitive data on the m1 frequency domain units, the STA 300 further includes:

[0272] The communication unit 320 is used to receive preemption indication information, wherein the preemption indication information is used to instruct the AP to preempt the TXOP acquired by the first STA.

[0273] In some embodiments, the preemption indication information is carried in a block confirmation frame corresponding to the first uplink transmission, or the preemption indication information is carried in a management frame.

[0274] In some embodiments, when the preemption indication information is carried through the block acknowledgment frame corresponding to the first uplink transmission, the block acknowledgment control field in the block acknowledgment frame corresponding to the first uplink transmission includes a field for instructing the AP to preempt the TXOP acquired by the first STA.

[0275] In some embodiments, after learning that the first STA or AP has enabled the delay-sensitive transmission priority mode, the other STA determines that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data cache information.

[0276] In some embodiments, when the first STA has enabled the delay-sensitive transmission priority mode, the other STAs can learn that the first STA has enabled the delay-sensitive transmission priority mode through beacon frames or management frames sent by the AP.

[0277] In some embodiments, the latency-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, or the latency-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

[0278] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

[0279] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

[0280] In some embodiments, when the AP has enabled the delay-sensitive transmission priority mode, the other STA learns that the AP has enabled the delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

[0281] In some embodiments, the AP indicates at least one of the following while indicating that it has enabled the delay-sensitive transmission priority mode: the duration of the delay-sensitive transmission priority mode enabled for the AP, and the m1 frequency domain units.

[0282] In some embodiments, the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

[0283] In some embodiments, after learning that the first STA has reserved frequency domain units for reporting delay-sensitive data in the TXOP it has won, the other STA determines that the first STA has reserved frequency domain units for reporting delay-sensitive data in each uplink transmission in the TXOP.

[0284] In some embodiments, the other STA learns from the request sent by the first STA to send an RTS frame that the first STA has reserved frequency domain units in the TXOP it has won for reporting latency-sensitive data;

[0285] In this RTS frame, the unicast or multicast bits in the receive address RA are used to indicate whether the first STA has reserved frequency domain units for reporting delay-sensitive data in this TXOP.

[0286] In some embodiments, the other STA learns from the second trigger frame sent by the AP that the first STA has reserved frequency domain units for reporting delay-sensitive data cache information in the first uplink transmission.

[0287] In some embodiments, the second trigger frame includes a fourth field;

[0288] The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data buffer information in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0289] The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

[0290] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or,

[0291] The first TXOP is the TXOP obtained by AP.

[0292] In some embodiments, the second trigger frame includes a fifth field; wherein the fifth field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0293] In some embodiments, the m1 frequency domain units are agreed upon by a protocol, or the m1 frequency domain units are configured by the AP.

[0294] In some embodiments, the other STA uses some or all of the frequency domain units in the m1 frequency domain units to report cached information of delay-sensitive data; or, the other STA reports cached information of delay-sensitive data on the available frequency domain units in the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

[0295] In some embodiments, when the other STA reports cached information of latency-sensitive data on the available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried through a Quality of Service (QoS) empty frame.

[0296] In some embodiments, the processing unit 310 is further configured to reserve m2 frequency domain units in the second uplink transmission; wherein the m2 frequency domain units are used for buffering information of one or more other STA-reported delay-sensitive data containing uplink delay-sensitive data to be transmitted, and m2 is a positive integer.

[0297] In some embodiments, the frequency domain units among the m² frequency domain units are RU; or...

[0298] The frequency domain units in these m2 frequency domain units are sub-channels.

[0299] In some embodiments, the frequency domain units in the m1 frequency domain units are the same as the frequency domain units in the m2 frequency domain units.

[0300] In some embodiments, the frequency domain units in the m1 frequency domain units are different from the frequency domain units in the m2 frequency domain units.

[0301] In some embodiments, one or more other STAs with more than a number x of uplink latency-sensitive data to be transmitted report cached information of latency-sensitive data via NDP or QoS empty frames, where x is 0 or a positive number.

[0302] In some embodiments, the value of x is determined by the protocol, or the value of x is configured or indicated by the AP in a beacon frame or trigger frame.

[0303] In some embodiments, when the other STA reports cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability training field in the NDP indicates the AID information of the STA that sent the NDP.

[0304] In some embodiments, the AID information of each STA that transmits the NDP is associated with a pass set index or a subcarrier set index.

[0305] In some embodiments, the bandwidth used by the UHR-LTF in this NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or,

[0306] The bandwidth used by the UHR-LTF in this NDP is one of the following: 26 channels, 52 channels, or 106 channels.

[0307] In some embodiments, each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or,

[0308] Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

[0309] In some embodiments, for uplink transmission of frequency domain units that reserve cache information for reporting delay-sensitive data, the duration of the Physical Layer Protocol Data Unit (PPDU) for uplink data transmission by the first STA is less than or equal to a preset value.

[0310] In some embodiments, the preset value is negatively correlated with the number of frequency domain units reserved by the first STA in uplink transmission for reporting delay-sensitive data cache information.

[0311] In some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0312] It should be understood that the STA 300 according to the embodiments of this application can correspond to the first STA in the method embodiments of this application, and the above and other operations and / or functions of each unit in STA 300 are respectively to implement the corresponding process of the first STA in the method 200 shown in FIG8. For the sake of brevity, they will not be described in detail here.

[0313] Figure 35 shows a schematic block diagram of a site STA 400 according to an embodiment of this application. The STA 400 is a second STA, and as shown in Figure 35, the STA 400 includes:

[0314] Communication unit 410 is used to report buffer information of time delay sensitive data on m1 frequency domain units;

[0315] Among them, the m1 frequency domain units are the frequency domain units reserved by the first STA in the first uplink transmission, and m1 is a positive integer.

[0316] In some embodiments, the frequency domain units among the m1 frequency domain units are resource units RU; or...

[0317] The frequency domain units in the m1 frequency domain units are sub-channels.

[0318] In some embodiments, the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP; or,

[0319] The first uplink transmission is the uplink transmission triggered by the access point (AP) after acquiring the TXOP; or,

[0320] The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

[0321] In some embodiments, before the second STA reports cached information for latency-sensitive data, the STA 400 further includes:

[0322] The processing unit 420 is used to determine, after learning that the first STA or AP has enabled the delay-sensitive transmission priority mode, that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the first uplink transmission.

[0323] In some embodiments, when the first STA has enabled the delay-sensitive transmission priority mode, the processing unit 420 is further configured to learn that the first STA has enabled the delay-sensitive transmission priority mode through a beacon frame or management frame sent by the AP.

[0324] In some embodiments, the latency-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, or the latency-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

[0325] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

[0326] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

[0327] In some embodiments, when the AP has enabled the delay-sensitive transmission priority mode, the processing unit 420 is further configured to know that the AP has enabled the delay-sensitive transmission priority mode by at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

[0328] In some embodiments, the AP indicates at least one of the following while indicating that it has enabled the delay-sensitive transmission priority mode: the duration of the delay-sensitive transmission priority mode enabled for the AP, and the m1 frequency domain units.

[0329] In some embodiments, the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

[0330] In some embodiments, before the second STA reports cached information for latency-sensitive data, the STA 400 further includes:

[0331] The processing unit 420 is used to determine, after the second STA learns that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in each uplink transmission of the TXOP it has won, that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in each uplink transmission of the TXOP.

[0332] In some embodiments, the processing unit 420 is further configured to learn, through the request sent by the first STA, that the first STA has reserved a frequency domain unit in the TXOP it has won for reporting delay-sensitive data in the RTS frame;

[0333] In this RTS frame, the unicast or multicast bits in the receive address RA are used to indicate whether the first STA has reserved frequency domain units for reporting delay-sensitive data in this TXOP.

[0334] In some embodiments, before the second STA reports the cached information of delay-sensitive data, the processing unit 420 is further configured to learn through the second trigger frame sent by the AP that the first STA has reserved a frequency domain unit for reporting cached information of delay-sensitive data in the first uplink transmission.

[0335] In some embodiments, the second trigger frame includes a fourth field;

[0336] The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data buffer information in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0337] The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

[0338] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or,

[0339] The first TXOP is the TXOP obtained by AP.

[0340] In some embodiments, the second trigger frame includes a fifth field; wherein the fifth field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0341] In some embodiments, the m1 frequency domain units are agreed upon by a protocol, or the m1 frequency domain units are configured by the AP.

[0342] In some embodiments, the communication unit 410 is specifically used for:

[0343] Buffer information for reporting delay-sensitive data in some or all of the m1 frequency domain units; or...

[0344] The cache information for reporting delay-sensitive data on the available frequency domain units in the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

[0345] In some embodiments, when the second STA reports cached information of latency-sensitive data on the available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried through a Quality of Service (QoS) empty frame.

[0346] In some embodiments, the communication unit 410 is further configured to report cached information of time-delay sensitive data on m2 frequency domain units;

[0347] The m2 frequency domain units are reserved by the first STA in the second uplink transmission, and m2 is a positive integer.

[0348] In some embodiments, the frequency domain units among the m² frequency domain units are RU; or...

[0349] The frequency domain units in these m2 frequency domain units are sub-channels.

[0350] In some embodiments, the frequency domain units in the m1 frequency domain units are the same as the frequency domain units in the m2 frequency domain units.

[0351] In some embodiments, the frequency domain units in the m1 frequency domain units are different from the frequency domain units in the m2 frequency domain units.

[0352] In some embodiments, when the amount of uplink latency-sensitive data to be transmitted exceeds x, the communication unit 410 is also used to report the cache information of latency-sensitive data through NDP or QoS empty frames, where x is 0 or a positive number.

[0353] In some embodiments, the value of x is determined by the protocol, or the value of x is configured or indicated by the AP in a beacon frame or trigger frame.

[0354] In some embodiments, when the second STA reports cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability long training field in the NDP indicates the AID information of the second STA.

[0355] In some embodiments, the AID information of each STA transmitting cached information carrying latency-sensitive data for an NDP is associated with a pass set index or a subcarrier set index.

[0356] In some embodiments, the bandwidth used by the UHR-LTF in this NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or,

[0357] The bandwidth used by the UHR-LTF in this NDP is one of the following: 26 channels, 52 channels, or 106 channels.

[0358] In some embodiments, each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or,

[0359] Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

[0360] In some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0361] It should be understood that the STA 400 according to the embodiments of this application can correspond to the second STA in the method embodiments of this application, and the above and other operations and / or functions of each unit in STA 400 are respectively to implement the corresponding process of the second STA in the method 200 shown in FIG8. For the sake of brevity, they will not be described in detail here.

[0362] Figure 36 shows a schematic block diagram of an access point AP 500 according to an embodiment of this application. As shown in Figure 36, the AP 500 includes:

[0363] Communication unit 510 is used to receive the first uplink transmission from the first station STA;

[0364] In this first uplink transmission, the first STA reserves m1 frequency domain units. These m1 frequency domain units are used to buffer information for one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data. m1 is a positive integer.

[0365] In some embodiments, the frequency domain units among the m1 frequency domain units are resource units RU; or...

[0366] The frequency domain units in the m1 frequency domain units are sub-channels.

[0367] In some embodiments, the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP; or,

[0368] The first uplink transmission is the uplink transmission triggered by the access point (AP) after acquiring the TXOP; or,

[0369] The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

[0370] In some embodiments, prior to the first uplink transmission, the communication unit 510 is further configured to send a first trigger frame to the first STA;

[0371] The first trigger frame includes a first field;

[0372] The first field is used to indicate that the first STA reserves frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0373] The first field is used to indicate that the first STA reserves a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first transmission opportunity (TXOP), and the first uplink transmission is the uplink transmission in the first TXOP.

[0374] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or,

[0375] The first TXOP is the TXOP obtained by the access point (AP).

[0376] In some embodiments, the first trigger frame further includes a second field; wherein the second field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0377] In some embodiments, the first trigger frame further includes a third field; wherein the third field is used to indicate parameter information for the other STA to perform null data physical protocol data unit (NDP) feedback.

[0378] In some embodiments, the parameter information fed back by the NDP includes at least one of the following: association identifier AID, starting AID, feedback type, uplink target received power, and number of users spatially multiplexed.

[0379] In some embodiments, if the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP, and one or more other STAs have reported buffer information of time-sensitive data on the m1 frequency domain units, the communication unit 510 is further configured to send preemption indication information to the first STA, wherein the preemption indication information is used to indicate that the AP will preempt the TXOP acquired by the first STA.

[0380] In some embodiments, the preemption indication information is carried in a block confirmation frame corresponding to the first uplink transmission, or the preemption indication information is carried in a management frame.

[0381] In some embodiments, when the preemption indication information is carried through the block acknowledgment frame corresponding to the first uplink transmission, the block acknowledgment control field in the block acknowledgment frame corresponding to the first uplink transmission includes a field for indicating that the AP will preempt the TXOP acquired by the first STA.

[0382] In some embodiments, after learning that the first STA or the AP has enabled the delay-sensitive transmission priority mode, the other STA determines that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data cache information.

[0383] In some embodiments, when the first STA has enabled the delay-sensitive transmission priority mode, the other STAs can learn that the first STA has enabled the delay-sensitive transmission priority mode through the beacon frame or management frame sent by the AP.

[0384] In some embodiments, the latency-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, or the latency-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

[0385] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

[0386] In some embodiments, when the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

[0387] In some embodiments, when the AP has enabled the delay-sensitive transmission priority mode, the other STA learns that the AP has enabled the delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

[0388] In some embodiments, the AP indicates at least one of the following while indicating that it has enabled the delay-sensitive transmission priority mode: the duration of the delay-sensitive transmission priority mode enabled for the AP, and the m1 frequency domain units.

[0389] In some embodiments, the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

[0390] In some embodiments, the communication unit 510 is further configured to send a second trigger frame, which is configured to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the first uplink transmission.

[0391] In some embodiments, the second trigger frame includes a fourth field;

[0392] The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data buffer information in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or...

[0393] The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

[0394] In some embodiments, the first TXOP is the TXOP obtained by the first STA; or,

[0395] The first TXOP is the TXOP obtained by AP.

[0396] In some embodiments, the second trigger frame includes a fifth field; wherein the fifth field is used to indicate frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

[0397] In some embodiments, the m1 frequency domain units are agreed upon by a protocol, or the m1 frequency domain units are configured by the AP.

[0398] In some embodiments, the communication unit 510 is further configured to receive buffer information of delay-sensitive data reported by one or more other STAs using some or all of the frequency domain units in the m1 frequency domain units; or,

[0399] The communication unit 510 is also used to receive buffer information of delay-sensitive data reported by one or more other STAs on available frequency domain units among the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

[0400] In some embodiments, when other STAs report cached information of latency-sensitive data on available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried through a Quality of Service (QoS) empty frame.

[0401] In some embodiments, the communication unit 510 is further configured to receive a second uplink transmission from the first STA;

[0402] In this second uplink transmission, the first STA reserves m2 frequency domain units. These m2 frequency domain units are used to buffer information for one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data. m2 is a positive integer.

[0403] In some embodiments, the frequency domain units among the m² frequency domain units are RU; or...

[0404] The frequency domain units in these m2 frequency domain units are sub-channels.

[0405] In some embodiments, the frequency domain units in the m1 frequency domain units are the same as the frequency domain units in the m2 frequency domain units.

[0406] In some embodiments, the frequency domain units in the m1 frequency domain units are different from the frequency domain units in the m2 frequency domain units.

[0407] In some embodiments, one or more other STAs with more than a number x of uplink latency-sensitive data to be transmitted report cached information of latency-sensitive data via NDP or QoS empty frames, where x is 0 or a positive number.

[0408] In some embodiments, the value of x is determined by the protocol, or the value of x is configured or indicated by the AP in a beacon frame or trigger frame.

[0409] In some embodiments, when other STAs report cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability training field in the NDP indicates the AID information of the STA that sent the NDP.

[0410] In some embodiments, the AID information of each STA that transmits the NDP is associated with a pass set index or a subcarrier set index.

[0411] In some embodiments, the bandwidth used by the UHR-LTF in this NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or,

[0412] The bandwidth used by the UHR-LTF in this NDP is one of the following: 26 channels, 52 channels, or 106 channels.

[0413] In some embodiments, each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or,

[0414] Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

[0415] In some embodiments, for uplink transmission of frequency domain units that reserve cache information for reporting delay-sensitive data, the duration of the Physical Layer Protocol Data Unit (PPDU) for uplink data transmission by the first STA is less than or equal to a preset value.

[0416] In some embodiments, the preset value is negatively correlated with the number of frequency domain units reserved by the first STA in uplink transmission for reporting delay-sensitive data cache information.

[0417] In some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0418] It should be understood that the AP 500 according to the embodiments of this application can correspond to the AP in the method embodiments of this application, and the above and other operations and / or functions of each unit in AP 500 are respectively to implement the corresponding process of AP in method 200 shown in FIG8. For the sake of brevity, they will not be described in detail here.

[0419] Figure 37 is a schematic structural diagram of a communication device 600 provided in an embodiment of this application. The communication device 600 shown in Figure 37 includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0420] In some embodiments, as shown in FIG37, the communication device 600 may further include a memory 620. The processor 610 may retrieve and run computer programs from the memory 620 to implement the methods described in the embodiments of this application.

[0421] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0422] In some embodiments, as shown in FIG37, the communication device 600 may further include a transceiver 630, which the processor 610 may control to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0423] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

[0424] In some embodiments, the processor 610 can implement the functions of the processing unit in the STA, or the processor 610 can implement the functions of the processing unit in the AP. For the sake of brevity, these will not be described in detail here.

[0425] In some embodiments, transceiver 630 can implement the functions of a communication unit in a STA, which will not be described in detail here for the sake of brevity.

[0426] In some embodiments, transceiver 630 can perform the functions of a communication unit in an AP, which will not be described in detail here for the sake of brevity.

[0427] In some embodiments, the communication device 600 may specifically be an AP in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0428] In some embodiments, the communication device 600 may specifically be a STA in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the first STA or the second STA in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0429] Figure 38 is a schematic structural diagram of an apparatus according to an embodiment of this application. The apparatus 700 shown in Figure 38 includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0430] In some embodiments, as shown in FIG38, the device 700 may further include a memory 720. The processor 710 may retrieve and run computer programs from the memory 720 to implement the methods described in the embodiments of this application.

[0431] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0432] In some embodiments, the processor 710 can implement the functions of the processing unit in the STA, or the processor 710 can implement the functions of the processing unit in the AP. For the sake of brevity, these will not be described in detail here.

[0433] In some embodiments, the device 700 may further include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips. Optionally, the processor 710 may be located inside or outside the chip.

[0434] In some embodiments, the input interface 730 can implement the function of a communication unit in a STA, or the input interface 730 can implement the function of a communication unit in an AP.

[0435] In some embodiments, the device 700 may further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips. Optionally, the processor 710 may be located inside or outside the chip.

[0436] In some embodiments, the output interface 740 can implement the function of a communication unit in a STA, or the output interface 740 can implement the function of a communication unit in an AP.

[0437] In some embodiments, the device can be applied to the AP in the embodiments of this application, and the device can implement the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0438] In some embodiments, the device can be applied to the STA in the embodiments of this application, and the device can implement the corresponding processes implemented by the first STA or the second STA in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0439] In some embodiments, the apparatus mentioned in the present application may also be a chip. For example, it may be a system-on-a-chip, a system-on-a-chip, a chip system, or a system-on-a-chip, etc.

[0440] Figure 39 is a schematic block diagram of a communication system 800 provided in an embodiment of this application. As shown in Figure 39, the communication system 800 includes a STA 810 and an AP 820.

[0441] Specifically, the STA 810 can be used to implement the corresponding functions implemented by the first STA or the second STA in the above method, and the AP 820 can be used to implement the corresponding functions implemented by the AP in the above method. For the sake of brevity, these will not be elaborated further here.

[0442] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0443] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0444] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0445] This application also provides a computer-readable storage medium for storing computer programs.

[0446] In some embodiments, the computer-readable storage medium may be applied to the AP in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0447] In some embodiments, the computer-readable storage medium may be applied to the STA in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first STA or the second STA in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0448] This application also provides a computer program product, including computer program instructions.

[0449] In some embodiments, the computer program product can be applied to the AP in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0450] In some embodiments, the computer program product can be applied to the STA in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first STA or the second STA in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0451] This application also provides a computer program.

[0452] In some embodiments, the computer program can be applied to the AP in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0453] In some embodiments, the computer program can be applied to the STA in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the first STA or the second STA in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0454] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0455] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

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

[0459] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A method for wireless communication, characterized in that, include: The first station (STA) reserves m1 frequency domain units in the first uplink transmission; wherein, the m1 frequency domain units are used for buffering information of one or more other STAs reporting delay-sensitive data that contains uplink delay-sensitive data to be transmitted, and m1 is a positive integer.

2. The method as described in claim 1, characterized in that, The frequency domain units among the m1 frequency domain units are resource units RU; or... The frequency domain units among the m1 frequency domain units are sub-channels.

3. The method as described in claim 1 or 2, characterized in that, The first uplink transmission is the uplink transmission performed by the first STA after acquiring the TXOP; or, The first uplink transmission is an uplink transmission triggered by the access point (AP) after acquiring the TXOP, executed by the first STA; or, The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

4. The method according to any one of claims 1 to 3, characterized in that, Before the first STA performs the first uplink transmission, the method further includes: The first STA receives the first trigger frame; The first trigger frame includes a first field; The first field is used to indicate that the first STA reserves frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or, The first field is used to indicate that the first STA reserves a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first transmission opportunity TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

5. The method as described in claim 4, characterized in that, The first TXOP is the TXOP obtained by the first STA; or, The first TXOP is the TXOP obtained by the access point (AP).

6. The method as described in claim 4 or 5, characterized in that, The first trigger frame further includes a second field; wherein the second field is used to indicate the frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

7. The method according to any one of claims 4 to 6, characterized in that, The first trigger frame further includes a third field; wherein the third field is used to indicate the parameter information of the other STAs for feedback of the Null Data Physical Protocol Data Unit (NDP).

8. The method as described in claim 7, characterized in that, The NDP feedback parameter information includes at least one of the following: association identifier AID, starting AID, feedback type, uplink target received power, and number of users spatially multiplexed.

9. The method according to any one of claims 1 to 8, characterized in that, If the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP, and one or more other STAs have reported buffer information for delay-sensitive data on the m1 frequency domain units, the method further includes: The first STA receives a preemption instruction, wherein the preemption instruction is used to instruct the AP to preempt the TXOP acquired by the first STA.

10. The method as described in claim 9, characterized in that, The preemption indication information is carried in the block confirmation frame corresponding to the first uplink transmission, or the preemption indication information is carried in the management frame.

11. The method as described in claim 10, characterized in that, When the preemption indication information is carried through the block acknowledgment frame corresponding to the first uplink transmission, the block acknowledgment control field in the block acknowledgment frame corresponding to the first uplink transmission includes a field for instructing the AP to preempt the TXOP acquired by the first STA.

12. The method according to any one of claims 1 to 11, characterized in that, After learning that the first STA or AP has enabled the delay-sensitive transmission priority mode, the other STAs determine that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data cache information.

13. The method as described in claim 12, characterized in that, When the first STA has enabled the delay-sensitive transmission priority mode, the other STAs can learn that the first STA has enabled the delay-sensitive transmission priority mode through beacon frames or management frames sent by the AP.

14. The method as described in claim 13, characterized in that, The delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the AP's request, or the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

15. The method as described in claim 14, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

16. The method as described in claim 14, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

17. The method as described in claim 12, characterized in that, When the AP has enabled the delay-sensitive transmission priority mode, the other STAs will know that the AP has enabled the delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

18. The method as described in claim 17, characterized in that, The AP indicates that it has enabled the delay-sensitive transmission priority mode, and at the same time indicates at least one of the following: the duration of the delay-sensitive transmission priority mode enabled by the AP, and the m1 frequency domain units.

19. The method as described in claim 17 or 18, characterized in that, The enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

20. The method according to any one of claims 1 to 11, characterized in that, After the other STAs learn that the first STA has reserved frequency domain units in the TXOP it has won for reporting delay-sensitive data, they determine that the first STA has reserved frequency domain units in each uplink transmission in the TXOP for reporting delay-sensitive data.

21. The method as described in claim 20, characterized in that, The other STAs learn from the request sent by the first STA that the first STA has reserved frequency domain units in the TXOP it has won for reporting latency-sensitive data by sending an RTS frame; In the RTS frame, the unicast or multicast bits in the receive address RA are used to indicate whether the first STA has reserved a frequency domain unit for reporting delay-sensitive data in this TXOP.

22. The method according to any one of claims 1 to 11, characterized in that, The other STAs learn through the second trigger frame sent by the AP that the first STA has reserved a frequency domain unit in the first uplink transmission for reporting delay-sensitive data cache information.

23. The method as described in claim 22, characterized in that, The second trigger frame includes a fourth field; The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or... The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

24. The method as described in claim 23, characterized in that, The first TXOP is the TXOP obtained by the first STA; or, The first TXOP is the TXOP obtained by AP.

25. The method according to any one of claims 22 to 24, characterized in that, The second trigger frame includes a fifth field; wherein the fifth field is used to indicate the frequency domain unit information reserved by the first STA for reporting delay-sensitive data.

26. The method according to any one of claims 1 to 25, characterized in that, The m1 frequency domain units are defined by the protocol, or the m1 frequency domain units are configured by the AP.

27. The method according to any one of claims 1 to 26, characterized in that, The other STAs use some or all of the frequency domain units in the m1 frequency domain units to report cached information of delay-sensitive data; Alternatively, the other STAs may report cached information of delay-sensitive data on the available frequency domain units among the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

28. The method as described in claim 27, characterized in that, When other STAs report cached information of latency-sensitive data on available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried through Quality of Service (QoS) empty frames.

29. The method according to any one of claims 1 to 28, characterized in that, The method further includes: The first STA reserves m2 frequency domain units in the second uplink transmission; wherein, the m2 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data containing uplink delay-sensitive data to be transmitted, and m2 is a positive integer.

30. The method as described in claim 29, characterized in that, The frequency domain units among the m² frequency domain units are RU; or... The frequency domain units among the m2 frequency domain units are sub-channels.

31. The method as described in claim 29 or 30, characterized in that, The frequency domain units in the m1 frequency domain units are the same as those in the m2 frequency domain units.

32. The method as described in claim 29 or 30, characterized in that, The frequency domain units in the m1 frequency domain units are different from those in the m2 frequency domain units.

33. The method according to any one of claims 1 to 32, characterized in that, One or more other STAs with more than x uplink latency-sensitive data to be transmitted report buffer information of latency-sensitive data via NDP or QoS empty frames, where x is 0 or a positive number.

34. The method as described in claim 33, characterized in that, The value of x is determined by the protocol, or the value of x is configured or indicated by the AP in the beacon frame or trigger frame.

35. The method as described in claim 33 or 34, characterized in that, When other STAs report cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability long training field in the NDP indicates the AID information of the STA that sent the NDP.

36. The method as described in claim 35, characterized in that, Each STA transmitting the NDP has its AID information associated with a pass set index or subcarrier set index.

37. The method as described in claim 35 or 36, characterized in that, The bandwidth used by the UHR-LTF in the NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or, The bandwidth used by the UHR-LTF in the NDP is one of the following: 26 channels, 52 channels, or 106 channels.

38. The method according to any one of claims 35 to 37, characterized in that, Each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or, Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

39. The method according to any one of claims 1 to 38, characterized in that, For uplink transmission of frequency domain units that reserve buffer information for reporting latency-sensitive data, the duration of the Physical Layer Protocol Data Unit (PPDU) for the first STA transmitting uplink data is less than or equal to a preset value.

40. The method as described in claim 39, characterized in that, The preset value is negatively correlated with the number of frequency domain units reserved by the first STA in uplink transmission for reporting delay-sensitive data.

41. A method for wireless communication, characterized in that, include: The second station STA reports buffer information for time-delay sensitive data on m1 frequency domain units; Wherein, the m1 frequency domain units are frequency domain units reserved by the first STA in the first uplink transmission, and m1 is a positive integer.

42. The method as described in claim 41, characterized in that, The frequency domain units among the m1 frequency domain units are resource units RU; or... The frequency domain units among the m1 frequency domain units are sub-channels.

43. The method as described in claim 41 or 42, characterized in that, The first uplink transmission is the uplink transmission performed by the first STA after acquiring the TXOP; or, The first uplink transmission is an uplink transmission triggered by the access point (AP) after acquiring the TXOP, executed by the first STA; or, The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

44. The method according to any one of claims 41 to 43, characterized in that, Before the second STA reports the cached information of latency-sensitive data, the method further includes: After the second STA learns that the first STA or AP has enabled the delay-sensitive transmission priority mode, it determines that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data buffer information.

45. The method as described in claim 44, characterized in that, The method further includes: When the first STA has enabled the delay-sensitive transmission priority mode, the second STA learns that the first STA has enabled the delay-sensitive transmission priority mode through the beacon frame or management frame sent by the AP.

46. ​​The method as described in claim 45, characterized in that, The delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the AP's request, or the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

47. The method as described in claim 46, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

48. The method as described in claim 46, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

49. The method as described in claim 44, characterized in that, The method further includes: When the AP has enabled the delay-sensitive transmission priority mode, the second STA learns that the AP has enabled the delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

50. The method as described in claim 49, characterized in that, The AP indicates that it has enabled the delay-sensitive transmission priority mode, and at the same time indicates at least one of the following: the duration of the delay-sensitive transmission priority mode enabled by the AP, and the m1 frequency domain units.

51. The method as described in claim 49 or 50, characterized in that, The enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

52. The method according to any one of claims 41 to 43, characterized in that, Before the second STA reports the cached information of latency-sensitive data, the method further includes: After learning that the first STA has reserved frequency domain units in the TXOP it has won for reporting delay-sensitive data, the second STA determines that the first STA has reserved frequency domain units in each uplink transmission in the TXOP for reporting delay-sensitive data.

53. The method as described in claim 52, characterized in that, The method further includes: The second STA learns from the request sent by the first STA that the first STA has reserved a frequency domain unit in the TXOP it has won in order to report buffer information for time-sensitive data by sending an RTS frame; In the RTS frame, the unicast or multicast bits in the receive address RA are used to indicate whether the first STA has reserved a frequency domain unit for reporting delay-sensitive data in this TXOP.

54. The method according to any one of claims 41 to 43, characterized in that, Before the second STA reports the cached information of latency-sensitive data, the method further includes: The second STA learns from the second trigger frame sent by the AP that the first STA has reserved a frequency domain unit for reporting delay-sensitive data cache information in the first uplink transmission.

55. The method as described in claim 54, characterized in that, The second trigger frame includes a fourth field; The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or... The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

56. The method as described in claim 55, characterized in that, The first TXOP is the TXOP obtained by the first STA; or, The first TXOP is the TXOP obtained by AP.

57. The method according to any one of claims 54 to 56, characterized in that, The second trigger frame includes a fifth field; wherein the fifth field is used to indicate the frequency domain unit information reserved by the first STA for reporting delay-sensitive data.

58. The method according to any one of claims 41 to 57, characterized in that, The m1 frequency domain units are defined by the protocol, or the m1 frequency domain units are configured by the AP.

59. The method according to any one of claims 41 to 58, characterized in that, The second STA reports buffer information for delay-sensitive data on m1 frequency domain units, including: The second STA reports buffer information of delay-sensitive data in some or all of the frequency domain units in the m1 frequency domain units; or, The second STA reports the cache information of delay-sensitive data on the available frequency domain units among the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

60. The method as described in claim 59, characterized in that, When the second STA reports cached information of latency-sensitive data on the available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried by the Quality of Service (QoS) empty frame.

61. The method according to any one of claims 41 to 60, characterized in that, The method further includes: The second STA reports buffer information for delay-sensitive data across m2 frequency domain units; Wherein, the m2 frequency domain units are the frequency domain units reserved by the first STA in the second uplink transmission, and m2 is a positive integer.

62. The method as described in claim 61, characterized in that, The frequency domain units among the m² frequency domain units are RU; or... The frequency domain units among the m2 frequency domain units are sub-channels.

63. The method as described in claim 61 or 62, characterized in that, The frequency domain units in the m1 frequency domain units are the same as those in the m2 frequency domain units.

64. The method as described in claim 61 or 62, characterized in that, The frequency domain units in the m1 frequency domain units are different from those in the m2 frequency domain units.

65. The method according to any one of claims 41 to 64, characterized in that, The method further includes: If the amount of uplink latency-sensitive data to be transmitted exceeds x, the second STA reports the buffer information of the latency-sensitive data through NDP or QoS empty frames, where x is 0 or a positive number.

66. The method as described in claim 65, characterized in that, The value of x is determined by the protocol, or the value of x is configured or indicated by the AP in the beacon frame or trigger frame.

67. The method as described in claim 65 or 66, characterized in that, When the second STA reports the cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability long training field in the NDP indicates the AID information of the second STA.

68. The method as described in claim 67, characterized in that, Each STA's AID information for an NDP that transmits buffered information carrying latency-sensitive data is associated with a pass set index or subcarrier set index.

69. The method as described in claim 67 or 68, characterized in that, The bandwidth used by the UHR-LTF in the NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or, The bandwidth used by the UHR-LTF in the NDP is one of the following: 26 channels, 52 channels, or 106 channels.

70. The method according to any one of claims 67 to 69, characterized in that, Each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or, Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

71. A method for wireless communication, characterized in that, include: Access point (AP) receives the first uplink transmission from the first site (STA); In the first uplink transmission, the first STA reserves m1 frequency domain units. The m1 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data. m1 is a positive integer.

72. The method as described in claim 71, characterized in that, The frequency domain units among the m1 frequency domain units are resource units RU; or... The frequency domain units among the m1 frequency domain units are sub-channels.

73. The method as described in claim 71 or 72, characterized in that, The first uplink transmission is the uplink transmission performed by the first STA after acquiring the TXOP; or, The first uplink transmission is an uplink transmission triggered by the access point (AP) after acquiring the TXOP, executed by the first STA; or, The first uplink transmission is an uplink response or uplink acknowledgment to the downlink transmission performed by the AP after acquiring the TXOP.

74. The method according to any one of claims 71 to 73, characterized in that, Prior to the first uplink transmission, the method further includes: The AP sends a first trigger frame to the first STA; The first trigger frame includes a first field; The first field is used to indicate that the first STA reserves frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or, The first field is used to indicate that the first STA reserves a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first transmission opportunity TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

75. The method as described in claim 74, characterized in that, The first TXOP is the TXOP obtained by the first STA; or, The first TXOP is the TXOP obtained by the access point (AP).

76. The method as described in claim 74 or 75, characterized in that, The first trigger frame further includes a second field; wherein the second field is used to indicate the frequency domain unit information reserved by the first STA for reporting latency-sensitive data.

77. The method according to any one of claims 74 to 76, characterized in that, The first trigger frame further includes a third field; wherein the third field is used to indicate the parameter information of the other STAs for feedback of the Null Data Physical Protocol Data Unit (NDP).

78. The method as described in claim 77, characterized in that, The NDP feedback parameter information includes at least one of the following: association identifier AID, starting AID, feedback type, uplink target received power, and number of users spatially multiplexed.

79. The method according to any one of claims 71 to 78, characterized in that, If the first uplink transmission is an uplink transmission performed by the first STA after acquiring the TXOP, and one or more other STAs have reported buffer information for delay-sensitive data on the m1 frequency domain units, the method further includes: The AP sends a preemption instruction to the first STA, wherein the preemption instruction is used to instruct the AP to preempt the TXOP acquired by the first STA.

80. The method as described in claim 79, characterized in that, The preemption indication information is carried in the block confirmation frame corresponding to the first uplink transmission, or the preemption indication information is carried in the management frame.

81. The method as described in claim 80, characterized in that, When the preemption indication information is carried through the block acknowledgment frame corresponding to the first uplink transmission, the block acknowledgment control field in the block acknowledgment frame corresponding to the first uplink transmission includes a field for indicating that the AP will preempt the TXOP acquired by the first STA.

82. The method according to any one of claims 71 to 81, characterized in that, After the other STAs learn that the first STA or the AP has enabled the delay-sensitive transmission priority mode, they determine that the first STA has reserved frequency domain units in the first uplink transmission for reporting delay-sensitive data cache information.

83. The method as described in claim 82, characterized in that, When the first STA has enabled the delay-sensitive transmission priority mode, the other STAs can learn that the first STA has enabled the delay-sensitive transmission priority mode through the beacon frame or management frame sent by the AP.

84. The method as described in claim 83, characterized in that, The latency-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, or the latency-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and notified to the AP.

85. The method as described in claim 84, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled based on the request of the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is configured by the AP in the request information, and / or, the m1 frequency domain units are configured by the AP in the request information.

86. The method as described in claim 84, characterized in that, When the delay-sensitive transmission priority mode corresponding to the first STA is enabled by the first STA and the first STA notifies the AP, the duration of the enabled delay-sensitive transmission priority mode corresponding to the first STA is indicated by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the first STA in the notification information, and / or, the m1 frequency domain units are configured by the AP in the notification response.

87. The method as described in claim 82, characterized in that, When the AP has enabled the delay-sensitive transmission priority mode, the other STAs will know that the AP has enabled the delay-sensitive transmission priority mode through at least one of the following frames sent by the AP: beacon frame, probe response frame, association response frame, reassociation response frame, and operating mode announcement frame.

88. The method as described in claim 87, characterized in that, The AP indicates that it has enabled the delay-sensitive transmission priority mode, and at the same time indicates at least one of the following: the duration of the delay-sensitive transmission priority mode enabled by the AP, and the m1 frequency domain units.

89. The method as described in claim 87 or 88, characterized in that, The enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is associated with the transmission information of delay-sensitive data in the Basic Service Set (BSS), or the enabling and / or disabling of the delay-sensitive transmission priority mode corresponding to the AP is set by user signaling.

90. The method according to any one of claims 71 to 81, characterized in that, The method further includes: The AP sends a second trigger frame, which is used to instruct the first STA to reserve a frequency domain unit for reporting delay-sensitive data in the first uplink transmission.

91. The method as described in claim 90, characterized in that, The second trigger frame includes a fourth field; The fourth field is used to indicate that the first STA has reserved frequency domain units for reporting delay-sensitive data in at least one uplink transmission, wherein the at least one uplink transmission includes the first uplink transmission; or... The fourth field is used to indicate that the first STA has reserved a frequency domain unit for reporting delay-sensitive data in the uplink transmission of the first TXOP, and the first uplink transmission is the uplink transmission in the first TXOP.

92. The method as described in claim 91, characterized in that, The first TXOP is the TXOP obtained by the first STA; or, The first TXOP is the TXOP obtained by AP.

93. The method according to any one of claims 90 to 92, characterized in that, The second trigger frame includes a fifth field; wherein the fifth field is used to indicate the frequency domain unit information reserved by the first STA for reporting delay-sensitive data.

94. The method according to any one of claims 71 to 93, characterized in that, The m1 frequency domain units are defined by the protocol, or the m1 frequency domain units are configured by the AP.

95. The method according to any one of claims 71 to 94, characterized in that, The method further includes: The AP receives buffer information of delay-sensitive data reported by one or more other STAs using some or all of the frequency domain units in the m1 frequency domain units; or... The AP receives cached information of delay-sensitive data reported by one or more other STAs on available frequency domain units among the m1 frequency domain units obtained by the random access UORA mechanism based on uplink orthogonal frequency division multiple access.

96. The method as described in claim 95, characterized in that, When other STAs report cached information of latency-sensitive data on available frequency domain units among the m1 frequency domain units obtained by the UORA mechanism, the cached information of latency-sensitive data reported on the available frequency domain units is carried through Quality of Service (QoS) empty frames.

97. The method according to any one of claims 71 to 96, characterized in that, The method further includes: The AP receives the second uplink transmission from the first STA; In the second uplink transmission, the first STA reserves m2 frequency domain units. The m2 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data, where m2 is a positive integer.

98. The method as described in claim 97, characterized in that, The frequency domain units among the m² frequency domain units are RU; or... The frequency domain units among the m2 frequency domain units are sub-channels.

99. The method as described in claim 97 or 98, characterized in that, The frequency domain units in the m1 frequency domain units are the same as those in the m2 frequency domain units.

100. The method as described in claim 97 or 98, characterized in that, The frequency domain units in the m1 frequency domain units are different from those in the m2 frequency domain units.

101. The method according to any one of claims 71 to 100, characterized in that, One or more other STAs with more than x uplink latency-sensitive data to be transmitted report buffer information of latency-sensitive data via NDP or QoS empty frames, where x is 0 or a positive number.

102. The method as described in claim 101, characterized in that, The value of x is determined by the protocol, or the value of x is configured or indicated by the AP in the beacon frame or trigger frame.

103. The method as described in claim 101 or 102, characterized in that, When other STAs report cached information of latency-sensitive data through NDP, the pass set index or subcarrier set index used by the UHR-LTF ultra-high reliability long training field in the NDP indicates the AID information of the STA that sent the NDP.

104. The method as described in claim 103, characterized in that, Each STA transmitting the NDP has its AID information associated with a pass set index or subcarrier set index.

105. The method as described in claim 103 or 104, characterized in that, The bandwidth used by the UHR-LTF in the NDP is one of the following: 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, 320MHz; or, The bandwidth used by the UHR-LTF in the NDP is one of the following: 26 channels, 52 channels, or 106 channels.

106. The method according to any one of claims 103 to 105, characterized in that, Each pass set index corresponds to n1 subcarriers, where n1 = 4, 5, or 6; or, Each subcarrier set index corresponds to n2 subcarriers, where n2 = 4, 5, or 6.

107. The method according to any one of claims 71 to 106, characterized in that, For uplink transmission of frequency domain units that reserve buffer information for reporting latency-sensitive data, the duration of the Physical Layer Protocol Data Unit (PPDU) for the first STA transmitting uplink data is less than or equal to a preset value.

108. The method as described in claim 107, characterized in that, The preset value is negatively correlated with the number of frequency domain units reserved by the first STA in uplink transmission for reporting delay-sensitive data.

109. A station STA, characterized in that, The STA is a first STA, and the STA includes: The processing unit is used to reserve m1 frequency domain units in the first uplink transmission; wherein the m1 frequency domain units are used for buffering information of one or more other STA-reported delay-sensitive data containing uplink delay-sensitive data to be transmitted, and m1 is a positive integer.

110. A station STA, characterized in that, The STA is a second STA, and the STA includes: The communication unit is used to report buffer information of time-delay sensitive data on m1 frequency domain units; Wherein, the m1 frequency domain units are frequency domain units reserved by the first STA in the first uplink transmission, and m1 is a positive integer.

111. An access point (AP), characterized in that, include: The communication unit is used to receive the first uplink transmission from the first station STA. In the first uplink transmission, the first STA reserves m1 frequency domain units. The m1 frequency domain units are used for buffering information of one or more other STAs that report delay-sensitive data to be transmitted uplink delay-sensitive data. m1 is a positive integer.

112. A station STA, characterized in that, The STA is a first STA, and the STA includes: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory, causing the STA to perform the method as described in any one of claims 1 to 40.

113. A station STA, characterized in that, The STA is a second STA, and the STA includes: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory, causing the STA to perform the method as described in any one of claims 41 to 70.

114. An access point (AP), characterized in that, include: A processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program stored in the memory, causing the AP to perform the method as described in any one of claims 71 to 108.

115. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 40.

116. A chip, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 41 to 70.

117. A chip, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 71 to 108.

118. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed, implements the method as described in any one of claims 1 to 40.

119. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed, implements the method as described in any one of claims 41 to 70.

120. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed, implements the method as described in any one of claims 71 to 108.

121. A computer program product, characterized in that, It includes computer program instructions, which, when executed, implement the method as described in any one of claims 1 to 40.

122. A computer program product, characterized in that, It includes computer program instructions, which, when executed, implement the method as described in any one of claims 41 to 70.

123. A computer program product, characterized in that, It includes computer program instructions, which, when executed, implement the method as described in any one of claims 71 to 108.

124. A computer program, characterized in that, When the computer program is executed, the method as described in any one of claims 1 to 40 is implemented.

125. A computer program, characterized in that, When the computer program is executed, the method as described in any one of claims 41 to 70 is implemented.

126. A computer program, characterized in that, When the computer program is executed, the method as described in any one of claims 71 to 108 is implemented.

Images