Apparatus and method for low latency communication

The apparatus and method address LL data transmission delays by using a receiver, transmitter, and circuitry to preempt ongoing transmissions, ensuring timely and efficient data transfer in wireless communication systems.

WO2026235625A1PCT designated stage Publication Date: 2026-11-12PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SG2026/050235
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-10
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently and reliably transmitting low latency (LL) data due to delays caused by stations (STAs) failing to timely indicate data arrival to access points (APs), leading to potential transmission delays.

Method used

A communication apparatus and method that includes a receiver to detect LL data, a transmitter to send a Trigger frame for data transmission, and circuitry to preempt ongoing transmissions, utilizing BlockAck frames and data urgency levels to facilitate efficient LL data transfer.

Benefits of technology

Enables reliable and efficient low latency communication by ensuring timely data transmission, improving network performance and user experience through preemptive data handling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SG2026050235_12112026_PF_FP_ABST
    Figure SG2026050235_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A first communication apparatus (100) for low latency (LL) communication with a second communication apparatus (100) is disclosed. The first communication apparatus comprises: a receiver (104), which in operation, receives an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and receives the LL data from the second communication apparatus; a transmitter (102), which in operation, transmits, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; and circuitry (114), which in operation, processes the received LL data.
Need to check novelty before this filing date? Find Prior Art

Description

APPARATUS AND METHOD FOR LOW LATENCY COMMUNICATONTECHNICAL FIELD

[0001] The following relates generally to wireless communications, and more specifically, it relates to apparatuses and methods for low latency communication.BACKGROUND

[0002] Low latency (LL) communication is an important functionality in IEEE 802.11 standards. There have been discussions in the art about reducing delay of LL data by indicating LL data arrival in time, and thereby enabling transmission of LL data [ref. 1-8], However, when one or more stations (STAs) have LL data to be transmitted to an access point (AP), this may lead to potential problems, such as delay of transmission of the LL data, if a STA is unable to timely indicate to the AP about arrival of the LL data. For completeness, it is hereby clarified that the terminologies of STA, AP and the like, as set out in the description below, follow those defined under IEEE 802.11, as known in the art.

[0003] So, there is a need for a solution that may address at least one of the problems of the prior art, and / or to provide a choice useful in the art. For example, it is desired for a method that may enable multiple STAs to reliably and efficiently perform transmission of LL data.SUMMARY

[0004] The described techniques herein may relate to low latency communication between a first communication apparatus (e.g. an AP) and a second communication apparatus (e.g. a STA).

[0005] According to a 1staspect, there is disclosed a first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: a receiver, which in operation, receives an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and receives the LL data from the second communication apparatus; a transmitter, which in operation, transmits, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; and circuitry, which in operation, processes the received LL data.

[0006] Additionally or alternatively, a transmission may be ongoing at the first communication apparatus, and the circuitry, which in operation, may preempt, based on the received indication, the ongoing transmission, prior to receiving the LL data.

[0007] Additionally or alternatively, the indication may be received via a BlockAck (BA) frame.

[0008] Additionally or alternatively, the indication may be configured with a value of 0 or 1, in which the value of 0 indicates unavailability of LL data to be transmitted, and the value of 1 indicates availability of LL data to be transmitted.

[0009] Additionally or alternatively, the indication may be received, in response to a multiuser (MU) physical layer protocol data unit (PPDU) transmitted by the first communication apparatus.

[0010] Additionally or alternatively, the transmitter, which in operation, may further transmit, to the second communication apparatus, a second Trigger frame to request information about the LL data, prior to transmitting the first Trigger frame, wherein the second Trigger frame is a buffer status report poll (BSRP) Trigger frame.

[0011] Additionally or alternatively, the first Trigger frame may be transmitted, based in part on a data urgency level of the LL data communicated by the second communication apparatus,

[0012] Additionally or alternatively, the data urgency level may be communicated via an access category index (ACI) bitmap.

[0013] Additionally or alternatively, the circuitry, which in operation, may determine, based on the data urgency level, a size of a resource unit (RU) to be allocated to the second communication apparatus to enable transmission of the LL data.

[0014] Additionally or alternatively, the transmitter, which in operation, may further transmit, to the second communication apparatus, a polling frame to request information on a preemption intent of the second communication apparatus, which indicates whether the second communication apparatus has intent for the first communication apparatus to enable preemption, wherein the polling frame is transmitted prior to receiving, from the second communication apparatus, the indication about the LL data to be transmitted to the firstcommunication apparatus; and the receiver, which in operation, may receive, from the second communication apparatus, a response to the polling frame indicating the preemption intent.

[0015] Additionally or alternatively, the polling frame may be one of: a buffer status report poll (BSRP) Trigger frame, and a Null data packet (NDP) feedback report poll (NFRP) Trigger frame.

[0016] Additionally or alternatively, the preemption intent may be indicated via a Multi-STA BlockAck (M-BA) frame, or a stream classification service (SCS) Request frame.

[0017] Additionally or alternatively, the polling frame may be an add block acknowledgment (ADDBA) Request frame, and the preemption intent is indicated via an ADDBA Response frame.

[0018] Additionally or alternatively, the receiver, which in operation, may receive, from the second communication apparatus, an add block acknowledgment (ADDBA) Request frame configured to indicate a preemption intent.

[0019] Additionally or alternatively, the first communication apparatus may be an access point (AP), and the second communication apparatus may be a station (STA) configured to communicate with the AP.

[0020] According to a 2ndaspect, there is disclosed a method at a first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: receiving an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus; transmitting, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; receiving, from the second communication apparatus, the LL data; and processing the received LL data.

[0021] According to a 3rdaspect, there is disclosed a second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: circuitry, which in operation, buffers LL data; a transmitter, which in operation, transmits, an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted, and transmits, to the first communication apparatus, the LL data; and a receiver, which in operation, receives, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data.

[0022] According to a 4thaspect, there is disclosed a method at a second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: buffering LL data; transmitting an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; receiving, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data; and transmitting, to the first communication apparatus, the LL data.

[0023] Additionally or alternatively, the method may further comprise: transmitting, to the first communication apparatus, a buffer status report (BSR) configured to include information about the LL data.

[0024] Additionally or alternatively, the first communication apparatus may be an access point (AP), and the second communication apparatus may be a station (STA) configured to communicate with the AP.

[0025] Additional benefits and advantages of the disclosed aspects may become apparent from the specification and drawings. The benefits and / or advantages may be individually obtained by the various aspects and features of the specification and drawings, which need not all be provided in order to obtain one or more of such benefits and / or advantages.BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views and which together with the detailed description below are incorporated in and form part of the specification, serve to illustrate various aspects and to explain various principles and advantages in accordance with the present disclosure.

[0027] FIG. 1 is a block diagram of a communication apparatus for low latency (LL) communication, in accordance with aspects of the present disclosure.

[0028] FIG. 2 is a flowchart illustrating a method at a first communication apparatus for LL communication, in accordance with aspects of the present disclosure.

[0029] FIG. 3 is a flowchart illustrating a method at a second communication apparatus for LL communication, in accordance with aspects of the present disclosure.

[0030] FIG. 4 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0031] FIG. 5 depicts a frame format of a triggered response scheduling (TRS) Control field in a QoS Null frame, in accordance with aspects of the present disclosure.

[0032] FIG. 6 depicts a frame format of a control frame, in accordance with aspects of the present disclosure.

[0033] FIG. 7 depicts an example of a first frame format of a BlockAck (BA) frame, in accordance with aspects of the present disclosure.

[0034] FIG. 8 depicts an example of a second frame format of a BlockAck (BA) frame, in accordance with aspects of the present disclosure.

[0035] FIG. 9 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0036] FIG. 10 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0037] FIG. 11 depicts a frame format of a trigger-based (TB) physical layer protocol data unit (PPDU) frame, in accordance with aspects of the present disclosure.

[0038] FIG. 12 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0039] FIG. 13 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0040] FIG. 14 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0041] FIG. 15 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0042] FIG. 16 depicts a frame format of a buffer status report poll (BSRP) Trigger frame, in accordance with aspects of the present disclosure.

[0043] FIG. 17 depicts a frame format of a buffer status report (BSR), in accordance with aspects of the present disclosure.

[0044] FIG. 18 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0045] FIG. 19 depicts a frame format of a Multi-STA BlockAck (M-BA) frame, in accordance with aspects of the present disclosure.

[0046] FIG. 20 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0047] FIG. 21 depicts a deployment scenario between an AP and a plurality of STAs for LL communication, in accordance with aspects of the present disclosure.

[0048] FIG. 22a depicts a frame format of an add block acknowledgment (ADDBA) Request frame and FIG. 22b depicts a frame format of an ADDBA Response frame, in accordance with aspects of the present disclosure.

[0049] FIG. 23 depicts a frame format of an add block acknowledgment (ADDBA) Request frame, in accordance with aspects of the present disclosure.

[0050] FIG. 24 depicts a frame format of a Stream Classification Service (SCS) Request frame, in accordance with aspects of the present disclosure.

[0051] FIGs. 25 and 26 are block diagrams of devices for LL communication, in accordance with aspects of the present disclosure.

[0052] FIG. 27 is a block diagram of an AP communications manager for LL communication, in accordance with aspects of the present disclosure.

[0053] FIGs. 28 and 29 are block diagrams of devices for LL communication, in accordance with aspects of the present disclosure.

[0054] FIG. 30 is a block diagram of a STA communications manager for LL communication, in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0055] For completeness, it is hereby clarified that reference made to the definition of format: “[ref. X]” in any paragraph(s) in the description of the present disclosure is to be construed to refer to the corresponding citation “X” in the “References” section of the present specification. For example, [ref. 10] refers to citation

