# Patent

## Title
Range extension mode for WiFi

## Abstract

A method for generating a physical layer (PHY) data unit for transmission via a communication channel is described where the PHY data unit conforms to a first communication protocol. Orthogonal frequency division multiplexing (OFDM) symbols for a data field of the PHY data unit are generated according to a range extension coding scheme that corresponds to a range extension mode of the first communication protocol. A preamble of the PHY data unit is generated, the preamble having i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data field are generated according to the range extension coding scheme. The first portion of the preamble is formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the first portion of the preamble. The PHY data unit is generated to include the preamble and the data field.

## Background
CROSS-REFERENCES TO RELATED APPLICATIONS
This disclosure claims the benefit of U.S. Provisional Patent Application No. 61/895,591, entitled “Range Extension PHY” and filed on Oct. 25, 2013, and U.S. Provisional Patent Application No. 61/925,332, entitled “Range Extension PHY” and filed on Jan. 9, 2014, and U.S. Provisional Patent Application No. 61/950,727, entitled “Range Extension PHY” and filed on Mar. 10, 2014, and U.S. Provisional Patent Application No. 61/987,778, entitled “Range Extension PHY” and filed on May 2, 2014, the disclosures of each of which are incorporated herein by reference in their entireties.


FIELD OF THE DISCLOSURE
The present disclosure relates generally to communication networks and, more particularly, to wireless local area networks that utilize a range extension mode.
BACKGROUND
When operating in an infrastructure mode, wireless local area networks (WLANs) typically include an access point (AP) and one or more client stations. WLANs have evolved rapidly over the past decade. Development of WLAN standards such as the Institute for Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, and 802.11n Standards has improved single-user peak data throughput. For example, the IEEE 802.11b Standard specifies a single-user peak throughput of 11 megabits per second (Mbps), the IEEE 802.11a and 802.11g Standards specify a single-user peak throughput of 54 Mbps, the IEEE 802.11n Standard specifies a single-user peak throughput of 600 Mbps, and the IEEE 802.11ac Standard specifies a single-user peak throughput in the gigabits per second (Gbps) range. Future standards promise to provide even greater throughputs, such as throughputs in the tens of Gbps range.
SUMMARY
In an embodiment, a method for generating a physical layer (PHY) data unit for transmission via a communication channel, the PHY data unit conforming to a first communication protocol, includes generating orthogonal frequency division multiplexing (OFDM) symbols for a data field of the PHY data unit according to a range extension coding scheme that corresponds to a range extension mode of the first communication protocol. The method also includes generating a preamble of the PHY data unit, the preamble having i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data field are generated according to the range extension coding scheme, the first portion of the preamble being formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the first portion of the preamble. The method also includes generating the PHY data unit to include the preamble and the data field.
In another embodiment, an apparatus includes a network device having one or more integrated circuits. The integrated circuits are configured to generate orthogonal frequency division multiplexing (OFDM) symbols for a data field of a physical layer (PHY) data unit according to a range extension coding scheme that corresponds to a range extension mode of a first communication protocol to which the PHY data unit conforms. The integrated circuits are also configured to generate a preamble of the PHY data unit, the preamble having i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data field are generated according to the range extension coding scheme, the first portion of the preamble being formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the first portion of the preamble. The integrated circuits are also configured to generate the PHY data unit to include the preamble and the data field.
In yet another embodiment, a method for generating a physical layer (PHY) data unit for transmission via a communication channel, the PHY data unit conforming to a first communication protocol, includes generating a first plurality of orthogonal frequency division multiplexing (OFDM) symbols for a first field of a preamble to be included in the PHY data unit. Each OFDM symbol of the first plurality of OFDM symbols corresponds to a first long training sequence of the first communication protocol that is obtained at least by multiplying a predetermined sequence with a second long training sequence of a second communication protocol. The method also includes encoding a first plurality of information bits for a second field of the preamble to generate a first plurality of encoded bits. The method includes mapping the first plurality of encoded bits to a first plurality of constellation symbols. The method also includes generating a first plurality of modified constellation symbols, including multiplying the first plurality of constellation symbols by the predetermined sequence. The method includes generating a second plurality of orthogonal frequency division multiplexing (OFDM) symbols to include the first plurality of modified constellation symbols. The method also includes generating the preamble to include the first plurality of OFDM symbols for the first field and the second plurality of OFDM symbols for the second field. The method also includes generating the PHY data unit to include at least the preamble.
In an embodiment, an apparatus includes a network interface device having one or more integrated circuits. The integrated circuits are configured to generate a first plurality of orthogonal frequency division multiplexing (OFDM) symbols for a first field of a preamble to be included in the physical layer (PHY) data unit. Each OFDM symbol of the first plurality of OFDM symbols corresponds to a first long training sequence of the first communication protocol that is obtained at least by multiplying a predetermined sequence with a second long training sequence of a second communication protocol. The integrated circuits are also configured to encode a first plurality of information bits for a second field of the preamble to generate a first plurality of encoded bits. The integrated circuits are configured to map the first plurality of encoded bits to a first plurality of constellation symbols. The integrated circuits are also configured to generate a first plurality of modified constellation symbols, including multiplying the first plurality of constellation symbols by the predetermined sequence. The integrated circuits are configured to generate a second plurality of orthogonal frequency division multiplexing (OFDM) symbols to include the first plurality of modified constellation symbols. The integrated circuits are also configured to generate the preamble to include the first plurality of OFDM symbols for the first field and the second plurality of OFDM symbols for the second field. The integrated circuits are configured to generate the PHY data unit to include at least the preamble.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of an example wireless local area network (WLAN), according to an embodiment.
FIGS. 2A and 2B are diagrams of a prior art data unit format.
FIG. 3 is a diagram of another prior art data unit format.
FIG. 4 is a diagram of another prior art data unit format.
FIG. 5 is a diagram of another prior art data unit format.
FIG. 6A is a group of diagrams of modulations used to modulate symbols in a prior art data unit.
FIG. 6B is a group of diagrams of modulations used to modulate symbols in an example data unit, according to an embodiment.
FIG. 7A is a diagram of an orthogonal frequency division multiplexing (OFDM) data unit, according to an embodiment.
FIG. 7B is a group of diagrams of modulations used to modulate symbols in the data unit depicted in FIG. 7A, according to an embodiment.
FIG. 8 is a block diagram of an OFDM symbol, according to an embodiment.
FIG. 9A is a diagram illustrating an example data unit in which a regular coding scheme is used for a preamble of the data unit, according to an embodiment.
FIG. 9B is a diagram illustrating an example data unit in which a regular coding scheme is used for only a portion a preamble of the data unit, according to an embodiment.
FIG. 10A is a diagram illustrating an example data unit in which tone spacing adjustment is used in combination with block coding, according to an embodiment.
FIG. 10B is a diagram illustrating an example data unit in which tone spacing adjustment is used in combination with block coding, according to another embodiment.
FIG. 11A is a diagram illustrating a regular mode data unit, according to an embodiment.
FIG. 11B is a diagram illustrating range extension mode data unit, according to an embodiment.
FIGS. 12A-12B are diagrams respectively illustrating two possible formats of a long training field, according to two example embodiments.
FIG. 13A is a diagram illustrating a non-legacy signal field of the regular mode data unit of FIG. 11A, according to an embodiment.
FIG. 13B is a diagram illustrating a non-legacy signal field of the range extension mode data unit of FIG. 11B, according to an embodiment.
FIG. 14A is a block diagram illustrating a range extension mode data unit, according to an embodiment.
FIG. 14B is a diagram illustrating a legacy signal field of the range extension mode data unit of FIG. 14A, according to one embodiment.
FIG. 14C is a diagram illustrating a Fast Fourier Transform (FFT) window for the legacy signal field of FIG. 14B at the legacy receiving device, according to an embodiment.
FIG. 15 is a block diagram illustrating format of a non-legacy signal field, according to an embodiment.
FIG. 16 is a block diagram illustrating an example PHY processing unit for generating regular mode data units using the regular coding scheme, according to an embodiment.
FIG. 17A is a block diagram of an example PHY processing unit for generating range extension mode data units using a range extension coding scheme, according to an embodiment.
FIG. 17B is a block diagram of an example PHY processing unit for generating range extension mode data units, according to another embodiment.
FIG. 18A is a block diagram of an example PHY processing unit for generating range extension mode data units using a range extension coding scheme, according to another embodiment.
FIG. 18B is a block diagram of an example PHY processing unit for generating range extension mode data units, according to another embodiment.
FIG. 19A is a block diagram of an example PHY processing unit for generating range extension mode data units, according to another embodiment.
FIG. 19B is a block diagram of an example PHY processing unit for generating range extension mode data units, according to another embodiment.
FIG. 20A is a diagram showing repetition of OFDM symbols in a preamble of a range extension mode data unit, according to an embodiment.
FIG. 20B is a diagram showing repetition of OFDM symbols in a preamble of a range extension mode data unit, according to an embodiment.
FIG. 20C is a diagram showing a time domain repetition scheme for OFDM symbols, according to one embodiment.
FIG. 20D is a diagram showing a repetition scheme for OFDM symbols, according to another embodiment.
FIG. 21 is a flow diagram of an example method for generating a data unit, according to an embodiment.
FIG. 22A is a diagram of a 20 MHz overall bandwidth having repetitions of the range extension data unit having a 10 MHz sub-band, according to an embodiment.
FIG. 22B is a diagram of a 40 MHz overall bandwidth having repetitions of the range extension data unit having a 10 MHz sub-band, according to an embodiment.
FIG. 22C is a diagram of an example tone plan for a 32-FFT mode, according to an embodiment.
FIG. 23 is a diagram of an example data unit in which the range extension mode is used for a preamble of the data unit, according to an embodiment.
FIG. 24 is a block diagram of an example PHY processing unit for generating range extension mode data units, according to another embodiment.
FIG. 25A is a diagram of an example 20 MHz total bandwidth having 1⁄2 tone spacing, according to an embodiment.
FIG. 25B is a diagram of an example 20 MHz total bandwidth having 1⁄2 tone spacing, according to an embodiment.
FIG. 26A is a diagram of a non-legacy tone plan for the range extension mode having a size 64 FFT and 1⁄2 tone spacing, according to an embodiment.
FIG. 26B is a diagram of a non-legacy tone plan for the range extension mode having a size 128 FFT and 1⁄2 tone spacing, according to an embodiment.
FIG. 26C is a diagram illustrating a non-legacy tone plan for the range extension mode having a size 256 FFT and 1⁄2 tone spacing, according to an embodiment.
FIG. 27 is a flow diagram of an example method for generating a data unit, according to an embodiment.
FIG. 28 is a flow diagram of an example method for generating a data unit, according to another embodiment.



