1 / 9

TGah Spec Development Process

TGah Spec Development Process. Authors:. Date: 2012-05-14. Authors:. In the last TGah ad hoc meeting, the group started to discuss on how to develop a 11ah spec 802.11ah is inheriting both PHY and MAC from 802.11ac heavily, but 802.11ac spec is not completed yet

bono
Download Presentation

TGah Spec Development Process

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. TGah Spec Development Process Authors: Date: 2012-05-14 Minyoung Park et. al., Intel Corp.

  2. Authors: Minyoung Park et. al., Intel Corp.

  3. In the last TGah ad hoc meeting, the group started to discuss on how to develop a 11ah spec • 802.11ah is inheriting both PHY and MAC from 802.11ac heavily, but 802.11ac spec is not completed yet • The group needs to find the cleanest/easiest way to develop an 802.11ah spec that incorporates many parts of a draft 802.11ac spec • This presentation includes • TGah Spec development process in IEEE Introduction Minyoung Park et. al., Intel Corp.

  4. For 802.11ah PHY, create a separate new PHY clause • E.g. Clause 2x: Sub 1 GHz (S1G) PHY specification • Clause number should be chosen not to conflict with 11af • The new 11ah PHY clause contains delta between 11ah and 11ac PHYs • Incorporate necessary parts of 802.11ac PHY/MAC by reference • Just point to sections of the 802.11ac draft spec that the new 802.11ah spec needs to include • This way, 802.11ah STA doesn’t support Clause 22 (VHT PHY) directly • Reference should be based on the latest 802.11ac draft at the time of writing a 802.11ah draft spec • The editor/members of TGah should track changes in a newer draft spec of 802.11ac, which may affect/break the current draft spec of 802.11ah that refers to the older version of 802.11ac draft spec PHY Minyoung Park et. al., Intel Corp.

  5. TGac is not designed to be easily re-clockable • Difficult to reuse terminology from VHT PHY that is specific to the “non-clock reduced” channel widths • E.g.: secondary40, secondary80, 20 MHz, 40 MHz, 80 MHz … • Possible solutions: • Start the 11ah PHY clause with an explanation of the down-clocking and then simply refer to 11ac PHY with the understanding that every mentioning of the 20/40/80/160 in 11ac is used with the appropriate down-clocked BW • E.g. secondary40 is treated as secondary4 when used in 11ah • Have a table that shows all the mappings between the parameters in 11ac and 11ah • secondary40  secondary4, • secondary80  secondary8, • 20MHz/40MHz/80MHz/160MHz 2MHz/4MHz/8MHz/16MHz PHY (cont.) Minyoung Park et. al., Intel Corp.

  6. Make necessary additions/changes to the MAC clauses for 11ah PHY and new MAC features • E.g. Clause 8: Frame formats, Clause 9: MAC sublayer functional description , Clause 10: MLME MAC Minyoung Park et. al., Intel Corp.

  7. 802.11ah Specification Development Draft 11ah spec Existing MAC related clauses (e.g. Clause 8,9,10) 11ah Spec Framework Clause 8: Frame formats text text text MAC sections Clause 9: MAC sublayer functional description text text text Clause 10: MLME PHY sections text text text text text VHT PHY clause (Clause 22) Separate new 802.11ah PHY clause (e.g. Clause 23 or 24) text Reference to 802.11ac PHY/MAC text text text Create draft texts for PHY/MACclauses in PHY/MAC ad hoc groups Section 22.x.x Reference to VHT PHY Section 22.x.x Minyoung Park et. al., Intel Corp.

  8. TGaf is using 11ac PHY. TGah should use a similar style of using TGac PHY as well. TGaf and other task groups are making changes to MAC clauses. There needs to be a selector (switch) to separate between the changes of different task groups. One option is to use Band Id defined in 802.11ad. Referencing VHT PHY clauses will be bringing all the unnecessary old stuffs from 11a/n/ac... Comments from Editors Meeting Minyoung Park et. al., Intel Corp.

  9. Do you support the 802.11ah specification development process shown in Slide 4-6 in TGah? • Y/N/A: Straw Poll Minyoung Park et. al., Intel Corp.

More Related