[0010] listed at the “References” section ofthe present specification, while [ref. 21-24] correspondingly refers to citations

[0021] -

[0024] mutatis mutandis.

[0056] Aspects of the present disclosure provide methods and corresponding apparatuses (e.g. at between an access point (AP) and at a station (STA), or between two STAs, where one of the STAs may function as an AP in this case) for low latency communication that may be deployed for IEEE 802.11 (Wi-Fi) networks. Nonetheless, it is also to be appreciated that the concepts and methods, in accordance with aspects of the present disclosure, may also be modified (mutatis mutandis) and be deployed for networks based on the 3 GPP standards such 3G, 4G, new radio (e.g., 5G NR) wireless technologies, or the like.

[0057] In accordance with aspects of the present disclosure, the AP and the STA may each be equipped with a multiple-input multiple-output (MIMO) antenna array comprising multiple panels (or otherwise known as antenna panels) for wireless communication.

[0058] In the context of IEEE 802.11 standards, the STA is a communication apparatus configured with capability to use a set of communication protocols based upon the IEEE 802.11 standards. Based on the IEEE 802.11-2020 definition, a STA may be any device that includes an IEEE 802.11 -conformant media access control (MAC) and physical layer (PHY) interface to the wireless medium (WM).

[0059] For example, a STA may be a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a desktop personal computer (PC), a personal digital assistant (PDA), either an access point or not (e.g., either an AP STA or a non-AP STA), or a Wi-Fi phone in a wireless local area network (WLAN) environment. In other aspects, the STA may further be an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, unmanned aerial vehicles (UAVs), meters, among other examples. The station may be fixed or mobile. In the WLAN environment, the terms “STA”, “non-AP STA”, “client”, “wireless client”, “user”, “user device”, and “mobile terminal” are often used interchangeably.

[0060] Likewise, an AP, which may be interchangeably referred to as a wireless access point (WAP) in the context of IEEE 802.11 standards, is a communication apparatus that allows STAs in a WLAN to connect to a wired network. The AP usually connects to a router (via a wired network) as a standalone device, but it may also be integrated with or employed in therouter. The AP may be a part of a basic service set (BSS), which consists of the AP and one or more STAs, facilitating communication between the STAs in the BSS.

[0061] It is to be appreciated that in the context of IEEE 802.11 standards, the AP is typically configured to operate in half-duplex mode, which implies the AP is unable to concurrently transmit and receive data at the same time on a same frequency channel. Hence, if the AP is currently transmitting a first data stream, and it is necessary to receive a second data stream from a STA, the current transmission needs to be stopped (i.e. to be preempted) by the AP in order that the second data stream from the STA can be received successfully by the AP. Aspects of the present disclosure discussed below are to be understood with this working principle of the AP in mind.

[0062] As mentioned above, a STA in a WLAN may work as an AP at different occasions, and vice versa. This is because communication apparatuses in the context of IEEE 802.11 standards may include both STA hardware components and AP hardware components. In this manner, the communication apparatuses may switch between a STA mode and an AP mode, based on actual WLAN conditions and / or requirements.

[0063] In various aspects below, each of the terms “channel” and “subchannel” may be used interchangeably with any one of “band”, “subband”, “subcarrier”, and “frequency segments”. The term “circuitry” may be used interchangeably with “module”.

[0064] The following description provides examples of methods and corresponding apparatuses for low latency communication, but they are not limiting on the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of aclaim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration”. Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0065] Any number of wireless networks may generally be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, and etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.

[0066] Aspects according to the present disclosure will be described, by way of example only, with reference to the drawings. Like reference numerals and characters in the drawings refer to like elements or equivalents.

[0067] FIG. 1 illustrates a block diagram of example components of a communication apparatus 100 configured for low latency (LL) communication, in accordance with aspects of the present disclosure. The communication apparatus 100 may be an AP or a STA, which may be used to implement aspects of the present disclosure. Each of these components may be in electronic communication with one another (e.g. via one or more buses).

[0068] The communication apparatus 100 may include circuitry 114, at least one radio transmitter 102, at least one radio receiver 104, and at least one antenna 112. The at least one antenna 112, in some implementations, may include multiple antennas, which are capable of concurrently transmitting or receiving multiple wireless transmissions (e.g. for MIMO communications). More specifically, the multiple antennas may be implemented in the form of an MU-MIMO antenna array, which is equipped to include multiple panels, according to an example.

[0069] The circuitry 114 may include at least one controller 106 for use in software and / or hardware-assisted execution of tasks that the controller 106 is designed to perform, including control of communications with other communication apparatuses in, for example, a MIMO wireless network. The circuitry 114 may further include at least one transmission signal generator 408 and at least one receive signal processor 110.

[0070] The controller 106 may generate control information. The controller 106 may also receive data from a data source (not shown), and the data may be for a downlink channel, and etc. The circuitry 114 may further include at least one memory (not shown) to store data and program codes for the communication apparatus 100. The memory may be (communicatively) coupled to the controller 106.

