WO2024254790A1

WO2024254790A1 - Configuration information for determining whether to preempt

Info

Publication number: WO2024254790A1
Application number: PCT/CN2023/100247
Authority: WO
Inventors: Jian Guo Liu; Zhi Jie Yang; Orhan Okan MUTGAN; Fei Gao
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Priority date: 2023-06-14
Filing date: 2023-06-14
Publication date: 2024-12-19
Anticipated expiration: 2025-12-14
Also published as: CN121549043A; EP4728807A1

Abstract

Embodiments of the present disclosure relate to a proactive grant for preemption. In an aspect, a first device determines configuration information for a transmission opportunity (TXOP) initiated by the first device. The configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP. The first device transmits the configuration information to the second device within the TXOP. In this way, low latency data frame transmission can be improved by preempting a TXOP under a preemption grant.

Description

CONFIGURATION INFORMATION FOR DETERMINING WHETHER TO PREEMPT

FIELD

Various example embodiments relate to the field of communications and in particular, to devices, methods, apparatuses, and a computer readable medium relating to configuration information for determining whether to preempt.

BACKGROUND

Recently, the institute of electrical and electronic engineers (IEEE) 802.11 Working Group has formed a new Study Group (SG) to define a project for new physical (PHY) and media access control (MAC) technologies to further increase the reliability and throughput of 802.11 wireless local area networks (WLANs) . Latency improvement is one of the main requirements in the ultra-high reliability (UHR) Group as described in the approved motion for UHR SG formation and in the project authorization request (PAR) .

Several new features are developed to support low latency data frame transmission. These features include multi-link operation (MLO) , restricted target wake time (R-TWT) and the MLO stream classification service (MSCS) based quality of service (QoS) signaling mechanism. Combining R-TWT with the MSCS based QoS signaling on 802.11be device can achieve a bounded latency of less than 25ms. However, it still can’t meet the requirements of the industrial applications that require latencies of less than tens of milliseconds to a few milliseconds. To schedule a low latency data frame transmission, preemption solutions are under discussion.

SUMMARY

In general, example embodiments of the present disclosure provide a solution related to a proactive grant for preemption.

In a first aspect, there is provided a first device. The first device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first device at least to: determine configuration information for a transmission opportunity (TXOP) initiated by the first device, wherein the configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP; and transmit the configuration information to the second device within the TXOP.

In a second aspect, there is provided a second device. The second device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second device at least to: receive, from a first device, configuration information for a TXOP initiated by the first device; determine, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and dependent on determining to preempt the TXOP for the data frame transmission, transmit or receive the data frame transmission within the TXOP.

In a third aspect, there is provided a method. The method comprises: determining, at a first device, configuration information for a TXOP initiated by the first device, wherein the configuration information is to be used for determining whether a second device is allowed to preempt the TXOP; and transmitting the configuration information to the second device within the TXOP.

In a fourth aspect, there is provided a method. The method comprises: receiving, at a second device and from a first device, configuration information for a TXOP initiated by the first device; determining, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and dependent on determining to preempt the TXOP for the data frame transmission, transmitting or receiving the data frame transmission within the TXOP.

In a fifth aspect, there is provided an apparatus. The apparatus comprises means for determining, at a first device, configuration information for a TXOP initiated by the first device, wherein the configuration information is to be used for determining whether a second device is allowed to preempt the TXOP; and means for transmitting the configuration information to the second device within the TXOP.

In a sixth aspect, there is provided an apparatus. The apparatus comprises means for receiving, at a second device and from a first device, configuration information for a TXOP initiated by the first device; means for determining, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and means for dependent on determining to preempt the TXOP for the data frame transmission, transmitting or receiving the data frame transmission within the TXOP.

In a seventh aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above third to fourth aspects.

In an eighth aspect, there is provided a computer program product comprising program instructions for performing at least the method according to any one of the above third to fourth aspects.

In a ninth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform at least the method according to any one of the above third to fourth aspects.

In an tenth aspect, there is provided a first device. The first device comprises: determining circuitry configured to determine configuration information for a TXOP initiated by the first device, wherein the configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP; and transmitting circuitry configured to transmit the configuration information to the second device within the TXOP.

In an eleventh aspect, there is provided a second device. The second device comprises: receiving circuitry configured to receive, from a first device, configuration information for a TXOP initiated by the first device; determining circuitry configured to determine, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and transmitting circuitry configured to, dependent on determining to preempt the TXOP for the data frame transmission, transmit the data frame transmission within the TXOP, or receiving circuitry configured to, dependent on determining to preempt the TXOP for the data frame transmission, receive the data frame transmission within the TXOP.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Some example embodiments will now be described with reference to the accompanying drawings, in which:

Fig. 1A illustrates an example communication system in which embodiments of the present disclosure may be implemented;

Fig. 1B illustrates a schematic diagram illustrating a preemption case for a low latency data frame transmission;

Fig. 1C illustrates a schematic diagram illustrating a delay issue that may be caused in a preemption case for a low latency data frame transmission;

Fig. 2 illustrates an example signaling chart of an example process according to some embodiments of the present disclosure;

Fig. 3 illustrates an example signaling chart of an exemplary proactive preemption grant process according to some embodiments of the present disclosure;

Fig. 4 illustrates a schematic diagram illustrating a preemption grant configuration according to some embodiments of the present disclosure;

Fig. 5 illustrates a schematic diagram illustrating another preemption grant configuration according to some embodiments of the present disclosure;

Fig. 6 illustrates a schematic diagram illustrating a further preemption grant configuration according to some embodiments of the present disclosure;

Fig. 7 illustrates a schematic diagram illustrating a still further preemption grant configuration according to some embodiments of the present disclosure;

Fig. 8 illustrates a schematic diagram illustrating a method implemented at a first device according to some other embodiments of the present disclosure;

Fig. 9 illustrates a schematic diagram illustrating a method implemented at a second device according to some other embodiments of the present disclosure;

Fig. 10 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure; and

Fig. 11 illustrates a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. As used herein, “at least one of the following: <a list of two or more elements> ” and “at least one of <a list of two or more elements> ” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as WLAN, Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the future sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future, wireless local network communication protocols such as IEEE 802.11 and the like and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to an access point (AP) or a base station (BS) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology. In the following description, the terms “network device” , “network (NW) , ” “AP” may be used interchangeably.