DETAILED DESCRIPTION
In embodiments described below, a wireless network device such as an access point (AP) of a wireless local area network (WLAN) transmits data streams to one or more client stations. The AP is configured to operate with client stations according to at least a first communication protocol. The first communication protocol is sometimes referred to herein as “high efficiency Wi-Fi,” “HEW” communication protocol, or 802.11ax communication protocol. In some embodiments, different client stations in the vicinity of the AP are configured to operate according to one or more other communication protocols which define operation in the same frequency band as the HEW communication protocol but with generally lower data throughputs. The lower data throughput communication protocols (e.g., IEEE 802.11a, IEEE 802.11n, and/or IEEE 802.11ac) are collectively referred herein as “legacy” communication protocols. In at least some embodiments, the legacy communication protocols are generally deployed in indoor communication channels, and the HEW communication protocol is at least sometimes deployed for outdoor communications, extended range communications, or communications in areas with reduced signal-to-noise ratios (SNR) of transmitted signals.
According to an embodiment, symbols transmitted by the AP are generated according to a range extension coding scheme that provides increased redundancy of symbols or information bits encoded within the symbols. The redundancy increases the likelihood of the symbols being successfully decoded by a device that receives the symbols from the AP, particularly in areas with reduced SNR. An amount of redundancy needed to mitigate the reduced SNR generally depends on a delay channel spread (e.g. for an outdoor communication channel), other signals that interfere with the symbols, and/or other factors. In an embodiment, the HEW communication protocol defines a regular mode and a range extension mode. The regular mode is generally used with communication channels characterized by shorter channel delay spreads (e.g., indoor communication channels) or generally higher SNR values, while the range extension mode is generally used with communication channels characterized by relatively longer channel delay spreads (e.g., outdoor communication channels) or generally lower SNR values in an embodiment. In an embodiment, a regular coding scheme is used in the regular mode, and a range extension coding scheme is used in the range extension mode.
In an embodiment, a data unit transmitted by the AP includes a preamble and a data portion, wherein the preamble is used, at least in part, to signal, to a receiving device, various parameters used for transmission of the data portion. In various embodiments, the preamble of a data unit is used to signal, to a receiving device, the particular coding scheme being utilized in at least the data portion of the data unit. In some embodiments, a same preamble format is used in the regular mode as in the range extension mode. In one such embodiment, the preamble includes an indication set to indicate whether the regular coding scheme or the range extension coding scheme is used for at least the data portion of the data unit. In some embodiments, the indicated regular coding scheme or range extension coding scheme is used for at least a portion of the preamble of the data unit, in addition to the data portion of the data unit. In an embodiment, the receiving device determines the particular coding scheme being utilized based on the indication in the preamble of the data unit, and then decodes the appropriate remaining portion of the data unit (e.g., the data portion, or a portion of the preamble and the data portion) using the particular coding scheme.
In another embodiment, a preamble used in the range extension mode is formatted differently from a preamble used in the regular mode. For example, the preamble used in the range extension mode is formatted such that the receiving device can automatically (e.g., prior to decoding) detect that the data unit corresponds to the range extension mode. In an embodiment, when the receiving device detects that the data unit corresponds to the range extension mode, the receiving device decodes the data portion of the data unit, and in at least some embodiments, at least a portion of the preamble as well as the data portion of the data unit, using the range extension coding scheme. On the other hand, when the receiving device detects that the data unit does not correspond to the range extension mode, the receiving device assumes that the data unit corresponds to the regular mode, in an embodiment. The receiving device then decodes at least the data portion of the data unit using the regular coding scheme, in an embodiment.
Additionally, in at least some embodiments, a preamble of a data unit in the regular mode and/or in the range extension mode is formatted such that a client station that operates according to a legacy protocol, and not the HEW communication protocol, is able to determine certain information regarding the data unit, such as a duration of the data unit, and/or that the data unit does not conform to the legacy protocol. Additionally, a preamble of the data unit is formatted such that a client station that operates according to the HEW protocol is able to determine the data unit conforms to the HEW communication protocol and whether the data unit is formatted according to the regular mode or the range extension mode, in an embodiment. Similarly, a client station configured to operate according to the HEW communication protocol also transmits data units such as described above, in an embodiment.
In at least some embodiments, data units formatted such as described above are useful, for example, with an AP that is configured to operate with client stations according to a plurality of different communication protocols and/or with WLANs in which a plurality of client stations operate according to a plurality of different communication protocols. Continuing with the example above, a communication device configured to operate according to both the HEW communication protocol (including the regular mode and the range extension mode) and a legacy communication protocol is able to determine that a given data unit is formatted according to the HEW communication protocol and not the legacy communication protocol, and further, to determine that the data unit is formatted according to the range extension mode and not the regular mode. Similarly, a communication device configured to operate according to a legacy communication protocol but not the HEW communication protocol is able to determine that the data unit is not formatted according to the legacy communication protocol and/or determine a duration of the data unit.
FIG. 1 is a block diagram of an example wireless local area network (WLAN) 10, according to an embodiment. An AP 14 includes a host processor 15 coupled to a network interface 16. The network interface 16 includes a medium access control (MAC) processing unit 18 and a physical layer (PHY) processing unit 20. The PHY processing unit 20 includes a plurality of transceivers 21, and the transceivers 21 are coupled to a plurality of antennas 24. Although three transceivers 21 and three antennas 24 are illustrated in FIG. 1, the AP 14 includes other suitable numbers (e.g., 1, 2, 4, 5, etc.) of transceivers 21 and antennas 24 in other embodiments. In one embodiment, the MAC processing unit 18 and the PHY processing unit 20 are configured to operate according to a first communication protocol (e.g., HEW communication protocol), including at least a first mode and a second mode of the first communication protocol. In some embodiments, the first mode corresponds to a range extension mode that uses a range extension coding scheme (e.g., block encoding, bit-wise replication, or symbol replication), a signal modulation scheme (e.g., phase shift keying or quadrature amplitude modulation), or both a range extension coding scheme and signal modulation scheme. The range extension mode is configured to increase a range and/or reduce a signal-to-noise (SNR) ratio, as compared to the second mode (e.g., a regular mode using a regular coding scheme), at which successful decoding of PHY data units conforming to the range extension mode is performed. In various embodiments, the range extension mode reduces a data rate of transmission as compared to the regular mode to achieve successful decoding with increased range and/or reduced SNR ratio. In another embodiment, the MAC processing unit 18 and the PHY processing unit 20 are also configured to operate according to a second communication protocol (e.g., IEEE 802.11ac Standard). In yet another embodiment, the MAC processing unit 18 and the PHY processing unit 20 are additionally configured to operate according to the second communication protocol, a third communication protocol, and/or a fourth communication protocol (e.g., the IEEE 802.11a Standard and/or the IEEE 802.11n Standard).
The WLAN 10 includes a plurality of client stations 25. Although four client stations 25 are illustrated in FIG. 1, the WLAN 10 includes other suitable numbers (e.g., 1, 2, 3, 5, 6, etc.) of client stations 25 in various scenarios and embodiments. At least one of the client stations 25 (e.g., client station 25-1) is configured to operate at least according to the first communication protocol. In some embodiments, at least one of the client stations 25 is not configured to operate according to the first communication protocol but is configured to operate according to at least one of the second communication protocol, the third communication protocol, and/or the fourth communication protocol (referred to herein as a “legacy client station”).
The client station 25-1 includes a host processor 26 coupled to a network interface 27. The network interface 27 includes a MAC processing unit 28 and a PHY processing unit 29. The PHY processing unit 29 includes a plurality of transceivers 30, and the transceivers 30 are coupled to a plurality of antennas 34. Although three transceivers 30 and three antennas 34 are illustrated in FIG. 1, the client station 25-1 includes other suitable numbers (e.g., 1, 2, 4, 5, etc.) of transceivers 30 and antennas 34 in other embodiments.
According to an embodiment, the client station 25-4 is a legacy client station, i.e., the client station 25-4 is not enabled to receive and fully decode a data unit that is transmitted by the AP 14 or another client station 25 according to the first communication protocol. Similarly, according to an embodiment, the legacy client station 25-4 is not enabled to transmit data units according to the first communication protocol. On the other hand, the legacy client station 25-4 is enabled to receive and fully decode and transmit data units according to the second communication protocol, the third communication protocol, and/or the fourth communication protocol.
In an embodiment, one or both of the client stations 25-2 and 25-3, has a structure the same as or similar to the client station 25-1. In an embodiment, the client station 25-4 has a structure similar to the client station 25-1. In these embodiments, the client stations 25 structured the same as or similar to the client station 25-1 have the same or a different number of transceivers and antennas. For example, the client station 25-2 has only two transceivers and two antennas (not shown), according to an embodiment.
In various embodiments, the PHY processing unit 20 of the AP 14 is configured to generate data units conforming to the first communication protocol and having formats described herein. The transceiver(s) 21 is/are configured to transmit the generated data units via the antenna(s) 24. Similarly, the transceiver(s) 21 is/are configured to receive data units via the antenna(s) 24. The PHY processing unit 20 of the AP 14 is configured to process received data units conforming to the first communication protocol and having formats described hereinafter and to determine that such data units conform to the first communication protocol, according to various embodiments.
In various embodiments, the PHY processing unit 29 of the client device 25-1 is configured to generate data units conforming to the first communication protocol and having formats described herein. The transceiver(s) 30 is/are configured to transmit the generated data units via the antenna(s) 34. Similarly, the transceiver(s) 30 is/are configured to receive data units via the antenna(s) 34. The PHY processing unit 29 of the client device 25-1 is configured to process received data units conforming to the first communication protocol and having formats described hereinafter and to determine that such data units conform to the first communication protocol, according to various embodiments.
FIG. 2A is a diagram of a prior art OFDM data unit 200 that the AP 14 is configured to transmit to the legacy client station 25-4 via orthogonal frequency division multiplexing (OFDM) modulation, according to an embodiment. In an embodiment, the legacy client station 25-4 is also configured to transmit the data unit 200 to the AP 14. The data unit 200 conforms to the IEEE 802.11a Standard and occupies a 20 Megahertz (MHz) band. The data unit 200 includes a preamble having a legacy short training field (L-STF) 202, generally used for packet detection, initial synchronization, and automatic gain control, etc., and a legacy long training field (L-LTF) 204, generally used for channel estimation and fine synchronization. The data unit 200 also includes a legacy signal field (L-SIG) 206, used to carry certain physical layer (PHY) parameters with the data unit 200, such as modulation type and coding rate used to transmit the data unit, for example. The data unit 200 also includes a data portion 208. FIG. 2B is a diagram of example data portion 208 (not low density parity check encoded), which includes a service field, a scrambled physical layer service data unit (PSDU), tail bits, and padding bits, if needed. The data unit 200 is designed for transmission over one spatial or space-time stream in a single input single output (SISO) channel configuration.
FIG. 3 is a diagram of a prior art OFDM data unit 300 that the AP 14 is configured to transmit to the legacy client station 25-4 via orthogonal frequency domain multiplexing (OFDM) modulation, according to an embodiment. In an embodiment, the legacy client station 25-4 is also configured to transmit the data unit 300 to the AP 14. The data unit 300 conforms to the IEEE 802.11n Standard, occupies a 20 MHz band, and is designed for mixed mode situations, i.e., when the WLAN includes one or more client stations that conform to the IEEE 802.11a Standard but not the IEEE 802.11n Standard. The data unit 300 includes a preamble having an L-STF 302, an L-LTF 304, an L-SIG 306, a high throughput signal field (HT-SIG) 308, a high throughput short training field (HT-STF) 310, and M data high throughput long training fields (HT-LTFs) 312, where M is an integer generally determined by the number of spatial streams used to transmit the data unit 300 in a multiple input multiple output (MIMO) channel configuration. In particular, according to the IEEE 802.11n Standard, the data unit 300 includes two HT-LTFs 312 if the data unit 300 is transmitted using two spatial streams, and four HT-LTFs 312 is the data unit 300 is transmitted using three or four spatial streams. An indication of the particular number of spatial streams being utilized is included in the HT-SIG field 308. The data unit 300 also includes a data portion 314.
FIG. 4 is a diagram of a prior art OFDM data unit 400 that the AP 14 is configured to transmit to the legacy client station 25-4 via orthogonal frequency domain multiplexing (OFDM) modulation, according to an embodiment. In an embodiment, the legacy client station 25-4 is also configured to transmit the data unit 400 to the AP 14. The data unit 400 conforms to the IEEE 802.11n Standard, occupies a 20 MHz band, and is designed for “Greenfield” situations, i.e., when the WLAN does not include any client stations that conform to the IEEE 802.11a Standard, and only includes client stations that conform to the IEEE 802.11n Standard. The data unit 400 includes a preamble having a high throughput Greenfield short training field (HT-GF-STF) 402, a first high throughput long training field (HT-LTF1) 404, a HT-SIG 406, and M data HT-LTFs 408, where M is an integer which generally corresponds to a number of spatial streams used to transmit the data unit 400 in a multiple input multiple output (MIMO) channel configuration. The data unit 400 also includes a data portion 410.
FIG. 5 is a diagram of a prior art OFDM data unit 500 that the AP 14 is configured to transmit to the legacy client station 25-4 via orthogonal frequency domain multiplexing (OFDM) modulation, according to an embodiment. In an embodiment, the legacy client station 25-4 is also configured to transmit the data unit 500 to the AP 14. The data unit 500 conforms to the IEEE 802.11ac Standard and is designed for “Mixed field” situations. The data unit 500 occupies a 20 MHz bandwidth. In other embodiments or scenarios, a data unit similar to the data unit 500 occupies a different bandwidth, such as a 40 MHz, an 80 MHz, or a 160 MHz bandwidth. The data unit 500 includes a preamble having an L-STF 502, an L-LTF 504, an L-SIG 506, two first very high throughput signal fields (VHT-SIGAs) 508 including a first very high throughput signal field (VHT-SIGA1) 508-1 and a second very high throughput signal field (VHT-SIGA2) 508-2, a very high throughput short training field (VHT-STF) 510, M very high throughput long training fields (VHT-LTFs) 512, where M is an integer, and a second very high throughput signal field (VHT-SIG-B) 514. The data unit 500 also includes a data portion 516.
FIG. 6A is a set of diagrams illustrating modulation of the L-SIG, HT-SIG1, and HT-SIG2 fields of the data unit 300 of FIG. 3, as defined by the IEEE 802.11n Standard. The L-SIG field is modulated according to binary phase shift keying (BPSK), whereas the HT-SIG1 and HT-SIG2 fields are modulated according to BPSK, but on the quadrature axis (Q-BPSK). In other words, the modulation of the HT-SIG1 and HT-SIG2 fields is rotated by 90 degrees as compared to the modulation of the L-SIG field.
FIG. 6B is a set of diagrams illustrating modulation of the L-SIG, VHT-SIGA1, and VHT-SIGA2 fields of the data unit 500 of FIG. 5, as defined by the IEEE 802.11ac Standard. Unlike the HT-SIG1 field in FIG. 6A, the VHT-SIGA1 field is modulated according to BPSK, same as the modulation of the L-SIG field. On the other hand, the VHT-SIGA2 field is rotated by 90 degrees as compared to the modulation of the L-SIG field.
FIG. 7A is a diagram of an OFDM data unit 700 that the AP 14 is configured to transmit to the client station 25-1 via orthogonal frequency domain multiplexing (OFDM) modulation, according to an embodiment. In an embodiment, the client station 25-1 is also configured to transmit the data unit 700 to the AP 14. The data unit 700 conforms to the first communication protocol and occupies a 20 MHz bandwidth. Data units that conform to the first communication protocol similar to the data unit 700 may occupy other suitable bandwidth such as 40 MHz, 80 MHz, 160 MHz, 320 MHz, 640 MHz, for example, or other suitable bandwidths, in other embodiments. The data unit 700 is suitable for “mixed mode” situations, i.e., when the WLAN 10 includes a client station (e.g., the legacy client station 25-4) that conforms to a legacy communication protocol, but not the first communication protocol. The data unit 700 is utilized in other situations as well, in some embodiments.
In an embodiment, the data unit 700 includes a preamble 701 having an L-STF 702, an L-LTF 704, an L-SIG 706, two first HEW signal fields (HEW-SIGAs) 708 including a first HEW signal field (HEW-SIGA1) 708-1 and a second HEW signal field (HEW-SIGA2) 708-2, an HEW short training field (HEW-STF) 710, M HEW long training fields (HEW-LTFs) 712, where M is an integer, and a third HEW signal field (HEW-SIGB) 714. Each of the L-STF 702, the L-LTF 704, the L-SIG 706, the HEW-SIGAs 708, the HEW-STF 710, the M HEW-LTFs 712, and the HEW-SIGB 714 comprises an integer number of one or more OFDM symbols. For example, in an embodiment, the HEW-SIGAs 708 comprise two OFDM symbols, where the HEW-SIGA1 708-1 field comprises the first OFDM symbol and the HEW-SIGA2 comprises the second OFDM symbol. In another embodiment, for example, the preamble 701 includes a third HEW signal field (HEW-SIGA3, not shown) and the HEW-SIGAs 708 comprise three OFDM symbols, where the HEW-SIGA1 708-1 field comprises the first OFDM symbol, the HEW-SIGA2 comprises the second OFDM symbol, and the HEW-SIGA3 comprises the third OFDM symbol. In at least some examples, the HEW-SIGAs 708 are collectively referred to as a single HEW signal field (HEW-SIGA) 708. In some embodiments, the data unit 700 also includes a data portion 716. In other embodiments, the data unit 700 omits the data portion 716.
In the embodiment of FIG. 7A, the data unit 700 includes one of each of the L-STF 702, the L-LTF 704, the L-SIG 706, the HEW-SIGA1s 708. In other embodiments in which an OFDM data unit similar to the data unit 700 occupies a cumulative bandwidth other than 20 MHz, each of the L-STF 702, the L-LTF 704, the L-SIG 706, the HEW-SIGA1s 708 is repeated over a corresponding number of 20 MHz sub-bands of the whole bandwidth of the data unit, in an embodiment. For example, in an embodiment, the OFDM data unit occupies an 80 MHz bandwidth and, accordingly, includes four of each of the L-STF 702, the L-LTF 704, the L-SIG 706, the HEW-SIGA1s 708, in an embodiment. In some embodiments, the modulation of different 20 MHz sub-bands signals is rotated by different angles. For example, in one embodiment, a first sub-band is rotated 0-degrees, a second sub-band is rotated 90-degrees, a third sub-band is rotated 180-degrees, and a fourth sub-band is rotated 270-degrees. In other embodiments, different suitable rotations are utilized. The different phases of the 20 MHz sub-band signals result in reduced peak to average power ratio (PAPR) of OFDM symbols in the data unit 700, in at least some embodiments. In an embodiment, if the data unit that conforms to the first communication protocol is an OFDM data unit that occupies a cumulative bandwidth such as 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 640 MHz, etc., the HEW-STF, the HEW-LTFs, the HEW-SIGB and the HEW data portion occupy the corresponding whole bandwidth of the data unit.
FIG. 7B is a set of diagrams illustrating modulation of the L-SIG 706, HEW-SIGA1 708-1, and HEW-SIGA2 708-2 of the data unit 700 of FIG. 7A, according to an embodiment. In this embodiment, the L-SIG 706, HEW-SIGA1 708-1, and HEW-SIGA2 708-2 fields have the same modulation as the modulation of the corresponding field as defined in the IEEE 802.11ac Standard and depicted in FIG. 6B. Accordingly, the HEW-SIGA1 field is modulated the same as the L-SIG field. On the other hand, the HEW-SIGA2 field is rotated by 90 degrees as compared to the modulation of the L-SIG field. In some embodiments having the third HEW-SIGA3 field, the HEW-SIGA2 field is modulated the same as the L-SIG field and the HEW-SIGA1 field, while the HEW-SIGA3 field is rotated by 90 degrees as compared to the modulation of the L-SIG field, the HEW-SIGA1 field, and the HEW-SIGA2 field.
In an embodiment, because the modulations of the L-SIG 706, HEW-SIGA1 708-1, and HEW-SIGA2 708-2 fields of the data unit 700 correspond to the modulations of the corresponding fields in a data unit that conforms to the IEEE 802.11ac Standard (e.g., the data unit 500 of FIG. 5), legacy client stations configured to operate according to the IEEE 802.11a Standard and/or the IEEE 802.11n Standard will assume, in at least some circumstances, that the data unit 700 conforms to the IEEE 802.11ac Standard and will process the data unit 700 accordingly. For example, a client station that conforms to the IEEE 802.11a Standard will recognize the legacy IEEE 802.11a Standard portion of the preamble of the data unit 700 and will set a duration of the data unit (or the data unit duration) according to a duration indicated in the L-SIG 706. For example, the legacy client station 25-4 will calculate a duration for the data unit based on a rate and a length (e.g., in number of bytes) indicated in the L-SIG field 706, according to an embodiment. In an embodiment, the rate and the length in the L-SIG field 706 are set such that a client station configured to operate according to a legacy communication protocol will calculate, based the rate and the length, a packet duration (T) that corresponds to, or at least approximates, the actual duration of the data unit 700. For example, the rate is set to indicate a lowest rate defined by the IEEE 802.11a Standard (i.e., 6 Mbps), and the length is set to a value computed such that packet duration computed using the lowest rate at least approximates the actual duration of the data unit 700, in one embodiment.
In an embodiment, a legacy client station that conforms to the IEEE 802.11a Standard, when receiving the data unit 700, will compute a packet duration for the data unit 700, e.g., using a rate field and a length field of L-SIG field 706, and will wait until the end of the computed packet duration before performing clear channel assessment (CCA), in an embodiment. Thus, in this embodiment, communication medium is protected against access by the legacy client station at least for the duration of the data unit 700. In an embodiment, the legacy client station will continue decoding the data unit 700, but will fail an error check (e.g., using a frame check sequence (FCS)) at the end of the data unit 700.
Similarly, a legacy client station configured to operate according to the IEEE 802.11n Standard, when receiving the data unit 700, will compute a packet duration (T) of the data unit 700 based on the rate and the length indicated in the L-SIG 706 of the data unit 700, in an embodiment. The legacy client station will detect the modulation of the first HEW signal field (HEW-SIGA1) 708-1 (BPSK) and will assume that the data unit 700 is a legacy data unit that conforms to the IEEE 802.11a Standard. In an embodiment, the legacy client station will continue decoding the data unit 700, but will fail an error check (e.g., using a frame check sequence (FCS)) at the end of the data unit. In any event, according to the IEEE 802.11n Standard, the legacy client station will wait until the end of a computed packet duration (T) before performing clear channel assessment (CCA), in an embodiment. Thus, communication medium will be protected from access by the legacy client station for the duration of the data unit 700, in an embedment.
A legacy client station configured to operate according to the IEEE 802.11ac Standard but not the first communication protocol, when receiving the data unit 700, will compute a packet duration (T) of the data unit 700 based on the rate and the length indicated in the L-SIG 706 of the data unit 700, in an embodiment. However, the legacy client station will not be able to detect, based on the modulation of the data unit 700, that the data unit 700 does not conform to the IEEE 802.11ac Standard, in an embodiment. In some embodiments, one or more HEW signal fields (e.g., the HEW-SIGA1 and/or the HEW-SIGA2) of the data unit 700 is/are formatted to intentionally cause the legacy client station to detect an error when decoding the data unit 700, and to therefore stop decoding (or “drop”) the data unit 700. For example, HEW-SIGA 708 of the data unit 700 is formatted to intentionally cause an error when the SIGA field is decoded by a legacy device according to the IEEE 802.11ac Standard, in an embodiment. Further, according to the IEEE 802.11ac Standard, when an error is detected in decoding the VHT-SIGA field, the client station will drop the data unit 700 and will wait until the end of a computed packet duration (T), calculated, for example, based on a rate and a length indicated in the L-SIG 706 of the data unit 700, before performing clear channel assessment (CCA), in an embodiment. Thus, communication medium will be protected from access by the legacy client station for the duration of the data unit 700, in an embodiment.
FIG. 8 is a diagram of an OFDM symbol 800, according to an embodiment. The data unit 700 of FIG. 7 includes OFDM symbols such as the OFDM symbols 800, in an embodiment. The OFDM symbol 800 includes a guard interval (GI) portion 802 and an information portion 804. In an embodiment, the guard interval comprises a cyclic prefix repeating an end portion of the OFDM symbol. In an embodiment, the guard interval portion 802 is used to ensure orthogonality of OFDM tones at a receiving device (e.g., the client station 25-1) and to minimize or eliminate inter-symbol interference due to multi-path propagation in the communication channel via which the OFDM symbol 800 is transmitted from a transmitting device (e.g., the AP 14) to the receiving device. In an embodiment, the length of the guard interval portion 802 is selected based on expected worst case channel delay spread in the communication channel between the transmitting device and the receiving device. For example, a longer guard interval is selected for outdoor communication channels typically characterized by longer channel delay spreads as compared to a shorter guard interval selected for indoor communication channels typically characterized by shorter channel delay spreads, in an embodiment. In an embodiment, the length of the guard interval portion 802 is selected based on a tone spacing (e.g., spacing between sub-carrier frequencies of the whole bandwidth of the data unit) with which the information portion 804 has been generated. For example, a longer guard interval is selected for a narrower tone spacing (e.g., 256 tones) as compared to a shorter guard interval for a wider tone spacing (e.g., 64 tones).
According to an embodiment, the guard interval portion 802 corresponds to a short guard interval, a normal guard interval, or a long guard interval, depending on mode of transmission being utilized. In an embodiment, the short guard interval or the normal guard interval is used for indoor communication channels, communication channels with relatively short channel delay spreads, or communication channels having suitably high SNR ratios, and the long guard interval is used for outdoor communication channels, communication channels with relatively long delay spreads, or communication channels not having suitably high SNR ratios. In an embodiment, the normal guard interval or the short guard interval is used for some or all OFDM symbols of an HEW data unit (e.g., the HEW data unit 700) when the HEW data unit is transmitted in the regular mode, and the long guard interval is used for at least some OFDM symbols of the HEW data unit when the HEW data unit is transmitted in the range extension mode.
In an embodiment, the short guard interval (SGI) has a length of 0.4 μs, the normal guard interval is 0.8 μs and the long guard interval (LGI) has a length of 1.2 μs or 1.8 μs. In an embodiment, the information portion 804 has a length of 3.2 μs. In other embodiments, the information portion 804 has an increased length that corresponds to the tone spacing with which the information portion 804 has been generated. For example, the information portion 804 has a first length of 3.2 μs for the regular mode using a first tone spacing of 64 tones and has a second length of 6.4 μs for a second tone spacing of 128 tones, where the second tone spacing and second length are both increased by an integer multiple of 2 as compared to the first tone spacing and first length. In an embodiment, the remaining length of the information portion 804 is filled with a copy of a received time-domain signal (e.g., the information portion 804 contains two copies of the received time-domain signal). In other embodiments, other suitable lengths for the SGI, the NGI, the LGI, and/or the information portion 804 are utilized. In some embodiments, the SGI has a length that is 50% of the length of the NGI, and the NGI has a length that is 50% of the length of the LGI. In other embodiments, the SGI has a length that is 75% or less of the length of the NGI, and the NGI has a length that is 75% or less of the length of the LGI. In other embodiments, the SGI has a length that is 50% or less of the length of the NGI, and the NGI has a length that is 50% or less of the LGI.
In other embodiments, OFDM modulation with reduced tone spacing is used in the range extension mode using a same tone plan (e.g., a predetermined sequence of indices that indicate which OFDM tones are designated for data tones, pilot tones, and/or guard tones). For example, whereas the regular mode for a 20 MHz bandwidth OFDM data unit uses a 64-point discrete Fourier transform (DFT), resulting in 64 OFDM tones (e.g., indices −32 to +31), the range extension mode uses a 128-point DFT for a 20 MHz OFDM data unit, resulting in 128 OFDM tones (e.g., indices −64 to +63) in the same bandwidth. In this case, tone spacing in the range extension mode OFDM symbols is reduced by a factor of two (1⁄2) compared to regular mode OFDM symbols while using the same tone plan. As another example, whereas the regular mode for a 20 MHz bandwidth OFDM data unit uses a 64-point discrete Fourier transform (DFT) resulting in 64 OFDM tones, the range extension mode uses a 256-point DFT for a 20 MHz OFDM data unit resulting in 256 OFDM tones in the same bandwidth. In this case, tone spacing in the range extension mode OFDM symbols is reduced by a factor of four (1⁄4) compared to the regular mode OFDM symbols. In such embodiments, long GI duration of, for example, 1.6 μs is used. However, the duration of the information portion of the range extension mode OFDM symbol is increased (e.g., from 3.2 μs to 6.4 μs), and the percentage of the GI portion duration to the total OFDM symbols duration remains the same, in an embodiment. Thus, in this case, loss of efficiency due to a longer GI symbol is avoided, in at least some embodiments. In various embodiments, the term “long guard interval” as used herein encompasses an increased duration of a guard interval as well as a decreased OFDM tone spacing that effectively increases duration of the guard interval.
FIG. 9A is a diagram illustrating an example data unit 900 in which the regular mode or range extension mode is used for a preamble of the data unit, according to an embodiment. The data unit 900 is generally the same as the data unit 700 of FIG. 7A and includes like-numbered elements with the data unit 700 of FIG. 7A. The HEW-SIGA field 708 (e.g., the HEW-SIGA1 708-1 or the HEW-SIGA2 708-2) of the data unit 900 includes a coding indication (CI) 902. According to an embodiment, the CI indication 902 is set to indicate one of (i) regular mode with a regular coding scheme or (ii) range extension mode with a range extension coding scheme. In an embodiment, the CI indication 902 comprises one bit, wherein a first value of the bit indicates the regular mode and a second value of the bit indicates the range extension mode. In some embodiments, the CI indication is combined with a modulation and coding scheme (MCS) indicator. In an embodiment, for example, the regular mode corresponds to MCS values which are determined to be valid by a legacy receiver device (e.g., in compliance with IEEE 802.11ac protocol), while the range extension mode corresponds to an MCS value that is determined to be invalid (or not supported) by the legacy receiver device (e.g., not in compliance with IEEE 802.11ac protocol). In other embodiments, the CI indication 902 has a plurality of bits that indicate a plurality of regular mode MCS values and a plurality of range extension mode MCS values. As illustrated in FIG. 9A, the regular coding scheme is used for all OFDM symbols of the preamble of the data unit 700, and one of the regular coding scheme or the range extension coding scheme, as indicated by the CI indication 902, is used for OFDM symbols of the data portion 716, in the illustrated embodiment.
In an embodiment, for example, where the range extension coding scheme is used for OFDM symbols of the data portion 716, the range and/or SNR at which successful decoding of PHY data units is generally improved (i.e., successful decoding at longer range and/or lower SNR) as compared to regular data units. In some embodiments, the improved range and/or SNR performance is not necessarily achieved for decoding of the preamble 701, which is generated using the regular coding scheme. In such embodiments, transmission of at least a portion of the preamble 701 with a transmission power boost, as compared to transmission power used for transmission of the data portion 716, to increase a decoding range of the portion of the preamble 701. In some embodiments, the portion of the preamble 701 that is transmitted with the transmission power boost includes legacy fields, such as the L-STF 702, L-LTF 704, and L-SIG 708, and/or non-legacy fields, such as the HEW-STF and HEW-LTF. In various embodiments, the transmission power boost is 3 dB, 6 dB, or other suitable values. In some embodiments, the transmission power boost is determined such that the “boosted” preamble 701 is decodable with similar performance as compared to the “unboosted” data portion 716 at a same location. In some embodiments, an increased length of the L-STF 702, L-LTF 704, and/or L-SIG 706 is used in combination with the transmission power boost. In other embodiments, the increased length of the L-STF 702, L-LTF 704, and/or L-SIG 706 is used instead of the transmission power boost.
FIG. 9B is a diagram illustrating an example data unit 950 in which the range extension coding scheme is used for a portion of a preamble of the data unit, according to an embodiment. The data unit 950 is generally the same as the data unit 900 of FIG. 9A, except that in the data unit 950 includes a preamble 751 in which the coding scheme indicated by the CI indication 902 is applied to OFDM symbols of a portion of the preamble 751 as well as to the OFDM symbols of the data portion 716. In particular, in the illustrated embodiment, the regular coding scheme is used for a first portion 751-1 of the preamble 701, and one of the regular coding scheme or the range extension coding scheme, as indicated by the CI indication 902, is used for OFDM symbols of a second portion 751-2 of the preamble 751, in addition to OFDM symbols of the data portion 716. Accordingly, the coding scheme indicated by the CI indication 902 skips the OFDM symbol that corresponds to the HEW-STF 710 and is applied beginning with the OFDM symbol that corresponds to the HEW-LTF 712-1, in the illustrated embodiment. Skipping the HEW-STF 710 allows the device receiving the data unit 950 sufficient time to decode the CI indication 902 and to properly set up the receiver to begin decoding OFDM symbols using the coding scheme indicated by the CI indication 902 prior to receiving such OFDM symbols, in at least some embodiments.
FIG. 10A is a diagram illustrating an example data unit 1000 in which OFDM tone spacing adjustment is used in combination with bit and/or symbol repetition for the range extension coding scheme, according to an embodiment. The data unit 1000 is generally the same as the data unit 900 of FIG. 7A, except that in the data unit 1000, when the CI indication 902 indicates that the range extension coding scheme is being utilized, the OFDM symbols of the data portion 716 are generated using OFDM modulation with reduced tone spacing compared to tone spacing used for regular mode OFDM symbols of the data unit 1000.
FIG. 10B is a diagram illustrating an example data unit 1050 in which OFDM tone spacing adjustment is used in combination with bit and/or symbol repetition for the range extension coding scheme, according to another embodiment. The data unit 1050 is generally the same as the data unit 950 of FIG. 9B, except that in the data unit 1050, when the CI indication 902 indicates that the range extension coding scheme is being utilized, the OFDM symbols of the second portion 751-2 and OFDM symbols of the data portion 716 are generated using OFDM modulation with reduced tone spacing compared to tone spacing used for regular mode OFDM symbols of the data unit 1050. In the embodiment shown in FIG. 10A, an overall bandwidth of 20 MHz is used with normal tone spacing and guard interval in the first portion 751-1 and tone spacing reduced by 2, long guard interval, and an FFT size of 64 repeated twice across the overall bandwidth. In some embodiments, a transmission power boost is applied to the first portion 751-1. In other embodiments, other multiples such as 4×, 8×, or other suitable values are used for one or more of reduced tone spacing, increased guard interval, increased symbol duration, or increased repetition across overall bandwidth.
In some embodiments, a different preamble format is used for range extension mode data units compared to the preamble used for regular mode data units. In such embodiments, a device receiving a data unit can automatically detect whether the data unit is a regular mode data unit or a range extension mode data unit based on the format of the preamble of the data unit. FIG. 11A is a diagram illustrating a regular mode data unit 1100, according to an embodiment. The regular mode data unit 1100 includes a regular mode preamble 1101. The regular mode preamble 1101 is generally the same as the preamble 701 of the data unit 700 of FIG. 7A. In an embodiment, the preamble 1101 includes a HEW-SIGA field 1108, which includes a first HEW-SIGA1 field 1108-1 and a second first HEW-SIGA2 field 1108-1. In an embodiment, the HEW-SIGA field 1108 (e.g., the HEW-SIGA1 1108-1 or the HEW-SIGA2 1108-2) of the preamble 1101 includes a CI indication 1102. The CI indication 1102 is set to indicate whether the range extension coding scheme or the regular coding scheme is used for OFDM symbols of the data portion 716 of the data unit 1100, in an embodiment. In an embodiment, the CI indication 1102 comprises one bit, wherein a first value of the bit indicates the regular coding scheme and a second value of the bit indicates the range extension coding scheme. As will be explained in more detail below, a device receiving the data unit 1100 is able to detect, based on the format of the preamble 1101, that the preamble 1101 is a regular mode preamble, and not an extension mode preamble, in an embodiment. Upon detecting that the preamble 1101 is the regular mode preamble, the receiving device determines, based on the CI indication 1102, whether the range extension coding scheme or the regular coding scheme is used for OFDM symbols of the data portion 716, and decodes the data portion 716 accordingly, in an embodiment. In some embodiments, when the CI indication 1102 indicates that the range extension coding scheme is being utilized, the OFDM symbols of a portion of the preamble 1101 (e.g., the HEW-LTFs and HEW-SIGB, as and OFDM symbols of the data portion 716 are generated using OFDM modulation with smaller tone spacing compared to tone spacing used for regular mode OFDM symbols of the data unit 1050
FIG. 11B is a diagram illustrating a range extension mode data unit 1150, according to an embodiment. The range extension mode data unit 1150 includes a range extension mode preamble 1151. The data unit 1150 is generally similar to the data unit 1100 of FIG. 11A, except that the preamble 1151 of the data unit 1150 is formatted differently from the preamble 1101 of the data unit 1100. In an embodiment, the preamble 1151 is formatted such that a receiving device that operates according to the HEW communication protocol is able to determine that the preamble 1151 is a range extension mode preamble rather than a regular mode preamble. In an embodiment, the range extension mode preamble 1151 includes an L-STF 702, an L-LTF 704, and an L-SIG 706, and one or more first HEW signal fields (HEW-SIGAs) 1152. In an embodiment, the preamble 1150 further includes one or more secondary L-SIG(s) 1154 that follow the L-SIG field 706. The secondary L-SIG(s) 1154 are followed by a second L-LTF field (L-LTF2) 1156, in some embodiments. In other embodiments, the preamble 1151 omits the L-SIG(s) 1154 and/or the L-LTF2 1156. In some embodiments, the preamble 1151 also includes an HEW-STF 1158, one or more HEW-LTF fields 1160, and a second HEW signal field (HEW-SIGB) 1162. In other embodiments, the preamble 1151 omits the HEW-STF 1158, the HEW-LTF(s) 1160 and/or the HEW-SIGB 1162. In an embodiment, the data unit 1150 also includes a data portion 716 (not shown in FIG. 11B). In some embodiments, the HEW signal fields (HEW-SIGAs) 1152 are modulated using a same range extension coding scheme as the data field 716.
In an embodiment, one or more symbols of the HEW-SIGAs 1152 is modulated using QBPSK instead of BPSK, for example, to allow autodetection between the regular mode and the range extension mode by the receiving device that operates according to the HEW communication protocol. In an embodiment, for example, where the regular mode preamble includes two BPSK symbols and one Q-BPSK symbol after the L-SIG 706 field, the range extension mode preamble includes three BPSK symbols and one Q-BPSK symbol after the L-SIG 706 field. In an embodiment, for example, when using a 4× bit-wise repetition of MCS0 with 48 data tones in each 64-FFT (20 MHz). In some embodiments, for example, where autodetection differentiate the regular mode from the range extension mode, some bits are omitted from the HEW-SIGAs 1152, such as bits used to indicate signal bandwidth, MCS value, or other suitable bits.
In one embodiment in which the preamble 1151 includes one or more secondary L-SIG(s) 1154, the content of each of the L-SIG(s) 1154 is the same as the content of the L-SIG 706 of the data unit 1150. In an embodiment, a receiving device receiving the data unit 1150 determines that the preamble 1151 corresponds to a range extension mode preamble by detecting the repetition(s) of the L-SIG fields 706, 1154. Further, in an embodiment, both a rate subfield and a length subfield of the L-SIG 706, and, accordingly, the rate subfield(s) and the length subfield(s) of the secondary L-SIG(s) 1154 are set to fixed (e.g., predetermined) values. In this case, upon detecting the repetition(s) of the L-SIG fields 706, 1154, the receiving device uses the fixed values in the repeating L-SIG fields as additional training information to improve channel estimation, in an embodiment. In some embodiments, however, at least the length subfield of the L-SIG 706, and accordingly at least the length fields of the secondary L-SIG(s) 1154, is not set to a fixed value. For example, the length field is instead set to a value determined based on the actual length of the data unit 1150, in an embodiment. In one such embodiment, the receiving device first decodes the L-SIG 706, and then detects the repetition(s) of the L-SIG fields 706, 1154 using the value of the length subfield in L-SIG 706. In another embodiment, the receiving device first detects the repetition(s) of the L-SIG fields 706, 1154, and then combines the detected multiple L-SIG fields 706, 1154 to improve decoding reliability of the L-SIG fields 706, 1154 and/or uses the redundant information in the multiple L-SIG fields 706, 1154 to improve channel estimation.
In an embodiment in which the preamble 1151 includes L-LTF2 1156, the OFDM symbol(s) of the L-LTF2 1156 are generated using the range extension coding scheme. In another embodiment in which the preamble 1151 includes L-LTF2 11156, the OFDM symbol(s) of the L-LTF2 1156 are generated using the regular coding scheme. For example, if a double guard interval (DGI) used in the L-LTF 704 is sufficiently long for the communication channel in which the data unit 1150 travels from the transmitting device to the receiving device, then OFDM symbols of the L-LTF2 1156 are generated using the regular coding scheme or, alternatively, the preamble 1151 omits the L-LTF2 1156, in an embodiment.
In another embodiment, the preamble 1151 omits the secondary L-SIG(s) 1154, but includes the L-LTF2 1156. In this embodiment, a receiving device detects that the preamble 1151 is the range extension mode preamble by detecting the presence of the L-LTF2 1156. FIGS. 12A-12B are diagrams illustrating two possible formats of LTFs suitable for use as the L-LTF2 1156 according to two example embodiments. Turning first to FIG. 12A, in a first example embodiment, an L-LTF2 1200 is formatted in the same manner as the L-LTF 704, i.e., as defined by a legacy communication protocol (e.g., the IEEE 802.11a/n/ac Standards). In particular, in the illustrated embodiment, the L-LTF2 1200 includes a double guard interval (DGI) 1202 followed by two repetitions of a long training sequence 1204, 1206. Turning now to FIG. 12B, in another example embodiment, an L-LTF2 1208 is formatted differently from the L-LTF 704. In particular, in the illustrated embodiment, the L-LTF2 1208 includes a first normal guard interval 1210, a first repetition of a long training sequence 1212, a second normal guard interval 1214, and a second repetition of the long training sequence 1216.
Referring back to FIG. 11B, in an embodiment, the HEW-SIGA(s) 1152 are generated using the range extension coding scheme. In an embodiment, the number of the HEW-SIGAs 1152 is the same as the number of the HEW-SIGA(s) 1108 of the regular mode preamble 1101. Similarly, in an embodiment, the content of the HEW-SIGAs 1152 is the same as the content of the HEW-SIGA(s) 1108 of the regular mode preamble 1101. In other embodiments, the number and/or the content of the HEW-SIGAs 1152 is different from the number and/or content of the HEW-SIGA(s) 1108 of the regular mode preamble 1101. A device receiving the data unit 1150 decodes the HEW-SIGA(s) 1152 using the range extension coding scheme based on detecting that the preamble 1151 corresponds to the range extension mode preamble and interprets the HEW-SIGA(s) 1152 appropriately as defined for the range extension mode, in an embodiment.
In an embodiment in which the preamble 1151 omits the L-SIG(s) 1154 and/or L-LTF2 1156, a receiving device determines whether a preamble corresponds to the range extension mode preamble 1151 or to the normal mode preamble 1101 by detecting whether the HEW-SIGA field in the preamble is generated using the range extension coding scheme or the regular coding scheme based on auto-correlation of the HEW-SIGA field using the range extension coding scheme and the regular coding scheme. FIGS. 13A-13B are diagrams of the HEW-SIGA 1108 of the regular mode preamble 1101 and the HEW-SIGA 1152 of the range extension mode preamble 1151, respectively, according to an embodiment. In the illustrated embodiment, the HEW-SIGA 1108 of the regular mode preamble 1101 includes a first NGI 1302, a first HEW-SIGA field 1304, a second NGI 1306, and a second HEW-SIGA field 1308. On the other hand, the HEW-SIGA 1152 of the range extension mode preamble 1151 includes a first LGI 1310, a first HEW-SIGA field 1312, a second LGI 1314, and a second HEW-SIGA field 1312. In an embodiment, a receiving device performs a first auto-correlation of the HEW-SIGA field using a normal guard interval structure, such as the structure illustrated in FIG. 13A, performs a second auto-correlation using a long guard interval structure, such as the structure illustrated in FIG. 13B, and performs a comparison of the auto-correlation results. If auto-correlation of the HEW-SIGA field using the long guard interval produces a greater result compared to the result of the auto-correlation of the HEW-SIGA field using the normal guard interval, then the receiving device determines that the preamble corresponds to the range extension mode preamble 1151, in an embodiment. On the other hand, if auto-correlation of the HEW-SIGA field using the normal guard interval produces a greater result compared to the result of auto-correlation of the HEW-SIGA field with the long guard interval, then the receiving device determines that the preamble corresponds to the regular mode preamble 1101, in an embodiment.
Referring again to FIG. 11B, in an embodiment, the preamble 1151 is formatted such that a legacy client station can determine a duration of the data unit 1150 and/or that the data unit does not conform to a legacy communication protocol. Additionally, the preamble 1151 is formatted such that a client station that operates according to the HEW protocol is able to determine that the data unit conforms to the HEW communication protocol, in an embodiment. For example, at least two OFDM symbols immediately following the L-SIG 706 of the preamble 1151, such as the L-SIG(s) 1154 and/or the L-LTF2 1156 and/or the HEW-SIGA(s) 1152, are modulated using BPSK modulation. In this case, a legacy client station will treat the data unit 1150 as a legacy data unit, will determine a duration of the data unit based on the L-SIG 706, and will refrain from accessing the medium for the determined duration, in an embodiment. Further, one or more other OFDM symbols of the preamble 1151, such as one or more of the HEW-SIG(s) 1152 are modulated using Q-BPSK modulation, allowing a client station operating according to the HEW communication protocol to detect that the data unit 1150 conforms to the HEW communication protocol, in an embodiment.
In some embodiments, the HEW communication protocol allows beamforming and/or multi user MIMO (MU-MIMO) transmission in the range extension mode. In other embodiments, the HEW communication protocol allows only single stream and/or only single user transmission in the range extension mode. With continued reference to FIG. 11B, in an embodiment in which the preamble 1151 includes the HEW-STF 1158 and the HEW-LTF(s) 1160, the AP 14 applies beamforming and/or multi-user transmission beginning with the HEW-STF 1158. In other words, the fields of the preamble 1151 precede the HEW-STF 1158 are omni-directional and, in multi-user mode, are intended to be received by all intended recipients of the data unit 1150, while the HEW-STF field 1158, as well as the preamble fields that follow the HEW-STF field 1158 and the data portion that follows the preamble 1151, are beam-formed and/or include different portions intended to be received by different intended recipients of the data unit 1150, in an embodiment. In an embodiment, the HEW-SIGB field 1162 includes user-specific information for the intended recipients of the data unit 1150 in MU-MIMO mode. The HEW-SIGB field 1162 is generated using the regular coding scheme or the range extension coding scheme, depending on an embodiment. Similarly, the HEW-STF 1158 is generated using the regular coding scheme or the range extension coding scheme, depending on an embodiment. In an embodiment, the training sequence used on the HEW-STF 1158 is the sequence defined in a legacy communication protocol, such as in the IEEE 802.11ac protocol.
On the other hand, in an embodiment in which the preamble 1151 omits the HEW-STF 1158 and the HEW-LTF(s) 1160, beamforming and MUMIMO are not allowed in the extension guard interval mode. In this embodiment, only single user single stream transmission is allowed in the extension guard interval mode. In an embodiment, a receiving device obtains a single stream channel estimate based on the L-LTF field 704, and demodulates the data portion of the data unit 1150 based on the channel estimate obtained based on the L-LTF field 704.
In some embodiments, a receiver device uses the HEW-STF field 1158 to re-start an automatic gain control (AGC) process for receiving the data portion 716. The HEW-STF has a same duration as the VHT-STF (i.e., 4 microseconds), in an embodiment. In other embodiments, the HEW-STF has a longer duration than the VHT-STF. In an embodiment, the HEW-STF has a same time-domain periodicity as the VHT-STF, such that in the frequency domain there are one non-zero tones every 4 tones and using a same tone spacing as IEEE 802.11ac. In other embodiments having a 1/N tone spacing, the HEW-STF has one non-zero tone in every 4*N tones. In embodiments where the overall bandwidth for the data unit is greater than 20 MHz, (e.g., 40 MHz, 80 MHz, etc.), the HEW-STF uses the same wider bandwidth VHT-STF as in IEEE 802.11ac (i.e., a duplication of the 20 MHz VHT-STF for overall bandwidth of 40 MHz, 80 MHz, 160 MHz, etc.).
FIG. 14A is a block diagram illustrating a range extension mode data unit 1400, according to an embodiment. The data unit 1400 includes a range extension mode preamble 1401. The range extension mode preamble 1401 is generally similar to the range extension mode preamble 1151 of FIG. 11B, except that the L-SIG 706 and the secondary L-SIG 1154 of the preamble 1151 are combined into a single L-SIG field 1406 in the preamble 1401. FIG. 14B is a diagram illustrating the L-SIG field 1406 according to one embodiment. In the embodiment of FIG. 14B, the L-SIG field 1406 includes a double guard interval 1410, a first L-SIG field 1412, which includes contents of L-SIG field 706 of the preamble 1151, and a second L-SIG field 1414, which includes contents of the secondary L-SIG2 field 1154 of the preamble 1151. In various embodiments, L-SIG field 1406 includes a length subfield set to a fixed value or set to a variable value, as discussed above with respect to the L-SIG fields 706, 1154 of FIG. 11B. In various embodiments, redundant (repeated) bits in L-SIG field 1406 are used for improved channel estimation as discussed above with respect to L-SIG fields 706, 1154 of FIG. 11B.
In an embodiment, a legacy client station receiving the data unit 1400 assumes that the L-SIG field 1406 includes a normal guard interval. As illustrated in FIG. 14C, the FFT window for L-SIG information bits assumed at the legacy client station is shifted compared to the actual L-SIG field 1412, in this embodiment. In an embodiment, to ensure that constellation points within the FFT window correspond to BPSK modulation, as expected by the legacy client station, and thus to allow the legacy client station to properly decode the L-SIG field 1412, modulation of the L-SIG field 1412 is phase-shifted relative to regular BPSK modulation. For example, in a 20 MHz OFDM symbol, if the normal guard interval is 0.8 μs, and the double guard interval is 1.6 μs, then modulation of an OFDM tone k of the L-SIG field 1412 is shifted with respect to the corresponding OFDM tone k of the original L-SIG as can be seen from:

SLSIG(k)=SSLSIG-LSIG(k)e−j·2π·0.8·20/64=SSLSIG-LSIG(k)·(−j)  Equation 1

Accordingly, in an embodiment, L-SIG field 1412 is modulated using reverse Q-BPSK rather than regular BPSK. Thus, for example, a bit of value 1 is modulated onto −j, and a bit of value 0 is modulated onto j, resulting in {j, −j} modulation rather than the regular {1, −1} BPSK modulation, in an embodiment. In an embodiment, due to the reverse Q-BPSK modulation of the L-SIG field 1412, a legacy client station can properly decode the L-SIG field 1412 an determine the duration of the data unit 1400 based on the L-SIG 1412 field, in an embodiment. A client station that operates according to the HEW protocol, on the other hand, can auto-detect that the preamble 1401 is a range extension mode preamble by detecting the repetition of the L-SIG field 1412 or by detecting the reverse Q-BPSK modulation of the L-SIG field within the FFT window of the legacy client station, in an embodiment. Alternatively, in other embodiments, a client station that operates according to the HEW protocol detects that the preamble 1401 is a range extension mode preamble using other detection methods discussed above, such as based on modulation or format of the HEW-SIGA field(s) 1152.

Referring FIGS. 11A-11B and 14A, long guard interval is used for initial OFDM symbols of both a regular mode preamble (e.g., the preamble 1101) and a range extension mode preamble (e.g., the preamble 1151 or the preamble 1401), in some embodiments. For example, referring to FIGS. 11A-11B, the L-STF field 702, the L-LTF field 704 and the L-SIG field 706, 1154, and HEW-SIGA field 1152 is each generated using the long guard interval, in an embodiment. Similarly, referring to FIG. 14A, the L-STF field 702, the L-LTF field 704, the L-SIG field 1406, and the HEW-SIGA(s) 1152 are generated using the long guard interval, in an embodiment. In an embodiment, a receiving device can determine whether a preamble corresponds to the regular mode preamble or the range extension mode preamble based on modulation of the HEW-SIGA field 1152 (e.g., Q-BPSK) or based on an indication included in the HEW-SIGA field 1152, in various embodiments. Further, similar to the preamble 1151 of FIG. 11B, the preamble 1401 of FIG. 14A includes or omits the second L-LTF2 field 1156, depending on the embodiment and/or scenario.
FIG. 15 is a block diagram illustrating a format of an HEW-SIGA field 1500, according to an embodiment. In some embodiments, the HEW-SIGA field(s) 1152 of the data unit 1150 or the data unit 1400 are formatted as the HEW-SIGA field 1500. In some embodiments, the HEW-SIGA field(s) 1108 are formatted as the HEW-SIGA field 1500. The HEW-SIGA field 1500 includes a double guard interval 1502, a first repetition of a HEW-SIGA field 1504 and a second repetition of a HEW-SIGA field 1506. In an example embodiment, the DGI is 1.8 μs and each repetition of HEW-SIGA is 3.2 μs. In an embodiment, the repeated bits in the HEW-SIGA field 1500 are used to increase reliability of decoding of the HEW-SIGA field 1500. In an embodiment, the format of the HEW-SIGA field 1500 is used to auto-detect a range extension mode preamble based on a comparison between auto-correlation of the HEW-SIGA field of the preamble using the format of the HEW-SIGA field 1500 and auto-correlation of the HEW-SIGA field of the preamble using the regular HEW-SIGA field format used in the regular mode, such as the format illustrated in FIG. 13A. In some embodiments, the HEW-SIGA field 1500 is modulated using less redundancy as compared to the data portion 716, because the additional time domain repetition of the HEW-SIGA field 1500 provides a sufficient improvement in decoding performance.
FIG. 16 is a block diagram illustrating an example PHY processing unit for generating regular mode data units using the regular coding scheme, according to an embodiment. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1600. In various embodiments and/or scenarios, the PHY processing unit 1600 generates range extension data units such as one of the data units of FIG. 9A, 9B, 10A, or 10B, for example. The PHY processing unit 1600 includes a scrambler 1602 that generally scrambles an information bit stream to reduce the occurrence of long sequences of ones or zeros. An FEC encoder 1606 encodes scrambled information bits to generate encoded data bits. In one embodiment, the FEC encoder 1606 includes a binary convolutional code (BCC) encoder. In another embodiment, the FEC encoder 1606 includes a binary convolutional encoder followed by a puncturing block. In yet another embodiment, the FEC encoder 1606 includes a low density parity check (LDPC) encoder. An interleaver 1610 receives the encoded data bits and interleaves the bits (i.e., changes the order of the bits) to prevent long sequences of adjacent noisy bits from entering a decoder at the receiver. A constellation mapper 1614 maps the interleaved sequence of bits to constellation points corresponding to different subcarriers of an OFDM symbol. More specifically, for each spatial stream, the constellation mapper 1614 translates every bit sequence of length log2(M) into one of M constellation points.
The output of the constellation mapper 1614 is operated on by an inverse discrete Fourier transform (IDFT) unit 1618 that converts a block of constellation points to a time-domain signal. In embodiments or situations in which the PHY processing unit 1600 operates to generate data units for transmission via multiple spatial streams, the cyclic shift diversity (CSD) unit 1622 inserts a cyclic shift into all but one of the spatial streams to prevent unintentional beamforming. The output of the CSD unit 1622 is provided to the guard interval (GI) insertion and windowing unit 1626 that prepends, to an OFDM symbol, a circular extension of the OFDM symbol and smooths the edges of each symbol to increase spectral decay. The output of the GI insertion and windowing unit 1626 is provided to the analog and radio frequency (RF) unit 1630 that converts the signal to analog signal and upconverts the signal to RF frequency for transmission.
In various embodiments, the range extension mode corresponds to a lowest data rate modulation and coding scheme (MCS) of the regular mode and introduces redundancy or repetition of bits into at least some fields of the data unit or repetition of symbols to further reduce the data rate. For example, the range extension mode introduces redundancy into the data portion and/or the non-legacy signal field of a range extension mode data unit or repetition of symbols according to one or more range extension coding schemes described below, in various embodiments and/or scenarios. As an example, according to an embodiment, regular mode data units are generated according a regular coding scheme. In various embodiments, the regular coding scheme is a modulation and coding scheme (MCS) selected from a set of MCSs, such as MCS0 (binary phase shift keying (BPSK) modulation and coding rate of 1⁄2) to MCS9 (quadrature amplitude modulation (QAM) and coding rate of 5⁄6), with higher order MCSs corresponding to higher data rates. Range extension mode data units, in one such embodiment, are generated using a range extension coding scheme, such as a modulation and coding as defined by MCS0 and with added bit repetition, block encoding, or symbol repetition that further reduce the data rate.
FIG. 17A is a block diagram of an example PHY processing unit 1700 for generating range extension mode data units using a range extension coding scheme, according to an embodiment. In some embodiments, the PHY processing unit 1700 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1700.
The PHY processing unit 1700 is similar to the PHY processing unit 1600 of FIG. 16 except that the PHY processing unit 1700 includes a block coder 1704 coupled to a scrambler 1702. In an embodiment, the block coder 1704 reads incoming (scrambled) information bits one block at a time, generates a number of copies of each block (or each bit in a block), interleaves the resulting bits according to the range extension coding scheme and outputs the interleaved bits for further encoding by a FEC encoder 1706 (e.g., a binary convolutional encoder). Generally, each block contains the number of information bits that, after having been encoded by the block coder 1704 and by the FEC encoder 1706, fill the data tones of a single OFDM symbol, according to an embodiment. As an example, in one embodiment, the block coder 1704 generates two copies (2× repetition) of each block of 12 information bits to generate 24 bits to be included in an OFDM symbol. The 24 bits are then encoded by the FEC encoder 1706 at the coding rate of 1⁄2 to generate 48 bits that modulate 48 data tones of an OFDM symbol (e.g., using BPSK modulation). As another example, in another embodiment, the block coder 1704 generates four copies (4× repetition) of each block of 6 information bits to generate 24 bits which are then encoded by the FEC encoder 1706 at the coding rate of 1⁄2 to generate 48 bits that modulate 48 data tones of an OFDM symbol. As yet another example, in another embodiment, the block coder 1704 generates two copies (2× repetition) of each block of 13 information bits to generate 26 bits which are then encoded by the FEC encoder 1706 at the coding rate of 1⁄2 to generate 52 bits that modulate 52 data tones of an OFDM symbol. In other embodiments, the block coder 1704 and FEC encoder 1706 are configured to generate 104, 208, or any suitable number of bits for modulation of data tones of an OFDM symbol.
In some embodiments, the block coder 1704 applies a 4× repetition scheme when generating a data (or a signal) field as defined by MCS0 as specified in the IEEE 802.11n Standard for 20 MHz channel, i.e., with 52 data tones per OFDM symbol. In this case, according to an embodiment, the block coder 1704 generates four copies of each block of 6 information bits to generate 24 bits and then adds two padding bits (i.e., two bits of a predetermined values) to provide the specified number of bits (i.e., 26 bits for 52 data tones) to the BCC encoder which encoded the 26 bits using the coding rate of 1⁄2 to generate 52 coded bits for modulating the 52 data tones.
In one embodiment, the block coder 1704 utilizes a “block level” repetition scheme in which each block of n bits is repeated m consecutive times. As an example, if m is equal to 4 (4× repetitions), the block coder 1704 generates a sequence [C, C, C, C], where C is a block of n bits, according to an embodiment. In another embodiment, the block coder 1704 utilizes a “bit level” repetition scheme in which each incoming bit is repeated m consecutive times. In this case, in an embodiment, if m is equal to 4 (4× repetitions), the block coder 1704 generates the sequence [b1 b1 b1 b1 b2 b2 b2 b2 b3 b3 b3 b3 . . . ], where b1 is the first bit in the block of bits, b2 is the second bit, and so on. In yet another embodiment, the block coder 1704 generates m number of copies of the incoming bits and interleaves the resulting bit stream according to any suitable code. Alternatively, in still another embodiment, the block coder 1704 encodes incoming bits or incoming blocks of bits using any suitable code, e.g., a Hamming block code with the coding rate of a 1⁄2, 1⁄4, etc., or any other block code with the coding rate of 1⁄2, 1⁄4, etc. (e.g., (1,2) or (1, 4) block code, (12,24) block code or (6, 24) block code, a (13,26) block code, etc.).
According to an embodiment, the effective coding rate corresponding to a combination of the coding performed by the block coder 1704 and coding performed by the FEC encoder 1706 the product of the two coding rates. For example, in an embodiment in which the block coder 1704 utilizes 4× repetition (or coding rate of 1⁄4) and the FEC encoder 1706 utilizes a coding rate of 1⁄2, the resulting effective coding rate is equal to 1⁄8. As a result of the reduced coding rate compared to the coding rate used to generate a similar regular mode data unit, data rate in range extension mode is effectively reduced by a factor corresponding to the number the coding rate applied by the block coder 1704 (e.g., a factor of 2, a factor of 4, etc.), according to an embodiment.
According to some embodiments, the block coder 1704 utilizes the same block coding scheme for generating the signal field of a control mode data unit as the block coding scheme used for generating the data portion of the control mode data unit. For instance, in an embodiment, an OFDM symbol of the signal field and an OFDM symbol of the data portion each includes 48 data tones, and in this embodiment, the block coder 1704 applies a 2× repetition scheme to blocks of 12 bits for the signal field and the data portion, for example. In another embodiment, the data portion and the signal field of a control mode data unit are generated using different block coding schemes. For example, in an embodiment, the long range communication protocol specifies a different number of data tones per OFDM symbol in the signal field compared to the number of data tones per OFDM symbol in the data portion. Accordingly, in this embodiment, the block coder 1704 utilizes a different block size and, in some embodiments, a different coding scheme, when operating on the signal field compared to the block size and the coding scheme used for generating the data portion. For example, if the long range communication protocol specifies 52 data tones per OFDM symbol of the signal field and 48 data tones per OFDM tones of the data portion, the block coder 1704 applies a 2× repetition scheme to blocks of 13 bits of the signal field and a 2× repetition scheme to blocks of 12 bits of the data portion, according to one embodiment.
The FEC encoder 1706 encodes the block coded information bits, according to an embodiment. In an embodiment, BCC encoding is performed continuously over the entire field being generated (e.g., the entire data field, the entire signal field, etc.). Accordingly, in this embodiment, information bits corresponding to the field being generated are partitioned into blocks of a specified size (e.g., 6 bits, 12 bits, 13 bits, or any other suitable number of bits), each block is processed by the block coder 1704, and the resulting data stream is then provided to the FEC encoder 1706 which continuously encodes the incoming bits.
Similar to the interleaver 1610 of FIG. 16, in various embodiments, the interleaver 1710 changes the order of bits in order to provide diversity gain and reduce the chance that consecutive bits in a data stream will become corrupted in the transmission channel. In some embodiments, however, the block coder 1704 provides sufficient diversity gain and the interleaver 1710 is omitted. In some embodiments, the interleaver 1710 or the FEC encoder 1706 provides the bits to the constellation mapper 1614 for transmission, as described above.
In some embodiments, information bits in the data portion of a range extension mode data unit are be padded (i.e., a number of bits of a known value is added to the information bits) so that the data unit occupies an integer number of OFDM symbols, for example. Referring to FIG. 1, in some embodiments, padding is implemented in the MAC processing unit 18, 28 and/or the PHY processing unit 20, 29. In some such embodiments, the number of padding bits is determined according to padding equations provided in a short range communication protocol (e.g., the IEEE 802.11a Standard, the IEEE 802.11n Standard, the IEEE 802.11ac Standard, etc.). In general, these padding equations involve computing a number of padding bits based, in part, on a number of data bits per OFDM symbol (NDBPS) and/or a number coded data bits per symbol (NCBPS). In range extension mode, according to an embodiment, the number of padding bits is determined based on the number of information bits in an OFDM symbol (e.g., 6 bits, 12 bits, 13 bits, etc.) before the information bits are block encoded by the block coder 1704 and BCC encoded by the FEC encoder 1706. Accordingly, the number of padding bits in a range extension mode data unit is generally different from the number of padding bits in the corresponding regular mode data (or in the corresponding short range data unit). On the other hand, according to an embodiment, the number of coded bits per symbol is the same as the number of coded bits per symbol in regular mode data unit (or in the corresponding short range data unit), e.g., 24, 48, 52, etc. coded bits per OFDM.
FIG. 17B is a block diagram of an example PHY processing unit 1750 for generating range extension mode data units, according to another embodiment. In some embodiments, the PHY processing unit 1750 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1750.
The PHY processing unit 1750 is similar to the PHY processing unit 1700 of FIG. 17A, except that in the PHY processing unit 1750, the FEC encoder 1706 is replaced by the LDPC encoder 1756. Accordingly, in this embodiment, the output of the block coder 1704 is provided for further block encoding by the LDPC encoder 1756. In an embodiment, the LDPC encoder 1756 utilizes a block code corresponding to a coding rate of 1⁄2, or a block code corresponding to another suitable coding rate. In the illustrated embodiment, the PHY processing unit 1750 omits the interleaver 1710 because adjacent bits in an information stream are generally spread out by the LDPC code itself and no further interleaving is needed. Additionally, in an embodiment, further frequency diversity is provided by the LDPC tone remapping unit 1760. According to an embodiment, the LDPC tone remapping unit 1760 reorders coded information bits or blocks of coded information bits according to a tone remapping function. The tone remapping function is generally defined such that consecutive coded information bits or blocks of information bits are mapped onto nonconsecutive tones in the OFDM symbol to facilitate data recovery at the receiver in cases in which consecutive OFDM tones are adversely affected during transmission. In some embodiments, the LDPC tone remapping unit 1760 is omitted. Referring again to FIG. 17A, in various embodiments, a number of tail bits are typically added to each field of a data unit for proper operation of the FEC encoder 1706, e.g., to ensure that the BCC encoder, after having encoded each field, is brought back to zero state. In one embodiment, for example, six tail bits are inserted at the end of the data portion before the data portion is provided to the FEC encoder 1706 (e.g., after the bits are processed by the block coder 1704).
In some embodiments, the signal field of a range extension mode data unit has a different format compared to the signal field format of a regular mode data unit. In some such embodiment, the signal field of range extension mode data units is shorter compared to a signal field of a regular mode data unit. For example, only one modulation and coding scheme is used in range extension mode, according to an embodiment, and therefore less information (or no information) regarding modulation and coding needs to be communicated in the range extension mode signal field. Similarly, in an embodiment, maximum length of a range extension mode data unit is shorter compared to a maximum length of a regular mode data unit and, in this case, less bits are needed for the length subfield of the range extension mode signal field. As an example, in one embodiment, a range extension mode signal field is formatted according to the IEEE 802.11n Standard but omits certain subfields (e.g., the low density parity check (LDPC) subfield, the space time block coding (STBC) subfield, etc.). Additionally or alternatively, in some embodiments, a range extension mode signal field includes a shorter CRC subfield compared to the cyclic redundancy check (CRC) subfield of a regular mode signal field (e.g., less than 8 bits). In general, in range extension mode, certain signal field subfields are omitted or modified and/or certain new information is added, according to some embodiments.
FIG. 18A is a block diagram of an example PHY processing unit 1800 for generating range extension mode data units using a range extension coding scheme, according to another embodiment. In some embodiments, the PHY processing unit 1800 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1800.
The PHY processing unit 1800 is similar to the PHY processing unit 1700 of FIG. 17A, except that in the PHY processing unit 1800 a block coder 1808 is located after an FEC encoder 1806. Accordingly, in this embodiment, information bits are first scrambled by scrambler 1802, encoded by the FEC encoder 1806 and the FEC coded bits are then replicated or otherwise block encoded by the block coder 1808. As in the example embodiment of the PHY processing unit 1700, in an embodiment, processing by the FEC encoder 1806 is performed continuously over the entire field being generated (e.g., the entire data portion, the entire signal field, etc.). Accordingly, in this embodiment, information bits corresponding to the field being generated are first encoded by the FEC encoder 1806 and the BCC coded bits are then partitioned into blocks of a specified size (e.g., 6 bits, 12 bits, 13 bits, or any other suitable number of bits). Each block is then processed by the block coder 1808. As an example, in one embodiment, the FEC encoder 1806 encodes 12 information bits per OFDM symbol using the coding rate of 1⁄2 to generate 24 BCC coded bits and provides the BCC coded bits to the block coder 1808. In an embodiment, the block coder 1808 generates two copies of each incoming block and interleaves the generated bits according to a range extension coding scheme coding scheme to generate 48 bits to be included in an OFDM symbol. In one such embodiment, the 48 bits correspond to 48 data tones generated using a Fast Fourier Transform (FFT) of size 64 at the IDFT processing unit 1818. As another example, in another embodiment, the FEC encoder 1806 encodes 6 information bits per OFDM symbol using the coding rate of 1⁄2 to generate 12 BCC coded bits and provides the BCC coded bits to the block coder 1808. In an embodiment, the block coder 1808 generates two copies of each incoming block and interleaves the generated bits according to a range extension coding scheme to generate 24 bits to be included in an OFDM symbol. In one such embodiment, the 24 bits correspond to 24 data tones generated using an FFT of size 32 at the IDFT processing unit 1818.
Similar to the block coder 1704 of FIG. 17A, the range extension coding scheme used by the block coder 1808 to generate the signal field of a range extension mode data unit, depending on an embodiment, is the same as or different from the range extension coding scheme used by the block coder 1808 to generate the data portion of the range extension mode data unit. In various embodiments, the block coder 1808 implements a “block level” repetition scheme or a “bit level” repetition scheme as discussed above in regard to the block coder 1704 of FIG. 17A. Similarly, in another embodiment, the block coder 1808 generates m number of copies of the incoming bits and interleaves the resulting bit stream according to a suitable code, or otherwise encodes incoming bits or incoming blocks of bits using any suitable code, e.g., a Hamming block code with the coding rate of a 1⁄2, 1⁄4, etc., or any other block code with the coding rate of 1⁄2, 1⁄4, etc. (e.g., (1,2) or (1, 4) block code, (12,24) block code or (6, 24) block code, a (13,26) block code, etc.). The effective coding rate for data units generated by the PHY processing unit 1800 is a product of the coding rate used by the FEC encoder 1806 and the number of repetitions (or the coding rate) used by the block coder 1808, according to an embodiment.
In an embodiment, the block coder 1808 provides sufficient diversity gain such that no further interleaving of coded bits is needed, and the interleaver 1810 is omitted. One advantage of omitting the interleaver 1810 is that in this case OFDM symbols with 52 data tones can be generated using 4× or a 6× repetition schemes even though in some such situations the number of data bits per symbol is not an integer. For example, in one such embodiment, the output of the FEC encoder 1806 is partitioned into blocks of 13 bits and each block is repeated four times (or block encoded with a rate of 1⁄4) to generate 52 bits to be included in an OFDM symbol. In this case, if the FEC encoder 1806 utilizes a coding rate of 1⁄2, the number of data bits per symbol is equal 6.5. In an example embodiment utilizing 6× repetition, the FEC encoder 1806 encodes information bits using a coding rate of 1⁄2 and the output is partitioned into blocks of four bits. The block coder 1808 repeats each four bit block six times (or block encodes each block using a coding rate of 1⁄6) and adds four padding bits to generate 52 bits to be included in an OFDM symbol.
As in the example of the PHY processing unit 1700 of FIG. 17A discussed above, if padding is used by the PHY processing unit 1800, the number of data bits per symbol (NDBPS) used for padding bit computations is the actual number of non-redundant data bits in an OFDM symbol (e.g., 6 bits, 12 bits, 13 bits as in the example above, or any other suitable number of bits). The number of coded bits per symbol (NCBPS) used in padding bit computations is equal to the number of bits actually included in an OFDM symbol (e.g., 24 bits, 48 bits, 52 bits, or any other suitable number of bits included in an OFDM symbol).
Also as in the example of the PHY processing unit 1700 of FIG. 17, a number of tail bits are typically inserted into each field of a data unit for proper operation of the FEC encoder 1806, e.g., to ensure that the BCC encoder, after having encoded each field, is brought back to zero state. In one embodiment, for example, six tail bits are inserted at the end of the data portion before the data portion is provided to the FEC encoder 1806 (i.e., after processing by the block coder 1704 is performed). Similarly, in the case of a signal field, tail bits are inserted at the end of the signal field before the signal field is provided to the FEC encoder 1806, according to an embodiment. In an example embodiment in which the block coder 1808 utilizes a 4× repetition scheme (or another block code with the coding rate of 1⁄4), the FEC encoder 1806 utilizes the coding rate of 1⁄2, and the signal field includes 24 information bits (including tail bits), the 24 signal field bits are BCC encoded to generate 48 BCC encoded bits which are then partitioned into four blocks of 12 bits each for further encoding by the block coder 1808. Accordingly, in this embodiment, the signal field is transmitted over four OFDM symbols each of which includes 6 information bits of the signal field.
Further, in some embodiments, the PHY processing unit 1800 generates OFDM symbols with 52 data tones according to the MCS0 specified in the IEEE 802.11n Standard or the IEEE 802.11ac Standard and the block coder 1808 utilizes a 4× repetition scheme. In some such embodiments, extra padding is used to ensure that the resulting encoded data stream to be included in an OFDM symbol includes 52 bits. In one such embodiment, padding bits are added to coded information the bits after the bits have been processed by the block coder 1808.
In the embodiment of FIG. 18A, the PHY processing unit 1800 also includes a peak to average power ratio (PAPR) reduction unit 1809. In an embodiment, the PAPR reduction unit 1809 flips the bits in some or all repeated blocks to reduce or eliminate the occurrence of the same bit sequences at different frequency locations in an OFDM symbol thereby reducing the peak to average power ratio of the output signal. In general, bit flipping involves changing the bit value of zero to the bit value of one and changing the bit vale of one to the bit value of zero. According to an embodiment, the PAPR reduction unit 1809 implements bit flipping using an XOR operation. For example, in an embodiment utilizing 4× repetition of a block of coded bits, if a block of coded bits to be included in an OFDM symbols is denoted as C and if C′=C XOR 1 (i.e., block C with bits flipped), then some possible bit sequences at the output of the PAPR reduction unit 1809, according to some embodiments, are [C C′ C′ C′], [C′ C′ C′ C], [C C′ C C′], [C C C C′], etc. In general, any combination of block with bits flipped and blocks with bits not flipped can be used. In some embodiments, the PAPR unit 1809 is omitted.
FIG. 18B is a block diagram of an example PHY processing unit 1850 for generating range extension mode data units, according to another embodiment. In some embodiments, the PHY processing unit 1850 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1850.
The PHY processing unit 1850 is similar to the PHY processing unit 1800 of FIG. 18, except that in the PHY processing unit 1850, the FEC encoder 1806 is replaced by the LDPC encoder 1856. Accordingly, in this embodiment, information bits are first encoded by the LDPC encoder 1856 and the LDPC coded bits are then replicated or otherwise block encoded by the block coder 1808. In an embodiment, the LDPC encoder 1856 utilizes a block code corresponding to a coding rate of 1⁄2, or a block code corresponding to another suitable coding rate. In the illustrated embodiment, the PHY processing unit 1850 omits the interleaver 1810 because adjacent bits in an information stream are generally spread out by the LDPC code itself and, according to an embodiment, no further interleaving is needed. Additionally, in an embodiment, further frequency diversity is provided by the LDPC tone remapping unit 1860. According to an embodiment, the LDPC tone remapping unit 1860 reorders coded information bits or blocks of coded information bits according to a tone remapping function. The tone remapping function is generally defined such that consecutive coded information bits or blocks of information bits are mapped onto nonconsecutive tones in the OFDM symbol to facilitate data recovery at the receiver in cases in which consecutive OFDM tones are adversely affected during transmission. In some embodiments, the LDPC tone remapping unit 1860 is omitted.
FIG. 19A is a block diagram of an example PHY processing unit 1900 for generating range extension mode data units, according to another embodiment. In some embodiments, the PHY processing unit 1900 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1900.
The PHY processing unit 1900 is similar to the PHY processing unit 1800 of FIG. 18A except that in the PHY processing unit 1900 the block coder 1916 is located after the constellation mapper 1914. Accordingly, in this embodiment, BCC encoded information bits, after having been processed by the interleaver 1910, are mapped to constellation symbols and the constellation symbols are then replicated or otherwise block encoded by the block coder 1916. According to an embodiment, processing by the FEC encoder 1906 is performed continuously over the entire field being generated (e.g., the entire data field, the entire signal field, etc.). In this embodiment, information bits corresponding to the field being generated are first encoded by the FEC encoder 1806 and the BCC coded bits are then mapped to constellation symbols by the constellation mapper 1914. The constellation symbols are then partitioned into blocks of a specified size (e.g., 6 symbols, 12 symbols, 13 symbols, or any other suitable number of symbols) and each block is then processed by the block coder 1916. As an example, in an embodiment utilizing 2× repetition, the constellation mapper 1914 generates 24 constellation symbols and the block coder 1916 generates two copies of the 24 symbols to generate 48 symbols corresponding to 48 data tones of an OFDM symbol (e.g., as specified in the IEEE 802.11a Standard). As another example, in an embodiment utilizing 4× repetition, the constellation mapper 1914 generates 12 constellation symbols and the block coder 1916 generates four copies of the 12 constellation symbols to generate 48 symbols corresponding to 48 data tones of an OFDM symbol (e.g., as specified in the IEEE 802.11a Standard). As yet another example, in an embodiment utilizing 2× repetition, the constellation mapper 1914 generates 26 constellation symbols and the block coder 1916 repeats the 26 symbols (i.e., generates two copies of the 26 symbols) to generate 52 symbols corresponding to 52 data tones of an OFDM symbol (e.g., as specified in the IEEE 802.11n Standard or the IEEE 802.11ac Standard). In general, in various embodiments and/or scenarios, the block coder 1916 generates any suitable number of copies of blocks of incoming constellation symbols and interleaves the generated symbols according to any suitable coding scheme. Similar to the block coder 1704 of FIG. 17A and the block coder 1808 of FIG. 18A, the range extension coding scheme used by the block coder 1916 to generate a signal field (or signal fields) of a range extension mode data unit is, depending on the embodiment, the same as or different from the range extension coding scheme used by the block coder 1916 to generate the data portion of the range extension mode data unit. The effective coding rate for data units generated by the PHY processing unit 1900 is a product of the coding rate used by the FEC encoder 1906 and the number of repetitions (or the coding rate) used by the block coder 1916, according to an embodiment.
According to an embodiment, because redundancy in this case is introduced after the information bits have been mapped to constellation symbols, each OFDM symbol generated by the PHY processing unit 1900 includes less non-redundant data tones compared to OFDM data tones included in a regular mode data units. Accordingly, the interleaver 1910 is designed to operate on fewer tones per OFDM symbol compared to the interleaver used in the regular mode (such as the interleaver 1610 of FIG. 16), or the interleaver used in generating the corresponding short range data unit. For example, in an embodiment with 12 non-redundant data tones per OFDM symbol, the interleaver 1910 is designed using the number of columns (Ncol) of 6 and the number of rows (Nrow) of 2*the number of bits per subcarrier (Nbpscs). In another example embodiment with 12 non-redundant data tones per OFDM symbol, the interleaver 1910 is designed using Ncol of 4 and Nrow of 3*Nbpscs. In other embodiments, other interleaver parameters different from interleaver parameter used in the regular mode are utilized for the interleaver 1910. Alternatively, in an embodiment, the block coder 1916 provides sufficient diversity gain such that no further interleaving of coded bits is needed, and the interleaver 1910 is omitted. In this case, as in the example embodiment utilizing the PHY processing unit 1800 of FIG. 18A, OFDM symbols with 52 data tones can be generated using 4× or a 6× repetition schemes even though in some such situations the number of data bits per symbol is not an integer.
As in the example embodiment of the PHY processing unit 1700 of FIG. 17A or the PHY processing unit 1800 of FIG. 18A discussed above, if padding is used by the PHY processing unit 1900, the number of data bits per symbol (NDBPS) used for padding bit computations is the actual number of non-redundant data bits in an OFDM symbol. (e.g., 6 bits, 12 bits, 13 bits as in the example above, or any other suitable number of bits). The number of coded bits per symbol (NCBPS) used in padding bit computations is equal to the number of non-redundant bits included in an OFDM symbol which, in this case, corresponds to number of bits in the block of constellation symbols processed by the block coder 1916 (e.g., 12 bits, 24 bits, 26 bits, etc.).
In some embodiments, the PHY processing unit 1900 generates OFDM symbols with 52 data tones according to the MCS0 specified in the IEEE 802.11n Standard or the IEEE 802.11ac Standard and the block coder 1916 utilizes a 4× repetition scheme. In some such embodiments, extra padding is used to ensure that the resulting encoded data stream to be included in an OFDM symbol includes 52 bits. In one such embodiment, padding bits are added to coded information the bits after the bits have been processed by the block coder 1808.
In the embodiment of FIG. 19, the PHY processing unit 1900 includes a peak to average power ratio (PAPR) reduction unit 1917. In an embodiment, the peak to average power ratio unit 1917 adds a phase shift to some of the data tones modulated with repeated constellations. For example, in one embodiment the added phase shift is 180 degrees. The 180 degree phase shift corresponds to a sign flip of the bits that modulate the data tones for which phase shifts are implemented. In another embodiment, the PAPR reduction unit 1917 adds a phase shift that is different than 180 degrees (e.g., a 90 degree phase shift or any other suitable phase shift). As an example, in an embodiment utilizing 4× repetition, if a block of 12 constellation symbols to be included in an OFDM symbols is denoted as C and if simple block repetition is performed, the resulting sequence is [C C C C]. In some embodiments, the PAPR reduction unit 1917 introduces a sign flip (i.e., −C) or a 90 degree phase shift (i.e., j*C) for some of the repeated blocks. In some such embodiments, the resulting sequence is, for example, [C −C −C −C], [−C −C −C −C], [C −C C −C], [C C C −C], [C j*C, j*C, j*C], or any other combination of C, −C, j*C, and −j*C. In general, any suitable phase shift can be introduced in any repeated block in various embodiments and/or scenarios. In some embodiments, the PAPR reduction unit 1809 is omitted.
In some embodiments, the PHY processing unit 1900 generates OFDM symbols with 52 data tones according to the MCS0 specified in the IEEE 802.11n Standard or the IEEE 802.11ac Standard and the block coding 1916 utilizes a 4× repetition scheme. In some such embodiments, extra pilot tones are inserted to ensure that the resulting number of data and pilot tones in an OFDM symbol is equal to 56 as specified in the short range communication protocol. As an example, in an embodiment, six information bits are BCC encoded at the coding rate of 1⁄2 and the resulting 12 bits are mapped to 12 constellation symbols (BPSK). The 12 constellation symbols modulate 12 data tones which are then repeated four times the generated 48 data tones. Four pilot tones are added as specified in the IEEE 802.11n Standard and 4 extra pilot tones are added to generate 56 data and pilot tones.
FIG. 19B is a block diagram of an example PHY processing unit 1950 for generating range extension mode data units, according to another embodiment. In some embodiments, the PHY processing unit 1950 generates signal and/or data fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 1950.
The PHY processing unit 1950 is similar to the PHY processing unit 1900 of FIG. 19, except that in the PHY processing unit 1950, the FEC encoder 1906 is replaced by the LDPC encoder 1956. Accordingly, in this embodiment, LDPC encoded information bits are mapped to constellation symbols by the constellation mapper 1914 and the constellation symbols are then replicated or otherwise block encoded by the block coder 1916. In an embodiment, the LDPC encoder 1956 utilizes a block code corresponding to a coding rate of 1⁄2, or a block code corresponding to another suitable coding rate. In the illustrated embodiment, the PHY processing unit 1950 omits the interleaver 1910 because adjacent bits in an information stream are generally spread out by the LDPC code itself and, according to an embodiment, no further interleaving is needed. Additionally, in an embodiment, further frequency diversity is provided by the LDPC tone remapping unit 1960. According to an embodiment, the LDPC tone remapping unit 1960 reorders coded information bits or blocks of coded information bits according to a tone remapping function. The tone remapping function is generally defined such that consecutive coded information bits or blocks of information bits are mapped onto nonconsecutive tones in the OFDM symbol to facilitate data recovery at the receiver in cases in which consecutive OFDM tones are adversely affected during transmission. In some embodiments, the LDPC tone remapping unit 1960 is omitted.
In the embodiments described above with regard to FIGS. 17-19, the range extension mode introduces redundancy by repeating bits and/or constellation symbols in frequency domain. Alternatively, in some embodiments, the range extension coding scheme includes OFDM symbol repetition of the signal and/or data fields of range extension mode data units that is performed in time domain. For example, FIG. 20A is a diagram showing a 2× repetition of each OFDM symbol of HT-SIG1 and HT-SIG2 fields in a preamble of a range extension mode data unit, according to an embodiment. Similarly, FIG. 20B is a diagram showing a 2× repetition of each OFDM symbol of the L-SIG field in a preamble of a range extension mode data unit, according to an embodiment. FIG. 20C is a diagram showing a time domain repetition scheme for OFDM symbols in the data portion of a control mode data unit, according to one embodiment. FIG. 20D is a diagram showing a repetition scheme for OFDM symbols in the data portion, according to another embodiment. As shown, in the embodiment of FIG. 20C OFDM symbol repetitions are output continuously, while in the embodiment of FIG. 20D OFDM symbol repetitions are interleaved. In general, OFDM symbol repetitions are interleaved according to any suitable interleaving scheme, in various embodiments and/or scenarios.
FIG. 21 is a flow diagram of an example method 2100 for generating a data unit, according to an embodiment. With reference to FIG. 1, the method 2100 is implemented by the network interface 16, in an embodiment. For example, in one such embodiment, the PHY processing unit 20 is configured to implement the method 2100. According to another embodiment, the MAC processing 18 is also configured to implement at least a part of the method 2100. With continued reference to FIG. 1, in yet another embodiment, the method 2100 is implemented by the network interface 27 (e.g., the PHY processing unit 29 and/or the MAC processing unit 28). In other embodiments, the method 2100 is implemented by other suitable network interfaces.
At block 2102, information bits to be included in the data unit are encoded according to a block code. In one embodiment, information bits are encoded using a block level or a bit level repetition scheme described above with respect to the block coder 1704 of FIG. 17, for example. At block 2104, the information bits are encoded using an FEC encoder, such as the FEC encoder 1706 of FIG. 17A, or the LDPC encoder 1756 of FIG. 17B, for example. At block 2106, information bits are mapped to constellation symbols. At block 2108, a plurality of OFDM symbols is generated to include the constellation points. At block 2110, the data unit is generated to include the OFDM symbols.
In one embodiment, as illustrated in FIG. 21, information bits are encoded using a block encoder first (block 2102) and the block coded bits are then encoded using a FEC encoder (block 2104), such as described above with respect to FIG. 17A, for example. In another embodiment, the order of blocks 2102 and 2104 is interchanged. Accordingly, in this embodiment, information bits are FEC encoded first and the FEC encoded bits are encoded according to a block coding scheme, such as described above with respect to FIG. 18A, for example. In yet another embodiment, block 2102 is positioned after block 2106. In this embodiment, information bits are FEC encoded at block 2104, the FEC encoded bits are mapped to constellation symbols at block 2106, and the constellation symbols are then encoded according to a block coding or repetition scheme, such as described above with respect to FIG. 19A, for example, at block 2102.
In various embodiments, the range extension coding scheme uses a reduced size fast Fourier transform (FFT) technique that outputs a reduced number of constellation symbols which are repeated over an overall bandwidth to improve range and/or SNR performance. For example, in an embodiment, a constellation mapper maps a sequence of bits to a plurality of constellation symbols corresponding to 32 subcarriers (e.g., a 32-FFT mode) having 24 data tones. The 32 sub-carriers correspond to a 10 MHz sub-band of an overall 20 MHz bandwidth. In this example, the constellation symbols are repeated across the overall bandwidth of 20 MHz to provide redundancy of the constellation symbols. In various embodiments, the reduced size FFT technique is used in combination with the bit-wise and/or symbol replication techniques described above with regard to FIGS. 17-19.
In some embodiments where additional bandwidth is available, such as 40 MHz, 80 MHz, 160 MHz, 320 MHz, 640 MHz, etc., the 32 subcarriers are repeated across each 10 MHz sub-band of the overall bandwidth. For example, in another embodiment, a 32-FFT mode corresponds to a 5 MHz sub-band of an overall 20 MHz bandwidth. In this embodiment, the plurality of constellations are repeated 4× across the overall 20 MHz bandwidth (i.e., in each 5 MHz sub-band). Accordingly, a receiving device combines the multiple constellations to improve decoding reliability of the constellations. In some embodiments, the modulation of different 5 or 10 MHz sub-bands signals is rotated by different angles. For example, in one embodiment, a first sub-band is rotated 0-degrees, a second sub-band is rotated 90-degrees, a third sub-band is rotated 180-degrees, and a fourth sub-band is rotated 270-degrees. In other embodiments, different suitable rotations are utilized. The different phases of the 20 MHz sub-band signals result in reduced peak to average power ratio (PAPR) of OFDM symbols in the data unit, in at least some embodiments.
FIG. 22A is a diagram of a 20 MHz overall bandwidth having 2× repetitions of the range extension data unit having a 10 MHz sub-band, according to an embodiment. As shown in FIG. 22A, each sub-band of 10 MHz is rotated by a rotation r1 and r2, respectively. FIG. 22B is a diagram of a 40 MHz overall bandwidth having 4× repetitions of the range extension data unit having the 10 MHz sub-band, according to an embodiment. As shown in FIG. 22B, each sub-band of 10 MHz is rotated by a rotation r1, r2, r3, and r4, respectively. FIG. 22C is a diagram of an example tone plan 2230 for a 32-FFT mode that corresponds to a 10 MHz sub-band, according to an embodiment. The tone plan 2230 includes 32 total tones, having 24 data tones, 2 pilot tones at indices +7 and −7, 1 direct current tone, and 5 guard tones as shown in FIG. 22. In embodiments where the reduced size FFT technique is used, the corresponding tone plan is used for the HEW-LTF field, when present. In other embodiments where the reduced size FFT technique is used but the HEW-LTF field is not present, the L-LTF field 704 is modified to include additional ±1 signs for pilot tones to the corresponding indices of the modified tone plan. For example, in an embodiment, tones −29, −27, +27, and +29 are added to the tone plan for the L-LTF field. In a further embodiment, ±1 signs are removed from the L-LTF tone plan in tones −2, −1, 1, and 2 in the 20 MHz bandwidth. Similar changes are applied for overall bandwidths of 40 MHz, 80 MHz, 160 MHz, etc.
FIG. 23 is a diagram of an example data unit 2300 in which the range extension mode is used for a preamble 2301 of the data unit, according to an embodiment. In some embodiments, the preamble 2301 indicates both the regular mode and the range extension mode. In such an embodiment, another method to differentiate the regular mode from the range extension mode is used, such as those described above with regard to FIGS. 9, 10, and 11.
The data unit 2301 is generally similar to and includes like-numbered elements with the data unit 1150 of FIG. 11B, except that the preamble 2301 of the data unit 2300 is formatted differently from the preamble 1151 of the data unit 1101. In an embodiment, the preamble 2301 is formatted such that a receiving device that operates according to the HEW communication protocol is able to determine that the preamble 2301 is a range extension mode preamble rather than a regular mode preamble. In an embodiment, the preamble 2301 includes a modified long training field M-LTF 2304 and a modified signal field M-SIG 2306 in place of the L-LTF 704 and the L-SIG 706, respectively, as compared to the data unit 1151. In an embodiment, the preamble 2301 includes the L-STF 702, a double guard interval followed by two repetitions of a modified long training sequence as the M-LTF 2304, a normal guard interval, and the modified signal field M-SIG. In some embodiments, the preamble 2301 further includes one or more first HEW signal fields (HEW-SIGAs) 1152. In an embodiment, the preamble 2301 further includes one or more secondary L-SIG(s) 1154 that follow the M-SIG field 2306. The secondary L-SIG(s) 1154 are followed by a second L-LTF field (L-LTF2) 1156, in some embodiments. In other embodiments, the preamble 2301 omits the L-SIG(s) 1154 and/or the L-LTF2 1156. In some embodiments, the preamble 2301 also includes an HEW-STF 1158, one or more HEW-LTF fields 1160, and a second HEW signal field (HEW-SIGB) 1162. In other embodiments, the preamble 2301 omits the HEW-STF 1158, the HEW-LTF(s) 1160 and/or the HEW-SIGB 1162. In an embodiment, the data unit 2300 also includes a data portion 716 (not shown in FIG. 23). In some embodiments, the HEW signal fields (HEW-SIGAs) 1152 are modulated using a same range extension coding scheme as the data field 716.
In various embodiments, the M-LTF 2304 corresponds to the L-LTF 704 multiplied by a predetermined sequence (e.g., a polarization code). For example, using an index i, an i-th constellation symbol of the L-LTF 704 is multiplied by an i-th value (e.g., ±1) of the predetermined sequence to obtain the M-LTF 2304, as shown in Equation 1:

M-LTFi=Ci*L-LTFi  (Equation 1)

where C is the predetermined sequence. In some embodiments, the M-SIG 2306 corresponds to the L-SIG 706 multiplied by the predetermined sequence, as shown in Equation 2:

M-SIGi=Ci*L-SIGi  (Equation 2)

In some embodiments, a length (i.e., a number of values) of the predetermined sequence is equal to a sum of a number of data tones and a number of pilot tones per 20 MHz band in the IEEE 802.11ac protocol, for example 52 values (i.e., for 48 data tones and 4 pilot tones).

In an embodiment, the predetermined sequence and the modified long training sequence each have a length that is greater than or equal to the sum of the number of data tones and the number of pilot tones. As described above with regard to the tone plan 2230 for a 32-FFT mode that corresponds to a 10 MHz sub-band, if the HEW-STF and/or HEW-LTF fields do not exist in the range extension preamble, the receiver relies upon the L-LTF field for demodulation of subsequent fields. In an embodiment, a tone plan miss-match between the 20 MHz L-LTF and the 10 MHz 32-FFT mode is corrected by inserting +1 or −1 signs in the L-LTF for the missing tones (e.g., tones −29, −27, +27, and +29 for a total of 58 tones).
FIG. 24 is a block diagram of an example PHY processing unit 2400 for generating range extension mode data units, according to another embodiment. In some embodiments, the PHY processing unit 2400 generates signal and/or training fields of range extension mode data units. Referring to FIG. 1, the AP 14 and the client station 25-1, in one embodiment, each include a PHY processing unit such as the PHY processing unit 2400.
The PHY processing unit 2400 is similar to the PHY processing unit 1700 of FIG. 17A, except that in the PHY processing unit 2400 a tone multiplier 2404 is located after the constellation mapper 1614. In some embodiments, the tone multiplier 2404 generates i) modified constellation symbols for the L-SIG field (i.e., M-SIG 2306) and ii) a modified long training sequence for the L-LTF field (i.e., M-LTF 2304) of a range extension mode data unit.
In some embodiments, the PHY processing unit 2400 is configured to generate a first long training sequence for the range extension mode preamble at least by multiplying the predetermined sequence with a second long training sequence of a second communication protocol. In an embodiment, for example, the tone multiplier 2404 multiplies the predetermined sequence by the L-LTF 704 to obtain the M-LTF 2304. The tone multiplier 2404 provides the M-LTF 2304 to the IDFT 1618 in place of the L-LTF 704 during the range extension mode, in an embodiment.
In an embodiment, the tone multiplier 2404 receives constellation symbols for data to be included in the L-SIG 706 from the constellation mapper 1614 and receives constellation symbols for pilot tones from a pilot tone generator 2408. Accordingly, the M-SIG 2306 output from the tone multiplier 2404 includes modified constellation symbols for data tones and pilot tones to be converted into a time-domain signal by the IDFT 1618, in an embodiment.
In some embodiments, a receiver device decodes the M-SIG 2306, for example, using channel estimates based on the M-LTF 2304. In this example, because both the L-LTF 704 and L-SIG 706 have been multiplied by the predetermined sequence, the legacy receiver device effectively removes the multiplication as part of a channel estimation process or auto-correlation process. In an embodiment, a receiving device determines whether a preamble corresponds to the range extension mode preamble 2400 or to the normal mode preamble 1101 by detecting whether the LTF field (e.g., either the M-LTF 2304 or the L-LTF 704) in the preamble is generated with (e.g., multiplied by) the predetermined sequence or without multiplying with the predetermined sequence based on auto-correlation of the L-LTF field with and without multiplication with the predetermined sequence. In an embodiment, the receiving device performs a first auto-correlation of the LTF with the L-LTF 704, performs a second auto-correlation of the LTF with the M-LTF 2304, and performs a comparison of the auto-correlation results. If auto-correlation with the M-LTF 2304 produces a greater result compared to the result of the auto-correlation with the L-LTF 704, then the receiving device determines that the preamble corresponds to the range extension mode preamble 2300, in an embodiment. On the other hand, if auto-correlation of the LTF with the L-LTF 704 produces a greater result compared to the result of auto-correlation with the M-LTF 2304, then the receiving device determines that the preamble corresponds to the regular mode preamble 1101, in an embodiment. The receiver device performs the auto-correlation in the frequency domain, in some embodiments, according to Equation 3:

