EP4211964A1

EP4211964A1 - Apparatus, system, and method of time allocation within a transmit opportunity

Info

Publication number: EP4211964A1
Application number: EP21867518.9A
Authority: EP
Inventors: Laurent Cariou; Daniel Bravo; Dibakar Das; Dmitry Akhmetov
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2020-09-09
Filing date: 2021-09-08
Publication date: 2023-07-19
Also published as: WO2022056009A1

Abstract

For example, a trigger frame may be communicated from an Access Point (AP) Station (STA) to a non-AP STA. The trigger frame may be configured to indicate an allocation of an allocated time for the non-AP STA within a Transmit Opportunity (TxOP) of the AP STA, the allocated time configured for transmission of one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA.

Description

APPARATUS, SYSTEM, AND METHOD OF TIME ALLOCATION WITHIN A TRANSMIT OPPORTUNITY

CROSS REFERENCE

[001] This application claims the benefit of and priority from US Provisional Patent Application No. 63/076,211 entitled “Enhanced Mechanism for Triggering Single User (SU) Physical Layer Protocol Data Units (PPDUs) in 802.1 Ibe”, filed September 9, 2020, the entire disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

[002] Embodiments described herein generally relate to time allocation within a transmit opportunity.

BACKGROUND

[003] Some wireless communication networks may provide high-throughput data for users of wireless communication devices. For example, some wireless communication networks may utilize wide bandwidths for wireless transmissions.

[004] There is a need for technical solutions to provide increased and/or efficient access to the wireless communication medium.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[007] Fig. 2 is a schematic illustration of an Extremely High Throughput (EHT) Physical layer (PHY) Protocol Data Unit (PPDU) format, which may be implemented in accordance with some demonstrative embodiments.

[008] Fig. 3 is a schematic illustration of a time allocation within a Transmit Opportunity (TxOP), in accordance with some demonstrative embodiments.

[009] Fig. 4 is a schematic illustration of a time allocation within a TxOP, in accordance with some demonstrative embodiments.

[0010] Fig. 5 is a schematic illustration of a time allocation within a TxOP, in accordance with some demonstrative embodiments.

[0011] Fig. 6 is a schematic illustration of a time allocation within a TxOP, in accordance with some demonstrative embodiments.

[0012] Fig. 7 is a schematic flow-chart illustration of a method of time allocation within a TxOP, in accordance with some demonstrative embodiments.

[0013] Fig. 8 is a schematic flow-chart illustration of a method of time allocation within a TxOP, in accordance with some demonstrative embodiments.

[0014] Fig. 9 is a schematic illustration of a product of manufacture, in accordance with some demonstrative embodiments. DETAILED DESCRIPTION

[0015] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments 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.

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

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

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

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

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

[0021] 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, February 2021); and/or IEEE 802.11be (IEEE P802.11be/D1.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 2021)) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE) and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

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

[0023] 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 Frequency-Division Multiplexing (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), Global System for Mobile communication (GSM), 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.

[0024] 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. [0025] 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.

[0026] 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, the circuitry may be implemented in, or 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.

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

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

[0029] Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over a frequency band between 1GHz and 7.250Ghz, for example, a 2.4 Gigahertz (GHz) frequency band, a 5 GHz frequency band, and/or a 6GHz frequency band. However, other aspects may be implemented utilizing any other suitable wireless communication frequency bands, for example, an Extremely High Frequency (EHF) band (the millimeter wave (mmWave) frequency band), e.g., a frequency band within the frequency band of between 20Ghz and 300GHz, a frequency band above 45GHz, a 5G frequency band, a frequency band below 20GHz, e.g., a Sub 1 GHz (SIG) band, a WLAN frequency band, a WPAN frequency band, a frequency band according to the WGA specification, and the like.

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

[0031] Some demonstrative embodiments may be implemented by an Extremely High Throughput (EHT) STA, which may include for example, a STA having a radio transmitter, which is capable of operating on a channel that is in frequency bands between 1GHz and 7.250Ghz. The EHT STA may perform other additional or alternative functionality. Other embodiments may be implemented by any other apparatus, device and/or station.

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

[0033] As shown in Fig. 1, in some demonstrative embodiments, 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, and/or one more other devices.

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

[0035] For example, devices 102 and/or 140 may include, for example, a UE, an MD, a STA, an AP, a Smartphone, 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 onboard 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 video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a media player, a television, a music player, a smart device such as, for example, lamps, climate control, car components, household components, appliances, and the like. [0036] In some demonstrative embodiments, 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 embodiments, 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 embodiments, components of one or more of devices 102 and/or 140 may be distributed among multiple or separate devices.

[0037] In some demonstrative embodiments, 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.

[0038] In some demonstrative embodiments, 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 display, a screen, a touch-screen, one or more audio speakers or earphones, and/or other suitable output devices.

[0039] In some demonstrative embodiments, 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 disk drive, a solid-state drive (SSD), and/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.

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

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

[0042] In some demonstrative embodiments, radio 114 and/or radio 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, radio 114 may include at least one receiver 116, and/or radio 144 may include at least one receiver 146.

[0043] In some demonstrative embodiments, radio 114 and/or radio 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, radio 114 may include at least one transmitter 118, and/or radio 144 may include at least one transmitter 148.

[0044] In some demonstrative embodiments, radio 114 and/or radio 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, radio 114 and/or radio 144 may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like.

[0045] In some demonstrative embodiments, radios 114 and/or 144 may be configured to communicate over a directional band, for example, a frequency band in frequency bands between 1 GHz and 7.250 GHz, for example, a 2.4GHz band, a 5GHz band, a 6GHz band, and/or any other frequency band, for example, frequency band above 45 GHz, an SIG band, and/or any other band.

[0046] In some demonstrative embodiments, radios 114 and/or 144 may include, or may be associated with one or more, e.g., a plurality of, antennas.

[0047] In some demonstrative embodiments, device 102 may include one or more, e.g., a single antenna or a plurality of, antennas 107, and/or device 140 may include on or more, e.g., a plurality of, antennas 147.

[0048] 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. Antennas 107 and/or 147 may include, for example, antennas suitable for directional communication, e.g., using beamforming techniques. For example, antennas 107 and/or 147 may include a single antenna, a plurality of antennas, a phased array antenna, a multiple element antenna, a set of switched beam antennas, and/or the like. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0049] In some demonstrative embodiments, antennas 107 and/or antennas 147 may be connected to, and/or associated with, one or more Radio Frequency (RF) chains.

[0050] In some demonstrative embodiments, device 102 may include one or more, e.g., a plurality of, RF chains 109 connected to, and/or associated with, antennas 107. [0051] In some demonstrative embodiments, one or more of RF chains 109 may be included as part of, and/or implemented as part of one or more elements of radio 114, e.g., as part of transmitter 118 and/or receiver 116.

[0052] In some demonstrative embodiments, device 140 may include one or more, e.g., a plurality of, RF chains 149 connected to, and/or associated with, antennas 147.

[0053] In some demonstrative embodiments, one or more of RF chains 149 may be included as part of, and/or implemented as part of one or more elements of radio 144, e.g., as part of transmitter 148 and/or receiver 146.

[0054] In some demonstrative embodiments, 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 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 and/or one or more other devices, e.g., as described below.