The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a station (STA) , a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” , “UE” and “STA” may be used interchangeably.

As used herein, the term “AP device” may refer to a device via which to access any wired or wireless network. For example, the wired or wireless network may be a broadband network, the Internet, a local area network, a metropolitan area network, a mobile communication network, or the like. For convenience, AP devices are also referred to as AP stations or APs herein. The AP device may support, for example, the Wi-Fi protocol or any other known or future-developed similar protocols. For example, the AP device may be a wireless router, a terminal device with a router function, a network device with a router function, and so on.

As used herein, the term “TXOP holder” may refer to a device that initiates a TXOP to communicate with other device (s) within the TXOP. For example, the device may sense a channel and get the TXOP in a listen before talk (LBT) procedure. The TXOP holder can be also referred to as an initiating device. As used herein, the term “non-TXOP holder” may refer to a device that communicates with a TXOP holder or other device (s) within a TXOP initiated by the TXOP holder. The non-TXOP holder can be also referred to as a responding device.

Although functionalities described herein can be performed, in various example embodiments, in a fixed and/or a wireless network node, in other example embodiments, functionalities may be implemented in a user equipment apparatus (such as a cell phone or tablet computer or laptop computer or desktop computer or mobile IoT device or fixed IoT device) . This user equipment apparatus can, for example, be furnished with corresponding capabilities as described in connection with the fixed and/or the wireless network node (s) , as appropriate. The user equipment apparatus may be the user equipment and/or a control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functionalities include the bootstrapping server function and/or the home subscriber server, which may be implemented in the user equipment apparatus by providing the user equipment apparatus with software configured to cause the user equipment apparatus to perform from the point of view of these functions/nodes.

Principles and implementations of the present disclosure will be described in detail below with reference to the figures. Fig. 1A illustrates an example communication system 100 in which embodiments of the present disclosure may be implemented. The system 100 includes an STA 110 and an AP 120. The system 100 may also include an STA 130. In some embodiments, the STA 110 may initiate a TXOP to communicate with the AP 120. In this case, the STA 110 is the TXOP holder and the AP 120 is the non-TXOP holder. Alternatively, the AP 120 may be the TXOP holder and the STA 110 may be the non-TXOP holder.

It is to be understood that the number of AP and STA and their connections are only for the purpose of illustration without suggesting any limitations. The system 100 may include any suitable number of AP and STA adapted for implementing embodiments of the present disclosure.

Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, wireless local network communication protocols such as IEEE 802.11 and the like, cellular communication protocols, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.

To schedule a low latency data frame transmission, preemption solutions are under discussion. One possible case is to preempt the ongoing transmission or TXOP by the non-TXOP holder, i.e., in case of low latency data frame buffered at a non-TXOP holder, the low latency data frame can be transmitted before the current TXOP is end.

Fig. 1B illustrates a schematic diagram 150 illustrating a preemption case for a low latency data frame transmission. As illustrated in Fig. 1B, the non-TXOP holder (i.e., AP) can transmit a low latency data frame to another device (i.e., STA2) by preempting current TXOP initiated by the TXOP holder (i.e., STA1) .

For example, as shown in Fig. 1B, STA1 as a TXOP holder may transmit a request to send (RTS) frame 151 to AP and the AP may transmit a clear to send (CTS) frame 152 to the STA1 as a response. Then STA1 may transmit non-low latency data 153 to the AP. Low latency data for STA2 may arrive at time A at the AP STA1 while the STA1 is transmitting the non-low latency data 153 to the AP. To transmit the low latency data frame to STA2, the AP may need to preempt the TXOP initiated by the STA1. The AP may terminate the transmission of the non-low latency data by transmitting a block acknowledgment (BA) frame 154 to the STA1. Then, the AP may transmit the low latency data 155 to the STA2 within the STA1’s TXOP. The STA2 may transmit a BA frame 156 to the AP upon reception of the low latency data. The STA1 may continue transmission of the non-low latency data 157 to the AP in remaining time of the STA1’s TXOP.

For this case, the AP needs to schedule a low-latency data frame transmission by preempting the ongoing transmission or preempting the TXOP initiated by a STA. For the preemption operation, an open issue is that the STA may also buffer low-latency data frames for transmission within its TXOP, and the TXOP preemption proposal will be unfair and unfriendly to the STA.

Fig. 1C which illustrates a schematic diagram 180 illustrating a delay issue that may be caused in a preemption case for a low latency data frame transmission. As illustrated in Fig. 1C, when the STA1 is transmitting data frame to the AP within its TXOP, low-latency data frames are buffered at both the AP and the STA1. If the AP interrupts the ongoing transmission from STA1 and schedules the low latency data frame transmission 155 to the STA2 using the STA1’s TXOP, and results in that the STA1 cannot transmit the low-latency data frame 158 to the AP in time, which would cause a higher delay issue for the low-latency data frame transmission for STA1.

Another open issue is that the AP may be not allowed to preempt the TXOP initiated by other device for low-latency data frame transmission. As an example, according to European Telecommunication Standards Institute (ETSI) regulation rule that Responding Device Channel Access Mechanism in 5GHz unlicensed band shown below, a Responding Device may perform transmissions on the current operating channel for the remaining Channel Occupancy Time (i.e., TXOP) after it received a transmission grant from an associated initiating device (i.e., TXOP holder) . That means that the AP shall receive a transmission grant from the STA for the preemption operation so that it can schedule a low latency data frame transmission within the TXOP initiated by the STA.

Table 1: Responding Device Channel Access Mechanism

In view of the above and other aspects, embodiments of the present disclosure provide a proactive grant solution for preemption operation within a TXOP. In the solution, a first device as a TXOP holder determines a configuration information for a TXOP initiated by the first device. The configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP. Then, the first device transmits the configuration information to the second device within the TXOP. The second device determines, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission. Dependent on determining to preempt the TXOP for the data frame transmission, the second device transmits or receives the data frame transmission within the TXOP. In this way, low latency data frame transmission can be improved by preempting a TXOP under a preemption grant from the TXOP holder. Thus, the TXOP holder can determine whether the preemption operation is allowed considering certain conditions, e.g., data frame type/QoS (i.e., latency or priority) of itself.

