Cross BSS preemption

Abstract

A first device in a first basic service set (BSS) is described. The first device being configured to one or more of perform sequential packet transmissions of at least two packets, where each pair of the at least two packets is separated by a time gap, transmit an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS comprising a second AP and one or more non-AP devices associated with the second AP, and receive a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets. Further, the sequential packet transmissions of the first device are preempted to allow the second device to perform communication actions in the second BSS.

Description

[0001] CROSS BSS PREEMPTION

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to cross basic service set (BSS) preemption.

[0004] INTRODUCTION

[0005] Wi-Fi, also known as Wireless Local Area Network (WLAN), is a technology that currently mainly operates in the 2.4 GHz, the 5 GHz band, and the 6 GHz band. There are specifications regulating an access point’s or mobile terminal’s physical (PHY) layer, medium access layer (MAC) layer and other aspects in order to secure compatibility and inter-operability between different WLAN entities, e.g., between an access point and mobile terminals, both of which may be referred to as stations (STAs) herein. Wi-Fi is generally operated in license-exempt bands, and as such, communication over Wi-Fi may be subject to interference sources from any number of known and unknown devices. Wi-Fi is commonly used as wireless extensions to fixed broadband access, e.g., in domestic environments and hotspots, like airports, train stations and restaurants.

[0006] Low latency in IEEE 802, 11 UHR

[0007] The Institute of Electrical and Electronics Engineers (IEEE) is a professional association that promulgates standards and develops standard amendments. The main amendment currently under development is the IEEE 802.1 Ibn amendment, also known as “ultra high reliability (UHR)” amendment, which has specified goals of the next generation Wi-Fi standards. One of the key goals of the next generation Wi-Fi standards is to improve the performance for low latency services such as automation, cloud gaming and extended reality (XR). For example, a key goal may include “at least one mode of operation capable of reducing latency by 25% for the 95th percentile of the latency distribution compared to the Extremely High Throughput MAC / PHY operation.” MAC / PHY operation may refer to medium access control (MAC) and / or physical layer (PHY) operation. One of the candidate features is to extend the IEEE 802.1 Ibe feature called restricted target wake time (R-TWT) which allows an access point (AP) to set up a periodic schedule where certain low latency traffic should be prioritized to have better protection by involving nearby APs to also respect this agreement.

[0008] However, as R-TWT sets up a periodic schedule for delivery, R-TWT, by design, does not deal well with (i.e., perform above a predetermined threshold when in presence of) low latency traffic that is more irregular, such as event-based traffic or periodic traffic with jitter, than other traffic.

[0009] Preemption in UHR Study Group (SG)

[0010] To deal with event-based traffic, the introduction of preemption into UHR has been advocated. By using preemption, an ongoing transmission may be interrupted in order to prioritize another typically more critical transmission. For example, a physical layer protocol data unit (PPDU) may be divided into several smaller PPDUs in order to leave short time gaps that may be occupied by transmissions carrying low latency data. In other words, waiting for the delivery of the entire PPDU before competing for channel access may not be necessary.

[0011] In existing technology, if two or more neighboring BSS(s) are operating as normal (i.e., as expected per standard requirements), they may block the channel for a long time (i.e., longer than a predetermined time) without giving preemption opportunities to potential time-critical STAs that may need it.

[0012] An example is shown in FIG. 1 which is a schematic diagram showing how an interfering overlapping BSS (OBSS) potentially may block the channel for a predetermined time even though the low latency BSS are able to preempt to prioritize their own low latency transmissions. AP 2 attempts to deliver low latency DL data to a STA in its BSS, STA 21. However, AP 1 has already won the transmission opportunity (TXOP) and is delivering downlink (DL) data to STA 11 when the data arrives in the MAC buffer of AP 2. Thus, AP 1 may act as a channel blocker for several milliseconds even though AP 2 can deliver the data in a timely manner through preemption. This blockage may prove detrimental to the service of STA 21.

[0013] SUMMARY

[0014] Some embodiments advantageously provide methods, systems, and apparatuses for cross BSS preemption.

[0015] Aspects are provided in the independent claims, and embodiments thereof are provided in the dependent claims.

[0016] One or more embodiments provide a procedure for APs to coordinate their operation such that a BSS that does not necessarily deliver low latency data leaves opportunities that may be used by a nearby BSS for low latency data delivery, e.g., allowing for coordinated operation across BSSs. In some embodiments a method in a first wireless communication device is described. The method may be described as follows and / or include one or more of the following example steps / embodiments:

[0017] 1. A method at a first wireless communication device, device 1, in a first basic service set (BSS1), wherein BSS1 comprises a first access point device (API) and one or more non-AP devices associated with API, the method comprising: a. devicel sequentially transmitting multiple small packets, each pair out of which is separated by a time gap, wherein the multiple small packets are segments of a large packet; b. devicel indicating that its small packet transmissions can be preempted by a device belonging to a second BSS2 comprising a second AP, AP2, and one or more non-AP devices associated with AP2; c. devicel receiving a pre-emption request during one of the time gaps between the small packets from a second device, device2, belonging to BSS2; and / or d. devicel preempting its small packet transmissions to allow device2 to undertake its own communications in BSS2.

[0018] 2. As lb, where the indication is included in one or more out of the small packets being transmitted.

[0019] 3. As 2, where the indication is explicit and is performed by using a dedicated bit, or a field in the small packet in which it is carried, and such indication indicates that the subsequent small packet can be pre-empted.

[0020] 4. As 2, where the indication is implicit and is performed by using a specific BSS color, wherein usage of that specific BSS color for a small packet implies that the subsequent small packet can be pre-empted.

[0021] 5. As any of the above, where devicel is API.

