WO2024072399A1

WO2024072399A1 - Apparatus, system, and method of communicating during a transmit opportunity (txop) over a wireless communication channel

Info

Publication number: WO2024072399A1
Application number: PCT/US2022/045296
Authority: WO
Inventors: Laurent Cariou; Thomas J. Kenney
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-04
Anticipated expiration: 2025-03-30
Also published as: EP4595669A1

Abstract

For example, a wireless communication device may be configured to transmit protection information to signal that a Transmit Opportunity (TxOP) over a wireless communication channel is to be protected according to a preemption-based protection scheme. For example, the TxOP may include a preemption period between a first transmission period and a second transmission period. For example, the preemption-based protection scheme may be configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, and to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period. For example, the wireless communication device may be configured to pause communication over the wireless communication channel during the preemption period to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic.

Description

APPARATUS, SYSTEM, AND METHOD OF COMMUNICATING DURING A TRANSMIT OPPORTUNITY (TXOP) OVER A WIRELESS COMMUNICATION CHANNEL TECHNICAL FIELD

[001] Aspects described herein generally relate to communicating during a Transmit Opportunity (TxOP) over a wireless communication channel.

BACKGROUND [002] Devices in a wireless communication system may be configured to communicate according to communication protocols, which may be configured to support high-throughput data for users of wireless communication devices.

BRIEF DESCRIPTION OF THE DRAWINGS

[003] For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

[004] Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative aspects.

[005] Fig. 2 is a schematic illustration of a multi-link communication scheme, which may be implemented in accordance with some demonstrative aspects.

[006] Fig. 3 is a schematic illustration of a multi-link communication scheme, which may be implemented in accordance with some demonstrative aspects.

[007] Fig. 4 is a schematic illustration of a Transmit Opportunity (TxOP) configured according to a preemption mechanism, which may be implemented in accordance with some demonstrative aspects.

[008] Fig. 5 is a schematic flow-chart illustration of a method of communicating during a TxOP over a wireless communication channel, in accordance with some demonstrative aspects.

[009] Fig. 6 is a schematic flow-chart illustration of a method of communicating during a TxOP over a wireless communication channel, in accordance with some demonstrative aspects.

[0010] Fig. 7 is a schematic illustration of a product of manufacture, in accordance with some demonstrative aspects.

DETAILED DESCRIPTION

[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some aspects. However, it will be understood by persons of ordinary skill in the art that some aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.

[0012] Discussions herein utilizing terms such as, for example, “processing”, “computing”, “calculating”, “determining”, “establishing”, “analyzing”, “checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer’s registers and/or memories into other data similarly represented as physical quantities within the computer’ s registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.

[0013] The terms “plurality” and “a plurality”, as used herein, include, for example, “multiple” or “two or more”. For example, “a plurality of items” includes two or more items.

[0014] References to “one aspect”, “an aspect”, “demonstrative aspect”, “various aspects” etc., indicate that the aspect(s) so described may include a particular feature, structure, or characteristic, but not every aspect necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one aspect” does not necessarily refer to the same aspect, although it may.

[0015] As used herein, unless otherwise specified the use of the ordinal adjectives “first”, “second”, “third” etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0016] Some aspects may be used in conjunction with various devices and systems, for example, a User Equipment (UE), a Mobile Device (MD), a wireless station (STA), a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a wearable device, a sensor device, an Internet of Things (loT) device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a Wireless Video Area Network (WVAN), a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a Wireless PAN (WPAN), and the like.

[0017] Some aspects may be used in conjunction with devices and/or networks operating in accordance with existing IEEE 802.11 standards (including IEEE 802.11- 2020 (IEEE 802.11-2020, IEEE Standard, for Information Technology — Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks — Specific Requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, December, 2020); and/or IEEE 802.11be (IEEE P802.11be/D2.0 Draft Standard for Information technology — Telecommunications and information exchange between systems Local and metropolitan area networks — Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 8: Enhancements for extremely high throughput (EHT), May 2022)) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

