WO2018132126A1

WO2018132126A1 - Beam tracking indication for enhanced directional multi-gigabit single-carrier physical layer protocol data units

Info

Publication number: WO2018132126A1
Application number: PCT/US2017/039847
Authority: WO
Inventors: Claudio Rafael Cunha Monteiro DA SILVA; Carlos Cordeiro; Michael Genossar
Original assignee: Intel IP Corporation
Priority date: 2017-01-13
Filing date: 2017-06-29
Publication date: 2018-07-19
Also published as: DE112017006828T5

Abstract

A wireless communication device, system and method. The device comprises a memory and processing circuitry. The processing circuitry includes logic to encode an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field. A legacy header field L-Header of the legacy preamble and header portion includes a legacy beam tracking request field set to indicate to a legacy device that no beam tracking is requested. An EDMG beam tracking request field of the EDMG preamble and header portion is set to indicate to a peer EDMG wireless communication device that beam tracking is requested. The processing circuitry is to cause transmission of the EDMG SC PPDU, and to cause the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

Description

BEAM TRACKING INDICATION FOR ENHANCED DIRECTIONAL MULTI-GIGABIT SINGLE-CARRIER PHYSICAL LAYER PROTOCOL DATA UNITS

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application is derived from U.S. provisional application serial number 62/445,998, filed January 13, 2017, and claims priority to that date for all applicable subject matter.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to wireless local area networks (network environments) and Wi-Fi networks including networks operating in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards. Some embodiments relate to IEEE 802.1 lay. Some embodiments relate to methods, computer readable media, and apparatus for beam tracking indication for enhanced directional multi-gigabit (EDMG) single-carrier physical layer protocol data units (PPDUs).

BACKGROUND

[0003] Efficient use of the resources of a wireless local-area network (network environment) is important to provide bandwidth and acceptable response times to the users of the network environment. However, often there are many devices trying to share the same resources and some devices may be limited by the communication protocol they use or by their hardware bandwidth. Moreover, wireless devices may need to operate with both newer protocols and with legacy device protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

[0005] Fig. 1 shows an exemplary network environment, in accordance with one or more embodiments;

[0006] Fig. 2 illustrates a functional diagram of an example wireless communication system, such as a wireless communication station (STA) or a wireless access point (AP), in accordance with one or more embodiments of the disclosure

[0007] Fig. 3a illustrates an example of directional multi-gigabit (DMG) single-carrier (SC) PPDU in accordance with IEEE 802.11-2016;

[0008] Fig. 3b illustrates an example of an EDMG SC PPDU, in accordance with some embodiments;

[0009] Fig. 4 illustrates a block diagram of an example machine to perform any one or more of the techniques discussed herein; and

[0010] Fig. 5 shows a flow diagram of a method according to an embodiment.

DETAILED DESCRIPTION

[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] Example embodiments described herein provide certain systems, methods, and devices, for providing signaling information to Wi-Fi devices in various Wi-Fi networks, including, but not limited to, IEEE 802.1 lad and/or IEEE 802.1 lay (i.e. Next Generation 60 GHz or NG60) using millimeter- Wave (mmWave) communication.

[0013] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0014] A directional multi-gigabit (DMG) communication may involve one or more directional links to communicate at a rate of multiple gigabits per second. An amendment to a DMG operation in a 60 GHz band, such as according to an Institute of Electrical and Electronics Engineers (IEEE) 802. Had standard, is defined, for example, by an IEEE 802.1 lay project (NG60 project). EDMG compliant devices may provide a maximum throughput of at least 20 gigabits per second (measured at the Medium Access Control (MAC) data service access point), while maintaining or improving the power efficiency per station. EDMG operation is typically on license-exempt bands above 45 GHz, such as, for example, 60 GHz. Stations (STAs) devices in compliance with 802.1 lay may be termed enhanced DMG STAs (EDMG STAs) or EDMG devices. It is to be noted that "STA" as used herein may sometimes be used to refer among other things to a user device or to an access point (AP). In some demonstrative embodiments, one or more STAs may be configured to communicate over an EDMG basic service set (EDMG BSS), and/or any other network. In some scenarios, an EDMG STA may have reciprocal EDMG antennas. Hereinafter, DMG is meant to refer to devices, or networks, such as BSS', compliant with 802. Had or 802.11- 2016, and EDMG will be used to refer to devices, or networks such BSS' compliant with 802. Hay.

[0015] An EDMG STA may further support 2.16 GHz and 4.32 GHz contiguous channel widths, single spatial stream communication for both transmitting and receiving in all supported channel widths, and/or non-EDMG duplicate format transmission. In addition, an EDMG STA may further support two or more spatial stream communication for both transmitting and receiving using SC or OFDM modulations, EDMG MU PPDUs on transmitting and receiving using SC or OFDM modulations, non-contiguous channel widths of 2.16+2.16 GHz or of 4.32+4.32 GHz, channel widths of 6.48 GHz or 8.64 GHz, a 64 point non-uniform constellation, and/or channel-wise downlink (DL) frequency division multiple access (FDMA), for example where an EDMG PCP or EDMG AP may simultaneously transmit to multiple EDMG STAs allocated to different channels.

[0016] Fig. 1 illustrates a network environment 100 in accordance with some embodiments. The network environment may comprise a basic service set (BSS) or personal BSS (PBSS) that may include a master station 102, which may be an access point (AP) or PBSS control point (PCP), a plurality of wireless (e.g., IEEE 802.1 lay) STAs or devices 104 and a plurality of legacy (e.g., IEEE 802.11n/ac/ad) STAs or devices 106. STAs 104 may include EDMG devices, and STAs 106 may include DMG devices.

