1 / 10

Proposed 802.11ax Specification Framework - Background

Proposed 802.11ax Specification Framework - Background. Authors:. Date: 2014-11-03. Abstract. This document describes some possible considerations on 802.11ax specification framework document. Why SFD Discussion is Needed. In terms of time-line

aresler
Download Presentation

Proposed 802.11ax Specification Framework - Background

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposed 802.11ax Specification Framework - Background Authors: Date: 2014-11-03 Minho Cheong, ETRI

  2. Abstract This document describes some possible considerations on 802.11ax specification framework document Minho Cheong, ETRI

  3. Why SFD Discussion is Needed • In terms of time-line • As the TGax agreed before in March 2014 (option B selected among three schedule options suggested), initial version of 802.11ax SFD is expected to introduce in November, 2014 • Because we may not have enough time on the entire progress of 802.11ax compared to the potential schedule of other competing specifications which also tries to utilize the unlicensed 5GHz band. • In terms of TG-level productivity • It may be highly recommended to have in common discussion in the TGax on specification (framework) growing even at its initial stage to get wide and more solid consensus Minho Cheong, ETRI

  4. What We’ve Done Before on SFD • Initial version of 802.11ac SFD (September, 2009) • 3 VHT Physical Layer • This section describes the functional blocks in the physical layer. • 3.1 Channelization • R3.1.A: The draft specification shall include support for 80 MHz PHY transmission. • For 80 MHz operation, the channelization shown in Figure xxx shall be used. • Include figure or table showing 80 MHz channelization in major regulatory domains • 3.2 Preamble • 3.2.1 VHT mixed format preamble • A VHT mixed format (MF) preamble shall be supported in the draft specification and device support is mandatory. The VHT mixed format preamble shall have the following characteristics: • R3.2.1.A: Robust legacy 11a deferral. The VHT MF preamble shall be designed such that a legacy 11a device will defer for the duration of the transmission to the same degree that it does for an HT MF preamble. • R3.2.1.B: Robust legacy 11n deferral. A VHT MF preamble shall be designed such that a legacy HT STA will defer for the duration of the transmission to the same degree that it does for an HT MF transmission. Minho Cheong, Newracom, Inc.

  5. What We’ve Done Before on SFD • Initial version of 802.11ac SFD (September, 2009) • R3.2.1.D: The VHT MF preamble shall include training for • a wider channel • 1 to TBD spatial streams (see Section 3.4) • DL MU-MIMO • R3.2.1.E: Since the HT SIG field cannot be expanded without breaking backward compatibility, the VHT MF preamble shall include a VHT SIG field. The VHT SIG field may include singaling for the following: • a) wider bandwidth • b) enhanced MCS (see Section 3.3) • c) more spatial streams (see Section 3.4) • 3.2.2 VHT Sounding PPDU • R3.2.2.A: The sounding PPDU shall be enhanced from the HT sounding PPDU to support at least 8 transmit antennas. • R3.2.2.B: The draft specification shall mandate a single preamble format for sounding PPDUs. • 3.3 Enhanced MCS • R3.3.A: The draft specification shall include 256 QAM. Device support for 256 QAM is TBD [mandatory or optional]. • R3.3.B: The draft specification shall maintain the 11n modulation, interleaving and coding architecture. Minho Cheong, Newracom, Inc.

  6. What We’ve Done Before on SFD • Initial version of 802.11ac SFD (September, 2009) • R3.3.C: The draft specification shall minimize the number of additional MCS options. • R3.3.D: The draft specification shall include support for a different MCS for each STA in a DL MU-MIMO transmission. • R3.3.E: The draft specification shall include an expanded MCS set for the additional spatial streams supported. • 3.4 Spatial Multiplexing • R3.4.A: The draft specification shall include support for up to TBD spatial streams. • 3.5 CCA • R3.5.A: CCA shall support detection and deferral on the 20 MHz subchannels that are busy for any possible combination of channel use and signalling bandwidth with a single transmission in an otherwise idle RF bandwidth. This includes • a) a single 20 MHz transmission on any 20 MHz sub-channel • b) a single 40 MHz transmission on either 40 MHz sub-channel • c) a single 80 MHz transmission • 4 DL MU-MIMO • R4.A: DL MU-MIMO shall be built on one type of the 11n channel sounding PPDU and transmit beamforming protocol. • R4.B: DL MU-MIMO shall provide MAC protocol extensions to support multiple acknowledgement responses from the individual STAs receiving the MU-MIMO transmission. • R4.C: The DL MU-MIMO MAC protocol extensions shall work with EDCA Minho Cheong, Newracom, Inc.

  7. What We’ve Done Before on SFD • Initial version of 802.11ah SFD (September, 2011) • 3 S1G Physical Layer • This section describes the functional blocks of the physical layer. • 3.1 Channelization • 3.2 S1G PLCP Sublayer • 3.3 Modulation and Coding Scheme (MCS) • 4 MAC Layer • This section describes the functional blocks of the MAC layer. • 4.1 Power Save • 4.2 Channel Access • 4.3 Large Number of STAs Support Minho Cheong, Newracom, Inc.

  8. What We’ve Discussed in 802.11ax • Top features relatively actively discussed • DL OFDMA • UL OFDMA • DL MU-MIMO (2.4GHz as well) • UL MU-MIMO • Dynamic CCA • And so on Minho Cheong, Newracom, Inc.

  9. Conclusions • 11-14-1429-00-00ax-proposed-802.11ax-specification-framework-document • just tries to list-up only very agreeable top-level features among what have been discussed during the HEW SG and TGax. • Propose the above skeleton document could be an initial starting point for moving forward Minho Cheong, Newracom, Inc.

  10. References [1] 11-14-1009-02-00ax-proposed-802-11ax-functional-requirements [2] 11-11-1137-02-00ah-specification-framework-for-tgah [3] 11-09-0992-03-00ac-proposed-specification-framework-for-tgac Minho Cheong, ETRI

More Related