[0018] Some aspects may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a Personal Communication Systems (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable Global Positioning System (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a Multiple Input Multiple Output (MIMO) transceiver or device, a Single Input Multiple Output (SIMO) transceiver or device, a Multiple Input Single Output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, Digital Video Broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a Smartphone, a Wireless Application Protocol (WAP) device, or the like.

[0019] Some aspects may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Infra-Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division Multiple Access (SDMA), Extended TDMA (E- TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband (UWB), 4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other aspects may be used in various other devices, systems and/or networks.

[0020] The term “wireless device”, as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative aspects, a wireless device may be or may include a peripheral that may be integrated with a computer, or a peripheral that may be attached to a computer. In some demonstrative aspects, the term “wireless device” may optionally include a wireless service.

[0021] The term “communicating” as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase “communicating a signal” may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase “communicating a signal” may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device. The communication signal may be transmitted and/or received, for example, in the form of Radio Frequency (RF) communication signals, and/or any other type of signal.

[0022] As used herein, the term "circuitry" may refer to, be part of, or include, an Application Specific Integrated Circuit (ASIC), an integrated circuit, an electronic circuit, a processor (shared, dedicated or group), and/or memory (shared. Dedicated, or group), that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, some functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some aspects, circuitry may include logic, at least partially operable in hardware.

[0023] The term “logic” may refer, for example, to computing logic embedded in circuitry of a computing apparatus and/or computing logic stored in a memory of a computing apparatus. For example, the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and/or operations. In one example, logic may be embedded in various types of memory and/or firmware, e.g., silicon blocks of various chips and/or processors. Logic may be included in, and/or implemented as part of, various circuitry, e.g. radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, and/or the like. In one example, logic may be embedded in volatile memory and/or non-volatile memory, including random access memory, read only memory, programmable memory, magnetic memory, flash memory, persistent memory, and the like. Logic may be executed by one or more processors using memory, e.g., registers, stuck, buffers, and/or the like, coupled to the one or more processors, e.g., as necessary to execute the logic.

[0024] Some demonstrative aspects may be used in conjunction with a WLAN, e.g., a WiFi network. Other aspects may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a “piconet”, a WPAN, a WVAN and the like.

[0025] Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over a sub- 10 Gigahertz (GHz) frequency band, for example, a 2.4GHz frequency band, a 5GHz frequency band, a 6GHz frequency band, and/or any other frequency band below 10GHz.

[0026] Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over an Extremely High Frequency (EHF) band (also referred to as the “millimeter wave (mmWave)” frequency band), for example, a frequency band within the frequency band of between 20Ghz and 300GHz, for example, a frequency band above 45GHz, e.g., a 60GHz frequency band, and/or any other mmWave frequency band.

[0027] Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over the sub- 10 GHz frequency band and/or the mmWave frequency band, e.g., as described below. However, other aspects may be implemented utilizing any other suitable wireless communication frequency bands, for example, a 5G frequency band, a frequency band below 20GHz, a Sub 1 GHz (SIG) band, a WLAN frequency band, a WPAN frequency band, and the like.

[0028] Some demonstrative aspects may be implemented by a mmWave STA (mSTA), which may include for example, a STA having a radio transmitter, which is capable of operating on a channel that is within the mmWave frequency band. In one example, mmWave communications may involve one or more directional links to communicate at a rate of multiple gigabits per second, for example, at least 1 Gigabit per second, e.g., at least 7 Gigabit per second, at least 30 Gigabit per second, or any other rate.

[0029] In some demonstrative aspects, the mmWave STA may include a Directional Multi-Gigabit (DMG) STA, which may be configured to communicate over a DMG frequency band. For example, the DMG band may include a frequency band wherein the channel starting frequency is above 45 GHz.

[0030] In some demonstrative aspects, the mmWave STA may include an Enhanced DMG (EDMG) STA, which may be configured to implement one or more mechanisms, which may be configured to enable Single User (SU) and/or Multi-User (MU) communication of Downlink (DL) and/or Uplink frames (UL) using a MIMO scheme. For example, the EDMG STA may be configured to implement one or more channel bonding mechanisms, which may, for example, support communication over a channel bandwidth (BW) (also referred to as a “wide channel”, an “EDMG channel”, or a “bonded channel”) including two or more channels, e.g., two or more 2.16 GHz channels. For example, the channel bonding mechanisms may include, for example, a mechanism and/or an operation whereby two or more channels, e.g., 2.16 GHz channels, can be combined, e.g., for a higher bandwidth of packet transmission, for example, to enable achieving higher data rates, e.g., when compared to transmissions over a single channel. Some demonstrative aspects are described herein with respect to communication over a channel BW including two or more 2.16 GHz channels, however other aspects may be implemented with respect to communications over a channel bandwidth, e.g., a “wide” channel, including or formed by any other number of two or more channels, for example, an aggregated channel including an aggregation of two or more channels. For example, the EDMG STA may be configured to implement one or more channel bonding mechanisms, which may, for example, support an increased channel bandwidth, for example, a channel BW of 4.32 GHz, a channel BW of 6.48 GHz, a channel BW of 8.64 GHz, and/or any other additional or alternative channel BW. The EDMG STA may perform other additional or alternative functionality.

[0031] In other aspects, the mmWave STA may include any other type of STA and/or may perform other additional or alternative functionality. Other aspects may be implemented by any other apparatus, device and/or station.

[0032] The term “antenna”, as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some aspects, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some aspects, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a set of switched beam antennas, and/or the like.

[0033] Reference is made to Fig. 1, which schematically illustrates a system 100, in accordance with some demonstrative aspects.

[0034] As shown in Fig. 1, in some demonstrative aspects, system 100 may include one or more wireless communication devices. For example, system 100 may include a wireless communication device 102, a wireless communication device 140, a wireless communication device 150, and/or one or more other devices.

[0035] In some demonstrative aspects, devices 102, 140 and/or 150 may include a mobile device or a non-mobile, e.g., a static, device.

[0036] For example, devices 102, 140 and/or 150 may include, for example, a UE, an MD, a STA, an AP, a PC, a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, an Internet of Things (loT) device, a sensor device, a handheld device, a wearable device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “Carry Small Live Large” (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an “Origami” device or computing device, a device that supports Dynamically Composable Computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-ray disc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, a High Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a Personal Video Recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a Personal Media Player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a Digital Still camera (DSC), a media player, a Smartphone, a television, a music player, or the like.

[0037] In some demonstrative aspects, device 102 may include, for example, one or more of a processor 191, an input unit 192, an output unit 193, a memory unit 194, and/or a storage unit 195; and/or device 140 may include, for example, one or more of a processor 181, an input unit 182, an output unit 183, a memory unit 184, and/or a storage unit 185. Devices 102 and/or 140 may optionally include other suitable hardware components and/or software components. In some demonstrative aspects, some or all of the components of one or more of devices 102 and/or 140 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other aspects, components of one or more of devices 102 and/or 140 may be distributed among multiple or separate devices.

[0038] In some demonstrative aspects, processor 191 and/or processor 181 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. Processor 191 may execute instructions, for example, of an Operating System (OS) of device 102 and/or of one or more suitable applications. Processor 181 may execute instructions, for example, of an Operating System (OS) of device 140 and/or of one or more suitable applications.

[0039] In some demonstrative aspects, input unit 192 and/or input unit 182 may include, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 193 and/or output unit 183 may include, for example, a monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.

[0040] In some demonstrative aspects, memory unit 194 and/or memory unit 184 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 195 and/or storage unit 185 may include, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. Memory unit 194 and/or storage unit 195, for example, may store data processed by device 102. Memory unit 184 and/or storage unit 185, for example, may store data processed by device 140.

[0041] In some demonstrative aspects, wireless communication devices 102, 140, and/or 150 may be capable of communicating content, data, information and/or signals via a wireless medium (WM) 103. In some demonstrative aspects, wireless medium 103 may include, for example, a radio channel, an RF channel, a WiFi channel, a cellular channel, a 5G channel, an IR channel, a Bluetooth (BT) channel, a Global Navigation Satellite System (GNSS) Channel, and the like.

[0042] In some demonstrative aspects, WM 103 may include one or more wireless communication frequency bands and/or channels. For example, WM 103 may include one or more channels in a sub-lOGhz wireless communication frequency band, for example, a 2.4GHz wireless communication frequency band, one or more channels in a 5GHz wireless communication frequency band, and/or one or more channels in a 6GHz wireless communication frequency band. In another example, WM 103 may additionally or alternative include one or more channels in a mmWave wireless communication frequency band.

[0043] In other aspects, WM 103 may include any other type of channel over any other frequency band.

[0044] In some demonstrative aspects, device 102, device 140, and/or device 150 may include one or more radios including circuitry and/or logic to perform wireless communication between devices 102, 140, 150 and/or one or more other wireless communication devices. For example, device 102 may include one or more radios 114, and/or device 140 may include one or more radios 144.

[0045] In some demonstrative aspects, radio 114 may include at least a first radio 119, and a second radio 120. For example, radio 119 may be configured to communicate over a first wireless communication channel, and/or radio 120 may be configured to communicate over a second wireless communication channel, e.g., as described below.

[0046] In some demonstrative aspects, radio 144 may include at least a first radio 147, and a second radio 149. For example, radio 147 may be configured to communicate over the first wireless communication channel, and/or radio 149 may be configured to communicate over the second wireless communication channel, e.g., as described below.

[0047] In some demonstrative aspects, radios 114 and/or 144 may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, a radio 114 may include at least one receiver 116, and/or a radio 144 may include at least one receiver 146.

[0048] In some demonstrative aspects, radios 114 and/or 144 may include one or more wireless transmitters (Tx) including circuitry and/or logic to transmit wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, a radio 114 may include at least one transmitter 118, and/or a radio 144 may include at least one transmitter 148.

[0049] In some demonstrative aspects, radios 114 and/or 144, transmitters 118 and/or 148, and/or receivers 116 and/or 146 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; modulation elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital and/or digital to analog converters; filters; and/or the like. For example, radios 114 and/or 144 may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like.

[0050] In some demonstrative aspects, radios 114 and/or 144 may be configured to communicate over a 2.4GHz band, a 5GHz band, a 6GHz band, and/or any other band, for example, a directional band, e.g., an mmWave band, a 5G band, an S 1G band, and/or any other band.

[0051] In some demonstrative aspects, radios 114 and/or 144 may include, or may be associated with one or more, e.g., a plurality of, antennas. [0052] In some demonstrative aspects, device 102 may include one or more antennas 107, e.g., a single antenna 107 or a plurality of antennas 107, and/or device 140 may include one or more antennas 147, e.g., a single antenna 147 or a plurality of antennas 147.

[0053] Antennas 107 and/or 147 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 107 and/or 147 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some aspects, antennas 107 and/or 147 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some aspects, antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0054] In some demonstrative aspects, device 102 may include a controller 124, and/or device 140 may include a controller 154. Controller 124 may be configured to perform and/or to trigger, cause, instruct and/or control device 102 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140, 150 and/or one or more other devices; and/or controller 154 may be configured to perform, and/or to trigger, cause, instruct and/or control device 140 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140, 150 and/or one or more other devices, e.g., as described below.

[0055] In some demonstrative aspects, controllers 124 and/or 154 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media- Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, baseband (BB) circuitry and/or logic, a BB processor, a BB memory, Application Processor (AP) circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of controllers 124 and/or 154, respectively. Additionally or alternatively, one or more functionalities of controllers 124 and/or 154 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0056] In one example, controller 124 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 102, and/or a wireless station, e.g., a wireless STA implemented by device 102, to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 124 may include at least one memory, e.g., coupled to the one or more processors, which may be configured, for example, to store, e.g., at least temporarily, at least some of the information processed by the one or more processors and/or circuitry, and/or which may be configured to store logic to be utilized by the processors and/or circuitry.

[0057] In one example, controller 154 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 140, and/or a wireless station, e.g., a wireless STA implemented by device 140, to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 154 may include at least one memory, e.g., coupled to the one or more processors, which may be configured, for example, to store, e.g., at least temporarily, at least some of the information processed by the one or more processors and/or circuitry, and/or which may be configured to store logic to be utilized by the processors and/or circuitry.

[0058] In some demonstrative aspects, at least part of the functionality of controller 124 may be implemented as part of one or more elements of radio 114, and/or at least part of the functionality of controller 154 may be implemented as part of one or more elements of radio 144.

[0059] In other aspects, the functionality of controller 124 may be implemented as part of any other element of device 102, and/or the functionality of controller 154 may be implemented as part of any other element of device 140.

[0060] In some demonstrative aspects, device 102 may include a message processor 128 configured to generate, process and/or access one or messages communicated by device 102. [0061] In one example, message processor 128 may be configured to generate one or more messages to be transmitted by device 102, and/or message processor 128 may be configured to access and/or to process one or more messages received by device 102, e.g., as described below.

[0062] In one example, message processor 128 may include at least one first component configured to generate a message, for example, in the form of a frame, field, information element and/or protocol data unit, for example, a MAC Protocol Data Unit (MPDU); at least one second component configured to convert the message into a PHY Protocol Data Unit (PPDU), for example, by processing the message generated by the at least one first component, e.g., by encoding the message, modulating the message and/or performing any other additional or alternative processing of the message; and/or at least one third component configured to cause transmission of the message over a wireless communication medium, e.g., over a wireless communication channel in a wireless communication frequency band, for example, by applying to one or more fields of the PPDU one or more transmit waveforms. In other aspects, message processor 128 may be configured to perform any other additional or alternative functionality and/or may include any other additional or alternative components to generate and/or process a message to be transmitted.

[0063] In some demonstrative aspects, device 140 may include a message processor 158 configured to generate, process and/or access one or more messages communicated by device 140.

[0064] In one example, message processor 158 may be configured to generate one or more messages to be transmitted by device 140, and/or message processor 158 may be configured to access and/or to process one or more messages received by device 140, e.g., as described below.

[0065] In one example, message processor 158 may include at least one first component configured to generate a message, for example, in the form of a frame, field, information element and/or protocol data unit, for example, an MPDU; at least one second component configured to convert the message into a PPDU, for example, by processing the message generated by the at least one first component, e.g., by encoding the message, modulating the message and/or performing any other additional or alternative processing of the message; and/or at least one third component configured to cause transmission of the message over a wireless communication medium, e.g., over a wireless communication channel in a wireless communication frequency band, for example, by applying to one or more fields of the PPDU one or more transmit waveforms. In other aspects, message processor 158 may be configured to perform any other additional or alternative functionality and/or may include any other additional or alternative components to generate and/or process a message to be transmitted.

[0066] In some demonstrative aspects, message processors 128 and/or 158 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, MAC circuitry and/or logic, PHY circuitry and/or logic, BB circuitry and/or logic, a BB processor, a BB memory, AP circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of message processors 128 and/or 158, respectively. Additionally or alternatively, one or more functionalities of message processors 128 and/or 158 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0067] In some demonstrative aspects, at least part of the functionality of message processor 128 may be implemented as part of radio 114, and/or at least part of the functionality of message processor 158 may be implemented as part of radio 144.

[0068] In some demonstrative aspects, at least part of the functionality of message processor 128 may be implemented as part of controller 124, and/or at least part of the functionality of message processor 158 may be implemented as part of controller 154.

[0069] In other aspects, the functionality of message processor 128 may be implemented as part of any other element of device 102, and/or the functionality of message processor 158 may be implemented as part of any other element of device 140.

[0070] In some demonstrative aspects, at least part of the functionality of controller 124 and/or message processor 128 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of one or more radios 114. For example, the chip or SoC may include one or more elements of controller 124, one or more elements of message processor 128, and/or one or more elements of one or more radios 114. In one example, controller 124, message processor 128, and one or more radios 114 may be implemented as part of the chip or SoC.

[0071] In other aspects, controller 124, message processor 128 and/or the one or more radios 114 may be implemented by one or more additional or alternative elements of device 102.

[0072] In some demonstrative aspects, at least part of the functionality of controller 154 and/or message processor 158 may be implemented by an integrated circuit, for example, a chip, e.g., a SoC. In one example, the chip or SoC may be configured to perform one or more functionalities of one or more radios 144. For example, the chip or SoC may include one or more elements of controller 154, one or more elements of message processor 158, and/or one or more elements of one or more radios 144. In one example, controller 154, message processor 158, and one or more radios 144 may be implemented as part of the chip or SoC.

[0073] In other aspects, controller 154, message processor 158 and/or one or more radios 144 may be implemented by one or more additional or alternative elements of device 140.

[0074] In some demonstrative aspects, device 102, device 140, and/or device 150 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more STAs. For example, device 102 may include at least one STA, device 140 may include at least one STA, and/or device 150 may include at least one STA.

[0075] In some demonstrative aspects, device 102, device 140, and/or device 150 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more Extremely High Throughput (EHT) STAs. For example, device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more EHT STAs, and/or device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more EHT STAs.

[0076] In other aspects, device 102, device 140, and/or device 150 may include, operate as, perform the role of, and/or perform one or more functionalities of, any other wireless device and/or station, e.g., a WLAN STA, a WiFi STA, and the like. [0077] In some demonstrative aspects, device 102, device 140, and/or device 150 may be configured operate as, perform the role of, and/or perform one or more functionalities of, an access point (AP), e.g., an EHT AP STA.

[0078] In some demonstrative aspects, device 102, device 140, and/or device 150 may be configured to operate as, perform the role of, and/or perform one or more functionalities of, a non-AP STA, e.g., an EHT non-AP STA.

[0079] In other aspects, device 102, device 140, and/or device 150 may operate as, perform the role of, and/or perform one or more functionalities of, any other additional or alternative device and/or station.

[0080] In one example, a station (STA) may include a logical entity that is a singly addressable instance of a medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM). The STA may perform any other additional or alternative functionality.