[0017] The master station 102 may be an AP configured to transmit and receive in accordance with one or more IEEE 802.11 communication protocols, such as IEEE 802.11-2016 and IEEE 802. Hay. In some embodiments, the master station 102 may be a base station. The master station 102 may be part of a PBSS. The master station 102 may use other communications protocols as well as the IEEE 802.11 protocol. The IEEE 802.11 protocol may include using single-carrier (SC) modulation, orthogonal frequency division multiple- access (OFDMA), time division multiple access (TDMA), and/or code division multiple access (CDMA). The IEEE 802.11 protocol may include a multiple access technique. For example, the IEEE 802.11 protocol may include code division multiple access (CDMA), space-division multiple access (SDMA), multiple-input multiple-output (MIMO), multi-user (MU) MIMO (MU-MIMO), and/or single-input single-output (SISO). The master station 102 and/or wireless STAs 104 may be configured to operate in accordance with 802.1 lay or Next Generation 60 (NG60), Wi-Fi Gigabyte (WiGig).

[0018] The wireless STAs 104 and 106 may be wireless transmit and receive devices such as a cellular telephone, smart telephone, handheld wireless device, wireless glasses, wireless watch, wireless personal device, tablet, or another device that may be transmitting and receiving using the IEEE 802.11 protocol and possibly one or more other wireless communication protocols. In some embodiments, the wireless STAs 104 or 106 may operate in accordance with IEEE 802.1 lax, although, for purposes of the instant description, STAs 106 will still be referred to as legacy STAs because they are DMG compliant and not EDMG compliant STAs. The STAs 104 and/or master station 102 may be part of a BSS and may also operate in accordance with IEEE 802. Hay where one of the STAs 104 and/or master station 102 takes the role of the Priority Control Point (PCP).

[0019] The master station 102 may communicate with legacy devices 106 in accordance with legacy IEEE 802.11 communication techniques using frequencies in license-exempt bands above 45 GHz, such as, for example, 60 GHz. In example embodiments, the master station 102 may also be configured to communicate with wireless STAs 104 in accordance with legacy IEEE 802.11 communication techniques. The master station 102 may use techniques of 802. Had for communication with legacy devices 106. The master station 102 and/or STA 104 may be a personal basic service set (PBSS) Control Point (PCP) which can be equipped with large aperture antenna array or Modular Antenna Array (MAA). [0020] The master station 102 and/or STAs 104 may be equipped with more than one antenna. Each of the antennas of master station 102 or STA 104 may be a phased array antenna with many elements. In some embodiments, an IEEE 802. Hay wireless communication frame may be configurable to have the same bandwidth as a channel. In some embodiments, the master station 102 and/or STAs 104 may be equipped with one or more EDMG antennas, which may include multiple radio-frequency baseband (RF-BB) chains. The master station 102 and/or STAs 104 may be configured to perform beamforming and may each have an antenna weight vector associated with one or more antennas. In some embodiments, the master station 102 and/or STAs 104 may be a EDMG master station 102 or an EDMG STA 104, respectively. In some embodiments, the master station 102 and/or STA 104 may transmit a frame, such as a PPDU.

[0021] An IEEE 802.1 lay frame may be configured for transmitting a number of spatial streams, which may be in accordance with a multi-user (MU) Multiple-Input Multiple-Output (MEVIO) or MU-MIMO scheme. In other embodiments, the master station 102, wireless STAs 104, and/or legacy device 106 may also implement different technologies such as code division multiple access (CDMA) 2000, CDMA 2000 IX, CDMA 2000 Evolution-Data Optimized (EV-DO), Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Long Term Evolution (LTE), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), BlueTooth®, or other technologies.

[0022] In accordance with some IEEE 802. Hay embodiments, a master station 102 may operate as a master station which may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium, which may be termed a transmission opportunity (TxOP) for performing beamforming training for a multiple access technique such as OFDMA or MU-MIMO. In some embodiments, the multiple-access technique used during a TxOP may be a scheduled OFDMA technique, although this is not a requirement. In some embodiments, the multiple access technique may be a space-division multiple access (SDMA) technique. In some embodiments, a single-carrier (SC) modulation technique may be used.

[0023] The master station 102 may communicate with legacy STAs 106 and/or with STAs 104 in accordance with legacy IEEE 802.11 communication techniques. In example embodiments, the STAs 104 and/or the master station 102 may be configured to perform the methods and operations herein described in conjunction with Figs. 1-5 as will be described in further detail below.

[0024] A procedure in IEEE 802.1 lad and/or IEEE 802.11-2016 (which subsumes IEEE 802.1 lad) to allow beam tracking requests cannot be valid in an EDMG or IEEE 802. Hay (EDMG) environment in the single-carrier mode as will be described further below. Therefore, a new procedure may be used to enable an EDMG wireless communication device to request receive and/or transmit beam tracking when using EDMG single-carrier PPDUs.

[0025] In some embodiments, systems/devices/methods described herein may allow an EDMG wireless communication device to request a peer EDMG wireless communication device to perform receive and/or transmit beam tracking by way of a new beam tracking request field in the EDMG-Header-A field of an EDMG single-carrier (SC) PPDUs. In some embodiments, systems/devices/methods described herein further define settings for other fields used in the EDMG portion of the SC PPDU to allow beam tracking. Until the instant disclosure, there have been no known solutions for allowing a beam tracking indication for EDMG wireless communication devices when using the single carrier mode.

[0026] Fig. 2 shows a functional diagram of an exemplary wireless communication system 200 in accordance with some embodiments. In one embodiment, Fig. 2 illustrates a functional block diagram of a wireless communication system that may be suitable for use as an EDMG master station 102 (Fig. 1) or an EDMG STA 104 (FIG. 1) in accordance with some embodiments. The wireless communication system 200 may also be suitable for use as a handheld device, mobile device, cellular telephone, smartphone, tablet, netbook, wireless terminal, laptop computer, wearable computer device, femtocell, High Data Rate (HDR) subscriber station, access point, access terminal, or other personal communication system (PCS) device.

