[go: up one dir, main page]

EP4548485A1 - Appareil, système et procédé de communication d'un paquet avec un champ d'apprentissage (trn) - Google Patents

Appareil, système et procédé de communication d'un paquet avec un champ d'apprentissage (trn)

Info

Publication number
EP4548485A1
EP4548485A1 EP22949634.4A EP22949634A EP4548485A1 EP 4548485 A1 EP4548485 A1 EP 4548485A1 EP 22949634 A EP22949634 A EP 22949634A EP 4548485 A1 EP4548485 A1 EP 4548485A1
Authority
EP
European Patent Office
Prior art keywords
trn
field
sta
mmwave
packet
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22949634.4A
Other languages
German (de)
English (en)
Inventor
Laurent Cariou
Thomas J. Kenney
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP4548485A1 publication Critical patent/EP4548485A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/261—Details of reference signals
    • H04L27/2613—Structure of the reference signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06958—Multistage beam selection, e.g. beam refinement

Definitions

  • TRN Training Training
  • Devices in a wireless communication system may be configured to communicate over a millimeterWave (mmWave) wireless communication channel.
  • mmWave millimeterWave
  • FIG. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative aspects.
  • FIG. 2 is a schematic illustration of a multi-link communication scheme, which may be implemented in accordance with some demonstrative aspects.
  • FIG. 3 is a schematic illustration of a multi-link communication scheme, which may be implemented in accordance with some demonstrative aspects.
  • Fig. 4 is a schematic illustration of a Null Data Packet (NDP), in accordance with some demonstrative aspects.
  • Fig. 6 is a schematic illustration of a Physical layer (PHY) Protocol Data Unit (PPDU), in accordance with some demonstrative aspects.
  • PHY Physical layer
  • PPDU Protocol Data Unit
  • FIG. 7 is a schematic illustration of a packet exchange, in accordance with some demonstrative aspects.
  • FIG. 8 is a schematic illustration of a packet exchange, in accordance with some demonstrative aspects.
  • 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 aspect”, “an aspect”, “demonstrative aspect”, “various aspects” etc. indicate that the aspect(s) so described may include a particular feature, structure, or characteristic, but not every aspect necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one aspect” does not necessarily refer to the same aspect, although it may.
  • 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, December, 2020); and/or IEEE 802.11be (IEEE P802.11be/D1.5 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), March 2022)) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.
  • IEEE 802.11- 2020 IEEE 802.11-
  • Some aspects may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Infra-Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division Multiple Access (SDMA), Extended TDMA (E- TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBeeTM, Ultra-Wideband (UWB), 4G
  • 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
  • circuitry may include logic, at least partially operable in hardware.
  • logic may refer, for example, to computing logic embedded in circuitry of a computing apparatus and/or computing logic stored in a memory of a computing apparatus.
  • the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and/or operations.
  • logic may be embedded in various types of memory and/or firmware, e.g., silicon blocks of various chips and/or processors.
  • Logic may be included in, and/or implemented as part of, various circuitry, e.g. radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, and/or the like.
  • logic may be embedded in volatile memory and/or non-volatile memory, including random access memory, read only memory, programmable memory, magnetic memory, flash memory, persistent memory, and the like.
  • Logic may be executed by one or more processors using memory, e.g., registers, stuck, buffers, and/or the like, coupled to the one or more processors, e.g., as necessary to execute the logic.
  • Some demonstrative aspects may be used in conjunction with a WLAN, e.g., a WiFi network.
  • Other aspects may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a “piconet”, a WPAN, a WVAN and the like.
  • EHF Extremely High Frequency
  • mmWave millimeter wave
  • a wireless communication network communicating over an Extremely High Frequency (EHF) band (also referred to as the “millimeter wave (mmWave)” frequency band), for example, a frequency band within the frequency band of between 20Ghz and 300GHz, for example, a frequency band above 45GHz, e.g., a 60GHz frequency band, and/or any other mmWave frequency band.
  • EHF Extremely High Frequency
  • Some demonstrative aspects may be used in conjunction with a wireless communication network communicating over the sub- 10 GHz frequency band and/or the mmWave frequency band, e.g., as described below.
  • a wireless communication network communicating over the sub- 10 GHz frequency band and/or the mmWave frequency band, e.g., as described below.
  • other aspects may be implemented utilizing any other suitable wireless communication frequency bands, for example, a 5G frequency band, a frequency band below 20GHz, a Sub 1 GHz (SIG) band, a WLAN frequency band, a WPAN frequency band, and the like.
  • SIG Sub 1 GHz
  • mmWave STA which may include for example, a STA having a radio transmitter, which is capable of operating on a channel that is within the mmWave frequency band.
  • mmWave communications may involve one or more directional links to communicate at a rate of multiple gigabits per second, for example, at least 1 Gigabit per second, e.g., at least 7 Gigabit per second, at least 30 Gigabit per second, or any other rate.
  • the mmWave STA may include a Directional Multi-Gigabit (DMG) STA, which may be configured to communicate over a DMG frequency band.
  • DMG Directional Multi-Gigabit
  • the DMG band may include a frequency band wherein the channel starting frequency is above 45 GHz.
  • the mmWave STA may include an Enhanced DMG (EDMG) STA, which may be configured to implement one or more mechanisms, which may be configured to enable Single User (SU) and/or Multi-User (MU) communication of Downlink (DL) and/or Uplink frames (UL) using a MIMO scheme.
  • EDMG STA may be configured to implement one or more channel bonding mechanisms, which may, for example, support communication over a channel bandwidth (BW) (also referred to as a “wide channel”, an “EDMG channel”, or a “bonded channel”) including two or more channels, e.g., two or more 2.16 GHz channels.
  • BW channel bandwidth
  • the channel bonding mechanisms may include, for example, a mechanism and/or an operation whereby two or more channels, e.g., 2.16 GHz channels, can be combined, e.g., for a higher bandwidth of packet transmission, for example, to enable achieving higher data rates, e.g., when compared to transmissions over a single channel.
  • channels e.g., 2.16 GHz channels
  • Some demonstrative aspects are described herein with respect to communication over a channel BW including two or more 2. 16 GHz channels, however other aspects may be implemented with respect to communications over a channel bandwidth, e.g., a “wide” channel, including or formed by any other number of two or more channels, for example, an aggregated channel including an aggregation of two or more channels.
  • the EDMG STA may be configured to implement one or more channel bonding mechanisms, which may, for example, support an increased channel bandwidth, for example, a channel BW of 4.32 GHz, a channel BW of 6.48 GHz, a channel BW of 8.64 GHz, and/or any other additional or alternative channel BW.
  • the EDMG STA may perform other additional or alternative functionality.
  • the mmWave STA may include any other type of STA and/or may perform other additional or alternative functionality.
  • Other aspects may be implemented by any other apparatus, device and/or station.
  • 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.
  • 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 or 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 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 on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-
  • 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.
  • 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 monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.
  • LED Light Emitting Diode
  • LCD Liquid Crystal Display
  • memory unit 194 and/or memory unit 184 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units.
  • Storage unit 195 and/or storage unit 185 may include, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units.
  • 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, an RF channel, a WiFi channel, a cellular channel, a 5G channel, an IR channel, a Bluetooth (BT) channel, a Global Navigation Satellite System (GNSS) Channel, and the like.
  • WM 103 may include one or more wireless communication frequency bands and/or channels.
  • WM 103 may include one or more channels in a sub-lOGhz wireless communication frequency band, for example, one or more channels in a 2.4GHz wireless communication frequency band, one or more channels in a 5GHz wireless communication frequency band, and/or one or more channels in a 6GHz wireless communication frequency band.
  • WM 103 may additionally or alternatively include one or more channels in a mmWave wireless communication frequency band.
  • WM 103 may include any other type of channel over any other frequency band.
  • 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 implement transmit and receive functionalities using separate transmit and receive antenna elements.
  • antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • device 102 may include 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.
  • at least part of the functionality of controller 124 may be implemented as part of one or more elements of radio 114, and/or at least part of the functionality of controller 154 may be implemented as part of one or more elements of radio 144.
  • 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 more 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, an MPDU; at least one second component configured to convert the message into a PPDU, for example, by processing the message generated by the at least one first component, e.g., by encoding the message, modulating the message and/or performing any other additional or alternative processing of the message; and/or at least one third component configured to cause transmission of the message over a wireless communication medium, e.g., over a wireless communication channel in a wireless communication frequency band, for example, by applying to one or more fields of the PPDU one or more transmit waveforms.
  • 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.
  • 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. [0071] In some demonstrative aspects, at least part of the functionality of message processor 128 may be implemented as part of controller 124, and/or at least part of the functionality of message processor 158 may be implemented as part of controller 154.
  • 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 one or more radios 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 one or more radios 114.
  • controller 124, message processor 128, and one or more radios 114 may be implemented as part of the chip or SoC.
  • controller 124, message processor 128 and/or the one or more radios 114 may be implemented by one or more additional or alternative elements of device 102.
  • controller 154 and/or message processor 158 may be implemented by an integrated circuit, for example, a chip, e.g., a SoC.
  • the chip or SoC may be configured to perform one or more functionalities of one or more radios 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 one or more radios 144.
  • controller 154, message processor 158, and one or more radios 144 may be implemented as part of the chip or SoC.
  • controller 154, message processor 158 and/or one or more radios 144 may be implemented by one or more additional or alternative elements of device 140.
  • 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 Extremely High Throughput (EHT) STAs.
  • EHT Extremely High Throughput
  • 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 mmWave STAs, e.g., DMG STAs, EDMG STAs, and/or any other mmWave STA.
  • device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more mmWave STAs
  • device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, one or more mmWave STAs.
  • 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 one station (STA) and provides access to the distribution services, via the wireless medium (WM) for associated STAs.
  • STA station
  • WM wireless medium
  • An AP may include a STA and a distribution system access function (DSAF). The AP may perform any other additional or alternative functionality.
  • DSAF distribution system access function
  • devices 102 and/or 140 may be configured to communicate in an EHT network, and/or any other network.
  • 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, an IEEE 802.1 lay 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, an IEEE 802.1 lay Specification and/or any other specification and/or protocol.
  • device 102 and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, one or more multilink logical entities, e.g., as described below.
  • device 102 and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, any other entities, e.g., which are not multi-link logical entities.
  • a multi-link logical entity may include a logical entity that contains one or more STAs.
  • the logical entity may have one MAC data service interface and primitives to the logical link control (LLC) and a single address associated with the interface, which can be used to communicate on a distribution system medium (DSM).
  • DSM may include a medium or set of media used by a distribution system (DS) for communications between APs, mesh gates, and the portal of an extended service set (ESS).
  • the DS may include a system used to interconnect a set of basic service sets (BSSs) and integrated local area networks (LANs) to create an extended service set (ESS).
  • BSSs basic service sets
  • LANs local area networks
  • ESS extended service set
  • a multi-link logical entity may allow STAs within the multi-link logical entity to have the same MAC address.
  • the multi-link entity may perform any other additional or alternative functionality.
  • device 102 and/or device 140 may include, operate as, perform a role of, and/or perform the functionality of, a Multi-Link Device (MLD).
  • MLD Multi-Link Device
  • device 102 may include, operate as, perform a role of, and/or perform the functionality of, at least one MLD
  • device 140 may include, operate as, perform a role of, and/or perform the functionality of, at least one MLD, e.g., as described below.
  • an MLD may include a device that is a logical entity and has more than one affiliated STA and has a single MAC service access point (SAP) to LLC, which includes one MAC data service.
  • the MLD may perform any other additional or alternative functionality.
  • device 102 and/or device 140 may be configured to operate as, perform the role of, and/or perform one or more functionalities of, an AP MLD.
  • 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 MLD.
  • 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.
  • an AP MLD may include an MLD, where each STA affiliated with the MLD is an AP.
  • the AP MLD may include a multi-link logical entity, where each STA within the multi-link logical entity is an EHT AP.
  • the AP MLD may perform any other additional or alternative functionality.
  • a non-AP MLD may include an MLD, where each STA affiliated with the MLD is a non-AP STA.
  • the non-AP MLD may include a multi-link logical entity, where each STA within the multi-link logical entity is a non- AP EHT STA.
  • the non-AP MLD may perform any other additional or alternative functionality.
  • a multi-link infrastructure framework may be configured as an extension from a one link operation between two STAs, e.g., an AP and a non-AP STA.
  • controller 124 may be configured to control, perform and/or to trigger, cause, instruct and/or control device 102 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP MLD 131 including a plurality of STAs 133, e.g., including an AP STA 135, an AP STA 137, an AP STA 139, and/or an mmWave STA 141.
  • AP MLD 131 may include four STAs. In other aspects, AP MLD 131 may include any other number of STAs.
  • AP STA 135, AP STA 137, AP STA 139, and/or mmWave STA 141 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an EHT AP STA.
  • AP STA 135, AP STA 137, AP STA 139, and/or mmWave STA 141 may perform any other additional or alternative functionality.
  • mmWave STA 141 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a mmWave AP STA. In other aspects, mmWave STA 141 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of an mmWave network controller to control communication over an mmWave wireless communication network.
  • the one or more radios 114 may include, for example, a radio for communication by AP STA 135 over a first wireless communication frequency channel and/or frequency band, e.g., a 2.4Ghz band, as described below.
  • the one or more radios 114 may include, for example, a radio for communication by AP STA 137 over a second wireless communication frequency channel and/or frequency band, e.g., a 5Ghz band, as described below.
  • the one or more radios 114 may include, for example, a radio for communication by AP STA 139 over a third wireless communication frequency channel and/or frequency band, e.g., a 6Ghz band, as described below.
  • the one or more radios 114 may include, for example, a radio for communication by mmWave STA 141 over a fourth wireless communication frequency channel and/or frequency band, e.g., an mmWave band, for example, a wireless communication band above 45Ghz, for example, a 60GHz band or any other mmWave band, e.g., as described below.
  • a fourth wireless communication frequency channel and/or frequency band e.g., an mmWave band, for example, a wireless communication band above 45Ghz, for example, a 60GHz band or any other mmWave band, e.g., as described below.
  • the radios 114 utilized by STAs 133 may be implemented as separate radios. In other aspects, the radios 114 utilized by STAs 133 may be implemented by one or more shared and/or common radios and/or radio components.
  • controller 124 may be configured to control, perform and/or to trigger, cause, instruct and/or control device 102 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, any other additional or alternative entity and/or STA, e.g., a single STA, multiple STAs, and/or a non-MLD entity.
  • controller 154 may be configured to control, perform and/or to trigger, cause, instruct and/or control device 140 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an MLD 151 including a plurality of STAs 153, e.g., including a STA 155, a STA 157, a STA 159, and/or a STA 161.
  • MLD 151 may include four STAs. In other aspects, MLD 151 may include any other number of STAs.
  • STA 155, STA 157, STA 159, and/or STA 161 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an EHT STA. In other aspects, STA 155, STA 157, STA 159, and/or STA 161 may perform any other additional or alternative functionality.
  • STA 161 may be configured to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an mmWave STA, e.g., as described below.
  • the mmWave STA 161 may be configured to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a non-AP mmWave STA, e.g., as described below.
  • the one or more radios 144 may include, for example, a radio for communication by STA 155 over a first wireless communication frequency channel and/or frequency band, e.g., a 2.4Ghz band, as described below.
  • the one or more radios 144 may include, for example, a radio for communication by STA 157 over a second wireless communication frequency channel and/or frequency band, e.g., a 5Ghz band, as described below.
  • the one or more radios 144 may include, for example, a radio for communication by STA 159 over a third wireless communication frequency channel and/or frequency band, e.g., a 6Ghz band, as described below.
  • the one or more radios 144 may include, for example, a radio for communication by mmWave STA 161 over a fourth wireless communication frequency channel and/or frequency band, e.g., a mmWave band, as described below.
  • the radios 144 utilized by STAs 153 may be implemented as separate radios. In other aspects, the radios 144 utilized by STAs 153 may be implemented by one or more shared and/or common radios and/or radio components.
  • controller 154 may be configured to control, perform and/or to trigger, cause, instruct and/or control MLD 151 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a non-AP MLD.
  • STA 155, STA 157, STA 159, and/or mmWave STA 161 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, a non-AP STA, e.g., a non-AP EHT STA.
  • controller 154 may be configured to control, perform and/or to trigger, cause, instruct and/or control MLD 151 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP MLD.
  • STA 155, STA 157, STA 159, and/or mmWave STA 161 may operate as, perform a role of, and/or perform one or more operations and/or functionalities of, an AP EHT STA.
  • controller 154 may be configured to control, perform and/or to trigger, cause, instruct and/or control device 140 to operate as, perform a role of, and/or perform one or more operations and/or functionalities of, any other additional or alternative entity and/or STA, e.g., a single STA, multiple STAs, and/or a non-MLD entity.
  • Fig. 2 schematically illustrates a multi-link communication scheme 200, which may be implemented in accordance with some demonstrative aspects.
  • a first multi-link logical entity 202 (“multi-link logical entity 1”), e.g., a first MLD, may include a plurality of STAs, e.g., including a STA 212, a STA 214, a STA 216, and a STA 218.
  • AP MLD 131 (Fig. 1) may perform one or more operations of, one or more functionalities of, the role of, and/or the functionality of, multi-link logical entity 202.
  • a second multi-link logical entity 240 (“multi-link logical entity 2”), e.g., a second MLD, may include a plurality of STAs, e.g., including a STA 252, a STA 254, a STA 256, and a STA 258.
  • MLD 151 (Fig. 1) may perform one or more operations of, one or more functionalities of, the role of, and/or the functionality of, multi-link logical entity 240.
  • multi-link logical entity 202 and multi-link logical entity 240 may be configured to form, setup and/or communicate over a plurality of links, for example, including a link 272 between STA 212 and STA 252, a link 274 between STA 214 and STA 254, a link 276 between STA 216 and STA 256, and/or a link 278 between STA 218 and STA 258.
  • FIG. 3 schematically illustrates a multi-link communication scheme 300, which may be implemented in accordance with some demonstrative aspects.
  • a multi-link AP logical entity 302 may include a plurality of AP STAs, e.g., including an AP STA 312, an AP STA 314, an AP STA 316, and an mmWave STA 318.
  • AP MLD 131 (Fig. 1) may perform one or more operations of, one or more functionalities of, the role of, and/or the functionality of, multi-link AP logical entity 302.
  • a multi-link non-AP logical entity 340 may include a plurality of non-AP STAs, e.g., including a non-AP STA 352, a non-AP STA 354, a non-AP STA 356, and an mmWave STA 358.
  • MLD 151 (Fig. 1) may perform one or more operations of, one or more functionalities of, the role of, and/or the functionality of, multi-link non-AP logical entity 340.
  • multi-link AP logical entity 302 and multi-link non-AP logical entity 340 may be configured to form, setup and/or communicate over a plurality of links, for example, including a link 372 between AP STA 312 and non-AP STA 352, a link 374 between AP STA 314 and non-AP STA 354, a link 376 between AP STA 316 and non-AP S T A 356 , and/or a link 378 between mmW ave STA 318 and mmW ave STA 358.
  • multi-link AP logical entity 302 may include a multi-band AP MLD, which may be configured to communicate over a plurality of wireless communication frequency bands.
  • AP STA 312 may be configured to communicate over a 2.4Ghz frequency band
  • AP STA 314 may be configured to communicate over a 5Ghz frequency band
  • AP STA 316 may be configured to communicate over a 6Ghz frequency band
  • mmWave STA 318 may be configured to communicate over a mmWave frequency band.
  • AP STA 312, AP STA 314, AP STA 316, and/or mmWave STA 318 may be configured to communicate over any other additional or alternative wireless communication frequency bands.
  • device 102 and/or device 140 may be configured to support a technical solution for communication between mmWave STAs, e.g., mmWave STA 141 and mmWave STA 161, over the mmWave frequency band, e.g., as described below.
  • device 102 and/or device 140 may be configured to support a technical solution to utilize communications over the sub- 10GHz frequency band, for example, to assist one or more operations to be performed by the mmWave STAs, e.g., mmWave STA 141 and/or mmWave STA 161, over the mmWave frequency band, e.g., as described below.
  • the mmWave STAs e.g., mmWave STA 141 and/or mmWave STA 161
  • the mmWave frequency band e.g., as described below.
  • device 102 and/or device 140 may be configured to support a technical solution to utilize communications over the sub- 10GHz frequency band, for example, to assist a beamforming training procedure to be performed by the mmWave STAs, e.g., mmWave STA 141 and/or mmWave STA 161, over the mmWave frequency band, e.g., as described below.
  • mmWave STAs e.g., mmWave STA 141 and/or mmWave STA 161
  • the mmWave frequency band e.g., as described below.
  • device 102 and/or device 140 may be configured to provide a technical solution to support mmWave operation, e.g., operation at the 60GHz band, together with, and/or as part of, a sub-lOGhz functionality, for example, of a mainstream Wi-Fi protocol, e.g., as described below.
  • mmWave operation e.g., operation at the 60GHz band
  • sub-lOGhz functionality for example, of a mainstream Wi-Fi protocol, e.g., as described below.
  • device 102 and/or device 140 may be configured to support a technical solution, which may be based on and/or may utilize cost reduction of a wireless communication architecture, which may allow to reuse at least some components of, e.g., as much as possible of, the same baseband, for communications by both a sub- 10 GHz radio, e.g., a regular Wi-Fi radio, and a mmWave radio, e.g., a 60GHz radio.
  • a sub- 10 GHz radio e.g., a regular Wi-Fi radio
  • a mmWave radio e.g., a 60GHz radio.
  • device 102 and/or device 140 may be configured to support a technical solution, which may be based on and/or may utilize an enhanced throughput supported by mmWave techniques, e.g., compared to a sub- 10GHz band (lower band), which may have less potential for throughput enhancement.
  • mmWave techniques e.g., compared to a sub- 10GHz band (lower band), which may have less potential for throughput enhancement.
  • device 102 and/or device 140 may be configured to support a technical solution, which may be based on, and/or may utilize, a multi-link framework, for example, according to an MLD architecture, e.g., as described above.
  • a technical solution which may be based on, and/or may utilize, a multi-link framework, for example, according to an MLD architecture, e.g., as described above.
  • device 102 and/or device 140 may be configured to utilize the multi-link framework, for example, to improve operation on multiple links.
  • the multi-link framework may be utilized to allow compensating for a fragility of an mmWave link, e.g., a 60GHz link, for example, through a fallback to the sub-lOGHz band (lower band) operation.
  • device 102 and/or device 140 may be configured to support a technical solution to utilize a beamforming (BF) training procedure, e.g., a Basic Beamforming Training (BBT) procedure, which may allow two or more STAs to train their analog smart antenna, for example, to determine the best sector to use to point in the direction of each other, for example, on transmit and/or receive directions, e.g., as described below.
  • BF beamforming
  • BBT Basic Beamforming Training
  • the basic beamforming training procedure may include a sector sweep by an initiator device to transmit training symbols and/or a training frame multiple times, for example, using different sectors, e.g., as described below.
  • a receiver device may perform a receive sector sweep procedure, for example, during the sector sweep of the initiator device, e.g., as described below.
  • the receiver device may operate at an omni-receive mode to receive training frames from the initiator device.
  • the receiver device may measure one or more values, e.g., a Received Signal Strength Indicator (RSSI), based on training frames that the receive device is capable of receiving from the initiator device.
  • RSSI Received Signal Strength Indicator
  • device 102 and/or device 140 may be configured to support a technical solution to perform beamforming training, e.g., the basic beamforming training procedure, over an mmWave wireless communication channel assisted by communications over a sub-lOGHz wireless communication channel, e.g., as described below.
  • beamforming training e.g., the basic beamforming training procedure
  • mmWave wireless communication channel assisted by communications over a sub-lOGHz wireless communication channel, e.g., as described below.
  • device 102 and/or device 140 may be configured to perform one or more operations of a procedure (also referred to as “sub- lOGhz assisted procedure”), which may make use of an existing sub-lOGhz link, e.g., a sub-7 GHz link, between two STAs that intend to establish an mmWave link, e.g., a 60 GHz link, to exchange discovery and/or beamforming training-related information, e.g., as described below.
  • a procedure also referred to as “sub- lOGhz assisted procedure”
  • an existing sub-lOGhz link e.g., a sub-7 GHz link
  • mmWave link e.g., a 60 GHz link
  • the sub-lOGhz assisted procedure may be configured for implementation by a first STA, e.g., a STA implemented by device 102, and a second STA, e.g., a STA implemented by device 140, to perform discovery and/or initial beamforming training in the mmWave band, e.g., the 60 GHz band, for example, by exchanging related information on an existing sub-lOGhz link, e.g., a sub-7 GHz link, as described below.
  • a first STA e.g., a STA implemented by device 102
  • a second STA e.g., a STA implemented by device 140
  • the sub-lOGhz assisted procedure may be configured for implementation by two STAs that have a sub-7 GHz link established to perform 60 GHz discovery and/or initial beamforming, e.g., as described below.
  • the sub-lOGhz assisted procedure may include a first phase (phase 1), which may be configured to support the 60 GHz discovery and initial beamforming process.
  • the first phase may be initiated with the exchange of BF-assistance information on an existing sub-7 GHz link.
  • the BF-assistance information may include system parameters, e.g., a number of sectors, and/or target start time, which may assist in configuring the BF over the mmWave band.
  • the sub-lOGhz assisted procedure may include a second phase (phase 2), which may be configured to support discovery and/or initial beamforming training over the mmWave band.
  • the second phase may include a transmit sector-sweep by an AP, e.g., using different sectors, and possibly other beamforming training procedures.
  • the sector-sweep by the AP may include transmission of training (TRN) signals in a MAC frame and/or a Null Data Packet (NDP).
  • TRN training
  • NDP Null Data Packet
  • the AP may provide to a STA information, e.g., a sector identifier (ID) and/or basic service set identifier (BSSID), in PHY and/or MAC.
  • STA information e.g., a sector identifier (ID) and/or basic service set identifier (BSSID)
  • ID sector identifier
  • BSSID basic service set identifier
  • the TRN signals may be configured in accordance with an IEEE 802.1 lad/ay Specification.
  • the TRN signal may have any other additional or alternative configuration.
  • the TRN signals may be configured to include Long Training Field (LTF)Ztraining sequences, which may be transmitted a plurality of times, e.g., X times.
  • LTF Long Training Field
  • a receiver STA may lock reception in an omni-directional receive mode, for example, based on a first part of a PPDU from the AP, and may use a different Rx sector, e.g., for each LTF/training sequence, for example, to perform Rx training.
  • the sub-lOGhz assisted procedure may include a third phase (phase 3), which may be configured to support feedback of the discovery and initial beamforming process, for example, over the existing sub-7 GHz link.
  • phase 3 may be configured to support feedback of the discovery and initial beamforming process, for example, over the existing sub-7 GHz link.
  • the STA may be configured to send to the AP a feedback frame including feedback information, for example, based on measurements performed by the STA on the TRN signals received by the STA.
  • the feedback information may include an indication of one or more sectors, e.g., a best sector, which may be identified based on the measurements.
  • the feedback information may include some or all of the measurement information corresponding to the one or more sectors, e.g., an RSSI corresponding to the best sector, and/or any other additional or alternative information.
  • device 102 and/or device 140 may be configured to generate, transmit, and/or process one or more packets including one or more TRN fields according to a training field format, e.g., as described below.
  • device 102 and/or device 140 may be configured to generate, transmit, and/or process one or more packets including one or more TRN fields according to the training field format, for example, as part of a BF training, for example, an initial BF training procedure.
  • device 102 and/or device 140 may be configured to generate, transmit, and/or process one or more packets including one or more TRN fields according to the training field format, for example, as part of a beamtracking procedure and/or a beam-refinement procedure, for example, after the initial BF training procedure.
  • a beam-tracking procedure and/or a beam-refinement procedure may be performed, for example, after an initial beamforming phase to determine a best beam, for example, in order to track evolution of the best beam and/or to refine one or more beams.
  • the initial beamforming procedure may be sufficient to provide a way for 2 peers to point to each other and transmit/receive PPDUs, e.g., with a decent reliability and/or SNR.
  • device 102 and/or device 140 may be configured to generate, transmit, and/or process one or more packets including one or more TRN fields according to a training field format, which may be configured to provide a technical solution to support an improved, efficient, and/or optimized beamforming training sequence, e.g., as described below.
  • controller 124 may be configured to cause a mmWave STA implemented by device 102, e .g, mmWave STA 141, to transmit a preamble of a packet over a mmWave wireless communication channel, , e.g., as described below.
  • the mmWave channel may include a 60GHz channel. In other aspects, the mmWave channel may include any other mmWave channel.
  • the preamble may be configured to include a Short Training Field (STF), a Long Training Field (LTF) after the STF, and a Signal (SIG) field after the LTF, e.g., as described below.
  • STF Short Training Field
  • LTF Long Training Field
  • SIG Signal
  • the SIG field may include a presence indicator configured to indicate that the packet includes a TRN field configured for BF training, e.g., as described below.
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to transmit the TRN field of the packet over the mmWave wireless communication channel, e.g., as described below.
  • the TRN field may be after the SIG field, e.g., as described below.
  • the TRN field may include a plurality of TRN subfields, e.g., as described below.
  • a TRN subfield of the plurality of TRN subfields may include at least one of the STF or the LTF, for example, the same STF and/or the same LTF of the preamble, e.g., as described below.
  • the TRN subfield may include the STF, for example, the same STF of the preamble, e.g., as described below.
  • the TRN subfield may include the LTF, for example, the same LTF of the preamble,, e.g., as described below.
  • the TRN subfield may include the LTF after the STF, e.g., as described below.
  • the TRN subfield may include a plurality of repetitions of the LTF, e.g., as described below.
  • the TRN subfield may include any other additional or alternative fields and/or combination of fields.
  • controller 154 may be configured to cause a first mmWave STA, for example, an mmWave STA implemented by device 140, e.g., mmWave STA 153, to process a preamble of a packet received from a second mmWave STA over a mmWave wireless communication channel, e.g., as described below.
  • the preamble of the received packet may include an STF, an LTF after the STF, and a SIG field after the LTF, e.g., as described below.
  • the SIG field may include a presence indicator configured to indicate than the packet includes a TRN field configured for BF training after the SIG field, e.g., as described below.
  • controller 154 may be configured to cause the mmWave STA implemented by device 140 to perform measurements on one or more received TRN subfields of the TRN field of the received packet, e.g., as described below.
  • a TRN subfield of the TRN field of the received packet may include at least one of the STF or the LTF, for example, the same STF and/or the same LTF of the preamble, e.g., as described below.
  • the mmWave STA implemented by device 140 may process the preamble of the packet received from the mmWave STA implemented by device 102 over the mmWave wireless communication channel.
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to transmit the preamble, for example, according to a first Transmit (Tx) antenna setting of the mmWave STA implemented by device 102, e.g., as described below.
  • Tx first Transmit
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to transmit the plurality of TRN subfields, for example, according to one or more second Tx antenna settings of the mmWave STA implemented by device 102, e.g., as described below.
  • the one or more second Tx antenna settings may be different from the first Tx antenna setting, e.g., as described below.
  • the first Tx antenna setting may include an omni-directional setting, e.g., as described below.
  • the first Tx antenna setting may include a BF Tx setting according to a previous BF training, e.g., as described below. [00183] In other aspects, the first Tx antenna setting may include any other antenna setting.
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to transmit the plurality of TRN subfields, for example, according to a sector sweep via a plurality of Tx antenna sectors of the mmWave STA implemented by device 102, e.g., as described below.
  • controller 154 may be configured to cause the mmWave STA implemented by device 140 to receive one or more received TRN subfields, for example, according to a sector sweep via a plurality of Receive (Rx) antenna sectors of the mmWave STA implemented by device 140, e.g., as described below.
  • Rx Receive
  • the packet communicated between the first mmWave STA, e.g., the mmWave STA implemented by device 102, and the second mmWave STA, e.g., the mmWave STA implemented by device 140, may include an NDP , e.g., as described below.
  • the packet communicated between the first mmWave STA, e.g., the mmWave STA implemented by device 102, and the second mmWave STA, e.g., the mmWave STA implemented by device 140, may include a PPDU, e.g., as described below.
  • the PPDU may include a data field after the SIG field, and the TRN filed may be after the data field, e.g., as described below.
  • the packet communicated between the first mmWave STA, e.g., the mmWave STA implemented by device 102, and the second mmWave STA, e.g., the mmWave STA implemented by device 140 may include any other type of packet.
  • the SIG field in the packet communicated between the first mmWave STA, e.g., the mmWave STA implemented by device 102, and the second mmWave STA, e.g., the mmWave STA implemented by device 140 may include a TRN type indicator configured to indicate a type of the TRN field, e.g., as described below.
  • the TRN type indicator may be configured to indicate the type of the TRN field from a plurality of predefined TRN field types, e.g., as described below.
  • the plurality of predefined TRN field types may include a Transmit (Tx) TRN field type to indicate that the plurality of TRN subfields includes Tx TRN subfields for Tx BF training, e.g., as described below.
  • Tx Transmit
  • the plurality of predefined TRN field types may include a Receive (Rx) TRN field type configured to indicate that the plurality of TRN subfields includes Rx TRN subfields for Rx BF training, e.g., as described below.
  • Rx Receive
  • the plurality of predefined TRN field types may include a Tx/Rx TRN field type to indicate that the plurality of TRN subfields includes one or more Tx TRN subfields and one or more Rx TRN subfields, e.g., as described below.
  • the SIG field may include an Rx/Tx field to indicate a count of Rx TRN subfields in a group of Rx TRN subfields corresponding to a Tx TRN subfield, e.g., as described below.
  • the TRN type indicator may include a TRN type field including a type value from a plurality of predefined type values, e.g., as described below.
  • the plurality of predefined type values may include a first value to indicate a Tx TRN field type, a second value to indicate an Rx TRN field type, and/or a third value to indicate a Tx/Rx TRN field type, e.g., as described below.
  • the SIG field may include a TRN subfield count field to indicate a count of the plurality of TRN subfields in the TRN field, e.g., as described below.
  • the SIG field may include a length field, which may be configured to indicate a length of the TRN subfields, e.g., as described below.
  • the SIG field may include an LTF count field, which may be configured to indicate a count of LTFs per TRN subfield, e.g., as described below.
  • the SIG field may include a Tx/Rx configuration field, which may be configured to indicate a configuration of Tx TRN subfields and Rx TRN subfields in the TRN field, e.g., as described below.
  • the SIG field may include any other additional or alternative field corresponding to a configuration of the TRN field and/or contents of the TRN field.
  • a mmWave STA e.g., an initiator device initiating a packet transmission
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to set the packet including the TRN field to include a feedback indication, e.g., as described below.
  • the feedback indication may be configured to indicate a request that an other mmWave STA participating in the BF training is to transmit to the mmWave STA implemented by device 102 feedback, for example, based on the TRN field, e.g., as described below.
  • the mmWave STA implemented by device 102 may participate in BF training with the mmWave STA implemented by device 140.
  • the mmWave STA implemented by device 102 may transmit to the mmWave STA implemented by device 140 the packet including the TRN field and the feedback indication to indicate the request that mmWave STA implemented by device 140 is to transmit feedback to the mmWave STA implemented by device 102.
  • the feedback indication may include feedback configuration information to configure which information is to be included in the feedback, e.g., as described below.
  • the SIG field of the packet may include the feedback indication, e.g., as described below.
  • the feedback indication may be included in a data field of the packet.
  • the packet including the TRN field may include a data field, e.g., after the SIG field, and the feedback indication may be included in a data field.
  • any other additional or alternative field of the packet may be configured to include the feedback indication.
  • controller 154 may be configured to cause the mmWave STA implemented by device 140 to process the packet received from the mmWave STA implemented by device 102, for example, to identify the feedback indication indicating the request that the mmWave STA implemented by device 140 is to transmit feedback based on the measurements on the one or more received TRN subfields of the packet, e.g., as described below.
  • controller 154 may be configured to cause the first mmWave STA implemented by device 140 to, based on the feedback indication in the packet, transmit a packet including the feedback to the mmWave STA implemented by device 102, for example, based on the measurements on the one or more received TRN subfields, e.g., as described below.
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to set the packet to include a reversedirection TRN request indication, e.g., as described below.
  • the reverse-direction TRN request indication may be configured to indicate a request that another mmWave STA participating in the BF training is to transmit another packet including a reverse-direction TRN field from the other mmWave STA, e.g., as described below.
  • controller 124 may be configured to cause the mmWave STA implemented by device 102 to set the packet to include a reverse-direction TRN request indication to indicate a request that the mmWave STA implemented by device 140 is to transmit another packet including a reverse-direction TRN field from device 140.
  • the SIG field of the packet may include the reverse-direction TRN request indication, e.g., as described below.
  • the reverse-direction TRN request indication may be included in a data field of the packet.
  • the packet including the TRN field may include a data field, e.g., after the SIG field, and the reverse-direction TRN request indication may be included in a data field.
  • any other additional or alternative field of the packet may be configured to include the reverse-direction TRN request indication.
  • controller 154 may be configured to cause the mmWave STA implemented by device 140 to identify that a received packet from another mmWave STA includes a reverse-direction TRN field.
  • controller 154 may be configured to cause the mmWave STA implemented by device 140 to, based on the reverse-direction TRN request indication in the received packet, transmit another packet including a reversedirection TRN field to the other mmWave STA, e.g., as described below.
  • the mmWave STA implemented by device 140 may be configured to, based on the reverse-direction TRN request indication in the packet from the mmWave STA implemented by device 102, transmit another packet including a reverse-direction TRN field to the mmWave STA implemented by device 102.
  • device 102 and/or device 140 may be configured to communicate a packet including a TRN field according to a training field format, e.g., as described below.
  • the TRN field may be appended at an end of a packet, for example, any PPDU, e.g., as described below.
  • the TRN field may be appended to a PPDU including one or more MAC Service Data Units (MSDUs), one or more Block Acknowledgements (BAs), and/or any other additional or alternative types of PPDUs.
  • MSDUs MAC Service Data Units
  • BAs Block Acknowledgements
  • the TRN field may include a plurality of TRN subfields, e.g., as described below.
  • the TRN field may be configured according to a TRN field format including a plurality of identical TRN subfields. For example, some or all of the TRN subfields in the TRN field may be identical.
  • the plurality of identical TRN subfields may be configured to provide a technical solution to support a receiver device to perform an RSSI measurement on the TRN field, for example, for a particular configuration of a Tx sector, e.g., of a transmitted of the TRN field, and an Rx sector, e.g., of the receiver device.
  • a TRN field may be configured according to a TRN field format including a plurality of different TRN subfields. For example, some or all of the TRN subfields in the TRN field may different from one another. In one example, the TRN field may be configured according to a TRN field format including two or more different TRN subfields, which may alternate or repeat according to some scheme.
  • device 102 and/or device 140 may be configured to communicate one or more types of TRN fields, for example, from a plurality of different types of TRN fields, e.g., as described below.
  • a TRN field may be configured to include Tx TRN subfields, for example, where a transmit sector may change from one Tx TRN subfield to another.
  • a TRN field may be configured to include Rx TRN subfields, for example, where a transmit sector may not change, while a receiver sector may change from one Rx TRN subfield to another.
  • device 102 and/or device 140 may be configured to communicate and/or process TRN fields of one or more of the following TRN field types:
  • TRN field including only Tx TRN subfields.
  • TRN field including only Rx TRN subfields.
  • a TRN field including Tx TRN and Rx TRN subfields may form a group corresponding to a Tx TRN subfield.
  • device 102 and/or device 140 may be configured to generate, transmit, and/or process a packet, e.g., a PPDU, including a TRN field, and a SIG field including one or more predefined parameters of TRN subfields in the TRN field, e.g., some of, or all of, the following parameters and/or fields:
  • a packet e.g., a PPDU, including a TRN field, and a SIG field including one or more predefined parameters of TRN subfields in the TRN field, e.g., some of, or all of, the following parameters and/or fields:
  • a field indicating one or more ways to calculate a length of a PPDU, for example, before the TRN fields.
  • TRN type indicating a type of the TRN field.
  • the TRN type field may indicate whether the TRN field includes Tx TRN subfields, Rx TRN subfields, or a combination of Tx TRN subfields and Rx TRN subfields.
  • a field indicating a count of Rx TRN subfields in a group of Rx TRN subfields corresponding to a Tx TRN subfield for example, in case the TRN field includes a combination of Tx TRN subfields and Rx TRN subfields.
  • a field indicating a count of LTFs per TRN subfield for example, in case of a MIMO TRN.
  • the SIG field may include a parameter, e.g., a flag, configured to denote a multiple TRN subfields mode.
  • a parameter e.g., a flag
  • one or more parameter fields described above e.g., such as a count of TRN fields and/or a length field, may be overloaded with the parameters listed in this subelement.
  • device 102 and/or device 140 may be configured to communicate feedback from a receiver of the packet including the TRN field, e.g., as described below.
  • an initiator of a packet e.g., a PPDU, including a TRN field, e.g., a STA implemented by device 102, may be configured to include in the transmitted packet a feedback indication to signal that a receiver of the packet needs to respond with a feedback, e.g., beamforming feedbacks, for example, in the case of transmitter training.
  • the initiator may include the feedback indication in a PHY header of the packet including the TRN field.
  • the initiator may be configured to signal the feedback indication in the SIG fields of the packet.
  • the initiator may signal the feedback indication in a MAC layer, e.g., through a dedicated frame.
  • the initiator may signal the feedback indication via a new specific A-control frame.
  • the initiator may signal the feedback indication using any other additional or alternative field, frame and/or signaling mechanism.
  • a responder STA for example, a receiver of the packet including the TRN field, e.g., a STA implemented by device 140, may be configured to transmit a packet including the feedback to the initiator, for example, based on the feedback indication in the received packet.
  • the feedback may be configured to indicate a sector ID, e.g., a best sector ID, to identify a sector, e.g., a best sector, of the initiator, from which a TRN subfield is received by the responder.
  • a sector ID e.g., a best sector ID
  • the feedback may indicate the sector ID, for example using a numbering corresponding to the order of a Tx TRN subfield.
  • the receiver may be configured to determine the sector ID, e.g., the best sector ID, for example, based on an RSSI measurement, and/or any other additional or alternative metrics, for example, including rank of sectors, and/ or eigenvalue analysis.
  • the sector ID e.g., the best sector ID, for example, based on an RSSI measurement, and/or any other additional or alternative metrics, for example, including rank of sectors, and/ or eigenvalue analysis.
  • the receiver may be configured to include additional, e.g., more elaborate, information in the feedback.
  • the feedback may include an RSSI for every Tx sector ID, a full digital beamforming report for the best sector, e.g., in order to support digital beamforming jointly, and/or any other additional or alternative information.
  • device 102 and/or device 140 may be configured to communicate one or more packets with reverse-direction TRN fields, e.g., as described below.
  • an initiator of a packet may be configured to include in the packet a reverse-direction TRN request indication.
  • the reverse-direction TRN request indication may be configured to signal that a receiver of the packet needs to respond to the packet, e.g., the PPDU, with another packet, e.g., another PPDU, that contains a TRN field (“reverse-direction TRN field”), for example, in order to perform a beamforming training in a reverse direction.
  • the initiator may include the reverse-direction TRN request indication in a PHY header of the packet.
  • the initiator may be configured to signal the feedback indication in the SIG fields of the packet.
  • the initiator may signal the reverse-direction TRN request indication in a MAC layer, e.g., through a dedicated frame.
  • the initiator may signal the reverse-direction TRN request indication via a new specific A-control frame.
  • the initiator may signal the reverse-direction TRN request indication using any other additional or alternative field, frame and/or signaling mechanism.
  • the initiator may include in the packet one or more parameters, which may be configured to support performing the beamforming training, for example, in the packet.
  • one or more parameters, e.g., some or all parameters, for the beamforming training may be exchange and/or negotiated between the initiator and the responder ahead of time, for example, before the transmission of the packet.
  • one or more parameters, e.g., some or all parameters, for the beamforming training may be may be represented by a compressed signaling.
  • FIG. 4 schematically illustrates an NDP 400, in accordance with some demonstrative aspects.
  • a STA implemented by device 102 (Fig. 1) and/or a STA implemented by device 140 (Fig. 1) may be configured to generate, transmit, and/or process NDP 400.
  • a preamble 401 of the NDP 400 may include an STF 402, an LTF 404 after STF 402, and a SIG field 406 (also referred to as “Wi-Fi 8 SIG” or “W8-SIG”),e.g., after LTF 404.
  • the SIG field 406 may be after a non-High Throughput SIG (L-SIG) field 405.
  • SIG field 406 may include a presence indicator 407 configured to indicate that the NDP 400 includes a TRN field 408 configured for BF training.
  • TRN field 408 may be after SIG field 406.
  • TRN field 408 may include a plurality of TRN subfields 410.
  • a TRN subfield 412 of the plurality of TRN subfields 410 may include an STF 414.
  • the STF 414 may include, or may be identical to, STF 402.
  • TRN subfield 412 may include an LTF 416 after the STF 414.
  • the LTF 416 may include, or may be identical to, LTF 404.
  • FIG. 5 schematically illustrates an NDP 500, in accordance with some demonstrative aspects.
  • a STA implemented by device 102 (Fig. 1) and/or a STA implemented by device 140 (Fig. 1) may be configured to generate, transmit, and/or process NDP 500.
  • a preamble 501 of the NDP 500 may include an STF 502, an LTF 504 after STF 502, and a SIG field 506 after LTF 504.
  • the SIG field 506 may be after an L-SIG field 505.
  • SIG field 506 may include a presence indicator 507 configured to indicate that the NDP 500 includes a TRN field 508 configured for BF training.
  • TRN field 508 may be after SIG field 506.
  • TRN field 508 may include a plurality of TRN subfields 510.
  • the plurality of TRN subfields 510 may include one or more Tx TRN subfields 512, and/or one or more Rx TRN subfields 514.
  • the SIG field 506 may include a TRN type indicator 509 configured to indicate a type of the TRN field 508.
  • the TRN type indicator 509 may be configured to indicate the type of the TRN field 508 from a plurality of predefined TRN field types.
  • the TRN type indicator 509 may include a Tx/Rx TRN field type to indicate that the plurality of TRN subfields 510 includes the one or more Tx TRN subfields 512, and/or the one or more Rx TRN subfields 514.
  • FIG. 6 schematically illustrates a PPDU 600, in accordance with some demonstrative aspects.
  • a STA implemented by device 102 (Fig. 1) and/or a STA implemented by device 140 (Fig. 1) may be configured to generate, transmit, and/or process PPDU 600.
  • a preamble 601 of the PPDU 600 may include an STF 602, an UTF 604 after the STF 602, and a SIG field 606 after the LTF 604.
  • the SIG field 606 may be after an L-SIG field 605.
  • TRN field 610 may include a plurality of TRN subfields 612.
  • SIG field 606 may include signaling parameters 619 for configuring TRN field 610.
  • signaling parameters 619 may signal a type of the TRN field 610 and/or a configuration of the TRN subfields 612, e.g., as described above.
  • a TRN subfield 614 of the plurality of TRN subfields 612 may include an STF 616.
  • the STF 616 may include, or may be identical to, STF 602.
  • the TRN subfield 614 may include an LTF 618, for example, after the STF 616.
  • the LTF 618 may include, or may be identical to, LTF 604.
  • FIG. 7 schematically illustrates a packet exchange, in accordance with some demonstrative aspects.
  • an mmWave STA implemented by device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, an initiator STA 742.
  • an mmWave STA implemented by device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, a responder STA 740.
  • initiator STA 742 may be configured to generate and transmit a PPDU 750.
  • PPDU 750 may include an STF 702, an LTF 704 after the STF 702, and a SIG field after the LTF 704.
  • the SIG field 706 may be after an L-SIG field 705.
  • PPDU 750 may include a data field 708 after SIG field 706.
  • PPDU 750 may include a TRN field 710, e.g., appended at the end of PPDU 750, for example, after data field 708.
  • TRN field 710 may include a plurality of TRN subfields 712.
  • TRN field 710 may be configured to support Tx beamforming training of initiator STA 742.
  • TRN subfields 712 may include Tx TRN subfields.
  • SIG field 706 may include signaling parameters 719 for configuring TRN field 710.
  • signaling parameters 719 may signal a type of the TRN field 710 and/or a configuration of the TRN subfields 712, e.g., as described above.
  • signaling parameters 719 may include a Tx TRN field type to indicate that the plurality of TRN subfields 712 includes Tx TRN subfields for Tx BF training.
  • PPDU 750 may include a feedback indication 720 to indicate a request that responder STA 740 is to transmit to initiator 742 feedback, for example, based on the TRN field 710.
  • feedback indication 720 may include feedback configuration information to configure which information is to be included in the feedback, e.g., as described above.
  • SIG field 706 may include feedback indication 720.
  • data field 708 may include feedback indication 720.
  • responder STA 740 may be configured to receive and process PPDU 750 including feedback indication 720.
  • responder STA 740 may be configured to, based on identifying the feedback indication 720 in PPDU 750, transmit a packet 760 including feedback 714 to initiator STA 742.
  • feedback 714 may be based on measurements performed by responder STA 740 on one or more received TRN subfields of the plurality of TRN subfields 712.
  • feedback 714 may include an indication of a best Tx sector of the initiator STA 742, e.g., which may be identified by the responder STA 742, for example, based on the measurements performed on the received TRN subfields.
  • feedback 714 may include one or more RSSI values, e.g., corresponding to one or more Tx sectors of the initiator STA 742, e.g., which may be identified by the responder STA 742, for example, based on the measurements performed on the received TRN subfields.
  • the feedback 714 may include an RSSI corresponding to the best Tx sector.
  • the feedback 714 may include a plurality of RSSIs corresponding to a plurality of Tx sectors.
  • feedback 714 may include a complete compressed beamforming feedback, e.g., which may be identified by the responder STA 742, for example, based on the measurements performed on the received TRN subfields.
  • feedback 714 may include any other additional or alternative information.
  • FIG. 8 schematically illustrates a packet exchange, in accordance with some demonstrative aspects.
  • an mmWave STA implemented by device 102 may include, operate as, perform the role of, and/or perform one or more functionalities of, an initiator STA 842.
  • an mmWave STA implemented by device 140 may include, operate as, perform the role of, and/or perform one or more functionalities of, a responder STA 840.
  • initiator STA 842 and/or responder STA 840 may be configured to perform the packet exchange of Fig. 8, for example, in a way that may support refinement of a BF training, for example, in both Tx and Rx communication directions.
  • initiator STA 842 may be configured to generate and transmit a PPDU 850.
  • PPDU 850 may include an STF 802, an LTF 804 after the STF 802, and a SIG field after the LTF 804.
  • the SIG field 806 may be after an L-SIG field 805.
  • PPDU 850 may include a data field 808 after SIG field 806.
  • PPDU 850 may include a TRN field 810, e.g., appended at the end of PPDU 850, for example, after data field 808.
  • TRN field 810 may include a plurality of TRN subfields 812.
  • TRN field 810 may be configured to support Rx beamforming training of responder STA 840.
  • TRN subfields 812 may include Rx TRN subfields.
  • SIG field 806 may include signaling parameters 819 for configuring TRN field 810.
  • signaling parameters 819 may signal a type of the TRN field 810 and/or a configuration of the TRN subfields 812, e.g., as described above.
  • signaling parameters 819 may include an Rx TRN field type to indicate that the plurality of TRN subfields 812 includes Rx TRN subfields for Rx BF training.
  • PPDU 850 may include a reverse-direction TRN request indication 820.
  • reverse-direction TRN request indication 820 may be configured to indicate a request that responder STA 840 is to transmit a packet including a reverse-direction TRN field from responder STA 840.
  • SIG field 806 may include reversedirection TRN request indication 820.
  • data field 808 may include reversedirection TRN request indication 820.
  • reverse-direction TRN request indication 820 may be included in any other additional or alternative field of PPDU 850.
  • responder STA 840 may be configured to receive and process PPDU 850 including reverse-direction TRN request indication 820.
  • responder STA 840 may be configured to, based on identifying the reverse-direction TRN request indication 820 in the PPDU 850, transmit a packet 860 including a reverse-direction TRN field 816 to initiator STA 842.
  • packet 860 may include a BA field 814, for example, after a SIG field 813.
  • packet 860 may include reverse-direction TRN field 816, which may be configured for Rx BF training of initiator STA 842.
  • reverse-direction TRN field 816 may include a plurality of TRN subfields 818.
  • SIG field 813 may include an Rx TRN field type to indicate that the plurality of TRN subfields 818 includes Rx TRN subfields for Rx BF training.
  • FIG. 9 schematically illustrates an NDP 900, in accordance with some demonstrative aspects.
  • an mmWave STA implemented by device 102 (Fig. 1) and/or an mmWave STA implemented by device 140 (Fig. 1) may be configured to generate, transmit, and/or process NDP 900.
  • a preamble 901 of the NDP 900 may include an STF 902, an LTF 904 after STF 902, and a SIG field 906 after LTF 904.
  • the SIG field 606 may be after an L-SIG field 905.
  • SIG field 906 may include a presence indicator 907 configured to indicate that the NDP 900 includes a TRN field 908 configured for BF training.
  • TRN field 908 may be after SIG field 906.
  • TRN field 908 may include a plurality of TRN subfields 910.
  • a TRN subfield 912 of the plurality of TRN subfields 910 may include an STF 916.
  • the STF 916 may include, or may be identical to, STF 902.
  • TRN subfield 912 may include an LTF 918, e.g., after the STF 916.
  • the LTF 918 may include, or may be identical to, LTF 904.
  • a TRN subfield 914 of the plurality of TRN subfields 910 may include a plurality of repetitions of an LTF 920.
  • the LTF 920 may include, or may be identical to, LTF 918.
  • the LTF 920 may include, or may be identical to, LTF 904.
  • the plurality of repetitions of the LTF 920 may be configured to provide a technical solution to assist in performing MIMO BF training.
  • the plurality of repetitions of the LTF 920 may be transmitted from different antennas with a specific spreading code to differentiate the different antennas, e.g., utilizing tools for digital sounding in the 2.4/5/6GHz bands.
  • Fig. 10 schematically illustrates a method of communicating a packet including a TRN field, in accordance with some demonstrative aspects.
  • one or more of the operations of the method of Fig. 10 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1), and/or device 140 (Fig. 1), an MLD, e.g., MLD 131 (Fig. 1) and/or MLD 151 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).
  • a system e.g., system 100 (Fig. 1)
  • wireless devices e.g.,
  • the method may include transmitting from an mmWave STA a preamble of a packet over a mmWave wireless communication channel.
  • the preamble may include an STF, an LTF after the STF, and a SIG field after the LTF.
  • the SIG field may include a presence indicator configured to indicate that the packet includes a TRN field configured for BF training.
  • controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to transmit the preamble of the packet over the mmWave wireless communication channel, e.g., as described above.
  • the method may include transmitting the TRN field of the packet over the mmWave wireless communication channel.
  • the TRN field may be after the SIG field, and may include a plurality of TRN subfields.
  • a TRN subfield may include at least one of the STF or the LTF.
  • controller 124 (Fig. 1) may be configured to cause, trigger, and/or control device 102 (Fig. 1) to transmit the TRN field of the packet over the mmWave wireless communication channel, e.g., as described above.
  • Fig. 11 schematically illustrates a method of communicating a packet including a TRN field, in accordance with some demonstrative aspects.
  • a system e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1) and/or device 140 (Fig. 1), an MLD, e.g., MLD 131 (Fig. 1) and/or MLD 151 (Fig. 1), a controller, e.g., controller 124 (Fig. 1) and/or controller 154 (Fig. 1), a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1), and/or a message processor, e.g., message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).
  • a system e.g., system 100 (Fig. 1)
  • wireless devices e.g., device 102 (Fig. 1) and/or device 140 (Fig. 1)
  • MLD e.g.
  • the method may include processing at a first mmWave STA a preamble of a packet received from a second mmWave STA over a mmWave wireless communication channel.
  • the preamble may include an STF, an LTF after the STF, and a SIG field after the LTF.
  • the SIG field may include a presence indicator configured to indicate that the packet includes a TRN field configured for BF training after the SIG field.
  • controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to process the preamble of the packet received from device 102 (Fig. 1), e.g., as described above.
  • the method may include performing measurements on one or more received TRN subfields of the TRN field of the packet.
  • a TRN subfield may include the STF and/or the LTF.
  • controller 154 (Fig. 1) may be configured to cause, trigger, and/or control device 140 (Fig. 1) to perform measurements on one or more received TRN subfields of the TRN field of the packet, e.g., as described above.
  • Product 1200 may include one or more tangible computer-readable (“machine-readable”) non-transitory storage media 1202, which may include computer-executable instructions, e.g., implemented by logic 1204, operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at device 102 (Fig. 1), device 140 (Fig. 1), MLD 131 (Fig. 1), MLD 151 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), receiver 146 (Fig.
  • 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 1200 and/or machine -readable storage media 1202 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or nonremovable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like.
  • machine-readable storage media 1202 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide- silicon (SONOS) memory, a disk, a hard drive, and the like.
  • 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 content addressable memory
  • 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.
  • a communication link e.g., a modem, radio or network connection.
  • logic 1204 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 1204 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like.
  • the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • the instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function.
  • the instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, machine code, and the like.
  • Example 1 includes an apparatus comprising logic and circuitry configured to cause a millimeterWave (mmWave) wireless communication station (STA) to transmit a preamble of a packet over a mmWave wireless communication channel, the preamble comprising a Short Training Field (STF), a Long Training Field (LTF) after the STF, and a Signal (SIG) field after the LTF, and optionally, wherein the SIG field comprises a presence indicator configured to indicate that the packet comprises a Training (TRN) field configured for Beamforming (BF) training; and transmit the TRN field of the packet over the mmWave wireless communication channel, the TRN field is after the SIG field, the TRN field comprising a plurality of TRN subfields, and optionally, wherein a TRN subfield comprises at least one of the STF or the LTF.
  • mmWave millimeterWave
  • STA millimeterWave wireless communication station
  • Example 2 includes the subject matter of Example 1, and optionally, and optionally, wherein the SIG field comprises a TRN type indicator configured to indicate a type of the TRN field.
  • Example 3 includes the subject matter of Example 2, and optionally, and optionally, wherein the TRN type indicator is configured to indicate the type of the TRN field from a plurality of predefined TRN field types, and optionally, wherein the plurality of predefined TRN field types comprises a Transmit (Tx) TRN field type, and a Receive (Rx) TRN field type, and optionally, wherein the Tx TRN field type is to indicate that the plurality of TRN subfields comprises Tx TRN subfields for Tx BF training, and optionally, wherein the Rx TRN field type is to indicate that the plurality of TRN subfields comprises Rx TRN subfields for Rx BF training.
  • Tx Transmit
  • Rx Receive
  • Example 4 includes the subject matter of Example 3, and optionally, and optionally, wherein the plurality of predefined TRN field types comprises a Tx/Rx TRN field type to indicate that the plurality of TRN sub fields comprises one or more Tx TRN subfields and one or more Rx TRN subfields.
  • Example 5 includes the subject matter of Example 4, and optionally, and optionally, wherein the SIG field comprises an Rx/Tx field to indicate a count of Rx TRN subfields in a group of Rx TRN subfields corresponding to a Tx TRN subfield.
  • the SIG field comprises an Rx/Tx field to indicate a count of Rx TRN subfields in a group of Rx TRN subfields corresponding to a Tx TRN subfield.
  • Example 6 includes the subject matter of any one of Examples 2-5, and optionally, and optionally, wherein the TRN type indicator comprises a TRN type field comprising a type value from a plurality of predefined type values, the plurality of predefined type values comprises a first value to indicate a Transmit (Tx) TRN field type, a second value to indicate a Receive (Rx) TRN field type, and a third value to indicate a Tx/Rx TRN field type.
  • the TRN type indicator comprises a TRN type field comprising a type value from a plurality of predefined type values
  • the plurality of predefined type values comprises a first value to indicate a Transmit (Tx) TRN field type, a second value to indicate a Receive (Rx) TRN field type, and a third value to indicate a Tx/Rx TRN field type.
  • Example 7 includes the subject matter of any one of Examples 1-6, and optionally, and optionally, wherein the SIG field comprises a TRN subfield count field to indicate a count of the plurality of TRN subfields.
  • Example 8 includes the subject matter of any one of Examples 1-7, and optionally, and optionally, wherein the SIG field comprises at least one of a length field, an LTF count field, or a Transmit (Tx)/Receive (Rx) (Tx/Rx) configuration field, and optionally, wherein the length field is to indicate a length of the TRN subfields, the LTF count field is to indicate a count of LTFs per TRN subfield, the Tx/Rx configuration field to indicate a configuration of Tx TRN subfields and Rx TRN subfields in the TRN field.
  • the SIG field comprises at least one of a length field, an LTF count field, or a Transmit (Tx)/Receive (Rx) (Tx/Rx) configuration field
  • Tx/Rx Transmit
  • Rx Transmit
  • Tx/Rx configuration field to indicate a configuration of Tx TRN subfields in the TRN field.
  • Example 9 includes the subject matter of any one of Examples 1-8, and optionally, and optionally, wherein the packet comprises a feedback indication to indicate a request that an other mmWave STA participating in the BF training is to transmit to the mmWave STA feedback based on the TRN field.
  • Example 10 includes the subject matter of Example 9, and optionally, and optionally, wherein the feedback indication comprises feedback configuration information to configure which information is to be included in the feedback.
  • Example 11 includes the subject matter of Example 9 or 10, and optionally, and optionally, wherein the SIG field comprises the feedback indication.
  • Example 12 includes the subject matter of Example 9 or 10, and optionally, and optionally, wherein the packet comprises a data field after the SIG field, the data field comprising the feedback indication.
  • Example 13 includes the subject matter of any one of Examples 1-12, and optionally, and optionally, wherein the packet comprises a reverse-direction TRN request indication to indicate a request that an other mmWave STA participating in the BF training is to transmit another packet comprising a reverse-direction TRN field from the other mmWave STA.
  • the packet comprises a reverse-direction TRN request indication to indicate a request that an other mmWave STA participating in the BF training is to transmit another packet comprising a reverse-direction TRN field from the other mmWave STA.
  • Example 14 includes the subject matter of Example 13, and optionally, and optionally, wherein the SIG field comprises the reverse-direction TRN request indication.
  • Example 15 includes the subject matter of Example 13, and optionally, and optionally, wherein the packet comprises a data field after the SIG field, the data field comprising the reverse-direction TRN request indication.
  • Example 16 includes the subject matter of any one of Examples 1-15, and optionally, and optionally, wherein the apparatus is configured to cause the mmWave STA to transmit the preamble according to a first Transmit (Tx) antenna setting of the mmWave STA, and to transmit the plurality of TRN subfields according to one or more second Tx antenna settings of the mmWave STA, the one or more second Tx antenna settings different from the first Tx antenna setting.
  • Tx Transmit
  • Example 17 includes the subject matter of Example 16, and optionally, and optionally, wherein the first Tx antenna setting comprises an omni-directional setting.
  • Example 18 includes the subject matter of Example 16, and optionally, and optionally, wherein the first Tx antenna setting comprises a BF Tx setting according to a previous BF training.
  • Example 19 includes the subject matter of any one of Examples 1-18, and optionally, and optionally, wherein the apparatus is configured to cause the mmWave STA to transmit the plurality of TRN subfields according to a sector sweep via a plurality of Transmit (Tx) antenna sectors of the mmWave STA.
  • the apparatus is configured to cause the mmWave STA to transmit the plurality of TRN subfields according to a sector sweep via a plurality of Transmit (Tx) antenna sectors of the mmWave STA.
  • Tx Transmit
  • Example 20 includes the subject matter of any one of Examples 1-19, and optionally, and optionally, wherein the TRN subfield comprises the STF.
  • Example 21 includes the subject matter of Example 20, and optionally, and optionally, wherein the TRN subfield comprises the LTF after the STF.
  • Example 22 includes the subject matter of any one of Examples 1-21, and optionally, and optionally, wherein the TRN subfield comprises the LTF.
  • Example 23 includes the subject matter of any one of Examples 1-22, and optionally, and optionally, wherein the TRN subfield comprises a plurality of repetitions of the LTF.
  • Example 24 includes the subject matter of any one of Examples 1-23, and optionally, and optionally, wherein the packet comprises a Null-Data-Packet (NDP).
  • NDP Null-Data-Packet
  • Example 25 includes the subject matter of any one of Examples 1-23, and optionally, and optionally, wherein the packet comprises a Physical layer (PHY) Protocol Data Unit (PPDU) comprising a data field after the SIG field, and optionally, wherein the TRN field is after the data field.
  • PHY Physical layer
  • PPDU Protocol Data Unit
  • Example 26 includes the subject matter of any one of Examples 1-25, and optionally, and optionally, wherein the mmWave wireless communication channel comprises a 60GHz channel.
  • Example 27 includes the subject matter of any one of Examples 1-26, and optionally, comprising a radio to transmit the packet over the mmWave wireless communication channel.
  • Example 28 includes the subject matter of Example 27, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the mmWave STA.
  • Example 29 includes an apparatus comprising logic and circuitry configured to cause a first millimeterWave (mmWave) wireless communication station (STA) to process a preamble of a packet received from a second mmWave STA over a mmWave wireless communication channel, the preamble comprising a Short Training Field (STF), a Long Training Field (LTF) after the STF, and a Signal (SIG) field after the LTF, and optionally, wherein the SIG field comprises a presence indicator configured to indicate that the packet comprises a Training (TRN) field configured for Beamforming (BF) training after the SIG field; and perform measurements on one or more received TRN subfields of the TRN field of the packet, and optionally, wherein a TRN subfield comprises at least one of the STF or the LTF.
  • TRN Training
  • BF Beamforming
  • Example 30 includes the subject matter of Example 29, and optionally, and optionally, wherein the SIG field comprises a TRN type indicator configured to indicate a type of the TRN field.
  • Example 31 includes the subject matter of Example 30, and optionally, and optionally, wherein the TRN type indicator is configured to indicate the type of the TRN field from a plurality of predefined TRN field types, and optionally, wherein the plurality of predefined TRN field types comprises a Transmit (Tx) TRN field type, and a Receive (Rx) TRN field type, and optionally, wherein the Tx TRN field type is to indicate that the plurality of TRN subfields comprises Tx TRN subfields for Tx BF training, and optionally, wherein the Rx TRN field type is to indicate that the plurality of TRN subfields comprises Rx TRN subfields for Rx BF training.
  • Tx Transmit
  • Rx Receive
  • Example 32 includes the subject matter of Example 31, and optionally, and optionally, wherein the plurality of predefined TRN field types comprises a Tx/Rx TRN field type to indicate that the plurality of TRN sub fields comprises one or more Tx TRN subfields and one or more Rx TRN subfields.
  • Example 33 includes the subject matter of Example 32, and optionally, and optionally, wherein the SIG field comprises an Rx/Tx field to indicate a count of Rx TRN subfields in a group of Rx TRN subfields corresponding to a Tx TRN subfield.
  • Example 34 includes the subject matter of any one of Examples 30-33, and optionally, and optionally, wherein the TRN type indicator comprises a TRN type field comprising a type value from a plurality of predefined type values, the plurality of predefined type values comprises a first value to indicate a Transmit (Tx) TRN field type, a second value to indicate a Receive (Rx) TRN field type, and a third value to indicate a Tx/Rx TRN field type.
  • the TRN type indicator comprises a TRN type field comprising a type value from a plurality of predefined type values
  • the plurality of predefined type values comprises a first value to indicate a Transmit (Tx) TRN field type, a second value to indicate a Receive (Rx) TRN field type, and a third value to indicate a Tx/Rx TRN field type.
  • Example 35 includes the subject matter of any one of Examples 29-34, and optionally, and optionally, wherein the SIG field comprises a TRN subfield count field to indicate a count of the plurality of TRN subfields.
  • Example 36 includes the subject matter of any one of Examples 29-35, and optionally, and optionally, wherein the SIG field comprises at least one of a length field, an LTF count field, or a Transmit (Tx)/Receive (Rx) (Tx/Rx) configuration field, and optionally, wherein the length field is to indicate a length of the TRN subfields, the LTF count field is to indicate a count of LTFs per TRN subfield, the Tx/Rx configuration field to indicate a configuration of Tx TRN subfields and Rx TRN subfields in the TRN field.
  • the SIG field comprises at least one of a length field, an LTF count field, or a Transmit (Tx)/Receive (Rx) (Tx/Rx) configuration field
  • Tx/Rx Transmit
  • Rx Transmit
  • Tx/Rx configuration field to indicate a configuration of Tx TRN subfields and Rx TRN subfields in the TRN field.
  • Example 37 includes the subject matter of any one of Examples 29-36, and optionally, and optionally, wherein the apparatus is configured to cause the first mmWave STA to, based on a feedback indication in the packet, transmit a packet comprising feedback to the second mmWave STA based on the measurements on the one or more received TRN subfields.
  • Example 38 includes the subject matter of Example 37, and optionally, and optionally, wherein the feedback indication comprises feedback configuration information to configure which information is to be included in the feedback.
  • Example 39 includes the subject matter of Example 37 or 38, and optionally, and optionally, wherein the SIG field comprises the feedback indication.
  • Example 40 includes the subject matter of Example 37 or 38, and optionally, and optionally, wherein the packet comprises a data field after the SIG field, the data field comprising the feedback indication.
  • Example 41 includes the subject matter of any one of Examples 29-36, and optionally, and optionally, wherein the apparatus is configured to cause the first mmWave STA to, based on a reverse-direction TRN request indication in the packet, transmit another packet comprising a reverse-direction TRN field to the second mmWave STA.
  • Example 42 includes the subject matter of Example 41, and optionally, and optionally, wherein the SIG field comprises the reverse-direction TRN request indication.
  • Example 43 includes the subject matter of Example 41, and optionally, and optionally, wherein the packet comprises a data field after the SIG field, the data field comprising the reverse-direction TRN request indication.
  • Example 44 includes the subject matter of any one of Examples 29-43, and optionally, and optionally, wherein the apparatus is configured to cause the first mmWave STA to receive the one or more received TRN subfields according to a sector sweep via a plurality of Receive (Rx) antenna sectors of the first mmWave STA.
  • the apparatus is configured to cause the first mmWave STA to receive the one or more received TRN subfields according to a sector sweep via a plurality of Receive (Rx) antenna sectors of the first mmWave STA.
  • Example 45 includes the subject matter of any one of Examples 29-44, and optionally, and optionally, wherein the TRN subfield comprises the STF.
  • Example 46 includes the subject matter of Example 45, and optionally, and optionally, wherein the TRN subfield comprises the LTF after the STF.
  • Example 47 includes the subject matter of any one of Examples 29-46, and optionally, and optionally, wherein the TRN subfield comprises the LTF.
  • Example 48 includes the subject matter of any one of Examples 29-47, and optionally, and optionally, wherein the TRN subfield comprises a plurality of repetitions of the LTF.
  • Example 49 includes the subject matter of any one of Examples 29-48, and optionally, and optionally, wherein the packet comprises a Null-Data-Packet (NDP).
  • NDP Null-Data-Packet
  • Example 50 includes the subject matter of any one of Examples 29-49, and optionally, and optionally, wherein the packet comprises a Physical layer (PHY) Protocol Data Unit (PPDU) comprising a data field after the SIG field, and optionally, wherein the TRN field is after the data field.
  • Example 51 includes the subject matter of any one of Examples 29-50, and optionally, and optionally, wherein the mmWave wireless communication channel comprises a 60GHz channel.
  • Example 52 includes the subject matter of any one of Examples 29-51, and optionally, comprising a radio to receive the packet over the mmWave wireless communication channel.
  • Example 53 includes the subject matter of Example 52, and optionally, comprising one or more antennas connected to the radio, and a processor to execute instructions of an operating system of the first mmWave STA.
  • Example 54 comprises a wireless communication device comprising the apparatus of any of Examples 1-53.
  • Example 55 comprises an apparatus comprising means for executing any of the described operations of any of Examples 1-53.
  • Example 56 comprises a product comprising one or more tangible computer- readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a wireless communication device to perform any of the described operations of any of Examples 1-53.
  • Example 57 comprises an apparatus comprising: a memory interface; and processing circuitry configured to: perform any of the described operations of any of Examples 1-53.
  • Example 58 comprises a method comprising any of the described operations of any of Examples 1-53.

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) à ondes millimétriques (mmWave) peut être configurée pour : transmettre un préambule d'un paquet sur un canal de communication sans fil mmWave, le préambule comprenant un champ d'apprentissage court (STF), un champ d'apprentissage long (LTF) après le STF, ainsi qu'un champ de signal (SIG) après le LTF, le champ SIG comprenant un indicateur de présence configuré pour indiquer que le paquet comprend un champ d'apprentissage (TRN) configuré pour un apprentissage de formation de faisceau (BF); et transmettre le champ TRN du paquet sur le canal de communication sans fil mmWave, le champ TRN étant après le champ SIG, le champ TRN comprenant une pluralité de sous-champs TRN, un sous-champ TRN comprenant le STF et/ou le LTF.
EP22949634.4A 2022-06-30 2022-06-30 Appareil, système et procédé de communication d'un paquet avec un champ d'apprentissage (trn) Pending EP4548485A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2022/035623 WO2024005809A1 (fr) 2022-06-30 2022-06-30 Appareil, système et procédé de communication d'un paquet avec un champ d'apprentissage (trn)