[0071] The memory may include RAM, ROM, or a combination thereof. The memory may store computer-readable code including instructions that, when executed by a processor (e.g. the controller 106) cause the communication apparatus 100 to perform various functions or methods described herein. In some implementations, the memory may contain, among other things, a BIOS (being a Basic Input / Output System) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0072] The controller 106 may process (e.g. encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The controller 106 may also generate reference symbols.

[0073] The controller 106 may control the transmission signal generator 108 for generating signals (e.g., an uplink (UL) signal, a downlink (DL) signal, etc.) to be transmitted via the radio transmitter 102 to other communication apparatuses and the receive signal processor 110 for processing signals (e.g., an UL signal, a DL signal, etc.) received via the radio receiver 104 from other communication apparatuses. The transmission signal generator 108 and the receive signal processor 110 may be implemented as independent, stand-alone modules of the communication apparatus 100 that communicate with the controller 106 for the above-mentioned functions, as depicted in FIG. 1.

[0074] The controller 106 may include an intelligent hardware device, (e.g. a general -purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the controller 106 may be configured to operate a memory array using a memory controller. In some implementations, a memory controller may further be integrated into controller 106. The controller 106 may be configured to execute computer-readable code stored in a memory (arranged either internal or external to the controller 106) to cause the communication apparatus 100 to perform various functions(e.g. functions or tasks that support detecting and / or tracking sensing targets, in accordance with aspects of the present disclosure).

[0075] The computer-readable code may include instructions to implement aspects of the present disclosure, including instructions for LL communication between different communication apparatuses (e.g. between an AP and a STA, or between two STAs, where one of the STAs may function as an AP). The computer-readable code may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some implementations, the computer-readable code may not be directly executable by the controller 106 but may cause a computing device (e.g. when compiled and executed) to perform functions described herein.

[0076] In some examples, the radio transmitter 102 and the radio receiver 104 may together be collocated and implemented as a single module, which may be termed a transceiver. The transceiver may communicate bi-directionally, via one or more antennas, wired, wireless links, or the like. For example, the transceiver may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate packets and provide the modulated packets to the antenna 112 for transmission, and to demodulate packets received from the antenna 112.

[0077] The circuitry 114, the radio transmitter 102, the radio receiver 104, and the antenna 112 of the communication apparatus 100 may be used to perform the various techniques and methods described herein. In the case of the communication apparatus 100 being an AP, the controller 106 may include an AP communications manager 2515, 2615 (refer to FIGs. 25-26) that may be configured to perform the operations shown in FIG. 2, as well as other operations described herein. On the other hand, in the case of the communication apparatus 100 being a STA, the controller 106 may include a STA communications manager 2815, 2915 (refer to FIGs. 28-29) that may be configured to perform the operations shown in FIG. 3, as well as other operations described herein.

[0078] Alternatively, the transmission signal generator 108 and the receive signal processor 110 may also be arranged within the controller 106. In various examples, the radio transmitter 102, the radio receiver 104, and the antenna 112 may be arranged to be controlled collectively by the controller 106.

[0079] FIG. 2 is a flowchart illustrating a method 200 at a first communication apparatus for low latency (LL) communication with a second communication apparatus, in accordance with aspects of the present disclosure. The operations of method 200 may be implemented by the AP, or its components (e.g. the first communication apparatus is the AP, and the second communication apparatus is a STA). For example, the operations of method 200 may be performed by an AP communications manager as described with reference to FIGs. 25-27. In some examples, the AP may execute a set of instructions to control the functional elements of the AP to perform the functions described below. Additionally or alternatively, the AP may perform aspects of the functions described below using special-purpose hardware.

[0080] Notwithstanding, the operations of method 200 may alternatively be implemented by a STA (or its components), if the STA is configured to function as an AP (e.g. the first communication apparatus is a first STA, and the second communication apparatus is a second STA).

[0081] At 205, the AP may receive an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus. The operations of 205 may be performed according to the methods described herein. In some examples, aspects of the operations of 205 may be performed by a receive component as described with reference to FIGs. 26-27.

[0082] In some aspects, the indication may be received via a BlockAck (BA) frame. The indication may be configured with a value of 0 or 1, in which the value of 0 indicates unavailability of LL data to be transmitted, whereas the value of 1 indicates availability of LL data to be transmitted.

[0083] In certain aspects, the indication may be received, in response to a multi-user (MU) physical layer protocol data unit (PPDU) transmitted by the first communication apparatus.

[0084] Alternatively or additionally, it is to be appreciated that if there is an ongoing transmission at the AP, the method may further comprise: preempting, based on the received indication, the ongoing transmission, prior to receiving the LL data. This is necessary, because as afore discussed, the AP operates in the half-duplex mode, i.e. the AP is unable to concurrently transmit and receive data on a same frequency channel. Preempting the ongoing transmission advantageously permits the AP to then receive the LL data for processing as soonas possible, in order to thereby satisfy the time-sensitive processing requirements imposed by the nature of the LL data.

[0085] Specifically, it is to be appreciated that in the context of IEEE 802.11 standards, the term “preemption” refers to a mechanism whereby ongoing transmission(s) at the AP / STA is stopped, so that high-priority network traffic (or signals) are given preference over low-priority traffic to improve network performance and reliability, especially in congested environments. The step of preemption may be performed according to the methods described herein. In some examples, aspects of the operations of preemption may be performed by a preempt component as described with reference to FIGs. 26-27.

[0086] At 210, the AP may transmit, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data. The operations of 210 may be performed according to the methods described herein. In some examples, aspects of the operations of 210 may be performed by a transmit component as described with reference to FIGs. 26-27.

[0087] In some aspects, the first Trigger frame may be transmitted, based in part on a data urgency level of the LL data communicated by the second communication apparatus. The data urgency level may be communicated via an access category index (ACI) bitmap.

[0088] In other aspects, based on the data urgency level, a size of a resource unit (RU) to be allocated to the second communication apparatus to enable transmission of the LL data may be determined by the first communication apparatus.

[0089] In further aspects, the first communication apparatus may further transmit, to the second communication apparatus, a second Trigger frame to request information about the LL data, prior to transmitting the first Trigger frame, wherein the second Trigger frame is a buffer status report poll (BSRP) Trigger frame.

[0090] In some aspects, the first communication apparatus may optionally receive, from the second communication apparatus, an add block acknowledgment (ADDBA) Request frame configured to indicate a preemption intent.

[0091] At 215, the AP may receive, from the second communication apparatus (based on receipt thereby of the first Trigger frame transmitted by the AP at 210), the LL data. The operations of 215 may be performed according to the methods described herein. In someexamples, aspects of the operations of 215 may be performed by a receive component as described with reference to FIGs. 26-27.

[0092] At 220, the AP may process the received LL data. The operations of 220 may be performed according to the methods described herein. In some examples, aspects of the operations of 220 may be performed by a process component as described with reference to FIGs. 26-27.

[0093] Additionally or alternatively, the first communication apparatus may further transmit, to the second communication apparatus, a polling frame to request information on a preemption intent of the second communication apparatus, which indicates whether the second communication apparatus has intent for the first communication apparatus to enable preemption, wherein the polling frame is transmitted prior to receiving, from the second communication apparatus, the indication about the LL data to be transmitted to the first communication apparatus. Consequently, the first communication apparatus may receive, from the second communication apparatus, a response to the polling frame indicating the preemption intent.

[0094] In some aspects, the polling frame may be one of: a buffer status report poll (BSRP) Trigger frame, and a Null data packet (NDP) feedback report poll (NFRP) Trigger frame. The preemption intent may be indicated via a Multi-STA BlockAck (M-BA) frame, or a stream classification service (SCS) Request frame.

[0095] In other aspects, the polling frame may be an add block acknowledgment (ADDBA) Request frame, and the preemption intent may be indicated via an ADDBA Response frame.

[0096] In some implementations, the operations of the method 200 may be programmed into, and stored as corresponding computer-readable code that is executable by the first communication apparatus. The above description for the various components in FIG. 1 apply, mutatis mutandis, for an example implementation at the AP. In this case, the controller 106 may include an AP communications manager 2515, 2615 that may be configured to perform the operations depicted in FIG. 2, as well as other operations described herein.

[0097] FIG. 3 is a flowchart illustrating a method 300 at a second communication apparatus for low latency (LL) communication with a first communication apparatus, in accordance with aspects of the present disclosure. The operations of method 300 may be implemented by theSTA, or its components (e.g. the second communication apparatus is the STA, and the first communication apparatus is an AP). For example, the operations of method 300 may be performed by a STA communications manager as described with reference to FIGs. 28-30. In some examples, the STA may execute a set of instructions to control the functional elements of the STA to perform the functions described below. Additionally or alternatively, the STA may perform aspects of the functions described below using special-purpose hardware.

[0098] At 305, the STA may buffer LL data. It is to be appreciated that buffering the LL data is considered a form of processing of the LL data, as understood in the art. So broadly, the STA is processing the LL data, when buffering the LL data. The operations of 305 may be performed according to the methods described herein. In some examples, aspects of the operations of 305 may be performed by a process and buffer component as described with reference to FIGs. 29-30.

[0099] At 310, the STA may transmit an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted. The operations of 310 may be performed according to the methods described herein. In some examples, aspects of the operations of 310 may be performed by a transmit component as described with reference to FIGs. 29-30.

[0100] At 315, the STA may receive, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data. The operations of 315 may be performed according to the methods described herein. In some examples, aspects of the operations of 315 may be performed by a receive component as described with reference to FIGs. 29-30.

[0101] At 320, the STA may transmit (based on receipt of the first Trigger frame at 315, which was transmitted by the AP), to the first communication apparatus, the LL data. The operations of 320 may be performed according to the methods described herein. In some examples, aspects of the operations of 320 may be performed by a process and buffer component as described with reference to FIGs. 29-30.

[0102] In some implementations, the operations of the method 300 may be programmed into, and stored as corresponding computer-readable code that is executable by the second communication apparatus.

[0103] In accordance with aspects of the present disclosure, there is disclosed a first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: a receiver, which in operation, receives an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and receives the LL data from the second communication apparatus; a transmitter, which in operation, transmits, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; and circuitry, which in operation, preempts, based on the received indication, an ongoing transmission at the first communication apparatus, and processes the received LL data. The circuitry, the receiver, and the transmitter may be referenced to the corresponding components afore described with FIG. 1.

[0104] In accordance with aspects of the present disclosure, there is further disclosed a corresponding second communication apparatus for low latency (LL) communication with the first communication apparatus, which comprises: circuitry, which in operation, buffers LL data; a transmitter, which in operation, transmits, an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted, and transmits, to the first communication apparatus, the LL data; and a receiver, which in operation, receives, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data. Similarly, the circuitry, the transmitter and the receiver may be referenced to the corresponding components afore described with FIG. 1.

[0105] In an example, referring to a deployment scenario 400 depicted in FIG. 4, an AP 405 (being the TXOP holder) is configured to transmit data to a plurality of STAs 410 (e.g. STA1, STA2, and STA3) sequentially, and if there are no data 415 intended for a STA 410 (e.g. STA3), the AP 405 may instead transmit a QoS Null frame 420 or a control frame 420 (as known in the art - refer below to discussions for FIGs. 5-6) to inform said STA 410 as such. An example frame format of the QoS Null frame 420 will be discussed below with reference to FIG. 5. An example frame format of a control frame 420 will be discussed below with reference to FIG. 6. Particularly, the STAs 410 may respond with a BlockAck (BA) frame 425 arranged to indicate whether there are LL data buffered at the respective STAs 410, in which the LL data are received from higher (OSI) layers in the associated STAs 410, and transmission of the LL data to the AP 405 may (in certain instances) require the AP 405 to enable andperform preemption. The OSI layers refer to the 7 layers conceptualized under the Open Systems Interconnection (OSI) model, as known in the art. For example, the BA frame 425 may include a field (having an LL value), that permits indication of absence or presence of LL data buffered at the STA 410 to be transmitted. The indication of the LL value may also be known as LL indication in various different aspects of the present disclosure discussed hereafter.

[0106] For example, if the LL indication is 0, it may indicate unavailability of LL data to be transmitted by the STA 410 (to the AP 405), and so preemption by the AP 405 is not required (regardless whether there are ongoing transmission(s) at the AP 405). Conversely, if the LL indication is 1, it may indicate availability of LL data to be transmitted by the STA 410 (to the AP 405), and therefore, preemption by the AP 405 may be required (if there are ongoing transmi ssion(s) at the AP 405). Referring to FIG. 4, it is depicted there are no LL data buffered at STA1 410 and STA2 410 (i.e. the LL indication is set to 0, and corresponding BA frames 425 are respectively transmitted by STA1 410 and STA2 410 to the AP 405 to inform the latter), and thus it is not necessary for the AP 405 to enable preemption in those instances.

[0107] On the other hand, there are LL data buffered at STA3 410 (i.e. the LL indication is set to 1, and a BA frame 425 is transmitted by STA3 410 to the AP 405 to inform the latter), and the AP 405 needs to enable preemption (if there are ongoing transmission(s) at the AP 405) in order to receive the LL data from STA3 410. The effect of this methodology is that a STA 410 may indicate to the AP 405, that there are LL data buffered at the STA 410 for transmission, regardless of whether the STA 410 may be a recipient of (prior) data from the AP 405. The benefit of this methodology is that multiple STAs 410 may indicate LL data arrival in time from higher OSI layers at the respective STAs 410 to the AP 405, which subsequently may enable the STAs 410 to transmit LL data with low latency, and improved efficiency. Overall, this may lead to better and improved network performance, thereby resulting in improved user experience at the STAs 410.

[0108] In accordance with aspects of the present disclosure, an example frame format 500 of a triggered response scheduling (TRS) Control field in the QoS Null frame is depicted in FIG. 5, whereby the mechanism of TRS Control may be implemented through the QoS Null frame. In this case, a Solicit LL Indication subfield 505 is implemented in the QoS Null frame, and the Solicit LL Indication subfield 505 may take on a value of 0 or 1. If the Solicit LLIndication subfield 505 is set to a value of 1, it indicates the QoS Null frame is configured to solicit BA frame(s) with the LL indication set to 1; otherwise if the QoS Null frame is not configured to solicit BA frame(s) with the LL indication set to 1, the value for the Solicit LL Indication subfield 505 is set to 0. It is to be appreciated that a reserved field in the QoS Null frame may be used to implement the Solicit LL Indication subfield 505. The effect of using the QoS Null frame in this manner enables the AP to notify the STAs that the QoS Null frame is transmitted to solicit from the STA(s) that have buffered LL data to send, i.e. the LL indication is set to 1. Hence, the STA(s) may respond with BA frames with the LL indication set to 1 and may also indicate arrival in time of the associated LL data at the STA(s) from higher OSI layers thereat.

[0109] In accordance with aspects of the present disclosure, an example frame format 600 of a control frame is depicted in FIG. 6. A block acknowledgement request (BAR) frame may be used as the control frame (but not limited to as such), as above described with FIG. 4, and a proposed frame format 600 of the BAR frame is shown in FIG. 6. Specifically, there is a BAR control subfield 605 implemented in the BAR frame, and within the BAR control subfield 605, a Solicit LL Indication subfield 610 is further implemented. Similarly, the Solicit LL Indication subfield 610 may be set to a value of 0 or 1. If the Solicit LL Indication subfield 610 is set to a value of 1, it indicates the BAR frame is configured to solicit BA frame(s) with the LL indication set to 1; otherwise if the BAR frame is not configured to solicit BA frame(s) with the LL indication set to 1, the value for the Solicit LL Indication subfield 610 is set to 0. It is to be appreciated that a Reserved field 615 in the BAR frame may also be used to implement the Solicit LL Indication subfield 610.

[0110] Notwithstanding, it is also to be appreciated that a buffer status report poll (BSRP) Trigger frame, and a Null data packet (NDP) feedback report poll (NFRP) Trigger frame may also be considered as other available options for soliciting the respective LL indications from STAs, which are respectively included in a BSR (e.g. based on an access category (AC) identifier (ACI) bitmap) and an NDP feedback report (e.g. based on the set of subcarriers of the high-efficiency long training field (HE-LTF)). That is to say, the BSRP Trigger frame, or the NFRP Trigger frame may also be used as the control frame, as above described with reference to FIG. 5.[oni] FIG. 7 illustrates an example of a first frame format 700 of a BlockAck (BA) frame, in accordance with aspects of the present disclosure. It is highlighted that the BA frame is arranged to be of the same format as the frame format of a M-BA frame, as set out in the IEEE low latency indication proposed draft text (PDT) [ref. 10], It is to be appreciated that in the Per AID TID Info field 705 depicted in the first frame format 700, there is defined an AID TID Info subfield 710, which comprises an AID11 subfield 715, an Ack Type subfield 720, and a TID subfield 725. In an example, the AID 11 subfield 715 is not set to a value of 2045, the Ack Type subfield 720 is set to a value of 0, and the TID subfield 725 is set to a value of 13.

[0112] The various types of proposed encoding available in the Feedback Type subfield for the M-BA frame is depicted in a table 730 (in FIG. 7), if the AID11 subfield 715 is not set to 2045, and if the combination of the Ack Type subfield 720 is set to 0 and the TID subfield 725 is set to 13, respectively. A Feedback Type subfield 735 is included in a Block Ack Starting Sequence Control subfield 740 of the first frame format 700.

[0113] FIG. 7 further illustrates an example format of a Feedback subfield 745 for low latency feedback, in which when a value of the Feedback Type field 730-1 in the table 730 is of value 1, the Feedback subfield 745 is a format that may be utilised in a Feedback subfield 750 arranged in the Per AID TID Info field 705. So, the Feedback subfield 745 is proposed based upon the table 730. In context, it is to be appreciated that the value in the Feedback Type subfield 735 indicates the type of feedback (as referenced under the Feedback subfield type 730-2 in the table 730) - if the value is 1, it indicates the type of feedback is low latency feedback, and so the Feedback subfield 745 may be employed for the Feedback subfield 750.

[0114] FIG. 8 illustrates an example of a second frame format 800 of a BlockAck (BA) frame, in accordance with aspects of the present disclosure. Specifically, a BA Control subfield 805 is configured in the second frame format 800, and an LL Indication subfield 810 is included in the BA Control subfield 805. The value of the LL Indication subfield 810 may be set to 1 to indicate there are LL data buffered at an associated STA, and the LL Indication subfield 810 is otherwise set to 0 to indicate there are no LL data buffered at the STA. An existing reserved bit may be used to implement the LL Indication subfield 810.

[0115] Further, a STA may also indicate in the BA frame regarding if the AP needs to enable preemption in a subsequent downlink (DL) physical layer protocol data unit (PPDU) transmission. The AP may also determine whether to include a preemption intent polling, e.g.if the STA indicates preemption is not needed, the AP may stop the preemption operation for the STA. Another reserved bit (not shown in FIG. 8) may be used by the STA to inform the preemption intent vis-a-vis the subsequent DL PPDU transmission.

[0116] In an example, referring to a deployment scenario 900 depicted in FIG. 9, an AP 905 (being the TXOP holder) is configured to transmit a multi-user (MU) PPDU 915, which is arranged to include data frames and / or QoS Null frames in different resource units (RUs) in the MU PPDU 915 intended respectively for a plurality of STAs 910 (e.g. STA1, STA2, and STA3). This scenario is directed at enabling preemption during an MU PPDU transmission 920. Particularly, if there are downlink (DL) data from the AP 905 intended for a STA 910, the AP 905 transmits the data frame (with the DL data) in the RU to the STA 910 (e.g. STA1, and STA2). On the other hand, if there are no DL data from the AP 905 to a STA 910, the AP 905 then transmits a QoS Null frame in the RU to said STA 910 (e.g. STA3).

[0117] In response to receiving the MU PPDU 915, the STAs 910 may respond with respective BA frames 920 for multi-user transmission (e.g. OFDMA, MU-MIMO transmissions, etc.) that are configured to include indication whether there are LL data buffered at the respective STAs 910, which may then require preemption by the AP 905. For example, in FIG. 9, if the LL indication is set to a value of 1, it indicates there are LL data buffered at a STA 910, and preemption at the AP 905 is needed, and vice-versa, if the LL indication is set to a value of 0. It is to be appreciated that scheduling information for the BA frame 920 may be carried in either the TRS Control subfield or a Trigger frame (not shown in FIG. 9). In this manner, the AP 905 may poll multiple STAs 910 simultaneously to obtain the respective LL indications in advance, and thereby reduce delay on the part of the STAs 910 in transmitting LL data. It is to be appreciated that the frame format for the QoS Null frame and the BA frame 920 may follow the same respective frame formats, as afore discussed in FIGs. 5, and 7-8. Alternatively, instead of transmitting in different RUs, the MU PPDU 915 and BA frames 920 may instead be transmitted using different spatial streams (this is not depicted in FIG. 9).

[0118] In an example, referring to a deployment scenario 1000 depicted in FIG. 10, an AP 1005 (as the TXOP holder) is configured to transmit a multi-user (MU) PPDU 1015 to a plurality of STAs 1010 (e.g. STA1, STA2, and STA3). This is directed to the scenario whereby only one STA 1010 provides the LL indication set to the value of 1. Particularly in this scenario 1000, LL data intended for the AP 1005 arrives at STA3 1010 (from higher OSI layers thereat).STA3 1010 then provides, in a BA frame 1020, the LL indication with a value of 1 to indicate there are LL data buffered at STA3 1010 for transmission to the AP 1005. Upon receiving the BA frame 1020 from STA3 1010 (with the LL indication set to 1), the AP 1005 stops (i.e. preempt) any ongoing DL transmission(s) and transmits a basic Trigger frame (TF) 1025 to solicit the LL data from STA3 1010. Once STA3 1010 has received the basic TF 1025 from the AP 1005, STA3 1010 proceeds to transmit the LL data 1030 to the AP 1005.

[0119] FIG. 11 shows a frame format 1100 of a trigger-based (TB) physical layer protocol data unit (PPDU) frame, in accordance with aspects of the present disclosure. The frame format 1100 of the TB PPDU may be adopted for use in the deployment scenario 1000 of FIG. 10. In the frame format 1100 of the TB PPDU, there is defined a U-SIG subfield 1105, which has two portions, being a U-SIG- 1 portion 1110 and a U-SIG-2 portion 1115. Specifically, a More LL Data subfield 1120 is defined at bit “B20” 1125 in the U-SIG-1 portion 1110 of the U-SIG subfield 1105. The More LL Data subfield 1120 may take the value of 1 to indicate there are more LL data buffered at a STA to be sent to the AP, and otherwise the More LL Data subfield 1120 may take the value of 0. It is to be appreciated that a Disregard subfield 1130, 1135 (arranged in either the U-SIG-1 portion 1110 or the U-SIG-2 portion 1115) or a Validate subfield 1140 (arranged in the U-SIG-2 portion 1115) may alternatively be used to implement the More LL Data subfield 1120. In other examples, the More LL Data subfield 1120 may be included in the MAC header of a data packet (not shown in FIG. 11). The effect of using the proposed TB PPDU is that, when a STA indicates there are no more LL data buffered at the STA to be sent, the AP may avoid enabling preemption and improving efficiency of operations at the AP.

[0120] In an example, FIG. 12 illustrates a deployment scenario 1200 between an AP 1205 (as the TXOP holder) and a plurality of STAs 1210 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. In particular, LL data intended for the AP 1205 arrive at multiple STAs 1210 (e.g. at STA2, and at STA3). Hence, this is directed to the scenario whereby multiple STAs 1210 provide the LL indication set to the value of 1. So, the scenario 1200 of FIG. 12 may be viewed as a variation of the deployment scenario 1000 depicted in FIG. 10.

[0121] In FIG. 12, STA2 1210 and STA3 1210 provide, in respective BA frames 1215, the LL indication with a value of 1 to indicate there are LL data buffered at STA2 1210 and STA31210 for transmission to the AP 1205. Upon receiving the BA frame 1215 from STA2 1210 and STA3 1210 (with the LL indication set to 1), the AP 1205 stops (i.e. preempt) any ongoing DL transmission(s), and broadcasts a BSRP Trigger frame 1220 to STA2 1210 and STA3 1210 to gather information about the LL data buffered at STA2 1210 and STA3 1210. Upon receiving the BSRP Trigger frame 1220, STA2 1210 and STA3 1210 in turn respond with respective BSRs 1225 to the AP 1205. After receiving the BSRs 1225 from STA2 1210 and STA3 1210, the AP 1205 broadcasts a basic TF 1230 to STA2 1210 and ST A3 1210 in order to solicit the LL data, based in part on a data urgency level of the LL data (e.g. as indicated in an ACI bitmap). Alternatively, the AP 1205 may also send the basic TF 1230, without sending the BSRP Trigger frame 1220, based on determination by the AP 1205 or based on prior knowledge at the AP 1205. Once STA2 1210 and STA3 1210 have received the basic TF 1230 from the AP 1205, each of STA2 1210 and STA3 1210 may proceed to transmit the associated LL data 1235 to the AP 1205. In this scenario 1200, the LL data 1235 are transmitted sequentially (in time) by the STAs 1210, i.e. STA2 1210 first transmits the LL data 1235, and followed by STA3 1210.

[0122] In an example, FIG. 13 illustrates a deployment scenario 1300 between an AP 1305 (as the TXOP holder) and a plurality of STAs 1310 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. In particular, LL data intended for the AP 1305 arrive at multiple STAs 1310 (e.g. at STA2, and at STA3)from higher OSI layers thereat. Hence, this is directed to the scenario whereby multiple STAs 1310 provide the LL indication set to the value of 1. So, the scenario 1300 of FIG. 13 may be viewed as a variation of the deployment scenario 1200 depicted in FIG. 12.

[0123] In FIG. 13, STA2 1310 and STA3 1310 provide, in respective BA frames 1315, the LL indication with a value of 1 to indicate there are LL data buffered at STA2 1310 and STA3 1310 for transmission to the AP 1305. Upon receiving the BA frame 1315 from STA2 1310 and STA3 1310 (with the LL indication set to 1), the AP 1305 stops (i.e. preempt) any ongoing DL transmi ssion(s), and broadcasts a basic TF 1320 to STA2 1310 and STA3 1310 to solicit the LL data buffered at STA2 1310 and STA3 1310. Once STA2 1310 and STA3 1310 have received the basic TF 1320 from the AP 1305, STA2 1310 and STA3 1310 may proceed to transmit the associated LL data 1330, 1335 to the AP 1305. In this scenario 1300, the LL data 1330, 1335 are transmitted jointly by the STAs 1310, i.e. STA2 1310 transmits in a first RU indicated by the basic TF 1320, and STA3 1310 transmits in a second RU indicated by thebasic TF 1320. The first RU and second RU may be located in respective subcarriers in a same orthogonal frequency division multiplexing (OFDM) symbol. The advantage is that the STAs 1310 may transmit LL data 1330, 1335 concurrently in different RUs in the same time symbol.

[0124] Alternatively or additionally, the AP 1305 may also send a BSRP Trigger frame (i.e. follows the same mechanism explained vis-a-vis FIG. 12) to gather information about the LL data buffered at STA2 1310 and STA3 1310, before broadcasting the basic TF 1320. In this manner, with information about the LL data, the AP 1305 may determine, in advance, sizes of respective RUs to be allocated for transmitting the LL data by each of STA2 1310 and STA3 1310, which may be based at least in part on a data urgency level of the LL data.

[0125] In an example, FIG. 14 illustrates a deployment scenario 1400 between an AP 1405 (as the TXOP holder) and a plurality of STAs 1410 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. Prior to the AP 1405 transmitting 1415 a downlink (DL) PPDU 1420 to the STAs 1410, the AP 1405 may initially transmit a polling frame 1425 (e.g. a control frame, or a management frame) to poll each of the STAs 1410 for intent to request the AP 1405 to enable preemption. The DL PPDU 1420 may include a plurality of RUs located in respective subcarriers in a same OFDM symbol. Each of the STAs 1410 may reply to the polling frame 1425 in a response frame 1430, which may be configured with different RUs (that are located in respective subcarriers in a same OFDM symbol) to enable the respective STAs 1410 to respond.

[0126] In FIG. 14, it is depicted that STA1 1410 and STA3 1410 have indicated preemption intent in the respective response frames 1430. When the AP 1405 does not have DL data to transmit to a STA 1410 (e.g. STA3 1410) that has indicated preemption intent, the AP 1405 may transmit a QoS Null frame (to STA3 1410) to allow preemption (e.g. if the AP 1405 may still be transmitting DL data to other STA1 1410, STA2 1410, even if the AP 1405 presently does not transmit any DL data to STA3 1410). In this manner, the AP 1405 may identify, in advance, STAs 1410 that require frames to allow preemption. As a result, a STA 1410 may transmit LL data with low latency. When LL data arrives at a STA 1410 (e.g. STA3 1410), the said STA 1410 may then send a BA frame 1435 to provide indication (to the AP 1405) that there are LL data buffered at the STA 1410. In this manner, the AP 1405 may utilize resources with improved efficiency versus the case of transmitting a QoS Null frame to all the STAs 1410. Alternatively, instead of transmitting in different RUs, the DL PPDU 1420 and BAframes 1435 may instead be transmitted using different spatial streams (this is not depicted in FIG. 14).

[0127] In an example, FIG. 15 illustrates a deployment scenario 1500 between an AP 1505 (as the TXOP holder) and a plurality of STAs 1510 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. This depicts a variation of the deployment scenario 1400 of FIG. 14. Specifically, a buffer status report poll (BSRP) Trigger frame 1515 is utilized by the AP 1505 as the polling frame, and a buffer status report (BSR) 1520 is utilized by the STAs 1510 to respectively respond to the BSRP Trigger frame 1515.

[0128] A proposed frame format 1600 of the BSRP Trigger frame is depicted in FIG. 16. The frame format 1600 includes a Common Info field 1605, which is arranged to include a Preemption Intent Poll subfield 1610. If the Preemption Intent Poll subfield 1610 is set to 1, it indicates the AP is polling a STA for (potential) preemption intent, and vice-versa, if the Preemption Intent Poll subfield 1610 is set to 0. A Reserved subfield 1615 in the Common Info field 1605 may also be used to implement the Preemption Intent Poll subfield 1610.

[0129] A proposed frame format 1700 of the BSR is depicted in FIG. 17, as an example in the present disclosure. Specifically, the frame format 1700 of the BSR includes a BSR Control subfield (not shown in Fig. 17), which in turn includes a Control Information subfield 1705. The Control Information subfield 1705 may be extended to include an indication by a STA for preemption intent. To clarify, preemption intent in this context indicates whether the STA has intent for the AP to enable preemption. The preemption intent may be indicated by setting a ACI High subfield 1710 (included in the Control Information subfield 1705) to a value indicating low latency AC, and a Queue Size High subfield 1715 (included in the Control Information subfield 1705) to 0. It is to be appreciated that the BSR Control subfield may be included in a QoS Null frame or a Management frame (as known in the art).

[0130] In an example, FIG. 18 illustrates a deployment scenario 1800 between an AP 1805 and a plurality of STAs 1810 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. This depicts another variation of the deployment scenario 1400 of FIG. 14. Specifically, a buffer status report poll (BSRP) Trigger frame 1815 is utilized by the AP 1805 as the polling frame, and a Multi-STA BlockAck (M-BA) frame 1820 is utilized by the STAs 1810 to respond to the BSRP Trigger frame 1815. Theframe format of the BSRP Trigger frame 1815 may be referenced to the proposed frame format 1600 of the same depicted in FIG. 16. It is to be appreciated that the M-BA frame 1820 is suitable to be used as an Initial Control Response (ICR) frame due to its flexibility to carry additional information [ref. 10, 11],

[0131] FIG. 19 depicts a proposed frame format 1900 of a Multi-STA BlockAck (M-BA) frame, in accordance with aspects of the present disclosure. The frame format 1900 of the M-BA frame includes a BA information subfield 1905 (being a Per AID TID Info field), which in turn includes a Block Ack Starting Sequence Control subfield 1910 and a Block Ack Bitmap subfield 1915. The Block Ack Starting Sequence Control subfield 1910 is configured to include a Fragment Number subfield 1920 and a Starting Sequence Number subfield 1925. It is to be appreciated that the Starting Sequence Number subfield 1925 are configured as Reserved bits. The Starting Sequence Number subfield 1925 may be configured to include a Preemption Intent subfield 1930 and a Reserved subfield 1935. The Preemption Intent subfield 1930 may be used by a STA to convey whether said STA has intent for the AP to enable preemption. The value of the Preemption Intent subfield 1930 is set to 1 to indicate the STA has intent for AP to enable preemption, or set to 0 otherwise.

[0132] Alternatively, a Reserved subfield 1940 in the Block Ack Bitmap subfield 1915 may also be used to implement the Preemption Intent subfield 1930.

[0133] Notwithstanding, the Reserved subfield 1935 in the Block Ack Starting Sequence Control subfield 1910 may alternatively be used to implement the Preemption Intent subfield 1930.

[0134] In an example, FIG. 20 illustrates a deployment scenario 2000 between an AP 2005 (as the TXOP holder) and a plurality of STAs 2010 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. This depicts another variation of the deployment scenario 1400 of FIG. 14. Specifically, the AP 2005 transmits a polling frame 2015 (such as a control frame) to all the STAs 2010 to poll for intent for the AP 2005 to enable preemption, and thereafter, if a STA 2010 indicated there is no intent for preemption by the AP 2005, and also that there are no DL data from the AP 2005 for the said STA 2010, the AP 2005 performs no transmission to said STA 2010. Otherwise, the AP 2005 transmits data frames, QoS Null frames 2030 (or control frames) to each of STAs 2010 sequentially, in which said STAs 2010 have respectively indicated there is intent forpreemption by the AP 2005. That is to say, if there are DL data from the AP 2005 intend for a STA 2010, the AP 2005 transmits a data frame 2025 (having the DL data) to the STA 2010. On the other hand, if there are no DL data from the AP 2005 intended for a STA 2010, but yet the STA 2010 has indicated an intent for preemption, the AP 2005 then transmits a QoS Null frame 2030 (or a control frame) to the STA 2010 to solicit LL indication from the STA 2010.

[0135] To elaborate with respect to FIG. 20, STA1 2010 has indicated a preemption intent, and there are DL data from AP 2005 intended for STA1 2010. So the AP 2005 sends the DL data to STA1 2010. STA22010 has indicated no preemption intent, and there are no DL data for STA22010 from the AP 2005. As a result, the AP 2005 transmits nothing to STA22010. STA3 2010 has indicated a preemption intent, and there are no DL data from the AP 2005 for STA3 2010. Hence, the AP 2005 transmits a QoS Null frame 2030 to STA32010 to solicit LL indication. STA1 2010 and STA3 2010 may send the LL indication in a BA frame 2035, in accordance with the afore various aspects described. It is to be appreciated that QoS Null frame 2030 and BA frame 2035 follow the respective frame formats above described with reference to FIGs. 5, 7.

[0136] In an example, FIG. 21 illustrates a deployment scenario 2100 between an AP 2105 (as the TXOP holder) and a plurality of STAs 2110 (e.g. STA1, STA2, and STA3) for LL communication, in accordance with aspects of the present disclosure. This depicts another variation of the deployment scenario 1400 of FIG. 14. Specifically, the AP 2105 broadcasts a polling frame 2115 (such as a control frame) to all STAs 2110 to poll them for intent for preemption by the AP 2105, and thereafter, if a STA 2110 indicated (in a response frame 2120) there is no intent for preemption, and also that there are no DL data from the AP 2105 for the said STA 2110, the AP 2105 performs no transmission to said STA 2110. Otherwise, the AP 2105 makes a transmission 2125 for an MU PPDU 2130, in which data frames or QoS Null frames are transmitted, via different RUs in the MU PPDU 2130, to each of the STAs 2110 that have respectively indicated (in respective response frames 2120) there is intent for preemption. In other words, if there are DL data from the AP 2105 intended for a STA 2110, the AP 2105 transmits a data frame (having the DL data) in an allocated RU in the MU PPDU 2130 to the STA 2110. On the other hand, if there are no DL data from the AP 2105 intended for a STA 2110, but yet the STA 2110 has indicated an intent for preemption, the AP 2105 then transmits a QoS Null frame in an allocated RU in the MU PPDU 2130 to the STA 2110.

[0137] To explain with respect to FIG. 21, STA1 2110 has indicated a preemption intent (in a response frame 2120), and there are DL data from the AP 2105 intended for STA1 2110. So the AP 2105 sends the DL data to STA1 2110 via a first RU (e.g. depicted as RU1 in FIG.21) in the MU PPDU 2130. STA2 2110 has indicated no preemption intent (in a response frame 2120), and there are no DL data for STA2 2110 from the AP 2105. As a result, the AP 2105 transmits nothing to STA2 2110. Separately, STA3 2110 has indicated a preemption intent (in a response frame 2120), and there are no DL data from the AP 2105 for STA3 2110. So, the AP 2105 transmits a QoS Null frame to STA3 2110 via a second RU (e.g. depicted as RU2 in FIG. 21) in the MU PPDU 2130 for soliciting LL data. STA1 2110 and STA3 2110 may send the LL indication in a BA frame 2135, in accordance with the afore described. It is to be appreciated that QoS Null frame and BA frame 2135 follow the respective frame formats as above described with reference to FIGs. 5, 7.

[0138] Alternatively, instead of transmitting in different RUs, the MU PPDU 2130 and BA frames 2135 may instead be transmitted using different spatial streams (this is not depicted in FIG. 21).

[0139] In various examples, the AP may also poll for preemption intent from a plurality of STAs during a BA agreement procedure (as known in the art) performed prior to data transmission, in which the AP may include related information in an add block acknowledgment (ADDBA) Request frame, which is then transmitted to the STA. In turn, the STA may indicate a preemption intent within a ADDBA Response frame, which is then transmitted as a response (to the ADDBA Request frame) to the AP. In connection, FIG. 22a depicts a frame format 2200 of the ADDBA Request frame and FIG. 22b depicts a frame format 2250 of the ADDBA Response frame, in accordance with aspects of the present disclosure.

[0140] Referring to FIG. 22a, there is configured an ADDBA Extended Parameter Set subfield 2205 in the frame format 2200 of the ADDBA Request frame, and within the ADDBA Extended Parameter Set subfield 2205, a Preemption Intent Poll subfield 2210 is defined. The Preemption Intent Poll subfield 2210 is set to 1 to indicate the AP is polling for preemption intent from a STA, or the Preemption Intent Poll subfield 2210 is otherwise set to 0 to indicate the AP is not polling for preemption intent from the STA. It is to be appreciated that a Reserved subfield 2215 (arranged in the ADDBA Extended Parameter Set subfield 2205) may be used to implement the Preemption Intent Poll subfield 2210.

[0141] Referring to FIG. 22b, there is similarly configured an ADDBA Extended Parameter Set subfield 2255 in the frame format 2250 of the ADDBA Response frame, and within the ADDBA Extended Parameter Set subfield 2255, a Preemption Intent subfield 2260 is defined. The Preemption Intent subfield 2260 is set to 1 to indicate the STA has intent for the AP to enable preemption, and otherwise set to 0 to indicate the STA has no intent for the AP to enable preemption. It is to be appreciated that a Reserved subfield 2265 (arranged in the ADDBA Extended Parameter Set subfield 2255) may be used to implement the Preemption Intent subfield 2260.

[0142] In various examples, a STA may indicate a preemption intent during a BA agreement procedure (as known in the art) in an add block acknowledgment (ADDBA) Request frame, wherein a frame format 2300 of said ADDBA Request frame is depicted in the FIG. 23. Specifically, the STA may include a preemption intent in the ADDBA Request frame, which is transmitted to the AP.

[0143] Referring to FIG. 23, there is configured an ADDBA Extended Parameter Set subfield 2305 in the frame format 2300 of the ADDBA Request frame, and within the ADDBA Extended Parameter Set subfield 2305, a Preemption Intent subfield 2310 is defined. The Preemption Intent subfield 2310 is set to 1 to indicate the STA has intent for the AP to enable preemption, or is otherwise set to 0 to indicate the STA has no intent for the AP to enable preemption. It is to be appreciated that a Reserved subfield 2315 (arranged in the ADDBA Extended Parameter Set subfield 2305) may be used to implement the Preemption Intent subfield.

[0144] It is to be appreciated that optionally, if a STA has indicated a preemption intent in the ADDBA Request frame, the AP may then poll for preemption intent during transmit opportunities (TXOPs), in accordance with the examples described with reference to FIGs. 22a, 22b.

[0145] In various examples, instead of polling a STA for associated preemption intents, the AP may determine whether to transmit a QoS Null frame to the STA based on certain conditions being satisfied (e.g. based on whether Stream Classification Service (SCS) is used). In this context, the AP may transmit a QoS Null frame to the STA to solicit LL data, if the STA has requested usage of SCS stream(s). Optionally, the STA may also indicate a preemptionintent in a SCS Request frame that is transmitted to the AP, in which a frame format 2400 of said SCS Request frame is depicted in FIG. 24.

[0146] Referring to FIG. 24, there is configured a SCS Descriptor List subfield 2405 in the frame format 2400 of the SCS Request frame, and within the SCS Descriptor List subfield 2405, an Optional Subelements subfield 2410 is defined. In the Optional Subelements subfield 2410, there is defined a Subelement ID subfield 2415, which may be used to indicate preemption intent. Particularly, if a subelement for preemption intent is present (in the Subelement ID subfield 2415), it indicates the STA has intent for the AP to enable preemption or otherwise, if a subelement for preemption intent is absent (from the Subelement ID subfield 2415), it then indicates the STA has no intent for the AP to enable preemption. Additionally, or alternatively, a Data subfield in the Preemption Intent subelement may include the preemption intent indication. It is to be appreciated that an existing reserved field in the Subelement ID subfield 2415 may be used to implement the indication for preemption intent, for example, when a value for the Subelement ID subfield 2415 is set to 220 - in this regard, reference is made to a table 2450 in FIG. 24 that tabulates a range of possible values that may be set in the Subelement ID subfield 2415.

[0147] It is to be appreciated that optionally, if a STA has indicated a preemption intent in the SCS Request frame, the AP may then poll for preemption intent during transmit opportunities (TXOPs), in accordance with the examples described with reference to FIGs. 22a, 22b.

[0148] FIG. 25 is a block diagram of a device 2505 for low latency (LL) communication, in accordance with aspects of the present disclosure. The device 2505 may be an example of aspects of the AP, and may implement the first communication apparatus configured to perform the method 200 of FIG. 2. The device 2505 may be an implementation of the communication apparatus 100 of FIG.1. The device 2505 may include a receiver 2510, an AP communications manager 2515, and a transmitter 2520. The AP communications manager 2515 can be implemented, at least in part, by one or both of a modem and a processor. Each of these components may be in communication with one another (e.g. via one or more buses).

[0149] The receiver 2510 may receive information such as packets, user data, or control information associated with various information channels (e.g. control channels, data channels, or the like). Information may be passed on to other components of the device 2505. Thereceiver 2510 may be an example of aspects of the radio receiver 104 described with reference to FIG. 1. The receiver 2510 may utilize a single antenna or a set of antennas (e.g. for MIMO communications).

[0150] The AP communications manager 2515 may receive an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus; may transmit, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; may receive, from the second communication apparatus, the LL data; and may process the received LL data.

[0151] The transmitter 2520 may transmit signals generated by other components of the device 2505. For example, the transmitter 2520 may be an example of aspects of the radio transmitter 102 described with reference to FIG. 1. The transmitter 2520 may utilize a single antenna or a set of antennas (e.g. for MIMO communications). In some examples, the transmitter 2520 may be collocated with the receiver 2510 in a transceiver component.

[0152] FIG. 26 is a block diagram of a device 2605 for low latency (LL) communication, in accordance with aspects of the present disclosure. The device 2605 may be an example of aspects of a device 2505, or an AP. The device 2605 may be an implementation of the communication apparatus 100 of FIG.1. The device 2605 may include a receiver 2610, an AP communications manager 2615, and a transmitter 2620. The AP communications manager 2615 can be implemented, at least in part, by one or both of a modem and a processor. Each of these components may be in communication with one another (e.g. via one or more buses).

[0153] The receiver 2610 may receive information such as packets, user data, or control information associated with various information channels (e.g. control channels, data channels, or the like). Information may be passed on to other components of the device 2605. The receiver 2610 may be an example of aspects of the radio receiver 104 described with reference to FIG. 1. The receiver 2610 may utilize a single antenna or a set of antennas (e.g. for MIMO communications).

[0154] The AP communications manager 2615 may include a receive component 2625, a preempt component 2630 (i.e. that may optionally be used in certain circumstances, and the component is depicted by dashed lines in FIG. 26 to indicate this optionality), a process component 2635, and a transmit component 2640.

[0155] The receive component 2625 may receive an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and may further receive, from the second communication apparatus, the LL data. In some examples, the receive component 2625 may be part of the receiver 2610.

[0156] The preempt component 2630 may, on the condition that there is an ongoing transmission at the AP, preempt, based on the received indication, the ongoing transmission, prior to receiving the LL data. Hence, the preempt component 2630 may not be activated in absence of ongoing transmission(s) at the AP, prior to receiving the LL data.

[0157] The transmit component 2640 may transmit, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data. In some examples, the transmit component 2640 may be part of the transmitter 2620.

[0158] The process component 2635 may process the received LL data.

[0159] The transmitter 2620 may transmit signals generated by other components of the device 2605. For example, the transmitter 2620 may be an example of aspects of the radio transmitter 102 described with reference to FIG. 1. The transmitter 2620 may utilize a single antenna or a set of antennas (e.g. for MIMO communications). In some examples, the transmitter 2620 may be collocated with the receiver 2610 in a transceiver component.

[0160] FIG. 27 is a block diagram of a communications manager 2705 for low latency (LL) communication, in accordance with aspects of the present disclosure. The communications manager 2705 may be an example of aspects of an AP communications manager 2515 (in FIG.25), or an AP communications manager 2615 (in FIG. 26) described herein. The communications manager 2705 may include a transmit component 2710, a receive component 2715, an optional preempt component 2720, and a process component 2725. Each of these components may communicate 2730, directly or indirectly, with one another (e.g. via one or more buses).

[0161] The transmit component 2710 may transmit, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data.

[0162] The receive component 2715 may receive an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and may further receive, from the second communication apparatus, the LL data.

[0163] The preempt component 2720 may, on the condition that there is an ongoing transmission at the AP, preempt, based on the received indication, the ongoing transmission, prior to receiving the LL data. So, the preempt component 2720 may not be activated in absence of ongoing transmission(s) at the AP, prior to receiving the LL data. The preempt component 2720 is depicted by dashed lines in FIG. 27 to indicate the optional operation of the preempt component 2720.

[0164] The process component 2725 may process the received LL data.

[0165] FIG. 28 is a block diagram of a device 2805 for low latency (LL) communication, in accordance with aspects of the present disclosure. The device 2805 may be an example of aspects of a STA, and may implement the second communication apparatus that performs the method 300 of FIG. 3. The device 2805 may be an implementation of the communication apparatus 100 of FIG.1. The device 2805 may include a receiver 2810, a STA communications manager 2815, and a transmitter 2820. The STA communications manager 2815 can be implemented, at least in part, by one or both of a modem and a processor. Each of these components may be in communication with one another (e.g. via one or more buses).

[0166] The receiver 2810 may receive information such as packets, user data, or control information associated with various information channels (e.g. control channels, data channels, or the like). Information may be passed on to other components of the device 2805. The receiver 2810 may be an example of aspects of the radio receiver 104 described with reference to FIG. 1. The receiver 2810 may utilize a single antenna or a set of antennas (e.g. for MIMO communications).

[0167] The STA communications manager 2815 may process by way of buffering LL data; may transmit an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; may receive, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data; and may transmit, to the first communication apparatus, the LL data.

[0168] The transmitter 2820 may transmit signals generated by other components of the device 2805. For example, the transmitter 2820 may be an example of aspects of the radio transmitter 102 described with reference to FIG. 1. The transmitter 2820 may utilize a single antenna or a set of antennas (e.g. for MIMO communications). In some examples, the transmitter 2820 may be collocated with the receiver 2810 in a transceiver component.

[0169] FIG. 29 is a block diagram of a device 2905 for low latency (LL) communication, in accordance with aspects of the present disclosure. The device 2905 may be an example of aspects of a device 2805, or a STA. The device 2905 may be an implementation of the communication apparatus 100 of FIG.1. The device 2905 may include a receiver 2910, a STA communications manager 2915, and a transmitter 2935. The STA communications manager 2915 can be implemented, at least in part, by one or both of a modem and a processor. Each of these components may be in communication with one another (e.g. via one or more buses).

[0170] The receiver 2910 may receive information such as packets, user data, or control information associated with various information channels (e.g. control channels, data channels, or the like). Information may be passed on to other components of the device 2905. The receiver 2910 may be an example of aspects of the radio receiver 104 described with reference to FIG. 1. The receiver 2910 may utilize a single antenna or a set of antennas (e.g. for MIMO communications).

[0171] The STA communications manager 2915 may include a transmit component 2920, a receive component 2925 and a buffer component 2930.

[0172] The buffer component 2930 may buffer LL data.

[0173] The transmit component 2920 may transmit an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted, and may further transmit, to the first communication apparatus, the LL data. In some examples, the transmit component 2920 may be part of the transmitter 2935.

[0174] The receive component 2925 may receive, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data. In some examples, the receive component 2925 may be part of the receiver 2910.

[0175] The transmitter 2935 may transmit signals generated by other components of the device 2905. For example, the transmitter 2935 may be an example of aspects of the radiotransmitter 102 described with reference to FIG. 1. The transmitter 2935 may utilize a single antenna or a set of antennas (e.g. for MIMO communications). In some examples, the transmitter 2935 may be collocated with the receiver 2910 in a transceiver component.

[0176] FIG. 30 is a block diagram of a communications manager 3005 for low latency (LL) communication, in accordance with aspects of the present disclosure. The communications manager 3005 may be an example of aspects of a STA communications manager 2815 (in FIG.28), or a STA communications manager 2915 (in FIG. 29) described herein. The communications manager 3005 may include a transmit component 3010, a receive component 3015, and a buffer component 3020. Each of these components may communicate 3025, directly or indirectly, with one another (e.g. via one or more buses).

[0177] The buffer component 3020 may buffer LL data.

[0178] The transmit component 3010 may transmit an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted, and may further transmit, to the first communication apparatus, the LL data.

[0179] The receive component 3015 may receive, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data.

[0180] All of the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods, if applicable, may be combined.

[0181] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0182] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general -purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0183] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0184] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0185] As used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (such as, A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on”.

[0186] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

[0187] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples”. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0188] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but to be accorded the broadest scope consistent with the principles and novel features disclosed herein.EXAMPLES