[0022] 6. As 5, where a mutual agreement is established between API and AP2 prior to the small packet transmissions, wherein the agreement comprises API allowing AP2 or any non-AP device in BSS2 to pre-empt its packet transmissions.

[0023] 7. As 6, where AP2 relays the agreement and pre-emption possibility to the non- AP devices in its BSS, i.e., BSS2. By using the principles of the embodiments above, the risk of long blockages of the channel may be avoided and support and protection for low latency services may be provided.

[0024] BRIEF DESCRIPTION OF THE DRAWINGS

[0025] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0026] FIG. 1 is a schematic diagram showing how an interfering OBSS potentially may block the channel for a predetermined time even though the low latency BSS are able to preempt to prioritize their own low latency transmissions;

[0027] FIG. 2 is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure;

[0028] FIG. 3 is a block diagram of an AP communicating with a non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure;

[0029] FIG. 4 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0030] FIG.5 is a block diagram of a host computer communicating via an access point with a non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure;

[0031] FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for executing a client application at a non-AP STA according to some embodiments of the present disclosure;

[0032] FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a non-AP STA according to some embodiments of the present disclosure;

[0033] FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data from the non-AP STA at a host computer according to some embodiments of the present disclosure; FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a host computer according to some embodiments of the present disclosure;

[0034] FIG. 10 is a flowchart of an example process in first device according to some embodiments of the present disclosure;

[0035] FIG. 11 shows an example topology according to some embodiments of the present disclosure;

[0036] FIG. 12 shows an example frame exchange according to some embodiments of the present disclosure; and

[0037] FIG. 13 shows an example message exchange according to some embodiments of the present disclosure.

[0038] DETAILED DESCRIPTION

[0039] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to cross BSS preemption. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0040] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0041] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0042] In some embodiments, the term “access point” or “AP” is used interchangeably and may comprise, or be, a network node. The AP may include any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), network router, network switch, etc. The AP may also comprise test equipment. The AP may comprise a radio router, a radio transceiver, WiFi access point, wireless local area network (WLAN) access point, a network controller, etc.

[0043] In some embodiments, the non-limiting term “device” is used to describe a wireless device (WD) and / or user equipment (UE) that may be used to implement some embodiments of the present disclosure. In some embodiments, the device may be and / or comprise an access point (AP) station (STA). In some embodiments, the device may be and / or comprise a non-access point station (non-AP STA). In some embodiments, the device may be any type of device capable of communicating with a network node, such as an AP, over radio signals. The device may be any radio communication device, target device, a portable device, device-to-device (D2D) device, machine type device or device capable of machine to machine communication (M2M), low-cost and / or low-complexity device, a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, Reduced Capability (RedCap) device, etc.

[0044] Further, a device may be considered a network node and may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware. The network node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the network node is said to be virtualized. A network node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations. In some embodiments, the device includes a wireless communication device.

[0045] Even though the descriptions herein may be explained in the context of one of a Downlink (DL) and an Uplink (UL) communication, it should be understood that the basic principles disclosed may also be applicable to the other of the one of the DL and the UL communication. In some embodiments in this disclosure, the principles may be considered applicable to, e.g., a first STA and, e.g., a second STA. For DL communication, the first STA may be the transmitter, and the second STA may be the receiver. For UL communication, the transmitter may be the second STA, and the receiver may be the first STA. In some embodiments, the first STA may be an AP or non-AP STA, and the second STA may be an AP or a non-AP STA.

[0046] Note also that some embodiments of the present disclosure may be supported by an IEEE 802.11 standard. IEEE 802.11 denotes a set of Wireless Local Area Network (WLAN) air interface standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to a few hundred meters). Some embodiments may also be supported by standard documents disclosed in Third Generation Partnership Project (3GPP) technical specifications. That is, some embodiments of the description can be supported by the above documents (e.g., standard documents). In addition, all the terms disclosed in the present document may be described by the above standard documents.

[0047] Note that although terminology from one particular wireless system, such as, for example, IEEE 802.11, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5th Generation (5G) and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0048] Note further, that functions described herein as being performed by one or more of a first STA, second STA, transmitting STA, receiving STA, AP, non-AP STA, wireless device, network node, etc., may be distributed over a plurality of STAs, APs, non-AP STAs, wireless devices, network nodes, etc. In other words, it is contemplated that the functions of the devices described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0049] In one or more embodiments, the term “small packet” is used and may refer to a packet transmitted and / or received and / or determined by an AP or STA or any other device. The small packet may have characteristics such as packet length, duration, size, etc., that is smaller than a predetermined value. Any one of packet length, duration, size of the small packet may be comparable to a “large packet”, which may also be a packet transmitted and / or received and / or determined by an AP or STA or any other device and may have characteristics such as packet length, duration, size, etc. Any one of packet length, duration, size of the large packet may be larger than any one of the corresponding packet length, duration, size of the small packet. The small packet may be a segment of a segmented large packet or a fragment of a fragmented PPDU. The small packet may have a length about 1 ms when the large packet may be up to 10 ms long.

[0050] In some embodiments, the term “transmission signal quality condition” is used and may refer to transmit (TX) signal quality requirements, such as in terms of EVM of the transmitted signal. A maximum TX power may be limited by the transmit signal quality requirements.