[0081] In one example, an AP may include an entity that contains one station (STA) and provides access to the distribution services, via the wireless medium (WM) for associated STAs. An AP may include a STA and a distribution system access function (DSAF).The AP may perform any other additional or alternative functionality.

[0082] In some demonstrative aspects devices 102, 140, and/or 150 may be configured to communicate in an EHT network, and/or any other network.

[0083] In some demonstrative aspects, devices 102, 140, and/or 150 may be configured to operate in accordance with one or more Specifications, for example, including one or more IEEE 802.11 Specifications, e.g., an IEEE 802.11-2020 Specification, an IEEE 802.1 Ibe Specification, and/or any other specification and/or protocol.

[0084] In some demonstrative aspects, device 102, device 140, and/or device 150 may include, operate as, perform a role of, and/or perform the functionality of, one or more multi-link logical entities, e.g., as described below.

[0085] In other aspect, device 102, device 140, and/or device 150 may include, operate as, perform a role of, and/or perform the functionality of, any other entities, e.g., which are not multi-link logical entities. [0086] For example, a multi-link logical entity may include a logical entity that contains one or more STAs. The logical entity may have one MAC data service interface and primitives to the logical link control (LLC) and a single address associated with the interface, which can be used to communicate on a distribution system medium (DSM). For example, the DSM may include a medium or set of media used by a distribution system (DS) for communications between APs, mesh gates, and the portal of an extended service set (ESS). For example, the DS may include a system used to interconnect a set of basic service sets (BSSs) and integrated local area networks (LANs) to create an extended service set (ESS). In one example, a multi-link logical entity may allow STAs within the multi-link logical entity to have the same MAC address. The multi-link entity may perform any other additional or alternative functionality.

[0087] In some demonstrative aspects, device 102, device 140, and/or device 150 may include, operate as, perform a role of, and/or perform the functionality of, a Multi-Link Device (MLD). For example, device 102 may include, operate as, perform a role of, and/or perform the functionality of, at least one MLD, and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, at least one MLD, e.g., as described below.

[0088] For example, an MLD may include a device that is a logical entity and has more than one affiliated STA and has a single MAC service access point (SAP) to LLC, which includes one MAC data service. The MLD may perform any other additional or alternative functionality.

[0089] In some demonstrative aspects, for example, an infrastructure framework may include a multi-link AP logical entity, which includes APs, e.g., on one side, and a multi-link non-AP logical entity, which includes non-APs, e.g., on the other side.

[0090] In some demonstrative aspects, device 102, device 140, and/or device 150 may be configured to operate as, perform the role of, and/or perform one or more functionalities of, an AP MLD.

[0091] In some demonstrative aspects, device 102, device 140, and/or device 150 may be configured to operate as, perform the role of, and/or perform one or more functionalities of, a non-AP MLD. [0092] In other aspects, device 102, device 140, and/or device 150 may operate as, perform the role of, and/or perform one or more functionalities of, any other additional or alternative device and/or station.

[0093] For example, an AP MLD may include an MLD, where each STA affiliated with the MLD is an AP. In one example, the AP MLD may include a multi-link logical entity, where each STA within the multi-link logical entity is an EHT AP. The AP MLD may perform any other additional or alternative functionality.

[0094] For example, a non-AP MLD may include an MLD, where each STA affiliated with the MLD is a non-AP STA. In one example, the non-AP MLD may include a multi-link logical entity, where each STA within the multi-link logical entity is a non- AP EHT STA. The non-AP MLD may perform any other additional or alternative functionality.

[0095] In one example, a multi-link infrastructure framework may be configured as an extension from a one link operation between two STAs, e.g., an AP and a non-AP STA.

[0096] In some demonstrative aspects, controller 124 may be configured to cause, trigger, instruct and/or control device 102 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP MLD 131 including a plurality of AP STAs 133, e.g., including an AP STA 135, an AP STA 137 and/or an AP STA 139. In some aspects, as shown in Fig. 1, AP MLD 131 may include three AP STAs. In other aspects, AP MLD 131 may include any other number of AP STAs.

[0097] In one example, AP STA 135, AP STA 137 and/or AP STA 139 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an EHT AP STA. In other aspects, AP STA 135, AP STA 137 and/or AP STA 139 may perform any other additional or alternative functionality.

[0098] In some demonstrative aspects, for example, the one or more radios 114 may include, for example, a radio for communication by AP STA 135 over a first wireless communication frequency channel and/or frequency band, e.g., a 2.4GHz band, as described below.

[0099] In some demonstrative aspects, for example, the one or more radios 114 may include, for example, a radio for communication by AP STA 137 over a second wireless communication frequency channel and/or frequency band, e.g., a 5GHz band, as described below.

[00100] In some demonstrative aspects, for example, the one or more radios 114 may include, for example, a radio for communication by AP STA 139 over a third wireless communication frequency channel and/or frequency band, e.g., a 6GHz band, as described below.

[00101] In some demonstrative aspects, the radios 114 utilized by APs 133 may be implemented as separate radios. In other aspects, the radios 114 utilized by APs 133 may be implemented by one or more shared and/or common radios and/or radio components.

[00102] In other aspects, controller 124 may be configured to cause, trigger, instruct and/or control device 102 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, any other additional or alternative entity and/or STA, e.g., a single STA, multiple STAs, and/or a non-MLD entity.

[00103] In some demonstrative aspects, controller 154 may be configured to cause, trigger, instruct and/or control device 140 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an MLD 151 including a plurality of STAs 153, e.g., including a STA 155, a STA 157 and/or a STA 159. In some aspects, as shown in Fig. 1, MLD 151 may include three STAs. In other aspects, MLD 151 may include any other number of STAs.

[00104] In one example, STA 155, STA 157 and/or STA 159 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an EHT STA. In other aspects, STA 155, STA 157 and/or STA 159 may perform any other additional or alternative functionality.

[00105] In some demonstrative aspects, for example, the one or more radios 144 may include, for example, a radio for communication by STA 155 over a first wireless communication frequency channel and/or frequency band, e.g., a 2.4GHz band, as described below.

[00106] In some demonstrative aspects, for example, the one or more radios 144 may include, for example, a radio for communication by STA 157 over a second wireless communication frequency channel and/or frequency band, e.g., a 5GHz band, as described below.

[00107] In some demonstrative aspects, for example, the one or more radios 144 may include, for example, a radio for communication by STA 159 over a third wireless communication frequency channel and/or frequency band, e.g., a 6GHz band, as described below.

[00108] In some demonstrative aspects, the radios 144 utilized by STAs 153 may be implemented as separate radios. In other aspects, the radios 144 utilized by STAs 153 may be implemented by one or more shared and/or common radios and/or radio components.