[0189] The following examples are disclosed, in accordance with aspects of the present disclosure.

[0190] Example 1: A first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: a receiver, which in operation, receives an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus, and receives the LL data from the second communication apparatus; a transmitter, which in operation, transmits, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; and circuitry, which in operation, processes the received LL data.

[0191] Example 2: The apparatus of example 1, wherein a transmission is ongoing at the first communication apparatus, and the circuitry, which in operation, preempts, based on the received indication, the ongoing transmission, prior to receiving the LL data.

[0192] Example 3: The apparatus of example 1, wherein the indication is received via a BlockAck (BA) frame.

[0193] Example 4: The apparatus of example 1, wherein the indication is configured with a value of 0 or 1, in which the value of 0 indicates unavailability of LL data to be transmitted, and the value of 1 indicates availability of LL data to be transmitted.

[0194] Example 5: The apparatus of example 1, wherein the indication is received, in response to a multi-user (MU) physical layer protocol data unit (PPDU) transmitted by the first communication apparatus.

[0195] Example 6: The apparatus of example 1, wherein: the transmitter, which in operation, further transmits, to the second communication apparatus, a second Trigger frame to request information about the LL data, prior to transmitting the first Trigger frame, wherein the second Trigger frame is a buffer status report poll (BSRP) Trigger frame.