[0051] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0052] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 2 a schematic diagram of the communication system 10, according to one embodiment, constructed in accordance with the principles of the present disclosure. The communication system 10 in FIG. 2 is a non- limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and / or networks. Referring to FIG. 2, system 10 may comprise a wireless local area network (WLAN). The devices in the system 10 may communicate over one or more spectrums, such as, for example, a license-exempt spectrum, which may include frequency bands typically used by Wi-Fi technology. One or more of the devices may be further configured to communicate over other frequency bands, such as shared licensed frequency bands, etc. The system 10 may include one or more service areas 13a, 13b, etc. (collectively referred to herein as “service area 13”), which may be defined by corresponding access points (APs) 14a, 14b, etc. (collectively referred to herein as “AP STA 14”). A service area 13 may also correspond to and / or be associated with a coverage area, a cell, and / or a basic service set (BSS).

[0053] The AP STAs 14 may or may not be connectable to another network, such as a core network over a wired or wireless connection. The system 10 includes a plurality of non-AP devices, such as, for example, non-AP STAs 16a, 16b, 16c (collectively referred to as non-AP STAs 16). Each of the non-AP STAs 16 may be located in one or more service areas 13 and may be configured to wirelessly connect to one or more AP STA 14. Note that although two AP STAs 14a and 14b and two non-AP STAs 16a and 16b are shown for convenience, the communication system may include many more non-AP STAs 16 and AP STAs 14. Each AP STA 14 may connect to / serve / configure / schedule / etc. one or more non-AP STAs 16.

[0054] It should be understood that the system 10 may include additional nodes and / or devices not shown in FIG. 2. In addition, the system 10 may include many more connections and / or interfaces than those shown in FIG. 2. Thus, the elements shown in FIG. 2 are presented for ease of understanding.

[0055] Also, it is contemplated that a non-AP STA 16 can be in communication and / or configured to separately communicate with more than one AP STA 14 and / or more than one type of AP STA 14. Furthermore, an AP STA 14 may be in communication and / or configured to separately communicate with other AP STAs 14, as described herein, which may be via wired and / or wireless communication channels.

[0056] A non-AP STA 16 is configured to include a non-AP STA Management Unit 17, which is configured to perform one or more non-AP STA 16 functions described herein. An AP STA 14 is configured to include an AP STA Management Unit 18, which is configured to perform one or more AP STA 14 functions described herein. Example implementations, in accordance with an embodiment, of the AP STA 14 and non-AP STA 16 discussed in the preceding paragraphs will now be described with reference to FIG. 3.

[0057] An AP STA 14 or a non-AP STA 16 may be generally referred to as a STA 19. For example, a first STA 19a may be an AP STA 14, and a second STA 19b may be a non-AP STA 16. System 10 may include one or more additional STAs 19n (which include AP STAs 14 and / or non-AP STAs 16), which may be in communication with STA 19a and / or STA 19b.

[0058] The AP STA 14 includes hardware 20 including a communication interface 23, processing circuitry 24, a processor 26, and memory 28. The communication interface 23 may be configured to communicate with any of the nodes / devices in the system 10 according to some embodiments of the present disclosure, such as with one or more other AP STAs 14 and / or one or more non-AP STAs 16. In some embodiments, the communication interface 23 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and / or one or more RF transceivers, and / or may be considered a radio interface. In some embodiments, the communication interface 23 may also include a wired interface.

[0059] The processing circuitry 24 may include one or more processors 26 and memory, e.g., memory 28. In addition to a processor 26 and memory 28, the processing circuitry 24 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 26 may be configured to access (e.g., write to and / or read from) the memory 28, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0060] The AP STA 14 may further include software 30 stored internally in, for example, memory 28, or stored in external memory (e.g., database) accessible by the AP STA 14 via an external connection. The software 30 may be executable by the processing circuitry 24. The processing circuitry 24 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., AP STA 14. The memory 28 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 30 may include instructions stored in memory 28 that, when executed by the processor 26 and / or AP STA Management Unit 18 causes the processing circuitry 24 and / or configures the AP STA 14 to perform the processes described herein with respect to the AP STA 14.

[0061] Referring still to FIG. 3, the non-AP STA 16 includes hardware 32, which may include a communication interface 34, processing circuitry 36, a processor 38, and memory 40. The communication interface 34 may be configured to communicate with one or more AP STA 14 and / or other STA 19n, such as via wireless connection 35, and / or with other elements in the system 10, according to some embodiments of the present disclosure. In some embodiments, the communication interface 34 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and / or one or more RF transceivers, and / or may be considered a radio interface. In some embodiments, the communication interface 34 may also include a wired interface. In some embodiments, AP STA 14 may be configured to communicate with another AP STA 14, non-AP STA 16, and / or STA 19n via wireless connection 35 and / or via a wired connection (not shown).

[0062] The processing circuitry 36 may include one or more processors 38 and memory, such as, the memory 40. Furthermore, in addition to a traditional processor and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0063] Thus, the non-AP STA 16 may further include software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database) accessible by the non- AP STA 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by the non-AP STA 16. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software may include instructions stored in memory 40 that, when executed by the processor 38 and / or non-AP STA Management Unit 17, causes the processing circuitry 36 and / or configures the non-AP STA 16 to perform the processes described herein with respect to the non-AP STA 16.

[0064] In FIG. 3, the connection between the STAs 19 (i.e., AP STA 14, the non-AP STA 16, and STA 19n) is shown without explicit reference to any intermediary devices or connections. However, it should be understood that intermediary devices and / or connections may exist between these devices, although not explicitly shown.