maxL|ΣiyiLiyi+1*Li+1|  (Equation 3)

where yi is a final received and averaged L-LTF sequence, Li is the transmitted L-LTF sequence belonging to IEEE 802.11a/n/ac or the modified long training sequence M-LTF. For example, Li is either Ci*L-LTFi for the range extension mode or L-LTFi for the regular mode. In some scenarios, cross correlation of successive tones generally removes channel effects and frequency domain match filtering finds the most likely transmitted sequence. In some embodiments, the receiver device uses channel estimation from the M-LTF to decode additional fields of the data unit (i.e., HEW-SIG and/or data fields). In some scenarios, the values of the predetermined sequence corresponding to pilot tones are all one, allowing phase tracking on the pilot tones.

In some embodiments, OFDM modulation with reduced tone spacing is used with a same size FFT to reduce the data rate in the range extension mode. For example, whereas the regular mode for a 20 MHz bandwidth OFDM data unit uses a 64-point fast Fourier transform (FFT), resulting in 64 OFDM tones, the range extension mode uses a reduced tone spacing by a factor of 2, resulting in 128 OFDM tones in the same bandwidth. In this case, tone spacing in the range extension mode OFDM symbols is reduced by a factor of two (1⁄2) compared to the regular mode OFDM symbols while using a same 64-point FFT, a 2× increased symbol duration, and 2× increased guard interval, where the symbols are then repeated in the remaining bandwidth. As another example, whereas the regular mode for a 20 MHz bandwidth OFDM data unit uses a 64-point fast Fourier transform (FFT) resulting in 64 OFDM tones, the range extension mode uses a 1⁄4 reduced tone spacing for a 20 MHz OFDM data unit resulting in 256 OFDM tones in the same bandwidth. In this case, tone spacing in the range extension mode OFDM symbols is reduced by a factor of four (1⁄4) compared to the regular mode OFDM symbols while using a 4× increased symbol duration and 4× increased guard interval. In such embodiments, long GI duration of, for example, 1.6 μs is used. However, the duration of the information portion of the range extension mode OFDM symbol is increased (e.g., from 3.2 μs to 6.4 μs), and the percentage of the GI portion duration to the total OFDM symbols duration remains the same, in an embodiment. Thus, in this case, loss of efficiency due to a longer GI symbol is avoided, in at least some embodiments. In various embodiments, the term “long guard interval” as used herein encompasses an increased duration of a guard interval as well as a decreased OFDM tone spacing that effectively increases duration of the guard interval. In other embodiments, tone spacing is reduced, guard intervals are increased, and symbol duration is increased according to factors of 6, 8, or other suitable values. In some embodiments, variations in tone spacing, guard intervals, and symbol duration are used in combination with block coding or symbol repetition, as described above.
The total signal bandwidth of data units for the range extension mode in some embodiments is 20 MHz. For example, increased signal bandwidth is not likely to further increase the range or improve SNR performance. In some embodiments, the range extension mode is configured to use an FFT size up to 512 points. In such an embodiment, if tone-spacing is reduced by a factor of 4 for the range extension mode, then a total bandwidth for the 512 FFT is 40 MHz, thus the range extension mode uses up to 40 MHz signal bandwidth.
In other embodiments, the range extension mode is configured for up to the largest available signal bandwidth (e.g., 160 MHz). In various embodiments, for example, a 1⁄2 tone spacing corresponds to a 64 FFT for a 10 MHz band, a 128 FFT for a 20 MHz band, a 256 FFT for a 40 MHz band, a 512 FFT for a 80 MHz band, and a 1024 FFT for a 160 MHz band. In some embodiments, the reduced tone spacing is used in combination with a smaller FFT size. In various embodiments, shorter guard intervals are used with reduced tone spacing, for example, a normal guard interval having a duration equal to 25% of a duration of an OFDM symbol and a short guard interval having a duration equal to 1/9th of an OFDM symbol.
In some embodiments, the range extension mode uses a smaller tone spacing (i.e., 1⁄2, 1⁄4, etc.). In such an embodiment, the same FFT size represents a smaller bandwidth, for example, 1⁄2 tone spacing corresponds to a 64 FFT over a 10 MHz band. In an embodiment, the tone plan within a same FFT size is the same for both the range extension mode and the regular mode, for example, a 64 FFT in the range extension mode uses a same tone plan as in a 64 FFT for 20 MHz in IEEE 802.11ac. FIG. 25A is a diagram of an example 20 MHz total bandwidth having 1⁄2 tone spacing, according to an embodiment. In this case, the indices for the original DC tones of a legacy tone plan for each 64FFT are now in the middle of the 10 MHz sub-band, instead of in the middle of the total 20 MHz bandwidth, and the indices for the original guard tones are proximate to the true DC tone. In some embodiments where the band used for a range extension mode data unit is less than 20 MHz, a non-legacy tone plan includes additional data or pilot tones at the indices for the original DC tones, because the indices will not overlap with the “true DC tone,” because the smallest signal bandwidth is 20 MHz for the range extension mode or regular mode. In some embodiments, the non-legacy tone plan includes additional data tones in place of guard tones at the edges of the legacy tone plan to keep a same number of populated tones.
In other embodiments, when the tone spacing is reduced, the impact from a direct current offset and carrier frequency offset (CFO) becomes larger as compared to the regular mode. FIG. 25B is a diagram of an example 20 MHz total bandwidth having 1⁄2 tone spacing, according to an embodiment. In some embodiments, additional zero tones are defined proximate to the direct current tone of a band for a non-legacy tone plan of the range extension mode as compared to the legacy tone plan of the same FFT size in the regular mode. In various embodiments, the additional zero tones are defined only beyond a predetermined FFT size and/or tone spacing, for example, when the FFT size is greater than or equal to 128 with tone spacing reduced by 1⁄2, or when the FFT size is greater than or equal to 256 with tone spacing reduced by 1⁄4. In some embodiments, an increased number of guard tones is used for a non-legacy tone plan for the range extension mode, for example, to maintain a same absolute guard space (e.g., absolute frequency space) at a band edge as compared to the legacy tone plan of the regular mode. In this case, a total number of data tones and pilot tones in the non-legacy tone plan is less than the legacy tone plan. In some examples, the same absolute guard space facilitates filter designs. In some embodiments, for example, where the total number of data tones for the non-legacy tone plan is different from a same FFT size of the regular mode, PHY parameters for the FEC interleaver and/or LDPC tone mapper are redefined for the number of data tones of the non-legacy tone plan.
FIG. 26A is a diagram of a non-legacy tone plan 2600 for the range extension mode having a size 64 FFT and 1⁄2 tone spacing, according to an embodiment. In the non-legacy tone plan 2600, additional guard tones are included (i.e., guard tones −28, −27, +27, +28) as compared to a legacy tone plan for the regular mode. In some embodiments, the 64 FFT populates the DC tone with either a pilot tone or data tone. FIG. 26B is a diagram of a non-legacy tone plan 2601 for the range extension mode having a size 128 FFT and 1⁄2 tone spacing, according to an embodiment. In the non-legacy tone plan 2601, additional guard tones (i.e., guard tones −58, −57, +57, +58) and additional DC tones (i.e., DC tones −2, −1, 0, 1, 2) are included as compared to a legacy tone plan for the regular mode. FIG. 26C is a diagram illustrating a non-legacy tone plan 2602 for the range extension mode having a size 256 FFT and 1⁄2 tone spacing, according to an embodiment. In the non-legacy tone plan 2602, additional guard tones (i.e., guard tones −122, −121, +121, +122) and additional DC tones (i.e., DC tones −2, −1, 0, 1, 2) are included as compared to a legacy tone plan for the regular mode. In other embodiments, additional guard tones and/or DC tones are added to the non-legacy tone plans for the range extension mode as compared to the regular mode.
FIG. 27 is a flow diagram of an example method 2700 for generating a data unit, according to an embodiment. With reference to FIG. 1, the method 2700 is implemented by the network interface 16, in an embodiment. For example, in one such embodiment, the PHY processing unit 20 is configured to implement the method 2700. According to another embodiment, the MAC processing 18 is also configured to implement at least a part of the method 2700. With continued reference to FIG. 1, in yet another embodiment, the method 2700 is implemented by the network interface 27 (e.g., the PHY processing unit 29 and/or the MAC processing unit 28). In other embodiments, the method 2700 is implemented by other suitable network interfaces.
At block 2702, first OFDM symbols for a data field are generated. In various embodiments, generating the OFDM symbols at block 2702 includes generating OFDM symbols of the data portion according to one of the range extension coding scheme that corresponds to the range extension mode or the regular coding scheme that corresponds to the regular mode. In an embodiment, the range extension coding scheme includes the range extension coding schemes described above with respect to FIG. 10 (e.g., reduced tone spacing). In another embodiment, the range extension coding scheme includes the range extension coding schemes described above with respect to FIGS. 17-20 (e.g., bit-wise repetition or symbol repetition). In yet another embodiment, the range extension coding scheme includes the range extension coding schemes described above with respect to FIG. 22 (e.g., data unit repetition). In yet another embodiment, the range extension coding scheme includes a suitable combination of the range extension coding schemes described above with respect to FIG. 10, FIGS. 17-20, and FIG. 22.
In an embodiment, generating the OFDM symbols for the data portion of the PHY data unit according to the range extension coding scheme includes: encoding a plurality of information bits using a forward error correction (FEC) encoder (e.g., the FEC encoder 1706, 1806, or 1906) to obtain a plurality of encoded bits; mapping the plurality of encoded bits to a plurality of constellation symbols, for example, using the constellation mapper 1614 or 1914; generating the OFDM symbols to include the plurality of constellation symbols, for example, using the IDFT 1618 or 1818. In an embodiment, generating the OFDM symbols further includes performing one of: i) encoding the plurality of information bits according to a block coding scheme (e.g., using the block coder 1704), ii) encoding the plurality of encoded bits according to the block coding scheme (e.g., using the block coder 1808), or iii) encoding the plurality of constellation symbols according to the block coding scheme (e.g., using the block coder 1916). In another embodiment, generating the OFDM symbols for the data field includes generating the OFDM symbols for the data field to include a plurality of constellation symbols in a first bandwidth portion of a channel bandwidth and a copy of the plurality of constellation symbols in a second bandwidth portion of the channel bandwidth, for example, as described above with respect to FIG. 22. In a further embodiment, the copy of the plurality of constellation symbols is generated to include a predetermined phase shift.
At block 2704, a preamble of the data unit is generated. The preamble generated at block 2704 is generated to indicate whether at least the data portion of the data unit generated at block 2702 is generated using the range extension coding scheme or the regular coding scheme. In various embodiments and/or scenarios, one of the preambles 701 (FIGS. 9A, 10A), 751 (FIGS. 9B, 10B), 1101 (FIG. 11A), 1151 (FIG. 11B), or 1401 (FIG. 14A) is generated at block 1604. In other embodiments, other suitable preambles are generated at block 2704.
In an embodiment, the preamble is generated to have i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data portion are generated according to the range extension coding scheme. In a further embodiment, the first portion of the preamble is formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol (e.g., a legacy communication protocol), but does not conform to the first communication protocol (e.g., the HEW communication protocol), to determine the duration of the PHY data unit based on the first portion of the preamble.
In an embodiment, the preamble generated at block 2704 includes a CI indication set to indicate whether at least the data portion is generated using the range extension coding scheme or the regular coding scheme. In an embodiment, the CI indication comprises one bit. In an embodiment, a portion of the preamble, in addition to the data portion, is generated using the coding scheme indicated by the CI indication. In another embodiment, the preamble generated at block 2704 is formatted such that a receiving device can automatically detect (e.g., without decoding) whether the preamble corresponds to a regular mode preamble or to a range extension mode preamble. In an embodiment, detection of the range extension mode preamble signals to the receiving device that at least the data portion is generated using the range extension coding scheme.
In an embodiment, generating the preamble includes generating a second portion of the preamble including second OFDM symbols for i) a short training field according to the first communication protocol and ii) at least one copy of the short training field, and generating third OFDM symbols for i) a long training field according to the first communication protocol and ii) at least one copy of the long training field. In a further embodiment, the OFDM symbols for the data portion, the second OFDM symbols, and the third OFDM symbols have a same tone plan that is distinct from a tone plan for the first portion of the preamble.
In another embodiment, block 2704 includes generating a first signal field for the PHY data unit according to the second communication protocol (e.g., the legacy communication protocol) and generating a second signal field as a copy of the first signal field to indicate that at least some OFDM symbols of the data field are generated according to the range extension mode. In a further embodiment, the first signal field and the second signal field indicate that the duration of the PHY data unit is a predetermined duration and the second signal field is usable by a receiver device that conforms to the first communication protocol as a supplemental training field. In another embodiment, the first signal field and the second signal field are decodable in combination by a receiver device that conforms to the first communication protocol to increase a decoding reliability of the first signal field and the second signal field.
In an embodiment, the first portion of the preamble includes i) a legacy short training field that conforms to the second communication protocol, ii) a non-legacy long training field, and iii) a legacy signal field that conforms to the second communication protocol, and the second portion of the preamble does not include any training fields. In this embodiment, a first plurality of constellation symbols are generated for the legacy short training field using a legacy tone plan that conforms to the second communication protocol, a second plurality of constellation symbols are generated for the non-legacy long training field using a non-legacy tone plan; and the OFDM symbols for the data field include a third plurality of constellation symbols generated using the non-legacy tone plan.
In an embodiment, OFDM symbols are generated for the first portion of the preamble as a legacy preamble, using a normal guard interval, that conforms to the second communication protocol, and OFDM symbols are generated for the second portion of the preamble using a long guard interval. In a further embodiment, OFDM symbols for a non-legacy signal field and a non-legacy short training field of the second portion of the preamble are generated using the normal guard interval, and OFDM symbols for the second portion of the preamble are generated for a non-legacy long training field using the long guard interval. In another embodiment, OFDM symbols are generated for a legacy signal field of the first portion of the preamble using the normal guard interval, and OFDM symbols are generated for a non-legacy signal field of the second portion of the preamble using a long guard interval. In an embodiment, the second portion of the preamble is decodable by receiver devices that conform to the first communication protocol and the long guard interval of the second preamble signals to the receiver devices that conform to the first communication protocol that the PHY data unit conforms to the range extension mode. In yet another embodiment, OFDM symbols are generated for the second portion of the preamble, using the long guard interval, for i) a non-legacy signal field and ii) a copy of a first OFDM symbol for the non-legacy signal field. In an embodiment, OFDM symbols are generated for each field of a plurality of fields of the second portion of the preamble to include i) a double guard interval, ii) a first OFDM symbol for the field, and iii) a second OFDM symbol for the field that is a copy of the first OFDM symbol.
At block 2706, the data unit is generated to include the preamble generated at block 2704 and the data portion generated at block 2702. In an embodiment, the PHY data unit is generated to include a double guard interval according to the second communication protocol followed by the first portion of the signal field and the second portion of the signal field, without a guard interval between the first signal field and the second signal field.
In some embodiments, at least the first portion of the preamble is transmitted with a transmission power boost as compared to the data field to increase a decoding range of the first portion of the preamble.
In another embodiment, OFDM symbols for the data field are generated using a first tone spacing and a long guard interval, and OFDM symbols for the first portion of the preamble are generated using i) a second tone spacing that is different from the first tone spacing, and ii) a regular guard interval. In a further embodiment, the second tone spacing of the first portion of the preamble is i) a legacy tone spacing that conforms to the second communication protocol, and ii) an integer multiple of the first tone spacing of the data field, and the regular guard interval is a legacy guard interval that conforms to the second communication protocol. In another embodiment, OFDM symbols for the second portion of the preamble are generated including i) at least a first OFDM symbol using the legacy tone spacing and the legacy guard interval and ii) at least a second OFDM symbol using the first tone spacing and the long guard interval. In yet another embodiment, the OFDM symbols for the data field are generated using the first tone spacing to include a plurality of constellation symbols in a first bandwidth portion of a channel bandwidth and a copy of the plurality of constellation symbols in a second bandwidth portion of the channel bandwidth, and the first bandwidth portion and the second bandwidth portion have a same bandwidth. In a further embodiment, generating the OFDM symbols for the data field includes generating the copy of the plurality of constellation symbols to include a predetermined phase shift.
In an embodiment, generating the OFDM symbols for the data field includes generating the OFDM symbols for the data field using the first tone spacing, the long guard interval, and a long symbol duration. In a further embodiment, generating the OFDM symbols for the first portion of the preamble comprises generating OFDM symbols for the first portion of the preamble using the second tone spacing, the regular guard interval, and a regular symbol duration. In a further embodiment, the second tone spacing of the first portion of the preamble is i) a legacy tone spacing and ii) an integer n multiple of the first tone spacing of the data field, the regular guard interval is a legacy guard interval, and the long symbol duration is an integer n multiple of the regular symbol duration.
In another embodiment, generating the OFDM symbols for the data field of the PHY data unit according to the range extension mode includes: generating the OFDM symbols for the data field using a non-legacy tone spacing and a non-legacy tone plan that do not conform to the second communication protocol; and generating the preamble comprises generating OFDM symbols for the first portion of the preamble using a second tone spacing that is different from the non-legacy tone spacing and a legacy tone plan that is different from the non-legacy tone plan. In a further embodiment, the non-legacy tone plan includes at least one guard tone in place of a corresponding data tone of the legacy tone plan proximate to a direct current tone. In an embodiment, the non-legacy tone plan includes at least one data tone in place of a corresponding guard tone of the legacy tone plan such that the non-legacy tone plan and the legacy tone plan have a same number of data tones. In another embodiment, the non-legacy tone plan includes fewer data tones than the legacy tone plan and generating the OFDM symbols for the data field using the non-legacy tone spacing and the non-legacy tone plan includes encoding information bits for the OFDM symbols using an error correcting code based on a number of data tones of the non-legacy tone plan. In an embodiment, the error correcting code is a binary convolutional code. In another embodiment, the error correcting code is a low density parity check code.
FIG. 28 is a flow diagram of an example method 2800 for generating a data unit, according to an embodiment. With reference to FIG. 1, the method 2800 is implemented by the network interface 16, in an embodiment. For example, in one such embodiment, the PHY processing unit 20 is configured to implement the method 2800. According to another embodiment, the MAC processing 18 is also configured to implement at least a part of the method 2800. With continued reference to FIG. 1, in yet another embodiment, the method 2800 is implemented by the network interface 27 (e.g., the PHY processing unit 29 and/or the MAC processing unit 28). In other embodiments, the method 2800 is implemented by other suitable network interfaces.
At block 2802, a first plurality of orthogonal frequency division multiplexing (OFDM) symbols is generated for a first field of a preamble to be included in the PHY data unit, in an embodiment. In some embodiments, each OFDM symbol of the first plurality of OFDM symbols corresponds to a first long training sequence of the first communication protocol that is obtained at least by multiplying a predetermined sequence with a second long training sequence of a second communication protocol. At block 2804, a first plurality of information bits for a second field of the preamble are encoded to generate a first plurality of encoded bits, in an embodiment.
At block 2806, the first plurality of encoded bits are mapped to a first plurality of constellation symbols, in an embodiment. At block 2808, a first plurality of modified constellation symbols are generated, including multiplying the first plurality of constellation symbols by the predetermined sequence, in an embodiment. At block 2810, a second plurality of orthogonal frequency division multiplexing (OFDM) symbols are generated to include the first plurality of modified constellation symbols, in an embodiment. At block 2812, the preamble is generated to include the first plurality of OFDM symbols for the first field and the second plurality of OFDM symbols for the second field, in an embodiment. At block 2814, the PHY data unit is generated to include at least the preamble.
In some embodiments, the first plurality of information bits includes a first set of one or more information bits that indicate a duration of the PHY data unit, the preamble being formatted such that the preamble is decodable by a receiver device that conforms to the second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the preamble. In an embodiment, an i-th value of the first long training sequence corresponds to an i-th value of the predetermined sequence multiplied with a corresponding i-th value of the second long training sequence where i is an index.
In an embodiment, a length of the first long training sequence is greater than or equal to a sum of a number of data tones and a number of pilot tones in an OFDM symbol specified by the second communication protocol. In some embodiments, generating the first plurality of modified constellation symbols includes multiplying the predetermined sequence by a plurality of pilot tone constellation symbols for the second communication protocol. In some embodiments, values of the predetermined sequence that correspond to the plurality of pilot tone constellation symbols have a value of 1. In an embodiment, values of the predetermined sequence have a value of +1 or −1.
In some embodiments, generating the first plurality of OFDM symbols includes generating the first plurality of OFDM symbols such that an auto-correlation output for the first field generated by a receiver that conforms to the first communication protocol will signal i) a first mode of the first communication protocol or ii) a second mode of the first communication protocol to enable automatic detection of the first mode or the second mode by the receiver device. In an embodiment, the first field includes the first long training sequence. In another embodiment, the first field includes the second long training sequence.
In an embodiment, the method 2800 further includes: encoding a second plurality of information bits for a data field of the PHY data unit to generate a second plurality of encoded bits; mapping the second plurality of encoded bits to a second plurality of constellation symbols; generating a second plurality of modified constellation symbols, including multiplying the predetermined sequence by the second plurality of constellation symbols; generating a third plurality of orthogonal frequency division multiplexing (OFDM) symbols to include the second plurality of modified constellation symbols; and generating the data field to include the third plurality of OFDM symbols, where generating the PHY data unit includes generating the PHY data unit to include at least the preamble and the data field.
At least some of the various blocks, operations, and techniques described above may be implemented utilizing hardware, a processor executing firmware instructions, a processor executing software instructions, or any combination thereof. When implemented utilizing a processor executing software or firmware instructions, the software or firmware instructions may be stored in any computer readable memory such as on a magnetic disk, an optical disk, or other storage medium, in a RAM or ROM or flash memory, processor, hard disk drive, optical disk drive, tape drive, etc. Likewise, the software or firmware instructions may be delivered to a user or a system via any known or desired delivery method including, for example, on a computer readable disk or other transportable computer storage mechanism or via communication media. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency, infrared and other wireless media. Thus, the software or firmware instructions may be delivered to a user or a system via a communication channel such as a telephone line, a DSL line, a cable television line, a fiber optics line, a wireless communication channel, the Internet, etc. (which are viewed as being the same as or interchangeable with providing such software via a transportable storage medium). The software or firmware instructions may include machine readable instructions that, when executed by the processor, cause the processor to perform various acts.
When implemented in hardware, the hardware may comprise one or more of discrete components, an integrated circuit, an application-specific integrated circuit (ASIC), etc.
While the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, changes, additions and/or deletions may be made to the disclosed embodiments without departing from the scope of the invention.