[0027] The wireless communication system 200 may include radio IC circuitry 202 and a front-end module (FEM) 210 for transmitting and receiving signals to and from other communication stations using one or more antennas 201. The FEM 210 may include a receive signal path comprising circuitry configured to operate on signals above 45 GHz, such as 60 GHz signals by way of example, received from one or more antennas 201, to amplify the received signals and to provide the amplified versions of the received signals to the radio IC circuitry 202 for further processing. FEM 210 may also include a transmit signal path which may include circuitry configured to amplify signals provided by the radio IC circuitry 202 for wireless transmission by one or more of the antennas 201. Radio IC 202 may include a receive signal path which may include circuitry to down-convert signals received from the FEM circuitry 210 and provide baseband signals to a baseband processor 209. The radio IC circuitry 202 may also include a transmit signal path which may include circuitry to up- convert baseband signals provided by the baseband processor 209 and provide RF output signals to the FEM circuitry 210 for subsequent wireless transmission by the one or more antennas 201. Baseband processor 209 may include a memory 212, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the baseband processor 209. The memory 212 in baseband processor 209 may further including stored software and/or firmware for allowing the baseband processor to perform MAC and PHY operations, such as those described herein. Baseband processor 209 may further including processing circuitry 214 that may include control logic to process the signals received from the receive signal path of the radio IC circuitry 202. Baseband processor 209 is also configured to also generate corresponding baseband signals for the transmit signal path of the radio IC circuitry 202, and may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with an application processor 206 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 202. In some embodiments, the system 200 and/or the baseband processor 209 may be configured to perform operations detailed herein.

[0028] In accordance with some embodiments, the baseband processor 209 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The wireless communication system 200 may be arranged to transmit and receive signals, the signals being caused to be transmitted or received by the baseband processor 209 and/or application processor 206. In some embodiments, baseband processor 209 and application processor 206 of the communication system 200 may each include one or more processors. In other embodiments, two or more antennas 201 may be coupled to the FEM 210 arranged for sending and receiving signals. The memory 208 and/or memory 212 may store information for configuring the application processor 206 and/or baseband processor 209 to perform operations for configuring and causing transmission or reception of message frames and performing the various operations described herein. The memory 208 or 212 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 208 or 212 may include a computer-readable storage device may, read-only memory (ROM), random- access memory (RAM), magnetic disk storage media, optical storage media, flash- memory devices and other storage devices and media. [0029] In some embodiments, wireless communication system 200 may be part of a portable wireless communication apparatus, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[0030] In some embodiments, the wireless communication system 200 may include one or more antennas 201. The antennas 201 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

[0031] In some embodiments, the communication system 200 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0032] Although wireless communication system 200 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication system 200 may refer to one or more processes operating on one or more processing elements.

[0033] According to embodiments a wireless communication device may include a wireless communication system, for example the system 200 of Fig. 2, or any one or more components of a wireless communication system, such as a baseband processor, a wireless circuit card, a wireless integrated circuit, to name a few.

[0034] IEEE 802. Had and 802.11-2016 (IEEE Std 802.11™-2016) propose a different SC PPDU format than that proposed to be used in 802.1 lay. Reference will now be made to Figs. 3a and 3b in order to showcase these differences. It is to be noted that neither of the figures, including Figs. 3a and 3b, are necessarily drawn to scale with respect to the frequency domain or the time domain, that the various fields and subfields shown may or may not be in the order illustrated, may or may not directly follow each other in the manner illustrated, and further that the EDMG SC PPDU may include more fields and subfields, or less fields and subfields than the ones illustrated.

[0035] Fig. 3a illustrates an example of directional multi-gigabit (DMG) single-carrier mode PPDU in accordance with the legacy IEEE 802.11-2016 or 802.1 lad. As seen in Fig. 3a, the structure of the shown DMG SC PPDU 300a includes a short training field (STF) 301a, a channel estimation field (CEF) 303a, a DMG header field 305a, a data field 307 and a training sequences field or training field (TRN) 309. The STF and CEF make up the DMG PPDU preamble, and the header field makes up the DMG PPDU header. The STF provides timing adjustment and automatic gain control adjustment to the receiver; the CEF allows channel estimation at the receiver. The DMG header field 305a provides other information to the receiver to allow the receiver to decode the data portion or payload 307, including for example modulation and coding scheme (MCS) information, information to allow initialization of the receiver decode and scrambler, information on the type of packet being transmitted, and a length of the data portion 307 of the PPDU and of the TRN field 309. In particular, as shown schematically in Fig. 3a, the DMG header 305a may include, among other fields, a length field L 311a, including information on the number of data octets in the physical layer service data unit (PSDU) of the PPDU, a packet type of PT field 313a, a training (TRN) length field TRN-LEN or TRN-L 315a which sets forth information on the length of the training subfields either appended or requested in the PPDU (depending on parameters such as packet type in PT field 313a and in the beam tracking request BTR field 317a), a beam tracking request field (BTR) 317a which allows the receiver to know whether the PPDU is a beam tracking request PPDU, and a MCS field 319a. It is to be noted that DMG header field 305a includes other fields/subfields not expressly called out in this disclosure, as would be recognized by one skilled in the art.

[0036] For a DMG wireless communication system, such as a STA or an AP that operates in accordance with IEEE Std 802.11™-2016 and/or 802. Had, as defined for example in sub- clause or section 10.38.7 of 802.11-2016, a station (beam tracking initiator) may request a peer station (beam tracking responder) to perform receive beam tracking in a specific way, and in particular, by setting, in a transmitted packet, a TXVECTOR parameter BEAM TRACKING REQUEST to beam tracking requested, TRN-LEN to the number of requested TRN units, and packet type to TRN-R-PACKET. A beam tracking responder that receives a packet with the beam tracking request BTR field 317a in the PHY DMG header 305a, equal to 1, and the packet type field PT 313a equal to zero, shall follow the rules described in section 20.10.2.2 of 802.11-2016, and shall include a beam refinement Automatic Gain Control (AGC) field and TRN-R subfields appended to the following packet transmitted to the initiator in the same allocation, with a modulation and coding scheme (MCS) index greater than 0. The value of TRN-LEN in the following packet from the responder to the initiator shall be equal to the value of the TRN-LEN parameter or TRN-L field 315a in the PPDU packet from the initiator.

[0037] Thus, as suggested in the previous paragraph paraphrased from 802.11-2016, a DMG station may request a peer DMG station STA to perform receive beam tracking by doing the following:

(1) setting the beam tracking request field (BTR) 317a in the header 305a to one (to indicate the need for beam tracking);

(2) setting the packet type field PT 313a in the header 305a to zero (to indicate a PPDU that contains a request for a TRN field to be appended to a future response PPDU when the BTR field is set to 1); and