Fig. 2 illustrates an example signaling chart illustrating an example process 200 according to some embodiments of the present disclosure. The process 200 may involve a first device 201 and a second device 202. The first device 201 may be a TXOP holder, e.g., one of the STA 110 or the AP 120 as shown in Fig. 1A. The second device 202 may be a non-TXOP holder, e.g., the other one of the AP 120 or the STA 110 as shown in Fig. 1A.

As shown in Fig. 2, the second device 202 as a non-TXOP holder may transmit 210 an indication 211 to the first device 201 as a TXOP holder. The indication 211 may be used for configuring the first device 201 to support a proactive grant for preempting a TXOP initiated by the first device 201. The first device 201 may receive the indication 211.

With reference to Fig. 2, the first device 201 determines 213 configuration information for a TXOP initiated by the first device 201. The configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP. Then, the first device 201 transmits 214 the configuration information 215 to the second device 202 within the TXOP.

Upon receiving 216 the configuration information 215, the second device 202 determines 217 whether to preempt the TXOP for a data frame transmission dependent on the configuration information. If the second device 202 determines to preempt the TXOP for the data frame transmission, the second device 202 transmits or receives the data frame transmission within the TXOP.

In some embodiments, the first device 201 may determine the configuration information dependent on at least one of a QoS status and priority of at least one buffered data frame at the first device 201. For example, if a low latency data frame is to be transmitted by the first device 201 within the TXOP, the first device 201 may determine the configuration information to indicate that the second device 202 is not allowed to preempt the TXOP. If no low latency data frame is to be transmitted by the first device within the TXOP, the first device 201 may determine the configuration information to indicate that the second device 202 is allowed to preempt the TXOP.

The first device 201 may transmit the configuration information via a field in an existing frame. For example, the configuration information can be carried in a header of one or more PPDU frame with the TXOP. Alternatively or in addition, the first device 201 may transmit the configuration information via a frame designed for transmitting the configuration information.

If the configuration information indicates that the second device 202 is allowed to preempt the TXOP, the second device 202 may further determine whether to preempt the TXOP. For example, if a priority of the data frame transmission is higher than the priority threshold, the second device 202 may determine to preempt the TXOP. If the priority is lower than or equal to the priority threshold, the second device 202 may determine not to preempt the TXOP. In some embodiments, if a latency of the data frame transmission is longer than the latency threshold, the second device 202 may determine to preempt the TXOP. If the latency is shorter than or equal to the latency threshold, the second device 202 may determine not to preempt the TXOP.

In the case that a low latency data frame arrives at the first device 201 within the TXOP, e.g., after the transmission of the configuration information, the first device 201 may transmit other configuration information (e.g., second configuration information) to the second device 202 to indicate that the second device 202 is not allowed to preempt the TXOP. The second device 202 may determine whether to preempt the TXOP dependent on the latest configuration information.

The configuration information (as well as the second configuration information) may comprise an indication of whether the second device 202 is allowed to preempt the TXOP. Alternatively or in addition, the configuration information may comprise a priority threshold for the second device to determine whether to preempt the TXOP. Alternatively or in addition, the configuration information may comprise a latency threshold for the second device to determine whether to preempt the TXOP. Alternatively or in addition, the configuration information may comprise one or more device identifiers (IDs) of devices that are allowed to preempt the TXOP. In some embodiments, the first device 201 may broadcast the configuration information to the one or more devices.

In some embodiments, the configuration information may indicate a preemption occasion for starting preemption within the TXOP. Alternatively or in addition, the preemption occasion is pre-configured or pre-defined. In some embodiments, the preemption occasion may be within a time window. The time window may comprise an inter frame space (IFS) . In some embodiments, the preemption occasion may be after a PPDU frame transmission. Alternatively or in addition, the preemption occasion may be after a BA frame transmission. In some embodiments, the preemption occasion may allow the second device 202 to terminate the PPDU frame transmission within the TXOP.

If the second device 202 determines to preempt the TXOP for the data frame transmission, it may transmit the data frame transmission to the first device 201 or a third device starting from the preemption occasion. Alternatively or in addition, the second device 202 may transmit a trigger to the third device for the data frame transmission starting from the preemption occasion and receive the data frame transmission from the third device.

On the first device 201 side, the first device 201 may monitor whether there is a frame transmission from the second device 202 starting from the preemption occasion. If the frame transmission is detected, the first device 201 may terminate an ongoing transmission within the TXOP. If it fails to detect the frame transmission, the first device 201 may continue the ongoing transmission within the TXOP after the preemption occasion.

To monitor whether there is a frame transmission from the second device 202 starting from the preemption occasion, the first device 201 may perform energy detection (ED) . For example, the first device 201 may detect energy within the preemption occasion, and compare the detected energy with a threshold. If the detected energy level is lower than the ED threshold, the channel is considered idle and thus data transmission is allowed for the first device 201. Alternatively or in addition, the first device 201 may perform signal detection within the preemption occasion. For example, the first device 201 may detect preamble or/and MAC header to detect whether a data transmission is performed by the second device 202.

In some embodiments, the preemption occasion may be not applied. For example, the configuration information may do not indicate a preemption occasion, and the preemption occasion may be not pre-configured or pre-defined. In this case, if the second device 202 determines to preempt the TXOP, the second device 202 may transmit an indication for early terminating an ongoing transmission within the TXOP to the first device 201. Then, the second device 202 can transmit the data frame transmission within the TXOP to the first device 201 or a third device, or receive the data frame transmission within the TXOP from the third device. The indication may be transmitted via, e.g., a BA frame or a new frame. Upon receiving the indication for early terminating an ongoing transmission within the TXOP, the first device 201 can terminate the ongoing transmission within the TXOP.

With the process 200, a proactive grant solution for preemption operations within a TXOP is provided. In the solution, the TXOP holder can determine whether the preemption operation is allowed considering certain conditions. Low latency data frame transmission can be improved by preempting a TXOP under a preemption grant from the TXOP holder. It is to be noted that the above process 200 is merely an example, and may have additional or less operations. It is also to be noted that operations of the above process 200 may be carried out separately or in any suitable combination.

