Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a device. The method comprises: in a first TXOP, a first STA sending first uplink transmission to an AP, wherein the first STA reserves one or more frequency-domain units in the first uplink transmission, the one or more frequency-domain units are used for reporting first indication information by means of a second STA, and the first indication information is used for indicating that the second STA includes low-latency traffic to be transmitted, and / or the second STA needs to preempt the first TXOP. By means of the one or more frequency-domain units reserved by the first STA, the second STA may report the first indication information. On the basis of the first indication information, the second STA may preempt the first TXOP, thereby transmitting the low-latency traffic in a timely manner.

Description

Wireless communication methods and communication devices Technical Field

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

[0002] Event-driven low-latency traffic is unpredictable and therefore cannot be transmitted by pre-scheduling appropriate resources. Improving the transmission performance of latency-sensitive traffic is a problem that needs to be solved.

[0003] Summary of the Invention

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

[0005] In a first aspect, a wireless communication method is provided. The method includes: within a first transmission opportunity (TXOP), a first station (STA) sends a first uplink transmission to an access point (AP); wherein the first STA reserves one or more frequency domain units in the first uplink transmission, and the one or more frequency domain units are used by a second STA to report first indication information, the first indication information indicating that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0006] Secondly, a wireless communication method is provided. The method includes: within a first TXOP, a second STA reports first indication information to an AP on one or more frequency domain units; wherein the one or more frequency domain units are frequency domain resources reserved by the first STA in a first uplink transmission, and the first indication information indicates that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0007] Thirdly, a wireless communication method is provided, the method comprising: within a first TXOP, an AP receiving a first uplink transmission from a first STA; wherein the first STA reserves one or more frequency domain units in the first uplink transmission, the one or more frequency domain units being used by a second STA to report first indication information, the first indication information being used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0008] Fourthly, a communication device is provided, which is a first STA. The communication device includes: a transmitting unit for sending a first uplink transmission to an AP within a first TXOP; wherein the first STA reserves one or more frequency domain units in the first uplink transmission, and the one or more frequency domain units are used by a second STA to report first indication information, the first indication information indicating that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0009] Fifthly, a communication device is provided, which is a second STA. The communication device includes: a reporting unit, used to report first indication information to the AP on one or more frequency domain units within a first TXOP; wherein the one or more frequency domain units are frequency domain resources reserved by the first STA in a first uplink transmission, and the first indication information is used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0010] In a sixth aspect, a communication device is provided, which is an access point (AP). The communication device includes: a receiving unit, configured to receive a first uplink transmission from a first station (STA) within a first TXOP; wherein the first STA reserves one or more frequency domain units in the first uplink transmission, and the one or more frequency domain units are used by a second STA to report first indication information, the first indication information indicating that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0011] A seventh aspect provides a communication device, including a processor and a memory, the memory for storing one or more computer programs, the processor for invoking the computer programs in the memory to cause the communication device to perform some or all of the steps in the method of the first aspect.

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

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

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

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

[0016] The second STA can report first indication information using one or more frequency domain units reserved by the first STA. Based on the first indication information, the second STA can preempt the first TXOP, thereby enabling timely transmission of low-latency traffic. Attached Figure Description

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

[0018] Figure 2 is an example of the cache status report polling trigger frame format.

[0019] Figure 3 is an example diagram of the Quality of Service (QoS) empty frame format.

[0020] Figure 4 is an example of the polling trigger frame format for the feedback report of the empty data physical layer protocol data unit.

[0021] Figure 5 is an example diagram of the format of the feedback parameter set element of the data unit in the empty data physical layer transmission protocol.

[0022] Figure 6 is an example diagram of the data unit format of the efficient null data physical layer protocol based on trigger feedback.

[0023] Figure 7 is an example diagram of a low-latency transmission resource reservation scheme based on puncturing.

[0024] Figure 8 is an example diagram of a scheme that indicates low-latency data traffic based on overlapping physical layer protocol data units (PPDUs).

[0025] Figure 9 is an example diagram of the frequency domain resources of the low latency indicator frame.

[0026] Figure 10 is an example diagram of a technical solution that uses a smaller inter-frame interval to transmit preemption requests.

[0027] Figure 11 is an example diagram of the transmission process of the strong preemption request corresponding to Figure 10.

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

[0029] Figure 13 is a schematic diagram of a first trigger frame format provided in an embodiment of this application.

[0030] Figure 14 is an example diagram of the High Efficiency Sounding NDP (HE Sounding NDP) physical layer protocol data unit format.

[0031] Figure 15 is an example diagram of an EHT sounding NDP format.

[0032] Figure 16 is an example diagram of the Ultra-Reliable Sounding NDP (UHR) physical layer protocol data unit format.

[0033] Figure 17 is a schematic diagram of a second type of PPDU format provided in an embodiment of this application.

[0034] Figure 18 is a schematic diagram of the format of a second trigger frame provided in an embodiment of this application.

[0035] Figure 19 is a schematic diagram of another second trigger frame format provided in an embodiment of this application.

[0036] Figure 20 is a schematic diagram of another second trigger frame format provided in an embodiment of this application.

[0037] Figure 21 is a schematic diagram of another second trigger frame format provided in an embodiment of this application.

[0038] Figure 22 is a schematic diagram of another second trigger frame format provided in an embodiment of this application.

[0039] Figure 23 is a schematic diagram of another second trigger frame format provided in an embodiment of this application.

[0040] Figure 24 is a schematic diagram of the block confirmation frame format provided in an embodiment of this application.

[0041] Figure 25 is an example diagram of a wireless communication method provided in an embodiment of this application.

[0042] Figure 26 is an example diagram of a wireless communication method provided in Embodiment 1 of this application.

[0043] Figure 27 is an example diagram of a wireless communication method provided in Embodiment 2 of this application.

[0044] Figure 28 is an example diagram of a wireless communication method provided in Embodiment 3 of this application.

[0045] Figure 29 is an example diagram of a wireless communication method provided in Embodiment 4 of this application.

[0046] Figure 30 is an example diagram of a wireless communication method provided in Embodiment 5 of this application.

[0047] Figure 31 is an example diagram of a wireless communication method provided in Embodiment 7 of this application.

[0048] Figure 32 is an example diagram of another wireless communication method provided in Embodiment 7 of this application.

[0049] Figure 33 is an example diagram of another wireless communication method provided in Embodiment 7 of this application.

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

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

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

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

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

[0055] Communication system

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

[0057] Figure 1 illustrates a wireless communication system 100 used in an embodiment of this application. The wireless communication system 100 may include an access point (AP) 110 and a station (STA) 120 that accesses the network through the access point 110.

[0058] In some scenarios, AP is also called AP STA, meaning that in a certain sense, AP is also a type of STA.

[0059] In some scenarios, STA is also called non-AP STA.

[0060] The communication in the communication system 100 can be communication between AP and STA, communication between STA and STA, or communication between STA and peer STA. A peer STA can refer to a device that communicates with the other end of the STA. For example, a peer STA may be an AP or a STA.

[0061] 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 with WiFi chips (such as mobile phones) or network devices (such as routers).

[0062] 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 is connected to a router, it acts as a STA; when a mobile phone serves as a hotspot for other mobile phones, it acts as an AP.

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

[0064] In some embodiments, both the STA and AP can support the 802.11be standard. The STA or AP can also support various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

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

[0066] A multi-link device that includes one or more access points (APs) can be called an access point multi-link device (AP MLD), and a multi-link device that includes one or more non-AP STAs can be called a non-AP multi-link device (Non-AP MLD).

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

[0068] In the embodiments of this application, STA can be a mobile phone, tablet computer, laptop computer, handheld computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc., that supports WLAN / WiFi technology.

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

[0070] Figure 1 illustrates an example of one AP and two STAs. Optionally, the communication system 100 may include multiple APs and other numbers of STAs, which is not limited in this application embodiment.

[0071] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication device may include access point 110 and station 120 with communication functions. Access point 110 and station 120 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, gateways and other network entities. This application embodiment does not limit this.

[0072] APs and STAs can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and satellites. This application does not limit the scenarios in which the APs and STAs are located.

[0073] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0074] Uplink orthogonal frequency division multiple access-based random access (UORA) mechanism

[0075] The AP should indicate the range of the OFDMA contention window (OCW) in the UORA parameter set element so that non-AP STAs 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 Clock Warp) and an internal orthogonal frequency division multiple access (OFDMA) random access backoff (OBO) counter. The OCW is... min To OCW max An integer within the range. (A non-AP HE STA shall maintain an internal OCW and an internal OBO counter. OCW is an integer within the range OCW.) min to OCW max .)

[0077] The size of all random access (RA) resource units (RUs) in the set shall be the same as the size of the RA-RU indicated by the RU Allocation subfield in the User Info field. A non-AP HE STA shall determine the total number of eligible RA-RUs in a contiguous set from the Number Of RA-RU subfields (see Table 9-92 (RA-RU Information subfield format (11ax))) in the User Info field corresponding to an eligible RA-RU, excluding RA-RUs that are not within its operating bandwidth.