[0055] In some demonstrative embodiments, 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 embodiments, 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 embodiments, 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 embodiments, 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 embodiments, 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 embodiments, device 140 may include a message processor 158 configured to generate, process and/or access one or 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, 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 embodiments, 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 embodiments, 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, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (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 embodiments, 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 embodiments, 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 embodiments, 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 embodiments, 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 radio 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 radio 114. In one example, controller 124, message processor 128, and radio 114 may be implemented as part of the chip or SoC. [0071] In other embodiments, controller 124, message processor 128 and/or radio 114 may be implemented by one or more additional or alternative elements of device 102.

[0072] In some demonstrative embodiments, 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 System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio 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 radio 144. In one example, controller 154, message processor 158, and radio 144 may be implemented as part of the chip or SoC.

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

[0074] In some demonstrative embodiments, device 102 and/or device 140 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, and/or device 140 may include at least one STA.

[0075] In some demonstrative embodiments, device 102 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. For example, device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT STA, and/or device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT STA.

[0076] In other embodiments, devices 102 and/or 140 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 embodiments, device 102 and/or device 140 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.

[0078] In some demonstrative embodiments, device 102 and/or device 140 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 embodiments, device 102 and/or device 140 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 a station (STA), e.g., one STA, and provides access to distribution services, via the wireless medium (WM) for associated STAs. The AP may perform any other additional or alternative functionality.

[0082] In one example, a non-AP STA may include a STA that is not contained within an AP. The non-AP STA may perform any other additional or alternative functionality.

[0083] In some demonstrative embodiments devices 102 and/or 140 may be configured to communicate over an EHT network, and/or any other network. For example, devices 102 and/or 140 may perform Multiple-Input-Multiple-Output (MIMO) communication, for example, for communicating over the EHT networks, e.g., over an EHT frequency band, e.g., in frequency bands between 1 GHz and 7.250 GHz.

[0084] In some demonstrative embodiments, devices 102 and/or 140 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.

[0085] In some demonstrative embodiments, devices 102 and/or 140 may be configured according to one or more standards, for example, in accordance with an IEEE 802.1 Ibe Standard, which may be configured, for example, to enhance the efficiency and/or performance of an IEEE 802.11 Specification, which may be configured to provide Wi-Fi connectivity.

[0086] Some demonstrative embodiments may enable, for example, to significantly increase the data throughput defined in the IEEE 802.11-2020 Specification, for example, up to a throughput of 30 Giga bits per second (Gbps), or to any other throughput, which may, for example, satisfy growing demand in network capacity for new coming applications.

[0087] Some demonstrative embodiments may be implemented, for example, to support increasing a transmission data rate, for example, by applying MIMO and/or Orthogonal Frequency Division Multiple Access (OFDM A) techniques.

[0088] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate MIMO communications and/or OFDMA communication in frequency bands between 1 GHz and 7.250 GHz.

[0089] In some demonstrative embodiments, device 102 and/or device 140 may be configured to support one or more mechanisms and/or features, for example, OFDMA, Single User (SU) MIMO, and/or Multi-User (MU) MIMO, for example, in accordance with an IEEE 802.11 be Standard and/or any other standard and/or protocol.

[0090] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, one or more EHT STAs. For example, device 102 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT ST A, and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT STA.

[0091] In some demonstrative embodiments, devices 102 and/or 140 may implement a communication scheme, which may include Physical layer (PHY) and/or Media Access Control (MAC) layer schemes, for example, to support one or more applications, and/or increased throughput, e.g., throughputs up to 30 Gbps, or any other throughput.

[0092] In some demonstrative embodiments, the PHY and/or MAC layer schemes may be configured to support OFDMA techniques, SU MIMO techniques, and/or MU MIMO techniques.

[0093] In some demonstrative embodiments, devices 102 and/or 140 may be configured to implement one or more mechanisms, which may be configured to enable SU and/or MU communication of Downlink (DL) and/or Uplink frames (UL) using a MIMO scheme.

[0094] In some demonstrative embodiments, device 102 and/or device 140 may be configured to implement one or more MU communication mechanisms. For example, devices 102 and/or 140 may be configured to implement one or more MU mechanisms, which may be configured to enable MU communication of DL frames using a MIMO scheme, for example, between a device, e.g., device 102, and a plurality of devices, e.g., including device 140 and/or one or more other devices.

[0095] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate over an EHT network, and/or any other network and/or any other frequency band. For example, devices 102 and/or 140 may be configured to communicate DL transmissions and/or UL transmissions, for example, for communicating over the EHT networks.

[0096] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate over a channel bandwidth, e.g., of at least 20 Megahertz (MHz), in frequency bands between 1 GHz and 7.250 GHz.

[0097] In some demonstrative embodiments, devices 102 and/or 140 may be configured to implement one or more mechanisms, which may, for example, support communication over a wide channel bandwidth (BW) (“channel width”) (also referred to as a “wide channel” or “wide BW”) covering two or more channels, e.g., two or more 20 MHz channels, e.g., as described below.

[0098] In some demonstrative embodiments, wide channel mechanisms may include, for example, a mechanism and/or an operation whereby two or more channels, e.g., 20MHz channels, can be combined, aggregated or bonded, e.g., for a higher bandwidth of packet transmission, for example, to enable achieving higher throughputs, e.g., when compared to transmissions over a single channel. Some demonstrative embodiments are described herein with respect to communication over a channel BW including two or more 20MHz channels, however other embodiments 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, a bonded or aggregated channel including a bonding or an aggregation of two or more channels.

[0099] In some demonstrative embodiments, device 102 and/or device 140 may be configured to communicate one or more transmissions over one or more channel BWs, for example, including a channel BW of 20MHz, a channel BW of 40MHz, a channel BW of 80MHz, a channel BW of 160MHz, a channel BW of 320MHz, and/or any other additional or alternative channel BW, e.g., as described below. [00100] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive a Physical Layer (PHY) Protocol Data Unit (PPDU) having a PPDU format (also referred to as “EHT PPDU format”), which may be configured, for example, for communication between EHT stations, e.g., as described below.

[00101] In some demonstrative embodiments, a PPDU, e.g., an EHT PPDU, may include at least one non-EHT field, e.g., a legacy field, which may be identified, decodable, and/or processed by one or more devices (“non-EHT devices”, or “legacy devices”), which may not support one or more features and/or mechanisms (“nonlegacy” mechanisms or “non-EHT mechanisms”). For example, the legacy devices may include non-EHT stations and/or non-High Throughput (HT) stations, which may be, for example, configured according to an IEEE 802.11-2020 Standard, and the like.

[00102] Reference is made to Fig. 2, which schematically illustrates an EHT PPDU format 200, which may be implemented in accordance with some demonstrative embodiments. In one example, devices 102 (Fig. 1) and/or 140 (Fig. 1) may be configured to generate, transmit, receive and/or process one or more EHT PPDUs having the structure and/or format of EHT PPDU 200.

[00103] In one example, devices 102 (Fig. 1) and/or 140 (Fig. 1) may communicate EHT PPDU 200, for example, as part of a transmission over a channel, e.g., an EHT channel, having a channel bandwidth including one or more 20MHz channels, for example, a channel B W of 20MHz, a channel BW of 40MHz, a channel BW of 80MHz, a channel BW of 160MHz, a channel BW of 320MHz, and/or any other additional or alternative channel BW, e.g., as described below.

[00104] In some demonstrative embodiments, EHT PPDU 200 may include an EHT SU PPDU, which may be utilized for transmission from an EHT STA, e.g., an EHT STA implemented by device 102 (Fig. 1), to one another STA, e.g., an EHT STA implemented by device 140 (Fig. 1).

[00105] In some demonstrative embodiments, EHT PPDU 200 may include an EHT MU PPDU, which may be utilized for transmission from an EHT STA, e.g., an EHT STA implemented by device 102 (Fig. 1), to one or more users, for example, one or more EHT STAs, including an EHT STA implemented by device 140 (Fig. 1). [00106] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a non-High Throughput (non-HT) (legacy) Short Training Field (STF) (L-STF) 202, followed by a non-HT (Legacy) Long Training Field (LTF) (L-LTF) 204, which may be followed by a non-HT Signal (SIG) (L-SIG) field 206.

[00107] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a repeated non-HT SIG (RL-SIG) field 208, which may follow the L-SIG field 206. The RL-SIG field 208 may be followed by a Universal SIG (U-SIG) field 210.

[00108] In some demonstrative embodiments, as shown in Fig. 2, EHT PPDU 200 may include a plurality of EHT-modulated fields, e.g., following the U-SIG field 210.

[00109] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT Signal (EHT-SIG) field 212.

[00110] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT STF (EHT-STF) field 214, e.g., following the EHT-SIG field 212.

[00111] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, an EHT LTF (EHT-LTF) field 216, e.g., following the EHT-STF field 214.

[00112] In some demonstrative embodiments, as shown in Fig. 2, the EHT modulated fields may include, for example, a data field 218, e.g., following the EHT-LTF field 216, and/or a Packet Extension (PE) field 220, e.g., following the data field 218.

[00113] In some demonstrative embodiments, EHT PPDU 200 may include some or all of the fields shown in Fig. 2 and/or one or more other additional or alternative fields.

[00114] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive and/or process one or more transmissions, e.g., including one or more EHT PPDUs, e.g., as described below.

[00115] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process one or more transmissions, e.g., including one or more EHT PPDUs, e.g., including one or more fields according to the EHT PPDU format of Fig. 2. [00116] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive and/or process an EHT PPDU, e.g., in accordance with an IEEE 802,.llbe Specification and/or any other specification, e.g., as described below.

[00117] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process the EHT PPDU as an EHT MU PPDU, for example, in accordance with the EHT PPDU formal 200 (Fig. 2).

[00118] In some demonstrative aspects, the EHT MU PPDU may include a PPDU that carries one or more PHY service data units (PSDUs) for one or more STAs using a downlink multi-user multiple input, multiple output (DL-MU-MIMO) technique, an orthogonal frequency division multiple access (DL OFDMA) technique, or a combination of the two techniques.

[00119] In some demonstrative embodiments, for example, devices 102 and/or 140 may be configured to perform one or more operations, and/or functionalities of an EHT STA, which may be configured, for example, to generate, transmit, receive and/or process the EHT MU PPDU, for example, over a 20MHz channel width, a 40MHz channel width, a 80MHz channel width, a 160MHz channel width, and/or a 320Mhz channel width.

[00120] In other embodiments, any other additional or alternative channel width may be utilized.

[00121] In some demonstrative embodiments, devices 102 and/or 140 may be configured to implement a mechanism for time allocation within a Transmit Opportunity (TxOP), e.g., as described below.

[00122] In some demonstrative embodiments, an AP STA, e.g., an AP STA implemented by device 140, may be configured to obtain a TxOP, for example, according to a channel access mechanism, for example, according to one or more channel access rules of an IEEE 802.11 Specification, and/or any other channel access rules and/or mechanisms. [00123] In some demonstrative embodiments, the AP STA, e.g., the AP STA implemented by device 140, may be configured to allocate a time period within the TxOP to a non-AP STA, for example, a non-AP STA implemented by device 102, e.g., as described below.

[00124] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive one or more trigger frames, e.g., “light-weight” trigger frames, which may be configured to solicit single user (SU) physical layer protocol data units (PPDUs), e.g., as described below.

[00125] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive one or more trigger frames, e.g., “light-weight” trigger frames, which may be configured to support one or more, e.g., several, use-cases, for example, in order to reduce contention in a Basic Service Set (BSS). For example, such methods may require some, e.g., little, information about channel conditions, such as, for example, a Buffered Status Report (BSR), from triggered STAs.

[00126] In some demonstrative embodiments, a SU PPDU triggering may facilitate that an AP transmits a Trigger Frame (TF), e.g., a SU-TF, which may elicit non-TB PPDUs from one or more triggered STAs, e.g., as described below.

[00127] In some demonstrative embodiments, a SU PPDU triggering may facilitate time allocation according to a mode (also referred to as “time allocation mode”), for example, which may be selected from a plurality of predefined modes, e.g., as described below.

[00128] In some demonstrative embodiments, the time allocation mode may have one or more recovery rules, for example, for recovering the allocated time period, e.g., as described below.

[00129] In some demonstrative embodiments, the time allocation mode may include, for example, a mode (“Mode 1”), in which a triggered STA may align a response PPDU duration on multiple links, e.g., as described below.

[00130] In some demonstrative embodiments, the time allocation mode may include, for example, a mode (“Mode 2”), in which the triggered STA may transmit one UL PPDU within an allocated time, which is allocated by the TF, e.g., as described below. [00131] In some demonstrative embodiments, the time allocation mode may include, for example, a mode (“Mode 3”), in which the triggered STA may transmit multiple PPDUs, e.g., within the allocated time, which is allocated by the TF, e.g., as described below.

[00132] In some demonstrative aspects, the time allocation mode may be defined, for example, such that the non-AP STA is allowed to transmit PPDUs to the AP STA, which allocated the time allocation within the TxOP, e.g., as described below.

[00133] In some demonstrative aspects, the time allocation mode may be defined, for example, such that the non-AP STA is allowed to transmit PPDUs to one or more other STAs other than the AP STA, which allocated the time allocation within the TxOP. For example, the non-AP STA may be allowed to transmit PPDUs including Peer-to-Peer (P2P) frames to one or more other non-AP STAs, e.g., as described below.

[00134] In some demonstrative embodiments, one or more of the modes may be defined with clarification on how to handle recovery rules, e.g., to allow the AP STA to recover an unused portion of the allocated time, and/or how to extend it in future for other purposes, e.g., for Multi- AP implementations.

[00135] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications according to a SU PPDU triggering mechanism, which may be configured to facilitate clarification on different modes and corresponding recovery rules, which may be utilized, for example, for time allocation, e.g., as described below.

[00136] In some demonstrative embodiments, the SU PPDU triggering mechanism may be configured to facilitate a mode where triggered STAs may be allowed to utilize Enhanced Distributed Channel Access (EDC A) during a triggered time allocation, e.g., as described below.

[00137] In some demonstrative embodiments, the SU PPDU triggering mechanism may be configured to facilitate clarifications on extending to related use-cases such as, for example, Multi-AP and/or Non Simultaneous Transmit-Receive (STR) operation, e.g., as described below.

[00138] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications utilizing a frame format, e.g., a new frame format, which may have a similar structure to existing TFs, where many unused parameters may be reserved or not present.

[00139] In some demonstrative embodiments, the SU PPDU triggering mechanism may be configured to facilitate an efficient light-weight mechanism, which may provide a technical solution to improve channel access, e.g., as described below.

[00140] In some demonstrative embodiments, controller 154 may be configured 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, of an AP STA, e.g., as described below.

[00141] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to configure a trigger frame (TF) to indicate an allocation of an allocated time for a non-AP STA within a Transmit Opportunity (TxOP) of the AP, e.g., as described below.

[00142] In some demonstrative embodiments, the allocated time may be configured for transmission of one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA, e.g., as described below.

[00143] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to transmit the trigger frame to initiate the allocation of the allocated time to the non-AP STA, e.g., as described below.

[00144] In some demonstrative embodiments, the AP implemented by device 140 may include an EHT AP. In other aspects, any other type of AP STA may be used.

[00145] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set a field in the trigger frame to indicate the allocation of the allocated time for the non-AP STA, e.g., as described below.

[00146] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set a user field in the trigger frame to indicate the allocation of the allocated time for the non-AP STA, e.g., as described below. [00147] In other embodiments, any other additional or alternative field and/or mechanism may be used to indicate the allocation of the allocated time for the non-AP STA.

[00148] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to process a response frame from the non-AP STA in response to the trigger frame, e.g., as described below.

[00149] In some demonstrative embodiments, the response frame may include a Clear to Send (CTS), e.g., as described below.

[00150] In other embodiments, the response frame may include any other type of frame, e.g., a control frame and/or any other frame.

[00151] In some demonstrative embodiments, the response frame may be configured to confirm the allocation of the allocated time for the non-AP STA, e.g., as described below.

[00152] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set a mode field in the trigger frame to indicate a type (mode) of the allocation of the allocated time for the non-AP STA, e.g., as described below.

[00153] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set the mode field to a predefined mode value from a plurality of predefined mode values, which may indicate a respective plurality of allocation modes, e.g., as described below.

[00154] In some demonstrative embodiments, the plurality of predefined mode values may include at least two mode values to indicate at least two respective allocation modes, e.g., as described below.

[00155] In some demonstrative embodiments, the plurality of predefined mode values may include three mode values to indicate three respective allocation modes, e.g., as described below.

[00156] In other embodiments, any other number of modes may be implemented. [00157] In some demonstrative embodiments, the plurality of predefined mode values may include, for example, a first mode value and a second mode value, e.g., as described below.

[00158] In some demonstrative embodiments, the first mode value may be configured to indicate a first mode, e.g., an Uplink (UL) mode (any other name may be used for this mode), in which the non-AP STA may be allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, e.g., as described below.

[00159] In some demonstrative embodiments, the second mode value may be configured to indicate a second mode, e.g., a Peer-to Peer (P2P) mode (any other name may be used for this mode), in which the non-AP STA may be allowed to transmit UL PPDUs to the AP, or PPDUs to one or more other non-AP STAs during the allocated time for the non-AP STA, e.g., as described below.

[00160] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set the mode field to indicate a mode, e.g., the Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, e.g., as described below.

[00161] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to set the mode field to indicate a mode, e.g., a Peer-to-Peer(P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP, or PPDUs to other non-AP STAs, during the allocated time for the non-AP STA, e.g., as described below.

[00162] In other embodiments, any other additional or alternative modes may be implemented.

[00163] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to recover the TxOP for transmission by the AP STA, for example, before an end of the allocated time for the non-AP STA, e.g., as described below.

[00164] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to recover the TxOP for transmission by the AP STA, for example, based on a Pomt-Inter-Frame-Space (PIFS) idle rule, e.g., as described below.

[00165] In other embodiments, any other additional or alternative recovery rules may be used

[00166] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to recover the TxOP for transmission by the AP STA, for example, based on identifying an expiration of a Network Allocation Vector (NAV) set by a PPDU from the nom-AP STA, e.g., as described below.

[00167] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to recover the TxOP for transmission by the AP STA, for example, after the allocated time for the non-AP STA, e.g., as described below.

[00168] In some demonstrative embodiments, controller 154 may be configured to cause the AP STA implemented by device 140 to recover the TxOP for transmission by the AP STA, for example, based on a PIFS idle rule, e.g., as described below.

[00169] In other embodiments, any other additional or alternative recovery rules may be used

[00170] In some demonstrative embodiments, controller 124 may be configured 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, of a non-AP STA, e.g., as described below.

[00171] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process a trigger frame received from an AP STA.

[00172] For example, the trigger frame received by the non-AP STA implemented by device 102 may include the trigger frame transmitted by the AP STA implemented by device 140, e.g., as described above. [00173] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process the trigger frame from the AP to initiate an allocation of an allocated time for the non-AP STA within a TxOP of the AP, e.g., as described below.

[00174] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process a field in the trigger frame, and to determine the allocation of the allocated time for the non-AP STA based on the field.

[00175] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process a user field in the trigger frame, and to determine the allocation of the allocated time for the non-AP STA based on the user field.

[00176] In other embodiments, any other additional or alternative field and/or mechanism may be used to indicate the allocation of the allocated time for the non-AP STA.

[00177] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit one or more non Trigger Based (non-TB) PPDUs from the non-AP STA during the allocated time for the non- AP STA, e.g., as described below.

[00178] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit a response frame to the AP, for example, in response to the trigger frame, e.g., as described below.

[00179] In some demonstrative embodiments, the response frame may include a CTS, e.g., as described below.

[00180] In other embodiments, the response frame may include any other type of frame, e.g., a control frame, and/or any other frame.

[00181] In some demonstrative embodiments, the response frame may be configured to confirm the allocation of the allocated time for the non-AP STA, e.g., as described below. [00182] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit the response frame to the AP, for example, before transmitting the one or more non-TB PPDUs, for example, before transmitting any non-TB PPDUs, e.g., as described below.

[00183] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to process a mode field in the trigger frame, and to determine a type of the allocation of the allocated time for the non-AP STA, for example, based on the mode field, e.g., as described below.

[00184] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to determine the type of the allocation of the allocated time for the non-AP STA, for example, based on detection of a mode value from a plurality of predefined mode values. For example, the plurality of predefined mode values may be configured to indicate a respective plurality of allocation modes, e.g., as described below.

[00185] In some demonstrative embodiments, the plurality of predefined mode values may include at least two mode values to indicate at least two respective allocation modes, e.g., as described below.

[00186] In some demonstrative embodiments, the plurality of predefined mode values may include three mode values to indicate three respective allocation modes, e.g., as described below.

[00187] In other embodiments, any other number of modes may be defined.

[00188] In some demonstrative embodiments, the plurality of predefined mode values may include a first mode value and a second mode value, e.g., as described below.

[00189] In some demonstrative embodiments, the first mode value may be configured to indicate a first mode, e.g., the UL mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, e.g., as described below.

[00190] In some demonstrative embodiments, the second mode value may be configured to indicate the P2P mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP, or PPDUs to other non-AP STAs during the allocated time for the non-AP STA, e.g., as described below. [00191] In other embodiments, any other additional or alternative modes may be implemented.

[00192] In some demonstrative embodiments, controller 124 may be configured to allow and/or enable the non-AP STA implemented by device 102 to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, for example, based on a determination that the mode field indicates the UL mode, e.g., as described below.

[00193] In some demonstrative embodiments, controller 124 may be configured to prohibit, prevent, and/or disable the non-AP STA implemented by device 102 from transmitting PPDUs to other non-AP STAs, e.g., P2P PPDUs, during the allocated time for the non-AP STA, for example, based on a determination that the mode field indicates the UL mode, e.g., as described below.

[00194] In some demonstrative embodiments, controller 124 may be configured to allow and/or enable the non-AP STA implemented by device 102 to transmit UL PPDUs to the AP and/or PPDUs to other non-AP STAs during the allocated time for the non-AP STA, for example, based on a determination that the mode field indicates the P2P mode, e.g., as described below.

[00195] In some demonstrative embodiments, controller 124 may be configured to cause the non-AP STA implemented by device 102 to transmit a frame including an indication that the non-AP STA is to return to the AP an unused portion of the allocated time for the non-AP STA, e.g., as described below.

[00196] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications for communication during a time allocation within a TxOP according to one or more modes, e.g., as described below.

[00197] In some demonstrative embodiments, a time allocation mode may be configured such that a STA (“transmitter STA”, “triggering STA”, or “allocating STA”) transmitting a trigger frame, e.g., a SU-TF, to another STA (“receiver STA”, “triggered STA” or “granted STA”) may determine, e.g., through explicit signaling and/or using any other mechanism, whether a length of a response PPDU from the receiver STA may exactly match the allocated time or whether the response PPDU is to be within the allocated time. [00198] In some demonstrative embodiments, the TF transmitter STA may be defined to always remain the TxOP owner in this mode, for example, except for one or more conditions, e.g., possibly when the TF is transmitted in response to another frame, e.g., an RTS frame, and/or any other condition.

[00199] In some demonstrative embodiments, the trigger frame may be configured to include an indication, e.g., a one bit signaling field or any other indication, e.g., in a user information (info) field, a common info field, or any other field, about whether alignment is sought. For example, the trigger frame may be configured to include a first indication, e.g., a first bit value, to indicate that alignment is requested, e.g., that the receiver STA is to transmit a PPDU, which is to end at an end of the allocated time. For example, the trigger frame may be configured to include a second indication, e.g., a second bit value, to indicate that alignment is not requested, e.g., that the receiver STA is to transmit a PPDU, which may end at or before the end of the allocated time.

[00200] Reference is made to Fig. 3, which schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, device 102 (Fig. 1) and/or device 140 (Fig. 1) may be configured to perform one or more communications and/or operations according to Fig. 3.

[00201] In some demonstrative embodiments, as shown in Fig. 3, an AP 340 may transmit a trigger frame 304, e.g., a New-format TF (NTF), to a first STA (STA1) 302. For example, controller 154 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 140 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, AP 340. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 302.

[00202] In some demonstrative embodiments, the trigger frame 304 may include an indication of a time allocation 306 to be allocated to STA 302, e.g., within a TxOP of the AP 340.

[00203] In some demonstrative embodiments, the trigger frame 304 may include an indication to indicate whether the time allocation 306 is allocated for a fixed PPDU duration. For example, as shown in Fig. 3, the trigger frame 304 may include an indication that the time allocation is 306 is allocated for transmission of a PPDU with a fixed length corresponding to the duration of the time allocation 306.

[00204] In some demonstrative embodiments, as shown in Fig. 3, the STA 302 may receive and process the trigger frame 304.

[00205] In some demonstrative embodiments, as shown in Fig. 3, the STA 302 may transmit a PPDU 308 to AP 340 during the allocated time 306. For example, as shown in Fig. 3, based on the indication in trigger frame 304, the STA 302 may configure the PPDU 308 as a SU PPDU with a fixed duration based on the duration of the time allocation 306, e.g., such that transmission of the PPDU 308 will end at an end of the time allocation 306.

[00206] In some demonstrative embodiments, as shown in Fig. 3, the AP 340 may receive and process the PPDU 308, and may transmit a Block Acknowledgement (BA) 310 to STA 302, e.g., to acknowledge the PPDU 308.

[00207] In some demonstrative embodiments, as shown in Fig. 3, AP 340 may transmit a trigger frame 314, e.g., an NTF, to a second STA (STA2) 372. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 372.

[00208] In some demonstrative embodiments, the trigger frame 314 may include an indication of a time allocation 316 to be allocated to STA 372, e.g., within the TxOP of the AP 340.

[00209] In some demonstrative embodiments, the trigger frame 314 may include an indication to indicate whether the time allocation 316 is allocated for a fixed PPDU duration. For example, as shown in Fig. 3, the trigger frame 314 may include an indication that the time allocation is 316 is allocated for transmission of a PPDU with any length, which is equal to or less than the duration of the time allocation 316 (max PPDU duration).

[00210] In some demonstrative embodiments, as shown in Fig. 3, the STA 372 may receive and process the trigger frame 314.

[00211] In some demonstrative embodiments, as shown in Fig. 3, the STA 372 may transmit a PPDU 318 to AP 340 during the allocated time 316. For example, as shown in Fig. 3, based on the indication in trigger frame 314, the STA 372 may configure the PPDU 318 as a SU PPDU with a duration, which is less than or equal to the duration of the time allocation 316, e.g., such that transmission of the PPDU 318 will end before or at an end of the time allocation 316.

[00212] In some demonstrative embodiments, as shown in Fig. 3, the AP 340 may receive and process the PPDU 318, and may transmit a BA 320 to STA 372, e.g., to acknowledge the PPDU 318. As shown in Fig. 3, the BA 320 may be transmitted before the end of the time allocation 316.

[00213] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications according to a time allocation mode, which may be configured such that the STA transmitting the trigger frame, e.g., a SU-TF, may configure the trigger frame to start an allocated time period, during which the triggered STA is allowed to transmit one or more PPDUs, e.g., as described below.

[00214] In some demonstrative embodiments, the allocated time period may include, or may be configured as, an intra-TxOP time period, during which the triggered/granted STA may be the TxOP holder.

[00215] In some demonstrative embodiments, during the allocated time period, the triggered STA may be allowed to transmit one or more non-TB PPDUs, e.g., as described below.

[00216] In some demonstrative embodiments, during the allocated time period, the triggered STA may be allowed to transmit one or more non-TB PPDUs to the triggering STA, e.g., in the form of one or mor UL PPDUs, e.g., as described below.

[00217] In some demonstrative embodiments, during the allocated time period, the triggered STA may be allowed to transmit one or more non-TB PPDUs to the triggering STA, e.g., in the form of one or mor UL PPDUs, and/or to some other STA, e.g., in the form of P2P PPDUs, e.g., as described below.

[00218] In some demonstrative embodiments, the allocated time period may be configured such that any STA or some specific STA, which may be collocated with the triggered STA, may also be allowed to transmit during the allocated time period. [00219] In some demonstrative embodiments, the triggered STA may be allowed to return any unused portion of the TxOP to the TF transmitter, for example, by explicitly signaling that the unused portion of the TxOP is to be recovered by the TF transmitter.

[00220] In one example, the triggered STA may transmit a Quality of Service (QoS) null frame to indicate that an unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00221] In another example, the triggered STA may transmit a QoS null frame with some explicit signaling, e.g., an End of Service Period (EOSP) bit set to 1, a Queue Size subfield set to 0, or the like, to indicate that an unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00222] In another example, the triggered STA may transmit a QoS Data frame with some explicit signaling, e.g., by setting a Duration field set to cover only the response PPDU, or any other indication, to indicate that an unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00223] In another example, the triggered STA may transmit another frame, for example, a Contention Free (CF) end (CF-end) frame, or any other frame, to indicate that an unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00224] In other embodiments, any other frame, e.g., a new frame, may be used to indicate that an unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00225] In some demonstrative embodiments, the TxOP owner STA, e.g., the TF transmitter, may optionally implement one or more contention mechanisms, e.g., regular contention mechanisms, e.g., following the explicit signaling from the triggered STA that the unused portion of the TxOP is to be returned to and/or recovered by, the TF transmitter.