[0196] Example 7: The apparatus of example 1, wherein the first Trigger frame is transmitted, based in part on a data urgency level of the LL data communicated by the second communication apparatus.

[0197] Example 8: The apparatus of example 7, wherein the data urgency level is communicated via an access category index (ACI) bitmap.

[0198] Example 9: The apparatus of example 7, wherein: the circuitry, which in operation, determines, based on the data urgency level, a size of a resource unit (RU) to be allocated to the second communication apparatus to enable transmission of the LL data.

[0199] Example 10: The apparatus of example 1, wherein the second communication apparatus is included in a plurality of communication apparatuses in communication with the first communication apparatus.

[0200] Example 11: The apparatus of example 1, wherein: the transmitter, which in operation, further transmits, to the second communication apparatus, a polling frame to request information on a preemption intent of the second communication apparatus, which indicates whether the second communication apparatus has intent for the first communication apparatus to enable preemption, wherein the polling frame is transmitted prior to receiving, from the second communication apparatus, the indication about the LL data to be transmitted to the first communication apparatus; and the receiver, which in operation, receives, from the second communication apparatus, a response to the polling frame indicating the preemption intent.

[0201] Example 12: The apparatus of example 11, wherein the polling frame is one of: a buffer status report poll (BSRP) Trigger frame, and a Null data packet (NDP) feedback report poll (NFRP) Trigger frame.