[0078] If a high-efficiency STA (HE STA) has a pending frame for the AP upon receiving a trigger frame containing at least one eligible RA-RU, and if the HE STA's OBO counter is not greater than the number of eligible RA-RUs in the trigger frame from that AP, then the HE STA sets its OBO counter to zero and randomly selects one of the eligible RA-RUs to be considered for transmission. Otherwise, the HE STA decrements its OBO counter by the number of eligible RA-RUs in the trigger frame.

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

[0080] Table 1

[0081] For extremely high throughput (EHT) STAs or EHT APs, the maximum number and types of RUs that can be used under each CBW 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 term "tone" in this application can also be called a subcarrier, meaning that "tone" and "subcarrier" can be interchanged.

[0084] Buffer status report (BSR)

[0085] The AP sends a BSR polling (BSRP) trigger frame to obtain buffer status reports from multiple STAs. The STA indicates the amount of data in the buffer queue corresponding to at least one traffic identifier (TID) in at least one frame (e.g., a quality of service (QoS) null frame) contained in a responsive physical layer protocol data unit (PPDU). In the QoS Control field, the STA indicates the amount of data in the buffer queue corresponding to at least one traffic identifier (TID). In the buffer status report control (BSR Control) subfield of the high-efficiency (HE) variant of the high throughput (HT) control field in at least one QoS null frame, the STA indicates the amount of data in the buffer queue corresponding to at least one access category (AC).

[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: 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), packet extension (PE) disambiguation (1 bit), uplink spatial multiplexing (16 bits), HE / EHT primary 160 (HE / EHT primary 160) field. 160, P160 (occupies 1 bit), Special User Information Field Identifier (occupies 1 bit), EHT Reserved (occupies 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] Null data physical protocol data unit feedback report (NFR)

[0089] The access point sends a Null Data Physical Protocol Data Unit Feedback Report Polling (NFRP) trigger frame to obtain null data physical layer transport protocol data unit feedback from multiple sites. Upon receiving the NFRP trigger frame, a site 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 site's feedback status (FEEDBACK_STATUS) (this transmission variable will be used to modulate the subcarrier of the long training field (LTF) of the NDP transmission) is set to 1; otherwise, the site's FEEDBACK_STATUS is set to 0. The resource request cache threshold is indicated by the access point in the empty data physical layer transport protocol data unit feedback parameter set element in the beacon frame and / or probe response frame and / or association response frame and / or reassociation response frame, 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 as shown in Figure 4; the general information field includes 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), GI and HE-LTF type (=2) (2 bits), multiple users multiple-in multiple-out (MU-MIMO) HE-LTF mode (1 bit), HE-LTF symbol number 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 field includes the following fields: association identifier (AID), feedback type, uplink target receive power, and number of spatially multiplexed users.

[0091] The NDP Feedback Report Parameter Set element is shown in Figure 5. The Resource Request Buffer Threshold Exponent field is used to calculate the buffer threshold between two different resource requests as defined in 26.5.7.4 (NDP feedback report for a resource request). The resource request buffer threshold value is equal to 2^(Resource Request Buffer Threshold Exponent) bytes.

[0092] If the AP does not include an NDP Feedback Report Parameter Set element in any of the frames it sends, the resource request buffer threshold is 256 bytes.

[0093] The HE TB feedback NDP format is shown in Figure 6. 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). As shown in Figure 6, there are two 4x HE-LTF symbols, each with a duration of 16 μs (2 HE-LTF symbols with 16 μs per symbol using 4x HE-LTF).

[0094] The NDP format uses a high-efficiency trigger-based PPDU (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. The protection interval (GI) used is 3.2 microseconds. Specifically, the duration of the 1x HE-LTF symbol is 3.2 microseconds, the duration of the 2x HE-LTF symbol is 6.4 microseconds, and the duration of the 4x HE-LTF symbol is 12.8 microseconds. The durations are not included in the protection interval calculation.

[0095] 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. Specifically, the HE-LTF subcarrier mapping relationship in HE TB feedback NDP can be shown in Table 3.

[0096] Table 3

[0097] 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 identifier in the NFRP trigger frame corresponds to the RU_TONE_SET_INDEX value of 1. For example, if the start association identifier 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] The transmission of event-driven (also known as unpredictable or difficult-to-predict) low-latency (LL) traffic can be achieved through the following technical solutions.

[0100] Resources reserved for low-latency transmission

[0101] In this technical solution, resources can be reserved for low-latency transmission using a method similar to preamble puncturing.

[0102] For example, to handle low-latency traffic in a way that avoids collisions or interference and doesn't require waiting for transmission opportunities at another site, the following scheduling method can be used: allocate resources under specific conditions and indicate that resource allocation information. As shown in Figure 7, the AP can indicate whether its sub-channels are punctured or non-punctured within its operating bandwidth. Low-latency traffic can be scheduled for transmission on punctured channels, and non-low-latency (non-LL) traffic can be scheduled for transmission on non-punctured channels. In other words, a specific punctured channel can be used for the transmission of event-driven low-latency traffic, thereby avoiding collisions with ongoing non-low-latency traffic transmission.

[0103] The design incorporates overlapping PPDU indicators for low-latency traffic.

[0104] When a STA has low-latency data that needs to be transmitted, it can send a low-latency indication frame (indicated by LL_IF). The low-latency indication frame can be transmitted overlay with an ongoing uplink transmission.

[0105] As shown in Figure 8, the holder of the TXOP is the AP, and the responder is STA1. A trigger frame (TF) indicates that the LL-IF can be transmitted. When STA1 sends a trigger-based PPDU (TB-PPDU), STA2 sends an LL_IF that overlaps with the TB-PPDU to preempt the TXOP. After receiving the LL_IF, the AP can instruct STA2 to send low-latency data (represented in Figure 8 by LL data).

[0106] This low-latency indication frame can be designed as a simple binary phase shift keying (BPSK) sequence that is mapped onto a portion of the subcarriers being transmitted (e.g., a small RU) and a portion of the OFDM symbols during transmission.

[0107] As shown in Figure 9, for an ongoing PPDU, the frequency domain resources of the Low Latency Indication Frame (LL-IF) can overlap with the PPDU. As shown in the right half of Figure 9, the LL-IF overlaps with the 26-tone RU and reserved tones of the ongoing PPDU. The format of the Low Latency Indication Frame is shown in the left half of Figure 9. The Low Latency Indication Frame shown in Figure 9 satisfies: P4 replicated 6 times; 4 OFDM symbols; 24 active subcarriers; mapped into data; and subcarriers of the 26-tone RU.

[0108] Preemption requests are transmitted using a smaller inter-frame interval.

[0109] The access point divides the longer downlink PPDU into multiple shorter PPDUs and transmits them continuously at x interframe spaces (xIFS) (where x represents an undetermined value; for example, xIFS could be PIFS). The preamble of the first short PPDU indicates whether the transmission within a certain duration (e.g., the duration of this transmission) can be preempted. If preemption is possible, other stations with low-latency traffic waiting to be transmitted (e.g., STA2, STA3) can use an interframe space (Tp) shorter than xIFS to transmit a preemption request (PR) to the access point, thereby interrupting the access point's downlink transmission.

[0110] As shown in Figure 10, the AP is the TXOP holder. The AP can divide a long PPDU into multiple downlink PPDUs (DL PPDUs) as shown in Figure 10, and transmit these multiple downlink PPDUs continuously in xIFS. In the preamble of the downlink PPDU, a preemption flag can be used to indicate whether the downlink transmission can be preempted. For example, when the preemption flag = 1, the STA can use the interframe interval Tp (less than xIFS) to transmit the PR. If an STA transmits the PR, the AP's downlink transmission is interrupted; if no STA transmits the PR, the AP's downlink transmission is not interrupted.

[0111] The following uses Figure 11 as an example to illustrate the transmission process of a preemption request. As shown in Figure 11, both STA2 and STA3 receive LL traffic destined for the AP. Therefore, both STA2 and STA3 transmit PR using Tp. Since the AP receives the PR, its downlink data transmission is suspended. However, because the AP has LL traffic destined for STA2, the AP will transmit a downlink LL PPDU to STA2. After the downlink LL PPDU transmission is complete, the AP can send TF to both STA2 and STA3, allowing STA2 and STA3 to send their respective LL PPDUs.

[0112] There are many problems with the transmission of low-latency traffic in related technologies.

[0113] Taking the technical solution of reserving resources for low-latency traffic transmission as an example, since low-latency traffic is difficult or unpredictable, reserving resources that match low-latency traffic is quite challenging. For instance, reserving too many resources can easily lead to resource waste; reserving too few resources may result in only a few stations being able to complete low-latency data transmission after UORA contention. Furthermore, when a station uses MU PPDU single-user transmission (SU transmission) for uplink, other stations cannot predict the length of the MU PPDU, making it difficult to achieve alignment with the MU PPDU when transmitting low-latency traffic.

