WO2022031832A1 - 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 - Google Patents

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 Download PDF

Info

Publication number
WO2022031832A1
WO2022031832A1 PCT/US2021/044521 US2021044521W WO2022031832A1 WO 2022031832 A1 WO2022031832 A1 WO 2022031832A1 US 2021044521 W US2021044521 W US 2021044521W WO 2022031832 A1 WO2022031832 A1 WO 2022031832A1
Authority
WO
WIPO (PCT)
Prior art keywords
bits
ppdu
service field
eht
bit
Prior art date
Application number
PCT/US2021/044521
Other languages
English (en)
Inventor
Laurent Cariou
Robert Stacey
Po-Kai Huang
Daniel Bravo
Original Assignee
Intel Corporation
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 Corporation filed Critical Intel Corporation
Priority to CN202180048092.9A priority Critical patent/CN115777229A/zh
Publication of WO2022031832A1 publication Critical patent/WO2022031832A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0092—Indication of how the channel is divided

Definitions

  • Embodiments described herein generally relate to communicating a Physical layer (PHY) Protocol Data Unit (PPDU) with an indication of a 320 Megahertz (MHz) channel width.
  • PHY Physical layer
  • PPDU Protocol Data Unit
  • 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 service field bit assignment, which may be implemented in accordance with some demonstrative embodiments.
  • Fig. 4 is a schematic illustration of subfield values of a frame control field, which may be implemented in accordance with some demonstrative embodiments.
  • FIG. 5 is a schematic flow-chart illustration of a method of transmitting a PPDU with an indication of a 320 Megahertz (MHz) channel width, in accordance with some demonstrative embodiments.
  • FIG. 6 is a schematic flow-chart illustration of a method of processing a received PPDU with an indication of a 320 MHz channel width, in accordance with some demonstrative embodiments.
  • Fig. 7 is a schematic illustration of a product of manufacture, 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
  • 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 (UW
  • 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.
  • 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 5GHz frequency band, and/or a 6GHz frequency band.
  • a frequency band between 1GHz and 7.250Ghz for example, a 2.4 Gigahertz (GHz) frequency band, a 5GHz frequency band, and/or a 6GHz frequency band.
  • 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.
  • FIG. 1 schematically illustrates a system 100, in accordance with some demonstrative embodiments.
  • 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
  • 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.
  • 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.
  • 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
  • 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.
  • 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 may store data processed by device 102.
  • Memory unit 184 and/or storage unit 185 may store data processed by device 140.
  • wireless communication devices 102 and/or 140 may be capable of communicating content, data, information and/or signals via a wireless medium (WM) 103.
  • 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.
  • 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 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.
  • Rx wireless receivers
  • radio 114 may include at least one receiver 116
  • radio 144 may include at least one receiver 146.
  • 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.
  • Tx wireless transmitters
  • radio 114 may include at least one transmitter 118
  • radio 144 may include at least one transmitter 148.
  • 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.
  • radios 114 and/or 144 may include, or may be associated with one or more, e.g., a plurality of, antennas.
  • 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.
  • antennas 107 and/or antennas 147 may be connected to, and/or associated with, one or more Radio Frequency (RF) chains.
  • RF Radio Frequency
  • 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.
  • 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.
  • MAC Media- Access Control
  • PHY Physical Layer
  • BB baseband
  • AP Application Processor
  • controllers 124 and/or 154 may be implemented
  • 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.
  • 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.
  • 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).
  • SoC System on Chip
  • the chip or SoC may be configured to perform one or more functionalities of radio 114.
  • 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.
  • controller 124, message processor 128, and radio 114 may be implemented as part of the chip or SoC.
  • controller 124, message processor 128 and/or radio 114 may be implemented by one or more additional or alternative elements of device 102.
  • 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.
  • 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.
  • device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT STA
  • device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, at least one EHT 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.
  • a station 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.
  • 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.
  • STA station
  • WM wireless medium
  • the AP may perform any other additional or alternative functionality.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Gbps Giga bits per second
  • 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 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.1 Ibe Standard and/or any other standard and/or protocol.
  • OFDMA OFDMA
  • SU Single User
  • MU Multi-User
  • 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 STA
  • 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.
  • 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.
  • 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
  • a 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”).
  • 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.
  • 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 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.
  • a channel e.g., an EHT channel
  • a channel bandwidth including one or more 20MHz channels, for example, 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.
  • 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 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 and/or a Packet Extension (PE) field 220, e.g., following the data field 218.
  • 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.
  • 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.
  • 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.11be Specification and/or any other specification, e.g., as described below.
  • 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).
  • 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
  • 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.
  • any other additional or alternative channel width may be utilized.
  • PPDUs e.g., EHT PPDUs and/or any other PPDUs
  • BWs wide channel BWs
  • next generation Wi-Fi implementations e.g., as described below.
  • a first mode of 160 MHz operation may include a contiguous 160 MHz mode, which may utilize a contiguous 160MHz channel.
  • a second mode of 160 MHz operation may include an 80 MHz+80 MHz mode, where each 80 MHz segment is contiguous, but the two 80 MHz segments may not be contiguous.
  • Some demonstrative embodiments may be implemented to address one or more technical issues with respect to communicating PPDUs, e.g., EHT PPDUs and/or any other PPDUs, over a channel width, for example, a 320 MHz channel width, and/or any other wide channel widths, e.g., as described below.
  • PPDUs e.g., EHT PPDUs and/or any other PPDUs
  • a channel width for example, a 320 MHz channel width, and/or any other wide channel widths, e.g., as described below.
  • Some demonstrative embodiments may be implemented to address one or more technical issues with respect to communicating PPDUs, e.g., EHT PPDUs and/or any other PPDUs, over a contiguous 320 MHz channel width, and/or over a 160+160 MHz channel width, e.g., according to a two segment design of two 160MHz segments, e.g., as described below.
  • PPDUs e.g., EHT PPDUs and/or any other PPDUs
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to communicate one or more legacy PPDUs, e.g., non-HT PPDUs and/or non-HT duplicated PPDUs, for example, to maintain coexistence with one or more legacy STAs, e.g., one or more non-EHT and/or non-HT STAs, e.g., as described below.
  • legacy PPDUs e.g., non-HT PPDUs and/or non-HT duplicated PPDUs
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to communicate one or more legacy PPDUs, e.g., non-HT PPDUs and/or non-HT duplicated PPDUs, for example, in order to reserve a wireless medium, e.g., for obtaining a Transmit Opportunity (TXOP), for example, for transmission of one or more EHT PPDUs, e.g., as described below.
  • legacy PPDUs e.g., non-HT PPDUs and/or non-HT duplicated PPDUs
  • TXOP Transmit Opportunity
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to utilize EHT enabled operation on a wide bandwidth, e.g., a channel width of 320MHz.
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to utilize one or more fields in an EHT PPDU, which may be configured to indicate a bandwidth of the transmission of the PPDU.
  • an EHT PPDU which may include one or more fields configured to indicate an EHT bandwidth, e.g., a 320MHz channel width or any other EHT bandwidth
  • legacy frame formats for example, non-HT PPDU formats, may not be configured for indication of the EHT bandwidth.
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to utilize communication of one or more control frames according to a non- EHT format, e.g., a legacy format or a non-HT format, 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”).
  • the legacy devices may include non-EHT stations and/or non-High Throughput (HT) stations, which may be, for example, configured according to the IEEE 802.11-2020 Standard, and the like.
  • control frames may include, for example, a Request to Send (RTS) frame, a Clear to Send (CTS) frame, and/or any other type of control frame, e.g., according to the IEEE 802.11-2020 Standard.
  • RTS Request to Send
  • CTS Clear to Send
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to communicate the control frames, e.g., RTS, CTS and/or any other control frames, in a non-EHT format, for example, a non-HT format.
  • the control frames e.g., RTS, CTS and/or any other control frames
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to communicate the control frames, e.g., RTS, CTS and/or any other control frames, according to a non-HT PPDU format.
  • the control frames e.g., RTS, CTS and/or any other control frames
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to communicate the control frames, e.g., RTS, CTS and/or any other control frames, according to a non-HT -duplicate PPDU format, which may include duplication of the PPDU to be transmitted over a plurality of 20MHz channels, e.g., all 20MHz channels, that constitute the larger bandwidth signal.
  • the control frames e.g., RTS, CTS and/or any other control frames
  • a non-HT -duplicate PPDU format which may include duplication of the PPDU to be transmitted over a plurality of 20MHz channels, e.g., all 20MHz channels, that constitute the larger bandwidth signal.
  • a control mechanism may be utilized by a transmitter and a receiver to exchange a control sequence in order to know what bandwidth, e.g., a largest idle bandwidth, could be used during a TxOP.
  • the control sequence may include an RTS/CTS exchange.
  • an EHT STA e.g., the EHT STA implemented by device 102 and/or the EHT STA implemented by device 140, may be configured to utilize one or more PPDU fields, which may be configured to provide bandwidth information of a wide channel BW, e.g., a 320MHz channel width and/or any other channel width, in one or more PPDU formats, for example, a non-HT PPDU format and/or a non-HT duplicate PPDU format, e.g., as described below.
  • a wide channel BW e.g., a 320MHz channel width and/or any other channel width
  • a PPDU format e.g., a non-HT PPDU format and/or a non-HT duplicate PPDU format, may be configured to provide bandwidth information of a wide channel BW, e.g., as described below.
  • the PPDU format configured to provide the bandwidth information of the wide channel BW may be utilized to provide a technical solution to support communication of control frames, e.g., as part of a an RTS/CTS exchange and/or any other control frame exchange, for example, to derive an intended bandwidth of operation, and/or or to dynamically converge toward a highest bandwidth idle for both a receiver and transmitter, e.g., before transmission and/or reception.
  • control frames e.g., as part of a an RTS/CTS exchange and/or any other control frame exchange, for example, to derive an intended bandwidth of operation, and/or or to dynamically converge toward a highest bandwidth idle for both a receiver and transmitter, e.g., before transmission and/or reception.
  • 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 a PPDU including an indication of a 320MHz channel width.
  • the PPDU may include a control frame, e.g., as described below.
  • the control frame may include an RTS frame or a CTS frame, e.g., as described below. In other embodiments, any other type of control frame may be implemented.
  • devices 102 and/or 140 may be configured communicate the PPDU with the indication of the 320MHz channel width, for example, to support, set up, control, manage, initiate, and/or enable communication of an EHT PPDU, e.g., according to the EHT PPDU format 200 (Fig. 2), over the 320Mhz channel width.
  • the EHT STA implemented by device 102 may be configured to transmit a first control frame, e.g., an RTS, in a non-HT duplicate format.
  • a first control frame e.g., an RTS
  • the EHT STA implemented by device 102 may be configured to set the first control frame to include an indication of the 320 MHz channel width, e.g., as described below.
  • the EHT STA implemented by device 140 may be configured to receive and process the first control frame in the non-HT duplicate format.
  • the EHT STA implemented by device 140 may be configured to identify the 320 MHz channel width indicated by the first control frame, e.g., as described below.
  • the EHT STA implemented by device 140 may be configured to transmit a second control frame, e.g., a CTS, in a non-HT duplicate format.
  • the EHT STA implemented by device 140 may be configured to set the second control frame to include an indication of the 320 MHz channel width, e.g., as described below.
  • the EHT STA implemented by device 102 may be configured to receive and process the second control frame in the non-HT duplicate format.
  • the EHT STA implemented by device 102 may be configured to identify the 320 MHz channel width indicated by the second control frame, e.g., as described below.
  • the 320 MHz channel width may be indicated by a service field signaling mechanism, which may utilize a service field of the PPDU, e.g., as described below.
  • the service field signaling mechanism may be configured to support the operation of 320 MHz, for example, based on a channel-bandwidth-in-non-HT (CH_BANDWIDTH_IN_NON_HT) indication, e.g., as described below.
  • CH_BANDWIDTH_IN_NON_HT channel-bandwidth-in-non-HT
  • devices 102 and/or 140 may be configured to generate, process, transmit and/or receive a PPDU including a service field, which is set to indicate the 320 MHz channel width, e.g., as described below.
  • the service field may be part of a data field of the PDU, e.g., as described below.
  • controller 124 may be configured to cause an EHT STA implemented by device 102 to set three bits in a service field of a PPDU to a predefined bit setting configured to indicate a channel width of 320 MHz, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit the PPDU over the channel width of 320 MHz, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit the PPDU as a non-High- Throughput (non-HT) PPDU duplicated over a plurality of 20 MHz channel widths in the 320 MHz channel width, e.g., as described below.
  • the PPDU may be transmitted according to any other PPDU format.
  • the PPDU may include a control frame, e.g., as described below.
  • the PPDU may include a Request to Send (RTS) or a Clear to Send (CTS) , e.g., as described below.
  • RTS Request to Send
  • CTS Clear to Send
  • the PPDU may include any other type of control frame and. /or any other type of frame.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit the PPDU over the channel width of 320 MHz in a 6 Gigahertz (GHz) frequency band, e.g., as described below..
  • GHz 6 Gigahertz
  • the PPDU may be transmitted over any other channel and/or band.
  • the three bits in the service field may include two bits of a scrambler initialization sequence portion of the service field, and a bit of a reserved portion of the service field, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to set the three bits in the service field to the predefined bit setting by setting the two bits of the scrambler initialization sequence portion to a first predefined value, and setting the bit of the reserved portion to a second predefined value, e.g., as described below.
  • the second predefined value may be 1, e.g., as described below. In other embodiments any other value may be defined.
  • the first predefined value may be 0, e.g., as described below. In other embodiments any other value may be defined.
  • the scrambler initialization sequence portion may include 7 bits, e.g., as described below.
  • the two bits of the scrambler initialization sequence portion may include two last bits of the 7 bits, e.g., as described below.
  • the bit of the reserved portion may include a first bit in the reserved portion immediately subsequent to the two last bits of the 7 bits, e.g., as described below.
  • the service field may include 16 bits denoted as bits B0-B 15, e.g., as described below.
  • the three bits in the service field may include the bits B5, B6, and B7 of the service field, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to set the three bits in the service field to the predefined bit setting, for example, by setting the bits B5 and B6 to a first predefined value, and setting the bit B7 to a second predefined value, e.g., as described below.
  • the second predefined value may be 1, e.g., as described below. In other embodiments any other value may be defined.
  • the first predefined value may be 0, e.g., as described below. In other embodiments any other value may be defined.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to set the three bits in the service field to the predefined bit setting, for example, by setting the three bits in the service field to a three-bit value of 4, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to set the three bits in the service field to the predefined bit setting according to a Channel Bandwidth in non-High- Throughput (CH_BANDWIDTH_IN_NON_HT) parameter to indicate the channel width of 320 MHz, e.g., as described below.
  • CH_BANDWIDTH_IN_NON_HT Channel Bandwidth in non-High- Throughput
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to set a Transmit Address (TA) field in the PPDU to a bandwidth signaling TA, e.g., as described below.
  • TA Transmit Address
  • controller 154 may be configured to cause an EHT STA implemented by device 140 to process a service field in a received PPDU, for example, the PPDU transmitted by device 102, e.g., as described below.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to determine that a channel width of the PPDU is a channel width of 320 MHz based, for example, on a determination that three bits in the service field have a predefined bit setting configured to indicate the channel width of 320 MHz, e.g., as described below.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to receive the PPDU as a non-High- Throughput (non-HT) PPDU duplicated over a plurality of 20 MHz channel widths in the 320 MHz channel width, e.g., as described below.
  • non-HT High- Throughput
  • the PPDU may be received according to any other PPDU format.
  • the PPDU may include a control frame, e.g., as described below.
  • the PPDU may include an RTS or a CTS , e.g., as described below.
  • the PPDU may include any other type of control frame and./or any other type of frame.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to receive the PPDU in a 6 GHz frequency band, e.g., as described below..
  • the PPDU may be received over any other channel and/or band.
  • a TA field in the PPDU may include a bandwidth signaling TA, e.g., as described below.
  • the three bits in the service field may include two bits of a scrambler initialization sequence portion of the service field, and a bit of a reserved portion of the service field, e.g., as described below.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to determine that that three bits in the service field have the predefined bit setting based, for example, on a determination that the two bits of the scrambler initialization sequence portion have a first predefined value, and the bit of the reserved portion has a second predefined value, e.g., as described below.
  • the second predefined value may be 1, e.g., as described below. In other embodiments any other value may be defined.
  • the first predefined value may be 0, e.g., as described below. In other embodiments any other value may be defined.
  • the scrambler initialization sequence portion may include 7 bits, e.g., as described below.
  • the two bits of the scrambler initialization sequence portion may include two last bits of the 7 bits, e.g.,. as described below.
  • the bit of the reserved portion may include a first bit in the reserved portion immediately subsequent to the two last bits of the 7 bits, e.g., as described below.
  • the service field may include 16 bits denoted as bits B0-B15, and the three bits in the service field may include the bits B5, B6, and B7 of the service field, e.g., as described below.
  • any other bits may be used.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to determine that that three bits in the service field have the predefined bit setting based, for example, on a determination that the bits B5 and B6 have a first predefined value, and the bit B7 has a second predefined value, e.g., as described below.
  • the second predefined value may be 1, e.g., as described below. In other embodiments any other value may be defined.
  • the first predefined value may be 0, e.g., as described below. In other embodiments any other value may be defined.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to determine that that three bits in the service field have the predefined bit setting based, for example, on a determination that the three bits in the service field have a three-bit value of 4, e.gt., as described below.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to determine, based on the three bits in the service field, that a Channel Bandwidth in non-High-Throughput (CH_BANDWIDTH_IN_NON_HT) parameter is to indicate the channel width of 320 MHz, e.g., as described below.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit a first control frame, for example, an RTS, which may be configured to indicate the 320MHz channel width, e.g., as described above.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to configure the first control frame, e.g., the RTS, to indicate the 320MHz channel width, for example, to indicate an intent to communicate over the 320MHz channel width, e.g., during a TxOP.
  • the first control frame e.g., the RTS
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to configure the first control frame, e.g., the RTS, to indicate the 320MHz channel width, for example, based on a determination that the 320MHz channel width is idle.
  • the first control frame e.g., the RTS
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to receive and process the first control frame, e.g., the RTS, and to identify the indicated 320MHz channel width, e.g., as described above.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to transmit a second control frame, for example, a CTS, e.g., in response to the first control frame.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to configure the second control frame, e.g., the CTS, to indicate the 320MHz channel width, e.g., as described above.
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to configure the second control frame, e.g., the CTS, to indicate the 320MHz channel width, for example, based on a determination that the 320MHz channel width is idle.
  • the second control frame e.g., the CTS
  • controller 154 may be configured to cause the EHT STA implemented by device 140 to configure the second control frame, e.g., the CTS, to indicate another channel width, for example, narrower than the 320 MHz channel width, e.g., based on a channel bandwidth which is detected to be idle at the STA implemented by device 140.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to receive and process the second control frame, e.g., the CTS, and to identify the channel width indicated by the second control frame, e.g., as described above.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to establish a TxOP for communicating with the EHT STA implemented by device 140, for example, based on the exchange of the first and second control frames.
  • controller 124 may be configured to cause the EHT STA implemented by device 102, and/or controller 154 may be configured to cause the EHT STA implemented by device 140, to establish a TxOP for communication between the EHT STA implemented by device 140 and the EHT STA implemented by device 140, for example, based on the exchange of the first and second control frames.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit an EHT PPDU to the EHT STA implemented by device 140, for example, based on the exchange of the first and second control frames.
  • controller 124 may be configured to cause the EHT STA implemented by device 102 to transmit the EHT PPDU to the EHT STA implemented by device 140, for example, over a channel width, which may be determined based on the exchange of the first and second control frames.
  • FIG. 3 schematically illustrates a service field bit assignment, which may be implemented in accordance with some demonstrative embodiments.
  • a service field 300 may include a plurality of bits, for example, 16 bits, denoted as bits B0...B15 (or bits 0...15).
  • bits B0...B15 or bits 0...15
  • the bit 0 may be transmitted first in time.
  • the service field 300 may be configured for use in a PPDU, for example, according to a non-HT PPDU format, e.g., a non-HT duplicate PPDU format.
  • the service field 300 may be included as part of a data field of a PPDU.
  • the data field may include the service field 300, which may be followed by a PSDU.
  • abit assignment of service field 300 may be configured, for example, in compliance with the non-HT PPDU format, e.g., the non-HT duplicate PPDU format, for example, in compliance with the IEEE 802.11- 2020 Specification.
  • the bit assignment of service field 300 may include a scrambler initialization sequence portion 302, which may be followed by a reserved portion 304.
  • the scrambler initialization sequence portion 302 may include 7 bits, e.g., the bits B0, Bl, B2, B3, B4, B5, and B6.
  • the reserved portion 304 may include 9 bits, e.g., the bits B7, B8, B9, B 10, Bl l, B12, B 13, B14, and B 15.
  • bits of the scrambler initialization sequence portion 302 may be utilized to indicate a channel width, for example, in control frames, e.g., as described below.
  • a Transmit Address (TA) field of control frames may be set to a bandwidth signaling TA, for example, by setting an individual/group bit of a MAC address to 1. Any other additional or alternative mechanism may be implemented to indicate the bandwidth signaling TA.
  • TA Transmit Address
  • bits of the service field of the PPDU e.g., at least bits which may usually be used for scrambling initialization, e.g., bits in portion 302, may be reused for bandwidth signaling.
  • bits of the service field of the PPDU may be set to carry the bandwidth of the PPDU, and/or one or more other indications, for example, whether a device transmitting the PPDU supports static or dynamic bandwidth operation.
  • bits of scrambler initialization sequence portion 302 of service field 300 may be used to provide a channel width indication, for example, when the TA filed of the PPDU is set to the bandwidth signaling TA.
  • bits of scrambler initialization sequence portion 302 of service field 300 may be used to indicate a CH_BANDWIDTH_IN_NON_HT parameter, which may be used to indicate a channel width of the PPDU, e.g., as described below.
  • 3 bits of the service field 300 may be utilized to indicate a channel width of 320MHz, e.g., as described below.
  • the 3 bits of the service field 300 which are utilized to indicate the channel width of 320MHz, may include two bits of the scrambler initialization sequence portion 302 and a bit of the reserved portion 304, e.g., as described below.
  • the 3 bits of the service field 300 which are utilized to indicate the channel width of 320MHz, may include the bits B5, B6, and B7 of the service field 300, e.g., as described below.
  • 3 bits of the service field 300 may be utilized to indicate the CH_BANDWIDTH_IN_NON_HT parameter for a channel width of 320MHz, e.g., as described below.
  • the 3 bits of the service field 300 which are utilized to indicate the CH_BANDWIDTH_IN_NON_HT parameter for the channel width of 320MHz, may include two bits of the scrambler initialization sequence portion 302 and a bit of the reserved portion 304, e.g., as described below.
  • the 3 bits of the service field 300 which are utilized to indicate the CH_BANDWIDTH_IN_NON_HT parameter for the channel width of 320MHz, may include the bits B5, B6, and B7 of the service field 300, e.g., as described below.
  • a bit of the reserved bits in reserved potion 304 may be utilized, e.g., together with two bits of the scrambler initialization sequence portion 302, for example, in order to define the CH_BANDWDITH_IN_NON_HT field and/or a Channel-BW-in-non-HT-temp (CBWinNonHTtemp) field as a 3-bit field, e.g., instead of a 2 -bit field including only bits of the scrambler initialization sequence portion 302.
  • CBWinNonHTtemp Channel-BW-in-non-HT-temp
  • the bit of the reserved bits in reserved potion 304 may be utilized, e.g., together with two bits of the scrambler initialization sequence portion 302, for example, in order to define the CH_B ANDWDITH_IN_NON_HT field and/or the CBWinNonHTtemp field as a 3-bit field, for example, when the PPDU is to be sent to a Next Best Thing (NBT) STA.
  • NBT Next Best Thing
  • this new bit may not be modulated, for example, if the transmission is to be sent towards a non-HT STA, e.g., a STA in compliance with an IEEE 802.11ax Specification.
  • bit B7 of service field 300 may be set together with two bits of the scrambler initialization sequence portion 302, e.g., bits B5 and B6, in order to define the CH_BANDWDITH_IN_NON_HT field and/or the CBWinNonHTtemp field as a 3-bit field.
  • another option may be to use three bits of the seven bits of the scrambler initialization sequence portion 302 to define the CH_B ANDWDITH_IN_NON_HT field and/or the CBWinNonHTtemp field as a 3-bit field.
  • bit of the 7 bits of the scrambler initialization sequence portion 302 may be used in addition to the bits B5 and B6.
  • a number of bits used to generate a pseudo-random integer may be reduced from 4 bits to 3 bits.
  • one of the bits B0-B4, e.g., the bit B3 or any other bit, may be used together with the bits B5 and B6 to define the CH_BANDWDITH_IN_NON_HT field and/or the CBWinNonHTtemp field, e.g., for signaling the 320MHz channel width.
  • the remaining bits of bits B0-B4, e.g., the bots B0, B l, B2, and/or B4 may be used to generate a pseudorandom integer.
  • the additional bit e.g., the bit B7 in the reserved portion 304, or the additional bit in the scrambler initialization sequence portion 302, e.g., bit B3, may be used to indicate one or more modes or combinations for the 320MHz channel width, e.g., in a contiguous format or a non-contiguous format.
  • the additional bit e.g., the bit B7 in the reserved portion 304, or the additional bit in the scrambler initialization sequence portion 302, e.g., bit B3, may be set to a predefined value, e.g., 1, and the 2 bits in the scrambler initialization sequence portion 302, e.g., bits B5 and B6, may be set to a predefined value, e.g., 3, in order to define a new 320MHz channel width mode.
  • a dotllcurrentchannelcenterfrequencyindexl parameter may be set to a first value, e.g., 0, for contiguous operation over a contiguous 320Mhz channel width.
  • the dotllcurrentchannelcenterfrequencyindexl parameter may be set to a second value, e.g., other than 0, for a non-contiguous 160+160MHz channel width.
  • this signaling scheme may be in accordance with a signaling scheme for 160 MHz, for example, if the additional bit, e.g., the bit B7 in the reserved portion 304, or the additional bit in the scrambler initialization sequence portion 302, e.g., bit B3, is set to 0.
  • the 3-bit CH_B ANDWDITH_IN_NON_HT field and/or the 3-bit CBWinNonHTtemp field may be defined as a new 3-bit field with 8 combinations, e.g., based on the values of the three bits in the service field 300.
  • the three bits in the service field 300 may include the 2 bits in the scrambler initialization sequence portion 302, e.g., bits B5 and B6, and the additional bit, e.g., the bit B7 in the reserved portion 304, or the additional bit in the scrambler initialization sequence portion 302, e.g., bit B3, as described above.
  • the 3-bit value of 0 may be assigned to indicate the 20 MHz channel width
  • the 3-bit value of 1 may be assigned to indicate the 40 MHz channel width
  • the 3-bit value of 2 may be assigned to indicate the 80 MHz channel width
  • the 3-bit value of 3 may be assigned to indicate the 160 MHz channel width
  • the 3- bit value of 4 may be assigned to indicate the 320 MHz channel width.
  • the 3-bit CH_BANDWDITH_IN_NON_HT field and/or the 3- bit CBWinNonHTtemp field may be defined as follows:
  • 3-bit values e.g., 5, 6, and/or 7, may be used to indicate further extensions, e.g., to a 640MHz channel width.
  • devices 102 and/or 140 may be configured to generate, process, transmit and/or receive a PPDU including an indication on whether the service field of the PPDU is to be interpreted to include the 3-bit indication of the channel width, e.g., as described below.
  • the indication whether the service field of the PPDU is to be interpreted to include the 3-bit indication of the channel width may be useful in supporting a receiver of the PPDU to determine how to process the bits of the service field. For example, it may be indicated to the received whether to process the bits of the service field according to the 3-bit channel width indication, e.g., as described above, or whether to process the bits of the service field according to a 2- bit channel width indication.
  • the TA field that carries the MAC address of the transmitter in control frames may be configured as the bandwidth signaling TA, for example, by modifying the MAC address by setting the Individual/Group bit to 1, e.g., instead of 0, as described above.
  • another bit may be changed, e.g., from 0 to 1, in the MAC address, for example, in order to signal that the TA field is to be recognized as an “EHT bandwidth signaling TA”.
  • the service field is encoded as, and is to processed as, containing the mechanism described above for allowing the signaling of the 320 MHz bandwidth, e.g., using the 3-bit value.
  • another option may be to use a reserved field in the MAC header of the corresponding frame.
  • FIG. 4 schematically illustrates subfield values of a frame control field, which may be implemented in accordance with some demonstrative embodiments.
  • one of the fields of the frame control field of Fig. 4 may be set to “1” and used as a non-reserved field.
  • at least one of the fields “To DS”, “From DS”, “More Frag”, “Retry”, “Protected Frame” and/or “+HTC”, may be set to a value of “1” to indicate that the service field is encoded as, and is to processed as, containing the mechanism described above for allowing the signaling of the 320 MHz bandwidth, e.g., using the 3-bit value.
  • a Receiver Address (RA) field of the PPDU may be configured to provide the indication on whether the service field of the PPDU is to be interpreted to include the 3-bit indication of the channel width.
  • a transmitter of the PPDU e.g., the STA implemented by device 102 (Fig. 1), may include a bandwidth signaling TA in the TA field of the PPDU and a bandwidth signaling RA in the RA field of the PPDU.
  • the bandwidth signaling RA may be identified when the unicast/multicast bit in the MAC address of the RA field is set to multicast, e.g., instead of unicast. Any other setting of the RA field may be used to indicate the EHT bandwidth signaling RA.
  • devices 102 and/or 140 may be configured to generate, process, transmit and/or receive a PPDU including an indication of the 320Mhz field, for example, based on two bits in the service field, e.g., service field 300 (Fig., 3), as described below.
  • the 2-bit field format e.g., using the bits B5 and B6 of service field 300 (Fig. 3) may be redefined in cases of a PPDU transmitted to an EHT STA, e.g., an NBT STA.
  • the entries of the 2-bit value may be shifted, e.g., from (0 for 20MHz, 1 for 40MHz, 2 for 80MHz, 3 for 160MHz), to (0 for 40MHz, 1 for 80MHz, 2 for 160MHz, 3 for 320MHz).
  • a first set of entries (0 for 20MHz, 1 for 40MHz, 2 for 80MHz, 3 for 160MHz) may be used to interpret PPDUs transmitted to non-EHT STAs
  • a second set of entries (0 for 40MHz, 1 for 80MHz, 2 for 160MHz, 3 for 320MHz) may be used to interpret PPDUs transmitted to EHT STAs.
  • another option for signaling the 320MHz bandwidth may be to define a new control frame format, e.g., a new RTS frame, a new CTS frame, and/or any other new control frame indicating a channel width, for communication over the 6GHz band.
  • a new field may be utilized to indicate the bandwidth in these new frames. This field can be of 3 bits or more if more non-contiguous combinations are needed.
  • the CTS frame may be configured to also include both a TA field and a Receiver Address (RA) field.
  • RA Receiver Address
  • Fig. 5 schematically illustrates a method of transmitting a PPDU with an indication of a 320 MHz channel width, in accordance with some demonstrative embodiments.
  • 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)
  • controller e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1)
  • the method may include setting three bits in a service field of a PPDU to a predefined bit setting configured to indicate a channel width of 320 MHz.
  • controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to set three bits in a service field of the PPDU to a predefined bit setting configured to indicate the channel width of 320 MHz, e.g., as described above.
  • the method may include transmitting the PPDU over the channel width of 320 MHz.
  • controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to transmit the PPDU over the channel width of 320 MHz, e.g., as described above.
  • Fig. 6 schematically illustrates a method of processing a received PPDU with an indication of a 320 MHz channel width, in accordance with some demonstrative embodiments.
  • 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)
  • controller e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1)
  • the method may include processing a service field in a received PPDU.
  • controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to process the service field in the received PPDU, e.g., as described above.
  • the method may include determining that a channel width of the PPDU is a channel width of 320 MHz, for example, based on a determination that three bits in the service field have a predefined bit setting configured to indicate the channel width of 320 MHz.
  • controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to determine that the channel width of the PPDU is the channel width of 320 MHz, for example, based on a determination that three bits in the service field have the predefined bit setting configured to indicate the channel width of 320 MHz, e.g., as described above.
  • Product 700 may include one or more tangible computer-readable (“machine-readable”) non- transitory storage media 702, which may include computer-executable instructions, e.g., implemented by logic 704, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at device 102 (Fig. 1), device 140 (Fig. 1), 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 700 and/or machine readable storage media 702 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like.
  • machine readable storage media 702 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide- silicon (SONOS) memory, a hard drive, an optical disk, a magnetic disk, and the like.
  • RAM random access memory
  • DDR-DRAM Double-Data-Rate DRAM
  • SDRAM static RAM
  • SRAM static RAM
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable programmable ROM
  • EEPROM electrically erasable programmable ROM
  • flash memory e.g., NOR or NAND flash memory
  • CAM
  • 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.
  • logic 704 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein.
  • the machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
  • logic 704 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like.
  • the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • the instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function.
  • the instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, 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 Extremely High Throughput (EHT) wireless communication station (STA) to set three bits in a service field of a Physical layer (PHY) Protocol Data Unit (PPDU) to a predefined bit setting configured to indicate a channel width of 320 Megahertz (MHz); and transmit the PPDU over the channel width of 320 MHz.
  • EHT Extremely High Throughput
  • STA wireless communication station
  • PHY Physical layer
  • PPDU Protocol Data Unit
  • Example 2 includes the subject matter of Example 1, and optionally, wherein the three bits in the service field comprise two bits of a scrambler initialization sequence portion of the service field, and a bit of a reserved portion of the service field.
  • Example 3 includes the subject matter of Example 2, and optionally, wherein the apparatus is configured to cause the EHT STA to set the three bits in the service field to the predefined bit setting by setting the two bits of the scrambler initialization sequence portion to a first predefined value, and setting the bit of the reserved portion to a second predefined value.
  • Example 4 includes the subject matter of Example 3, and optionally, wherein the second predefined value is 1.
  • Example 5 includes the subject matter of Example 3 or 4, and optionally, wherein the first predefined value is 0.
  • Example 6 includes the subject matter of any one of Examples 2-5, and optionally, wherein the scrambler initialization sequence portion comprises 7 bits, wherein the two bits of the scrambler initialization sequence portion comprise two last bits of the 7 bits, and the bit of the reserved portion comprises a first bit in the reserved portion immediately subsequent to the two last bits of the 7 bits.
  • Example 7 includes the subject matter of any one of Examples 1-6, and optionally, wherein the service field comprises 16 bits denoted as bits B0-B15, and wherein the three bits in the service field comprise the bits B5, B6, and B7 of the service field.
  • Example 8 includes the subject matter of Example 7, and optionally, wherein the apparatus is configured to cause the EHT STA to set the three bits in the service field to the predefined bit setting by setting the bits B5 and B6 to a first predefined value, and setting the bit B7 to a second predefined value.
  • Example 9 includes the subject matter of Example 8, and optionally, wherein the second predefined value is 1.
  • Example 10 includes the subject matter of Example 8 or 9, and optionally, wherein the first predefined value is 0.
  • Example 11 includes the subject matter of any one of Examples 1-10, and optionally, wherein the apparatus is configured to cause the EHT STA to set the three bits in the service field to the predefined bit setting by setting the three bits in the service field to a three -bit value of 4.
  • Example 12 includes the subject matter of any one of Examples 1-11, and optionally, wherein the apparatus is configured to cause the EHT STA to set the three bits in the service field to the predefined bit setting according to a Channel Bandwidth in non-High-Throughput (CH_BANDWIDTH_IN_NON_HT) parameter to indicate the channel width of 320 MHz.
  • CH_BANDWIDTH_IN_NON_HT Channel Bandwidth in non-High-Throughput
  • Example 13 includes the subject matter of any one of Examples 1-12, and optionally, wherein the apparatus is configured to cause the EHT STA to transmit the PPDU as a non-High-Throughput (non-HT) PPDU duplicated over a plurality of 20 MHz channel widths in the 320 MHz channel width.
  • non-HT Non-High-Throughput
  • Example 14 includes the subject matter of any one of Examples 1-13, and optionally, wherein the apparatus is configured to set a Transmit Address (TA) field in the PPDU to a bandwidth signaling TA.
  • TA Transmit Address
  • Example 15 includes the subject matter of any one of Examples 1-14, and optionally, wherein the PPDU comprises a control frame.
  • Example 16 includes the subject matter of any one of Examples 1-15, and optionally, wherein the PPDU comprises a Request to Send (RTS) or a Clear to Send (CTS).
  • RTS Request to Send
  • CTS Clear to Send
  • Example 17 includes the subject matter of any one of Examples 1-16, and optionally, wherein the apparatus is configured to cause the EHT STA to transmit the PPDU over the channel width of 320 MHz in a 6 Gigahertz (GHz) frequency band.
  • the apparatus is configured to cause the EHT STA to transmit the PPDU over the channel width of 320 MHz in a 6 Gigahertz (GHz) frequency band.
  • GHz Gigahertz
  • Example 18 includes the subject matter of any one of Examples 1-17, and optionally, comprising a radio to transmit the PPDU.
  • 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 EHT STA.
  • Example 20 includes an apparatus comprising logic and circuitry configured to cause an Extremely High Throughput (EHT) wireless communication station (STA) to process a service field in a received Physical layer (PHY) Protocol Data Unit (PPDU); and determine that a channel width of the PPDU is a channel width of 320 Megahertz (MHz) based on a determination that three bits in the service field have a predefined bit setting configured to indicate the channel width of 320 MHz.
  • Example 21 includes the subject matter of Example 20, and optionally, wherein the three bits in the service field comprise two bits of a scrambler initialization sequence portion of the service field, and a bit of a reserved portion of the service field.
  • Example 22 includes the subject matter of Example 21, and optionally, wherein the apparatus is configured to cause the EHT STA to determine that that three bits in the service field have the predefined bit setting based on a determination that the two bits of the scrambler initialization sequence portion have a first predefined value, and the bit of the reserved portion has a second predefined value.
  • Example 23 includes the subject matter of Example 22, and optionally, wherein the second predefined value is 1.
  • Example 24 includes the subject matter of Example 22 or 23, and optionally, wherein the first predefined value is 0.
  • Example 25 includes the subject matter of any one of Examples 21-24, and optionally, wherein the scrambler initialization sequence portion comprises 7 bits, wherein the two bits of the scrambler initialization sequence portion comprise two last bits of the 7 bits, and the bit of the reserved portion comprises a first bit in the reserved portion immediately subsequent to the two last bits of the 7 bits.
  • Example 26 includes the subject matter of any one of Examples 20-25, and optionally, wherein the service field comprises 16 bits denoted as bits B0-B15, and wherein the three bits in the service field comprise the bits B5, B6, and B7 of the service field.
  • Example 27 includes the subject matter of Example 26, and optionally, wherein the apparatus is configured to cause the EHT STA to determine that that three bits in the service field have the predefined bit setting based on a determination that the bits B5 and B6 have a first predefined value, and the bit B7 has a second predefined value.
  • Example 28 includes the subject matter of Example 27, and optionally, wherein the second predefined value is 1.
  • Example 29 includes the subject matter of Example 27 or 28, and optionally, wherein the first predefined value is 0.
  • Example 30 includes the subject matter of any one of Examples 20-29, and optionally, wherein the apparatus is configured to cause the EHT STA to determine that that three bits in the service field have the predefined bit setting based on a determination that the three bits in the service field have a three-bit value of 4.
  • Example 31 includes the subject matter of any one of Examples 20-30, and optionally, wherein the apparatus is configured to cause the EHT STA to determine, based on the three bits in the service field, that a Channel Bandwidth in non-High- Throughput (CH_BANDWIDTH_IN_NON_HT) parameter is to indicate the channel width of 320 MHz.
  • CH_BANDWIDTH_IN_NON_HT Channel Bandwidth in non-High- Throughput
  • Example 32 includes the subject matter of any one of Examples 20-31, and optionally, wherein the PPDU comprises a non-High-Throughput (non-HT) PPDU duplicated over a plurality of 20 MHz channel widths in the 320 MHz channel width.
  • non-HT non-High-Throughput
  • Example 33 includes the subject matter of any one of Examples 20-32, and optionally, wherein a Transmit Address (TA) field in the PPDU comprises a bandwidth signaling TA.
  • TA Transmit Address
  • Example 34 includes the subject matter of any one of Examples 20-33, and optionally, wherein the PPDU comprises a control frame.
  • Example 35 includes the subject matter of any one of Examples 20-34, and optionally, wherein the PPDU comprises a Request to Send (RTS) or a Clear to Send (CTS).
  • RTS Request to Send
  • CTS Clear to Send
  • Example 36 includes the subject matter of any one of Examples 20-35, and optionally, wherein the PPDU comprises a PPDU received in a 6 Gigahertz (GHz) frequency band.
  • GHz Gigahertz
  • Example 37 includes the subject matter of any one of Examples 20-36, and optionally, comprising a radio to receive the PPDU.
  • Example 38 includes the subject matter of Example 37, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the EHT STA.
  • Example 39 comprises an apparatus comprising means for executing any of the described operations of Examples 1-38.
  • Example 40 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- 38.
  • Example 41 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of Examples 1-38.
  • Example 42 comprises a method comprising any of the described operations of Examples 1-38.

