Patent Description:
Embodiments described herein generally relate to communicating a wireless transmission according to a Physical layer (PHY) scheme.

A wireless communication network in a millimeter-wave band may provide high-speed data access for users of wireless communication devices.

A wireless communication station may communicate a wireless transmission according to a Physical layer (PHY) scheme.

The Specification of IEEE <NUM>. 11ad-<NUM> ("<NPL>) defines four types of PHY schemes. Specifically, the IEEE <NUM>. 11ad-<NUM> defines four types of Physical Layer (PHY) schemes for communication, e.g., Single Carrier (SC), Orthogonal Frequency Division Multiplexing (OFDM), Low Power SC. (LPSC), and control PHY.

According to the Specification of IEEE <NUM>. 11ad-<NUM>, supporting reception of transmissions using basic SC modulations and Control PHY may be mandatory for all devices, while supporting OFDM and LPSC transmissions may be optional.

Accordingly, a device supporting only the SC and Control PHY configurations may not be able to decode OFDM and/or LPSC packets. <CIT> relates to a method for generating a frame structure that can be used with multiple transmission schemes, such as a Single Carrier (SC) transmission scheme and an Orthogonal Frequency Division Multiplexing (OFDM) transmission scheme. It is disclosed that a common short header may be employed in order to allow the subscriber device to determine for how long the transmission medium is busy. The common short header may be transmitted at the SC chip rate, and may comprise the following fields: a frame length field, a Modulation and Coding Scheme (MCS) field, an SC/OFDM bit indicating if the SC or the OFDM transmission scheme is employed for transmission of the frame, a Reserved (RES) field, and a Cyclic Redundancy Check (CRC) field.

The claimed invention corresponds to the embodiment of <FIG>.

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

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

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.

The terms "plurality" and "a plurality", as used herein, include, for example, "multiple" or "two or more". For example, "a plurality of items" includes two or more items.

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

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

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

Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (<NPL>) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE <NUM> standards (<NPL>; IEEE802. <NUM> ac-<NUM> ("<NPL>); IEEE <NUM>. 11ad ("<NPL>); IEEE-<NUM>. 11REVmc ("<NPL>"); IEEE802. <NUM>-ay (<NPL>) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless Fidelity (WiFi) Alliance (WFA) Peer-to-Peer (P2P) specifications (<NPL>) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE) and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

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

Some embodiments 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 <NUM>, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, Fifth Generation (<NUM>), or Sixth Generation (<NUM>) mobile networks, 3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems and/or networks.

The term "wireless device", as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, 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. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase "communicating a signal" may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase "communicating a signal" may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN, e.g., a wireless fidelity (WiFi) network. Other embodiments may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a "piconet", a WPAN, a WVAN and the like.

Some demonstrative embodiments may be used in conjunction with a wireless communication network communicating over a frequency band of <NUM>. However, other embodiments may be implemented utilizing any other suitable wireless communication frequency bands, for example, an Extremely High Frequency (EHF) band (the millimeter wave (mmWave) frequency band), e.g., a frequency band within the frequency band of between <NUM> and <NUM>, a frequency band above <NUM>, a frequency band below <NUM>, e.g., a Sub <NUM> (S1G) band, a <NUM> band, a <NUM> band, a WLAN frequency band, a WPAN frequency band, a frequency band according to the WGA specification, and the like.

The term "antenna", as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, 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.

The phrases "directional multi-gigabit (DMG)" and "directional band" (DBand), as used herein, may relate to a frequency band wherein the Channel starting frequency is above <NUM>. In one example, DMG communications may involve one or more directional links to communicate at a rate of multiple gigabits per second, for example, at least <NUM> Gigabit per second, e.g., <NUM> Gigabit per second, or any other rate.

Some demonstrative embodiments may be implemented by a DMG STA (also referred to as a "mmWave STA (mSTA)"), which may include for example, a STA having a radio transmitter, which is capable of operating on a channel that is within the DMG band. The DMG STA may perform other additional or alternative functionality. Other embodiments may be implemented by any other apparatus, device and/or station.

Reference is made to <FIG>, which schematically illustrates a system <NUM>, in accordance with some demonstrative embodiments.

As shown in <FIG>, in some demonstrative embodiments, system <NUM> may include one or more wireless communication devices. For example, system <NUM> may include wireless communication devices <NUM>, <NUM> and/or <NUM>.

In some demonstrative embodiments, devices <NUM> and/or <NUM> may include and/or perform the functionality of one or more STAs. For example, device <NUM> may include at least one STA, and/or device <NUM> may include at least one STA.

In some demonstrative embodiments, devices <NUM> and/or <NUM> may include and/or perform the functionality of one or more DMG STAs. For example, device <NUM> may include at least one DMG STA, and/or device <NUM> may include at least one DMG STA.

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

In some demonstrative embodiments, device <NUM> may include, for example, one or more of a processor <NUM>, an input unit <NUM>, an output unit <NUM>, a memory unit <NUM>, and/or a storage unit <NUM>; and/or device <NUM> may include, for example, one or more of a processor <NUM>, an input unit <NUM>, an output unit <NUM>, a memory unit <NUM>, and/or a storage unit <NUM>. Devices <NUM> and/or <NUM> may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of devices <NUM> and/or <NUM> may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of devices <NUM> and/or <NUM> may be distributed among multiple or separate devices.

Processor <NUM> and/or processor <NUM> includes, 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 multipurpose or specific processor or controller. Processor <NUM> executes instructions, for example, of an Operating System (OS) of device <NUM> and/or of one or more suitable applications. Processor <NUM> executes instructions, for example, of an Operating System (OS) of device <NUM> and/or of one or more suitable applications.

Input unit <NUM> and/or input unit <NUM> includes, 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 <NUM> and/or output unit <NUM> includes, 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.

Memory unit <NUM> and/or memory unit <NUM> 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 <NUM> and/or storage unit <NUM> includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. Memory unit <NUM> and/or storage unit <NUM>, for example, may store data processed by device <NUM>. Memory unit <NUM> and/or storage unit <NUM>, for example, may store data processed by device <NUM>.

In some demonstrative embodiments, wireless communication devices <NUM>, <NUM> and/or <NUM> may be capable of communicating content, data, information and/or signals via a wireless medium (WM) <NUM>. In some demonstrative embodiments, wireless medium <NUM> may include, for example, a radio channel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, an IR channel, a Bluetooth (BT) channel, a Global Navigation Satellite System (GNSS) Channel, and the like.

In some demonstrative embodiments, WM <NUM> may include a directional channel. For example, WM <NUM> may include a millimeter-wave (mmWave) wireless communication channel.

In some demonstrative embodiments, WM <NUM> may include a DMG channel. In other embodiments WM <NUM> may include any other directional channel.

In other embodiments, WM <NUM> may include any other type of channel over any other frequency band.

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may include one or more radios including circuitry and/or logic to perform wireless communication between devices <NUM>, <NUM>, <NUM> and/or one or more other wireless communication devices. For example, device <NUM> may include a radio <NUM>, and/or device <NUM> may include at least one radio <NUM>.

In some demonstrative embodiments, radios <NUM> and/or <NUM> may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio <NUM> may include a receiver <NUM>, and/or radio <NUM> may include a receiver <NUM>.

In some demonstrative embodiments, radios <NUM> and/or <NUM> may include one or more wireless transmitters (Tx) including circuitry and/or logic to send wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio <NUM> may include a transmitter <NUM>, and/or radio <NUM> may include a transmitter <NUM>.

In some demonstrative embodiments, radios <NUM> and/or <NUM> may include circuitry, logic, modulation elements, demodulation elements, amplifiers, analog to digital and digital to analog converters, filters, and/or the like. For example, radios <NUM> and/or <NUM> may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like.

In some demonstrative embodiments, radios <NUM> and/or <NUM> may include, or may be associated with, one or more antennas <NUM> and/or <NUM>, respectively.

In one example, device <NUM> may include a single antenna <NUM>. In other example, device <NUM> may include two or more antennas <NUM>.

Antennas <NUM> and/or <NUM> may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas <NUM> and/or <NUM> may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. Antennas <NUM> and/or <NUM> may include, for example, antennas suitable for directional communication, e.g., using beamforming techniques. For example, antennas <NUM> and/or <NUM> may include a phased array antenna, a multiple element antenna, a set of switched beam antennas, and/or the like. In some embodiments, antennas <NUM> and/or <NUM> may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas <NUM> and/or <NUM> may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

In some demonstrative embodiments, antennas <NUM> and/or <NUM> may include a directional antenna, which may be steered to a plurality of beam directions.

In some demonstrative embodiments, device <NUM> may include a controller <NUM>, and/or device <NUM> may include a controller <NUM>. Controllers <NUM> and/or <NUM> may be configured to perform one or more communications, may generate and/or communicate one or more messages and/or transmissions, and/or may perform one or more functionalities, operations and/or procedures between devices <NUM>, <NUM> and/or <NUM> and/or one or more other devices, e.g., as described below.

In some demonstrative embodiments, controllers <NUM> and/or <NUM> may include 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, and/or any other circuitry and/or logic, configured to perform the functionality of controllers <NUM> and/or <NUM>, respectively. Additionally or alternatively, one or more functionalities of controllers <NUM> and/or <NUM> may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

In one example, controller <NUM> may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause a wireless device, e.g., device <NUM>, and/or a wireless station, e.g., a wireless STA implemented by device <NUM>, to perform one or more operations, communications and/or functionalities, e.g., as described herein.

In some demonstrative embodiments, device <NUM> may include a message processor <NUM> configured to generate, process and/or access one or messages communicated by device <NUM>.

In one example, message processor <NUM> may be configured to generate one or more messages to be transmitted by device <NUM>, and/or message processor <NUM> may be configured to access and/or to process one or more messages received by device <NUM>, e.g., as described below. In one example, message processor <NUM> may be configured to process transmission of one or more messages from a wireless station, e.g., a wireless STA implemented by device <NUM>; and/or message processor <NUM> may be configured to process reception of one or more messages by a wireless station, e.g., a wireless STA implemented by device <NUM>.

In some demonstrative embodiments, message processors <NUM> and/or <NUM> may include circuitry, e.g., processor circuitry, memory circuitry, Media-Access Control (MAC) circuitry, Physical Layer (PHY) circuitry, and/or any other circuitry, configured to perform the functionality of message processors <NUM> and/or <NUM>. Additionally or alternatively, one or more functionalities of message processors <NUM> and/or <NUM> may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

In some demonstrative embodiments, at least part of the functionality of message processor <NUM> may be implemented as part of radio <NUM>, and/or at least part of the functionality of message processor <NUM> may be implemented as part of radio <NUM>.

In some demonstrative embodiments, at least part of the functionality of message processor <NUM> may be implemented as part of controller <NUM>, and/or at least part of the functionality of message processor <NUM> may be implemented as part of controller <NUM>.

In other embodiments, the functionality of message processor <NUM> may be implemented as part of any other element of device <NUM>, and/or the functionality of message processor <NUM> may be implemented as part of any other element of device <NUM>.

In some demonstrative embodiments, at least part of the functionality of controller <NUM> and/or message processor <NUM> may be implemented by an integrated circuit, for example, a chip, e.g., a System in Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio <NUM>. For example, the chip or SoC may include one or more elements of controller <NUM>, one or more elements of message processor <NUM>, and/or one or more elements of radio <NUM>. In one example, controller <NUM>, message processor <NUM>, and radio <NUM> may be implemented as part of the chip or SoC.

In other embodiments, controller <NUM>, message processor <NUM> and/or radio <NUM> may be implemented by one or more any additional or alternative elements of device <NUM>.

In some demonstrative embodiments, at least part of the functionality of controller <NUM> and/or message processor <NUM> may be implemented by an integrated circuit, for example, a chip, e.g., a SoC. In one example, the chip or SoC may be configured to perform one or more functionalities of radio <NUM>. For example, the chip or SoC may include one or more elements of controller <NUM>, one or more elements of message processor <NUM>, and/or one or more elements of radio <NUM>. In one example, controller <NUM>, message processor <NUM>, and radio <NUM> may be implemented as part of the chip or SoC.

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may be configured to support and/or perform communication according to one or more Physical layer (PHY) schemes, configurations and/or types ("PHY configurations" or "PHY schemes").

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may be configured to support transmissions according to one or more types of physical layers (PHY), e.g., one or more of four types of physical layers or any other number of PHY types.

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may be configured to support transmissions according to one or more of a Single Carrier (SC) PHY, an OFDM PHY, a Low Power SC (LPSC) PHY, a Control PHY, and/or any other PHY type.

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may be configured to support transmissions according to the SC PHY, the OFDM PHY, the LPSC PHY and/or the Control PHY, for example, in accordance with PHY schemes of an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., IEEE <NUM>. 11ad-<NUM>, IEEE <NUM>. 11REVmc, and/or any other Specification and/or protocol.

In some demonstrative embodiments, devices of system <NUM>, e.g., devices <NUM>, <NUM> and/or <NUM>, may be required to support one or more PHY configurations, while support of one or more other PHY configurations may be optional.

In one example, reception of SC transmissions, e.g., basic SC modulations, and Control PHY transmissions, may be defined as mandatory for all devices of system <NUM>, e.g., including devices <NUM>, <NUM> and/or <NUM>, while supporting OFDM PHY, LPSC PHY, and/or one or more other PHY configurations may be optional.

In some demonstrative embodiments, one or more devices of system <NUM>, e.g., devices <NUM> and/or <NUM>, may support one or more PHY configurations, for example, including at least OFDM PHY and/or LPSC PHY, for example, in addition to supporting SC PHY and/or Control PHY.

In some demonstrative embodiments, one or more devices of system <NUM>, e.g., device <NUM>, may not support OFDM PHY, LPSC PHY and/or one or more other PHY configurations, e.g., while supporting SC PHY and/or Control PHY.

In some demonstrative embodiments, one or more portions of packets ("OFDM and/or LPSC packets") transmitted according to the OFDM PHY and/or LPSC PHY schemes may have a modulation and/or coding scheme, which may not be supported by the SC PHY and/or the Control PHY.

In some demonstrative embodiments, a device not supporting OFDM PHY and/or LPSC PHY, for example, a device supporting only SC PHY ("SC only device"), e.g., device <NUM>, may not be able to demodulate and/or decode one or more portions of the OFDM and/or LPSC packets, for example, if the one or more portions are modulated and/or encoded using a modulation and/or encoding scheme, which is different from a modulation and coding scheme supported by the SC PHY and/or the Control PHY.

In one example, the SC only device, e.g., device <NUM>, may not be able to demodulate and/or decode a header of a packet, for example, if the header is modulated and/or encoded using a modulation and/or encoding scheme, which may be different from a modulation and/or encoding scheme supported by the SC PHY and/or the Control PHY.

In another example, the SC only device, e.g., device <NUM>, may not be able to perform a correct channel estimation based on a channel estimation (CE) field of a packet, for example, if the CE field includes a CE sequence configured according to a modulation and/or encoding scheme, which may be different from a SC modulation and/or encoding scheme.

According to these embodiments, the SC only device, e.g., device <NUM>, may not be able to determine a length and/or duration, e.g., a Transmit time (TxTIME), of the packet. Therefore, the SC only device, e.g., device <NUM>, may not be able to determine when it may be allowed to start a transmission. This situation may potentially result, for example, in a coexistence problem, e.g., a major coexistence problem, across PHYs, e.g., between devices supporting OFDM PHY and/or LPSC PHY, e.g., devices <NUM> and/or <NUM>, and devices not supporting OFDM PHY and/or LPSC PHY, e.g., device <NUM>.

In some demonstrative embodiments, a modulation of the OFDM and/or LPSC packet according to a scheme defined, for example, by the IEEE <NUM>. 11ad-<NUM> Specification, may not enable SC only devices, e.g., device <NUM>, to determine the length (TXTIME) of packets which are OFDM or LPSC packets.

<FIG> schematically illustrates a SC frame structure of a frame <NUM> ("SC frame"), in accordance with some demonstrative examples.

In some demonstrative examples, the SC frame structure of <FIG> may be configured in accordance with an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., an IEEE <NUM>. 11ad-<NUM> Specification, and/or any other Specification or Standard.

In some demonstrative examples, as shown in <FIG>, frame <NUM> may include a short training field <NUM>, a CE field <NUM>, a header field <NUM>, a data portion <NUM>, e.g., including a plurality of data blocks (BLK) <NUM>, an Automatic Gain Control (AGC) field <NUM>, and/or a Training (TRN) field <NUM>.

In some demonstrative examples, at least the CE field <NUM>, the header field <NUM>, and the data portion <NUM> may be encoded and/or modulated according to a SC PHY scheme. The SC PHY scheme may include, for example, a SC PHY modulation and/or coding scheme, for example, in accordance with an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., an IEEE <NUM>. 11ad-<NUM> Specification, and/or any other Specification or Standard.

In some demonstrative examples, a LPSC PHY frame structure may be similar, e.g., for one or more of the embodiments described herein, to the frame structure of the SC PHY frame <NUM> of <FIG>.

For example, an LPSC frame may have a structure similar to the structure of frame <NUM>. In one example, header <NUM> may include a LPSC header, and data portion <NUM> may be encoded and/or modulated according to a LPSC PHY scheme. The LPSC PHY scheme may include, for example, a LPSC PHY modulation and/or coding scheme, for example, in accordance with an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., an IEEE <NUM>. 11ad-<NUM> Specification, and/or any other Specification or Standard.

In some demonstrative examples, header field <NUM> may include a modulation and coding scheme (MCS) field <NUM> including an MCS value, e.g., as described below.

<FIG> schematically illustrates an OFDM frame structure of a frame <NUM> ("OFDM frame"), in accordance with some demonstrative examples.

In some demonstrative examples, the OFDM frame structure of <FIG> may be configured in accordance with an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., an IEEE <NUM>. 11ad-<NUM> Specification, and/or any other Specification or Standard.

In some demonstrative examples, as shown in <FIG>, frame <NUM> may include a short training field <NUM>, a CE field <NUM>, a header field <NUM>, a data portion <NUM>, e.g., including a plurality of OFDM Symbols (SYM) <NUM>, and AGC field <NUM>, and/or a Training (TRN) field <NUM>.

In some demonstrative examples, header field <NUM> may include a modulation and coding scheme (MCS) filed <NUM> including an MCS value, e.g., as described below.

In some demonstrative examples, the data portion <NUM> may be encoded and/or modulated according to an OFDM PHY scheme. The OFDM PHY scheme may include, for example, an OFDM PHY modulation and/or coding scheme, for example, in accordance with an IEEE Specification, for example, an IEEE <NUM> Specification, e.g., an IEEE <NUM>. 11ad-<NUM> Specification, and/or any other Specification or Standard.

In some demonstrative examples, the CE field <NUM> of the OFDM frame <NUM> may be different from the CE field <NUM> of the SC frame <NUM>.

In some demonstrative examples, a number of bits in the header <NUM> (SC header) of frame <NUM> may be the same as a number of bits in the header <NUM> (OFDM header) of OFDM frame <NUM>.

Referring back to <FIG>, in some demonstrative embodiments, a device that supports OFDM PHY, e.g., device <NUM> and/or device <NUM>, may be able to detect the CE field of an OFDM frame, e.g., CE field <NUM> (<FIG>) of OFDM frame <NUM> (<FIG>), which may be different from the CE field of a SC frame, e.g., CE field <NUM> (<FIG>) of SC frame <NUM> (<FIG>).

In some demonstrative examples, if the header of the OFDM frame, e.g., header <NUM> (<FIG>), is modulated according to an OFDM modulation scheme, the device supporting OFDM PHY, e.g., device <NUM> and/or device <NUM>, may be able to proceed to demodulate the header of the OFDM frame, for example, using an OFDM demodulation scheme, e.g., rather than a SC demodulation scheme.

In some demonstrative examples, if the header of the OFDM frame, e.g., header <NUM> (<FIG>), is modulated according to an OFDM modulation scheme, a SC only receiver, e.g., device <NUM>, may not be able to demodulate and/or decode the OFDM header and, therefore, the SC only receiver may not be able to determine the length of the OFDM frame.

In some demonstrative examples, the inability of the SC only receiver to demodulate the header of the OFDM frame may lead to a situation, in which the SC only device, e.g., device <NUM>, may not be able correctly operate a virtual carrier sense function, e.g., which may be required for channel access, for example, since the SC only device may not be able to determine the actual length of the OFDM frame.

In some demonstrative examples, if the header of a LPSC frame, e.g., header <NUM> (<FIG>) of a LPSC frame having a frame structure of <FIG>, is modulated according to a LPSC modulation scheme, a device supporting LPSC PHY, e.g., device <NUM> and/or device <NUM>, may be able to proceed to demodulate the header of the LPSC frame, for example, using a LPSC demodulation scheme, e.g., rather than a SC demodulation scheme.

In some demonstrative examples, if the header of the LPSC frame, e.g., header <NUM> (<FIG>) of the LPSC frame, is modulated according to a LPSC modulation scheme, a SC only receiver, e.g., device <NUM>, may not be able to demodulate and/or decode the LPSC header and, therefore, the SC only receiver may not be able to determine the length of the LPSC frame.

In some demonstrative examples, the inability of the SC only receiver to demodulate the header of the LPSC frame may lead to a situation, in which the SC only device, e.g., device <NUM>, may not be able correctly operate a virtual carrier sense function, e.g., which may be required for channel access, for example, since the SC only device may not be able to determine the actual length of the LPSC frame.

In some demonstrative embodiments, a device, e.g., device <NUM>, may be configured to transmit an OFDM frame and/or a LPSC frame, for example, to another device, e.g., device <NUM>, which may be configured to support OFDM PHY and/or LPSC PHY. The OFDM frame and/or a LPSC frame may be configured to enable a device, e.g., device <NUM>, which does not support OFDM PHY and/or LPSC PHY, to demodulate and/or decode one or more portions of the OFDM frame and/or a LPSC frame, for example, in a manner which may be sufficient to determine a duration of the OFDM frame and/or a LPSC frame, e.g., as described below.

In some demonstrative embodiments, device <NUM> and/or device <NUM> may be configured to support transmission and/or reception of both OFDM frames and LPSC frames. In other embodiments, device <NUM> and/or device <NUM> may be configured to support transmission and/or reception of OFDM frames, e.g., while not being able to support transmission and/or reception of LPSC frames. In other embodiments, device <NUM> and/or device <NUM> may be configured to support transmission and/or reception of LPSC frames, e.g., while not being able to support transmission and/or reception of OFDM frames.

In some demonstrative embodiments, device <NUM> may be configured to transmit a packet using a single preamble and/or header format, which may, for example, be applied with respect to packets of a plurality of PHY types, for example, including the OFDM PHY, the SC PHY, and/or the LPSC PHY, e.g., as described below.

In some demonstrative embodiments, the header of the frame may optionally be followed by another header, e.g., as described below.

In some demonstrative embodiments, device <NUM> may be configured to use the header fields of the OFDM and/or LPSC headers, while, for example, being configured to encode and/or modulate the header, for example, using the same bits as in SC, e.g., an encoding of a SC PHY header.

In some demonstrative embodiments, a device, e.g., device <NUM>, may be configured to use the same header field and/or CE field structure for SC and OFDM and/or LPSC frames, for example, instead of using a different header field and/or CE field, e.g., as described below.

In some demonstrative embodiments, a device, e.g., device <NUM>, may be configured to use the same CE field and/or header encoding and/or modulation for SC and OFDM and/or LPSC frames. In one example, the actual bits in the header may not be changed.

In some demonstrative embodiments, a device, e.g., device <NUM>, that receives a frame with this header may be able to detect that the frame is an OFDM frame, a SC frame, or an LPSC frame, for example, by inspecting the field of the modulation and coding scheme (MCS) in the header, e.g., MCS field <NUM> (<FIG>) for a SC frame or an LPSC frame, or field <NUM> (<FIG>) for an OFDM frame, e.g., as described below.

In some demonstrative embodiments, an MCS field of a SC frame, for example, MCS field <NUM> (<FIG>) may have an MCS value of a SC PHY scheme. For example, MCS field <NUM> (<FIG>) may have a value within a first range of MCS values, e.g., an MCS value between <NUM>-<NUM>, or any other range.

In some demonstrative embodiments, an MCS field of an OFDM frame, for example, MCS field <NUM> (<FIG>) may have an MCS value of an OFDM PHY scheme. For example, MCS field <NUM> (<FIG>) may have a value within a second range of MCS values, e.g., an MCS value between <NUM>-<NUM>, or any other range.

In some demonstrative embodiments, an MCS field of an LPSC frame, for example, MCS field <NUM> (<FIG>) may have an MCS value of an LPSC PHY scheme. For example, MCS field <NUM> (<FIG>) may have a value within a third range of MCS values, e.g., an MCS value between <NUM>-<NUM>, or any other range.

In some demonstrative embodiments, controller <NUM> may be configured to cause a wireless station, for example, a wireless station implemented by device <NUM>, to generate a frame including a header and a data portion. For example, controller <NUM> may cause message processor <NUM> to generate the frame.

In some demonstrative examples, the header of the frame may include an MCS value of an OFDM PHY scheme or an LPSC PHY scheme.

In some demonstrative examples, the frame may include an OFDM frame, e.g., having a frame structure of <FIG>. According to these embodiments, the header of the frame, e.g., header <NUM> (<FIG>), may include an MCS field, e.g., MCS field <NUM> (<FIG>), having an MCS value of an OFDM PHY scheme, e.g., as described below.

In some demonstrative examples, the frame may include an LPSC frame, having an LPSC frame structure, e.g., in accordance with the frame structure of <FIG>. According to these embodiments, the header of the frame, e.g., header <NUM> (<FIG>), may include an MCS field, e.g., MCS field <NUM> (<FIG>), having an MCS value of an LPSC PHY scheme, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to modulate and encode the header according to a SC PHY scheme, for example, using a modulation and encoding scheme of a SC PHY header.

In some demonstrative examples, the frame may include an OFDM frame, e.g., having a frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the header of the frame, e.g., header <NUM> (<FIG>), according to the SC PHY scheme, e.g., as described below.

In some demonstrative examples, the frame may include an LPSC frame, having an LPSC frame structure, e.g., in accordance with the frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the header of the frame, e.g., header <NUM> (<FIG>), according to the SC PHY scheme, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to modulate and encode the data portion according to the OFDM PHY scheme or the LPSC PHY scheme.

In some demonstrative examples, the frame may include an OFDM frame, e.g., having a frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the data portion of the frame, e.g., data portion <NUM> (<FIG>), according to the OFDM PHY scheme, e.g., as described below.

In some demonstrative examples, the frame may include an LPSC frame, having an LPSC frame structure, e.g., in accordance with the frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the data portion the frame, e.g., data portion <NUM> (<FIG>), according to the LPSC PHY scheme, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to process transmission of the frame. For example, controller <NUM> may cause radio <NUM> to transmit the frame.

In some demonstrative examples, controller <NUM> may set the MCS value in the MCS field of the header of frame, for example, based on the PHY scheme to modulate the data portion of the frame, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to set the MCS value, e.g., in MCS field <NUM> (<FIG>), to a value between <NUM> and <NUM>, and to modulate and encode the data portion, e.g., data portion <NUM> (<FIG>), according to the OFDM PHY scheme.

In some demonstrative examples, controller <NUM> may cause the wireless station to set the MCS value, e.g., in MCS field <NUM> (<FIG>), to a value between <NUM> and <NUM>, and to modulate and encode the data portion, e.g., data portion <NUM> (<FIG>), according to the LPSC PHY scheme.

In some demonstrative examples, controller <NUM> may cause the wireless station to process transmission of the header of the frame, e.g., header <NUM> (<FIG>), over a single carrier, and the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a multi-carrier, for example, if the frame is an OFDM frame.

In some demonstrative examples, controller <NUM> may cause the wireless station to process transmission of the header of the frame, e.g., header <NUM> (<FIG>), and the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a single carrier, for example, if the frame is an LPSC frame.

In some demonstrative examples, controller <NUM> may be configured to cause a wireless station, for example, a wireless station implemented by device <NUM>, to process reception of a frame ("the received frame") including a header and a data portion. For example, controller <NUM> may cause radio <NUM> and/or message processor <NUM> to process reception of the frame.

In one example, the received frame may include the frame transmitted by device <NUM>.

In some demonstrative examples, the header of the received frame may include an MCS value of an OFDM PHY scheme or an LPSC PHY scheme.

In some demonstrative examples, the received frame may include an OFDM frame, e.g., having a frame structure of <FIG>. According to these embodiments, the header of the received frame, e.g., header <NUM> (<FIG>), may include an MCS field, e.g., MCS field <NUM> (<FIG>), having an MCS value of an OFDM PHY scheme, e.g., as described below.

In some demonstrative examples, the received frame may include an LPSC frame, having an LPSC frame structure, e.g., in accordance with the frame structure of <FIG>. According to these embodiments, the header of the received frame, e.g., header <NUM> (<FIG>), may include an MCS field, e.g., MCS field <NUM> (<FIG>), having an MCS value of an LPSC PHY scheme, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to demodulate and decode the header of the received frame according to a SC PHY scheme.

In some demonstrative examples, the received frame may include an OFDM frame, e.g., having a frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to demodulate and decode the header of the received frame, e.g., header <NUM> (<FIG>), according to the SC PHY scheme, e.g., as described below.

In some demonstrative examples, the received frame may include an LPSC frame, having an LPSC frame structure, e.g., in accordance with the frame structure of <FIG>. According to these embodiments, controller <NUM> may cause the wireless station to demodulate and decode the header of the frame, e.g., header <NUM> (<FIG>), according to the SC PHY scheme, e.g., as described below.

In some demonstrative examples, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame, for example, based on the MCS value in the header portion of the received frame.

In some demonstrative examples, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame according to the OFDM PHY scheme or the LPSC PHY scheme, for example, based on the MCS value in the header portion of the received frame.

In some demonstrative examples, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame, e.g., data portion <NUM> (<FIG>), according to the OFDM PHY scheme, for example, when the MCS value, e.g., in MCS field <NUM> (<FIG>), is between <NUM> and <NUM>.

In some demonstrative examples, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame, e.g., data portion <NUM> (<FIG>), according to the LPSC PHY scheme, for example, when the MCS value, e.g., in MCS field <NUM> (<FIG>), is between <NUM> and <NUM>.

In some demonstrative examples, controller <NUM> may cause the wireless station to process reception of the header of the frame, e.g., header <NUM> (<FIG>), over a single carrier, and the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a multi-carrier.

In some demonstrative examples, controller <NUM> may cause radio <NUM> to process reception of the data portion of the received frame over a multi-carrier, for example, if the MCS value in the header portion of the received frame is an MCS value of an OFDM PHY scheme, e.g., an MCS value between <NUM> and <NUM>.

In some demonstrative examples, controller <NUM> may cause the wireless station to process reception of the header of the received frame, e.g., header <NUM> (<FIG>), and the data portion of the received frame, e.g., data portion <NUM> (<FIG>), over a single carrier, for example, if the frame is an LPSC frame.

In some demonstrative examples, controller <NUM> may cause radio <NUM> to process reception of the data portion of the received frame over a single-carrier, for example, if the MCS value in the header portion of the received frame is an MCS value of an LPSC PHY scheme, e.g., an MCS value between <NUM> and <NUM>.

In some demonstrative examples, the processing in the PHY layer of a device receiving a frame ("the receiving device"), e.g., device <NUM>, may be pipelined. Accordingly, by the time the header of the received frame is decoded by the receiving device, the receiving device may have already started processing of a next symbol of the frame. The next symbol may be different for OFDM and SC, e.g., even in an initial time domain processing.

In some demonstrative examples, device <NUM> may be configured to possibly add one or more dummy elements, e.g., one dummy element, two dummy elements or more than two dummy elements, for example, following the header of the frame, e.g., before a "real" data element of the data portion of the frame.

In some demonstrative examples, the one or more dummy elements may include one or more OFDM symbols, for example, if the frame is an OFDM frame.

For example, controller <NUM> may cause message processor <NUM> to add one or more OFDM symbols, e.g., one or more dummy OFDM symbols, for example, following header portion <NUM> (<FIG>), e.g., before the data symbols <NUM> (<FIG>) of data portion <NUM> (<FIG>), for example, when processing transmission of an OFDM frame.

In some demonstrative examples, the one or more dummy elements may include one or more LPSC blocks, for example, if the frame is an LPSC frame.

For example, controller <NUM> may cause message processor <NUM> to add one or more LPSC blocks, e.g., one or more dummy LPSC blocks, for example, following header portion <NUM> (<FIG>), e.g., before the data blocks <NUM> (<FIG>) of data portion <NUM> (<FIG>), for example, when processing transmission of an LPSC frame.

In some demonstrative embodiments, the dummy elements may allow the device receiving the frame, for example, to decode the header portion of the received frame, e.g., before the first "real" data symbol or block is to be processed.

In some demonstrative embodiments, devices <NUM>, <NUM> and/or <NUM> may be configured to communicate frames including a header, which may be modulated and encoded according to the SC PHY scheme, and may include the MCS value of the OFDM PHY scheme or the LPSC PHY scheme, e.g., as described above.

In some demonstrative embodiments, devices <NUM> and/or <NUM> may be configured to communicate frames having first and second headers, e.g., as described below.

In some demonstrative embodiments, device <NUM> may be configured to use a legacy, conventional or current SC header ("the first header") to "spoof" a SC device, e.g., device <NUM>, to correct the right length for a packet, e.g., an OFDM packet or an LPSC packet.

In some demonstrative embodiments, device <NUM> may be configured to add another header ("the second header"), e.g., immediately following the first header, with "correct" OFDM or LPSC information, e.g., as described below.

In some demonstrative embodiments, the second header may be configured to be processed, for example, by a device, e.g., device <NUM>, which may be configured to support OFDM PHY and/or LPSC PHY, e.g., as described below.

In some demonstrative embodiments, device <NUM> may be configured to generate and transmit a frame having the SC header ("the first header") followed by an additional header ("the second header"), e.g., configured for OFDM and/or LPSC.

<FIG> is a schematic block diagram illustration a frame structure of a frame <NUM> including two headers, in accordance with some demonstrative embodiments. In some demonstrative embodiments, device <NUM> (<FIG>) may be configured to generate and transmit a frame, e.g., an OFDM frame or an LPSC frame, having the frame structure of <FIG>, and/or device <NUM> (<FIG>) may be configured to process reception of a frame, e.g., and OFDM frame of an LPSC frame, having the frame structure of <FIG>, e.g., as described below.

In some demonstrative embodiments, as shown in <FIG>, frame <NUM> may include a short training field <NUM>, a CE field <NUM>, a first header field <NUM>, a second header field <NUM>, a data portion <NUM>, an Automatic Gain Control (AGC) field <NUM>, and/or a Training (TRN) field <NUM>.

In some demonstrative embodiments, as shown in <FIG>, data portion <NUM> may include a plurality of OFDM symbols <NUM>, e.g., if frame <NUM> is an OFDM frame.

In other embodiments, data portion <NUM> may include a plurality of data blocks (not shown), e.g., if frame <NUM> is an LPSC frame.

In some demonstrative embodiments, the first header <NUM> may be configured to have a structure, which may be in accordance with a header of a SC frame.

In some demonstrative embodiments, first header <NUM> may include a length field <NUM>, which may include a first length value, and an MCS field <NUM>, which may include a first MCS value.

In some demonstrative embodiments, the first header <NUM> may be configured to indicate a mandatory SC MCS value, and a length, which may, for example, cover the second header and one or more additional portions of the frame, e.g., including all additional OFDM symbols of an OFDM frame, or all LPSC blocks of an LPSC frame.

In some demonstrative embodiments, length field <NUM> may include the first length value configured according to a length of the second header <NUM> and the data portion <NUM>.

In some demonstrative embodiments, the MCS field <NUM> may include the first MCS value within a range of MCS values in accordance with a SC PHY scheme. For example, the MCS field <NUM> may include the first MCS value in the range between <NUM> and <NUM>.

In some demonstrative embodiments, the first header <NUM> may include an indication <NUM> of the second header <NUM>.

In some demonstrative embodiments, indication <NUM> may be in the form of a bit of one of the reserved bits in a SC header or any other indication or bit, to indicate that the second header <NUM> follows the first header <NUM>. For example, controller <NUM> (<FIG>) may set a reserved bit in header <NUM> to a predefined value, e.g., one, to indicate presence of the second header <NUM>.

In some demonstrative embodiments, the second header <NUM> may include a length field <NUM>, which may include a second length value, and an MCS field <NUM>, which may include a second MCS value. The second header <NUM> may optionally include one or more additional fields, e.g., one or more OFDM or LPSC fields.

In some demonstrative embodiments, MCS field <NUM> may include an MCS value corresponding to an MCS to be applied to the data portion <NUM>.

In some demonstrative embodiments, MCS field <NUM> may include an MCS value of the OFDM PHY scheme ("OFDM MCS"), e.g., an MCS value between <NUM> and <NUM>, for example, if data portion <NUM> is to be modulated and encoded according to an OFDM PHY scheme, e.g., if the frame is an OFDM frame.

In some demonstrative embodiments, MCS field <NUM> may include an MCS value of the LPSC PHY scheme ("LPSC MCS value"), e.g., an MCS value between <NUM> and <NUM>, for example, if data portion <NUM> is to be modulated and encoded according to an LPSC PHY scheme, e.g., if the frame is an LPSC frame.

In some demonstrative embodiments, the length field <NUM> may include an indication of the actual length of the frame.

In some demonstrative embodiments, the length field <NUM> may include the second length value configured, for example, according to at least a length of the data portion <NUM>.

In some demonstrative embodiments, the first MCS value in the MCS field <NUM> of the first header may be set, for example, to indicate whether or not the frame <NUM> is an OFDM frame or an LPSC frame.

In one example, controller <NUM> (<FIG>) may set the first MCS value in the MCS field <NUM> of the first header <NUM> to a first value, for example, "<NUM>", to indicate the frame is an OFDM frame.

In another example, controller <NUM> (<FIG>) may set the first MCS value in the MCS field <NUM> of the first header <NUM> to a second value, for example, "<NUM>", to indicate the frame is an LPSC frame.

In some demonstrative embodiments, setting the MCS value in the first header <NUM> to indicate whether the frame <NUM> is an OFDM frame or an LPSC frame may enable, for example, to provide an early indication of the frame type to a device receiving the frame <NUM>, e.g., device <NUM> (<FIG>). The device receiving the packet, e.g., device <NUM> (<FIG>), may be able to use this indication, for example, to prepare for the demodulation and/or decoding of the symbols or bits following the header <NUM>.

In some demonstrative embodiments, setting the MCS value in the first header <NUM> to an MCS value according to a SC PHY scheme, e.g., a value between <NUM> and <NUM>, may have an advantage, for example, of allowing some devices, for example, legacy devices, e.g., device <NUM>, already in the market, to support demodulating and/or decoding the length of OFDM and/or LPSC packets. For example, otherwise, these devices may interpret a header with an OFDM or LPSC MCS as an illegal SC header, and may drop the packet including frame <NUM>.

In some demonstrative embodiments, the first length value, which may be included in the length field <NUM>, may include a number of SC blocks corresponding at least to the length of the second header <NUM> and the data portion <NUM>, e.g., as described below.

In some demonstrative embodiments, controller <NUM> (<FIG>) may be configured to determine the first length value, denoted Length, to be included in the length field <NUM> of the first header <NUM>, for example, based on a length of data portion <NUM>, denoted Tdata.

For example, controller <NUM> (<FIG>) may be configured to determine the length Tdata e.g., as Tdata=NSYM*TSYM, for example, wherein NSYM denotes a number of symbols in the frame <NUM>, and TSYM denotes a length of a symbol.

In some demonstrative embodiments, device <NUM> may determine the value Length, for example, as follows: <MAT> wherein TBLK denotes a time of a single SC block, e.g., <NUM>/<NUM> microseconds (usecs), wherein TheaderSC denotes a duration of a SC header, and wherein TGI denotes a Guard Interval duration, e.g., in accordance with an IEEE <NUM> standard, e.g., IEEE <NUM>. 11ad-<NUM> or any other Specification or protocol.

In some demonstrative embodiments, the second header <NUM> may be encoded and/or modulated, for example, in the same way as the first header <NUM>.

In some demonstrative embodiments, the first header <NUM> and the second header <NUM> may be modulated and encoded according to a SC PHY scheme.

In one example, the first header <NUM> ("SC header") may include at least one or more of the following fields:.

In one example, the second header <NUM>, e.g., an "OFDM header" for an OFDM packet, may follow the first header <NUM>, e.g., the header of Table <NUM>, and may include at least one or more of the following fields:.

In some demonstrative embodiments, the header <NUM> and/or the header <NUM> may include any other additional or alternative field and/or parameters.

In some demonstrative embodiments, the header modulation of the SC header <NUM> may include transmitting the header block <NUM> twice, while the second header <NUM>, e.g., the new header, may be transmitted, for example, only once.

Referring back to <FIG>, in some demonstrative embodiments, controller <NUM> may be configured to cause a wireless station, for example, a wireless station implemented by device <NUM>, to generate a frame including first and second headers, e.g., in accordance with the structure of frame <NUM> (<FIG>). For example, controller <NUM> may cause message processor <NUM> to generate the frame.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to generate a frame, e.g., frame <NUM> (<FIG>) including at least a CE field, e.g., CE field <NUM> (<FIG>), a first header, e.g., header <NUM> (<FIG>), a second header, e.g., header <NUM> (<FIG>), and a data portion, e.g., data portion <NUM> (<FIG>).

In some demonstrative embodiments, the first header may include an indication of the second header, e.g., indication <NUM> (<FIG>).

In some demonstrative embodiments, the first header may include a first length value, e.g., in the length field <NUM> (<FIG>), configured according to a length of the second header and the data portion.

In some demonstrative embodiments, the first length value may include a number of SC blocks corresponding to the length of at least the second header and the data portion, e.g., according to Equation <NUM>.

In some demonstrative embodiments, the first header may include a first MCS value, e.g., in the MCS field <NUM> (<FIG>).

In some demonstrative embodiments, the second header may include a second length value, e.g., in the length field <NUM> (<FIG>), which may be configured according to a length of the data portion.

In some demonstrative embodiments, the second header may include a second MCS value, e.g., in the MCS field <NUM> (<FIG>).

In some demonstrative embodiments, the first MCS value may include a value in a range of MCS values of a SC PHY scheme, for example, a value between <NUM> and <NUM>.

In some demonstrative embodiments, controller <NUM> may set the MCS value in the MCS field, e.g., MCS field <NUM> (<FIG>), of the second header, e.g., header <NUM> (<FIG>), according to a modulation and coding scheme to be applied to the data portion, e.g., data portion <NUM> (<FIG>).

In some demonstrative embodiments, the second MCS value may include a value in a range of MCS values of an OFDM PHY scheme, e.g., a value between <NUM> and <NUM>, for example, if the data portion is to be modulated and encoded according to an OFDM PHY scheme.

In some demonstrative embodiments, the second MCS value may include a value in a range of MCS values of an LPSC PHY scheme, e.g., a value between <NUM> and <NUM>, for example, if the data portion is to be modulated and encoded according to an LPSC PHY scheme.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to modulate and encode the CE field, the first header, and the second header according to a SC PHY scheme. For example, controller <NUM> may cause the wireless station to modulate and encode CE field <NUM> (<FIG>), header <NUM> (<FIG>), and header <NUM> (<FIG>) according to the SC PHY scheme.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to modulate and encode the data portion according to the OFDM PHY scheme or the LPSC PHY scheme.

In some demonstrative embodiments, the frame may include an OFDM frame. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the data portion of the frame, e.g., data portion <NUM> (<FIG>), according to the OFDM PHY scheme.

In some demonstrative embodiments, the frame may include an LPSC frame, having an LPSC frame structure. According to these embodiments, controller <NUM> may cause the wireless station to modulate and encode the data portion the frame, e.g., data portion <NUM> (<FIG>), according to the LPSC PHY scheme, e.g., as described below.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to process transmission of the frame. For example, controller <NUM> may cause radio <NUM> to transmit the frame.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to process transmission of the first and/or second headers of the frame, e.g., header <NUM> (<FIG>) and header <NUM> (<FIG>), over a single carrier, and/or the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a multi-carrier, for example, if the frame is an OFDM frame.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to process transmission of the first and/or second headers of the frame, e.g., header <NUM> (<FIG>) and header <NUM> (<FIG>), and/or the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a single carrier, for example, if the frame is an LPSC frame.

In some demonstrative embodiments, controller <NUM> may be configured to cause a wireless station, for example, a wireless station implemented by device <NUM>, to process reception of a frame ("the received frame") including first and second headers and a data portion, e.g., according to the structure of frame <NUM> (<FIG>). For example, controller <NUM> may cause radio <NUM> and/or message processor <NUM> to process reception of the frame.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to demodulate and decode the CE field, e.g., CE field <NUM> (<FIG>), the first header, e.g., header <NUM> (<FIG>), and/or the second header, e.g., header <NUM> (<FIG>), according to a SC PHY scheme.

In some demonstrative embodiments, the second header of the received frame, e.g., header <NUM> (<FIG>), may include an MCS value of an OFDM PHY scheme or an LPSC PHY scheme, e.g., in MCS field <NUM> (<FIG>).

In some demonstrative embodiments, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame according to the OFDM PHY scheme or the LPSC PHY scheme, for example, based on the second MCS value in the second header portion of the received frame, e.g., the MCS value in MCS field <NUM> (<FIG>).

In some demonstrative embodiments, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame, e.g., data portion <NUM> (<FIG>), according to the OFDM PHY scheme, for example, when the MCS value, e.g., in MCS field <NUM> (<FIG>), is between <NUM> and <NUM>.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to demodulate and decode the data portion of the received frame, e.g., data portion <NUM> (<FIG>), according to the LPSC PHY scheme, for example, when the MCS value, e.g., in MCS field <NUM> (<FIG>), is between <NUM> and <NUM>.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to process reception of the first and/or second headers of the frame, e.g., headers <NUM> and <NUM> (<FIG>), over a single carrier, and/or the data portion of the frame, e.g., data portion <NUM> (<FIG>), over a multi-carrier.

In some demonstrative embodiments, controller <NUM> may cause radio <NUM> to process reception of the data portion of the received frame over a multi-carrier, for example, if the MCS value in the second header of the received frame, e.g., the MCS value in MCS field <NUM> (<FIG>), is an MCS value of an OFDM PHY scheme, e.g., an MCS value between <NUM> and <NUM>.

In some demonstrative embodiments, controller <NUM> may cause the wireless station to process reception of the first and/or second headers of the frame, e.g., headers <NUM> and <NUM> (<FIG>), and/or the data portion of the received frame, e.g., data portion <NUM> (<FIG>), over a single carrier, for example, if the frame is an LPSC frame.

In some demonstrative embodiments, controller <NUM> may cause radio <NUM> to process reception of the data portion of the received frame over a single-carrier, for example, if the MCS value in the second header of the received frame, e.g., the MCS value in MCS field <NUM> (<FIG>), is an MCS value of an LPSC PHY scheme, e.g., an MCS value between <NUM> and <NUM>.

In some demonstrative embodiments, another device, e.g., device <NUM>, may be able to demodulate and decode the first header, e.g., header <NUM> (<FIG>), and to determine the duration of the frame, e.g., based on the length indicated by the length field of the first header, e.g., length field <NUM> (<FIG>), for example, even if device <NUM> (<FIG>) is not capable of supporting the OFDM PHY scheme and/or the LPSC PHY scheme.

Reference is made to <FIG>, which schematically illustrates a method of communicating a wireless transmission according to a PHY scheme, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of <FIG> may be performed by one or more elements of a system, e.g., system <NUM> (<FIG>), for example, one or more wireless devices, e.g., device <NUM> (<FIG>) and/or device <NUM> (<FIG>), a controller, e.g., controller <NUM> (<FIG>) and/or controller <NUM> (<FIG>), a radio, e.g., radio <NUM> (<FIG>) and/or radio <NUM> (<FIG>), and/or a message processor, e.g., message processor <NUM> (<FIG>) and/or message processor <NUM> (<FIG>).

As indicated at block <NUM>, the method may include generating a frame including a header and a data portion, the header including an MCS value of an OFDM PHY scheme or an LPSC PHY scheme. For example, controller <NUM> (<FIG>) may cause message processor <NUM> (<FIG>) to generate frame <NUM> (<FIG>) including the MCS value of the OFDM PHY scheme in header <NUM> (<FIG>); or to generate frame <NUM> (<FIG>) including the MCS value of the LPSC PHY scheme in header <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include modulating and encoding the header according to a SC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to modulate and encode the header according to the SC PHY scheme, e.g., as described above.

As indicated at block <NUM>, the method may include modulating and encoding the data portion according to the OFDM PHY scheme or the LPSC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to modulate and encode the data portion according to the OFDM PHY scheme or the LPSC PHY scheme, for example, according to the MCS value, e.g., as described above.

As indicated at block <NUM>, the method may include processing transmission of the frame. For example, For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to process transmission of the frame, e.g., as described above.

As indicated at block <NUM>, the method may include processing reception of the frame. For example, controller <NUM> (<FIG>) may cause message processor <NUM> (<FIG>) to process reception of the frame, e.g., as described above.

As indicated at block <NUM>, the method may include demodulating and decoding the header of the frame according to a SC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to demodulate and decode the header of the frame according to a SC PHY scheme, e.g., as described above.

As indicated at block <NUM>, the method may include demodulating and decoding the data portion of the frame according to the OFDM PHY scheme or the LPSC PHY scheme, e.g., based on the MCS value in the header of the frame. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to demodulate and decode the data portion of the frame according to an OFDM PHY scheme or the LPSC PHY scheme, for example, based on the MCS value in the header of the frame, e.g., as described above.

As indicated at block <NUM>, the method may include generating a frame including a CE field, a first header, a second header, and a data portion, the first header including an indication of the second header, a first length value configured according to a length of the second header and the data portion, and a first MCS value, the second header including a second length value configured according to a length of the data portion, and a second MCS value. For example, controller <NUM> (<FIG>) may cause message processor <NUM> (<FIG>) to generate frame <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include modulating and encoding the CE field, the first header, and the second header according to a SC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to modulate and encode the CE field <NUM> (<FIG>), header <NUM> (<FIG>), and header <NUM> (<FIG>) according to the SC PHY scheme, e.g., as described above.

As indicated at block <NUM>, the method may include modulating and encoding the data portion according to the OFDM PHY scheme or the LPSC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to modulate and encode the data portion <NUM> (<FIG>) according to the OFDM PHY scheme or the LPSC PHY scheme, for example, according to the second MCS value in MCS field <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include processing transmission of the frame. For example, For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to process transmission of frame <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include processing reception of the frame. For example, controller <NUM> (<FIG>) may cause message processor <NUM> (<FIG>) to process reception of the frame <NUM> (<FIG>), e.g., as described above.

As indicated at block <NUM>, the method may include demodulating and decoding the CE field, the first header, and the second header according to a SC PHY scheme. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to demodulate and CE field <NUM> (<FIG>), header <NUM> (<FIG>), and header <NUM> (<FIG>) according to a SC PHY scheme, e.g., as described above.

As indicated at block <NUM>, the method may include demodulating and decoding the data portion of the frame according to the OFDM PHY scheme or the LPSC PHY scheme, e.g., based on the second MCS value in the second header of the frame. For example, controller <NUM> (<FIG>) may cause device <NUM> (<FIG>) to demodulate and decode the data portion <NUM> (<FIG>) of the frame <NUM> (<FIG>) according to an OFDM PHY scheme or the LPSC PHY scheme, for example, based on the MCS value in the MCS field <NUM> (<FIG>), e.g., as described above.

Reference is made to <FIG>, which schematically illustrates a product of manufacture <NUM>, in accordance with some demonstrative embodiments. Product <NUM> may include a non-transitory machine-readable storage medium <NUM> to store logic <NUM>, which may be used, for example, to perform at least part of the functionality of devices <NUM> and/or <NUM> (<FIG>), transmitters <NUM> and/or <NUM> (<FIG>), receivers <NUM> and/or <NUM> (<FIG>), controllers <NUM> and/or <NUM> (<FIG>), message processors <NUM> (<FIG>) and/or <NUM> (<FIG>), and/or to perform one or more operations and/or functionalities, for example, one or more operations of the method of <FIG> and/or <NUM>. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

In some demonstrative embodiments, product <NUM> and/or machine-readable storage medium <NUM> may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine-readable storage medium <NUM> 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), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), 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 floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic <NUM> 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.