[00109] In some demonstrative aspects, controller 154 may be configured to cause, trigger, instruct and/or control MLD 151 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a non-AP MLD. For example, STA 155, STA 157 and/or STA 159 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a non-AP EHT STA.

[00110] In some demonstrative aspects, controller 154 may be configured to cause, trigger, instruct and/or control MLD 151 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP MLD. For example, STA 155, STA 157 and/or STA 159 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP EHT STA.

[00111] In other aspects controller 154 may be configured to cause, trigger, instruct and/or control device 140 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, any other additional or alternative entity and/or STA, e.g., a single STA, multiple STAs, and/or a non-MLD entity.

[00112] Reference is made to Fig. 2, which schematically illustrates a multi-link communication scheme 200, which may be implemented in accordance with some demonstrative aspects.

[00113] As shown in Fig. 2, a first multi-link logical entity 202 (“multi-link logical entity 1”), e.g., a first MLD, may include a plurality of STAs, e.g., including a STA 212, a STA 214, and a STA 216. In one example, AP MLD 131 (Fig. 1) may perform one or more operations, one or more functionalities, the role of, and/or the functionality of, multi-link logical entity 202.

[00114] As shown in Fig. 2, a second multi-link logical entity 240 (“multi-link logical entity 2”), e.g., a second MLD, may include a plurality of STAs, e.g., including a STA 252, a STA 254, and a STA 256. In one example, MLD 151 (Fig. 1) may perform one or more operations, one or more functionalities, the role of, and/or the functionality of, multi-link logical entity 240.

[00115] As shown in Fig. 2, multi-link logical entity 202 and multi-link logical entity 240 may be configured to form, setup and/or communicate over a plurality of links, for example, including a link 272 between STA 212 and STA 252, a link 274 between STA 214 and STA 254, and/or a link 276 between STA 216 and STA 256.

[00116] Reference is made to Fig. 3, which schematically illustrates a multi-link communication scheme 300, which may be implemented in accordance with some demonstrative aspects.

[00117] As shown in Fig. 3, a multi-link AP logical entity 302, e.g., an AP MLD, may include a plurality of AP STAs, e.g., including an AP STA 312, an AP STA 314, and an AP STA 316. In one example, AP MLD 131 (Fig. 1) may perform one or more operations, one or more functionalities, the role of, and/or the functionality of, multilink AP logical entity 302.

[00118] As shown in Fig. 3, a multi-link non-AP logical entity 340, e.g., a non-AP MLD, may include a plurality of non-AP STAs, e.g., including a non-AP STA 352, a non-AP STA 354, and a non-AP STA 356. In one example, MLD 151 (Fig. 1) may perform one or more operations, one or more functionalities, the role of, and/or the functionality of, multi-link non-AP logical entity 340.

[00119] As shown in Fig. 3, multi-link AP logical entity 302 and multi-link non-AP logical entity 340 may be configured to form, setup and/or communicate over a plurality of links, for example, including a link 372 between AP STA 312 and non-AP STA 352, a link 374 between AP STA 314 and non-AP STA 354, and/or a link 376 between AP STA 316 and non-AP STA 356.

[00120] For example, as shown in Fig. 3, multi-link AP logical entity 302 may include a multi-band AP MLD, which may be configured to communicate over a plurality of wireless communication frequency bands. For example, as shown in Fig. 3, AP STA 312 may be configured to communicate over a 2.4GHz frequency band, AP STA 314 may be configured to communicate over a 5GHz frequency band, and/or AP STA 316 may be configured to communicate over a 6GHz frequency band. In other aspects, AP STA 312, AP STA 314, and/or AP STA 316, may be configured to communicate over any other additional or alternative wireless communication frequency bands.

[00121] Referring back to Fig. 1, in some demonstrative aspects, device 102, device 140, and/or device 150 may be configured to implement a low-latency wireless communication mechanism, which may be configured to provide a technical solution to support low-latency transmissions, e.g., very-low latency or ultra-low latency transmissions, in a wireless communication network, for example, a Wi-Fi network, e.g., as described below.

[00122] In some demonstrative aspects, the low-latency wireless communication mechanism may be configured to provide a technical solution to support emerging timesensitive wireless communications, e.g., as described below.

[00123] In some demonstrative aspects, devices 102, 140 and/or 150 may be configured to implement a low-latency wireless communication mechanism, which may be configured to provide a technical solution to support an efficient way to deliver a packet with a relatively low latency, e.g., as described below.

[00124] In some demonstrative aspects, there may be a need to provide a technical solution to support wireless communication of packets with a low latency.

[00125] For example, some wireless communication mechanisms, for example, a transmit opportunity (TxOP) mechanism and/or a frame aggregation mechanism, e.g., in accordance with the IEEE 802.11 Specification, may be implemented to increase the overall throughput of Wi-Fi devices. However, the frame aggregation mechanism may result in a relatively large PPDU data payload, which may occupy a much longer airtime.

[00126] For example, low latency applications may benefit, e.g., strongly, from small TxOP limits, for example, when operating in accordance with the IEEE 802.11 Specification. In contrast, high throughput applications may require long TxOPs, for example, to support more efficient use of resources, and/or to amortize an overhead of a sounding protocol.

[00127] In some demonstrative aspects, device 102 and/or device 140 may be configured to implement low latency wireless communication mechanism, which may be configured to provide a technical solution to support a coexistence between low latency applications and high throughput applications, e.g., as described below.

[00128] In some demonstrative aspects, device 102, device 140, and/or device 150 may be configured to communicate according to a preemption mechanism, which may be configured to provide a technical solution to support one or more STAs to preempt a wireless communication medium, for example, during a TxOP, e.g., as described below.

[00129] For example, a TxOP limit may be set to a relatively large value, e.g., 8 milliseconds (ms) or any other value, e.g., as described below.

[00130] For example, a TxOP may be configured to include one or more preemption periods, e.g., as described below.

[00131] For example, the TxOP may be configured to include a preemption pause, for example, every predefined duration of time, e.g., every 2ms, or any other time period.

[00132] For example, the preemption pause may be configured to give opportunity for high priority traffic to pre-empt the channel.

[00133] For example, the preemption period/pause may be set to a duration which is very short, for example, so that only very high priority devices could gain the channel during that pause.

[00134] For example, a TxOP holder and/or a TxOP responder of a TxOP, e.g., a relatively large TxOP, may be configured to pause/stop transmitting over a wireless communication medium, for example, during the one or more preemption periods/pauses in the TxOP.

[00135] For example, a contention period may be configured to start during the preemption period, for example, to allow for STAs to gain channel access.

[00136] For example, one or more preemption mechanisms may be defined to limit the number of users that can compete to access the medium during preemption period. [00137] For example, a STA that was a TxOP holder before the preemption period may stay the TxOP holder, for example, if no devices gained the channel during the preemption period/pause.

[00138] For example, according to a first mode of operation (simple mode), it may be defined that if a device gains the channel during the preemption period/pause, this device becomes a new TxOP holder of a new TxOP duration. For example, this new TxOP duration may be limited in time, e.g., to 2ms or any other duration. For example, it may be defined that a regular contention period may start at the end of the new TxOP.

[00139] For example, according to a second mode of operation (more complex mode), it may be defined that if a device gains the channel during the preemption period/pause, this device becomes a new TxOP holder for a max allowed duration. For example, a first TxOP holder of the initial TxOP may recover the TxOP for the remained of the initial TxOP. For example, the new TxOP holder may explicitly give back the TxOP to the first TxOP holder, e.g., through a signaling.

[00140] For example, it may be defined that during the preemption period/pause, a STA may gain the channel according to a contention mechanism, e.g., as described below.

[00141] For example, according to a first contention mechanism (a one-step contention) the channel may be gained by doing a regular backoff procedure and sending a packet to start occupying the medium when the backoff reaches zero, e.g., similar to a regular contention mechanism. For example, according to the first contention mechanism, there may be chances of collisions, e.g., if there are multiple STAs. For example, it may be defined that the first TxOP holder, e.g., a TxOP holder that stopped his TxOP to offer the preemption period, may be able to use the wireless communication medium again and stay the TxOP holder, for example, if the first TxOP holder didn’t receive a beginning of a packet, e.g., a Short Training Field (STF) or any other portion of a packet, before the duration of the preemption period duration.

[00142] For example, according to a second contention mechanism (two-step contention) I may be defined that during a first contention, STAs may send an STF, e.g., having a duration of 8 microseconds (us) or any other duration, when their backoff reaches zero, and may participate in a second contention. [00143] For example, it may be defined that there may be no backoffs during the first contention. For example, competing STAs that have traffic to send and are eligible to compete for a preemption period may be allowed to send an STF after a predefined time, for example, after a Short Interframe Space (SIFS).

[00144] For example, other competing STAs that may receive the STF frame may have their Clear Channel Assessment (CCA) busy and may stop contending.

[00145] For example, it may be defined that the first TxOP holder, which stopped his TxOP to offer the preemption period, may use the medium again and stay the TxOP holder, for example, if the first TxOP holder didn’t receive an STF before the duration of the first preemption period ends.

[00146] For example, it may be defined that the first TxOP holder may lose the TxOP and may not transmit at the end of the first preemption period, for example, if the first TxOP holder receives an STF during the first preemption period. For example, a second contention period may happen between the STAs that won the first contention in the first preemption period.

[00147] For example, it may be defined that, during the second contention period, only the STAs that won the first contention may have a full Enhanced Distributed Channel Access (EDCA) backoff to gain channel access. For example, a STA may gain channel access, for example, when the backoff reaches zero with the channel staying idle, e.g., similar to a regular EDCA backoff.