(3) setting the TRN-L field 315a with a value equal to NTRN (denoting the training length value) to the number of requested TRN units.

[0038] Therefore, a DMG PPDU that includes a receive beam tracking request may have a TRN-L field with a value NTRN larger than zero (that is, indicating a positive length for the training field) even though the packet does not contain a training field but is requesting one in a response to the DMG SC PPDU request for receive beam tracking. The above scenario poses a problem with respect to EDMG wireless communication system that aim to be backward compatible with DMG devices, as will be explained further below in relation to Fig. 3b.

[0039] Referring now to Fig. 3b, the figure illustrates an example of an EDMG SC PPDU 300b according to some embodiments. The shown PPDU 300b includes a non-EDMG or legacy preamble and header portion 310 and an EDMG preamble and header portion 312, both followed by a data portion 307 and a training field 309. It is to be noted that, in an EDMG SC PPDU that serves as a request for receive beam tracking, the training field 309 may not be present. The PPDU 300b includes a legacy short training field L-STF 301b, a legacy channel estimation field L-CEF 303b, together making up the legacy preamble portion, and, in addition, a legacy header field L-Header 305b. L-STF, L-CEF and L-Header together make up the non-EDMG/legacy preamble and header portion 310. The EDMG SC PPDU 300b further includes an EDMG preamble and header portion 312, which includes an EDMG Header-A 302, an EDMG-STF 304, an EDMG-CEF 306, and EDMG Header-B 308. Some of the fields in the EDMG preamble and header portion 312 may not be present based on the type of EDMG SC PPDU as would be recognized by a skilled person. The EDMG-Header-A, may include, among other fields, an EDMG BTR field 320, an EDMG TRN length field TRN-L 322 and an EDMG length field 324 indicating a length of the PSDU portion of the EDMG PPDU, a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit) 326, along with other fields such as an MCS field, bandwidth and other information (not shown).

[0040] In some embodiments, the L-Header 305b may include one or more of an MCS field 319b, a length field L 311b, a packet type or PT field 313b, a TRN-L field 315b, and a beam tracking field 317b, among other fields which are not shown. The L-Header 305b may contain information on: (1) the number of data octets in the PPDU's PSDU in the length field L 311b, and (2) MCS in the MCS field 319b, which together may determine the length of the data field 307. L-Header 305b may further include the TRN-L field 315b (denoted by NTRN as explained previously) to allow a determination at the receiver of the length of the training (TRN) field TRN-L 309. In some embodiments, values may be artificially defined for length field L 311b, MCS field 319b, and TRN-L field 315b in such a way that the values may indicate to a receiver the total duration (TXTIME) of the EDMG SC PPDU. The above artificial setting of values in the L-Header of an EDMG PPDU to enable a DMG station to determine this total duration and set its Network Allocation Vector (NAV) accordingly may be referred to as spoofing.

[0041] However, if an EDMG wireless communication system requests receive beam tracking using the same procedure adopted in 802.1 lad and/or 802.11-2016 and outlined above, the beam tracking request field BTR 317b would be set to one and PT 313b could be set to zero to indicate that receive beam tracking is requested. However, where the BTR 317b is set to one and the PT 313b is set to zero, a DMG STA receiving the legacy header automatically disregard value in the TRN-L 315b in determining the length of the EDMG SC PPDU, because it would believe that using the value in the TRN-L 315b would not be necessary to determine the EDMG SC PPDU's length (since, in receive beam tracking requests, a TRN field may not be present, but only requested, and also since the TRN-L 315b in L-Header would merely be a value that the DMG would need to use to determine the actual length of the EDMG SC PPDU). In other words, DMG STAs that receive the PPDU would assume that the PPDU does not contain a training field (because they would take NTRN signaled in the L- Header to be a requested value, and not the number of TRN units present in the received PPDU). However, in order for spoofing to work for DMG devices, the field values in the L- Header, such as values indicated by L 31 lb, MCS 319b and TRN-L 315b would all need to be used to determine the EDMG SC PPDU length. If the TRN-L 315b is ignored, the spoofed length determination would be inaccurate at a DMG device. In this way, a DMG device would incorrectly estimate the packet's duration, as spoofing would have failed at the DMG legacy receivers, leading to undesired interference and a degradation in network performance.

[0042] In order to allow backward compatibility of EDMG wireless communication system with DMG wireless communication system, the L-Header of an EDMG PPDU may include information regarding a total length/time duration of the EDMG PPDU so that DMG stations are able to back off their transmissions based on a decoding of the information in the L- Header field. This is because DMG wireless communication systems would be able to correctly process or decode the legacy preamble and L-Header of an EDMG PPDU, since the definition of these two fields is identical to the preamble and Header fields of a DMG PPDU as explained with respect to Fig. 3a, but would not be able to correctly process the EDMG preambles, headers and data field of an EDMG PPDU, which they would not need to process, as the EDMG PPDU is not addressed to them. However, we would still need to signal requests for beam tracking.

[0043] In view of the above, some embodiments pertain to a novel mechanism to enable EDMG wireless communication systems, such as EDMG wireless communication system 200 of Fig. 2, to request receive beam tracking by providing the EDMG beam tracking request field EDMG BTR field 320 (Fig. 3b) in the EDMG preamble and header portion 312, such as in the EDMG-Header-A 302 of the EDMG SC PPDU, and further by setting the beam tracking request field BTR 317b within the L-Header of the EDMG SC PPDU to a value that would indicate to a DMG or legacy wireless communication system that no beam tracking is requested, such as to a value of zero. In this manner, an EDMG receiver according to embodiments may determine, by decoding the EDMG Header- A portion 302, and specifically the EDMG BTR 320, that receive beam tracking for the EDMG wireless communication system sending the EDMG SC PPDU would be needed, while a DMG wireless communication system may be able to defer transmissions for the duration of the EDMG SC PPDU by being able to correctly decode the length of the EDMG SC PPDU by decoding the L-Header 305b of the EDMG SC PPDU. Thus, a new field according to embodiments may be placed in the EDMG portion of the EDMG SC PPDU, and currently does not exist in the specification draft IEEE P802.1 lay/DO.1, January 2017.