## Claims

1. A method for generating a physical layer (PHY) data unit for transmission via a communication channel, the PHY data unit conforming to a first communication protocol, the method comprising:
generating, by a first communication device, orthogonal frequency division multiplexing (OFDM) symbols for a data field of the PHY data unit according to a range extension coding scheme that corresponds to a range extension mode of the first communication protocol;
generating, by the first communication device, a preamble of the PHY data unit, the preamble having i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data field are generated according to the range extension coding scheme, the first portion of the preamble being formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the first portion of the preamble;
generating, by the first communication device, the PHY data unit to include the preamble and the data field; and
causing the PHY data unit to be transmitted from the first communication device to a second communication device;
wherein:
generating the preamble comprises generating OFDM symbols for the second portion of the preamble that include i) a non-legacy signal field, and ii) a copy of the non-legacy signal field, wherein the copy of the non-legacy signal field indicates that the at least some OFDM symbols of the data field are generated according to the range extension coding scheme;
generating the preamble further comprises i) generating the first portion of the preamble, and ii) generating the second portion of the preamble; and
generating the first portion of the preamble comprises generating a first legacy signal field for the PHY data unit according to the second communication protocol and generating a second legacy signal field as a copy of the first legacy signal field.

2. The method of claim 1, wherein generating the OFDM symbols for the data field of the PHY data unit according to the range extension coding scheme comprises:
encoding a plurality of information bits, to be included in the PHY data field, using a forward error correction (FEC) encoder to obtain a plurality of encoded bits;
mapping the plurality of encoded bits to a plurality of constellation symbols;
generating the OFDM symbols to include the plurality of constellation symbols; and
wherein the method further comprises performing one of:
i) encoding the plurality of information bits according to a block coding scheme,
ii) encoding the plurality of encoded bits according to the block coding scheme, or
iii) encoding the plurality of constellation symbols according to the block coding scheme.