[00226] In some demonstrative embodiments, the SU-TF transmitter STA may be allowed to implement one or more additional or alternative recovery rules, for example, for recovering a portion of the TxOP, e.g., in absence of explicit signaling.

[00227] In some demonstrative embodiments, an indication of which recovery rules are to be used may be explicitly signaled and/or negotiated, for example, by the AP Sta and/or the non-AP STA, e.g., in the TF, during capability exchange, and/or via any other signaling mechanism.

[00228] In some demonstrative embodiments, the trigger frame transmitter STA may be allowed to perform a PIFS recovery, for example, following the SU-TF transmission. For example, the triggered STA or any collocated STA may further protect its allocation, e.g., like a regular STA using optionally a Request to Send (RTS)ZClear to Send (CTS) (RTS-CTS) exchange.

[00229] In some demonstrative embodiments, the trigger frame transmitter STA may be configured to utilize explicit signaling in the SU-TF, for example, to indicate about whether the time allocation triggered by the trigger frame is to be used for P2P/Multi- AP communication, or for UL communication.

[00230] In some demonstrative embodiments, the above recovery rule may be followed, for example, if the time allocation is used for P2P communication.

[00231] In some demonstrative embodiments, a recovery rule, e.g., similar to a recovery rule of a Reverse Direction Grant (RDG) mechanism, may be utilized, for example, if the time allocation is used for UL communication to the trigger frame transmitter STA. For example, the SU-TF transmitter may regain medium, e.g., anytime in the time allocation, for example, through a PIFS-idle rule.