Fig. 3 illustrates an example signaling chart of an exemplary proactive preemption grant process 300 according to some embodiments of the present disclosure. The process 300 can be an example of the process 200 as shown in Fig. 2. The process 300 may involve the first device 201 and the second device 202 as shown in Fig. 2 and a third device 203. The third device 203 may be a STA that communicates with at least one of the first device 201 and the second device 202.

In process 300, the TXOP holder (e.g., the first device 201) can proactively determine whether to provide a preemption grant to a non-TXOP holder (e.g., the second device 202) . Only if the non-TXOP holder obtains the preemption grant from the TXOP holder, it will be allowed to preempt the current TXOP and schedule a buffered low latency frame transmission within the remaining TXOP.

As shown in Fig. 3, at 310, the first device 201 as a TXOP holder can be set or/pre-configured by the second device 202 as a non-TXOP holder to support the proactive grant feature on preemption operation. At 311, after the first device 201 initiates a TXOP, it can determine whether it’s allowed the second device 202 to preempt the current TXOP. The determination can be made at least based on a QoS status or priority of the buffered data frame locally.

In an embodiment, if the first device 201 needs to transmit low-latency traffic within the TXOP, it doesn’t allow the second device 202 to preempt the current TXOP; otherwise, it allows the second device 202 to preempt the current TXOP. In another embodiment, the first device 201 allows the second device 202 to preempt the current TXOP based on the configured priority threshold, e.g., if the priority of low latency data frame buffered at the second device 202 is higher than a configured priority threshold (which can be determined based on one of the buffered data frames with highest priority) , the first device 201 allows the second device 202 to preempt the current TXOP; otherwise, the second device 202 will not be allowed to preempt the current TXOP.

In a further embodiment, the first device 201 allows the second device 202 to preempt the current TXOP based on the configured latency threshold, e.g., if the maximum latency boundary at the second device 202 is higher than a configured latency threshold, the first device 201 allows the second device 202 to preempt the current TXOP; otherwise, the second device 202 will not be allowed to preempt the current TXOP.

At 312, the first device 201 transmits a preemption grant configuration to the second device 202 via a frame within the TXOP. The preemption grant configuration can include a preemption allowed indication, which is to indicate whether the second device 202 is allowed to preempt the current TXOP for low latency data frame transmission. Alternatively or in addition, the preemption grant configuration can include the priority and/or latency threshold; if presented, the first device 201 grants the second device 202 to preempt the current TXOP conditionally at least based on the priority/latency threshold. Alternatively or in addition, the preemption grant configuration can include a preemption occasion.

The first device 201 may indicate a preemption occasion that allow the preemption occurred after the current PPDU frame exchange, e.g., after PPDU or BA frame transmission, or allow to terminal the current PPDU frame exchange. The preemption occasion can be an xIFS, such as a Short Inter Frame Space (SIFS) , a Point Coordination Function (PCF) Interframe Space (PIFS) , a Distributed Coordination Function (DCF) Interframe Space (DIFS) , an Extended Interframe Space (EIFS) , etc. Alternatively or in addition, the preemption grant configuration can include one or more device IDs of devices that are allowed to preempt the TXOP. The preemption grant configuration can be transmitted through a new frame, or a field carried in a frame (e.g., a PHY header of a PPDU frame) , details will be elaborated with reference to Figs. 4-7 later.

Continuing to refer to Fig. 3, at 313, if there is a low latency data frame buffered, the second device 202 determines whether to preempt the current TXOP for the low latency data frame transmission based on the preemption grant configuration set by current TXOP holder.

In an embodiment, the second device 202 can preempt the current TXOP if at least one of the following conditions is met: the preemption grant configuration indicates the second device 202 can preempt the current TXOP; and/or the priority and/or latency of low latency frame buffered at the second device 202 meet the priority and/or latency threshold if configured by the first device 201. The second device 202 would make the decision based on the latest received preemption grant configuration.

As shown in Fig. 3, there are two cases about how to preempt the TXOP for transmitting the low latency data frame transmission. In case 1, a preemption occasion is presented in the preemption configuration or pre-configured/pre-defined. At 314, under the precondition that the second device 202 meet the preemption condition mentioned above, once the first device 201 finishes a PPDU frame exchange, e.g., receive a BA frame for the PPDU receiver, the second device 202 schedules the low latency data frame transmission within the remaining TXOP to the first device 201 or the third device 203 based on indicative of the preemption occasion. In an embodiment, the second device 202 preempts the ongoing transmissions during an xIFS time after receiving a PPDU frame from the first device 201 or transmitting a BA frame to the first device 201.

At 315, if the first device 201 monitors a frame transmission from the second device 202 starting from the preemption occasion, it terminates ongoing transmission within the TXOP; otherwise, it continues the ongoing transmission (s) within the TXOP after the preemption occasion.

In case 2, a preemption occasion isn’t presented in the preemption grant configuration or pre-configured/pre-defined. At 316, if the second device 202 is allowed to preempt and finishes reception of a PPDU frame from the first device 201, the second device 202 sends an early termination indication to the first device 201 through a frame.

In an embodiment, the indication can be signaled through a BA frame or be signaled through an action/control frame in another link for the case of multiple link operation. At 317, upon receiving the early termination indication, the first device 201 terminates ongoing transmission within the TXOP. At 318, the second device 202 schedules the low latency data frame transmission within the remaining TXOP to the first device 201 or the third device 203.

With the process 300, the TXOP holder can determine whether the preemption operation is allowed considering certain conditions. Low latency data frame transmission can be improved by preempting a TXOP under a preemption grant from the TXOP holder. It is to be noted that the above process 300 is merely an example, and may have additional or less operations. It is also to be noted that operations of the above process 500 may be carried out separately or in any suitable combination.

Some examples for the preemption operation will be described in details with reference to Figs. 4-7 below. Fig. 4 illustrates a schematic diagram 400 illustrating a preemption grant configuration according to some embodiments of the present disclosure. In Fig. 4, STA1 (e.g., the first device 201 as shown in Figs. 2 and 3) is the TXOP holder, AP (e.g., the second device as shown in Figs. 2 and 3) and STA2 (e.g., the third device as shown in Fig. 3) are non-TXOP holders.