[0114] Taking the technical solution involving overlapping PPDUs indicating low-latency data as an example, overlapping PPDUs may interfere with the PPDUs that are being transmitted, thereby affecting the reliability of transmission.

[0115] Taking a technical solution that uses a smaller inter-frame interval to transmit preemption requests as an example, this solution only solves the problem of preempting downlink transmission at the access point, but does not solve the problem of preempting uplink transmission at the site. Furthermore, transmissions from other sites (such as OBSS sites) or other systems may occur within the xIFS duration, causing the access point's downlink transmission to be mistakenly preempted. In addition, the transmission of preemption requests increases system load and total system latency.

[0116] Figure 12 is a schematic flowchart of a wireless communication method provided in an embodiment of this application to solve the above-mentioned problems. The method shown in Figure 12 can be executed by a first STA and an AP. The method shown in Figure 12 may include step S1210.

[0117] In step S1210, within the first TXOP, the first STA sends the first uplink transmission to the AP.

[0118] The first TXOP can be acquired by either the first STA or the AP. That is, the holder of the first TXOP can be either the first STA or the AP. If the holder of the first TXOP is the AP, the first STA can be the responder of the first TXOP.

[0119] The first uplink transmission may include the first STA transmitting one or more of the following: data frames, management frames, and control frames.

[0120] In some embodiments, the first uplink transmission can be 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.

[0121] The first STA may reserve one or more frequency domain units in the first uplink transmission. These one or more frequency domain units can be used by the second STA to report first indication information. The first indication information can indicate that the second STA contains low-latency traffic to be transmitted, and / or that the second STA needs to preempt the first TXOP. The second STA can be any STA belonging to the same network as the first STA. It is understood that the second STA can be any STA different from the first STA. Alternatively, the operation of other STAs different from the first STA within the same network can refer to the operation of the second STA.

[0122] A frequency domain unit may include a RU and / or a subchannel (e.g., a 20MHz subchannel). When the frequency domain unit is an RU, if the first STA reserves multiple RUs, these multiple RUs can be located in multiple subchannels. These multiple subchannels can be consecutive or discontinuous. For example, multiple RUs can constitute a single, complete subchannel (e.g., a 20MHz subchannel).

[0123] When the frequency domain unit 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.

[0124] Low-latency traffic can refer to traffic identified by a restricted target wake time traffic identifier (R-TWT TID) or traffic identified by a stream classification service identifier (SCS ID). Low-latency traffic can be event-driven. For example, low-latency traffic can include one or more of the following: traffic generated by user instant messaging interactions, traffic generated by sensors.

[0125] Non-low latency traffic can refer to traffic that is neither identified by the R-TWT TID nor by the SCS ID.

[0126] It should be noted that "low-latency traffic" is only an exemplary representation. In some embodiments, low-latency traffic may also be referred to as low-latency data, latency-sensitive data, latency-sensitive traffic, etc.

[0127] As mentioned above, the first indication information can be used to indicate that the second STA contains low-latency traffic to be transmitted. In other words, the first indication information can be used to indicate that one or more STAs contain low-latency traffic to be transmitted. Therefore, the first indication information can also be called a low-latency indication (LL indication).

[0128] Optionally, the method shown in Figure 12 may also include step S1220. Step S1220 may be performed by the second STA and AP.

[0129] In step S1220, the second STA reports the first instruction information to the AP.

[0130] For example, if the second STA has low-latency traffic exceeding x, the second STA can indicate to the AP via the first indication information that the second STA contains low-latency traffic to be transmitted, or the second STA needs to preempt the first TXOP to transmit the low-latency traffic. Here, x can be an integer greater than or equal to 0. When x is 0, the second STA can report the first indication information when the first STA receives low-latency traffic.

[0131] After receiving the first indication information, the AP can allocate resources to the second STA to enable the second STA to transmit low-latency traffic. These resources may include one or more of the following: time-domain resources, frequency-domain resources, and spatial-domain resources.

[0132] The first indication information is reported on one or more frequency domain units reserved for the first uplink transmission. That is, when the first STA transmits the first uplink, it can reserve one or more frequency domain units without performing uplink transmission. For the second STA, the first indication information can be reported on the reserved one or more frequency domain units. In other words, the first uplink transmission and the first indication information can occupy the same time domain resources, or the time domain resources occupied by the first uplink transmission and the first indication information may partially or completely overlap, and the frequency domain resources of the first uplink transmission and the first indication information do not overlap. Therefore, there is no interference between the first uplink transmission and the first indication information, thus avoiding the impact of interference on transmission reliability and reducing the total system latency.

[0133] The size of the first indication information is predictable. For example, all STAs can report the same first indication information, or a finite number of STAs can report different first indication information. Therefore, the resources reserved for reporting the first indication information are also predictable or determinable. In other words, compared to reserving resources for unpredictable low-latency traffic, reserving resources for the first indication information does not involve the problem of resource waste due to excessive reservations or the problem of low-latency traffic failing to be transmitted due to insufficient reservations.

[0134] Furthermore, the first indication information is shorter compared to low-latency traffic. Therefore, this application can avoid the misalignment problem with the MU PPDU when the site uplink uses single-user transmission.

[0135] In some embodiments, the first indication information may not distinguish between specific STAs. In other words, the first indication information indicates that one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or that one or more STAs associated with the AP need to preempt the first TXOP. Multiple STAs may report the same first indication information.

[0136] When the first indication does not distinguish between specific STAs, resource reservation can be minimized. For example, the first STA can reserve only a sub-channel with a bandwidth of 20MHz or a resource unit with 26 channels to meet the needs of multiple STAs reporting low latency indications and / or indicating the need to preempt TXOPs.

[0137] It is understandable that, when the first indication information does not distinguish between specific STAs, the AP, after receiving the first indication information, can determine that other STAs besides the first STA contain low-latency traffic to be transmitted, and / or that other STAs need to preempt the first TXOP; however, the AP cannot know from the first indication information which STA(s) contains low-latency traffic to be transmitted, and / or which STA(s) need to preempt the first TXOP.

[0138] In some embodiments, after receiving the first indication information, the AP can further determine low-latency traffic information. Low-latency traffic information may include: which STA(s) or STA(s) have low-latency traffic to be transmitted and / or the amount of low-latency traffic data for each STA. For example, the AP can determine the buffer status of each STA using the BSR and / or NFR technologies described above, thereby determining which STAs have low-latency traffic to be transmitted and / or the amount of low-latency traffic data. Exemplarily, in conjunction with the above-described technical solutions, the low-latency traffic transmission process can be divided into three steps: First, based on the first indication information, the access point determines whether any site has low-latency traffic to be transmitted; second, the access point obtains the specific low-latency traffic information; third, the site transmits the low-latency traffic.

[0139] In some implementations, all stations can use the same first indication information. That is, the first indication information indicates that one or more STAs among all STAs contain low-latency traffic to be transmitted, and / or that one or more STAs among all STAs need to preempt the first TXOP. Here, "all STAs" can refer to all STAs associated with the AP. Alternatively, "all STAs" can refer to all STAs belonging to the same network as the first STA. In this implementation, upon receiving the first indication information, the AP can determine that there are STAs among all STAs that have a low-latency traffic transmission requirement and / or a need to preempt the TXOP.

[0140] For example, if the AP can obtain the specific low-latency traffic and / or the amount of low-latency traffic to be transmitted from all STAs at once, all STAs can use the same first indication information. For instance, with a current operating bandwidth of 80MHz and a total number of STAs not exceeding 36, the AP can allocate at least 26 channel resource units to each STA in the BSRP to obtain the buffered data amount from all STAs. Therefore, with a current operating bandwidth of 80MHz and a total number of STAs not exceeding 36, all STAs can use the same first indication information.

[0141] In some implementations, all STAs can be divided into one or more STA groups, and stations within the same STA group can transmit the same first indication information. For example, one or more STA groups may include a first STA group, which may include a second STA. The first indication information can be used to indicate that one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or that one or more STAs in the first STA group need to preempt the first TXOP. In this implementation, the AP can obtain information that STAs in one or more STA groups among all STAs have low-latency traffic transmission needs and / or TXOP preemption needs. Compared to technical solutions where all stations use the same first indication information, the AP can narrow down the range of STAs with low-latency traffic transmission needs and / or TXOP preemption needs based on grouping, i.e., excluding some or all STAs without low-latency traffic transmission needs and / or TXOP preemption needs.

[0142] For example, if the AP cannot obtain the specific low-latency traffic and / or the amount of low-latency traffic to be transmitted from all STAs at once, the first indication information can be transmitted by STA groups. For instance, if the current operating bandwidth is 80MHz and the total number of STAs exceeds 36, all sites can be grouped, and STAs in the same STA group can use the same first indication information.