[0065] Although FIG. 3 shows non-AP STA Management Unit 17 and AP STA Management Unit 18, as being within a processor, it is contemplated that this element may be implemented such that a portion of the element is stored in a corresponding memory within the processing circuitry. In other words, the element may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0066] FIG. 4 is a schematic diagram of a communication system 10, according to another embodiment of the present disclosure. In the example of FIG. 4, the access point STA 14 and non-AP STAs 16 may be similar to those of the example of FIG. 2, described herein. Additionally, in the example of FIG. 4, one or more AP STAs 14 and / or non-AP STAs 16 may form and / or be part of a service set network 44 (e.g., a basic service set, or any other network, set, and / or grouping of AP STAs 14 and non-AP STAs 16). The communication system 10 and / or service set network 44 may itself be connected to a host computer 46, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 46 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 48, 50 between the communication system 10 and / or the service set network 44 and the host computer 46 may extend directly from the service set network 44 to the host computer 46 or may extend via an optional intermediate network 52. The intermediate network 52 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 52, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 52 may comprise two or more sub-networks (not shown).

[0067] The communication system of FIG. 3 as a whole enables connectivity between one of the connected non-AP STAs 16 and the host computer 46. The connectivity may be described as an over-the-top (OTT) connection. The host computer 46 and the connected non AP-STAs 16 are configured to communicate data and / or signaling via the OTT connection, using the service set network 44, any intermediate network 52 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, an AP STA 14 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 46 to be forwarded (e.g., handed over) to a connected non-AP STA 16. Similarly, the AP STA 14 need not be aware of the future routing of an outgoing uplink communication originating from the non-AP STA 16 towards the host computer 46.

[0068] Example implementations, in accordance with an embodiment, of the non-AP STA 16, AP STA 14, and host computer 46 discussed in the preceding paragraphs will now be described with reference to FIG. 5. In the example of FIG. 5, the AP STA 14 and the non- AP STA 16 may have similar features and components as the AP STA 14 and non-AP STA 16 depicted in FIG. 3. Additionally, the host computer 46 comprises hardware (HW) 53 including a communication interface 54 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 46 further comprises processing circuitry 56, which may have storage and / or processing capabilities. The processing circuitry 56 may include a processor 58 and memory 60. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 56 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 58 may be configured to access (e.g., write to and / or read from) memory 60, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0069] Processing circuitry 56 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 46. Processor 58 corresponds to one or more processors 58 for performing host computer 46 functions described herein. The host computer 46 includes memory 60 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 62 and / or the host application 64 may include instructions that, when executed by the processor 58 and / or processing circuitry 56, causes the processor 58 and / or processing circuitry 56 to perform the processes described herein with respect to host computer 46. The instructions may be software associated with the host computer 46.

[0070] The software 62 of host computer 46 may be executable by the processing circuitry 56. The software 62 includes a host application 64. The host application 64 may be operable to provide a service to a remote user, such as a non-AP STA 16 connecting via an OTT connection 66 terminating at the non-AP STA 16 and the host computer 46. In providing the service to the remote user, the host application 64 may provide user data which is transmitted using the OTT connection 66. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 46 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 56 of the host computer 46 may enable the host computer 46 to observe, monitor, control, transmit to and / or receive from the AP STA 14 and / or the non-AP STA 16. The processing circuitry 56 of the host computer 46 may include a host management unit 68 configured to enable the service provider to observe / monitor / control / transmit to / receive from / configure / etc. the AP STA 14 and / or the non-AP STA 16.

[0071] The communication interface 23 of AP STA 14 may be configured to facilitate a connection 66 to the host computer 46. The connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and / or through one or more intermediate networks 52 outside the communication system 10. The communication interface 34 of non-AP STA 16 may be configured to facilitate a connection 66 to the host computer 46. The connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and / or through one or more intermediate networks 52 outside the communication system 10.

[0072] The software 42 of non-AP STA 16 may include a client application 70. The client application 70 may be operable to provide a service to a human or non-human user via the non-AP STA 16, with the support of the host computer 46. In the host computer 46, an executing host application 64 may communicate with the executing client application 70 via the OTT connection 66 terminating at the non-AP STA 16 and the host computer 46. In providing the service to the user, the client application 70 may receive request data from the host application 64 and provide user data in response to the request data. The OTT connection 66 may transfer both the request data and the user data. The client application 70 may interact with the user to generate the user data that it provides.

[0073] In some embodiments, the inner workings of the AP STA 14, non-AP STA 16, and host computer 46 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 5.

[0074] In FIG. 5, the OTT connection 66 has been drawn abstractly to illustrate the communication between the host computer 46 and the non-AP STA 16 via the AP STA 14, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which may be configured to hide from the non-AP STA 16 or from the service provider operating the host computer 46, or both. While the OTT connection 66 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0075] The wireless connection 35 between the non-AP STA 16 and the AP STA 14 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the non-AP STA 16 using the OTT connection 66, in which the wireless connection 35 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0076] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 66 between the host computer 46 and non-AP STA 16, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 66 may be implemented in the software 62 of the host computer 46 or in the software 42 of the non-AP STA 16, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 66 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 62, 42 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 66 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the AP STA 14, and it may be unknown or imperceptible to the AP STA 14. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary wireless device signaling facilitating the host computer’s 46 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 62, 42 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 66 while it monitors propagation times, errors, etc.

[0077] Thus, in some embodiments, the host computer 46 includes processing circuitry 56 configured to provide user data and a communication interface 54 that is configured to forward the user data to a wireless network and / or cellular network for transmission to the non-AP STA 16. In some embodiments, the wireless network and / or cellular network also includes the AP STA 14 with a communication interface 23. In some embodiments, the AP STA 14 is configured to, and / or the AP STA 14 processing circuitry 24 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the non-AP STA 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the non-AP STA 16.

[0078] In some embodiments, the host computer 46 includes processing circuitry 56 and a communication interface 54 that is configured to receive user data originating from a transmission from a non-AP STA 16 to an AP STA 14. In some embodiments, the non- AP STA 16 is configured to, and / or comprises a communication interface 34 and / or processing circuitry 36 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the AP STA 14, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the AP STA 14.