[0044] According to some embodiments, by making use of an EDMG BTR 320 in the EDMG portion of an EDMG SC PPDU, an EDMG wireless communication system such as a STA or an AP may request a peer EDMG wireless communication system to perform receive beam tracking by setting the following in a transmitted packet:

1) an EDMG BTR 320 in the EDMG-Header-A 302 being set to indicate that beam tracking is requested, such as by being set to indicate a value equal to 1;

2) a TRN LEN or TRN-L 322 in the EDMG-Header-A being set to indicate the number of requested training units in the EDMG PPDU response to the request for receive beam tracking;

3) a packet type field PT 313b in the L-Header 305b being set to indicate a PPDU that contains a request for a TRN field to be appended to a future response PPDU, for example being set to indicate a value equal to zero (TRN-R-PACKET); and

4) a "RX TRN-Units per Each TX TRN-Unit" field 326 in the EDMG-Header-A 302 being set to indicate a value equal to zero.

[0045] According to some embodiments, by making use of an EDMG BTR 320 in the EDMG portion of an EDMG SC PPDU, an EDMG wireless communication system such as a STA or an AP may request a peer EDMG wireless communication system to perform transmit beam tracking by setting the following in a transmitted packet:

2) a TRN LEN or TRN-L 322 in the EDMG-Header-A being set to indicate the number of appended TRN units in the EDMG SC PPDU;

3) a packet type field PT 313b in the L-Header 305b being set to indicate a PPDU that contains a TRN field, for example being set to indicate a value equal to one (TRN-T- PACKET); and

4) "RX TRN-Units per Each TX TRN-Unit" field 326 in the EDMG-Header-A 302 being set to indicate a value equal to zero. [0046] In addition, in some embodiments, an EDMG wireless communication system may request a peer EDMG wireless communication system to perform transmit (e.g. initiator) and receive (e.g. responder) beam tracking by setting the following in a transmitted packet:

3) a packet type field PT 313b in the L-Header 305b being set to indicate a PPDU that contains a TRN field, for example being set to indicate a value equal to 1; and

4) "RX TRN-Units per Each TX TRN-Unit" field 326 in the EDMG-Header-A 302 being set to indicate a value greater than zero (TRN-T/R-PACKET).

[0047] In all three embodiments above, as previously described, the BTR 317b in the L- Header 305b is equal to zero. In this way, a DMG receiver, in response to receiving a request for receive beam tracking, will not disregard the TRN length field in the L-Header of the EDMG SC PPDU (because they would assume that the NTRN signaled in the L-Header is an actual value rather than a requested value) and will therefore correctly estimate the packet' s duration using TRN LEN or TRN-L 315b in the L-Header 305b.

[0048] Fig. 4 illustrates a block diagram of an example machine 400 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. In alternative embodiments, the machine 400 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 400 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 400 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 400 may be a master station 102, HE stations 104, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a portable communications device, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations. [0049] Machine (e.g., computer system) 400 may include a hardware processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 404 and a static memory 406, some or all of which may communicate with each other via an interlink (e.g., bus) 408.

[0050] Specific examples of main memory 404 include Random Access Memory (RAM), and semiconductor memory devices, which may include, in some embodiments, storage locations in semiconductors such as registers. Specific examples of static memory 406 include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Readonly Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0051] The machine 400 may further include a display device 410, an input device 412 (e.g., a keyboard), and a user interface (UI) navigation device 414 (e.g., a mouse). In an example, the display device 410, input device 412 and UI navigation device 414 may be a touch screen display. The machine 400 may additionally include a mass storage (e.g., drive unit) 416, a signal generation device 418 (e.g., a speaker), a network interface device 420, and one or more sensors 421, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 400 may include an output controller 428, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared(IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.). In some embodiments, the processor 402 and/or instructions 424 may comprise processing circuitry and/or transceiver circuitry.

[0052] The storage device 416 may include a machine readable medium 422 on which is stored one or more sets of data structures or instructions 424 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 424 may also reside, completely or at least partially, within the main memory 404, within static memory 406, or within the hardware processor 402 during execution thereof by the machine 400. In an example, one or any combination of the hardware processor 402, the main memory 404, the static memory 406, or the storage device 416 may constitute machine readable media.

[0053] Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0054] While the machine readable medium 422 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 424.

[0055] An apparatus of the machine 400 may be one or more of a hardware processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 404 and a static memory 406, sensors 421, network interface device 420, antennas 460, a display device 410, an input device 412, a UI navigation device 414, a mass storage 416, instructions 424, a signal generation device 418, and an output controller 428. The apparatus may be configured to perform one or more of the methods and/or operations disclosed herein. The apparatus may be intended as a component of the machine 400 to perform one or more of the methods and/or operations disclosed herein, and/or to perform a portion of one or more of the methods and/or operations disclosed herein. In some embodiments, the apparatus may include a pin or other means to receive power. In some embodiments, the apparatus may include power conditioning hardware.

[0056] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 400 and that cause the machine 400 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Readonly Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine-readable media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0057] The instructions 424 may further be transmitted or received over a communications network 426 using a transmission medium via the network interface device 420 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (HDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.

[0058] In an example, the network interface device 420 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 426. In an example, the network interface device 420 may include one or more antennas 460 to wirelessly communicate using at least one of single-input multiple-output (SFMO), multiple-input multiple-output (MFMO), or multiple-input single- output (MISO) techniques. In some examples, the network interface device 420 may wirelessly communicate using Multiple User MFMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 400, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0059] Reference is made to Fig. 5, which schematically illustrates a method in accordance with some demonstrative embodiments. For example, one or more of the operations of the method 500 of Fig. 5 may be performed by one or more elements of a wireless communication system, such as STA 200 of Fig. 2.

[0060] As indicated at block 502, the method includes encoding an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein: the legacy preamble and header portion includes a legacy header field L-Header, the L-Header including a legacy beam tracking request field, the legacy beam tracking request field being set to indicate to a legacy device that no beam tracking is requested; and the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field being set to indicate to a peer EDMG wireless communication device whether beam tracking is requested. At block 504, the method includes causing transmission of the EDMG SC PPDU. At block 506, the method includes causing the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