[00148] For example, the second contention mechanism may provide a technical solution to allow to reduce a size of the preemption period. This reduced size of the preemption period may come at a cost of increased complexity of the contention mechanism.

[00149] Reference is made to Fig. 4, which schematically illustrates a TxOP 402 configured according to a preemption mechanism, in accordance with some demonstrative aspects.

[00150] For example, device 102 (Fig. 1) and/or device 140 (Fig. 1) may communicate according to the preemption mechanism of Fig. 4. [00151] For example, a wireless communication device, e.g., device 102 (Fig. 1), may contend to obtain TxOP 402, for example, based on contention during a full contention period 401 according to a contention mechanism.

[00152] For example, as shown in Fig. 4, TxOP 402 may be configured to include one or more transmission periods, e.g., a transmission period 404, a transmission period 406, a transmission period 408, and/or a transmission period 410.

[00153] For example, as shown in Fig. 4, a transmission period, e.g., each transmission period, of the transmission periods of TxOP 402 may be configured to have a duration of 2ms, or any other duration.

[00154] For example, as shown in Fig. 4, TxOP 402 may include one or more preemption periods.

[00155] For example, a preemption period may be configured between two neighboring transmission durations.

[00156] For example, TxOP 402 may include a preemption period 403 between transmission period 404 and transmission period 406.

[00157] For example, the preemption period 403 may be configured to allow one or more preempt-eligible STAs, e.g., device 140 (Fig. 1), to communicate over the wireless communication channel during the TxOP 402.

[00158] For example, preemption period 403 may be configured to have a relatively short duration, e.g., a SIFS duration or any other duration, for example, so that only a STA having very high priority traffic to transmit, e.g., a preempt-eligible STA, may be able to gain access to the wireless communication channel during preemption period 403.

[00159] For example, a holder STA of TxOP 402 may pause communicating over the wireless communication channel during preemption period 403, for example, to allow one or more preempt-eligible STAs to contend for the wireless communication channel during a contention period.

[00160] For example, non-preempt-eligible STAs, e.g., device 150 (Fig. 1), may be prohibited from communicating over the wireless communication channel during preemption period 403. [00161] Referring back to Fig. 1, in some demonstrative aspects, device 102 and/or device 140 may be configured to implement a protection mechanism to protect a TxOP over a wireless communication channel, for example, according to a preemption-based protection scheme, e.g., as described below.

[00162] In some demonstrative aspects, the preemption-based protection scheme may be configured to provide a technical solution to support a TxOP holder of a TxOP, which is to transmit a PPDU to an intended receiver, to protect its TxOP, for example, while still allowing one or more preempt-eligible STAs to access the wireless communication medium during one or more preemption periods.

[00163] In some demonstrative aspects, the preemption-based protection scheme may be configured to provide a technical solution to support protection of the TxOP, for example, with regards to hidden nodes.

[00164] In some demonstrative aspects, the protection mechanism may be configured to utilize, for example, an exchange of Request to Send (RTS)/Clear to Send (CTS) frames, e.g., as described below.

[00165] In some demonstrative aspects, the protection mechanism may be based on definition of Network Allocation Vector (NAV) setting rules, e.g., as described below.

[00166] In some demonstrative aspects, the protection mechanism may be based on modification of the NAV setting rules, for example, defined in accordance with the IEEE 802.11 Specification, e.g., as described below.

[00167] In some demonstrative aspects, the protection mechanism may be defined that an AP is to signal a preemption period, e.g., as described below.

[00168] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to transmit protection information to signal that a TxOP over a wireless communication channel is to be protected, for example, according to a preemption-based protection scheme, e.g., as described below.

[00169] In some demonstrative aspects, the TxOP may include a preemption period between a first transmission period and a second transmission period, e.g., as described below. [00170] For example, device 102 may be configured to transmit protection information to signal that TxOP 402 (Fig. 4), which includes preemption period 403 (Fig. 4), is to be protected according to the preemption-based protection scheme.

[00171] In some demonstrative aspects, the preemption period may have a duration of at least 2ms, e.g., as described above. In other aspects, the preemption period may have any other duration.

[00172] In some demonstrative aspects, the preemption-based protection scheme may be configured to allow one or more preempt-eligible STAs to communicate over the wireless communication channel during the preemption period, e.g., as described below.

[00173] For example, the preemption-based protection scheme may allow a preempt- eligible STA, e.g., a STA implemented by device 140, to communicate over the wireless communication channel during the preemption period 403 (Fig. 4).

[00174] In some demonstrative aspects, the one or more preempt-eligible STAs may include one or more high-priority STAs allowed to preempt the wireless communication channel to communicate high-priority traffic.

[00175] In some demonstrative aspects, the one or more preempt-eligible STAs may include one or more Ultra-Low-Latency (ULL) STAs.

[00176] In other aspects, the one or more preempt-eligible STAs may include any other type of STA.

[00177] In some demonstrative aspects, the preemption-based protection scheme may be configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period, e.g., as described below.

[00178] For example, the preemption-based protection scheme may be configured to prohibit a non-preempt-eligible STA, e.g., a STA implemented by device 150, from communicating over the wireless communication channel during the preemption period 403 (Fig. 4).

[00179] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to pause communication over the wireless communication channel during the preemption period, for example, to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic, e.g., as described below.

[00180] For example, a TxOP holder, e.g., device 102, may pause communication over the wireless communication channel during the preemption period 403 (Fig. 3), for example, to provide an opportunity to a preempt-eligible STA, e.g., a STA implemented by device 140, to preempt the wireless communication channel to communicate traffic.

[00181] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to configure the protection information to include information configured to set a NAV to protect the preemption period, for example, according to the preemption-based protection scheme, e.g., as described below.

[00182] In some demonstrative aspects, the protection information may include information configured to set the NAV for a duration covering an entire duration of the TxOP, e.g., as described below.

[00183] In some demonstrative aspects, the protection information may include information configured to set the NAV for a duration covering at least the first transmission period and the preemption period, e.g., as described below.

[00184] In some demonstrative aspects, the protection information may include information configured to set the NAV for a duration covering the first transmission period, the preemption period, and one or more time slots following the preemption period, e.g., as described below.

[00185] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to transmit other protection information configured to reset the NAV for a duration covering the second transmission period, for example, based on a determination that no preempt-eligible STA has gained the wireless communication channel during the preemption period, e.g., as described below.

[00186] In some demonstrative aspects, the other protection information may be configured to reset the NAV, for example, for a duration covering the second transmission period and a subsequent preemption period between the second transmission period and a third transmission period, e.g., as described below.

[00187] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to identify a preemption request from a preempt-eligible STA, for example, based on a signal received from the preempt- eligible STA during the preemption period, e.g., as described below.

[00188] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to transmit a trigger to trigger a transmission from the preempt-eligible STA, for example, based on the preemption request, e.g., as described below.

[00189] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to identify the preempt-eligible STA, for example, based on a predefined signature in the signal, e.g., as described below.

[00190] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to configure the protection information to include a duration value in a duration field, e.g., as described below.

[00191] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to transmit a frame over the wireless communication channel, e.g., as described below.

[00192] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to configure the frame to include an RTS or a CTS-to-self, e.g., as described below.

[00193] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to configure the frame to include the duration field including the duration value, e.g., as described below.

[00194] In some demonstrative aspects, controller 124 may be configured to control, trigger, cause, and/or instruct device 102 to transmit a PPDU including the duration field over the wireless communication channel, e.g., as described below.

[00195] In some demonstrative aspects, the PPDU may be configured to include a PSDU including the duration field, e.g., as described below. [00196] In some demonstrative aspects, the PPDU may include a PHY header including a TxOP duration field, which may include the duration value, e.g., as described below.

[00197] In other aspects, the duration field may be included in any other part of the PPDU.

[00198] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to identify, based on protection information from a TxOP holder, e.g., the TxOP holder implemented by device 102, that a TxOP over a wireless communication channel is to be protected according to a preemptionbased protection scheme, e.g., as described below.

[00199] In some demonstrative aspects, the TxOP may be configured to include a preemption period between a first transmission period and a second transmission period, e.g., as described above.

[00200] In some demonstrative aspects, the preemption-based protection scheme may be configured to allow one or more preempt-eligible STAs to communicate over the wireless communication channel during the preemption period, e.g., as described above.

[00201] For example, a preempt-eligible STA, e.g., a STA implemented by device 140, may communicate over the wireless communication channel during the preemption period, for example, according to the preemption-based protection scheme.

[00202] In some demonstrative aspects, the preemption-based protection scheme may be configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period, e.g., as described above.

[00203] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to allow a preempt-eligible STA of the wireless communication device 140 to communicate over the wireless communication channel during the preemption period, for example, to preempt the wireless communication channel to transmit traffic. [00204] In some demonstrative aspects, the protection information may include information configured to set a NAV to protect the preemption period, for example, according to the preemption-based protection scheme, e.g., as described above.

[00205] In some demonstrative aspects, the protection information may include information configured to set the NAV for a duration covering an entire duration of the TxOP, e.g., as described above.

[00206] In some demonstrative aspects, the protection information may include information configured to set the NAV for a duration covering at least the first transmission period and the preemption period, e.g., as described above.

[00207] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to, based on a determination that the preempt- eligible STA of device 140 has gained the wireless communication channel, cause the preempt-eligible STA device 140 to transmit an RTS frame, for example, prior to transmitting the traffic over the wireless communication channel, e.g., as described below.