[0079] FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment. The communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIG. 5. In a first step of the method, the host computer 46 provides user data (Block SI 00). In an optional substep of the first step, the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64 (Block SI 02). In a second step, the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block S104). In an optional third step, the AP STA 14 transmits to the non-AP STA 16 the user data which was carried in the transmission that the host computer 46 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the non-AP STA 16 executes a client application, such as, for example, the client application 70, associated with the host application 64 executed by the host computer 46 (Block SI 08).

[0080] FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment. The communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 2 and 3. In a first step of the method, the host computer 46 provides user data (Block SI 10). In an optional substep (not shown) the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64. In a second step, the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block SI 12). The transmission may pass via the AP STA 14, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the non-AP STA 16 receives the user data carried in the transmission (Block SI 14).

[0081] FIG. 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment. The communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, the non-AP STA 16 receives input data provided by the host computer 46 (Block SI 16). In an optional substep of the first step, the non-AP STA 16 executes the client application 70, which provides the user data in reaction to the received input data provided by the host computer 46 (Block SI 18). Additionally or alternatively, in an optional second step, the non-AP STA 16 provides user data (Block S120). In an optional substep of the second step, the non-AP STA 16 provides the user data by executing a client application, such as, for example, client application 70 (Block S122). In providing the user data, the executed client application 70 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the non-AP STA 16 may initiate, in an optional third substep, transmission of the user data to the host computer 46 (Block S124). In a fourth step of the method, the host computer 46 receives the user data transmitted from the non-AP STA 16, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0082] FIG. 9 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment. The communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 2 and 3. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the AP STA 14 receives user data from the non-AP STA 16 (Block S128). In an optional second step, the AP STA 14 initiates transmission of the received user data to the host computer 46 (Block S130). In a third step, the host computer 46 receives the user data carried in the transmission initiated by the AP STA 14 (Block S132).

[0083] FIG. 10 is a flowchart of an example process in a first device such as AP STA 14. The first AP may refer to a first AP STA 14, the second AP may refer to a second AP STA 14, and a non-AP device may refer to non-AP STA 16. One or more Blocks and / or functions and / or methods performed by the AP STA 14 may be performed by one or more elements of the first AP STA 14 such as by AP STA Management Unit 18 in processing circuitry 24, memory 28, processor 26, communication interface 23, etc. according to the example process / method. The first device may be configured to perform (Block SI 34) sequential packet transmissions of at least two packets, each pair of the at least two packets being separated by a time gap, transmit (Block SI 36) an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS comprising the second AP and one or more non-AP devices associated with the second AP, receive (Block S138) a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets, and preempt (Block SI 40) the sequential packet transmissions of the first device to allow the second device to perform communication actions in the second BSS.

[0084] In some embodiments, each of the at least two packets is a segment of a segmented packet.

[0085] In some other embodiments, the indication is included in one or more of the at least two packets being transmitted.

[0086] In some embodiments, the indication is explicit and uses a dedicated bit and / or a field in one packet of the at least two packets that includes the indication. The indication further indicates that a subsequent packet of the at least two packets can be pre-empted. In some embodiments, the indication is implicit and uses a specific BSS color. Usage of the specific BSS color for one packet of the at least two packets implies that the subsequent packet of the at least two packets can be pre-empted.

[0087] In some other embodiments, the first device is the first AP.

[0088] In some embodiments, a mutual agreement is established between the first AP and the second AP prior to the sequential packet transmissions. The agreement includes a rule where the first AP allows the second AP or any non-AP device in the second BSS to preempt its sequential packet transmissions.

[0089] In some other embodiments, the second AP relays the agreement and pre-emption possibility to the non-AP devices in the second BSS.

[0090] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for cross BSS preemption.

[0091] One or more embodiments provide coordinating preemptable transmissions between multiple BSSs.

[0092] Channel protection

[0093] In some embodiments, ongoing communications are interrupted in a clean manner (i.e., without disruption). Further, the devices may be aware (e.g., informed, indicated) that the devices are not to interfere with low latency communication. FIG. 11 shows an example topology where AP STAs 14a, 14b (e.g., AP 1 and 2) are within communication range Each one of AP STAs 14a, 14b has one OBSS STA 16 in range and another OBSS STA 16 out of range. For example, AP 1 has OBSS STA21 in range, and OBSS STA22 out of range. In some embodiments, any protocol used by any device such as AP STAs 14 and / or non-AP STAs 16 may need to consider protecting the low latency transmitter from devices in range and out of range of the preempted BSS.

[0094] Protocol Description

[0095] For the examples below, AP STA 14 (e.g., AP STA 14a or AP 1) may be assumed to be delivering non-low latency traffic, to belong to the BSS that has currently won a TXOP, and to be delivering traffic. Further, AP STA 14 (e.g., AP STA 14b or AP 2) may be assumed to belong to the BSS that has low latency traffic to be delivered during the OBSS reserved TXOP and that needs to be delivered using preemption. AP STAs 14 may also be assumed to have exchanged information beforehand such that there is an agreement between the AP STAs 14 on how the preemption is to be performed. Additionally, the time gaps that is needed between the fragmented PPDUs or between the segmented packets may have varying durations depending on implementation. For example, if one does not want to introduce a new inter frame spacing (IFS), the preempted device may send fragmented PPDUs with a gap size equal to PIFS (which has the duration of SIFS + 1 slot duration) which would allow the low latency device to preempt using SIFS. This on the other hand requires the non-low latency device to increase the gap size, which is normally SIFS. Thus, for simplicity in the examples below we keep the SIFS gap between the fragmented PPDUs and denote the preemption time as xIFS which has a duration shorter than SIFS.