As shown in Fig. 4, STA1 initiates a TXOP for communication with AP. STA1 may transmit an RTS frame 401 to AP and the AP may transmit a CTS frame 402 to STA1 as a response. After STA1 initiates the TXOP, it can determine the preemption grant configuration based on QoS (e.g., priority) of buffered data frames. If there is not low latency data buffered at STA1, it may indicate in the preemption grant configuration through the header of PPDU frame 403 that the current TXOP is allowed to be preempted for low latency data frame transmission.

When the low latency data frame for STA2 arrives at time A at AP, it can transmit an early termination indication to STA1 through the BA frame 404 after STA1 finishes a PPDU frame transmission. After that, STA1 may terminate the ongoing transmission and AP can schedule low latency frame transmission 405 within the remaining TXOP for STA2. After AP finishes the low latency frame transmission 405, STA2 can transmit a BA frame 406 to AP.

Fig. 5 illustrates a schematic diagram 500 illustrating another preemption grant configuration according to some embodiments of the present disclosure. In Fig. 5, similarly, STA1 (e.g., the first device 201 as shown in Figs. 2 and 3) is the TXOP holder, AP (e.g., the second device as shown in Figs. 2 and 3) and STA2 (e.g., the third device as shown in Fig. 3) are non-TXOP holders.

As shown in Fig. 5, after RTS frame 501 to AP and CTS frame 502, multiple PPDU frames 503, 505 and 507 can be transmitted within a TXOP, and a preemption grant configuration can be carried in a header of per PPDU. Ba frames 504, 506 and 508 are responses to PPDU frames 503, 505 and 507, respectively. Based on the data frame buffered at STA1, STA1 can update the preemption configuration frame by frame.

As an example, the preemption grant configuration carried in PPDU#1 may indicate that the current TXOP can be preempted. However, as the low latency data frame arrives at time A during transmission of PPDU#1, the preemption grant configuration carried in PPDU#2/3 will indicate that the current TXOP can’t be preempted. Therefore, AP can’t transmit an early termination indication to STA1 after STA1 finishes transmission of PPDU#2 even if the low latency data for STA2 arrives at AP.

Fig. 6 illustrates a schematic diagram 600 illustrating a further preemption grant configuration according to some embodiments of the present disclosure. In this embodiment, assuming that a preemption occasion is indicated through the preemption configuration or (pre-) configured/defined, which is an xIFS after the PPDU frame transmission from the TXOP holder (e.g., STA1) . If the low latency data frame is buffered at AP, AP can preempt the TXOP for low latency data frame transmission starting from the PPDU.

In Fig. 6, STA1 initiates a TXOP to transmit data to the AP. STA1 may transmit an RTS frame 601 to AP and the AP may transmit a CTS frame 602 to STA1 as a response. As there is no low latency data buffered at the STA1, it can transmit a preemption configuration through the header of the PPDU frame 603 which indicates the AP allow to preempt its TXOP and transmit low latency data 605 during an xIFS time 604 following the PPDU transmission.

As illustrated in Fig. 6 (a) , AP could schedule a low latency data frame transmission 605 staring from the configured preemption occasion (i.e., the configured xIFS 604) following the PPDU frame transmission 603 from STA1 if AP buffered a low latency data frame for STA2. After AP finishes the low latency frame transmission 605, STA2 can transmit a BA frame 606 to AP. As STA1 detects the low latency data frame transmission from AP starting from the preemption occasion (i.e., the configured xIFS 604) , it would terminate the ongoing transmission within the TXOP.

As illustrated in Fig. 6 (b) , if there was no low latency data frame buffered at AP, it could transmit a BA frame 607 in response to reception of the PPDU#1 frame 603 and continue to receive data from the STA1 although it has got preemption grant from the STA1. As the STA1 doesn’t detect the low latency data frame transmission from the AP starting from the preemption occasion (i.e., the configured xIFS 604) , it can continue the ongoing transmission (i.e., PPDU#2) 608 within the TXOP. After STA1 finishes the low latency frame transmission 608, AP can transmit a BA frame 609 to AP.

Fig. 7 illustrates a schematic diagram 700 illustrating a still further preemption grant configuration according to some embodiments of the present disclosure. Similar to Fig. 6, a preemption occasion will be (pre-) configured for preemption operation. However, the preemption occasion can be different from that in Fig. 6. For example, the preemption occasion in Fig. 6 starts from the end of a PPDU frame transmission from the TXOP holder, while in Fig. 7, the preemption occasion starts from the end of a BA frame in response to a PPDU frame transmission from the TXOP holder.

In some embodiments of the present disclosure, the TXOP holder can specify any occasion for the non-TXOP holder to preempt the TXOP. If an xIFS is configured for the non-TXOP holder to preempt the TXOP, the length of the xIFS can be configurable.

With reference to Fig. 7, STA1 initiates a TXOP to transmit data to the AP. As there is no low latency data buffered at STA1, it can transmit a preemption configuration through the header of the PPDU frame 603 which indicates AP can preempt its TXOP and transmit low latency data during an xIFS time 604 following the PPDU transmission. Upon receiving the PPDU frame transmission from STA1, AP would first transmit a BA frame 609 in response to reception of the PPDU frame and schedule a low latency data frame transmission 605 starting from the configured preemption occasion (i.e., the configured xIFS 604) following the BA frame transmission 609.

Fig. 8 illustrates a schematic diagram illustrating a method 800 implemented at a first device according to some other embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the first device 201 as shown in, e.g., Figs. 2 and 3. In some other embodiments, the first device 201 can also be the STA1 in Figs. 4-7.

As shown in Fig. 8, at block 810, the first device 201 determines configuration information for a TXOP initiated by the first device 201. The configuration information is to be used at least for determining whether a second device 202 is allowed to preempt the TXOP. At block 820, the first device 201 transmits the configuration information to the second device 202 within the TXOP.

In some embodiments, prior to determining the configuration information, the first device 201 may receive an indication for configuring the first device to support a proactive grant for preempting the TXOP.

In some embodiments, the first device 201 may determine the configuration information dependent on at least one of a QoS status and priority of at least one buffered data frame at the first device 201.

For example, if a low latency data frame is to be transmitted by the first device 201 within the TXOP, the first device 201 may determine the configuration information to indicate that the second device 202 is not allowed to preempt the TXOP. If no low latency data frame is to be transmitted by the first device within the TXOP, the first device 201 may determine the configuration information to indicate that the second device 202 is allowed to preempt the TXOP.

