The present disclosure relates generally to communication networks and, more particularly, to wireless local area networks that utilize orthogonal frequency division multiplexing (OFDM).
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.
In an embodiment, a method for adapting an orthogonal frequency division multiplexing (OFDM) numerology configuration for use in a communication network includes adaptively selecting, at a first communication device, one or more OFDM numerology configurations to be used in communication with one or more second communication devices, including adaptively selecting at least one combination of two or more of (i) a guard interval duration, (ii) a tone spacing, (iii) a starting location of the selected guard interval duration, and (iv) a starting location of the selected tone spacing. The method also includes generating, at the first communication device, a physical layer (PHY) data unit to be transmitted to a second communication device of the one or more second communication devices, including using one of the one or more adaptively selected OFDM numerology configurations to generate OFDM symbols of at least a portion of the PHY data unit.
In another embodiment, a first communication device comprises a network interface configured to adaptively select one or more OFDM numerology configurations to be used in communication with one or more second communication devices, including adaptively selecting at least one combination of two or more of (i) a guard interval duration, (ii) a tone spacing, (iii) a starting location of the selected guard interval duration, and (iv) a starting location of the selected tone spacing. The network interface is also configured to generate a physical layer (PHY) data unit to be transmitted to a second communication device of the one or more second communication devices, including using one of the one or more adaptively selected OFDM numerology configurations to generate OFDM symbols of at least a portion of the PHY data unit.
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.
In an embodiment, a first communication device (e.g., an AP) adaptively selects an orthogonal frequency division multiplexing (OFDM) numerology configuration to be used in communicating with one or more second communication devices (e.g., one or more client stations) over an OFDM communication channel. In various embodiment, the first communication device adaptively selects the OFDM numerology configuration based on one or more factors such as specifics of the communication channel (e.g., whether the communication channel is an indoor communication channel or an outdoor communication channel), the maximum expected Doppler shift expected in the communication channel, capabilities of the one or more second communication devices, etc. Selecting OFDM numerology configuration involves selecting one or more of, or a combination of two or more of (i) a guard interval duration to be used with OFDM symbols of at least a portion of a data unit, (ii) a tone spacing to be used with OFDM symbols of at least a portion of a data unit, (iii) a starting location of the selected guard interval duration within the data unit, and (iv) a starting location of the selected tone spacing within the data unit, in various embodiments. Generally speaking, adaptively selecting an appropriate OFDM numerology configuration, e.g. for a particular communication channel or for particular equipment being utilized in communicating over the communication channel, improves throughput and/or quality of communication over the communication channel, as will be explained in more detail below, in at least some embodiments and/or scenarios.
The WLAN 10 includes a plurality of client stations 25. Although four client stations 25 are illustrated in
The client station 25-1 includes a host processor 26 coupled to a network interface device 27. The network interface device 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
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, 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) 24 is/are configured to receive the 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.
The data unit 200 includes a preamble 202, which, in turn, includes a legacy preamble portion 204 and a high efficiency WLAN (HEW) preamble portion 206. The legacy preamble portion 202 includes an L-STF 208, an L-LTF 210, and an L-SIG 212. The HEW preamble portion 706 includes two first HEW signal fields (HEW-SIGAs) 214 including a first HEW signal field (HEW-SIGA1) 214-1 and a second HEW signal field (HEW-SIGA2) 214-2, an HEW short training field (HEW-STF) 216, M HEW long training fields (HEW-LTFs) 218, where M is an integer, and a third HEW signal field (HEW-SIGB) 220. Each of the L-STF 208, the L-LTF 210, the L-SIG 212, the HEW-SIGAs 215, the HEW-STF 216, the M HEW-LTFs 218, and the HEW-SIGB 220 comprises an integer number of one or more OFDM symbols. For example, in an embodiment, the HEW-SIGAs 214 comprise two OFDM symbols, where the HEW-SIGA1214-1 field comprises the first OFDM symbol and the HEW-SIGA2214-2 comprises the second OFDM symbol, in an embodiment. In at least some examples, the HEW-SIGAs 214 are collectively referred to as a single HEW signal field (HEW-SIGA) 214. The L-SIG 212, the HEW-SIGAs 214 and the HEW-SIGB 220 generally carry formatting information for the data unit 200, in an embodiment.
In some embodiments, the data unit 200 also includes a data portion 222. In some embodiments, the data portion 222 includes OFDM data symbols 224 and one or more padding OFDM symbols 226. The OFDM padding symbols 226 correspond to one or more last OFDM symbols of the data portion 222, in an embodiment. In an embodiment, a padding OFDM symbol includes at least some padding bits added at the end of the data portion 226. The data unit 200 omits the padding OFDM symbols 226, or omits the entire data portion 222, in some embodiments.
In the embodiment of
Generally speaking symbol duration of an OFDM symbols, in time, is inversely proportional to the tone spacing used with the OFDM symbol. That is, if Δf corresponds to the tone spacing used with an OFDM symbol, then the time symbol duration of the OFDM symbol is T=1/Δf. Accordingly, a relatively smaller tone spacing used with an OFDM symbol results in a relatively larger symbol duration of the OFDM symbol, and vice versa, in an embodiment. For example, a tone spacing of Δf=312.5 kHz as in
According to an embodiment, the length of the guard interval portion 502 to be used with particular OFDM symbols of the data unit 200 is selected from a set of guard intervals supported by the HEW communication protocol. For example, the set of guard intervals supported by the HEW communication protocol includes 0.4 μs, 0.8 μs, 1.6 μs, and 3.2 μs guard intervals. In other embodiments, the set of guard intervals supported by the HEW communication protocol exclude one or more of 0.4 μs, 0.8 μs, 1.6 μs, and 3.2 μs and/or include one or more suitable guard intervals other than 0.4 μs, 0.8 μs, 1.6 μs, and 3.2 μs instead of or in addition to the guard intervals 0.4 μs, 0.8 μs, 1.6 μs, and 3.2 μs. In an embodiment, in accordance with terminology used in a legacy communication protocol (e.g., the IEEE 802-11n Standard or the IEEE 802-11 ac Standard), a guard interval of 0.8 μs is sometimes referred to herein as a “normal guard interval” and a guard interval of 0.4 μs is sometimes referred to herein as “short guard interval.”
In an embodiment, a first communication device (e.g., the AP 14 of
In an embodiment, the first communication device selects an OFDM numerology configuration to be used in communication with a second communication device based on one or more factors such as specifics of the communication channel (e.g., whether the communication channel is an indoor communication channel or an outdoor communication channel) between the first communication device and the second communication device, the maximum expected Doppler shift expected in the communication channel between the first communication device and the second communication device, capabilities of the second communication device, etc. In an embodiment, adaptively selecting an OFDM numerology configuration includes adaptively selecting a guard interval duration and/or a tone spacing to the used with at least some OFDM symbols of a data unit (or data units) communicated between the first communication device and the second communication device. Generally speaking, a relatively shorter guard interval and a relatively smaller tone spacing (resulting in a relatively longer OFDM symbol duration) reduces overhead and improves throughput in communication between the first communication device and the second communication device. However, a sufficiently long guard interval and/or sufficiently large tone spacing need to be used so as to achieve required or desired signal quality at the receiving communication device, in various embodiments and/or scenarios. Thus, for example, a sufficiently long guard interval is selected such that the guard interval is longer than the worst expected channel delay spread in the communication channel between the first communication device and the second communication device. Similarly, a sufficiently large tone spacing (and resulting sufficiently short OFDM symbol duration) is selected such that the communication channel between the first communication device and the second communication device remains sufficiently constant so as to maintain sufficient subcarrier orthogonality when the OFDM symbol is received by the receiving communication device, in an embodiment. Thus, a tone spacing is selected based at least in part on the worst expected Doppler spread of the communication channel between the first communication device and the second communication device. Further, a sufficiently large tone spacing is selected so as to maintain a sufficiently signal quality (e.g., carrier frequency offset, phase noise, etc.) at the receiving communication device according to receiver capabilities of the receiving communication device.
As discussed above, generally speaking, a guard interval duration is selected to be longer than the worst expected delay spread in the communication channel between the first communication device and the second communication device, in at least some embodiments and/or scenarios. Thus, for example, relatively longer guard intervals are selected for longer (larger coverage) communication channels characterized by generally longer channel delay spreads, such as outdoor communication channels, as compared to relatively shorter guard intervals selected for communication channels characterized by generally shorter channel delay spreads, such as indoor communication channels, in an embodiment. As also discussed above, a tone spacing is selected such that the resulting duration of the OFDM symbol is not too large relative to the rate of change of the communication channel, in some embodiments and/or scenarios. For example, a relatively smaller tone spacing (and the resulting relatively longer OFDM symbol durations) is selected for a slow varying communication channel, or a communication channel characterized by longer coherence time (such as a communication channel associated with a relatively slow moving communication device), as compared to a relatively larger tone spacing (and the resulting relatively shorter OFDM symbol duration) selected for a faster changing communication channel characterized by a relatively shorter coherence time (such as a communication channel associated with a relatively faster moving communication device), in an embodiment.
In some embodiments, the first communication device jointly selects a guard interval duration and a tone spacing so as to maintain a sufficiently low overhead and sufficiently high efficiency in communication between the first communication device and second communication device. For example, in an embodiment, the first communication device generally selects a relatively smaller tone spacing, resulting in a longer OFDM symbol duration, when a relatively longer guard interval is used, for example in case of an outdoor communication channel between the first communication device and the second communication device. Using a longer OFDM symbol duration, in effect, compensates for the longer guard interval, thereby maintaining the same efficiency and throughput as achieved with a shorter guard interval and a shorter OFDM symbols duration, in at least some embodiments and/or scenarios. In some embodiments, the first communication device selects a guard interval duration and/or a tone spacing such that the guard interval duration is a certain percentage, or a certain fraction, of the OFDM symbol duration resulting from the selected tone spacing. For example, a guard interval duration and/or a tone spacing is selected such that the guard interval is ¼ of the OFDM symbol, ⅛ of the OFDM symbol duration, 1/16 of the OFDM symbol duration, etc., or any other suitable fraction of the OFDM symbol duration, in various embodiments and/or scenarios.
In some embodiments, hardware capabilities of the receiving device or devices affect selection of the guard interval duration and/or tone spacing to be used in communication with the receiving device or devices. For example, some receiving devices are better able to handle impairments caused by signal propagation in the communication channel, allowing for relatively shorter guard intervals and/or relatively smaller tone spacing (and resulting longer OFDM symbol duration) to be used in communication with such receiving devices.
In an embodiment, adaptively selecting an OFDM numerology configuration includes adaptively selecting one or more of (i) a tone spacing, (ii) a guard interval duration and (ii) a beginning location for the adaptively selected tone spacing (iv) a beginning location of the adaptively selected guard interval duration. In some embodiments, one or more of (i) a tone spacing, (ii) a guard interval duration and (ii) a beginning location for the adaptively selected tone spacing (iv) a beginning location of the adaptively selected guard interval duration is/are predetermined (e.g., defined in the first communication protocol), and adaptively selecting OFDM numerology configuration includes adaptively selecting the other one or more of (i) a tone spacing, (ii) a guard interval duration and (ii) a beginning location for the adaptively selected tone spacing (iv) a beginning location of the adaptively selected guard interval duration. For example, in an embodiment, the first communication device selects a guard interval duration to be used with at least some OFDM symbols of the data unit 200, and the adaptively selected guard interval duration is used with at least some OFDM symbols of a portion of the data unit 200 beginning at a predetermined location within the data unit 200. As another example, the first communication device adaptively selects a guard interval duration and a starting location of the adaptively selected guard interval duration within the data unit 200, and the adaptively selected guard interval duration is used with at least some OFDM symbols of a portion of the data unit 200 beginning at the adaptively selected starting location within the data unit 200. As yet another example, the first communication device adaptively selects a tone spacing to be used with at least some OFDM symbols of the data unit 200, and the adaptively selected tone spacing is used with at least some OFDM symbols of a portion of the data unit 200 beginning at a predetermined location within the data unit 200. As another example, the first communication device adaptively selects a tone spacing and a starting location of the adaptively selected tone spacing within the data unit 200, and the adaptively selected guard interval duration is used with at least some OFDM symbols of a portion of the data unit 200 beginning at the adaptively selected starting location within the data unit 200. As yet another example, in yet another embodiment, the first communication device adaptively selects a guard interval duration and a tone spacing to be used with at least some OFDM symbols of the data unit 200, and the adaptively selected tone spacing and guard interval duration are used with at least some OFDM symbols in a portion (or in respective portions) of the data unit 200 beginning at a predetermined location (or at respective predetermined locations) within the data unit 200.
As yet another example, in another embodiment, the first communication device adaptively selects a guard interval duration, a tone spacing, and a starting location of the adaptively selected guard interval duration within the data unit 200. In this embodiment, the adaptively selected guard interval duration is used with at least some OFDM symbols in a portion of the data unit 200 beginning at the adaptively selected starting location within the data unit 200, while the adaptively selected tone spacing is used with at least some OFDM symbols in a portion of the data unit 200 beginning at a predetermined location within the data unit 200. As yet another example, in another embodiment, the first communication device adaptively selects a guard interval duration, a tone spacing, and a starting location of the adaptively selected tone spacing within the data unit 200. In this embodiment, the adaptively selected guard interval duration is used with at least some OFDM symbols in a portion of the data unit 200 beginning at a predetermined location within the data unit 200, while the adaptively selected tone spacing is used with at least some OFDM symbols in a portion of the data unit 200 beginning at the adaptively selected starting location within the data unit 200.
As still another example, in still another embodiment, the first communication device the first communication device adaptively selects a guard interval duration, a tone spacing, a starting location of the adaptively selected guard interval duration within the data unit 200, and a starting location of the adaptively selected tone spacing within the data unit 200. In this embodiment, the adaptively selected guard interval duration is used with at least some OFDM symbols in a portion of the data unit 200 beginning at the adaptively selected starting location of the selected guard interval duration within the data unit 200, and the adaptively selected tone spacing is used with at least some OFDM symbols in a portion of the data unit 200 beginning at the adaptively selected starting location of the selected tone spacing within the data unit 200. As yet another example, in yet another embodiment, the first communication device adaptively selects a guard interval duration, a tone spacing, and a staring location of the selected guard interval duration and tone spacing. In this embodiment, the adaptively selected guard interval duration and tone spacing are used with at least some OFDM symbols in a portion of the data unit 200 beginning at the adaptively selected starting location within the data unit 200.
In an embodiment, the first communication device additionally adaptively selects a beginning location of the second portion of the data unit (i.e., the location at which to start using the adaptively selected tone spacing and guard interval duration). For example, with continued reference to
In an embodiment, upon adaptively selecting OFDM numerology configuration to be used with the second communication device, the first communication device signals the selected OFDM numerology configuration to the second communication device. For example, in an embodiment, an indication of the adaptively selected OFDM numerology configuration is included in a preamble of a data unit transmitted from the first communication device to the second communication device. With reference to
In an embodiment, the beginning location sub-field 502-3 includes a single bit. The value of the single bit of the beginning location sub-field 502-3 indicates one of two options for beginning location of the second portion at which the adaptively selected tone spacing indicated by the TS sub-field 502-1 and the adaptively selected guard interval indicated by the GI sub-field 502-2. As just an example, a first value of the single bit of the beginning location sub-field 502-3 indicates that the tone spacing indicated by the TS sub-field 502-1 and the guard interval indicated by the GI sub-field 502-2 begins at the HEW data portion 222 of the data unit 200 (i.e., with the first OFDM symbol of the HEW data portion 222), and a second value of the single bit of the beginning location sub-field 502-3 indicates that the tone spacing indicated by the TS sub-field 502-1 and the guard interval indicated by the GI sub-field 502-2 begins at the first HEW-LTF field 218-1 of the data unit 200. In other embodiments, the beginning location sub-field 502-3 includes a number of bits other than one bit (e.g., 2 bits, 3 bits, etc.) In such embodiment, the beginning location sub-field 502-3 is capable of indicating more than two possible starting location options for the second portion of the data unit 200. In some embodiments, a single predetermined beginning location is defined as the beginning location of the second portion of the data unit 200 at which the adaptively selected tone spacing indicated by the TS sub-field 502-1 and the adaptively selected guard interval indicated by the GI sub-field 502-2 begins in the data unit 200. In such embodiments, the beginning location sub-field 502-3 to indicate the beginning location of the second portion of the data unit 200 is not needed and is omitted from the numerology indication field 500.
Turning now to
In an embodiment, in addition to or instead of indicating adaptively selected OFDM numerology configuration in a preamble of a data unit such as the data unit 200, the AP 14 signals the selected OFDM numerology configuration in a management frame or a control frame transmitted by the AP 14. For example, in an embodiment, the AP 14 selects a particular OFDM numerology configuration to be used in the network 10, and broadcasts the selected OFDM numerology configuration in a management frame or a control frame to the client stations 25 in the network 10. In an embodiment, the AP 14 broadcasts the selected OFDM numerology configuration in a beacon frame. In other embodiments, the AP 14 signals the selected OFDM numerology configuration in a suitable management of control frame other than a beacon frame. Then, the AP 14 transmits data units, such as the data unit 200, to the client stations 25 using the selected OFDM numerology configuration signaled to the client stations 25 in the management frame or the control frame.
In some embodiments, the AP 14 adaptively selects more than one OFDM configuration that can be used in the network 10. For example, the AP 14 considers communication channels between the AP14 and multiple ones of the client stations 25 within the network 10 to select multiple OFDM configurations based on channel characteristics of the respective communication channels between the AP14 and multiple ones of the client stations 25 within the network 10, in an embodiment. In one such embodiment, the AP 14 then transmits a management frame or a control frame to the multiple client stations 25 to signal the several possible OFDM numerology configurations selected by the AP 14 for communication with the client stations 25. The AP 14 then dynamically selects a particular one of the multiple selected OFDM numerology configurations to be used with a particular client station 25 and/or a particular data unit to be transmitted to a particular client station 25, in an embodiment. The AP 14 signals the particular selected OFDM numerology configuration in a preamble of a data unit transmitted to the client station 25, in some such embodiment. For example, the AP 14 signals the particular selected OFDM numerology configuration in a signal field of the preamble, such as in the HEW-SIGA field 214 or the HEW-SIGB field 220 of the data unit 200. For example, the signal field (e.g., the HEW-SIGA field 214 or the HEW-SIGB field 220) includes a one bit indication to indicate whether a first selected OFDM numerology configuration is used in the data unit or a second selected OFDM numerology configuration is used in the data unit. As another example, in another embodiment, the signal field (e.g., the HEW-SIGA field 214 or the HEW-SIGB field 220) includes a two bit indication to indicate a particular one of three, or a particular one of one or four, selected OFDM configurations that is used in the data unit. The signal field includes other suitable numbers of bits used to signal a particular one of other numbers of multiple selected OFDM configurations, in other embodiments.
In another embodiment, a client station (e.g., the client station 25-1) negotiates with the AP 14 to agree on one or more OFDM numerology configurations that can be used in communication between the client station 25 and the AP 14. For example, the client station 25 signals, in a management or control frame transmitted to the AP 14, receiver capabilities of the client station 25, and the AP 14 selects one or more OFDM numerology configurations supported by the client station 25 according to the receiver capabilities signaled by the client station 25. In an embodiment, the management or control frame used by the client station 25 to signal receiver capabilities of the client station 25 is one of a probe frame, an association frame, or a re-association frame. In other embodiments, the management or control frame used by the client station 25 to signal receiver capabilities of the client station 25 is a suitable frame other than a probe frame, an association frame, or a re-association frame.
In an embodiment in which more than one OFDM numerology configuration are selected for use in the network 10, a particular one of the selected OFDM numerology configurations is selected for a data unit, or for multiple consecutive data units, communicated between the AP 14 and the client station 25. In this embodiment, a data unit transmitted from the AP 14 to the client station 25 (or transmitted from the client station 25 to the AP 14) includes an indication of the particular OFDM numerology configuration used for transmission of the data unit. For example, the signal field (e.g., the HEW-SIGA field 214 or the HEW-SIGB field 220) includes a one bit indication to indicate whether a first selected OFDM numerology configuration is used in the data unit or a second selected OFDM numerology configuration is used in the data unit. As another example, in another embodiment, the signal field (e.g., the HEW-SIGA field 214 or the HEW-SIGB field 220) includes a two bit indication to indicate a particular one of three, or a particular one of one or four, selected OFDM configurations that is used in the data unit.
In another embodiment in which the AP 14 selects several possible OFDM numerology configurations to be used in the network 10, or negotiates several possible OFDM numerology configurations with a client station 25 in the network 10, a particular one of the several possible OFDM numerology configuration selected for a data unit is not explicitly signaled in the data unit. In an embodiment in which a particular one of the several possible OFDM numerology configuration selected for a data unit is not explicitly signaled in the data unit, a receiving device of the data unit (e.g., a client station 25 or the AP 14) automatically detects which particular one of the several possible OFDM numerology configurations is used in the data unit. For example, in an embodiment, the receiving device tests hypothesis corresponding to each one of the several possible OFDM numerology configurations to determine which one of the tested hypothesis most likely corresponds to the particular OFDM numerology configuration used in the data unit. As just an example, in an embodiment, the AP 14 selects four possible combinations of guard interval and tone spacing that can be used in communication with a client station 25 (e.g., GI=0.8 μs/TS=normal tone spacing (Δf), GI=0.8 μs/TS=½Δf, GI=1.6 μs/TS=Δf, and GI=1.6 μs/TS=½ Δf). A receiving device (e.g., a client station 25) receiving a data unit performs respective cross correlations of the received signal using each of the four selected OFDM numerology configurations, in an embodiment. In particular, the receiving device performs cross-correlations using FFT size corresponding to the Δf tone spacing, and cross-correlations using FFT size corresponding to the ½Δf tone spacing, and using corresponding OFDM symbol durations as the cross-correlation interval for each of the tone spacing configurations, in an embodiment. Similarly, the receiving device performs cross-correlations using each of the possible guard interval durations (0.8 μs and 1.6 μs), and the corresponding cyclic prefix length, which determines the length of the cross-correlation, in an embodiment. The receiving device then selects the hypothesis (the tone spacing/guard interval combination) that resulted in the highest result of the corresponding cross-correlation as the OFDM numerology configuration used in the data unit, in an embodiment. Accordingly, the receiving device demodulates and decodes the data unit using the detected the OFDM numerology configuration used in the data unit, in an embodiment.
At block 602, one or more OFDM numerology configurations are adaptively selected. In an embodiment, selecting the one or more OFDM configurations at block 602 includes selecting at least one combination of two or more of (i) a guard interval duration, (ii) a tone spacing, (iii) a starting location of the guard interval and (iv) a staring location of the tone spacing. In an embodiment, the one or more OFDM numerology configurations are adaptively selected to adapt to particular communication channel characteristics of the communication channel between a first communication device and a second communication device. For example, in an embodiment, the or more OFDM numerology configurations are selected based at least in part on (i) communication channel types of communication channels between the first communication device and the one or more second communication devices, (ii) maximum expected Doppler shifts expected in the communication channels between the first communication device and the one or more second communication devices, and (iii) receiver capabilities of the one or more second communication devices.
At block 604, a data unit is generated. In an embodiment, generating the data unit at block 604 includes generating OFDM symbols of at least a portion of the data unit using one of the one or more OFDM numerology configurations adaptively selected at block 602. In an embodiment, generating the OFDM data unit at block 604 further includes using a predetermined OFDM configuration to generate OFDM symbols of another portion of the data unit.
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.
This disclosure claims the benefit of U.S. Provisional Patent Application No. 61/986,726, entitled “Adaptive OFDM Numerology for High Efficiency WiFi” and filed on Apr. 30, 2014, the disclosure of which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5878057 | Maa | Mar 1999 | A |
6167515 | Lin | Dec 2000 | A |
6192498 | Arato | Feb 2001 | B1 |
6226771 | Hilla et al. | May 2001 | B1 |
6427219 | Yang | Jul 2002 | B1 |
6553534 | Yonge, III et al. | Apr 2003 | B2 |
6704364 | Lim et al. | Mar 2004 | B1 |
6856590 | Okada et al. | Feb 2005 | B2 |
6888844 | Mallory et al. | May 2005 | B2 |
6891881 | Trachewsky et al. | May 2005 | B2 |
6910172 | Hara et al. | Jun 2005 | B2 |
6934902 | Hara et al. | Aug 2005 | B2 |
7046746 | Keaney et al. | May 2006 | B1 |
7080348 | Savage | Jul 2006 | B2 |
7145955 | Bohnke et al. | Dec 2006 | B1 |
7203885 | Gibart | Apr 2007 | B2 |
7257758 | Manula et al. | Aug 2007 | B1 |
7336667 | Allen, Jr. et al. | Feb 2008 | B2 |
7388853 | Ptasinski et al. | Jun 2008 | B2 |
7406106 | Mallory | Jul 2008 | B2 |
7453285 | Kiel et al. | Nov 2008 | B2 |
7478314 | Cheong et al. | Jan 2009 | B1 |
7558537 | Trachewsky et al. | Jul 2009 | B2 |
7577210 | Lee | Aug 2009 | B2 |
7599332 | Zelst et al. | Oct 2009 | B2 |
7626576 | Anandakumar et al. | Dec 2009 | B2 |
7733939 | Trachewsky | Jun 2010 | B2 |
7742390 | Mujtaba | Jun 2010 | B2 |
7773565 | Hansen et al. | Aug 2010 | B2 |
7822005 | Ptasinski et al. | Oct 2010 | B2 |
7889707 | Niu et al. | Feb 2011 | B2 |
7904519 | Czotscher et al. | Mar 2011 | B2 |
7920599 | Subramanian et al. | Apr 2011 | B1 |
7961593 | Porat et al. | Jun 2011 | B2 |
7974225 | Kasher | Jul 2011 | B2 |
7987405 | Turner et al. | Jul 2011 | B2 |
8010865 | Gu et al. | Aug 2011 | B2 |
8046663 | Yoon | Oct 2011 | B2 |
8111704 | Singhal et al. | Feb 2012 | B2 |
8144647 | Nabar et al. | Mar 2012 | B2 |
8155138 | van Nee | Apr 2012 | B2 |
8179897 | Allen, Jr. et al. | May 2012 | B2 |
8201065 | Cheong et al. | Jun 2012 | B1 |
8218554 | Allen, Jr. et al. | Jul 2012 | B2 |
8223072 | Ponnuswamy | Jul 2012 | B2 |
8225187 | Schultz et al. | Jul 2012 | B1 |
8234551 | Shen et al. | Jul 2012 | B2 |
8245108 | Yoon | Aug 2012 | B2 |
8264977 | Sanguineti et al. | Sep 2012 | B2 |
8289869 | Sawai | Oct 2012 | B2 |
8310981 | Damnjanovic et al. | Nov 2012 | B2 |
8331419 | Zhang et al. | Dec 2012 | B2 |
8332719 | You et al. | Dec 2012 | B2 |
8339978 | Sawai et al. | Dec 2012 | B2 |
8369301 | Cai | Feb 2013 | B2 |
8397126 | Xu et al. | Mar 2013 | B2 |
8418024 | You et al. | Apr 2013 | B2 |
8462863 | Zhang et al. | Jun 2013 | B1 |
8494089 | Aoki et al. | Jul 2013 | B2 |
8498362 | Zhang et al. | Jul 2013 | B2 |
8509051 | Ling et al. | Aug 2013 | B2 |
8526351 | Fischer et al. | Sep 2013 | B2 |
8527853 | Lakkis | Sep 2013 | B2 |
8532077 | Stacey et al. | Sep 2013 | B2 |
8539287 | Lee et al. | Sep 2013 | B2 |
8542589 | Surineni et al. | Sep 2013 | B2 |
8543884 | Mansour | Sep 2013 | B2 |
8599804 | Erceg et al. | Dec 2013 | B2 |
8619907 | Mujtaba et al. | Dec 2013 | B2 |
8627171 | Pi | Jan 2014 | B2 |
8681757 | Lee et al. | Mar 2014 | B2 |
8718021 | Yu et al. | May 2014 | B2 |
8724720 | Srinivasa et al. | May 2014 | B2 |
8737189 | Hansen et al. | May 2014 | B2 |
8867653 | Zhang et al. | Oct 2014 | B2 |
8873680 | Zhang | Oct 2014 | B2 |
8885740 | Zhang et al. | Nov 2014 | B2 |
8948283 | Zhang | Feb 2015 | B2 |
8953696 | Stoye | Feb 2015 | B2 |
8982889 | Zhang | Mar 2015 | B2 |
9130727 | Zhang et al. | Sep 2015 | B2 |
9131528 | Zhang et al. | Sep 2015 | B2 |
9178745 | Zhang et al. | Nov 2015 | B2 |
9184794 | Ibrahim et al. | Nov 2015 | B1 |
9184967 | Ibrahim et al. | Nov 2015 | B1 |
9209837 | Cheong et al. | Dec 2015 | B1 |
9232435 | Schliwa-Bertling et al. | Jan 2016 | B2 |
9258829 | Ibrahim et al. | Feb 2016 | B1 |
9294164 | Zhang et al. | Mar 2016 | B2 |
9294323 | Zhang | Mar 2016 | B2 |
9397785 | Zhang et al. | Jul 2016 | B1 |
9414432 | Zhang | Aug 2016 | B2 |
9712358 | Zhang et al. | Jul 2017 | B2 |
20030012160 | Webster et al. | Jan 2003 | A1 |
20030031151 | Sharma et al. | Feb 2003 | A1 |
20030056043 | Kostadinov | Mar 2003 | A1 |
20030142626 | Umayabashi et al. | Jul 2003 | A1 |
20040081131 | Walton et al. | Apr 2004 | A1 |
20050169261 | Williams et al. | Aug 2005 | A1 |
20050237918 | Asai | Oct 2005 | A1 |
20050243774 | Choi et al. | Nov 2005 | A1 |
20060116091 | Hammes | Jun 2006 | A1 |
20060176966 | Stewart et al. | Aug 2006 | A1 |
20060250940 | Tirkkonen | Nov 2006 | A1 |
20070002878 | Moorti et al. | Jan 2007 | A1 |
20070014375 | Nakao | Jan 2007 | A1 |
20070047666 | Trachewsky | Mar 2007 | A1 |
20070147226 | Khandekar | Jun 2007 | A1 |
20070153760 | Shapira | Jul 2007 | A1 |
20070153830 | Xhafa et al. | Jul 2007 | A1 |
20070159957 | Ljung | Jul 2007 | A1 |
20070183307 | Akita | Aug 2007 | A1 |
20070183523 | Koo et al. | Aug 2007 | A1 |
20070204052 | Trainin | Aug 2007 | A1 |
20070268812 | Yoon | Nov 2007 | A1 |
20080056393 | Niu et al. | Mar 2008 | A1 |
20080298435 | Lakkis | Dec 2008 | A1 |
20080299962 | Kasher | Dec 2008 | A1 |
20090004971 | Dateki | Jan 2009 | A1 |
20090034635 | Von Elbwart et al. | Feb 2009 | A1 |
20090103485 | Singh et al. | Apr 2009 | A1 |
20090103649 | Vare | Apr 2009 | A1 |
20090185632 | Cai | Jul 2009 | A1 |
20090196163 | Du | Aug 2009 | A1 |
20090285321 | Schulz | Nov 2009 | A1 |
20100046358 | van Nee | Feb 2010 | A1 |
20100046542 | van Zelst et al. | Feb 2010 | A1 |
20100046656 | van Nee et al. | Feb 2010 | A1 |
20100074277 | Nishibayashi et al. | Mar 2010 | A1 |
20100091675 | Sawai | Apr 2010 | A1 |
20100202301 | Wen et al. | Aug 2010 | A1 |
20100232542 | Miyoshi et al. | Sep 2010 | A1 |
20100260159 | Zhang et al. | Oct 2010 | A1 |
20100309834 | Fischer et al. | Dec 2010 | A1 |
20100309848 | Erceg et al. | Dec 2010 | A1 |
20100310002 | Lauer et al. | Dec 2010 | A1 |
20110002219 | Kim et al. | Jan 2011 | A1 |
20110026639 | Rouquette-Leveil et al. | Feb 2011 | A1 |
20110092231 | Yoo et al. | Apr 2011 | A1 |
20110103366 | Morimoto | May 2011 | A1 |
20110110348 | Lee et al. | May 2011 | A1 |
20110134899 | Jones, IV et al. | Jun 2011 | A1 |
20110142020 | Kang et al. | Jun 2011 | A1 |
20110149927 | Stacey et al. | Jun 2011 | A1 |
20110194655 | Sampath et al. | Aug 2011 | A1 |
20110222490 | Fischer et al. | Sep 2011 | A1 |
20110255620 | Jones, IV et al. | Oct 2011 | A1 |
20110271169 | Pi | Nov 2011 | A1 |
20110280182 | Kim et al. | Nov 2011 | A1 |
20110299382 | Van Nee et al. | Dec 2011 | A1 |
20110305286 | Shimezawa | Dec 2011 | A1 |
20110305296 | Van Nee | Dec 2011 | A1 |
20120039292 | Lee et al. | Feb 2012 | A1 |
20120039406 | Srinivasa et al. | Feb 2012 | A1 |
20120054587 | Van Nee et al. | Mar 2012 | A1 |
20120069746 | Park | Mar 2012 | A1 |
20120122495 | Weng et al. | May 2012 | A1 |
20120155447 | Vermani et al. | Jun 2012 | A1 |
20120170563 | Abraham et al. | Jul 2012 | A1 |
20120195391 | Zhang et al. | Aug 2012 | A1 |
20120201316 | Zhang et al. | Aug 2012 | A1 |
20120294268 | Lee et al. | Nov 2012 | A1 |
20120294294 | Zhang | Nov 2012 | A1 |
20120294392 | Zhang | Nov 2012 | A1 |
20120300874 | Zhang | Nov 2012 | A1 |
20120327871 | Ghosh | Dec 2012 | A1 |
20130039313 | Hansen et al. | Feb 2013 | A1 |
20130070869 | Motamed et al. | Mar 2013 | A1 |
20130121244 | Vermani et al. | May 2013 | A1 |
20130121348 | Zhang et al. | May 2013 | A1 |
20130122822 | Srinivasan et al. | May 2013 | A1 |
20130128807 | Vermani et al. | May 2013 | A1 |
20130202001 | Zhang | Aug 2013 | A1 |
20130216002 | Suh et al. | Aug 2013 | A1 |
20130259017 | Zhang et al. | Oct 2013 | A1 |
20130294317 | Malladi et al. | Nov 2013 | A1 |
20140029681 | Zhang et al. | Jan 2014 | A1 |
20140064194 | Schliwa-Bertling et al. | Mar 2014 | A1 |
20140112168 | Chen et al. | Apr 2014 | A1 |
20140185662 | Azizi et al. | Jul 2014 | A1 |
20140185695 | Kenney et al. | Jul 2014 | A1 |
20140211775 | Sampath et al. | Jul 2014 | A1 |
20140269770 | Kenney et al. | Sep 2014 | A1 |
20140307612 | Vermani | Oct 2014 | A1 |
20140314064 | Park | Oct 2014 | A1 |
20140328435 | You | Nov 2014 | A1 |
20140337690 | Zhang | Nov 2014 | A1 |
20140348047 | Park | Nov 2014 | A1 |
20140355626 | Fechtel | Dec 2014 | A1 |
20140362935 | Porat et al. | Dec 2014 | A1 |
20150009894 | Vermani | Jan 2015 | A1 |
20150009978 | Choi | Jan 2015 | A1 |
20150030101 | Zhang et al. | Jan 2015 | A1 |
20150071372 | Zhang | Mar 2015 | A1 |
20150117227 | Zhang et al. | Apr 2015 | A1 |
20150117363 | Rong | Apr 2015 | A1 |
20150117433 | Zhang et al. | Apr 2015 | A1 |
20150180622 | Yoo | Jun 2015 | A1 |
20150207521 | Waters | Jul 2015 | A1 |
20150256308 | Ma | Sep 2015 | A1 |
20150264161 | Tian | Sep 2015 | A1 |
20150295676 | Kenney et al. | Oct 2015 | A1 |
20150381311 | Zhang et al. | Dec 2015 | A1 |
20150381394 | Zhang et al. | Dec 2015 | A1 |
20160050097 | Atungsiri | Feb 2016 | A1 |
20160072654 | Choi | Mar 2016 | A1 |
20160156750 | Zhang et al. | Jun 2016 | A1 |
20160204968 | Zhang | Jul 2016 | A1 |
20160212001 | Azizi | Jul 2016 | A1 |
20160234779 | Kenney | Aug 2016 | A1 |
20160241366 | Azizi | Aug 2016 | A1 |
20160353370 | Choi | Dec 2016 | A1 |
20170027001 | Choi | Jan 2017 | A1 |
20170033960 | Choi | Feb 2017 | A1 |
20170310514 | Zhang et al. | Oct 2017 | A1 |
20170310515 | Zhang et al. | Oct 2017 | A1 |
20170324598 | Suh | Nov 2017 | A1 |
20180048740 | Zhang et al. | Feb 2018 | A1 |
Number | Date | Country |
---|---|---|
1271477 | Oct 2000 | CN |
1571512 | Jan 2005 | CN |
1989748 | Jun 2007 | CN |
101282194 | Oct 2008 | CN |
101321034 | Dec 2008 | CN |
101562502 | Oct 2009 | CN |
103081427 | May 2013 | CN |
1968225 | Sep 2008 | EP |
2005-304063 | Oct 2005 | JP |
2007-506359 | Mar 2007 | JP |
2013-543672 | Dec 2013 | JP |
2013-543677 | Dec 2013 | JP |
WO-03005652 | Jan 2003 | WO |
WO-2006025996 | Mar 2006 | WO |
WO-2007074777 | Jul 2007 | WO |
WO-2008046163 | Apr 2008 | WO |
WO-2009052420 | Apr 2009 | WO |
WO-2009059229 | May 2009 | WO |
WO-2009084926 | Jul 2009 | WO |
WO-2009114612 | Sep 2009 | WO |
WO-2010120692 | Oct 2010 | WO |
WO-2011087560 | Jul 2011 | WO |
WO-2012039640 | Mar 2012 | WO |
WO-2012040396 | Mar 2012 | WO |
WO-2012106635 | Aug 2012 | WO |
WO-2012122119 | Sep 2012 | WO |
WO-2012122119 | Sep 2012 | WO |
WO-2013152111 | Oct 2013 | WO |
WO-2014183059 | Nov 2014 | WO |
Entry |
---|
Park, IEEE P802.11 Wireless LANs, Proposed Specification Framework for TGah, IEEE 802.11-11-1137r13, Jan. 2013, pp. 1, 3, 8. |
Choi et al., U.S. Appl. No. 61/820,185, filed May 7, 2013, whole document (Year: 2013). |
Wikipedia entry for Guard interval, Apr. 7, 2014, whole document (Year: 2014). |
Choi et al., Wirelesslan Preamble Design for Backward Compatibility (U.S. Appl. No. 61/935,805), filed Feb. 4, 2014, USPTO, whole document (Year: 2014). |
IEEE Std 802.11™ 2012 (Revision of IEEE Std 802.11-2007) IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, The Institute of Electrical and Electronics Engineers, Inc., pp. 1-2695 (Mar. 29, 2012). |
IEEE Std 802.11ac/D6.0 “Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 4: Enhancements for Very High Throughput for Operation in Bands below 6 GHZ,” The Institute of Electrical and Electronics Engineers, Inc., pp. 1-446 (Jul. 2013). |
IEEE Std 802.11af/D1.05 “Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 4: TV White Spaces Operation,” The Institute of Electrical and Electronics Engineers, Inc., pp. 1-123 (Nov. 2011). |
Lee et al., “TGaf PHY proposal,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-12/0809r5, pp. 1-43, Jul. 10, 2012. |
De Vegt, “Potential Compromise for 802.11ah Use Case Document”, Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/0457r0, pp. 1-27 (Mar. 2011). |
Park, “Proposed Specification Framework for TGah”, The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1137r6, pp. 1-13 (Mar. 2012). |
Park, “Proposed Specification Framework for TGah D9.x”, The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-yy/xxxxr0, pp. 1-30 (Jul. 2012). |
Park, “Proposed Specification Framework for TGah”, The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1137r11, pp. 1-36 (Sep. 2012). |
Park, “Specification Framework for TGah,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1137r13, pp. 1-58 (Jan. 14, 2013). |
Shao, “Channel Selection for 802.11ah,” doc.: IEEE 802.11-12/0816r0, pp. 1-11 (Jul. 2012). |
Taghavi et al., “Introductory Submission for TGah”, doc. No. IEEE 802.11-11/0062r0, Institute for Electrical and Electronics Engineers, pp. 1-5 (Jan. 14, 2011). |
Vermani et al. “Preamble Format for 1 MHz,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1482r2, pp. 1-30 (Nov. 2011). |
Vermani et al. “Spec Framework Text for PHY Numerology,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1311r0, pp. 1-5 (Sep. 2011). |
Yu et al., “Coverage extension for IEEE802.11ah,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/0035r1, pp. 1-10 (Jan. 2011). |
Zhang et al., “11ah Data Transmission Flow,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-11/1484r1, pp. 1-15 (Nov. 2011). |
Zhang et al., “1MHz Waveform in Wider BW ”, The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-12/0309r1, pp. 1-10 (Mar. 2012). |
Zhang et al., “Beamforming Feedback for Single Stream,” The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-12/1312r0, pp. 1-22 (Nov. 12, 2012). |
IEEE Std 802.11ac/D7.0 “Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 4: Enhancements for Very High Throughput for Operation in Bands below 6 GHZ,” The Institute of Electrical and Electronics Engineers, Inc., pp. 1-456 (Sep. 2013). |
Chen, “Home Network Basis: Transmission Environments and Wired/Wireless Protocols,” Prentice Hall, pp. 1-26 (Jul. 2003). |
Hiertz et al., “The IEEE 802.11 Universe,” IEEE Communications Magazine, pp. 62-70, (Jan. 2010). |
Mujtaba, “IEEE P802.11—Wireless LANs, TGn Sync Proposal Technical Specification,” The Institute of Electrical and Electronics Engineers, Inc., doc.: IEEE 802.11-04/0889r6, pp. 1-131 (May 2005). |
Perahia, et al., “Gigabit Wireless LANs: an overview of IEEE 802.11ac and 80211ad,” ACM SIGMOBILE Mobile Computing and Communications Review, vol. 15, No. 3, pp. 23-33 (Jul. 2011). |
Stacey et al., “IEEE P802.11, Wireless LANs, Proposed TGac Draft Amendment,” Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-10/1361r3 pp. 1-154 (Jan. 2011). |
Stacey et al., “Specification Framework for TGac,” document No. IEEE 802.11-09/0992r20, Institute for Electrical and Electronics Engineers, pp. 1-49, (Jan. 18, 2011). |
Van Nee et al. “The 802.11n MIMO-OFDM Standard for Wireless LAN and Beyond,” Wireless Personal Communications, vol. 37, pp. 445-453 (Jun. 2006). |
Invitation to Pay Fees and Partial International Search Report for International Application No. PCT/US2014/054991, dated Mar. 17, 2015 (6 pages). |
“IEEE P802.11n™/D3.00, Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 4: Enhancements for Higher Throughput,” The Institute of Electrical and Electronics Engineers, Inc., Sep. 2007. |
Chun et al., “Legacy Support on HEW frame structure,” doc: IEEE 11-13/1057r0, The Institute of Electrical and Electronics Engineers, Inc., pp. 1-8 (Sep. 2013). |
Francis, Michael, “Viterbi Decoder Block Decoding—Trellis Termination and Tail Biting,” Xilinx XAPP551 v2.0, pp. 1-21 (Jul. 30, 2010). |
Gunnam, et al., “Multi-Rate Layered Decoder Architecture for Block LDPC Codes of the IEEE 802.11n Wireless Standard,” IEEE International Symposium on Circuits and Systems, 2007 (ISCAS 2007), pp. 1645-1648 (2007). |
Harada, “Project: IEEE P802.15 Working Group for Wireless Personal Area Network (WPANs),” IEEE 802.15-07-0693-003c (May 2007). |
IEEE P802.15.4m/D3, May 2013 IEEE Standard for Local metropolitan area networks—“Part 15.4: Low Rate Wireless Personal Area Networks (LR-WPANs)”, Amendment 6: TV White Space Between 54 MHz and 862 MHz Physical Layer, Excerpt, 2 pages (May 2013). |
IEEE Std 802.11ad™/D9.0 “Draft Standard for Information technology—Telecommunications and information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements” Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band The Institute of Electrical and Electronics Engineers, Inc., (Jul. 2012). |
IEEE Std P802.11 ad/D5.0 “Draft Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band,” The Institute of Electrical and Electronics Engineers, Inc., Sep. 2011. |
Imashioya et al., “RTL Design of 1.2 Gbps MIMO WLAN System and Its Business Aspect,” IEEE 9th Int'l Symposium on Communications and Information Technology (ISCIT 2009), The Institute of Electrical and Electronics Engineers, pp. 296-301 (2009). |
Park, “Proposed Specification Framework for TGah”, The Institute of Electrical and Electronics Engineers, doc. No. IEEE 802.11-yy/xxxxr05, (Jan. 2012). |
Seok et al., “HEW PPDU Format for Supporting MIMO-OFDMA,” IEEE 802.11-14/1210r0, 16 pages, (Sep. 14, 2014). |
Shi et al., “Phase Tracking During VHT-LTF,” Doc. No. IEEE 802.11-10/0771r0, The Institute of Electrical and Electronics Engineers, Inc., pp. 1-19 (Jul. 2010). |
Syafei et al., “A Design of Next Generation Gigabit MIMO Wireless LAN System ,” IEEE 12th Int'l Conference on Advanced Communication Technology (ICACT 2010), The Institute of Electrical and Electronics Engineers, pp. 941-946 (2010). |
Syafei et al., “A Gigabit MIMO WLAN System with International Standardization Strategy,” IEEE Int'l Symposium on Intelligent Signal Processing and Communication Systems (ISPACS 2009), The Institute of Electrical and Electronics Engineers, pp. 228-231 (2009). |
Syafei et al., “Design of 1.2 Gbps MIMO WLAN System for 4K Digital Cinema Transmission,” IEEE 20th Int'l Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC 2009), The Institute of Electrical and Electronics Engineers, pp. 207-211 (2009). |
Van Zelst et al., “Pilot Sequence for VHT-DATA,” Doc. No. IEEE 802.11-10/0811r1, The Institute of Electrical and Electronics Engineers, Inc., pp. 1-10 (Jul. 2010). |
Zhang Zhao-Yang: “A Novel AFDM Transmission Scheme with Length-Adaptive Cyclic Prefix,” Journal of Zhejiang University. Science, Zhejiant University Press, Hangzhou, CN vol. 5, No. 11, Jul. 7, 2003, pp. 1336-1342. |
IEEE P802.11ah™/D1.3 “Draft Standard for Information Technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 6: Sub 1 GHz License Exempt Operation,” The Institute of Electrical and Electronics Engineers, Inc., pp. 1-466 (Apr. 2014). |
Number | Date | Country | |
---|---|---|---|
61986726 | Apr 2014 | US |