Landscapes

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

Abstract

Par exemple, une station de communication sans fil (STA) peut être configurée pour générer, transmettre, recevoir et/ou traiter, une unité de données de protocole (PPDU) de couche physique (PHY) avec une indication d'une largeur de canal de 320 mégahertz (MHz). Par exemple, la PPDU peut être configurée pour comprendre trois bits dans un champ de service réglé à un réglage de bit prédéfini configuré pour indiquer une largeur de canal de 320 MHz.
PCT/US2021/044521 2020-08-05 2021-08-04 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 WO2022031832A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180048092.9A CN115777229A (zh) 2020-08-05 2021-08-04 传递具有320mhz信道宽度的指示的物理层（phy）协议数据单元（ppdu）的装置、系统和方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202063061428P 2020-08-05 2020-08-05
US63/061,428 2020-08-05
US202063063829P 2020-08-10 2020-08-10
US63/063,829 2020-08-10

Publications (1)

Publication Number Publication Date
WO2022031832A1 true WO2022031832A1 (fr) 2022-02-10

Family

ID=80118783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/044521 WO2022031832A1 (fr) 2020-08-05 2021-08-04 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

Country Status (2)

Country Link
CN (1) CN115777229A (fr)
WO (1) WO2022031832A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023167499A1 (fr) * 2022-03-02 2023-09-07 엘지전자 주식회사 Largeur de bande d'une unité de données dans un système lan sans fil

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130155953A1 (en) * 2011-12-16 2013-06-20 Stmicroelectronics, Inc. Channel bandwidth indication and txop protection
US20170223665A1 (en) * 2014-08-07 2017-08-03 Lg Electronics Inc. Multi-user transmission method in wireless communication system and device therefor
US20180343585A1 (en) * 2011-05-12 2018-11-29 Electronics And Telecommunications Research Institute Method for transmitting data frame in wireless local area network and apparatus for the same
US20190215884A1 (en) * 2018-01-10 2019-07-11 Qualcomm Incorporated Mechanisms to support secondary channel operation
WO2020009425A1 (fr) * 2018-07-03 2020-01-09 엘지전자 주식회사 Procédé et dispositif d'identification de paquet dans un système lan sans fil

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180343585A1 (en) * 2011-05-12 2018-11-29 Electronics And Telecommunications Research Institute Method for transmitting data frame in wireless local area network and apparatus for the same
US20130155953A1 (en) * 2011-12-16 2013-06-20 Stmicroelectronics, Inc. Channel bandwidth indication and txop protection
US20170223665A1 (en) * 2014-08-07 2017-08-03 Lg Electronics Inc. Multi-user transmission method in wireless communication system and device therefor
US20190215884A1 (en) * 2018-01-10 2019-07-11 Qualcomm Incorporated Mechanisms to support secondary channel operation
WO2020009425A1 (fr) * 2018-07-03 2020-01-09 엘지전자 주식회사 Procédé et dispositif d'identification de paquet dans un système lan sans fil

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023167499A1 (fr) * 2022-03-02 2023-09-07 엘지전자 주식회사 Largeur de bande d'une unité de données dans un système lan sans fil