The first device 201 may transmit the configuration information via a field in an existing frame. Alternatively or in addition, the first device 201 may transmit the configuration information via a frame designed for transmitting the configuration information.

In some embodiments, the configuration information is first configuration information and indicates that the second device is allowed to preempt the TXOP; if a low latency data frame arrives at the first device 201 within the TXOP, the first device 201 may transmit second configuration information within the TXOP to indicate that the second device is not allowed to preempt the TXOP.

In some embodiments, the configuration information and the second configuration information may comprise an indication of whether the second device 202 is allowed to preempt the TXOP. Alternatively or in addition, the configuration information and the second configuration information may comprise a priority threshold for the second device to determine whether to preempt the TXOP. Alternatively or in addition, the configuration information and the second configuration information may comprise a latency threshold for the second device to determine whether to preempt the TXOP. Alternatively or in addition, the configuration information and the second configuration information may comprise one or more device IDs of devices that are allowed to preempt the TXOP.

In some embodiments, the configuration information may indicate a preemption occasion for starting preemption within the TXOP. Alternatively or in addition, the preemption occasion is pre-configured or pre-defined. In some embodiments, the preemption occasion may be within a time window. The time window may comprise an IFS. In some embodiments, the preemption occasion may be after a PPDU frame transmission. Alternatively or in addition, the preemption occasion may be after a BA frame transmission. In some embodiments, the preemption occasion may allow the second device 202 to terminate the PPDU frame transmission within the TXOP.

In some embodiments, dependent on detecting a frame transmission from the second device starting from the preemption occasion, the first device 201 may terminate an ongoing transmission within the TXOP. Alternatively, dependent on failing to detect the frame transmission, the first device 201 may continue the ongoing transmission within the TXOP after the preemption occasion.

In some embodiments, the configuration information may do not indicate a preemption occasion, and the preemption occasion may be not pre-configured or pre-defined. If the second device 202 is allowed to preempt the TXOP, the first device 201 may receive, from the second device 202, an indication for early terminating an ongoing transmission within the TXOP. Dependent on receiving the indication, the first device 201 may terminate the ongoing transmission within the TXOP.

In some embodiments, the first device may be one of an STA or an AP, and the second device may be one of an STA or an AP.

Fig. 9 illustrates a schematic diagram illustrating a method 900 implemented at a second device according to some other embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the second device 202 as shown in, e.g., Figs. 2 and 3. In some other embodiments, the second device 202 can also be the AP in Figs. 4-7.

As shown in Fig. 9, at block 910, the second device 202 receives, from the first device 201, configuration information for a TXOP initiated by the first device. At block 920, the second device 202 determines, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission. At block 930, dependent on determining to preempt the TXOP for the data frame transmission, the second device 202 transmits or receives the data frame transmission within the TXOP.

In some embodiments, the configuration information may be received via a field in an existing frame. Alternatively or in addition, the configuration information may be received via a frame designed for receiving the configuration information.

In some embodiments, prior to receiving the configuration information, the second device 202 may transmit, to the first device 201, an indication for configuring the first device to support a proactive grant for preempting the TXOP.

In some embodiments, the configuration information is first configuration information, and the second device 202 may receive second configuration information for the TXOP before receiving the first configuration information. Moreover, the second device 202 may determine whether to preempt the TXOP dependent on the first configuration information.

In some embodiments, the second device 202 is allowed to preempt the TXOP, and dependent on determining that a priority of the data frame transmission is higher than the priority threshold, the second device 202 may determine to preempt the TXOP. Alternatively, dependent on determining that the priority is lower than or equal to the priority threshold, the second device 202 may determine not to preempt the TXOP.

In some embodiments, the second device 202 is allowed to preempt the TXOP, and dependent on determining that a latency of the data frame transmission is longer than the latency threshold, the second device 202 may determine to preempt the TXOP. Alternatively, dependent on determining that the latency is shorter than or equal to the latency threshold, the second device 202 may determine not to preempt the TXOP.

In some embodiments, if the second device 202 determines to preempt the TXOP for the data frame transmission, it may transmit the data frame transmission to the first device 201 or a third device starting from the preemption occasion. Alternatively or in addition, the second device 202 may transmit a trigger to the third device for the data frame transmission starting from the preemption occasion and receive the data frame transmission from the third device.

In some embodiments, the configuration information may do not indicate a preemption occasion, and the preemption occasion may be not pre-configured or pre-defined. In this case, if the second device 202 determines to preempt the TXOP, the second device 202 may transmit an indication for early terminating an ongoing transmission within the TXOP to the first device 201. Then, the second device 202 can transmit the data frame transmission within the TXOP to the first device 201 or a third device, or receive the data frame transmission within the TXOP from the third device.

In some embodiments, an apparatus capable of performing any of the method 800 (for example, the first device 201) may comprise means for performing the respective steps of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises: means for determining, at a first device, configuration information for a TXOP initiated by the first device, wherein the configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP; and means for transmitting the configuration information to the second device within the TXOP.

In some embodiments, the apparatus further comprises means for: prior to determining the configuration information, receiving an indication for configuring the first device to support a proactive grant for preempting the TXOP.

In some embodiments, the means for determining configuration information comprises means for determining configuration information dependent on at least one of a QoS status and priority of at least one buffered data frame at the first device.

In some embodiments, the means for determining configuration information comprises means for: dependent on determining that a low latency data frame is to be transmitted by the first device within the TXOP, determining the configuration information to indicate that the second device is not allowed to preempt the TXOP; or dependent on determining that no low latency data frame is to be transmitted by the first device within the TXOP, determining the configuration information to indicate that the second device is allowed to preempt the TXOP.

In some embodiments, the configuration information is transmitted via a field in an existing frame. Alternatively or in addition, the configuration information is transmitted via a frame designed for transmitting the configuration information.

In some embodiments, the configuration information is first configuration information and indicates that the second device is allowed to preempt the TXOP; the apparatus further comprises means for: dependent on determining that a low latency data frame arrives at the first device within the TXOP, transmitting second configuration information within the TXOP to indicate that the second device is not allowed to preempt the TXOP.

