EP4211964A1 - Appareil, système et procédé d'attribution de temps durant une opportunité de transmission - Google Patents

Appareil, système et procédé d'attribution de temps durant une opportunité de transmission

Info

Publication number
EP4211964A1
EP4211964A1 EP21867518.9A EP21867518A EP4211964A1 EP 4211964 A1 EP4211964 A1 EP 4211964A1 EP 21867518 A EP21867518 A EP 21867518A EP 4211964 A1 EP4211964 A1 EP 4211964A1
Authority
EP
European Patent Office
Prior art keywords
sta
demonstrative embodiments
mode
allocated time
transmit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21867518.9A
Other languages
German (de)
English (en)
Other versions
EP4211964A4 (fr
Inventor
Laurent Cariou
Daniel Bravo
Dibakar Das
Dmitry Akhmetov
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP4211964A1 publication Critical patent/EP4211964A1/fr
Publication of EP4211964A4 publication Critical patent/EP4211964A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • Some wireless communication networks may provide high-throughput data for users of wireless communication devices.
  • some wireless communication networks may utilize wide bandwidths for wireless transmissions.
  • FIG. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.
  • 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.
  • EHT Extremely High Throughput
  • PHY Physical layer
  • PPDU Protocol Data Unit
  • Fig. 3 is a schematic illustration of a time allocation within a Transmit Opportunity (TxOP), in accordance with some demonstrative embodiments.
  • Fig. 4 is a schematic illustration of a time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • Fig. 6 is a schematic illustration of a time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • Fig. 8 is a schematic flow-chart illustration of a method of time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • 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.
  • processing 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.
  • 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.
  • UE User Equipment
  • MD Mobile Device
  • STA wireless station
  • PC Personal Computer
  • 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
  • AP wireless Access Point
  • 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
  • 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.
  • WAP Wireless Application Protocol
  • 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, ZigBeeTM, Ultra-Wideband (U
  • wireless device 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.
  • 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.
  • the term “wireless device” may optionally include a wireless service.
  • the term “communicating ’ as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal.
  • 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.
  • 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.
  • 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.
  • RF Radio Frequency
  • 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.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • 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.
  • the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and/or operations.
  • 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.
  • 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.
  • 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.
  • EHF Extremely High Frequency
  • mmWave millimeter wave
  • SIG Sub 1 GHz
  • WLAN Wireless Fidelity
  • WPAN Wireless Fidelity
  • antenna may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements.
  • 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.
  • EHT Extremely High Throughput
  • STA 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.
  • system 100 may include one or more wireless communication devices.
  • system 100 may include a wireless communication device 102, a wireless communication device 140, and/or one more other devices.
  • devices 102 and/or 140 may include a mobile device or a non-mobile, e.g., a static, device.
  • 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 UltrabookTM 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
  • 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.
  • OS Operating System
  • OS Operating System
  • 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.
  • device 102 may include at least one radio 114
  • device 140 may include at least one radio 144.
  • 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.
  • radio 114 and/or radio 144 may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like.
  • NIC wireless Network Interface Card
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • antennas 107 and/or 147 may implement transmit and receive functionalities using separate transmit and receive antenna elements.
  • antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • device 102 may include one or more, e.g., a plurality of, RF chains 109 connected to, and/or associated with, antennas 107.
  • 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.
  • device 140 may include one or more, e.g., a plurality of, RF chains 149 connected to, and/or associated with, antennas 147.
  • 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.
  • device 102 may include a controller 124
  • 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.
  • 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.
  • a wireless device e.g., device 102
  • a wireless station e.g., a wireless STA implemented by device 102
  • 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.
  • 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.
  • a wireless device e.g., device 140
  • a wireless station e.g., a wireless STA implemented by device 140
  • 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.
  • 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.
  • 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.
  • device 102 may include a message processor 128 configured to generate, process and/or access one or messages communicated by device 102.
  • 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.
  • 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.
  • 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.
  • device 140 may include a message processor 158 configured to generate, process and/or access one or messages communicated by device 140.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • SoC System on Chip
  • the chip or SoC may be configured to perform one or more functionalities of radio 144.
  • 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.
  • controller 154, message processor 158, and radio 144 may be implemented as part of the chip or SoC.
  • controller 154, message processor 158 and/or radio 144 may be implemented by one or more additional or alternative elements of device 140.
  • 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.
  • device 102 may include at least one STA
  • device 140 may include at least one STA.
  • 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.
  • 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.
  • AP access point
  • EHT AP EHT AP
  • 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.
  • 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.
  • devices 102 and/or 140 may be configured to communicate over an EHT network, and/or any other network.
  • 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.
  • MIMO Multiple-Input-Multiple-Output
  • 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.
  • OFDM A Orthogonal Frequency Division Multiple Access
  • 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.
  • 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.
  • device 102 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT ST A
  • device 140 may include, operate as, perform a role of, and/or perform the functionality of, at least one EHT STA.
  • 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.
  • PHY Physical layer
  • MAC Media Access Control
  • the PHY and/or MAC layer schemes may be configured to support OFDMA techniques, SU MIMO techniques, and/or MU MIMO techniques.
  • 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.
  • DL Downlink
  • UL Uplink frames
  • device 102 and/or device 140 may be configured to implement one or more MU communication mechanisms.
  • 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.
  • 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.
  • devices 102 and/or 140 may be configured to communicate DL transmissions and/or UL transmissions, for example, for communicating over the EHT networks.
  • 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.
  • a channel bandwidth e.g., of at least 20 Megahertz (MHz)
  • MHz Megahertz
  • 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.
  • BW wide channel bandwidth
  • 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.
  • 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.
  • 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.
  • 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.
  • PHY Physical Layer
  • PPDU Protocol Data Unit
  • EHT PPDU format PPDU format
  • FIG. 2 schematically illustrates an EHT PPDU format 200, which may be implemented in accordance with some demonstrative embodiments.
  • 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.
  • 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.
  • a channel e.g., an EHT channel
  • 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.
  • 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).
  • 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).
  • EHT STA e.g., an EHT STA implemented by device 102 (Fig. 1)
  • EHT STA e.g., an EHT STA implemented by device 102 (Fig. 1)
  • 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.
  • non-HT legacy Short Training Field
  • L-LTF Long Training Field
  • SIG non-HT Signal
  • 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.
  • U-SIG Universal SIG
  • EHT PPDU 200 may include a plurality of EHT-modulated fields, e.g., following the U-SIG field 210.
  • the EHT modulated fields may include, for example, an EHT Signal (EHT-SIG) field 212.
  • EHT-SIG EHT Signal
  • the EHT modulated fields may include, for example, an EHT STF (EHT-STF) field 214, e.g., following the EHT-SIG field 212.
  • EHT-STF EHT STF
  • the EHT modulated fields may include, for example, an EHT LTF (EHT-LTF) field 216, e.g., following the EHT-STF field 214.
  • EHT-LTF EHT LTF
  • 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.
  • a data field 218, e.g., following the EHT-LTF field 216 e.g., following the EHT-LTF field 216
  • PE Packet Extension
  • 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.
  • 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.
  • 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.
  • PSDUs PHY service data units
  • DL-MU-MIMO downlink multi-user multiple input, multiple output
  • DL OFDMA orthogonal frequency division multiple access
  • an AP STA e.g., an AP STA implemented by device 140
  • the AP STA e.g., the AP STA implemented by device 140
  • 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.
  • TF Trigger Frame
  • 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.
  • a mode also referred to as “time allocation mode”
  • time allocation mode may be selected from a plurality of predefined modes, e.g., as described below.
  • the time allocation mode may have one or more recovery rules, for example, for recovering the allocated time period, e.g., as described below.
  • 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.
  • 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.
  • EDC A Enhanced Distributed Channel Access
  • 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.
  • STR Non Simultaneous Transmit-Receive
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • TF trigger frame
  • TxOP Transmit Opportunity
  • 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.
  • non-TB Physical layer
  • PHY Physical layer
  • PPDUs Protocol Data Units
  • 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.
  • the AP implemented by device 140 may include an EHT AP. In other aspects, any other type of AP STA may be used.
  • 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.
  • 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.
  • 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.
  • the response frame may include any other type of frame, e.g., a control frame and/or any other frame.
  • the response frame may be configured to confirm the allocation of the allocated time for the non-AP STA, e.g., as described below.
  • 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.
  • 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.
  • 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.
  • the plurality of predefined mode values may include three mode values to indicate three respective allocation modes, e.g., as described below.
  • 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.
  • UL Uplink
  • 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.
  • 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.
  • 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.
  • PIFS Pomt-Inter-Frame-Space
  • 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.
  • 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.
  • 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.
  • 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.
  • the response frame may be configured to confirm the allocation of the allocated time for the non-AP STA, e.g., as described below.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a second indication e.g., a second bit value
  • 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.
  • the trigger frame 304 may include an indication to indicate whether the time allocation 306 is allocated for a fixed PPDU duration.
  • 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.
  • the STA 302 may receive and process the trigger frame 304.
  • 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.
  • 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.
  • BA Block Acknowledgement
  • AP 340 may transmit a trigger frame 314, e.g., an NTF, to a second STA (STA2) 372.
  • STA2 STA
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • 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.
  • 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.
  • the trigger frame 314 may include an indication to indicate whether the time allocation 316 is allocated for a fixed PPDU duration.
  • 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).
  • the STA 372 may receive and process the trigger frame 314.
  • 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.
  • 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.
  • the triggered STA may be allowed to transmit one or more non-TB PPDUs, e.g., as described below.
  • 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.
  • 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.
  • 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.
  • CF Contention Free
  • the TxOP owner STA 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.
  • 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.
  • 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.
  • 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.
  • the trigger frame transmitter STA may be allowed to perform a PIFS recovery, for example, following the SU-TF transmission.
  • 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.
  • RTS Request to Send
  • CTS Clear to Send
  • 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.
  • the above recovery rule may be followed, for example, if the time allocation is used for P2P communication.
  • 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.
  • the SU-TF transmitter may regain medium, e.g., anytime in the time allocation, for example, through a PIFS-idle rule.
  • the TxOP owner STA e.g., the trigger frame transmitter STA
  • NAV Network Allocation vector
  • the TxOP owner STA e.g., the trigger frame transmitter STA
  • the SU-TF transmitter STA may know a MAC address of the STA interface of the P2P link, e.g., in a softAP case.
  • Fig. 4 schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • device 102 Fig. 1
  • device 140 Fig. 1
  • Fig. 4 may be configured to perform one or more communications and/or operations according to Fig. 4.
  • 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.
  • TDMA Time Division Multiple Access
  • an AP 440 may transmit a trigger frame 404, e.g., an NTF, to a first STA (STA1) 402.
  • 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.
  • 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.
  • 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.
  • 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.
  • the STA 402 may receive and process the trigger frame 404.
  • 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.
  • 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.
  • AP 440 may transmit a trigger frame 414, e.g., an NTF, to a second STA (STA2) 472.
  • STA2 STA
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 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.
  • 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.
  • 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.
  • the STA 472 may receive and process the trigger frame 414.
  • 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.
  • 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.
  • FIG. 5 schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • device 102 Fig. 1
  • device 140 Fig. 1
  • Fig. 5 may be configured to perform one or more communications and/or operations according to Fig. 5.
  • one or more communications and/or operations according to Fig. 5 may be configured for a trigger TDMA mode with P2P transmission.
  • an AP 540 may transmit a trigger frame 504, e.g., an NTF, to a first STA (STA1) 502.
  • 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.
  • 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.
  • 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.
  • 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.
  • the STA 502 may receive and process the trigger frame 504.
  • 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.
  • 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.
  • AP 540 may transmit a trigger frame 514, e.g., an NTF, to a second STA (STA2) 572.
  • STA2 STA
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • 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.
  • 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.
  • 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.
  • the STA 572 may receive and process the trigger frame 514.
  • the STA 572 may transmit a PPDU 518 to another STA during the allocated time 516.
  • 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.
  • 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.
  • 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.
  • 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.
  • the time allocation mode may be configured such that multiple STAs may be scheduled within the allocated time.
  • the trigger frame transmitter STA e.g., the STA implemented by device 140
  • the trigger frame 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.
  • 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.
  • a contention mechanism e.g., one or more EDCA parameters and/or any other contention parameters
  • 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.
  • a contention mechanism e.g., EDCA parameters
  • the trigger frame may define different contention parameters, e.g., EDCA parameters, to be used by different STAs.
  • 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.
  • the allocation of the one or more contention parameters may be identified in a field of the trigger frame.
  • the allocation of the one or more contention parameters may be defined in the user info field, or any other field.
  • the allocation of the one or more contention parameters may be predefined or preconfigured, for example, in a Specification.
  • the allocation of the one or more contention 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.
  • SP Service period
  • 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.
  • a contention mechanism e.g., an EDCA contention or any other contention mechanism
  • an intra-BSS NAV may be set by the SU-TF.
  • 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.
  • 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.
  • 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.
  • 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.
  • a MAC address e.g., a special and/or preconfigured MAC address
  • 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.
  • Mgt management
  • the triggered STA e.g., the STA implemented by device 102
  • the triggered STA may be configured not to set any further NAV, e.g., other than a NAV set for the allocated time.
  • the triggered STA e.g., the STA implemented by device 102
  • 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.
  • a frame e.g., a CF-end frame
  • any other frame e.g., a new frame or an existing frame, e.g., a QoS-Null
  • the SU-TF transmitter STA may regain access to the medium, for example, after one or more STAs have returned medium time.
  • FIG. 6 schematically illustrates a time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • device 102 Fig. 1
  • device 140 Fig. 1
  • Fig. 6 may be configured to perform one or more communications and/or operations according to 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.
  • controller 154 Fig. 1
  • controller 154 Fig. 1
  • controller 124 Fig. 1
  • controller 124 Fig. 1
  • controller 124 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.
  • 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.
  • 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.
  • a contention mechanism e.g., an EDCA mechanism, or any other contention mechanism.
  • the STA 602 and STA 672 may receive and process the trigger frame 604.
  • 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.
  • the AP 640 may transmit a BA 610 to the STA 602, e.g., to acknowledge the PPDU 608.
  • 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.
  • 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.
  • 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.
  • 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.
  • non-AP STAs e.g., the STA implemented by device 102
  • triggered STAs e.g., the STA implemented by device 102
  • the response from a triggered STA may include information signaling the duration of the actual allocation to be used by the triggered STA.
  • 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.
  • a Control (Ctrl) frame e.g., CTS frame
  • Mgt management
  • any other type of frame which may be transmitted in a TB PPDU or a non-TB PPDU.
  • 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.
  • 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.
  • 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.
  • 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.
  • the trigger frame transmitter e.g., the STA implemented by device 140
  • the trigger frame transmitter 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.
  • 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.
  • the trigger frame transmitter e.g., the STA implemented by device 140
  • 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
  • the one bit signaling field may be reserved in the time allocation mode for the case when the SU-TF does not require alignment.
  • an AID value in the trigger frame may be set to contain a MAC address or some other identifier for the APs.
  • a Resource Unit (RU) field in the trigger frame may not be Reserved in the former case.
  • the AID field may signal a special value to signal that a MAC address is used.
  • the actual MAC address may be signaled separately in Trigger Dependent User Info.
  • 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.
  • the TXOP owner STA may be configured to multiplex regular UL transmissions with P2P transmissions, e.g., in different RUs.
  • 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.
  • the RU field may be set to signal the exact frequency allocation to be used.
  • the time allocation may be implemented with non- STR operation.
  • 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.
  • 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.
  • Fig. 7 schematically illustrates a method of time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • 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).
  • a system e.g., system 100 (Fig. 1)
  • wireless devices e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1)
  • a controller e.g., controller 124
  • the method may include transmitting the trigger frame to initiate the allocation of the allocated time to the non-AP STA.
  • 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.
  • Fig. 8 schematically illustrates a method of time allocation within a TxOP, in accordance with some demonstrative embodiments.
  • 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).
  • a system e.g., system 100 (Fig. 1)
  • wireless devices e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1)
  • a controller e.g., controller 124
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • AP Access Point
  • TxOP Transmit Opportunity
  • 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.
  • Example 3 includes the subject matter of Example 2, and optionally, wherein the response frame comprises a Clear to Send (CTS).
  • CTS Clear to Send
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • UL Uplink
  • P2P Peer-to Peer
  • 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.
  • UL Uplink
  • 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.
  • P2P Peer-to-Peer
  • 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.
  • 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.
  • NAV Network Allocation Vector
  • 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.
  • 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.
  • EHT Extremely High Throughput
  • Example 20 includes an apparatus comprising logic and circuitry configured to cause a non Access Point (AP) (non-AP) wireless communication station (STA) to:
  • AP Access Point
  • STA wireless communication station
  • [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;
  • Example 22 includes the subject matter of Example 21, and optionally, wherein the response frame comprises a Clear to Send (CTS).
  • CTS Clear to Send
  • 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.
  • 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.
  • 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.
  • 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.
  • UL Uplink
  • 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.
  • P2P Peer-to-Peer
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Example 37 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of Examples 1-34.
  • Example 38 comprises a method comprising any of the described operations of Examples 1-34.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Par exemple, une trame de déclenchement peut être communiquée d'une station (STA) point d'accès (AP) à une STA non AP. La trame de déclenchement peut être configurée pour indiquer une attribution d'un temps attribué pour la STA non AP durant une opportunité de transmission (TxOP) de la STA AP, le temps attribué étant configuré pour la transmission d'une ou plusieurs unités de données de protocole de couche physique (PHY) (PPDU) non basées sur un déclenchement (non TB) à partir de la STA non AP.
EP21867518.9A 2020-09-09 2021-09-08 Appareil, système et procédé d'attribution de temps durant une opportunité de transmission Pending EP4211964A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063076211P 2020-09-09 2020-09-09
PCT/US2021/049479 WO2022056009A1 (fr) 2020-09-09 2021-09-08 Appareil, système et procédé d'attribution de temps durant une opportunité de transmission

Publications (2)

Publication Number Publication Date
EP4211964A1 true EP4211964A1 (fr) 2023-07-19
EP4211964A4 EP4211964A4 (fr) 2024-10-16

Family

ID=80629977

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21867518.9A Pending EP4211964A4 (fr) 2020-09-09 2021-09-08 Appareil, système et procédé d'attribution de temps durant une opportunité de transmission

Country Status (2)

Country Link
EP (1) EP4211964A4 (fr)
WO (1) WO2022056009A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117596691A (zh) * 2022-08-08 2024-02-23 华为技术有限公司 基于被触发的传输机会共享机制的通信方法和通信装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11451424B2 (en) * 2018-03-26 2022-09-20 Lg Electronics Inc. Method and apparatus for transmitting PPDU on basis of S-TDMA in wireless LAN system
US11490261B2 (en) * 2018-07-10 2022-11-01 Lg Electronics Inc. Method and device for transmitting data in wireless LAN system

Also Published As

Publication number Publication date
EP4211964A4 (fr) 2024-10-16
WO2022056009A1 (fr) 2022-03-17

Similar Documents

Publication Publication Date Title
EP3289745B1 (fr) Appareil, système et procédé de communication sans fil multiutilisateur
US9801133B2 (en) Apparatus, system and method of communicating a wakeup packet response
US20220158790A1 (en) Apparatus, system, and method of a transmit sector sweep (txss) procedure over a millimeterwave (mmwave) wireless communication channel
US10362604B2 (en) Multi-user multiple-input multiple-output reverse direction duration communications
WO2016175943A1 (fr) Appareil, système et procédé de communication sans fil multi-utilisateur
US20190044596A1 (en) Apparatus, system and method of asymmetric beamforming training
EP3371959B1 (fr) Appareil, système et procédé de communication d'informations de contrôle dans une unité de données de protocole (ppdu) de protocole de convergence de couche physique (plcp)
WO2022051311A1 (fr) Appareil, système et procédé de communication sans fil avancée
US20230023324A1 (en) Apparatus, system, and method of communicating an extended range (er) physical layer (phy) protocol data unit (ppdu)
WO2018160213A1 (fr) Appareil, système, et procédé de communication d'une transmission à entrées multiples et sorties multiples (mimo) mono-utilisateur (su)
US11985080B2 (en) Apparatus, system, and method of communicating an extremely high throughput (EHT) physical layer (PHY) protocol data unit (PPDU)
EP3228139B1 (fr) Appareil, produit et procédé d'attribution dynamique utilisant une trame d'octroi
EP4211964A1 (fr) Appareil, système et procédé d'attribution de temps durant une opportunité de transmission
US20220225167A1 (en) Apparatus, system, and method of communicating bandwidth information of a wireless communication link
WO2022066881A1 (fr) Appareil, système et procédé d'accès prioritaire nsep (sécurité nationale et préparation aux situations d'urgence)
WO2022031832A1 (fr) Appareil, système et procédé de communication d'une unité de données de protocole (ppdu) de couche physique (phy) avec une indication d'une largeur de canal de 320 mhz
US20240224327A1 (en) Apparatus, system, and method of wireless communication during a transmit opportunity (txop)
US20230412711A1 (en) Apparatus, system, and method of communicating a physical layer (phy) protocol data unit (ppdu)
EP4440228A1 (fr) Appareil, système et procédé d'attribution de période de temps basée sur la contention pour trafic sensible à la latence
US20230328790A1 (en) Apparatus, system, and method of contending a wireless medium
US20230328791A1 (en) Apparatus, system, and method of multi access point (ap) (m-ap) operation over a wide channel bandwidth (bw)
US20220338147A1 (en) Apparatus, system, and method of communication during a synchronized transmit opportunity (s-txop)
US20220123882A1 (en) Apparatus, system, and method of wireless communication during a short-inter-frame-space (sifs)
US20240031087A1 (en) Apparatus, system, and method of 40 megahertz operating non access point (non-ap) station
US20230028973A1 (en) Apparatus, system, and method of time-sensitive communication via a multi user (mu) multiple-input-multiple-output (mimo) (mu-mimo) transmission

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230111

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20240912

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 74/04 20090101ALN20240906BHEP

Ipc: H04W 74/0816 20240101ALN20240906BHEP

Ipc: H04W 84/12 20090101ALI20240906BHEP

Ipc: H04W 74/00 20090101ALI20240906BHEP

Ipc: H04W 74/08 20090101ALI20240906BHEP

Ipc: H04W 72/04 20230101AFI20240906BHEP