[0143] It is understandable that using the same first indication information for all sites is a relatively simple implementation method. By grouping the first indication information, some or all STAs without low-latency traffic transmission needs and / or TXOP preemption needs can be excluded, thereby reducing the number of STAs the AP needs to acquire cached data, thus reducing the transmission overhead and load when the AP acquires cached data.

[0144] When multiple STAs are divided into one or more STA groups, the AP can indicate the grouping situation.

[0145] In some embodiments, packet status can be indicated by a first trigger frame. For example, the AP can send a first trigger frame to a first STA and / or a second STA to inform them of packet status.

[0146] In some embodiments, the access point may announce packet information in advance. For example, the access point may announce packet information in a beacon frame and / or a newly defined action frame.

[0147] Grouping information may include one or more of the following: the number of STAs in the first STA group, the number of groups in one or more STA groups, and the minimum associated identifier of multiple STAs. The number of STAs in the first STA group can also be indicated by the number of STAs belonging to the same STA group. The number of groups in one or more STA groups can be the total number of groups. The total number of groups can be indicated by the grouping modulus.

[0148] The first trigger frame may include a first field. The first field may be used to indicate the number of STAs in a first STA group, and / or the number of groups of one or more STA groups. In some embodiments, the first field may also be included in a beacon frame and / or a newly defined action frame.

[0149] The first trigger frame may include a second field. The second field may be used to indicate the smallest associated identifier of multiple STAs. In some embodiments, the second field may also be included in the beacon frame and / or a newly defined action frame.

[0150] Both the first and second fields can be part of the third field. The third field can be a newly added field in the first trigger frame. For example, the third field can be the special user information field 2.

[0151] Figure 13 is a schematic diagram of a first trigger frame format provided in an embodiment of this application. In Figure 13, this application adds a special user information 2 field marked with gray fill.

[0152] In Figure 13, the first field is the grouping factor field, the second field is the starting association identifier field, and the third field is the special user information field.

[0153] The initial association identifier field indicates the minimum association identifier value among the sites that can participate in this transfer opportunity (i.e., the first TXOP) preemption site.

[0154] The grouping factor field can indicate the number of sites belonging to the same group, or the grouping modulus.

[0155] Taking the grouping factor field, which indicates the number of sites belonging to the same group, as an example, the number of sites in the same group can be the value of the grouping factor plus 1. In this case, one group (e.g., the last group) may contain fewer sites than the number indicated by the grouping factor. For example, with the starting association identifier 3, if the grouping factor is 0, there is only one site in the same group (i.e., STAs with identifiers 3, 4, 5, etc., each form a separate group). As another example, with the starting association identifier 3, if the grouping factor is 1, there are two sites in the same group (i.e., STAs with identifiers 3 and 4 form one group, STAs with identifiers 5 and 6 form another group, and so on), and so on.

[0156] Taking the grouping factor field, which indicates the grouping modulus (or the total number of groups), as an example, sites whose difference between the association identifier and the initial association identifier is congruent to this modulus can be in the same group. In this case, the number of sites in each group may be inconsistent. For example, if the initial association identifier is 3, and the grouping modulus is 7, then sites like 3, 10, 17, etc., might be in one group, while sites like 4, 11, 18, etc., might be in another.

[0157] The UL Target Receive Power field can be used to indicate the expected receive power that the access point will receive when receiving the first indication information.

[0158] The "Number of Spatially Multiplexed Users" field can be used to indicate how many streams the first indication information is sent on. For example, 0 indicates one stream, and 1 indicates two streams. When indicating two streams, a station can determine on which stream to send the first indication information based on the difference between its own association identifier and the initial association identifier. For example, if the initial association identifier is 3, and the station's association identifier is 3, then the first indication information is sent on the first stream; if the station's association identifier is 4, then it is sent on the second stream; if the station's association identifier is 5, then it is sent on the first stream; if the station's association identifier is 6, then it is sent on the second stream, and so on.

[0159] The following describes the method for reporting the first instruction information.

[0160] In some embodiments, the first indication information can be reported via NDP. For example, when one or more reserved frequency domain units are one or more 20MHz sub-channels, the first indication information can be reported via NDP.

[0161] In some embodiments, the first indication information can be reported via a high efficiency trigger-based NDP (HETB feedback NDP).

[0162] When using HE TB feedback NDP to report the first indication information, the HE-LTF field can be mapped to RU_TONE_SET_INDEX so that one RU_TONE_SET_INDEX can correspond to one STA group or one STA. In related technologies, each AID corresponds to one set of subcarriers when the feedback information (FEEDBACK_STATUS) is 0, and to another set of subcarriers when the feedback information (FEEDBACK_STATUS) is 1. In this application, stations without low-latency traffic do not need to transmit this NDP, i.e., they do not need to use the 0 value of the feedback information (FEEDBACK_STATUS). Therefore, the subcarriers corresponding to it can be used to correspond to the 1 value of the feedback information (FEEDBACK_STATUS) of other AIDs.

[0163] For example, if the initial association flag is 6, as mentioned above, in the NFR, the subcarrier groups {–113,–77,–41,6,42,78} and {–112,–76,–40,7,43,79} under the 20MHz bandwidth correspond to the feedback information values ​​of 1 and 0 for the site with AID 6, respectively.

[0164] For example, in this scheme, if a site is a STA group, it can be changed to {–113,–77,–41,6,42,78} and {–112,–76,–40,7,43,79} corresponding to the feedback information value 1 for sites with AID 6 and 7 respectively, and so on.

[0165] For example, in this scheme, if two sites form a STA group, then {–113,–77,–41,6,42,78} and {–112,–76,–40,7,43,79} can be changed to correspond to the feedback information 1 value of the sites in the two groups (for example, AIDs 6, 7, 8, and 9 form one STA group, and AIDs 10, 11, 12, and 13 form another STA group), and so on.

[0166] It should be noted that, when all stations transmit the same first indication information, the NDP reporting the first indication information can include more than just the HE TB feedback NDP. The first indication information can be reported through one or more of the following NDPs: High Efficiency Sounding NDP (HE sounding NDP), Extremely High Throughput Sounding NDP (EHT sounding NDP), and Ultra High Reliability Sounding NDP (UHR sounding NDP). In other words, the LTF field does not need to undergo the aforementioned RU_TONE_SET_INDEX mapping. The LTF field can include one or more of the following: HE-LTF field, EHT-LTF field, and UHR-LTF field.

[0167] Figure 14 is an example diagram of the HE sounding NDP format. As shown in Figure 14, HE sounding NDP can include a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal field (L-SIG), a repeated legacy signal (RL-SIG), a high efficiency-SINGAL field-A (HE-SIG-A), a high efficiency short training field (HE-STF), a high efficiency long training field (HE-LTF), and packet extension (PE).

[0168] Figure 15 is an example diagram of the EHT sounding NDP format. As shown in Figure 15, the EHT sounding NDP can include: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signal field (L-SIG), repeated legacy signal (RL-SIG), universal signal field (U-SIG), extremely high throughput signal field (EHT-SIG), extremely high throughput short training field (EHT-STF), extremely high throughput long training fields (EHT-LTFs), and packet extension (PE).

[0169] Figure 16 is an example diagram of a possible UHR sounding NDP format. As shown in Figure 16, UHR sounding NDP can include: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signal field (L-SIG), repeated legacy signal (RL-SIG), universal signal field (U-SIG), ultra-high reliability signal field (UHR-SIG), ultra-high reliability short training field (UHR-STF), ultra-high reliability long training fields (UHR-LTFs), and packet extension (PE).

[0170] It should be noted that Figures 14 to 16 are merely examples. The corresponding NDP format may include some or all of the fields shown in the figures, or the NDP may include other fields.

[0171] In some embodiments, the first indication information can be transmitted via a second type of PPDU. For example, the first indication information can be carried in the LTF field of the preamble of the second type of PPDU. The second type of PPDU can be a newly defined type of PPDU.

[0172] Figure 17 is a schematic diagram of a second type of PPDU format provided in an embodiment of this application. As shown in Figure 17, the second type of PPDU includes the following fields: non-HT short training field (L-STF), legacy long training field (L-LTF), legacy signal field (L-SIG), repeated legacy signal (RL-SIG), universal signal field (U-SIG), ultra-high reliability short training field (UHR-STF), ultra-high reliability long training field (UHR-LTF), and packet extension (PE).

[0173] In Figure 17, the UHR-LTF field includes two 4x UHR-LTF symbols, each with a duration of 16 microseconds (2 UHR-LTF symbols with 16 μs per symbol using 4x UHR-LTF). The duration of the 4x HE-LTF symbols is 12.8 microseconds (duration not including the protection interval), and the protection interval (GI) used is 3.2 microseconds. The PE field duration is 0 microseconds (μs).

[0174] This application also defines the subcarrier mapping for RU_TONE_SET_INDEX in the UHR-LTF field. The subcarrier mapping for RU_TONE_SET_INDEX can be shown in Table 4.