Publications (1)

Publication Number Publication Date
EP4548485A1 true EP4548485A1 (fr) 2025-05-07

Family

ID=89381037

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22949634.4A Pending EP4548485A1 (fr) 2022-06-30 2022-06-30 Appareil, système et procédé de communication d'un paquet avec un champ d'apprentissage (trn)

Country Status (3)

Country Link
US (1) US20250350520A1 (fr)
EP (1) EP4548485A1 (fr)
WO (1) WO2024005809A1 (fr)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8422961B2 (en) * 2009-02-23 2013-04-16 Nokia Corporation Beamforming training for functionally-limited apparatuses
WO2017044420A1 (fr) * 2015-09-10 2017-03-16 Interdigital Patent Holdings, Inc. Procédés, appareil et systèmes pour une estimation de canal et un apprentissage de formation de faisceau simultané pour des communications à entrées multiples, sorties multiples (mimo)
CN118214465A (zh) * 2017-05-05 2024-06-18 交互数字专利控股公司 Mimo信道接入
CN114208042A (zh) * 2019-08-07 2022-03-18 索尼集团公司 通信设备及通信方法
US12463761B2 (en) * 2021-12-24 2025-11-04 Intel Corporation Apparatus, system, and method of a transmit sector sweep (TXSS) procedure over a millimeterwave (mmWave) wireless communication channel