[00208] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to transmit a signal from the preempt-eligible STA of device 140 during the preemption period, e.g., as described below.

[00209] In some demonstrative aspects, the signal may be configured to indicate a preemption request from the preempt-eligible STA of device 140, e.g., as described below.

[00210] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to transmit the traffic from the preempt- eligible STA of device 140, for example, based on receipt of a trigger from the TxOP holder after transmission of the signal from the preempt-eligible STA of device 140, e.g., as described below.

[00211] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to configure the signal transmitted to the TxOP holder during the preemption period to include a predefined signature to identify the preempt-eligible STA of device 140, e.g., as described below. [00212] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to identify a duration value, for example, based on the protection information received from the TxOP holder, e.g., as described below.

[00213] In some demonstrative aspects, the protection information may be configured to include the duration value in a duration field, e.g., as described below.

[00214] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to process a frame received from the TxOP holder over the wireless communication channel, e.g., as described below.

[00215] In some demonstrative aspects, the frame may include an RTS or a CTS-to- self.

[00216] In some demonstrative aspects, the frame may include the duration field.

[00217] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to process a PPDU received from the TxOP holder over the wireless communication channel, e.g., as described below.

[00218] In some demonstrative aspects, the PPDU may include a PSDU including the duration field.

[00219] In some demonstrative aspects, the PPDU may include a PHY header including a TxOP duration field, which may include the duration value.

[00220] In other aspects, the duration field may be included in any other part of the PPDU.

[00221] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to process the protection information from the TxOP holder to identify information configured to set a NAV to protect the preemption period according to the preemption-based protection scheme, e.g., as described below.

[00222] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to allow the preempt-eligible STA of device 140 to ignore the NAV, e.g., as described below.

[00223] In some demonstrative aspects, controller 154 may be configured to control, trigger, cause, and/or instruct device 140 to allow the preempt-eligible STA of device 140 to ignore the NAV, for example, based on a determination that the preempt-eligible STA of device 140 belongs to a same BSS as the TxOP holder, e.g., as described below.

[00224] In some demonstrative aspects, device 102 and/or device 140 may be configured to implement a preemption-based protection scheme to protect a TxOP over a wireless communication channel, e.g., as described below.

[00225] For example, it may be defined that a TxOP holder, e.g., a TxOP holder implemented by device 102, which is to transmit a PPDU to one or more intended receivers during a TxOP, may protect the TxOP, for example, while still allowing one or more STAs, e.g., preempt-eligible STAs, that are eligible to access the medium during the preemption phases, to access the wireless communication medium during the preemption periods.

[00226] In some demonstrative aspects, it may be defined that the TxOP holder is to set a NAV for one or more, e.g., all, STAs receiving a PPDU from the TxOP holder.

[00227] In some demonstrative aspects, the TxOP holder may set the NAV, for example, by sending an RTS or CTS-to-self frame.

[00228] In some demonstrative aspects, the TxOP holder may set the NAV, for example, by setting a duration field of PSDUs in the PPDU.

[00229] In some demonstrative aspects, the TxOP holder may set the NAV, for example, by using a TxOP duration field in a PHY header, for example, to set the NAV for an entire duration of the TxOP.

[00230] In some demonstrative aspects, it may be defined that NAV setting rules are to be modified, for example, to define a set of preempt-eligible STAs, which are eligible to preempt during the TxOP.

[00231] In some demonstrative aspects, it may be defined, for example, according to modified NAV setting rules, that the preempt-eligible STAs that want to preempt the PPDU during the TxOP, may be allowed to ignore the NAV that has been set by the TxOP holder.

[00232] In one example, the preempt-eligible STAs may be allowed to ignore the NAV that has been set by the TxOP holder, for example, when the TxOP holder shares the same BSS. [00233] In another example, the preempt-eligible STAs may be allowed to always ignore their NAV.

[00234] In some demonstrative aspects, it may be defined that the preempt-eligible STAs may be able to participate in a short contention during a preemption period during the TxOP, e.g., within the PPDU.

[00235] For example, it may be defined that the preempt-eligible STAs are to set the NAV to other STAs, for example, when the preempt-eligible STAs gain control of the wireless communication channel and start transmitting. For example, it may be defined that the preempt-eligible STAs may be allowed to set the NAV for a duration defined by a preemption mechanism, for example, for a duration of 2ms and/or any other duration.

[00236] For example, STAs that initially set their NAV based on an initial PPDU from the TxOP holder may or may not receive the transmission from the preempting STA. Accordingly, these STAs will keep their NAV set, for example, until the end of the planned TxOP, for example, if the first NAV was larger than the NAV set by the preemptable STA. In some cases, such a situation may result in inefficiencies.

[00237] In some demonstrative aspects, it may be mandated that the preemptable STA sends a Contention Free (CF) end (CF-end) frame at the end of its preempted TxOP, or sends a frame that gives the TxOP back to the first TxOP holder, for example, possibly reusing a mechanism of a Multi- AP TDMA.

[00238] In some demonstrative aspects, a TxOP holder, e.g., the TxOP holder implemented by device 102, may be configured to communicate protection information to signal that the TxOP is to be protected, for example, according to a preemption-based protection scheme, e.g., as described above.

[00239] In some demonstrative aspects, the protection information may include a duration value in a duration field, e.g., as described below.

[00240] In some demonstrative aspects, it may be defined that a TxOP duration field in a PHY header may include information configured to set a NAV, for example, according to the preemption-based protection scheme. [00241] For example, it may be defined that the NAV is to be set, e.g., by the information in the TxOP duration field, to cover a duration only until a few slots after an end of a first preemption period.

[00242] For example, the NAV may be reset, for example, every short 2ms PPDU.

[00243] In some demonstrative aspects, the NAV setting rules may be configured, e.g., modified, for example, to define a set of STAs that are eligible to preempt during the TxOP, e.g., preempt-eligible STAs.

[00244] In some demonstrative aspects, it may be defined that in case the preemptable STAs want to preempt the PPDU, the preemptable STAs may be allowed to ignore the NAV that has been set by the TxOP holder, for example, if the TxOP holder is in the same BSS as the preemptable STAs. In other aspects, it may be defined that the preemptable STAs may be allowed to always ignore their NAV.

[00245] For example, the preemptable STAs may be able to participate in a short contention during the preemption period within the PPDU, e.g., as described above.

[00246] For example, it may be defined that if the preemptable STAs gain channel and start transmitting, then the preemptable STAs are to set the NAV to other STAs.

[00247] For example, it may be defined that the preemptable STAs are only allowed to set the NAV for the duration that is allowed by the preemption protocol, for example, 2ms or any other duration.

[00248] In some demonstrative aspects, device 102 and/or device 140 may be configured to implement a preemption-based protection scheme, which may be configured to protect communications during a TxOP over a wireless communication channel, for example, with regard to hidden nodes, e.g., as described below.

[00249] In some demonstrative aspects, a TxOP holder may be implemented by an AP, and/or a preempt-eligible STA may be implemented by a non-AP STA.

[00250] For example, in some use cases, implementations and/or scenarios, there may be hidden nodes, which may not be able to receive transmissions from a preempt- eligible STA that gained the wireless communication channel.

[00251] In some demonstrative aspects, it may be defined, e.g., mandated, that the preempt-eligible STA, e.g., unless it is an AP, is to start access to a preemption period, for example, by transmitting an RTS/CTS frame, for example, prior to transmitting traffic over the wireless communication channel. For example, an RTS frame format may be changed, e.g., modified, for example, in order to indicate to an intended receiver that the receiver may ignore its NAV and to respond with a CTS frame.

[00252] In some demonstrative aspects, it may be defined, e.g., mandated, that a preemption the RTS/CTS exchange is to be implemented to protect the transmission from the preempt-eligible STA, for example, only when a TxOP holder is a STA and/or the preempt-eligible STA is an AP.

[00253] In some demonstrative aspects, a TxOP holder implemented by an AP device, e.g., device 102, may be configured to control protection of a TxOP over a wireless communication channel, for example, according to an AP-controlled preemption-based protection scheme, e.g., as described below.

[00254] In some demonstrative aspects, it may be defined that only the AP, e.g., the TxOP holder, is allowed to trigger a preemption period within its TxOPs.

[00255] For example, it may be defined that a PHY header of a PPDU that is transmitted by the TxOP holder and is to get the preemption period may include a signaling that indicates when the preemption period is to start.

[00256] For example, the information in the PHY header may include one or more parameters for preempt-eligible STAs to participate and/or respond to the preemption period that they want to gain access to the medium.

[00257] In some demonstrative aspects, the AP, e.g., the TxOP holder, may stop transmission of the PPDU, for example, during the preemption period (gap).

[00258] For example, a SIF or any other duration after the beginning of the preemption period, the preempt-eligible STAs that want to compete for the preemption period may send a signaling, e.g., a short signal, to the AP. For example, this signaling may include a signature for the STA. For example, the signature may be assigned to the STA by the AP. For example, the signature may be configured such that the AP may receive the short signal and determine which STA has made a request to preempt, for example, based on the signature in the short signal.

[00259] In some demonstrative aspects, it may be defined that the signature in the short signal is to be orthogonal to other signatures assigned to other preempt-eligible STAs. For example, two or more, e.g., multiple, preempt-eligible STAs may be allowed to request to gain access to the preemption period at the same time, for example, while still allowing the AP to determine which STAs made a request.