[0175] Table 4

[0176] It should be noted that Table 4 is for illustrative purposes only. The subcarrier mapping for each RU_TONE_SET_INDEX shown in Table 4 can be implemented independently. In other words, Table 4 can be used in a separate manner.

[0177] It should be noted that the subcarrier mapping of RU_TONE_SET_INDEX can also be one RU_TONE_SET_INDEX for every 5 or every 4 subcarriers, which can increase the number of stations that can participate in the feedback each time.

[0178] It should be noted that the mapping can also be designed differently for 52-tone RUs and / or 106-tone RUs than for 26-tone RUs, thereby evenly distributing each group of 6 subcarriers throughout the entire 52-tone RU and / or 106-tone RU. For example, in a 52-tone RU, the subcarrier group corresponding to a feedback information value of 1 where RU_TONE_SET_INDEX is 1 can be {S+1, S+9, S+17, S+25, S+33, S+41}.

[0179] Additionally, one RU_TONE_SET_INDEX can also correspond to one STA group.

[0180] Specifically, if all sites transmit the same first indication information, the aforementioned RU_TONE_SET_INDEX mapping can be omitted from the UHR-LTF field of the second type of PPDU. For example, it can be pre-specified that the mapping will not be performed, or the access point can pre-indicate or declare that the mapping will not be performed.

[0181] In some embodiments, the one or more frequency domain units reserved by the first STA may be located in the preamble of the PPDU. Exemplarily, the first uplink transmission can be transmitted via a first type of PPDU. The LTF field in the preamble of the first type of PPDU does not perform uplink transmission on the one or more reserved frequency domain units. The first type of PPDU can be a newly defined PPDU. That is, the first STA can send the first uplink transmission via a first type of PPDU, and reserve one or more frequency domain units in the preamble.

[0182] It is understandable that the second type of PPDU can correspond to the first type of PPDU. That is, when the first STA sends the first uplink transmission through the first type of PPDU, the second STA can report the first indication information through the second type of PPDU.

[0183] The above describes an implementation scheme where the first indication information is carried in a preamble. The following describes an implementation scheme where the first indication information is carried in a data field of a third type of PPDU.

[0184] In some embodiments, the first indication information may be carried in one or more LTF symbols in the data field. For example, when one or more frequency domain units are a small RU, the first indication information may be carried in one or more LTF symbols in the data field. The third type of PPDU may be a newly defined PPDU. One or more LTF symbols are transmitted in the data field of the third type of PPDU. In this case, the PPDU carrying the first uplink transmission (e.g., a TB PPDU triggered by a trigger frame) may use an existing format.

[0185] The number of LTF symbols transmitted in the data field of a third type of PPDU can be predefined. For example, in the case of uplink transmission based on a non-trigger frame, the number of LTF symbols can be 1.

[0186] The number of LTF symbols transmitted in the data field of a third type of PPDU can be indicative. For example, in the case of uplink transmission based on a trigger frame, the number of LTF symbols can be indicated by the trigger frame.

[0187] In some implementations, RU_TONE_SET_INDEX mapping can be performed on the LTF symbols of the data fields. The RU_TONE_SET_INDEX mapping of LTF symbols can be shown in Table 4.

[0188] In some implementations, the LTF symbols of the data field may not be mapped using RU_TONE_SET_INDEX. For example, if all stations transmit the same first indication information, the LTF symbols of the data field may not be mapped using RU_TONE_SET_INDEX. Exemplarily, it may be pre-specified that the mapping will not be performed, or the access point may pre-indicate or declare that the mapping will not be performed.

[0189] In some embodiments, the first indication information can be reported via a CTS frame carried in the data field. For example, when one or more reserved frequency domain units are one or more 20MHz subchannels or a smaller RU, the first indication information can be reported via a CTS frame carried in the data field. In this case, the PPDU carrying the first uplink transmission (e.g., a TB PPDU triggered by a trigger frame) can use an existing format.

[0190] It should be noted that, since the CTS frame (14 bytes, or 112 bits, in length) is one of the shortest frames, a specific transmission rate and / or a specific MCS can be specified for transmission when used to carry the first indication information. This ensures that the frame is transmitted within one PPDU symbol, thus resolving the PPDU end-alignment problem that may occur in the reserved time unit scheme. The specific MCS can be, for example, 16-QAM or 64-QAM. This is because an uplink PPDU carrying a data frame or management frame at a station includes at least one PPDU symbol. Even if the uplink PPDU carrying the first uplink transmission at the first STA includes only one PPDU symbol, based on this application, the CTS frame can still be transmitted within one PPDU symbol, thus avoiding the PPDU end-alignment problem caused by the first uplink transmission PPDU being transmitted but the CTS frame not being transmitted.

[0191] It should be noted that a specific transmission rate and / or a specific MCS can be satisfied by: predefinition, pre-announcement, or indication via trigger frame.

[0192] Pre-announcement can be made in advance by the AP. For example, the AP can announce it in a beacon frame and / or a newly defined action frame. Exemplarily, for a specific transmission rate and / or a specific MCS, the AP can announce it in a beacon frame and / or a newly defined action frame.

[0193] When this application is applied to uplink transmission based on trigger frames, the AP can indicate a specific transmission rate and / or a specific MCS through the trigger frame.

[0194] When the first indication information is carried in the data field, the scrambler seed of the data field of different PPDUs sent by different STAs needs to be consistent, so as to ensure that the PPDU symbols sent by each STA are consistent, thereby enabling the normal parsing of the data field.

[0195] A scrambling seed can satisfy one or more of the following: predefined, pre-announced, or indicated via a trigger frame. For example, the AP can announce the scrambling seed in a beacon frame and / or a newly defined action frame. As another example, when this application is applied to trigger frame-based uplink transmissions, the AP can indicate the scrambling seed via the trigger frame.

[0196] It should be noted that the technical solution of reporting the first indication information through the CTS frame carried in the data field may only be applicable to the case where all STAs transmit the same first indication information.

[0197] The following explains how to determine or indicate one or more frequency domain units reserved in the first uplink transmission.

[0198] One or more frequency domain units reserved by the first STA in the first uplink transmission can be indicated by reserved resource information. This reserved resource information needs to be known not only by the first STA for resource reservation, but also by other STAs (e.g., the second STA) to report the first indication information. Therefore, the reserved resource information can satisfy the following conditions: specified by the protocol, configured by the access point, configured by the physical AP MLD to which the access point belongs, or configured by the virtual AP MLD to which the AP belongs. The configuration can include semi-static or dynamic configuration.

[0199] For example, an access point can indicate reserved resource information in a beacon frame. Similarly, an access point can indicate reserved resource information when enabling delay-sensitive transmission priority mode. Furthermore, an access point can indicate reserved resource information in a trigger frame. The following explanation uses the example of indicating reserved resource information in a trigger frame.

[0200] In some embodiments, before the first STA performs the first uplink transmission, the first STA may receive a second trigger frame sent by the AP. The second trigger frame may be related to reserved resource information.

[0201] The second trigger frame may include a fourth field. This fourth field may be used to indicate that the first STA reserves frequency domain units for reporting the first indication information in at least one uplink transmission, the at least one uplink transmission including the first uplink transmission. Alternatively, the fourth field may be used to indicate that the first STA reserves frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP.

[0202] In some embodiments, the first TXOP is the TXOP acquired by the first STA. That is, the fourth field is used to indicate that the first STA reserves frequency domain units for reporting the first indication information in the uplink transmission of the TXOP acquired by the first STA.

[0203] In some embodiments, the first TXOP is the TXOP acquired by the AP. That is, the fourth field is used to indicate that the first STA reserves frequency domain units for reporting the first indication information in the uplink transmission of the TXOP acquired by the AP.

[0204] In some embodiments, the at least one uplink transmission may be indicated by the AP through other fields in the second 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 fourth field.

[0205] In some embodiments, the first TXOP may be indicated by the AP through other fields in the second 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 fourth field.

[0206] In some embodiments, the fourth field may occupy one bit. For example, a bit value of 0 may indicate that the first STA reserves frequency domain units for reporting the first indication information in at least one uplink transmission. Alternatively, a bit value of 0 may indicate that the first STA reserves frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP. Alternatively, a bit value of 1 may indicate that the first STA reserves frequency domain units for reporting the first indication information in at least one uplink transmission. Alternatively, a bit value of 1 may indicate that the first STA reserves frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP.

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

[0208] For example, the second trigger frame can be as shown in Figure 18, where in the general information field, the fourth field (indicated by a bold box) is located after the GI and HE-LTF type / trigger transport opportunity sharing mode fields, and before the HE-LTF symbol number and intermediate code period fields.

[0209] For example, the second trigger frame can be as shown in Figure 19, where in the general information field, the fourth field (indicated by a bold box) is located after the HE-LTF symbol number and intermediate code period fields, and before the LDPC extra symbol segment field.

