1 / 9

Preamble Discussions

Preamble Discussions. Authors:. Date: 2012-07-16. Authors continued:. Slide 2. Authors continued:. For >=2MHz, two preamble formats are defined: Short and Long preambles [1].

lou
Download Presentation

Preamble Discussions

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. Preamble Discussions Authors: Date: 2012-07-16 Hongyuan Zhang, et. Al.

  2. Authors continued: Hongyuan Zhang, et al Slide 2

  3. Authors continued: Hongyuan Zhang, et. Al.

  4. For >=2MHz, two preamble formats are defined: Short and Long preambles [1]. • Short preamble is the simplest to implement, may allow simple sensor devices (that only support 1MHz and 2MHz) to only do short preamble, other devices (AP, or STAs targeted for data applications) shall support both preambles. • To guarantee interoperability, any device has to be able to at least decode SIGA field of long preamble to set up CCA. Short and Long preamble Mandatory/Optional Rules Hongyuan Zhang, et. Al.

  5. Insert the following text in the spec framework: “ • Both short and long preambles are mandatory at the AP. • For a STA, • If it supports only 1MHz/2MHz, short preamble is mandatory, and long preamble is optional (exchanged by capability fields). • Otherwise, both short and long preambles are mandatory. • Any device shall be able to detect and decode SIGA field in the long preamble for CCA. ” Proposed Text Change (1) Hongyuan Zhang, et. Al.

  6. Current spec framework starts short preamble section as below. • “R.3.2.1.1.A: The general structure for SU open-loop packet is similar to 11n green field preamble, as below (short preamble):” • The description “SU open-loop” seems vague, and is not normative. • Similar to 11n green field packet and legacy 11a/g packets when transmitted with multiple antennas, there was no restriction on what spatial mapping matrix should be used (TxBF or not), as in 11n/11ac spec. • Transmitter/AP may decide on its own whether to transmit BF/Non-BF packets using short preamble or long preamble, basedon performances or other criterion, depending on implementations. Short Preamble Description Hongyuan Zhang, et. Al.

  7. Make the following text change: “ • R.3.2.1.1.A:  The general structure for SU open-loop packet is similar to 11n green field preamble, as below (short preamble): The general short preamble structure for greater than or equal to 2 MHz PHY packet is defined as in the figure below: ” Proposed Text Change (2) Hongyuan Zhang, et. Al.

  8. Do you agree with the text change as described in slide 5 and slide 7? Straw Poll / Pre-Motion Hongyuan Zhang, et. Al.

  9. [1] 11-12-0595-00-00ah-Rename-2MHz-Preamble References Hongyuan Zhang, et. Al.

More Related