[00260] In one example, the short signal may be configured to include a new signal, which does not replicate any current preamble signaling, for example, assuming that all STAs participating in a PPDU communication are preempt-eligible STAs.

[00261] In another example, the short signal may be configured to reuse fields, e.g., such as a non-High-Throughput (non-HT), e.g., legacy, Short Training Field (L-STF), a non-HT )legacy) Long Training Field (L-LTF), and/or a High Throughput (HT)/High Efficiency (HE) type LTF, where there are some shifts in either time or frequency of a waveform. For example, the short signal may be configured to have an overlay placed upon these fields.

[00262] For example, it may be defined that once the signaling including a preemption request signal is sent and/or received by the AP, a SIFS or any other time after, the AP may send a trigger frame to one or more preempt-eligible STAs that made the preemption request. For example, the one or more preempt-eligible STAs may transmit their urgent frames, for example, after receiving the trigger frame from the AP. According to this example, other STAs that receive the trigger from the AP may set their NAV appropriately.

[00263] Reference is made to Fig. 5, which schematically illustrates a method of communicating during a TxOP over a wireless communication channel, in accordance with some demonstrative aspects. For example, one or more of the operations of the method of Fig. 5 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1), an MLD, e.g., MLD 131 (Fig. 1) and/or MLD 151 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).

[00264] As indicated at block 502, the method may include transmitting, from a wireless communication device, protection information to signal that a TxOP over a wireless communication channel is to be protected according to a preemption-based protection scheme. For example, the TxOP may include a preemption period between a first transmission period and a second transmission period. For example, the preemption-based protection scheme may be configured to allow one or more preempt- eligible STAs to communicate over the wireless communication channel during the preemption period. For example, the preemption-based protection scheme may be configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to transmit the protection information to signal that the TxOP 402 (Fig. 4) is to be protected according to the preemption-based protection scheme, e.g., as described above.

[00265] As indicated at block 504, the method may include pausing communication over the wireless communication channel during the preemption period to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to pause communication over the wireless communication channel during the preemption period 403 (Fig. 4), for example, to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic, e.g., as described above.

[00266] Reference is made to Fig. 6, which schematically illustrates a method of communicating during a TxOP over a wireless communication channel, in accordance with some demonstrative aspects. For example, one or more of the operations of the method of Fig. 6 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1), an MLD, e.g., MLD 131 (Fig. 1) and/or MLD 151 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).

[00267] As indicated at block 602, the method may include identifying, at a wireless communication device, that a TxOP over a wireless communication channel is to be protected according to a preemption-based protection scheme, for example, based on protection information from a TxOP holder. For example, the TxOP may include a preemption period between a first transmission period and a second transmission period. For example, the preemption-based protection scheme may be configured to allow one or more preempt-eligible STAs to communicate over the wireless communication channel during the preemption period. For example, the preemptionbased protection scheme may be configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to identify, based on protection information from a TxOP holder, that a TxOP over a wireless communication channel is to be protected according to a preemption-based protection scheme, e.g., as described above.

[00268] As indicated at block 604, the method may include allowing a preempt-eligible STA of the wireless communication device to communicate over the wireless communication channel during the preemption period to preempt the wireless communication channel to transmit traffic. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to allow a preempt- eligible STA of device 140 (Fig. 1) to communicate over the wireless communication channel during the preemption period to preempt the wireless communication channel to transmit traffic, e.g., as described above.

[00269] Reference is made to Fig. 7, which schematically illustrates a product of manufacture 700, in accordance with some demonstrative aspects. Product 700 may include one or more tangible computer-readable (“machine-readable”) non-transitory storage media 702, which may include computer-executable instructions, e.g., implemented by logic 704, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at device 102 (Fig. 1), device 140 (Fig. 1), MLD 131 (Fig. 1), MLD 151 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), receiver 146 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), controller 124 (Fig. 1), and/or controller 154 (Fig. 1), to cause device 102 (Fig. 1), device 140 (Fig. 1), MLD 131 (Fig. 1), MLD 151 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), receiver 146 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), controller 124 (Fig. 1), and/or controller 154 (Fig. 1), to perform, trigger and/or implement one or more operations and/or functionalities, and/or to perform, trigger and/or implement one or more operations and/or functionalities described with reference to the Figs. 1, 2, 3, 4, 5, and/or 6, and/or one or more operations described herein. The phrases “non-transitory machine-readable medium” and “computer-readable non-transitory storage media” may be directed to include all machine and/or computer readable media, with the sole exception being a transitory propagating signal.

[00270] In some demonstrative aspects, product 700 and/or machine-readable storage media 702 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or nonremovable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine-readable storage media 802 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide- silicon (SONOS) memory, a disk, a hard drive, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.

[00271] In some demonstrative aspects, logic 704 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

[00272] In some demonstrative aspects, logic 704 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, machine code, and the like.

EXAMPLES

[00273] The following examples pertain to further aspects.

[00274] Example 1 includes an apparatus comprising logic and circuitry configured to cause a wireless communication device to transmit protection information to signal that a Transmit Opportunity (TxOP) over a wireless communication channel is to be protected according to a preemption-based protection scheme, wherein the TxOP comprises a preemption period between a first transmission period and a second transmission period, wherein the preemption-based protection scheme is configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, wherein the preemption-based protection scheme is configured to prohibit non- preempt-eligible STAs from communicating over the wireless communication channel during the preemption period; and pause communication over the wireless communication channel during the preemption period to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic.

[00275] Example 2 includes the subject matter of Example 1, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering an entire duration of the TxOP.

[00276] Example 3 includes the subject matter of Example 1, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering at least the first transmission period and the preemption period. [00277] Example 4 includes the subject matter of Example 3, and optionally, wherein the protection information comprises information configured to set the NAV for a duration covering the first transmission period, the preemption period, and one or more time slots following the preemption period.

[00278] Example 5 includes the subject matter of Example 3 or 4, and optionally, wherein the apparatus is configured to cause the wireless communication device to, based on a determination that no preempt-eligible STA has gained the wireless communication channel during the preemption period, transmit other protection information configured to reset the NAV for a duration covering the second transmission period.

[00279] Example 6 includes the subject matter of Example 5, and optionally, wherein the other protection information is configured to reset the NAV for a duration covering the second transmission period and a subsequent preemption period between the second transmission period and a third transmission period.

[00280] Example 7 includes the subject matter of any one of Examples 1-6, and optionally, wherein the apparatus is configured to cause the wireless communication device to identify a preemption request from a preempt-eligible STA based on a signal received from the preempt-eligible STA during the preemption period, and, based on the preemption request, transmit a trigger to trigger a transmission from the preempt- eligible STA.

[00281] Example 8 includes the subject matter of Example 7, and optionally, wherein the apparatus is configured to cause the wireless communication device to identify the preempt-eligible STA based on a predefined signature in the signal.

[00282] Example 9 includes the subject matter of any one of Examples 1-8, and optionally, wherein the protection information comprises a duration value in a duration field.

[00283] Example 10 includes the subject matter of Example 9, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit a frame over the wireless communication channel, the frame comprising a Request to Send (RTS) or a Clear-to-Send-to-self (CTS-to-self), the frame comprising the duration field. [00284] Example 11 includes the subject matter of Example 9, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit a Physical layer (PHY) Protocol Data Unit (PPDU) over the wireless communication channel, the PPDU comprising a PHY Service Data Unit (PSDU), the PSDU comprising the duration field.

[00285] Example 12 includes the subject matter of Example 9, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit a Physical layer (PHY) Protocol Data Unit (PPDU) over the wireless communication channel, the PPDU comprising a PHY header comprising a TxOP duration field, the TxOP duration field comprising the duration value.

[00286] Example 13 includes the subject matter of any one of Examples 1-12, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) to protect the preemption period according to the preemption-based protection scheme.

[00287] Example 14 includes the subject matter of any one of Examples 1-13, and optionally, wherein the preemption period has a duration of at least 2 milliseconds (ms).

[00288] Example 15 includes the subject matter of any one of Examples 1-14, and optionally, wherein the one or more preempt-eligible STAs comprises one or more high-priority STAs allowed to preempt the wireless communication channel to communicate high-priority traffic.

[00289] Example 16 includes the subject matter of any one of Examples 1-15, and optionally, wherein the one or more preempt-eligible STAs comprises one or more Ultra- Low-Latency (ULL) STAs.

[00290] Example 17 includes the subject matter of any one of Examples 1-16, and optionally, comprising at least one radio to communicate over the wireless communication channel.

[00291] Example 18 includes the subject matter of Example 17, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the wireless communication device.

[00292] Example 19 includes an apparatus comprising logic and circuitry configured to cause a wireless communication device to identify, based on protection information from a Transmit Opportunity (TxOP) holder, that a TxOP over a wireless communication channel is to be protected according to a preemption-based protection scheme, wherein the TxOP comprises a preemption period between a first transmission period and a second transmission period, wherein the preemption-based protection scheme is configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, wherein the preemption-based protection scheme is configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period; and allow a preempt-eligible STA of the wireless communication device to communicate over the wireless communication channel during the preemption period to preempt the wireless communication channel to transmit traffic.

[00293] Example 20 includes the subject matter of Example 19, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering an entire duration of the TxOP.

[00294] Example 21 includes the subject matter of Example 19, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering at least the first transmission period and the preemption period.

[00295] Example 22 includes the subject matter of Example 21, and optionally, wherein the protection information comprises information configured to set the NAV for a duration covering the first transmission period, the preemption period, and one or more time slots following the preemption period.