[0061] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine-readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0062] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0063] Examples:

[0064] The following examples pertain to further embodiments.

[0065] Example 1 includes a wireless communication device comprising a memory and processing circuitry coupled to the memory, the processing circuitry including logic to: encode an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein: the legacy preamble and header portion includes a legacy header field L-Header, the L-Header including a legacy beam tracking request field, the legacy beam tracking request field being set to indicate to a legacy device that no beam tracking is requested; and the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field being set to indicate to a peer EDMG wireless communication device that beam tracking is requested; cause transmission of the EDMG SC PPDU; and cause the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

[0066] Example 2 includes the subject matter of Example 1, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested.

[0067] Example 3 includes the subject matter of Example 1, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[0068] Example 4 includes the subject matter of Example 3, and optionally, wherein: the L- Header includes a packet type field; the EDMG Header-A field includes a training length field; and the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains a request that a training field be appended to a future response EDMG PPDU to the EDMG SC PPDU; and setting the training length field of the EDMG Header-A field to indicate a number of requested training units in the response EDMG PPDU.

[0069] Example 5 includes the subject matter of Example 4, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[0070] Example 6 includes the subject matter of Example 5, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[0071] Example 7 includes the subject matter of Example 3, and optionally, wherein: the L- Header includes a packet type field; the EDMG Header-A field includes a training length field; and the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and setting the training length field of the EDMG Header-A field to indicate a number of appended training units within the training field.

[0072] Example 8 includes the subject matter of Example 7, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[0073] Example 9 includes the subject matter of Example 8, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[0074] Example 10 includes the subject matter of Example 3, and optionally, wherein: the L- Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; setting the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and setting the RX TRN-Units per Each TX TRN-Unit to indicate a transmit and receive beam tracking request.

[0075] Example 11 includes the subject matter of Example 10, and optionally, wherein the

EDMG beam tracking field and the packet type field are both set to a value of one.

[0076] Example 12 includes the subject matter of Example 11, and optionally, wherein the

RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[0077] Example 13 includes the subject matter of Example 1, and optionally, wherein the L-

Header is set to indicate to a legacy DMG device a length of the EDMG SC PPDU.

[0078] Example 14 includes the subject matter of Example 1, and optionally, further including a front-end module and a radio integrated circuit (radio IC) coupled to the front-end module, the radio IC further being coupled to the processing circuitry.

[0079] Example 15 includes the subject matter of Example 14, and optionally, further including one or more antennas.

[0080] Example 16 includes 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 computer processor, cause the at least one computer processor to implement operations at a wireless communication device, the operations comprising: encoding an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein: the legacy preamble and header portion includes a legacy header field L-Header, the L-Header including a legacy beam tracking request field, the legacy beam tracking request field being set to indicate to a legacy device that no beam tracking is requested; and the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field being set to indicate to a peer EDMG wireless communication device whether beam tracking is requested; causing transmission of the EDMG SC PPDU; and causing the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

[0081] Example 17 includes the subject matter of Example 16, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested, and set to a value of zero to indicate to a peer EDMG wireless communication device that beam tracking is not needed.

[0082] Example 18 includes the subject matter of Example 16, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[0083] Example 19 includes the subject matter of Example 18, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the operations include encoding the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains a request that a training field be appended to a future response EDMG PPDU to the EDMG SC PPDU; and setting the training length field of the EDMG Header-A field to indicate a number of requested training units in the response EDMG PPDU.

[0084] Example 20 includes the subject matter of Example 19, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[0085] Example 21 includes the subject matter of Example 20, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[0086] Example 22 includes the subject matter of Example 18, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the operations include encoding the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and setting the training length field of the EDMG Header-A field to indicate a number of appended training units within the training field.

[0087] Example 23 includes the subject matter of Example 22, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[0088] Example 24 includes the subject matter of Example 23, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[0089] Example 25 includes the subject matter of Example 18, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the operations include encoding the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; setting the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and setting the RX TRN-Units per Each TX TRN-Unit to indicate a transmit and receive beam tracking request.

[0090] Example 26 includes the subject matter of Example 25, and optionally, wherein the

[0091] Example 27 includes the subject matter of Example 26, and optionally, wherein the

RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[0092] Example 28 includes the subject matter of Example 16, and optionally, wherein the L-

Header is set to indicate to a legacy DMG device a length of the EDMG SC PPDU. [0093] Example 29 includes a method to be performed at a wireless communication device, the method comprising: encoding an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein: the legacy preamble and header portion includes a legacy header field L-Header, the L-Header including a legacy beam tracking request field, the legacy beam tracking request field being set to indicate to a legacy device that no beam tracking is requested; and the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field being set to indicate to a peer EDMG wireless communication device whether beam tracking is requested; causing transmission of the EDMG SC PPDU; and causing the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

[0094] Example 30 includes the subject matter of Example 29, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested, and set to a value of zero to indicate to a peer EDMG wireless communication device that beam tracking is not needed.

[0095] Example 31 includes the subject matter of Example 29, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[0096] Example 32 includes the subject matter of Example 31, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the method includes encoding the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains a request that a training field be appended to a future response EDMG PPDU to the EDMG SC PPDU; and setting the training length field of the EDMG Header-A field to indicate a number of requested training units in the response EDMG PPDU.

[0097] Example 33 includes the subject matter of Example 32, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[0098] Example 34 includes the subject matter of Example 33, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[0099] Example 35 includes the subject matter of Example 31, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the method includes encoding the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and setting the training length field of the EDMG Header-A field to indicate a number of appended training units within the training field.

[00100] Example 36 includes the subject matter of Example 35, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[00101] Example 37 includes the subject matter of Example 36, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00102] Example 38 includes the subject matter of Example 31, and optionally, wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the method includes encoding the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; setting the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and setting the RX TRN-Units per Each TX TRN-Unit to indicate a transmit and receive beam tracking request.

[00103] Example 39 includes the subject matter of Example 38, and optionally, wherein the

[00104] Example 40 includes the subject matter of Example 39, and optionally, wherein the

RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[00105] Example 41 includes a wireless communication device comprising a memory and processing circuitry coupled to the memory, the processing circuitry including logic to: decode an Enhanced Directional Multi-Gigabit (EDMG) legacy preamble and header portion of an EDMG Single Carrier (SC) Physical Layer Protocol Data Unit (EDMG SC PPDU) sent by a peer EDMG device, the EDMG preamble and header portion including an EDMG Header, the EDMG Header including an EDMG beam tracking request field; determine that the peer EDMG device needs beam tracking based on an indication in the EDMG beam tracking request field; and cause beam tracking for the peer EDMG device based on the indication.

[00106] Example 42 includes the subject matter of Example 41, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate that beam tracking is requested for the peer EDMG device.

[00107] Example 43 includes the subject matter of Example 41, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[00108] Example 44 includes the subject matter of Example 43, and optionally, wherein the processing circuitry is further to decode a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the processing circuitry is to decode the EDMG Header- A field to determine a request to perform receive beam tracking for the peer EDMG wireless communication device in response to determining that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains a request that training subfields be appended to a response EDMG PPDU to the EDMG SC PPDU; and the training length field of the EDMG Header-A field indicates a number of requested training subfields in the response EDMG PPDU.

[00109] Example 45 includes the subject matter of Example 44, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[00110] Example 46 includes the subject matter of Example 45, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00111] Example 47 includes the subject matter of Example 43, and optionally, wherein the processing circuitry is further to decode a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the processing circuitry is to decode the EDMG SC PPDU to determine a request to perform transmit beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates a value of one to indicate that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; and the training length field of the EDMG Header-A field indicates a number of the appended training subfields.

[00112] Example 48 includes the subject matter of Example 47, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[00113] Example 49 includes the subject matter of Example 48, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00114] Example 50 includes the subject matter of Example 43, and optionally, wherein the processing circuitry is further to decode a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the processing circuitry is to decode the EDMG SC PPDU to determine a request to perform transmit and receive beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and the RX TRN-Units per Each TX TRN-Unit indicates a transmit and receive beam tracking request.

[00115] Example 51 includes the subject matter of Example 50, and optionally, wherein the

[00116] Example 52 includes the subject matter of Example 51, and optionally, wherein the

RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[00117] Example 53 includes the subject matter of Example 51, and optionally, further including a front-end module and a radio integrated circuit (radio IC) coupled to the front-end module, the radio IC further being coupled to the processing circuitry.

[00118] Example 54 includes the subject matter of Example 53, and optionally, further including one or more antennas. [00119] Example 55 includes 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 computer processor, cause the at least one computer processor to implement operations at a wireless communication device, the operations comprising: decoding an Enhanced Directional Multi-Gigabit (EDMG) legacy preamble and header portion of an EDMG Single Carrier (SC) Physical Layer Protocol Data Unit (EDMG SC PPDU) sent by a peer EDMG device, the EDMG preamble and header portion including an EDMG Header, the EDMG Header including an EDMG beam tracking request field; determining that the peer EDMG device needs beam tracking based on an indication in the EDMG beam tracking request field; and causing beam tracking for the peer EDMG device based on the indication.

[00120] Example 56 includes the subject matter of Example 55, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate that beam tracking is requested for the peer EDMG device.

[00121] Example 57 includes the subject matter of Example 55, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[00122] Example 58 includes the subject matter of Example 57, and optionally, wherein the operations further include decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the operations include decoding the EDMG Header-A field to determine a request to perform receive beam tracking for the peer EDMG wireless communication device in response to determining that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains a request that training subfields be appended to a response EDMG PPDU to the EDMG SC PPDU; and the training length field of the EDMG Header-A field indicates a number of requested training subfields in the response EDMG PPDU.

[00123] Example 59 includes the subject matter of Example 58, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[00124] Example 60 includes the subject matter of Example 59, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero. [00125] Example 61 includes the subject matter of Example 57, and optionally, wherein the operations further include decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the operations include decoding the EDMG SC PPDU to determine a request to perform transmit beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates a value of one to indicate that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; and the training length field of the EDMG Header-A field indicates a number of the appended training subfields.

[00126] Example 62 includes the subject matter of Example 61, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[00127] Example 63 includes the subject matter of Example 62, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00128] Example 64 includes the subject matter of Example 57, and optionally, wherein the operations further include decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the operations include decoding the EDMG SC PPDU to determine a request to perform transmit and receive beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and the RX TRN-Units per Each TX TRN-Unit indicates a transmit and receive beam tracking request.

[00129] Example 65 includes the subject matter of Example 64, and optionally, wherein the

[00130] Example 66 includes the subject matter of Example 65, and optionally, wherein the

RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[00131] Example 67 includes a method to be performed at a wireless communication device, the method comprising: decoding an Enhanced Directional Multi-Gigabit (EDMG) legacy preamble and header portion of an EDMG Single Carrier (SC) Physical Layer Protocol Data Unit (EDMG SC PPDU) sent by a peer EDMG device, the EDMG preamble and header portion including an EDMG Header, the EDMG Header including an EDMG beam tracking request field; determining that the peer EDMG device needs beam tracking based on an indication in the EDMG beam tracking request field; and causing beam tracking for the peer EDMG device based on the indication.

[00132] Example 68 includes the subject matter of Example 67, and optionally, wherein the EDMG beam tracking request field is set to a value of one to indicate that beam tracking is requested for the peer EDMG device.

[00133] Example 69 includes the subject matter of Example 67, and optionally, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

[00134] Example 70 includes the subject matter of Example 69, and optionally, further including decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the method includes decoding the EDMG Header-A field to determine a request to perform receive beam tracking for the peer EDMG wireless communication device in response to determining that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains a request that training subfields be appended to a response EDMG PPDU to the EDMG SC PPDU; and the training length field of the EDMG Header-A field indicates a number of requested training subfields in the response EDMG PPDU.

[00135] Example 71 includes the subject matter of Example 70, and optionally, wherein the EDMG beam tracking field is set to a value of one, and the packet type field is set to a value of zero.

[00136] Example 72 includes the subject matter of Example 71, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00137] Example 73 includes the subject matter of Example 69, and optionally, further including decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field; and the method includes decoding the EDMG SC PPDU to determine a request to perform transmit beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates a value of one to indicate that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; and the training length field of the EDMG Header-A field indicates a number of the appended training subfields.