[0096] Direct Preemption

[0097] In an embodiment, AP STA 14 of the BSS that is preempted and the low latency device (belonging to a neighbor BSS) are within communication range of each other. A preemption attempt made by the low latency transmitter is directly noticed by the preemptable device which will stop its communication. FIG. 12 shows an example frame exchange where both BSSs need to transmit DL PPDUs, which may be used whenever the low latency device (AP2 in FIG. 12) is in communication range of the non-low latency delivering AP STA 14 (API in FIG. 12).

[0098] In some embodiments, where the preemptable traffic is sent in the DL from the first AP STA 14a (AP 1) to the first non-AP STA 16a (STA 11), and the low latency traffic is also in DL between second AP STA 14b (AP 2) and either third non-AP STA 16c (STA 21) or fourth non-AP STA 16d (STA 22), a method may include one or more of the following:

[0099] 1. The first AP STA 14a (AP 1) initiates with request to send (RTS) and / or clear to send (CTS) with intended receiver to establish channel protection as well as indicating that preemption of this PPDU is allowed by AP STA 14b (AP 2).

[0100] 2. The first AP STA 14a (AP 1) starts transmitting fragmented DL PPDUs with Short Interframe Space (SIFS) spacing in between fragments.

[0101] 3. DL low latency data arrives in the MAC buffer of second AP STA 14b (AP 2).

[0102] 4. xIFS after the next fragmented PPDU, AP STA 14b (AP 2) preempts the ongoing transmission by transmitting its low latency DL PPDU. In some embodiments, xIFS < SIFS.

[0103] 5. SIFS after the transmitted low latency DL PPDU, the third non-AP STA 16c (STA 21) responds with BA indicating reception status. 6. The second AP STA 14b (AP 2) indicates that the preemption was completed and that first AP STA 14a (AP 1) can resume its operation by: a. Sending an explicit indication to signal that the preemption period is over, e.g., a modified CF-end. b. Signaling the preemption period as the duration field in the low latency PPDU.

[0104] 7. The first AP STA 14a (AP 1) resumes operation in its BSS by either transmitting more fragmented or non-fragmented PPDUs according to the agreement made with second AP STA 14b (AP 2).

[0105] A depiction of how such a frame exchange may look like when second AP STA 14b (AP 2) is sending low latency data to STA 21 can be seen in FIG. 12.

[0106] Periodic Preemption

[0107] In some embodiments, the AP STA 14 of the preempted BSS and the low latency transmitter are not within communication distance from each other. Methods may be performed so that when the low latency transmission is about to occur, the low latency transmitter knows intervals when it may transmit, and the non-low latency transmitter is made aware that it should pause its operation. An exemplary method is described in the following.

[0108] In some other embodiments, the AP STA 14 without low-latency traffic (e.g., API in the example above) may signal a periodic schedule where preemption is allowed. In some other embodiments, where API is delivering DL non-critical traffic and where an out-of-range non-AP STA 16 to first AP STA 14a (AP 1) (e.g., fourth non-AP STA 16d (STA 22)) wants to transmit low latency traffic that needs preemption in BSS2, then the protocol may include one or more of

[0109] 1. The first AP STA 14a (AP 1) initiates with RTS / CTS with intended receiver to establish channel protection as well as indicating that preemption of this PPDU is allowed by the second AP STA 14b (AP 2) and shares information on the periodic schedule where preemption is allowed.

[0110] 2. After the TXOP has been protected, the second AP STA 14b (AP 2) informs the non-AP STAs 16 in its BSS that a preemptable TXOP has been reserved and shares the periodic schedule where preemption indications can be sent.

[0111] 3. The first AP STA 14a (AP 1) continues its operation by transmitting fragmented DL PPDUs to the receiving STA. 4. UL low latency data arrives in the MAC buffer of the fourth non-AP STA 16d (STA 22).

[0112] 5. tpafter a fragmented PPDU, the second AP STA 14b (AP 2) receives a preemption indication from the fourth non-AP STA 16d (STA 22) indicating that it has low latency traffic to deliver.

[0113] 6. The first AP STA 14a (AP 1) sends one more fragmented DL PPDUs to the receiving non-AP STA 16.

[0114] 7. xIFS after the fragmented PPDU, the second AP STA 14b (AP 2) sends Neighbor Discovery Protocol (NDP) Feedback Report Poll (NFRP) trigger frame to collect Buffer status for the low latency data and to indicate to the first AP STA 14a (AP 1) that it is preempting the TXOP.

[0115] 8. The fourth non-AP STA 16d (STA 22) sends an NFR frame to indicate its buffer size to the second AP STA 14b (AP 2).

[0116] 9. The second AP STA 14b (AP 2) sends a TF to trigger the low latency data from the fourth non-AP STA 16d (STA 22).

[0117] 10. The fourth non-AP STA 16d (STA 22) transmits a low latency TB PPDU to the second AP STA 14b (AP 2).

[0118] 11. The second AP STA 14b (AP 2) indicates that BSS2 preemption operation are completed and that API can resume its operation by transmitting a modified BA which also acknowledges the low latency data.

[0119] 12. The first AP STA 14a (AP 1) resumes operation in its BSS by either transmitting more fragmented or non-fragmented PPDUs according to the agreement made with the second AP STA 14b (AP 2).

[0120] FIG. 13 shows a message exchange example of how periodic preemption may be used when a non-low latency DL transmission in BSS1 is preempted by a device in BSS2 that is out of range of the first AP STA 14a (AP 1). In this example in FIG. 13, non-AP STA 16c (STA 21) needs to transmit UL low latency data. In some embodiments, performing periodic preemption may cause waiting for one more fragmented PPDU transmissions in BSS1 before the preemption can be performed, with the benefit of also being able to allow all devices in BSS2 to preempt transmissions in BSS1.