Also Published As

Publication number Publication date
CN115777229A (zh) 2023-03-10

Similar Documents

Publication Publication Date Title
US10250355B2 (en) Apparatus, system and method of multi-user wireless communication
EP3289745B1 (fr) Appareil, système et procédé de communication sans fil multiutilisateur
US10015745B2 (en) Apparatus, system and method of communicating a wakeup packet
EP3289800B1 (fr) Appareil, système et procédé de communication d'une trame de communication sans fil avec un en-tête
US11902070B2 (en) Apparatus, system and method of communicating a physical layer protocol data unit (PPDU) including a training field
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)
WO2017074625A1 (fr) Appareil, système et procédé de communication sur la base d'une évaluation de canal libre (cca) dans une ou plusieurs directions
CN108476187B (zh) 根据传输空间-频率分集方案进行通信的装置、系统和方法
EP4209091A1 (fr) Appareil, système et procédé de communication sans fil avancée
US11985080B2 (en) Apparatus, system, and method of communicating an extremely high throughput (EHT) physical layer (PHY) protocol data unit (PPDU)
WO2018183081A1 (fr) Appareil, système et procédé de communication d'une ppdu mu edmg à champ b d'en-tête
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
WO2018017228A1 (fr) Appareil, système et procédé de communication d'une transmission selon un schéma de modulation d'amplitude en quadrature (qam) 256 entraîné en rotation
WO2023154084A1 (fr) Appareil, système et procédé de sondage de canal sur une large bande passante de canal
WO2019005747A1 (fr) Appareil, système et procédé de communication d'une unité de données de protocole (ppdu) de couche physique (phy) de multiplexage par répartition orthogonale de la fréquence (ofdm) multi-gigabits directionnelle améliorée (dmg) (edmg)
EP4211964A1 (fr) Appareil, système et procédé d'attribution de temps durant une opportunité de transmission
EP3602989B1 (fr) Appareil, système et procédé de communication d'une ppdu mu edmg ayant un champ b d'en-tête comprenant la répétition et le scramblage de bits d'en-tête codés
US20230023324A1 (en) Apparatus, system, and method of communicating an extended range (er) physical layer (phy) protocol data unit (ppdu)
US20230412711A1 (en) Apparatus, system, and method of communicating a physical layer (phy) protocol data unit (ppdu)
US20220338147A1 (en) Apparatus, system, and method of communication during a synchronized transmit opportunity (s-txop)
US20240022347A1 (en) Apparatus, system, and method of communicating unequal modulation and coding scheme (mcs) (uem) information
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
WO2022066881A1 (fr) Appareil, système et procédé d'accès prioritaire nsep (sécurité nationale et préparation aux situations d'urgence)
US20240048269A1 (en) Apparatus, system, and method of a pre forward error correction (fec) (pre-fec) padding

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21853186

Country of ref document: EP

Kind code of ref document: A1