[00232] In some demonstrative embodiments, the TxOP owner STA, e.g., the trigger frame transmitter STA, may be allowed to recover (“grab”) an unused portion of the TxOP, for example, if the TxOP owner STA can determine so, e.g., in an implementation- specific manner using baseline rules. For example, after a Network Allocation vector (NAV), e.g., as set by one or more PPDUs from a triggered P2P STA, has expired.

[00233] In some demonstrative embodiments, the TxOP owner STA, e.g., the trigger frame transmitter STA, may require the granted STA, or a device containing the granted STA, to initiate a TxOP using an RTS-CTS exchange, e.g., where the RTS frame sets the time allocation to be used by the STA. For example, the SU-TF transmitter STA may know a MAC address of the STA interface of the P2P link, e.g., in a softAP case.

[00234] Reference is made to Fig. 4, which schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, device 102 (Fig. 1) and/or device 140 (Fig. 1) may be configured to perform one or more communications and/or operations according to Fig. 4.

[00235] For example, one or more communications and/or operations according to Fig. 4 may be configured for a trigger Time Division Multiple Access (TDMA) mode with non-P2P transmission.

[00236] In some demonstrative embodiments, as shown in Fig. 4, an AP 440 may transmit a trigger frame 404, e.g., an NTF, to a first STA (STA1) 402. For example, controller 154 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 140 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, AP 440. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 402.