In some embodiments, the configuration information and the second configuration information each comprise at least one of the following: an indication of whether the second device is allowed to preempt the TXOP; a priority threshold for the second device to determine whether to preempt the TXOP; a latency threshold for the second device to determine whether to preempt the TXOP; or one or more device IDs of devices that are allowed to preempt the TXOP.

In some embodiments, the configuration information may indicate a preemption occasion for starting preemption within the TXOP. Alternatively or in addition, the preemption occasion is pre-configured or pre-defined. In some embodiments, the preemption occasion may be within a time window. The time window may comprise an IFS. In some embodiments, the preemption occasion may be after a PPDU frame transmission. Alternatively or in addition, the preemption occasion may be after a BA frame transmission. In some embodiments, the preemption occasion may allow the second device to terminate the PPDU frame transmission within the TXOP.

In some embodiments, the apparatus further comprises means for: dependent on detecting a frame transmission from the second device starting from the preemption occasion, terminating an ongoing transmission within the TXOP; or dependent on failing to detect the frame transmission, continuing the ongoing transmission within the TXOP after the preemption occasion.

In some embodiments, the configuration information may do not indicate a preemption occasion, and the preemption occasion may be not pre-configured or pre-defined. The apparatus further comprises means for: receiving, from the second device, an indication for early terminating an ongoing transmission within the TXOP; and dependent on receiving the indication, terminating the ongoing transmission within the TXOP.

In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 800. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

In some embodiments, an apparatus capable of performing any of the method 900 (for example, the second device 202) may comprise means for performing the respective steps of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises: means for receiving, at a second device from a first device, configuration information for a TXOP initiated by the first device; determine, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and dependent on determining to preempt the TXOP for the data frame transmission, transmit or receive the data frame transmission within the TXOP.

In some embodiments, the apparatus further comprises means for: prior to receiving the configuration information, transmitting, to the first device, an indication for configuring the first device to support a proactive grant for preempting the TXOP.

In some embodiments, the configuration information is received via a field in an existing frame. Alternatively or in addition, the configuration information is received via a frame designed for transmitting the configuration information.

In some embodiments, the configuration information is first configuration information, and the apparatus further comprises means for: receiving second configuration information for the TXOP before receiving the first configuration information; and determining whether to preempt the TXOP dependent on the first configuration information.

In some embodiments, the second device is allowed to preempt the TXOP and the means for determining whether to preempt the TXOP comprises means for: dependent on determining that a priority of the data frame transmission is higher than the priority threshold, determine to preempt the TXOP; or dependent on determining that the priority is lower than or equal to the priority threshold, determine not to preempt the TXOP.

In some embodiments, the second device is allowed to preempt the TXOP and the means for determining whether to preempt the TXOP comprises means for: dependent on determining that a latency of the data frame transmission is longer than the latency threshold, determine to preempt the TXOP; or dependent on determining that the latency is shorter than or equal to the latency threshold, determine not to preempt the TXOP.

In some embodiments, the means for transmitting the data frame transmission comprises means for: transmitting, to the first device or a third device, the data frame transmission starting from the preemption occasion. In some embodiments, the means for receiving the data frame transmission comprises means for: transmitting, to the third device, a trigger for the data frame transmission starting from the preemption occasion; and receiving, from the third device, the data frame transmission.

In some embodiments, the configuration information may do not indicate a preemption occasion, and the preemption occasion may be not pre-configured or pre-defined. The apparatus further comprises means for: dependent on determining to preempt the TXOP, transmitting, to the first device, an indication for early terminating an ongoing transmission within the TXOP; and transmitting the data frame transmission within the TXOP to the first device or a third device, or receive the data frame transmission within the TXOP from the third device.

In some embodiments, the second device may be one of an STA or an AP, and the first device may be one of an STA or an AP.

Fig. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure. The device 1000 may be provided to implement the communication device, for example the first device 201, or the second device 202 as shown in Figs. 2 and 3. As shown, the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the processor 1010, and one or more communication modules 1040 coupled to the processor 1010.

The communication module 1040 is for bidirectional communications. The communication module 1040 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.

The processor 1010 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1000 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1024, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1022 and other volatile memories that will not last in the power-down duration.

A computer program 1030 includes computer executable instructions that are executed by the associated processor 1010. The program 1030 may be stored in the ROM 1020. The processor 1010 may perform any suitable actions and processing by loading the program 1030 into the RAM 1020.

The embodiments of the present disclosure may be implemented by means of the program 1030 so that the device 1000 may perform any process of the disclosure as discussed with reference to Figs. 2 to 9. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

In some embodiments, the program 1030 may be tangibly contained in a computer readable medium which may be included in the device 1000 (such as in the memory 1020) or other storage devices that are accessible by the device 1000. The device 1000 may load the program 1030 from the computer readable medium to the RAM 1022 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. Fig. 11 shows an example of the computer readable medium 1100 in form of CD or DVD. The computer readable medium has the program 1030 stored thereon.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 800 or the method 900 as described above with reference to Figs. 8 and 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A first device comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the first device at least to:

determine configuration information for a transmission opportunity (TXOP) initiated by the first device, wherein the configuration information is to be used at least for determining whether a second device is allowed to preempt the TXOP; and

transmit the configuration information to the second device within the TXOP.
The first device of claim 1, wherein the first device is further caused to:

prior to determining the configuration information, receive an indication for configuring the first device to support a proactive grant for preempting the TXOP.
The first device of claim 1 or 2, wherein the first device is caused to determine the configuration information dependent on at least one of a quality of service (QoS) status and priority of at least one buffered data frame at the first device.
The first device of any of claims 1-3, wherein the first device is caused to determine the configuration information by at least one of the following:

dependent on determining that a low latency data frame is to be transmitted by the first device within the TXOP, determining the configuration information to indicate that the second device is not allowed to preempt the TXOP; or

dependent on determining that no low latency data frame is to be transmitted by the first device within the TXOP, determining the configuration information to indicate that the second device is allowed to preempt the TXOP.
The first device of any of claims 1-4, wherein the configuration information is transmitted via at least one of the following:

a field in an existing frame; or

a frame designed for transmitting the configuration information.
The first device of any of claims 1-5, wherein the configuration information is first configuration information and indicates that the second device is allowed to preempt the TXOP, and the first device is further caused to:

dependent on determining that a low latency data frame arrives at the first device within the TXOP, transmit second configuration information within the TXOP to indicate that the second device is not allowed to preempt the TXOP.
The first device of claim 6, wherein the configuration information and the second configuration information each comprise at least one of the following:

an indication of whether the second device is allowed to preempt the TXOP;

a priority threshold for the second device to determine whether to preempt the TXOP;

a latency threshold for the second device to determine whether to preempt the TXOP; or

one or more device identifiers (IDs) of devices that are allowed to preempt the TXOP.
The first device of any of claims 1-7, wherein:

the configuration information indicates a preemption occasion for starting preemption within the TXOP; or

the preemption occasion is pre-configured or pre-defined.
The first device of claim 8, wherein at least one of the following:

the preemption occasion is within a time window;

the preemption occasion is after a physical protocol data unit (PPDU) frame transmission;

the preemption occasion is after a block acknowledgment (BA) frame transmission; or

the preemption occasion allows the second device to terminate the PPDU frame transmission within the TXOP.
The first device of claim 9, wherein the time window comprises an inter frame space (IFS) .
The first device of claim 8, wherein the first device is further caused to:

dependent on detecting a frame transmission from the second device starting from the preemption occasion, terminate an ongoing transmission within the TXOP; or

dependent on failing to detect the frame transmission, continue the ongoing transmission within the TXOP after the preemption occasion.
The first device of any of claims 1-7, wherein the configuration information does not indicate a preemption occasion, the preemption occasion is not pre-configured or pre-defined, and the second device is allowed to preempt the TXOP, and wherein the first device is further caused to:

receive, from the second device, an indication for early terminating an ongoing transmission within the TXOP; and

dependent on receiving the indication, terminate the ongoing transmission within the TXOP.
The first device of any of claims 1-12, wherein the first device is one of a station (STA) or an access point (AP) , and the second device is one of an STA or an AP.
A second device comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the second device at least to:

receive, from a first device, configuration information for a transmission opportunity (TXOP) initiated by the first device;

determine, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and

dependent on determining to preempt the TXOP for the data frame transmission, transmit or receive the data frame transmission within the TXOP.
The second device of claim 14, the second device is further caused to:

prior to receiving the configuration information, transmit, to the first device, an indication for configuring the first device to support a proactive grant for preempting the TXOP.
The second device of claim 14 or 15, wherein the configuration information is received via at least one of the following:

a field in an existing frame; or

a frame designed for receiving the configuration information.
The second device of any of claims 14-16, wherein the configuration information is first configuration information, and the second device is further caused to:

receive second configuration information for the TXOP before receiving the first configuration information; and

determine whether to preempt the TXOP dependent on the first configuration information.
The second device of claim 17, wherein the configuration information and the second configuration information each comprise at least one of the following:

an indication of whether the second device is allowed to preempt the TXOP;

a priority threshold for the second device to determine whether to preempt the TXOP;

a latency threshold for the second device to determine whether to preempt the TXOP; or

one or more device identifiers (IDs) of devices that are allowed to preempt the TXOP.
The second device of claim 18, wherein the second device is allowed to preempt the TXOP, and the second device is caused to determine whether to preempt the TXOP by:

dependent on determining that a priority of the data frame transmission is higher than the priority threshold, determine to preempt the TXOP; or

dependent on determining that the priority is lower than or equal to the priority threshold, determine not to preempt the TXOP.
The second device of claim 18 or 19, wherein the second device is allowed to preempt the TXOP, and the second device is caused to determine whether to preempt the TXOP by:

dependent on determining that a latency of the data frame transmission is longer than the latency threshold, determine to preempt the TXOP; or

dependent on determining that the latency is shorter than or equal to the latency threshold, determine not to preempt the TXOP.
The second device of any of claims 14-18, wherein:

the configuration information indicates a preemption occasion for starting preemption within the TXOP; or

the preemption occasion is pre-configured or pre-defined.
The second device of claim 21, wherein at least one of the following:

the preemption occasion is within a time window;

the preemption occasion is after a physical protocol data unit (PPDU) frame transmission;

the preemption occasion is after a block acknowledgment (BA) frame transmission; or

the preemption occasion allows the second device to terminate the PPDU frame transmission.
The second device of claim 22, wherein the time window comprises an inter frame space (IFS) .
The second device of claim 22, wherein:

the second device is caused to transmit the data frame transmission by:

transmitting, to the first device or a third device, the data frame transmission starting from the preemption occasion; or

the second device is caused to receive the data frame transmission by:

transmitting, to the third device, a trigger for the data frame transmission starting from the preemption occasion; and

receiving, from the third device, the data frame transmission.
The second device of any of claims 14-20, wherein the configuration information does not indicate a preemption occasion, and the preemption occasion is not pre-configured or pre-defined, and wherein the second device is further caused to:

dependent on determining to preempt the TXOP, transmit, to the first device, an indication for early terminating an ongoing transmission within the TXOP; and

transmit the data frame transmission within the TXOP to the first device or a third device, or receive the data frame transmission within the TXOP from the third device.
The second device of any of claims 14-25, wherein the first device is one of a station (STA) or an access point (AP) , and the second device is one of an STA or an AP.
A method comprising:

determining, at a first device, configuration information for a transmission opportunity (TXOP) initiated by the first device, wherein the configuration information is to be used for determining whether a second device is allowed to preempt the TXOP; and

transmitting the configuration information to the second device within the TXOP.
A method comprising:

receiving, at a second device and from a first device, configuration information for a transmission opportunity (TXOP) initiated by the first device;

determining, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and

dependent on determining to preempt the TXOP for the data frame transmission, transmitting or receiving the data frame transmission within the TXOP.
An apparatus comprising:

means for determining, at a first device, configuration information for a transmission opportunity (TXOP) initiated by the first device, wherein the configuration information is to be used for determining whether a second device is allowed to preempt the TXOP; and

means for transmitting the configuration information to the second device within the TXOP.
An apparatus comprising:

means for receiving, at a second device and from a first device, configuration information for a transmission opportunity (TXOP) initiated by the first device;

means for determining, dependent on the configuration information, whether to preempt the TXOP for a data frame transmission; and

means for dependent on determining to preempt the TXOP for the data frame transmission, transmitting or receiving the data frame transmission within the TXOP.
A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least one of the methods of claims 27 and 28.