[0121] Even if a pre-emption agreement is setup between API and AP2 as discussed above, it may happen, when the third non-AP STA 16c (STA 21) is outside the communication range of both the first AP STA 14a (AP 1) and the first non-AP STA 16a (STA 11), that such third non-AP STA (STA 21) would not set its virtual network allocation vector (NAV) and may try to access the channel (and subsequently fail as the second AP STA 14b (AP 2) cannot respond) and not be able to receive the preemption information from the second AP STA 14b (AP 2). To avoid this situation, the second AP STA 14b (AP 2) may set the multi-user (MU) Enhanced Distributed Channel Access (EDCA) parameters to 0 to disallow EDCA access from STA 21 such that it would only access through triggered operation, thus giving the second AP STA 14b (AP 2)more control in this scenario.

[0122] UL non-Low Latency Traffic

[0123] In both examples above, DL traffic has been used as the preempted traffic source. However, the embodiments of the present disclosure are also compatible with UL non - critical traffic transmission in B SSL More specifically, trigger based (TB) UL traffic may be considered due to its predictability and because the operation is controlled by the AP STA 14. Additionally, it is expected that the TB UL PPDUs are not fragmented but instead may have a shorter length, possibly restricted.

[0124] If the low latency transmitting device can hear (i.e., communicate with) the nonlow latency AP STA 14, direct preemption may be used. If not, periodic preemption may be used, with some minor modifications to the schemes described above. For direct preemption, the low latency device may read out the duration field of the trigger frame to calculate the end time of the TB UL PPDU and instead preempt xIFS after that. For periodic preemption, the procedure may be similar to the DL case, although the schedule may align with the end times of the TB UL PPDUs.

[0125] Information Sharing

[0126] In some embodiments, an agreement may have to be made between the neighboring AP STA 14. This agreement may be for example be part of a multi-AP coordination handshake to set up operation for a long period going forward or it could be signaled on a PPDU or TXOP basis by having some bits in the preamble of each transmission.

[0127] One way to reuse some existing signaling and allow for implicit signaling of whether a PPDU is preemptable or not may be to reuse the BSS coloring bits. In some embodiments, BSS coloring bits may be used to identify if a transmission is coming from within its own BSS or outside, in which case with some certain conditions the device could transmit. In some other embodiments, groups of devices may be formed where PPDUs are preemptable or not.

[0128] General information that may be exchanged for the agreement may include: Restrictions for LL traffic o Access category o Length o Latency limit

[0129] • Fragmented PPDU length

[0130] • Time gap size

[0131] • Maximum LL PPDU size

[0132] • If periodic and / or direct preemption is allowed

[0133] • Traffic directions in LL and non-LL BSS (UL / DL)

[0134] Additionally, in order to decide if a BSS should make use of direct or periodic preemption, the neighborhood report may be used to determine if a low latency non-AP STA 16 is in range of any AP STAs 14 that its associated AP is also in range of.

[0135] Although the embodiments are described using AP STA 14 and non-AP STA 16, the embodiments are not limited as such, and any of the steps and / or functions and / or features and / or task and / or processes may be performed by any other component of system 10, such as STA 19, a device, a network node (e.g., a 3GPP network node), a wireless device (e g., a 3 GPP WD), etc.

[0136] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0137] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0138] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0139] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0140] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0141] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0142] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0143] Abbreviations that may be used in the preceding description include:

[0144] AP Access Point

[0145] BA Block Acknowledgement

[0146] BSS Basic Service Set

[0147] CTS Clear-to-Send

[0148] DL Downlink

[0149] EDC A Enhanced Distributed Channel Access

[0150] LL Low latency

[0151] MU Multi-User

[0152] NFR NDP Feedback Report

[0153] NFRP NDP Feedback Report Poll

[0154] PPDU Physical Protocol Data Unit

[0155] RTS Ready-to-Send

[0156] ST A Station

[0157] TB Trigger Based

[0158] TXOP Transmit Opportunity

[0159] UL Uplink

[0160] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings. Example Embodiments:

[0161] Embodiment Al . A first device configured to communicate with a second device and / or a first access point (AP) and / or a second AP, the first device being in a first basic service set (BSS), the first BSS comprising the first AP and one or more non-AP devices associated with the first AP, the first device being configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to one or more of perform sequential packet transmissions of at least two packets, each pair of the at least two packets being separated by a time gap; transmit an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS comprising the second AP and one or more non-AP devices associated with the second AP; receive a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets; and preempt the sequential packet transmissions of the first device to allow the second device to perform communication actions in the second BSS.

[0162] Embodiment A2. The first device of Embodiment Al, wherein each of the at least two packets is a segment of a segmented packet.

[0163] Embodiment A3. The first device of Embodiment Al, wherein the indication is included in one or more of the at least two packets being transmitted.

[0164] Embodiment A4. The first device of Embodiment A3, wherein the indication is explicit and uses a dedicated bit and / or a field in one packet of the at least two packets that includes the indication, the indication further indicating that a subsequent packet of the at least two packets can be pre-empted.

[0165] Embodiment A5. The first device of Embodiment A3, wherein the indication is implicit and uses a specific BSS color, usage of the specific BSS color for one packet of the at least two packets implies that the subsequent packet of the at least two packets can be pre-empted.

[0166] Embodiment A6. The first device of any one of Embodiments A1-A5, wherein the first device is the first AP.