[00237] In some demonstrative embodiments, the trigger frame 404 may include an indication of a time allocation 406 to be allocated to STA 402, e.g., within a TxOP of the AP 440.

[00238] In some demonstrative embodiments, the trigger frame 404 may include an indication to indicate that the time allocation 406 is allocated for communication of one or more UL PPDUs to the AP 440.

[00239] In some demonstrative embodiments, as shown in Fig. 4, the STA 402 may receive and process the trigger frame 404.

[00240] In some demonstrative embodiments, as shown in Fig. 4, the STA 402 may transmit a PPDU 408 to AP 440 during the allocated time 406. For example, as shown in Fig. 4, based on the indication in trigger frame 404, the STA 402 may configure the PPDU 408 as a SU PPDU with a duration, which may be within the time allocation 406.

[00241] In some demonstrative embodiments, as shown in Fig. 4, the AP 440 may receive and process the PPDU 408, and may transmit a BA 410 to STA 402, e.g., to acknowledge the PPDU 408.

[00242] In some demonstrative embodiments, as shown in Fig. 4, AP 440 may transmit a trigger frame 414, e.g., an NTF, to a second STA (STA2) 472. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, ST A 472.

[00243] In some demonstrative embodiments, the trigger frame 414 may include an indication of a time allocation 416 to be allocated to STA 472, e.g., within the TxOP of the AP 440.

[00244] In some demonstrative embodiments, the trigger frame 414 may include an indication to indicate that the time allocation 416 is allocated for communication of one or more UL PPDUs to the AP 440.

[00245] In some demonstrative embodiments, as shown in Fig. 4, the STA 472 may receive and process the trigger frame 414.

[00246] In some demonstrative embodiments, as shown in Fig. 4, the STA 472 may transmit a PPDU 418 to AP 440 during the allocated time 416. For example, as shown in Fig. 4, based on the indication in trigger frame 414, the STA 472 may configure the PPDU 418 as a SU PPDU with a duration, which may be within the time allocation 416.

[00247] In some demonstrative embodiments, as shown in Fig. 4, the AP 440 may receive and process the PPDU 418, and may transmit a BA 420 to STA 402, e.g., to acknowledge the PPDU 418.

[00248] Reference is made to Fig. 5, which schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, device 102 (Fig. 1) and/or device 140 (Fig. 1) may be configured to perform one or more communications and/or operations according to Fig. 5.

[00249] For example, one or more communications and/or operations according to Fig. 5 may be configured for a trigger TDMA mode with P2P transmission.

[00250] In some demonstrative embodiments, as shown in Fig. 5, an AP 540 may transmit a trigger frame 504, e.g., an NTF, to a first STA (STA1) 502. For example, controller 154 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 140 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, AP 540. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 502. [00251] In some demonstrative embodiments, the trigger frame 504 may include an indication of a time allocation 506 to be allocated to STA 502, e.g., within a TxOP of the AP 540.

[00252] In some demonstrative embodiments, the trigger frame 504 may include an indication to indicate that the time allocation 506 is allocated for communication of one or more PPDUs, which may be allowed to include P2P PPDUs communicated with other STAs, e.g., other than AP STA 540.

[00253] In some demonstrative embodiments, as shown in Fig. 5, the STA 502 may receive and process the trigger frame 504.

[00254] In some demonstrative embodiments, as shown in Fig. 5, the STA 502 may transmit a PPDU 508 to another STA during the allocated time 506. For example, as shown in Fig. 5, based on the indication in trigger frame 504, the STA 502 may configure the PPDU 508 as a SU PPDU in a P2P communication to another STA with a duration, which may be within the time allocation 506.

[00255] In some demonstrative embodiments, as shown in Fig. 5, the STA 502 may receive a BA 510 from the other STA, e.g., in a P2P communication, e.g., to acknowledge the PPDU 508.

[00256] In some demonstrative embodiments, as shown in Fig. 5, AP 540 may transmit a trigger frame 514, e.g., an NTF, to a second STA (STA2) 572. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 572.