[0202] Example 13: The apparatus of example 11, wherein the preemption intent is indicated via a Multi-STA BlockAck (M-BA) frame, or a stream classification service (SCS) Request frame.

[0203] Example 14: The apparatus of example 11, wherein the polling frame is an add block acknowledgment (ADDBA) Request frame, and the preemption intent is indicated via an ADDBA Response frame.

[0204] Example 15: The apparatus of example 1, wherein the receiver, which in operation, receives, from the second communication apparatus, an add block ack (ADDBA) Request frame configured to indicate a preemption intent.

[0205] Example 16: The apparatus of example 1, wherein the first communication apparatus is an access point (AP), and the second communication apparatus is a station (STA) configured to communicate with the AP.

[0206] Example 17: A method at a first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: receiving an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus; transmitting, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; receiving, from the second communication apparatus, the LL data; and processing the received LL data.

[0207] Example 18: A first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: means for receiving an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus; means for transmitting, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; means for receiving, from the second communication apparatus, the LL data; and means for processing the received LL data.

[0208] Example 19: A first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising: memory circuitry arranged to store executable code; and processor circuitry coupled to the memory circuitry, and arranged to execute the code to cause the apparatus to: receive an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus; transmit, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data; receive, from the second communication apparatus, the LL data; and process the received LL data.