3. The method of claim 1, wherein generating the OFDM symbols for the data field of the PHY data unit according to the range extension coding scheme comprises:
generating the OFDM symbols for the data field to include a plurality of constellation symbols in a first bandwidth portion of a channel bandwidth and a copy of the plurality of constellation symbols in a second bandwidth portion of the channel bandwidth, wherein the first bandwidth portion and the second bandwidth portion have a same bandwidth.

4. The method of claim 3, wherein generating the OFDM symbols for the data field comprises generating the copy of the plurality of constellation symbols to include a predetermined phase shift.

5. The method of claim 3, wherein:
the OFDM symbols for the data field comprise first OFDM symbols;
generating the preamble includes generating the second portion of the preamble;
generating the second portion of the preamble comprises:
generating second OFDM symbols for i) a short training field according to the first communication protocol and ii) at least one copy of the short training field, and
generating third OFDM symbols for i) a long training field according to the first communication protocol and ii) at least one copy of the long training field; and

the first OFDM symbols, the second OFDM symbols, and the third OFDM symbols have a same tone plan that is distinct from a tone plan for the first portion of the preamble.

6. The method of claim 1, wherein causing the PHY data unit to be transmitted from the first communication device to the second communication device comprises transmitting at least the first portion of the preamble with a transmission power boost as compared to the data field to increase a decoding range of the first portion of the preamble.