[00257] In some demonstrative embodiments, the trigger frame 514 may include an indication of a time allocation 516 to be allocated to STA 572, e.g., within a TxOP of the AP 540.

[00258] In some demonstrative embodiments, the trigger frame 514 may include an indication to indicate that the time allocation 516 is allocated for communication of one or more PPDUs, which may be P2P PPDUs communicated with other STAs, e.g., other than AP STA 540.

[00259] In some demonstrative embodiments, as shown in Fig. 5, the STA 572 may receive and process the trigger frame 514. [00260] In some demonstrative embodiments, as shown in Fig. 5, the STA 572 may transmit a PPDU 518 to another STA during the allocated time 516. For example, as shown in Fig. 5, based on the indication in trigger frame 514, the STA 572 may configure the PPDU 518 as a SU PPDU in a P2P communication to another STA with a duration, which may be within the time allocation 516.

[00261] In some demonstrative embodiments, as shown in Fig. 5, the STA 572 may receive a BA 520 from the other STA, e.g., in a P2P communication, e.g., to acknowledge the PPDU 518.

[00262] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications according to a time allocation mode, which may be configured such that following the SU-TF transmission, one or more triggered STAs may start contending for medium time within the time allocated in the TF, e.g., as described below.

[00263] In some demonstrative embodiments, the time allocation mode may be configured such that multiple STAs may be scheduled within the allocated time. For example, the trigger frame transmitter STA, e.g., the STA implemented by device 140, may configure the trigger frame to allocate the allocated time to a plurality of STAs, e.g., including the STA implemented by device 102, for example, by including in the trigger frame one or more STA identifiers and/or group identifiers to identify the plurality of STAs.

[00264] In some demonstrative embodiments, the trigger frame transmitter STA may configure the SU-TF to include one or more contention parameters of a contention mechanism, e.g., one or more EDCA parameters and/or any other contention parameters, to be used within the allocated time.

[00265] In some demonstrative embodiments, the trigger frame may define the same one or more contention parameters of a contention mechanism, e.g., EDCA parameters, to be used by all triggered STAs.

[00266] In some demonstrative embodiments, the trigger frame may define different contention parameters, e.g., EDCA parameters, to be used by different STAs. For example, the trigger frame transmitter STA may configure the trigger frame to include an indication of one or more first EDCA parameters to be used by one or more first triggered STAs for accessing the wireless medium during the time allocation; and/or an indication of one or more second EDCA parameters, e.g., different from the one or more first EDCA parameters, to be used by one or more second triggered STAs for accessing the wireless medium during the time allocation.

[00267] In some demonstrative embodiments, the allocation of the one or more contention parameters may be identified in a field of the trigger frame.

[00268] In some demonstrative embodiments, the allocation of the one or more contention parameters, e.g., the EDCA parameters, may be defined in the user info field, or any other field.

[00269] In some demonstrative embodiments, the allocation of the one or more contention parameters, e.g., the EDCA parameters, may be predefined or preconfigured, for example, in a Specification.

[00270] In some demonstrative embodiments, the allocation of the one or more contention parameters, e.g., the EDCA parameters, may be signaled, for example, during a capability exchange between the trigger frame transmitter STA and the triggered STA, and/or during any traffic flow setup, Service period (SP) negotiation, and/or any other negotiation or setup phase.

[00271] In some demonstrative embodiments, time allocation mode may be configured such that a triggered STA that wins according to a contention mechanism, e.g., an EDCA contention or any other contention mechanism, may become a TxOP holder for some time, e.g., for part of or all of the allocated time.

[00272] In some demonstrative embodiments, an intra-BSS NAV may be set by the SU-TF.

[00273] In some demonstrative embodiments, the trigger frame transmitter STA may configure the SU-TF to include a time offset, which may signal when each of the assigned STAs can start contending for the medium.

[00274] In some demonstrative embodiments, the SU-TF transmitter STA may poll at the beginning of the TxOP, e.g., to check which STAs can participate in the allocated time. [00275] In some demonstrative embodiments, the SU-TF transmitter STA may be configured to use one or more, e.g., special, EDCA parameters, which may be configured to allow the SU-TF transmitter STA to obtain access to (grab) the wireless medium, e.g., with a higher priority than the triggered STAs.

[00276] In some demonstrative embodiments, the trigger frame transmitter STA may configure the TF to include a MAC address, e.g., a special and/or preconfigured MAC address, which may identify the group of STAs that are triggered together for the allocated time.

[00277] In some demonstrative embodiments, the MAC address may be negotiated and/or exchanged, for example, during a capability exchange, through a management (Mgt) frame exchange, and/or any other negotiation and/or setup phase.

[00278] In some demonstrative embodiments, the triggered STA, e.g., the STA implemented by device 102, may be configured not to set any further NAV, e.g., other than a NAV set for the allocated time.

[00279] In some demonstrative embodiments, the triggered STA, e.g., the STA implemented by device 102, may be allowed to set a further NAV, e.g., other than a NAV set for the allocated time.

[00280] In some demonstrative embodiments, one or more of the triggered STAs may return unused medium time to the SU-TF transmitter STA, e.g., by transmitting a frame, e.g., a CF-end frame, and/or any other frame, e.g., a new frame or an existing frame, e.g., a QoS-Null, which signal the return of the unused time in the allocated time. Such a response may be triggered or unsolicited.

[00281] In some demonstrative embodiments, the SU-TF transmitter STA may regain access to the medium, for example, after one or more STAs have returned medium time.

[00282] Reference is made to Fig. 6, which schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, device 102 (Fig. 1) and/or device 140 (Fig. 1) may be configured to perform one or more communications and/or operations according to Fig. 6.

[00283] For example, one or more communications and/or operations according to Fig.

6 may be configured for a trigger an EDCA mode time allocation. [00284] In some demonstrative embodiments, as shown in Fig. 6, an AP 640 may transmit a trigger frame 604, e.g., an NTF, to a plurality of STAs, e.g., including a first STA (STA1) 602, and a second STA (STA2) 672. For example, controller 154 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 140 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, AP 640. For example, controller 124 (Fig. 1) may be configured to trigger, cause, instruct and/or control device 102 (Fig. 1) to perform a role of, one or more operations of, and/or functionalities of, STA 602 and/or STA 672.

[00285] In some demonstrative embodiments, the trigger frame 604 may include an indication of a time allocation 606, according to a NAV protection period, to be allocated to the plurality of STAs, e.g., within a TxOP of the AP 640.

[00286] In some demonstrative embodiments, the trigger frame 604 may include an indication to indicate that the time allocation 606 is allocated for communication by the plurality of STAs according to a contention mechanism, e.g., an EDCA mechanism, or any other contention mechanism.

[00287] In some demonstrative embodiments, as shown in Fig. 6, the STA 602 and STA 672 may receive and process the trigger frame 604.

[00288] In some demonstrative embodiments, as shown in Fig. 6, the STA 602 may contend for the medium, e.g., according to the EDDCA mechanism, and may gain access to the medium for transmitting a PPDU 608 to the AP 640 during the allocated time 606.

[00289] In some demonstrative embodiments, as shown in Fig. 6, the AP 640 may transmit a BA 610 to the STA 602, e.g., to acknowledge the PPDU 608.

[00290] In some demonstrative embodiments, as shown in Fig. 6, the STA 672 may contend for the medium, e.g., according to the EDDCA mechanism, and may gain access to the medium, e.g., after STA 602, for transmitting a PPDU 618 to another STA during the allocated time 606. For example, as shown in Fig. 6, the STA 672 may configure the PPDU 618 as a SU PPDU in a P2P communication to another STA with a duration, which may be within the time allocation 606. [00291] In some demonstrative embodiments, as shown in Fig. 6, the STA 672 may receive a BA 620 from the other STA, e.g., in a P2P communication, e.g., to acknowledge the PPDU 618.

[00292] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, process, transmit and/or receive communications according to a time allocation mode, which may be configured according to one or more allocation, signaling, and/or communication rules, e.g., as described below.

[00293] In some demonstrative embodiments, non-AP STAs, e.g., the STA implemented by device 102, may be allowed to transmit a SU-TF, e.g., to allocate the time allocation to one or more other STAs.

[00294] In some demonstrative embodiments, triggered STAs, e.g., the STA implemented by device 102, may be configured to transmit a response to the SU-TF, e.g., to acknowledge the allocation.

[00295] In some demonstrative embodiments, the response from a triggered STA may include information signaling the duration of the actual allocation to be used by the triggered STA.

[00296] In some demonstrative embodiments, the response may include a Control (Ctrl) frame, e.g., CTS frame, a management (Mgt) frame, and/or any other type of frame, which may be transmitted in a TB PPDU or a non-TB PPDU.