[0210] For example, the second trigger frame can be as shown in Figure 20, where in the general information field, the fourth field (indicated by a bold box) is located after the uplink space multiplexing field and before the HE / EHT P160 field.

[0211] For example, the second trigger frame can be as shown in Figure 21, where the fourth field (indicated by a bold box) is located after the EHT reserved field in the general information field.

[0212] As shown in Figures 18 to 21, the general information field in the second 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).

[0213] In some embodiments, the second trigger frame further includes a fifth field; wherein the fifth field is used to indicate the frequency domain unit information reserved by the first STA for reporting the first indication information.

[0214] For example, the AP can use four reserved bits from the second trigger frame (such as the four reserved bits in the special user information field) as the fifth field to indicate the number of reserved frequency domain units (such as sub-channels). 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, sub-channels corresponding to the main channel cannot be used as reserved sub-channels.

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

[0216] For example, the second trigger frame can be as shown in Figure 22, where, in the general information field, the fourth field (indicated by a bold box) is located after the GI and HE-LTF type / trigger transmission opportunity sharing mode fields, and the fourth 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 fifth field (occupying 4 bits) (indicated by a light gray box) can be located in the user information field related to the trigger frame subclass.

[0217] For example, the second trigger frame can be as shown in Figure 23, where, in the general information field, the fourth field (indicated by a bold box) is located after the GI and HE-LTF type / triggering opportunity sharing mode fields, and the fourth 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 fifth field (occupying 8 bits) (indicated by a light gray box) can be located in the user information field related to the trigger frame subclass.

[0218] As shown in Figures 22 and 23, the special user information fields in the second 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.

[0219] As shown in Figures 18 to 23, the user information fields in the second 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.

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

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

[0222] It should be noted that the first trigger frame and the second trigger frame can be the same or different trigger frames.

[0223] In some embodiments, if the second STA reports first indication information on one or more reserved frequency domain units, the AP can send preemption indication information to the first STA. This preemption indication information indicates that the AP will preempt the first TXOP.

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

[0225] In some embodiments, when the preemption indication information is carried in 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 indicating that the AP will preempt the first TXOP.

[0226] For example, as shown in Figure 24, 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 field of the first TXOP.

[0227] 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) can determine that the first STA has reserved one or more frequency domain units in the first uplink transmission for reporting the first indication information.

[0228] 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, they can determine that the first STA has reserved frequency domain units for reporting the first indication information in at least one uplink transmission, and the at least one uplink transmission includes the first uplink transmission.

[0229] 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, they can determine that the first STA has reserved frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP.

[0230] In some embodiments, if the first STA enables 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 and / or management frames sent by the AP.

[0231] For example, the first STA can perform a mode switch in advance (i.e., enable delay-sensitive transmission priority mode), and 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 reserved one or more 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 the first indication information in at least one uplink transmission, or it reserves frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP.

[0232] For example, if the first STA performs a mode switch in advance (i.e., enables delay-sensitive 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 reserved one or more 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 the first indication information in at least one uplink transmission, or it reserves frequency domain units for reporting the first indication information in the uplink transmission of the first TXOP.

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

[0234] 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 one or more frequency domain units are configured by the AP in the request information.

[0235] For example, the AP can send a management frame to at least one STA requesting the activation of delay-sensitive transmission priority mode. Optionally, the management frame can further indicate the following information: the duration of the delay-sensitive transmission priority mode activation, and / or, the specific frequency domain units reserved (i.e., one or more frequency domain units). When the delay-sensitive transmission priority mode is activated, the STA can reserve frequency domain units (sub-channels or RUs) for other STAs to report first indication information 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 requesting the deactivation of delay-sensitive transmission priority mode.

[0236] 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 one or more frequency domain units are configured by the first STA in the notification information, and / or, the one or more frequency domain units are configured by the AP in the notification response.

[0237] For example, a STA can send a management frame to the AP to notify it to enable 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., one or more frequency domain units reserved for other STAs to report first indication information); the AP responds with a management frame, which can further confirm or indicate modification of the reserved specific frequency domain units (i.e., one or more frequency domain units). When delay-sensitive transmission priority mode is enabled, a STA can reserve frequency domain units (sub-channels or RUs) for other STAs to report first indication information to the AP during uplink transmission in its own acquired TXOP, and 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.

[0238] In some embodiments, when the AP has enabled the delay-sensitive transmission priority mode, other STAs (such as a second STA) learn 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, operation mode notification frame, and newly defined management frame.

[0239] 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 one or more reserved frequency domain units.

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

[0241] For example, an AP can enable a delay-sensitive transmission priority mode. When this mode is enabled, the AP can request STAs to reserve frequency domain units during uplink transmissions in its acquired TXOPs for other STAs to report first indication information to the AP. For instance, the AP can send a management frame (e.g., a beacon frame and / or probe response frame and / or association response frame and / or reassociation response frame and / or operation mode notification frame) to inform STAs of the enabled delay-sensitive transmission priority mode. Optionally, this management frame can further indicate the following information: the duration of the delayed-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 operation mode notification frame) to inform the STA that delay-sensitive transmission priority mode is turned off.

[0242] In some embodiments, the number of frequency domain units reserved by the first STA can be m1, where m1 can be a positive integer. The first STA or the second STA reserves m2 frequency domain units in the second uplink transmission. These m2 frequency domain units are used by one or more other STAs containing uplink delay-sensitive data to be transmitted to report first indication information, where m2 is a positive integer. For example, the second uplink transmission can be used to transmit low-latency data from the second STA.

[0243] For example, the third STA reports the first indication information on m2 frequency domain units. Here, the m2 frequency domain units are reserved by the first STA or the second STA in the second uplink transmission, and m2 is a positive integer.

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

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

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

[0247] As shown in Figure 25, station 1 can reserve m1 sub-channels. Stations 2 and 3 report low-latency indications on m1 sub-channels. The AP obtains the buffer information of stations 2 and 3 through a BSRP trigger frame. Based on the obtained buffer information, the AP sends a trigger frame carrying an RU indication. Based on this RU indication, station 2 can reserve m2 RUs for other stations to send low-latency indications. Station 3 can reserve m2 RUs for other stations to send low-latency indications.

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

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

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

[0251] Example 1

[0252] As shown in Figure 26, the first station acquires a transmission opportunity and reserves at least one sub-channel during at least one uplink transmission with the access point. If at least one other station generates uplink low-latency data to be transmitted before this uplink transmission, the other station can use the reserved sub-channel to send a low-latency indication during this uplink transmission to indicate to the access point that the other station has low-latency traffic to be transmitted and / or needs to preempt the transmission opportunity. After receiving the low-latency indication, the access point indicates in its response or acknowledgment to the first station that it will preempt the transmission opportunity. After receiving the preemption indication, the first station will stop actively transmitting uplink data. After preempting the transmission opportunity, the access point will use existing BSRP trigger frames to obtain buffer status reports from multiple stations or use existing NFRP to obtain empty data physical layer transport protocol data unit feedback from multiple stations, and then use existing trigger frame-based uplink transmission procedures to trigger each station (including the other stations and / or the first station) to perform uplink transmission.

[0253] In the uplink transmission between the first station and the access point, the data frame and / or management frame may be used. The low latency indication may employ the existing Physical Layer Transport Protocol Data Unit Feedback (HETB Feedback NDP), and / or a CTS frame, and / or a PPDU as defined in this application. The response or acknowledgment from the access point to the first station may be a management frame and / or an acknowledgment frame and / or a block acknowledgment frame. The BSRP trigger frame and basic trigger frame sent by the access point to each station may use existing trigger frames, i.e., the uplink transmission triggered by such a trigger frame does not reserve sub-channels or resource units; or it may use the trigger frame as defined in this application, which carries a reserved sub-channel or resource unit indication, i.e., the uplink transmission triggered by such a trigger frame also reserves sub-channels or resource units.

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

[0255] Method 1: The first station performs a mode switch in advance (i.e., enables low-latency transmission priority mode), and the access point broadcasts in the beacon frame that the first station 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 aforementioned sub-channel in its acquired transmission opportunities.

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

[0257] Method 3: The first station indicates in the RTS frame sent to the access point that, for example, the 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, or 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 it can be indicated by the access point in the previous beacon frame.

[0258] In the transmission opportunity of the first site, the legacy STA does not support the low latency indication function and will not transmit the low latency indication.

[0259] If the existing HE TB feedback NDP is used, in the transmission opportunity of the first site, the access point does not send NFRP but receives the feedback of the empty data physical layer transport protocol data unit, so it can be distinguished that it is a low latency indication rather than the buffered data volume report in the existing technology.

[0260] Example 2