7. The method of claim 1, wherein the first legacy signal field and the second legacy signal field indicate that the duration of the PHY data unit is a predetermined duration, wherein the second signal field is usable by a receiver device that conforms to the first communication protocol as a supplemental training field.

8. The method of claim 1, wherein generating the PHY data unit to include the preamble and the data field comprises generating the PHY data unit to include a double guard interval according to the second communication protocol followed by the first legacy signal field and the second legacy signal field, without a guard interval between the first legacy signal field and the second legacy signal field.

9. The method of claim 1, wherein the first legacy signal field and the second legacy signal field are decodable in combination by a receiver device that conforms to the first communication protocol to increase a decoding reliability of the first legacy signal field and the second legacy signal field.

10. The method of claim 1, wherein:
the first portion of the preamble includes i) a legacy short training field that conforms to the second communication protocol, ii) a non-legacy long training field, and iii) a legacy signal field that conforms to the second communication protocol;
the second portion of the preamble does not include any training fields;
the method further comprises:
generating, by the first communication device, a first plurality of constellation symbols for the legacy short training field using a legacy tone plan that conforms to the second communication protocol,
generating, by the first communication device, a second plurality of constellation symbols for the non-legacy long training field using a non-legacy tone plan; and

generating the OFDM symbols for the data field comprises generating a third plurality of constellation symbols using the non-legacy tone plan.