[0209] Example 20: A non-transitory computer readable medium comprising executable instructions, which when executed by a processor of the first communication apparatus of any of examples 1-16, cause the apparatus to perform the method of example 17.

[0210] Example 21: A second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: circuitry, which in operation, buffers LL data; a transmitter, which in operation, transmits, an indication, to thefirst communication apparatus, that the second communication apparatus has the LL data to be transmitted, and transmits, to the first communication apparatus, the LL data; and a receiver, which in operation, receives, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data.

[0211] Example 22: A method at a second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: buffering LL data; transmitting an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; receiving, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data; and transmitting, to the first communication apparatus, the LL data.

[0212] Example 23: The method of example 22, further comprising: transmitting, to the first communication apparatus, a buffer status report (BSR) configured to include information about the LL data.

[0213] Example 24: The method of example 22, wherein the second communication apparatus is included in a plurality of communication apparatuses in communication with the first communication apparatus, and LL data of respective communication apparatuses are transmitted, to the first communication apparatus, via respective subcarriers in a same orthogonal frequency division multiplexing (OFDM) symbol.

[0214] Example 25 : The method of example 22, wherein the first communication apparatus is an access point (AP), and the second communication apparatus is a station (STA) configured to communicate with the AP.

[0215] Example 26: A second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: means for buffering LL data; means for transmitting an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; means for receiving, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data; and means for transmitting, to the first communication apparatus, the LL data.