In some demonstrative embodiments, logic <NUM> may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

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

Claim 1:
A method to be performed at a wireless communication station supporting directional multi-gigabit (DMG) transmissions according to Single Carrier (SC) physical layer (PHY) and an orthogonal frequency division multiplexing (OFDM) PHY, the method comprising:
generating a frame (<NUM>) to be transmitted by the wireless communication station, wherein in response to the frame being a OFDM frame, the frame (<NUM>) to comprise a data portion to be modulated according to an OFDM PHY scheme and a plurality of fields, the plurality of fields comprising a Short Training Field (<NUM>), STF, a Channel Estimation Field (<NUM>), CEF, a first header (<NUM>), a second header (<NUM>);
wherein the first header (<NUM>) comprises a first indication (<NUM>) to indicate a presence of the second header (<NUM>), a first MCS value in a first MCS field (<NUM>), and a length value in a length field (<NUM>), and wherein the second header (<NUM>) comprises an OFDM header for an OFDM packet including a second MCS value in a second MCS field (<NUM>);
setting the first indication (<NUM>) to indicate a presence of the second header (<NUM>);
setting the first MCS value in accordance with an SC PHY scheme;
setting the length value according to a length of the second header and the data portion;
setting the second MCS value to indicate that the data portion is modulated according to the OFDM scheme;
modulating (<NUM>) the plurality of fields of the frame (<NUM>) according to a Single Carrier, SC, scheme, the plurality of fields comprising the Short Training Field (<NUM>), STF, the Channel Estimation Field (<NUM>), CEF, the first header (<NUM>), and the second header (<NUM>);
modulating (<NUM>) the data portion (<NUM>) of the frame (<NUM>) according to the OFDM scheme, in accordance with the second MCS value; and
transmitting (<NUM>) the frame (<NUM>) via one or more directional links to communicate at a rate of multiple gigabits per second in a frequency band above <NUM> Gigahertz, GHz.