1 / 7

Proposal to Rename >=2MHz Preambles for Improved Clarity in TGah Specification Framework

This presentation by Hongyuan Zhang et al. advocates for renaming the existing >=2MHz preambles in the TGah specification framework. Currently referred to as "SU Preamble" and "MU Preamble," the proposed names, "Short Preamble" and "Long Preamble," aim to enhance clarity by reflecting their structural characteristics rather than their functionalities. Additional suggestions include renaming certain subfields in the long preamble for consistency. The proposal invites discussions and a straw poll on these changes.

michi
Télécharger la présentation

Proposal to Rename >=2MHz Preambles for Improved Clarity in TGah Specification Framework

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. Rename >=2MHz Preambles Authors: Date: 2012-05-15 Hongyuan Zhang, et. Al.

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

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

  4. Abstract This presentation proposes to rename >=2MHz preambles in current TGah spec framework. Hongyuan Zhang, et. Al.

  5. May 2012 • In current Spec Framework, the two 2MHz preambles are named as “SU Preamble” and “MU Preamble”. • Issues with the names based on functionalities: • Current “MU preamble” is allowed to transmit both MU and SU packets (as in 11ac). • We propose to rename the two preambles using neutral names (e.g. based on preamble structures itself) instead of based on functionalities. • Propose to rename as “short preamble” and “long preamble”—similar to 11b. • Also need to rename some subfields in the long preamble Discussions Hongyuan Zhang, et. Al.

  6. May 2012 • Do you agree to rename the >=2MHz preambles as “Short Preamble” and “Long Preamble”, and rename the long preamble subfields as below? • Replace “MU Portion” by “Data Portion” • Replace “MU-STF” by “D-STF” • Replace “MU-LTF1~NLTF” by “D-LTF1~NLTF” Straw Poll - 1 “Omni” Portion Data Portion … STF LTF1 SIGA D-STF D-LTF1 D-LTF_NLTF SIGB DATA Field (2 symbols) (2 symbols as 11n GF) (2 symbols) (1 symbol) (1 symbol each) DGI LTS LTS Hongyuan Zhang, et. Al.

  7. May 2012 • Move to rename the >=2MHz preambles as “Short Preamble” and “Long Preamble”, and rename the long preamble subfields as below? • Replace “MU Portion” by “Data Portion” • Replace “MU-STF” by “D-STF” • Replace “MU-LTF1~NLTF” by “D-LTF1~NLTF” Motion - 1 “Omni” Portion Data Portion … STF LTF1 SIGA D-STF D-LTF1 D-LTF_NLTF SIGB DATA Field (2 symbols) (2 symbols as 11n GF) (2 symbols) (1 symbol) (1 symbol each) DGI LTS LTS Hongyuan Zhang, et. Al.

More Related