[00138] Example 74 includes the subject matter of Example 73, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[00139] Example 75 includes the subject matter of Example 74, and optionally, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

[00140] Example 76 includes the subject matter of Example 69, and optionally, further including decoding a legacy header field L-Header of the EDMG SC PPDU, and wherein: the L-Header includes a packet type field; the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and the method includes decoding the EDMG SC PPDU to determine a request to perform transmit and receive beam tracking for the peer EDMG wireless communication device in response to a determination that: the EDMG beam tracking request field indicates that beam tracking is requested; the packet type field indicates that the EDMG SC PPDU contains appended training subfields; the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and the RX TRN-Units per Each TX TRN-Unit indicates a transmit and receive beam tracking request.

[00141] Example 77 includes the subject matter of Example 76, and optionally, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

[00142] Example 78 includes the subject matter of Example 77, and optionally, wherein the RX TRN-Units per Each TX TRN-Unit is set to a value larger than zero.

[00143] Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.

Claims

CLAIMS What is claimed is:

1. A wireless communication device comprising a memory and processing circuitry coupled to the memory, the processing circuitry including logic to:

encode an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein:

the legacy preamble and header portion includes a legacy header field L- Header, the L-Header including a legacy beam tracking request field, the legacy beam tracking request field being set to indicate to a legacy device that no beam tracking is requested; and

the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field being set to indicate to a peer EDMG wireless communication device that beam tracking is requested;

cause transmission of the EDMG SC PPDU; and

cause the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

2. The device of claim 1, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

3. The device of claim 2, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by:

setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested;

setting the packet type field to indicate that the EDMG SC PPDU contains a request that a training field be appended to a future response EDMG PPDU to the EDMG SC PPDU; and setting the training length field of the EDMG Header-A field to indicate a number of requested training units in the response EDMG PPDU.

4. The device of claim 2, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

5. The device of claim 2, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by:

setting the EDMG beam tracking request field a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested;

setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and

setting the training length field of the EDMG Header-A field to indicate a number of appended training units within the training field.

6. The device of claim 5, wherein the EDMG beam tracking field and the packet type field are both set to a value of one.

7. The device of claim 6, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

8. The device of claim 2, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field and a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit); and

the processing circuitry is to encode the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless communication device by: setting the EDMG beam tracking request field to indicate to a peer EDMG wireless communication device that beam tracking is requested;

setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field;

setting the training length field of the EDMG Header-A to indicate a number of appended training units within the training field; and

setting the RX TRN-Units per Each TX TRN-Unit to indicate a transmit and receive beam tracking request.

9. The device of claim 1, wherein the L-Header is set to indicate to a legacy DMG device a length of the EDMG SC PPDU.

10. The device of claim 1, further including a front-end module and a radio integrated circuit (radio IC) coupled to the front-end module, the radio IC further being coupled to the processing circuitry.

11. The device of claim 10, further including one or more antennas.

12. A method to be performed at a wireless communication device, the method

comprising:

encoding an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein:

the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG beam tracking request field set to indicate to a peer EDMG wireless communication device whether beam tracking is requested;

causing transmission of the EDMG SC PPDU; and

causing the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

13. The method of claim 12, wherein the EDMG beam tracking request field is set to a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested, and set to a value of zero to indicate to a peer EDMG wireless communication device that beam tracking is not needed.

14. The method of claim 12, wherein the EDMG Header includes an EDMG Header-A field, and wherein the EDMG beam tracking request field is within the EDMG Header-A field.

15. The method of claim 14, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the method includes encoding the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by:

setting the packet type field to indicate that the EDMG SC PPDU contains a request that a training field be appended to a future response EDMG PPDU to the EDMG SC PPDU; and

setting the training length field of the EDMG Header-A field to indicate a number of requested training units in the response EDMG PPDU.

16. The method of claim 15, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

17. The method of claim 14, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the method further includes encoding the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by:

setting the EDMG beam tracking request field a value of one to indicate to a peer EDMG wireless communication device that beam tracking is requested; setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and

18. The method of claim 17, wherein the EDMG-Header-A field further includes a receive training units per each transmit training unit field (RX TRN-Units per Each TX TRN-Unit), the RX TRN-Units per Each TX TRN-Unit being set to a value of zero.

19. The method of claim 14, wherein:

the L-Header includes a packet type field;

the method includes encoding the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless communication device by:

20. The method of claim 12, wherein the L-Header is set to indicate to a legacy DMG device a length of the EDMG SC PPDU.

21. A wireless communication device comprising:

means for encoding an Enhanced Directional Multi-Gigabit Single Carrier Physical Layer Protocol Data Unit (EDMG SC PPDU) including a legacy preamble and header portion, an EDMG preamble and header portion, a data portion and a training field, wherein:

the EDMG preamble and header portion includes an EDMG Header, the EDMG Header including an EDMG Header-A field, the EDMG Header-A field including an EDMG beam tracking request field set to indicate to a peer EDMG wireless communication device whether beam tracking is requested;

causing transmission of the EDMG SC PPDU; and

means for causing the peer EDMG wireless communication device to begin beam tracking based on the EDMG SC PPDU.

22. The device of claim 21, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the device further including means for encoding the EDMG SC PPDU to indicate a request to perform receive beam tracking to the peer EDMG wireless communication device by:

23. The device of claim 21, wherein:

the L-Header includes a packet type field;

the EDMG Header-A field includes a training length field; and

the device further includes means for encoding the EDMG SC PPDU to indicate a request to perform transmit beam tracking to the peer EDMG wireless communication device by:

setting the packet type field to indicate that the EDMG SC PPDU contains an appended training field; and setting the training length field of the EDMG Header-A field to indicate a number of appended training units within the training field.

24. The device of claim 21, wherein:

the L-Header includes a packet type field;

the device further includes means for encoding the EDMG SC PPDU to indicate a request to perform transmit and receive beam tracking to the peer EDMG wireless

communication device by:

25. A machine-readable medium including code, when executed, to cause a machine to perform the method of any one of claims 12-20.