[00296] Example 23 includes the subject matter of Example 21 or 22, and optionally, wherein the apparatus is configured to cause the wireless communication device to, based on a determination that the preempt-eligible STA of the wireless communication device has gained the wireless communication channel, cause the preempt-eligible STA of the wireless communication device to transmit a Request to Send (RTS) frame prior to transmitting the traffic over the wireless communication channel.

[00297] Example 24 includes the subject matter of any one of Examples 19-23, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit a signal from the preempt-eligible STA of the wireless communication device during the preemption period, the signal configured to indicate a preemption request from the preempt-eligible STA of the wireless communication device.

[00298] Example 25 includes the subject matter of Example 24, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit the traffic from the preempt-eligible STA of the wireless communication device, based on receipt of a trigger from the TxOP holder after transmission of the signal from the preempt-eligible STA of the wireless communication device.

[00299] Example 26 includes the subject matter of Example 24 or 25, and optionally, wherein the signal comprises a predefined signature to identify the preempt-eligible STA of the wireless communication device.

[00300] Example 27 includes the subject matter of any one of Examples 19-26, and optionally, wherein the protection information comprises a duration value in a duration field.

[00301] Example 28 includes the subject matter of Example 27, and optionally, wherein the apparatus is configured to cause the wireless communication device to process a frame received from the TxOP holder over the wireless communication channel, the frame comprising a Request to Send (RTS) or a Clear-to-Send-to-self (CTS-to-self), the frame comprising the duration field.

[00302] Example 29 includes the subject matter of Example 27, and optionally, wherein the apparatus is configured to cause the wireless communication device to process a Physical layer (PHY) Protocol Data Unit (PPDU) received from the TxOP holder over the wireless communication channel, the PPDU comprising a PHY Service Data Unit (PSDU), the PSDU comprising the duration field.

[00303] Example 30 includes the subject matter of Example 27, and optionally, wherein the apparatus is configured to cause the wireless communication device to process a Physical layer (PHY) Protocol Data Unit (PPDU) received from the TxOP holder over the wireless communication channel, the PPDU comprising a PHY header comprising a TxOP duration field, the TxOP duration field comprising the duration value. [00304] Example 31 includes the subject matter of any one of Examples 19-30, and optionally, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) to protect the preemption period according to the preemption-based protection scheme.

[00305] Example 32 includes the subject matter of Example 31, and optionally, wherein the apparatus is configured to cause the wireless communication device to allow the preempt-eligible STA of the wireless communication device to ignore the NAV.

[00306] Example 33 includes the subject matter of Example 31 or 32, and optionally, wherein the apparatus is configured to cause the wireless communication device to, based on a determination that the preempt-eligible STA of the wireless communication device belongs to a same Basic Service Set (BSS) as the TxOP holder, allow the preempt-eligible STA of the wireless communication device to ignore the NAV.

[00307] Example 34 includes the subject matter of any one of Examples 19-33, and optionally, wherein the preemption period has a duration of at least 2 milliseconds (ms).

[00308] Example 35 includes the subject matter of any one of Examples 19-34, and optionally, wherein the preempt-eligible STA of the wireless communication device comprises a high-priority STA allowed to preempt the wireless communication channel to communicate high-priority traffic.

[00309] Example 36 includes the subject matter of any one of Examples 19-35, and optionally, wherein the preempt-eligible STA of the wireless communication device comprises an Ultra-Low-Latency (ULL) STA.

[00310] Example 37 includes the subject matter of any one of Examples 19-36, and optionally, comprising at least one radio to communicate over the wireless communication channel.

[00311] Example 38 includes the subject matter of Example 37, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the wireless communication device.

[00312] Example 39 comprises a wireless communication device comprising the apparatus of any of Examples 1-38. [00313] Example 40 comprises an apparatus comprising means for executing any of the described operations of any of Examples 1-38.

[00314] Example 41 comprises a product comprising one or more tangible computer- readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a wireless communication device to perform any of the described operations of any of Examples 1-38.

[00315] Example 42 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of any of Examples 1-38.

[00316] Example 43 comprises a method comprising any of the described operations of any of Examples 1-38.

[00317] Functions, operations, components and/or features described herein with reference to one or more aspects, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other aspects, or vice versa.

[00318] While certain features have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Claims

CLAIMS What is claimed is:

1. An apparatus comprising logic and circuitry configured to cause a wireless communication device to: transmit protection information to signal that a Transmit Opportunity (TxOP) over a wireless communication channel is to be protected according to a preemptionbased protection scheme, wherein the TxOP comprises a preemption period between a first transmission period and a second transmission period, wherein the preemptionbased protection scheme is configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, wherein the preemption-based protection scheme is configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period; and pause communication over the wireless communication channel during the preemption period to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic.

2. The apparatus of claim 1, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering an entire duration of the TxOP.

3. The apparatus of claim 1, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) for a duration covering at least the first transmission period and the preemption period.

4. The apparatus of claim 3, wherein the protection information comprises information configured to set the NAV for a duration covering the first transmission period, the preemption period, and one or more time slots following the preemption period.

5. The apparatus of claim 3 configured to cause the wireless communication device to, based on a determination that no preempt-eligible STA has gained the wireless communication channel during the preemption period, transmit other protection information configured to reset the NAV for a duration covering the second transmission period.

6. The apparatus of claim 5, wherein the other protection information is configured to reset the NAV for a duration covering the second transmission period and a subsequent preemption period between the second transmission period and a third transmission period.

7. The apparatus of any one of claims 1-6 configured to cause the wireless communication device to identify a preemption request from a preempt-eligible STA based on a signal received from the preempt-eligible STA during the preemption period, and, based on the preemption request, transmit a trigger to trigger a transmission from the preempt-eligible STA.

8. The apparatus of claim 7 configured to cause the wireless communication device to identify the preempt-eligible STA based on a predefined signature in the signal.

9. The apparatus of any one of claims 1-6, wherein the protection information comprises a duration value in a duration field.

10. The apparatus of claim 9 configured to cause the wireless communication device to transmit a frame over the wireless communication channel, the frame comprising a Request to Send (RTS) or a Clear-to-Send-to-self (CTS-to-self), the frame comprising the duration field.

11. The apparatus of claim 9 configured to cause the wireless communication device to transmit a Physical layer (PHY) Protocol Data Unit (PPDU) over the wireless communication channel, the PPDU comprising a PHY Service Data Unit (PSDU), the PSDU comprising the duration field.

12. The apparatus of claim 9 configured to cause the wireless communication device to transmit a Physical layer (PHY) Protocol Data Unit (PPDU) over the wireless communication channel, the PPDU comprising a PHY header comprising a TxOP duration field, the TxOP duration field comprising the duration value.

13. The apparatus of any one of claims 1-6, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) to protect the preemption period according to the preemption-based protection scheme.

14. The apparatus of any one of claims 1-6, wherein the preemption period has a duration of at least 2 milliseconds (ms).

15. The apparatus of any one of claims 1-6, wherein the one or more preempt- eligible STAs comprises one or more high-priority STAs allowed to preempt the wireless communication channel to communicate high-priority traffic.

16. The apparatus of any one of claims 1-6, wherein the one or more preempt- eligible STAs comprises one or more Ultra-Low-Latency (ULL) STAs.

17. The apparatus of any one of claims 1-6 comprising at least one radio to communicate over the wireless communication channel.

18. The apparatus of claim 17 comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the wireless communication device.

19. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a wireless communication device to: transmit protection information to signal that a Transmit Opportunity (TxOP) over a wireless communication channel is to be protected according to a preemptionbased protection scheme, wherein the TxOP comprises a preemption period between a first transmission period and a second transmission period, wherein the preemptionbased protection scheme is configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, wherein the preemption-based protection scheme is configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period; and pause communication over the wireless communication channel during the preemption period to provide an opportunity to the one or more preempt-eligible STAs to preempt the wireless communication channel to communicate traffic.

20. The product of claim 19, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) to protect the preemption period according to the preemption-based protection scheme.

21. An apparatus comprising logic and circuitry configured to cause a wireless communication device to: identify, based on protection information from a Transmit Opportunity (TxOP) holder, that a TxOP over a wireless communication channel is to be protected according to a preemption-based protection scheme, wherein the TxOP comprises a preemption period between a first transmission period and a second transmission period, wherein the preemption-based protection scheme is configured to allow one or more preempt-eligible wireless communication stations (STAs) to communicate over the wireless communication channel during the preemption period, wherein the preemption-based protection scheme is configured to prohibit non-preempt-eligible STAs from communicating over the wireless communication channel during the preemption period; and allow a preempt-eligible STA of the wireless communication device to communicate over the wireless communication channel during the preemption period to preempt the wireless communication channel to transmit traffic.

22. The apparatus of claim 21 configured to cause the wireless communication device to, based on a determination that the preempt-eligible STA of the wireless communication device has gained the wireless communication channel, cause the preempt-eligible STA of the wireless communication device to transmit a Request to Send (RTS) frame prior to transmitting the traffic over the wireless communication channel.

23. The apparatus of claim 21 configured to cause the wireless communication device to transmit a signal from the preempt-eligible STA of the wireless communication device during the preemption period, the signal configured to indicate a preemption request from the preempt-eligible STA of the wireless communication device.

24. The apparatus of any one of claims 21-23, wherein the protection information comprises information configured to set a Network Allocation Vector (NAV) to protect the preemption period according to the preemption-based protection scheme.

25. The apparatus of claim 24 configured to cause the wireless communication device to allow the preempt-eligible STA of the wireless communication device to ignore the NAV.