[0167] Embodiment A7. The first device of Embodiment A6, wherein a mutual agreement is established between the first AP and the second AP prior to the sequential packet transmissions, the agreement including a rule where the first AP allows the second AP or any non-AP device in the second BSS to pre-empt its sequential packet transmissions.

[0168] Embodiment A8. The first device of Embodiment A7, wherein the second AP relays the agreement and pre-emption possibility to the non-AP devices in the second BSS.

[0169] Embodiment Bl. A method in a first device configured to communicate with a second device and / or a first access point (AP) and / or a second AP, the first device being in a first basic service set (BSS), the first BSS comprising the first AP and one or more non- AP devices associated with the first AP, the method comprising one or more of performing sequential packet transmissions of at least two packets, each pair of the at least two packets being separated by a time gap; transmitting an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS comprising the second AP and one or more non-AP devices associated with the second AP; receiving a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets; and preempting the sequential packet transmissions of the first device to allow the second device to perform communication actions in the second BSS.

[0170] Embodiment B2. The method of Embodiment Al, wherein each of the at least two packets is a segment of a segmented packet.

[0171] Embodiment B3. The method of Embodiment Bl, wherein the indication is included in one or more of the at least two packets being transmitted.

[0172] Embodiment B4. The method of Embodiment B3, wherein the indication is explicit and uses a dedicated bit and / or a field in one packet of the at least two packets that includes the indication, the indication further indicating that a subsequent packet of the at least two packets can be pre-empted.

[0173] Embodiment B5. The method of Embodiment B3, wherein the indication is implicit and uses a specific BSS color, usage of the specific BSS color for one packet of the at least two packets implies that the subsequent packet of the at least two packets can be pre-empted.

[0174] Embodiment B6. The method of any one of Embodiments B1-B5, wherein the first device is the first AP.

[0175] Embodiment B7. The method of Embodiment B6, wherein a mutual agreement is established between the first AP and the second AP prior to the sequential packet transmissions, the agreement including a rule where the first AP allows the second AP or any non-AP device in the second BSS to pre-empt its sequential packet transmissions.

[0176] Embodiment B8. The method of Embodiment B7, wherein the second AP relays the agreement and pre-emption possibility to the non-AP devices in the second BSS.

Claims

CLAIMS:

1. A first device configured to communicate with a second device and / or a first access point (AP) (14a) and / or a second AP (14b), the first device being in a first basic service set (BSS) (13a), the first BSS comprising the first AP and one or more non- AP devices (16a) associated with the first AP, the first device being configured to, and / or comprising a radio interface (23) and / or comprising processing circuitry (24) configured to one or more of perform sequential packet transmissions of at least two packets, each pair of the at least two packets being separated by a time gap; transmit an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS (13b) comprising the second AP and one or more non-AP devices (16b) associated with the second AP; receive a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets; and preempt the sequential packet transmissions of the first device to allow the second device to perform communication actions in the second BSS.

2. The first device of Claim 1, wherein each of the at least two packets is a segment of a segmented packet.

3. The first device of Claim 1, wherein the indication is included in one or more of the at least two packets being transmitted.

4. The first device of Claim 3, wherein the indication is explicit and uses a dedicated bit and / or a field in one packet of the at least two packets that includes the indication, the indication further indicating that a subsequent packet of the at least two packets can be pre-empted.

5. The first device of Claim 3, wherein the indication is implicit and uses a specific BSS color, usage of the specific BSS color for one packet of the at least two packets implies that the subsequent packet of the at least two packets can be pre-empted.

6. The first device of any one of Claims 1-5, wherein the first device is the first AP (14a).

7. The first device of Claim 6, wherein a mutual agreement is established between the first AP and the second AP prior to the sequential packet transmissions, the agreement including a rule where the first AP allows the second AP or any non-AP device in the second BSS to pre-empt its sequential packet transmissions.

8. The first device of Claim 7, wherein the second AP relays the agreement and pre-emption possibility to the non-AP devices in the second BSS.

9. A method in a first device configured to communicate with a second device and / or a first access point (AP) and / or a second AP, the first device being in a first basic service set (BSS), the first BSS comprising the first AP and one or more non-AP devices associated with the first AP, the method comprising one or more of performing sequential packet transmissions of at least two packets, each pair of the at least two packets being separated by a time gap (SI 34); transmitting an indication indicating that the sequential packet transmissions can be pre-empted by at least one device belonging to a second BSS comprising the second AP and one or more non-AP devices associated with the second AP (SI 36); receiving a pre-emption request from the second device belonging to the second BSS during the time gap between one of the pairs of the at least two packets (SI 38); and preempting the sequential packet transmissions of the first device to allow the second device to perform communication actions in the second BSS (S140).

10. The method of Claim 9, wherein each of the at least two packets is a segment of a segmented packet.

11. The method of Claim 9, wherein the indication is included in one or more of the at least two packets being transmitted.

12. The method of Claim 11, wherein the indication is explicit and uses a dedicated bit and / or a field in one packet of the at least two packets that includes the indication, the indication further indicating that a subsequent packet of the at least two packets can be pre-empted.

13. The method of Claim 11, wherein the indication is implicit and uses a specific BSS color, usage of the specific BSS color for one packet of the at least two packets implies that the subsequent packet of the at least two packets can be pre-empted.

14. The method of any one of Claims 9-13, wherein the first device is the first AP.

15. The method of Claim 14, wherein a mutual agreement is established between the first AP and the second AP prior to the sequential packet transmissions, the agreement including a rule where the first AP allows the second AP or any non-AP device in the second BSS to pre-empt its sequential packet transmissions.

16. The method of Claim 15, wherein the second AP relays the agreement and pre-emption possibility to the non-AP devices in the second BSS.

Images