[00297] In some demonstrative embodiments, the SU-TF may include additional signaling, for example, to indicate a pair of STAs that are scheduled for any P2P transmission, e.g., in a TDLS link.

[00298] In some demonstrative embodiments, the SU-TF may include signaling information to indicate all STAs that are allocated the same time resource, including collocated ones, for example, to enable spatial reuse in non-collocated STAs.

[00299] In some demonstrative embodiments, the SU-TF and its different modes may be signaled, for example, using a field in a common info field, a user info field, and/or any other field of a TF. [00300] In one example, a tngger frame transmitter, e.g., the STA implemented by device 140, may be configured to set a new Trigger Type subfield in a trigger frame, which may be configured to signal that this trigger frame is a SU-TF, which is to allocate the allocated time to the one or more triggered STAs.

[00301] In some demonstrative embodiments, the trigger frame transmitter, e.g., the STA implemented by device 140, may be configured to set a field, e.g., a new Trigger Dependent Common Info field , or any other field, to indicate a mode of the allocated time. For example, the mode of the allocated time may include a mode of the plurality of modes described above, and/or any other additional or alternative modes, e.g., including extensions proposed in future, e.g., to support Multi-AP behavior.

[00302] In some demonstrative embodiments, the trigger frame transmitter, e.g., the STA implemented by device 140, may be configured to set a signaling field, e.g., a one bit signaling field, e.g., in the Common Info field, the User Info field, or any other field, to signal whether the time allocation is for non-AP STAs or also for Multi-AP STAs.

[00303] In one example, the one bit signaling field may be reserved in the time allocation mode for the case when the SU-TF does not require alignment.

[00304] In some demonstrative embodiments, for example, when the bit indicates the allocation is for Multi-AP, this may be similar to C-OFDMA, C-TDMA, or C-SR. For example, an AID value in the trigger frame may be set to contain a MAC address or some other identifier for the APs. For example, a Resource Unit (RU) field in the trigger frame may not be Reserved in the former case.

[00305] In some demonstrative embodiments, for example, for the Multi-AP case, the AID field may signal a special value to signal that a MAC address is used. For example, the actual MAC address may be signaled separately in Trigger Dependent User Info.

[00306] In some demonstrative embodiments, for example, in a mode where alignment is required for multiple PPDUs, the SU-TF may be configured to include exact times to be used by the multiple response PPDUs, e.g., set SIFS apart. For example, if the requirement is to align 2 PPDUs, the duration field of the trigger frame may be set to include signaling for the entire time allocation, while an UL Length may be set to contain signaling for the first PPDU. [00307] In some demonstrative embodiments, the TXOP owner STA may be configured to multiplex regular UL transmissions with P2P transmissions, e.g., in different RUs. In one example, this feature may be implemented in a TF, e.g., a Basic TF or any other TF format, for example, using a bit in the Common Info field to signal whether alignment is required or not; and/or using a bit signaling in the User Info field to signal whether this allocation is for P2P transmissions or not. For example, the RU field may be set to signal the exact frequency allocation to be used.

[00308] In some demonstrative embodiments, the time allocation may be implemented with non- STR operation.

[00309] For example, an infrastructure AP or a STR non-AP STA may trigger the non- STR AP, e.g., using the SU-TF.

[00310] For example, parameters to be used by a non-STR AP for recovery following a blindness event may be conveyed, for example, by the infrastructure AP, or specified in a Specification, or decided by the non-STR AP itself.

[00311] In some demonstrative embodiments, a new signaling scheme/frame can be used to implement SU-TF that has similar structure as current Trigger frames but many unused parameters being either not present or Reserved, e.g., MCS, NSS, AP Tx power, UL Target RSSI, and the like.

[00312] In some demonstrative embodiments, the new frame can signal the different modes described previously as sub-types and follow similar rules on channel access, solicitation and design as described above.

[00313] In some demonstrative embodiments, the new frame can also signal existing TF modes such as Basic, MU-RTS etc. or their corresponding light-weighted versions as subtypes. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[00314] Reference is made to Fig. 7, which schematically illustrates a method of time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 7 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), 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).

[00315] As indicated at block 702, the method may include configuring at an AP STA a trigger frame to indicate an allocation of an allocated time for a non-AP STA within a TxOP of the AP, wherein the allocated time may be configured for transmission of one or more non-TB PPDUs from the non-AP STA. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to configure the trigger frame to indicate the allocation of an allocated time for a non-AP STA within a TxOP of the AP STA implemented by device 140, e.g., as described above.

[00316] As indicated at block 704, the method may include transmitting the trigger frame to initiate the allocation of the allocated time to the non-AP STA. For example, controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to transmit the trigger frame to initiate the allocation of the allocated time to the non-AP STA, e.g., as described above.

[00317] Reference is made to Fig. 8, which schematically illustrates a method of time allocation within a TxOP, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 8 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), 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).

[00318] As indicated at block 802, the method may include processing at a non-AP STA a trigger frame from an AP to initiate an allocation of an allocated time for the non-AP STA within a TxOP of the AP. For example, controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to process the trigger frame from the AP STA implemented by device 140 (Fig. 1) to initiate an allocation of an allocated time for the non-AP STA implemented by device 102 (Fig. 1), e.g., as described above.

[00319] As indicated at block 804, the method may include transmitting one or more non-TB PPDUs from the non-AP STA during the allocated time for the non-AP STA. For example, controller 124 (Fig. 1) may be configured to cause, tngger, and/or control device 102 (Fig. 1) to transmit the one or more non-TB PPDUs during the allocated time for the non-PA STA implemented by device 102 (Fig. 1), e.g., as described above.