[0216] Example 27: A second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising: memory circuitry arranged to store executable code; and processor circuitry coupled to the memory circuitry, and arranged to execute the code to cause the apparatus to: buffer LL data; transmit an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; receive, from the first communication apparatus based on the transmitted indication, a first Trigger frame configured to enable transmission of the LL data; and transmit, to the first communication apparatus, the LL data.

[0217] Example 28: A non-transitory computer readable medium comprising executable instructions, which when executed by a processor of the second communication apparatus of example 21, cause the apparatus to perform the method of any of examples 22-25.REFERENCES[1] IEEE 802.1 l-24 / 0389r0, Preemption for Low Latency[2] IEEE 802.11-24 / 103r0, TXOP Level Preemption for Low Latency Application [3] IEEE 802.1 l-24 / 1074r0, Preemption TXOP[4] IEEE 802.1 l-24 / 0866r0, Preemption for C-TDMA[5] IEEE 802.11 -23 / 1229r 1 , Preemption for low latency application follow up [6] IEEE 802.11-24 / 0168r0, TXOP preemption in 1 Ibn[7] IEEE 802.11 -23 / 1886r3, Preemption techniques to meet low-latency (LL) targets [8] IEEE 802.1 l-23 / 0092r0, Preemption for Low Latency Application[9] IEEE 802.1 l-25 / 0014rl3, tgbn-motions-list-part-2

[0010] IEEE 802.1 l-25 / 421r0, Low Latency Indication

[0011] IEEE 802.1 l-25 / 0430rl, Improving Acknowledgement Mechanisms

[0012] IEEE 802.1 l-25 / 0448r2, PDT for Low Latency Indication

Claims

CLAIMS1. A first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising:a transmitter, which in operation, transmits MU PPDU; anda receiver, which in operation, in response to the transmission of the MU PPDU, receives an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus.

2. The apparatus of claim 1, wherein the transmitter, which in operation, transmits, to the second communication apparatus based on the received indication, a first Trigger frame configured to enable transmission of the LL data.

3. The apparatus of claim 1, wherein a transmission is ongoing at the first communication apparatus, and the circuitry, which in operation, preempts, based on the received indication, the ongoing transmission, prior to receiving the LL data.

4. The apparatus of claim 1, wherein the indication is received via a BlockAck (BA) frame.

5. The apparatus of claim 1, wherein the indication is configured with a value of 0 or 1, in which the value of 0 indicates unavailability of LL data to be transmitted, and the value of 1 indicates availability of LL data to be transmitted.

6. The apparatus of claim 1, wherein the indication is received, in response to a multi-user (MU) physical layer protocol data unit (PPDU) transmitted by the first communication apparatus.

7. The apparatus of claim 1, wherein:the transmitter, which in operation, further transmits, to the second communication apparatus, a second Trigger frame to request information about the LL data, prior to transmitting the first Trigger frame,wherein the second Trigger frame is a buffer status report poll (BSRP) Trigger frame.

8. The apparatus of claim 1, wherein the first Trigger frame is transmitted, based in part on a data urgency level of the LL data communicated by the second communication apparatus.

9. The apparatus of claim 8, wherein:the circuitry, which in operation, determines, based on the data urgency level, a size of a resource unit (RU) to be allocated to the second communication apparatus to enable transmission of the LL data.

10. The apparatus of claim 2, wherein:the transmitter, which in operation, further transmits, to the second communication apparatus, a polling frame to request information on a preemption intent of the second communication apparatus, which indicates whether the second communication apparatus has intent for the first communication apparatus to enable preemption,wherein the polling frame is transmitted prior to receiving, from the second communication apparatus, the indication about the LL data to be transmitted to the first communication apparatus; andthe receiver, which in operation, receives, from the second communication apparatus, a response to the polling frame indicating the preemption intent.

11. The apparatus of claim 10, wherein the polling frame is one of: a buffer status report poll (BSRP) Trigger frame, and a Null data packet (NDP) feedback report poll (NFRP) Trigger frame.

12. The apparatus of claim 10, wherein the preemption intent is indicated via a Multi-STA BlockAck (M-BA) frame, or a stream classification service (SCS) Request frame.

13. The apparatus of claim 10, wherein the polling frame is an add block acknowledgment (ADDBA) Request frame, and the preemption intent is indicated via an ADDBA Response frame.

14. The apparatus of claim 1, wherein the receiver, which in operation, receives, from the second communication apparatus, an add block acknowledgment (ADDBA) Request frame configured to indicate a preemption intent.

15. The apparatus of claim 1, wherein the first communication apparatus is an access point (AP), and the second communication apparatus is a station (STA) configured to communicate with the AP.

16. A method at a first communication apparatus for low latency (LL) communication with a second communication apparatus, comprising:transmitting MU PPDU; andreceiving, in response to the transmission of the MU PPDU, an indication that the second communication apparatus has LL data buffered thereat to be transmitted to the first communication apparatus.

17. A second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising:circuitry, which in operation, buffers LL data;a transmitter, which in operation, transmits, an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted, and transmits, to the first communication apparatus, the LL data.

18. A method at a second communication apparatus for low latency (LL) communication with a first communication apparatus, comprising:buffering LL data;transmitting an indication, to the first communication apparatus, that the second communication apparatus has the LL data to be transmitted; andtransmitting, to the first communication apparatus, the LL data.

19. The method of claim 18, further comprising:transmitting, to the first communication apparatus, a buffer status report (BSR) configured to include information about the LL data.

20. The method of claim 18, wherein the first communication apparatus is an access point (AP), and the second communication apparatus is a station (STA) configured to communicate with the AP.