Also Published As

Publication number Publication date
WO2024005809A1 (fr) 2024-01-04
US20250350520A1 (en) 2025-11-13

Similar Documents

Publication Publication Date Title
US11438907B2 (en) Apparatus, system and method of beamforming and beam tracking
EP3289697B1 (fr) Appareil, système et procédé de formation de faisceau
EP4454192A1 (fr) Appareil, système et procédé de procédure de balayage de secteur de transmission (txss) sur un canal de communication sans fil à ondes millimétriques (mmwave)
US10681699B2 (en) Apparatus, system and method of communicating an enhanced directional multi gigabit (EDMG) capability element
US10243630B2 (en) Apparatus, system and method of communicating via a plurality of sectorized antennas
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
US11368204B2 (en) Apparatus, system and method of beam refinement protocol (BRP) transmit (TX) sector sweep (SS) (TXSS)
US11362720B2 (en) Apparatus, system and method of beam refinement protocol (BRP) transmit (TX) sector sweep (SS) (TXSS)
US20220338026A1 (en) Apparatus, system, and method of communicating a beamformed transmission
US20250330360A1 (en) Apparatus, system, and method of communicating a short training field (stf) over a millimeterwave (mmwave) channel
US12294892B2 (en) Apparatus, system, and method of communicating bandwidth information of a wireless communication link
US20250350520A1 (en) Apparatus, system, and method of communicating a packet with a training (trn) field
WO2018071057A1 (fr) Appareil, système et procédé de communication d'une trame au protocole d'affinement de faisceau (brp)
US20250330232A1 (en) Apparatus, system, and method of communicating a packet including a multiple-input-multiple-output (mimo) training (trn) field
US20240172281A1 (en) Apparatus, system, and method of multi-link operation (mlo) with a millimeter wave (mmwave) link
US20250175235A1 (en) Apparatus, system, and method of beamforming training over a millimeterwave (mmwave) wireless communication channel
EP4171155A1 (fr) Appareil, système et procédé de communication d'informations de bande passante d'une liaison de communication sans fil
US20240031087A1 (en) Apparatus, system, and method of 40 megahertz operating non access point (non-ap) station
EP4472330A1 (fr) Appareil, système et procédé de transmission d'une transmission conjointe
EP4171166A1 (fr) Appareil, système et procédé de communication d'un élément de qualité de service (qos)
WO2024144784A1 (fr) Appareil, système et procédé d'indication de dispositif à liaisons multiples (mld) non colocalisé
EP4548678A1 (fr) Appareil, système et procédé de communication sur un canal à ondes millimétriques (mmwave) sur la base d'informations communiquées sur un canal inférieur à 10 gigahertz (ghz) (sous-10 ghz)

Legal Events

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

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

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20241029

AK Designated contracting states

Kind code of ref document: A1

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

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)