[0261] As shown in Figure 27, the access point obtains a transmission opportunity and performs at least one downlink transmission with the first station. The first station reserves at least one sub-channel when responding to or acknowledging the access point uplink. 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 the low-latency indication during the uplink response or acknowledgment. After receiving the low-latency indication, the access point will use existing BSRP trigger frames to obtain buffer status reports from multiple stations or use existing NFRP to obtain empty data physical layer transport protocol data unit feedback from multiple stations. Then, it will use existing trigger frame-based uplink transmission procedures to trigger uplink transmission from each station (including the other stations and / or the first station).

[0262] The downlink transmission between the access point and the first station can consist of data frames and / or management frames. The low-latency indication can employ existing HE TB feedback NDP, and / or CTS frames, and / or the newly defined PPDU of this application. The uplink response or acknowledgment from the first station can consist of management frames and / or acknowledgment frames and / or block acknowledgment frames. The BSRP trigger frames and basic trigger frames sent by the access point to each station can use existing trigger frames, i.e., the uplink transmission triggered by these trigger frames does not reserve sub-channels or resource units; or they can use the newly defined trigger frames of this application, which carry a reserved sub-channel or resource unit indication, i.e., the uplink transmission triggered by these trigger frames also reserves sub-channels or resource units.

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

[0264] Example 3

[0265] As shown in Figure 28, the access point obtains a transmission opportunity and triggers the first station to perform at least one uplink transmission. The first station 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 this uplink transmission, the other station can use the reserved sub-channel to send the low-latency indication during this uplink transmission. After the access point provides the low-latency indication, it will use existing BSRP trigger frames to obtain buffer status reports from multiple stations or use existing NFRP to obtain empty data physical layer transport protocol data unit feedback from multiple stations. Then, it will use existing trigger frame-based uplink transmission procedures to trigger each station (including the other stations and / or the first station) to perform uplink transmission.

[0266] When the access point triggers the first site to initiate uplink transmission, it can use an existing trigger frame (i.e., a reserved sub-channel that is predefined or negotiated in advance in the uplink transmission of the first site), or it can use a trigger frame newly defined in this application to carry a reserved sub-channel indication. The low-latency indication can adopt the existing null data physical layer transport protocol data unit feedback (HETB feedback NDP), and / or a CTS frame, and / or a PPDU newly defined in this application. The uplink transmission of the first site can be a data frame and / or a management frame and / or an acknowledgment frame and / or a block acknowledgment frame. The trigger frame sent by the access point to each site can use an existing trigger frame, i.e., the uplink transmission triggered by this trigger frame does not reserve sub-channels or resource units; or it can use a trigger frame newly defined in this application, which carries a reserved sub-channel or resource unit indication, i.e., the uplink transmission triggered by this trigger frame also reserves sub-channels or resource units.

[0267] In Embodiment 3, the method for other stations to determine whether the first station 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.

[0268] Example 4

[0269] As shown in Figure 29, similar to Embodiment 3, after the access point obtains a transmission opportunity, the access point triggers multiple first stations (the first stations also include second stations) to perform at least one uplink transmission.

[0270] 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 MU-RTS trigger frame.

[0271] Example 5

[0272] As shown in Figure 30, similar to Embodiment 4, after the access point obtains a transmission opportunity, the access point performs at least one downlink transmission to at least one first station while triggering at least one uplink transmission to at least one second station. The first station of the access point may be the same as or different from the second station.

[0273] In this scenario, the method by which the other stations determine whether the first station has reserved a sub-channel or not is the same as in Embodiment 4.

[0274] Example 6

[0275] In the scenario described in Example 1, the first station may use any PPDU format it supports, other than 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.

[0276] In the scenario described in Example 2, when the first station responds or acknowledges to the access point uplink, it may use any PPDU format it supports, other than 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.

[0277] Example 7

[0278] In the scenarios described in at least one of Embodiments 3, 4, and 5, the first site may reserve at least one RU in its operating bandwidth. Figure 31 shows an example of the first site reserving at least one RU in the scenario described in Embodiment 3. Figure 32 shows an example of the first site reserving at least one RU in the scenario described in Embodiment 4. Figure 33 shows an example of the first site reserving at least one RU in the scenario described in Embodiment 5.

[0279] All stations can predict the preamble of the TB PPDU to be transmitted uplink by receiving the trigger frame sent by the access point, so that the transmission of PPDUs using the same preamble by other stations on at least one RU will not cause interference.

[0280] The existing HE TB feedback NDP format can only be transmitted over one or more complete 20MHz subchannels. The HE TB feedback NDP format can only be used when the reserved RU occupies one or more complete 20MHz subchannels.

[0281] When the reserved RU occupies only a portion of a 20MHz subchannel, the low-latency indication can only use a CTS frame and / or the second type of PPDU newly defined in this application. If the low-latency indication specifically uses a CTS frame (the data field carried in the PPDU), the TB PPDU triggered by the trigger frame can use the existing format. If the low-latency indication specifically uses the LTF field in the preamble of the newly defined PPDU, the LTF field of the TB PPDU triggered by the trigger frame also needs to be modified (i.e., not transmitted on the reserved RU).

[0282] It should be noted that, in the embodiments of this application, "field" can also be referred to as "domain" or "subfield". A field can occupy one or more bytes (byte / octet), or a field can occupy one or more bits (bit).

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

[0284] Figure 34 is a schematic structural diagram of a communication device 3400 provided in an embodiment of this application. The communication device 3400 is a first STA. The communication device 3400 includes a transmitting unit 3410.

[0285] The transmitting unit is used to send a first uplink transmission to the access point (AP) within the first TXOP; wherein the first STA reserves one or more frequency domain units in the first uplink transmission, and the one or more frequency domain units are used by the second STA to report first indication information, the first indication information being used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0286] In some embodiments, the first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

[0287] In some embodiments, the multiple STAs associated with the AP are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

[0288] In some embodiments, the device 3400 is further configured to: receive a first trigger frame; wherein the first trigger frame includes a first field, the first field being configured to indicate one or more of the following: the number of STAs in the first STA group, the number of groups of the one or more STA groups.

[0289] In some embodiments, the first trigger frame further includes a second field, which indicates the smallest association identifier among the plurality of STAs associated with the AP.

[0290] In some embodiments, the first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink over the reserved one or more frequency domain units.

[0291] In some embodiments, the first indication information is reported via one or more of the following NDPs: HE TB feedback NDP, HE sounding NDP, EHT sounding NDP, and UHR sounding NDP.

[0292] In some embodiments, the first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

[0293] In some embodiments, the first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

[0294] In some embodiments, the first indication information is carried in one or more LTF symbols in the data field.

[0295] In some embodiments, the first indication information is reported via a CTS frame carried in the data field.

[0296] In some embodiments, the scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

[0297] In an optional embodiment, the transmitting unit 3410 may be a transceiver 3730. The communication device 3400 may also include a processor 3710 and a memory 3720, as shown in FIG37.

[0298] Figure 35 is a schematic structural diagram of a communication device 3500 provided in an embodiment of this application. The communication device 3500 is a second STA, and the communication device 3500 includes: a reporting unit 3510.

[0299] The reporting unit 3510 is used to report first indication information to the AP in one or more frequency domain units within the first TXOP; wherein the one or more frequency domain units are frequency domain resources reserved by the first STA in the first uplink transmission, and the first indication information is used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0300] In some embodiments, the first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

[0301] In some embodiments, the multiple STAs associated with the AP are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

[0302] In some embodiments, the communication device 3500 is further configured to: receive a first trigger frame; wherein the first trigger frame includes a first field, the first field being configured to indicate one or more of the following: the number of STAs in the first STA group, the number of groups of the one or more STA groups.

[0303] In some embodiments, the first trigger frame further includes a second field, which indicates the smallest association identifier among the plurality of STAs associated with the AP.

[0304] In some embodiments, the first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink over the reserved one or more frequency domain units.

[0305] In some embodiments, the first indication information is reported via one or more of the following NDPs: HE TB feedback NDP, HE sounding NDP, EHT sounding NDP, and UHR sounding NDP.

[0306] In some embodiments, the first indication information is reported via a second type of PPDU; the first indication information is carried in the LTF field of the preamble of the second type of PPDU.

[0307] In some embodiments, the first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

[0308] In some embodiments, the first indication information is carried in one or more LTF symbols in the data field.

[0309] In some embodiments, the first indication information is reported via a CTS frame carried in the data field.

[0310] In some embodiments, the scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

[0311] In an optional embodiment, the reporting unit 3510 may be a transceiver 3730. The communication device 3500 may also include a processor 3710 and a memory 3720, as shown in FIG37.

[0312] Figure 36 is a schematic structural diagram of a communication device 3600 provided in an embodiment of this application. The communication device 3600 is an access point (AP). The communication device 3600 includes a receiving unit 3610.

[0313] The receiving unit 3610 is used to receive a first uplink transmission from a first STA within a first TXOP; wherein the first STA reserves one or more frequency domain units in the first uplink transmission, and the one or more frequency domain units are used by a second STA to report first indication information, the first indication information being used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

[0314] In some embodiments, the first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