[00320] Reference is made to Fig. 9, which schematically illustrates a product of manufacture 900, in accordance with some demonstrative embodiments. Product 900 may include one or more tangible computer-readable (“machine-readable”) non- transitory storage media 902, which may include computer-executable instructions, e.g., implemented by logic 904, 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), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), and/or receiver 146 (Fig. 1); to cause device 102 (Fig. 1), device 140 (Fig. 1), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 158 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), and/or receiver 146 (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, 6, 7, and/or 8, 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.

[00321] In some demonstrative embodiments, product 900 and/or machine readable storage media 902 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine readable storage media 902 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, sihcon-oxide-mtnde-oxide- silicon (SONOS) memory, a hard drive, an optical disk, a magnetic disk, 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.

[00322] In some demonstrative embodiments, logic 904 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.

[00323] In some demonstrative embodiments, logic 904 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, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

[00324] The following examples pertain to further embodiments.

[00325] Example 1 includes an apparatus comprising logic and circuitry configured to cause an Access Point (AP) to configure a trigger frame to indicate an allocation of an allocated time for a non-AP wireless communication station (STA) within a Transmit Opportunity (TxOP) of the AP, the allocated time configured for transmission of one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA; and transmit the trigger frame to initiate the allocation of the allocated time to the non-AP STA.

[00326] Example 2 includes the subject matter of Example 1, and optionally, wherein the apparatus is configured to cause the AP to process a response frame from the non- AP STA in response to the trigger frame.

[00327] Example 3 includes the subject matter of Example 2, and optionally, wherein the response frame comprises a Clear to Send (CTS).

[00328] Example 4 includes the subject matter of Example 2 or 3, and optionally, wherein the response frame is to confirm the allocation of the allocated time for the non-AP STA.

[00329] Example 5 includes the subject matter of any one of Examples 1-4, and optionally, wherein the apparatus is configured to cause the AP to set a mode field in the trigger frame to indicate a mode of the allocation of the allocated time for the non- AP STA.

[00330] Example 6 includes the subject matter of Example 5, and optionally, wherein the apparatus is configured to cause the AP to set the mode field to a predefined mode value from a plurality of predefined mode values, the plurality of predefined mode values to indicate a respective plurality of allocation modes.

[00331] Example 7 includes the subject matter of Example 6, and optionally, wherein the plurality of predefined mode values comprises three mode values to indicate three respective allocation modes.

[00332] Example 8 includes the subject matter of Example 6 or 7, and optionally, wherein the plurality of predefined mode values comprises a first mode value and a second mode value, the first mode value to indicate an Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, the second mode value to indicate a Peer-to Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

[00333] Example 9 includes the subject matter of any one of Examples 5-8, and optionally, wherein the apparatus is configured to cause the AP to set the mode field to indicate an Uplink (UL) mode, in which the non-AP ST A is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA.

[00334] Example 10 includes the subject matter of any one of Examples 5-8, and optionally, wherein the apparatus is configured to cause the AP to set the mode field to indicate a Peer-to-Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

[00335] Example 11 includes the subject matter of any one of Examples 1-10, and optionally, wherein the apparatus is configured to cause the AP to recover the TxOP for transmission before an end of the allocated time for the non-AP STA.

[00336] Example 12 includes the subject matter of Example 11, and optionally, wherein the apparatus is configured to cause the AP to recover the TxOP for transmission based on a Point-Inter-Frame-Space (PIFS) idle rule.

[00337] Example 13 includes the subject matter of Example 11 or 12, and optionally, wherein the apparatus is configured to cause the AP to recover the TxOP for transmission based on identifying an expiration of a Network Allocation Vector (NAV) set by a PPDU from the nom-AP STA.

[00338] Example 14 includes the subject matter of any one of Examples 1-13, and optionally, wherein the apparatus is configured to cause the AP to recover the TxOP for transmission after the allocated time for the non-AP STA.

[00339] Example 15 includes the subject matter of Example 14, and optionally, wherein the apparatus is configured to cause the AP to recover the TxOP for transmission based on a Point-Inter-Frame-Space (PIFS) idle rule.

[00340] Example 16 includes the subject matter of any one of Examples 1-15, and optionally, wherein the apparatus is configured to cause the AP to set a user field in the trigger frame to indicate the allocation of the allocated time for the non-AP STA.

[00341] Example 17 includes the subject matter of any one of Examples 1-16, and optionally, wherein the AP is an Extremely High Throughput (EHT) AP.

[00342] Example 18 includes the subject matter of any one of Examples 1-17, and optionally, comprising a radio to transmit the trigger frame. [00343] Example 19 includes the subject matter of Example 18, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the AP.

[00344] Example 20 includes an apparatus comprising logic and circuitry configured to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to:

[00345] process a trigger frame from an AP to initiate an allocation of an allocated time for the non-AP STA within a Transmit Opportunity (TxOP) of the AP; and

[00346] transmit one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA during the allocated time for the non-AP STA.

[00347] Example 21 includes the subject matter of Example 20, and optionally, wherein the apparatus is configured to cause the non-AP STA to transmit a response frame to the AP in response to the trigger frame.

[00348] Example 22 includes the subject matter of Example 21, and optionally, wherein the response frame comprises a Clear to Send (CTS).

[00349] Example 23 includes the subject matter of Example 21 or 22, and optionally, wherein the response frame is to confirm the allocation of the allocated time for the non-AP STA.

[00350] Example 24 includes the subject matter of any one of Examples 21-23, and optionally, wherein the apparatus is configured to cause the non-AP STA to transmit the response frame to the AP before transmitting the one or more non-TB PPDUs.

[00351] Example 25 includes the subject matter of any one of Examples 20-24, and optionally, wherein the apparatus is configured to cause the non-AP STA to process a mode field in the trigger frame, and to determine a mode of the allocation of the allocated time for the non-AP STA based on the mode field.

[00352] Example 26 includes the subject matter of Example 25, and optionally, wherein the apparatus is configured to cause the non-AP to determine the mode of the allocation of the allocated time for the non-AP STA based on detection of a mode value from a plurality of predefined mode values, the plurality of predefined mode values to indicate a respective plurality of allocation modes. [00353] Example 27 includes the subject matter of Example 26, and optionally, wherein the plurality of predefined mode values comprises three mode values to indicate three respective allocation modes.

[00354] Example 28 includes the subject matter of Example 26 or 27, and optionally, wherein the plurality of predefined mode values comprises a first mode value and a second mode value, the first mode value to indicate an Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, the second mode value to indicate a Peer-to-Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

[00355] Example 29 includes the subject matter of any one of Examples 25-28, and optionally, wherein the apparatus is configured to cause the non-AP STA to, based on a determination that the mode field indicates an Uplink (UL) mode, allow the non-AP STA to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA.

[00356] Example 30 includes the subject matter of any one of Examples 25-28, and optionally, wherein the apparatus is configured to cause the non-AP STA to, based on a determination that the mode field indicates a Peer-to-Peer (P2P) mode, allow the non- AP STA to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

[00357] Example 31 includes the subject matter of any one of Examples 20-30, and optionally, wherein the apparatus is configured to cause the non-AP STA to transmit a frame comprising an indication that the non-AP STA is to return to the AP an unused portion of the allocated time for the non-AP STA.

[00358] Example 32 includes the subject matter of any one of Examples 20-31, and optionally, wherein the apparatus is configured to cause the non-AP STA to process a user field in the trigger frame, and to determine the allocation of the allocated time for the non-AP STA based on the user field.

[00359] Example 33 includes the subject matter of any one of Examples 20-32, and optionally, comprising a radio to communicate the trigger frame and the one or more non-TB PPDUs. [00360] Example 34 includes the subject matter of Example 33, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the non-AP STA.

[00361] Example 35 comprises an apparatus comprising means for executing any of the described operations of Examples 1-34.

[00362] Example 36 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 computing device to perform any of the described operations of Examples 1- 34.

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

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

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

[00366] 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 an Access Point (AP) to: configure a trigger frame to indicate an allocation of an allocated time for a non-AP wireless communication station (STA) within a Transmit Opportunity (TxOP) of the AP, the allocated time configured for transmission of one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA; and transmit the trigger frame to initiate the allocation of the allocated time to the non-AP STA.

2. The apparatus of claim 1 configured to cause the AP to process a response frame from the non-AP STA in response to the trigger frame.

3. The apparatus of claim 2, wherein the response frame comprises a Clear to Send (CTS).

4. The apparatus of claim 1 configured to cause the AP to set a mode field in the trigger frame to indicate a mode of the allocation of the allocated time for the non-AP STA.

5. The apparatus of claim 4 configured to cause the AP to set the mode field to a predefined mode value from a plurality of predefined mode values, the plurality of predefined mode values to indicate a respective plurality of allocation modes.

6. The apparatus of claim 5, wherein the plurality of predefined mode values comprises a first mode value and a second mode value, the first mode value to indicate an Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA, the second mode value to indicate a Peer-to Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

55

7. The apparatus of claim 4 configured to cause the AP to set the mode field to indicate an Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non-AP STA.

8. The apparatus of claim 4 configured to cause the AP to set the mode field to indicate a Peer-to-Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP STAs during the allocated time for the non-AP STA.

9. The apparatus of any one of claims 1-8 configured to cause the AP to recover the TxOP for transmission before an end of the allocated time for the non-AP STA.

10. The apparatus of any one of claims 1-8 configured to cause the AP to recover the TxOP for transmission after the allocated time for the non-AP STA.

11. The apparatus of any one of claims 1-8 configured to cause the AP to recover the TxOP for transmission based on a Point-Inter-Frame-Space (PIFS) idle rule.

12. The apparatus of any one of claims 1-8 configured to cause the AP to set a user field in the trigger frame to indicate the allocation of the allocated time for the non- AP STA.

13. The apparatus of any one of claims 1-8, wherein the AP is an Extremely High Throughput (EHT) AP.

14. The apparatus of any one of claims 1-8 comprising a radio to transmit the trigger frame.

15. The apparatus of claim 14 comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the AP.

16. 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 an Access Point (AP) to: configure a trigger frame to indicate an allocation of an allocated time for a non-AP wireless communication station (STA) within a Transmit Opportunity (TxOP)

56 of the AP, the allocated time configured for transmission of one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA; and transmit the trigger frame to initiate the allocation of the allocated time to the non-AP STA.

17. The product of claim 16, wherein the instructions, when executed, cause the AP to process a response frame from the non-AP STA in response to the trigger frame.

18. The product of claim 17, wherein the response frame comprises a Clear to Send (CTS).

19. The product of any one of claims 16-18, wherein the instructions, when executed, cause the AP to set a mode field in the trigger frame to indicate a mode of the allocation of the allocated time for the non-AP STA.

20. The product of claim 19, wherein the instructions, when executed, cause the AP to set the mode field to indicate an Uplink (UL) mode, in which the non-AP STA is allowed to transmit only UL PPDUs to the AP during the allocated time for the non- AP STA.

21. The product of claim 19, wherein the instructions, when executed, cause the AP to set the mode field to indicate a Peer-to-Peer (P2P) mode, in which the non-AP STA is allowed to transmit UL PPDUs to the AP or PPDUs to other non-AP ST As during the allocated time for the non-AP STA.

22. An apparatus comprising logic and circuitry configured to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to: process a trigger frame from an AP to initiate an allocation of an allocated time for the non-AP STA within a Transmit Opportunity (TxOP) of the AP; and transmit one or more non Trigger Based (non-TB) Physical layer (PHY) Protocol Data Units (PPDUs) from the non-AP STA during the allocated time for the non-AP STA.

57

23. The apparatus of claim 22 configured to cause the non-AP STA to process a mode field in the trigger frame, and to determine a mode of the allocation of the allocated time for the non-AP STA based on the mode field.

24. The apparatus of claim 22 or 23 comprising a radio to communicate the trigger frame and the one or more non-TB PPDUs.

25. The apparatus of claim 24 comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the non-AP STA.

58