11. The method of claim 1, wherein generating the preamble comprises:
generating OFDM symbols for the first portion of the preamble as a legacy preamble, using a normal guard interval, that conforms to the second communication protocol; and
generating the OFDM symbols for the second portion of the preamble using a long guard interval.

12. The method of claim 11, wherein generating the OFDM symbols for the second portion of the preamble comprises:
generating OFDM symbols for the non-legacy signal field and a non-legacy short training field using the normal guard interval; and
generating OFDM symbols for a non-legacy long training field using the long guard interval.

13. The method of claim 11, wherein generating OFDM symbols for the second portion of the preamble comprises:
generating OFDM symbols for a legacy signal field using the normal guard interval; and
generating OFDM symbols for the non-legacy signal field using the long guard interval.

14. The method of claim 11, wherein:
the second portion of the preamble is decodable by receiver devices that conform to the first communication protocol; and
the long guard interval of the second portion of the preamble signals to the receiver devices that conform to the first communication protocol that the PHY data unit conforms to the range extension mode.

15. The method of claim 11, wherein generating OFDM symbols for the second portion of the preamble comprises:
generating OFDM symbols for each field of a plurality of fields of the second portion of the preamble to include i) a double guard interval, ii) a first OFDM symbol for the field, and iii) a second OFDM symbol for the field that is a copy of the first OFDM symbol.