[0315] In some embodiments, the multiple STAs associated with the AP are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

[0316] In some embodiments, the communication device 3600 is further configured to: send a first trigger frame; wherein the first trigger frame includes a first field, the first field being configured to indicate one or more of the following: the number of STAs in the first STA group, the number of groups of the one or more STA groups.

[0317] In some embodiments, the first trigger frame further includes a second field, which indicates the smallest association identifier among the plurality of STAs associated with the AP.

[0318] In some embodiments, the first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink over the reserved one or more frequency domain units.

[0319] In some embodiments, the first indication information is reported via one or more of the following NDPs: HE TB feedback NDP, HE sounding NDP, EHT sounding NDP, and UHR sounding NDP.

[0320] In some embodiments, the first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

[0321] In some embodiments, the first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

[0322] In some embodiments, the first indication information is carried in one or more LTF symbols in the data field.

[0323] In some embodiments, the first indication information is reported via a CTS frame carried in the data field.

[0324] In some embodiments, the scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

[0325] In an optional embodiment, the receiving unit 3610 may be a transceiver 3430. The communication device 3600 may also include a processor 3710 and a memory 3720, as shown in FIG37.

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

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

[0328] The apparatus 3700 may also include one or more memories 3720. The memories 3720 store a program that can be executed by the processor 3710, causing the processor 3710 to perform the methods described in the preceding method embodiments. The memories 3720 may be independent of the processor 3710 or integrated into the processor 3710.

[0329] The device 3700 may also include a transceiver 3730. The processor 3710 can communicate with other devices or chips via the transceiver 3730. For example, the processor 3710 can send and receive data with other devices or chips via the transceiver 3730.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0346] 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: During the first transmission opportunity (TXOP), the first station (STA) sends the first uplink transmission to the access point (AP); In this process, the first STA reserves one or more frequency domain units in the first uplink transmission. The one or more frequency domain units are used by the second STA to report first indication information. The first indication information indicates that the second STA contains low-latency traffic to be transmitted, and / or that the second STA needs to preempt the first TXOP.

2. The method according to claim 1, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

3. The method according to claim 1, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

4. The method according to claim 3, characterized in that, Also includes: The first STA receives the first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

5. The method according to claim 4, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

6. The method according to any one of claims 1-5, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

7. The method according to any one of claims 1-6, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

8. The method according to any one of claims 1-6, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

9. The method according to any one of claims 1-6, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

10. The method according to claim 9, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

11. The method according to claim 9, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

12. The method according to any one of claims 9-11, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

13. A method for wireless communication, characterized in that, include: During the first transmission opportunity (TXOP), the second station (STA) reports the first indication information to the access point (AP) on one or more frequency domain units; Wherein, the one or more frequency domain units are frequency domain resources reserved by the first STA in the first uplink transmission, and the first indication information is used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

14. The method according to claim 13, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

15. The method according to claim 13, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

16. The method according to claim 15, characterized in that, Also includes: The second STA receives the first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

17. The method according to claim 16, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

18. The method according to any one of claims 13-17, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

19. The method according to any one of claims 13-18, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

20. The method according to any one of claims 13-18, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

21. The method according to any one of claims 13-18, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

22. The method according to claim 21, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

23. The method according to claim 21, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

24. The method according to any one of claims 21-23, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

25. A method for wireless communication, characterized in that, include: During the first transmission opportunity (TXOP), the access point (AP) receives the first uplink transmission from the first site (STA). In this process, the first STA reserves one or more frequency domain units in the first uplink transmission. The one or more frequency domain units are used by the second STA to report first indication information. The first indication information indicates that the second STA contains low-latency traffic to be transmitted, and / or that the second STA needs to preempt the first TXOP.

26. The method according to claim 25, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

27. The method according to claim 25, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

28. The method according to claim 27, characterized in that, Also includes: The AP sends a first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

29. The method according to claim 28, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

30. The method according to any one of claims 25-29, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

31. The method according to any one of claims 25-30, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

32. The method according to any one of claims 25-30, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

33. The method according to any one of claims 25-30, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

34. The method according to claim 33, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

35. The method according to claim 33, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

36. The method according to any one of claims 33-35, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

37. A communication device, characterized in that, The device is a first site STA, and the communication device includes: The transmitting unit is used to send the first uplink transmission to the access point (AP) within the first transmission opportunity (TXOP). In this process, the first STA reserves one or more frequency domain units in the first uplink transmission. The one or more frequency domain units are used by the second STA to report first indication information. The first indication information indicates that the second STA contains low-latency traffic to be transmitted, and / or that the second STA needs to preempt the first TXOP.

38. The device according to claim 37, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

39. The device according to claim 37, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

40. The device according to claim 39, characterized in that, The device is also used for: Receive the first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

41. The device according to claim 40, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

42. The device according to any one of claims 37-41, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

43. The device according to any one of claims 37-42, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

44. The device according to any one of claims 37-42, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

45. The device according to any one of claims 37-42, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

46. ​​The device according to claim 45, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

47. The device according to claim 45, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

48. The device according to any one of claims 45-47, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

49. A communication device, characterized in that, The device is a second site STA, and the device includes: The reporting unit is used to report first indication information to the access point (AP) on one or more frequency domain units within the first transmission opportunity (TXOP). Wherein, the one or more frequency domain units are frequency domain resources reserved by the first STA in the first uplink transmission, and the first indication information is used to indicate that: the second STA contains low-latency traffic to be transmitted, and / or, the second STA needs to preempt the first TXOP.

50. The device according to claim 49, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

51. The device according to claim 49, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

52. The device according to claim 51, characterized in that, The device is also used for: Receive the first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

53. The device according to claim 52, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

54. The device according to any one of claims 49-53, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

55. The device according to any one of claims 49-54, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

56. The device according to any one of claims 49-54, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

57. The device according to any one of claims 49-54, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

58. The device according to claim 57, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

59. The device according to claim 57, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

60. The device according to any one of claims 57-59, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

61. A communication device, characterized in that, The device is an access point (AP), and the communication device includes: The receiving unit is configured to receive the first uplink transmission from the first station STA within the first transmission opportunity TXOP. In this process, the first STA reserves one or more frequency domain units in the first uplink transmission. The one or more frequency domain units are used by the second STA to report first indication information. The first indication information indicates that the second STA contains low-latency traffic to be transmitted, and / or that the second STA needs to preempt the first TXOP.

62. The device according to claim 61, characterized in that, The first indication information is used to indicate that: one or more STAs associated with the AP contain low-latency traffic to be transmitted, and / or, one or more STAs associated with the AP need to preempt the first TXOP.

63. The device according to claim 61, characterized in that, The AP is associated with multiple STAs that are divided into one or more STA groups, the one or more STA groups including a first STA group, the first STA group including a second STA, and the first indication information is used to indicate that: one or more STAs in the first STA group contain low-latency traffic to be transmitted, and / or, one or more STAs in the first STA group need to preempt the first TXOP.

64. The device according to claim 63, characterized in that, The device is also used for: Send the first trigger frame; The first trigger frame includes a first field, which indicates one or more of the following: the number of STAs in the first STA group, and the number of groups of the one or more STA groups.

65. The device according to claim 64, characterized in that, The first trigger frame also includes a second field, which is used to indicate the smallest association identifier among the multiple STAs associated with the AP.

66. The device according to any one of claims 61-65, characterized in that, The first uplink transmission is transmitted via a first type of physical layer protocol data unit (PPDU); the LTF field in the preamble of the first type of PPDU is not transmitted uplink on the reserved one or more frequency domain units.

67. The device according to any one of claims 61-66, characterized in that, The first indication information is reported through one or more of the following NAV physical layer transport protocol data units: High Efficiency Trigger-Based Feedback NAV Physical Layer Protocol Data Unit (HE TB feedback NDP), High Efficiency Sounding NAV Physical Layer Protocol Data Unit (HE sounding NDP), Extremely High Throughput Sounding NAV Physical Layer Protocol Data Unit (EHT sounding NDP), and Extremely High Reliability Sounding NAV Physical Layer Protocol Data Unit (UHR sounding NDP).

68. The device according to any one of claims 61-66, characterized in that, The first indication information is reported via a second type of PPDU; the first indication information is carried in the long training field (LTF) field of the preamble of the second type of PPDU.

69. The device according to any one of claims 61-66, characterized in that, The first indication information is reported via a third type of PPDU; the first indication information is carried in the data field of the third type of PPDU.

70. The device according to claim 69, characterized in that, The first indication information is carried in one or more LTF symbols in the data field.

71. The device according to claim 69, characterized in that, The first indication information is reported via a CTS frame carried in the data field.

72. The device according to any one of claims 69-71, characterized in that, The scrambling seed of the data field satisfies one or more of the following: predefined, pre-announced, or indicated by a trigger frame.

73. A communication device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to cause the communication device to perform the method as described in any one of claims 1-36.

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

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

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

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

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

Images