16. The method of claim 1, wherein generating the OFDM symbols for the second portion of the preamble comprises:
generating OFDM symbols that include three binary phase shift keying (BPSK) symbols and one quadrature binary phase shift keying (Q-BPSK) symbol.

17. The method of claim 1, wherein:
generating the OFDM symbols for the data field of the PHY data unit according to the range extension mode comprises:
generating the OFDM symbols for the data field using a first tone spacing and a long guard interval; and

generating the preamble comprises generating OFDM symbols for the first portion of the preamble using i) a second tone spacing that is different from the first tone spacing, and ii) a regular guard interval.

18. The method of claim 17, wherein:
the second tone spacing of the first portion of the preamble is i) a legacy tone spacing that conforms to the second communication protocol, and ii) an integer multiple of the first tone spacing of the data field; and
the regular guard interval is a legacy guard interval that conforms to the second communication protocol.

19. The method of claim 18, wherein generating the preamble includes:
generating OFDM symbols for the second portion of the preamble including i) at least a first OFDM symbol using the legacy tone spacing and the legacy guard interval and ii) at least a second OFDM symbol using the first tone spacing and the long guard interval.

20. The method of claim 18, wherein generating the preamble comprises generating the OFDM symbols for the second portion of the preamble, including:
generating the non-legacy signal field and a non-legacy short training field using the legacy tone spacing and the legacy guard interval; and
generating a non-legacy long training field using the first tone spacing and the longer guard interval.

21. The method of claim 17, wherein:
generating the OFDM symbols for the data field using the first tone spacing comprises generating the OFDM symbols for the data field to include a plurality of constellation symbols in a first bandwidth portion of a channel bandwidth and a copy of the plurality of constellation symbols in a second bandwidth portion of the channel bandwidth; and
the first bandwidth portion and the second bandwidth portion have a same bandwidth.

22. The method of claim 21, wherein generating the OFDM symbols for the data field comprises generating the copy of the plurality of constellation symbols to include a predetermined phase shift.

23. The method of claim 17, wherein:
generating the OFDM symbols for the data field comprises generating the OFDM symbols for the data field using the first tone spacing, the long guard interval, and a long symbol duration;
generating the OFDM symbols for the first portion of the preamble comprises generating OFDM symbols for the first portion of the preamble using the second tone spacing, the regular guard interval, and a regular symbol duration.

24. The method of claim 23, wherein:
the second tone spacing of the first portion of the preamble is i) a legacy tone spacing and ii) an integer n multiple of the first tone spacing of the data field;
the regular guard interval is a legacy guard interval; and
the long symbol duration is an integer n multiple of the regular symbol duration.

25. The method of claim 1, wherein:
generating the OFDM symbols for the data field of the PHY data unit according to the range extension mode comprises:
generating the OFDM symbols for the data field using a non-legacy tone spacing and a non-legacy tone plan that do not conform to the second communication protocol; and
generating the preamble comprises generating OFDM symbols for the first portion of the preamble using a second tone spacing that is different from the non-legacy tone spacing and a legacy tone plan that is different from the non-legacy tone plan.

26. The method of claim 25, wherein the non-legacy tone plan includes at least one guard tone in place of a corresponding data tone of the legacy tone plan proximate to a direct current tone.

27. The method of claim 26, wherein the non-legacy tone plan includes at least one data tone in place of a corresponding guard tone of the legacy tone plan such that the non-legacy tone plan and the legacy tone plan have a same number of data tones.

28. The method of claim 26, wherein:
the non-legacy tone plan includes fewer data tones than the legacy tone plan; and
generating the OFDM symbols for the data field using the non-legacy tone spacing and the non-legacy tone plan comprises encoding information bits for the OFDM symbols using an error correcting code based on a number of data tones of the non-legacy tone plan.

29. The method of claim 28, wherein the error correcting code is a binary convolutional code.

30. The method of claim 28, wherein the error correcting code is a low density parity check code.

31. A first communication device, comprising:
a network interface device having one or more integrated circuits configured to:
generate orthogonal frequency division multiplexing (OFDM) symbols for a data field of a physical layer (PHY) data unit according to a range extension coding scheme that corresponds to a range extension mode of a first communication protocol to which the PHY data unit conforms,
generate a preamble of the PHY data unit, the preamble having i) a first portion that indicates a duration of the PHY data unit and ii) a second portion that indicates whether at least some OFDM symbols of the data field are generated according to the range extension coding scheme, the first portion of the preamble being formatted such that the first portion of the preamble is decodable by a receiver device that conforms to a second communication protocol, but does not conform to the first communication protocol, to determine the duration of the PHY data unit based on the first portion of the preamble,
generate a first legacy signal field in the first portion of the preamble according to the second communication protocol and generate a second legacy signal field as a copy of the first legacy signal field,
generate the PHY data unit to include the preamble and the data field, and
cause the PHY data unit to be transmitted from the first communication device to a second communication device;

wherein the one or more integrated circuits are configured to generate OFDM symbols for the second portion of the preamble that include i) a non-legacy signal field, and ii) a copy of the non-legacy signal field, wherein the copy of the non-legacy signal field indicates that the at least some OFDM symbols of the data field are generated according to the range extension coding scheme.

32. The apparatus of claim 31, wherein the one or more integrated circuits are configured to:
generate the OFDM symbols for the data field to include i) a plurality of constellation symbols in a first bandwidth portion of a channel bandwidth and ii) a copy of the plurality of constellation symbols in a second bandwidth portion of the channel bandwidth, wherein the first bandwidth portion and the second bandwidth portion have a same bandwidth.

33. The apparatus of claim 32, wherein:
the OFDM symbols for the data field comprise first OFDM symbols;
the one or more integrated circuits are configured to
generate the second portion of the preamble including:
generating second OFDM symbols for i) a short training field according to the first communication protocol and ii) at least one copy of the short training field, and
generating third OFDM symbols for i) a long training field according to the first communication protocol and ii) at least one copy of the long training field; and


the first OFDM symbols, the second OFDM symbols, and the third OFDM symbols have a same tone plan that is distinct from a tone plan for the first portion of the preamble.

34. The apparatus of claim 32, the one or more integrated circuits are configured to cause the network interface to transmit at least the first portion of the preamble with a transmission power boost as compared to the data field to increase a decoding range of the first portion of the preamble.

35. The apparatus of claim 32, wherein:
the first portion of the preamble includes i) a legacy short training field that conforms to the second communication protocol, ii) a non-legacy long training field, and iii) a legacy signal field that conforms to the second communication protocol;
the second portion of the preamble does not include any training fields;
the one or more integrated circuits are configured to
generate a first plurality of constellation symbols for the legacy short training field using a legacy tone plan that conforms to the second communication protocol,
generate a second plurality of constellation symbols for the non-legacy long training field using a non-legacy tone plan, and
generate a third plurality of constellation symbols using the non-legacy tone plan as part of generating the OFDM symbols for the data field.

36. The apparatus of claim 32, wherein generating the preamble comprises:
generating OFDM symbols for the first portion of the preamble as a legacy preamble, using a normal guard interval, that conforms to the second communication protocol; and
generating OFDM symbols for the second portion of the preamble using a long guard interval.

37. The apparatus of claim 32, wherein the one or more integrated circuits are configured to
generate the OFDM symbols for the data field using a first tone spacing and a long guard interval; and
generate OFDM symbols for the first portion of the preamble using i) a second tone spacing that is different from the first tone spacing, and ii) a regular guard interval.

38. The apparatus of claim 32, wherein the one or more integrated circuits are configured to
generate the OFDM symbols for the data field using a non-legacy tone spacing and a non-legacy tone plan that do not conform to the second communication protocol; and
generate OFDM symbols for the first portion of the preamble using a second tone spacing that is different from the non-legacy tone spacing and a legacy tone plan that is different from the non-legacy tone plan.