1 / 14

Proposed Comment Resolution for TGaf PHY General Description

Proposed Comment Resolution for TGaf PHY General Description. Authors:. Date: 2012-09-16. Propose resolution to resolve following comments:

kalea
Download Presentation

Proposed Comment Resolution for TGaf PHY General Description

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 Comment Resolution for TGaf PHY General Description Authors: Date: 2012-09-16 Wookbong Lee, LG Electronics

  2. Propose resolution to resolve following comments: • 23, 34, 35, 36, 37, 38, 39, 85, 86, 193, 194, 201, 217, 262, 289, 346, 367, 383, 412, 482, 483, 484, 485, 486, 608, 689, 772, 807, 879, 880, 988, 989, 990, and 991. Outline Wookbong Lee, LG Electronics

  3. Clarification on broadcast frequency bands • CIDs: 23, 201 • TVHT STA is a VHT STA related one • CIDs: 34, 39, 86, 194, 289, 486, 608, 807, 879, 988 • Bandwidth related one • CIDs: 35, 36, 38, 85, 193, 217, 262, 367, 772, 989, 990, 991 • Better wording • CIDs: 482, 483, 484, 485, 689, 880 • Change values • CIDs: 37, 346, 383, 412 Related Comments Wookbong Lee, LG Electronics

  4. Currently IEEE 802.11af draft 2.0 has been written based on following concept • TVHT_MODE_1 TVHT PPDU is same as 40 MHz VHT PPDU • TVHT_MODE_2C or TVHT_MODE_2N TVHT PPDU is composed of two TVHT_MODE_1 TVHT PPDUs (one interleaver combines two parts) • TVHT_MODE_4C or TVHT_MODE_4N TVHT PPDU is composed of four TVHT_MODE_1 TVHT PPDUs (one interleaver combines four parts) • As pointed out in multiple comments, we have some problem with this concept with respect to MAC since we couldn’t correct all the relevant MAC sections • The problem is caused by “absolute” bandwidth (e.g. 20 MHz, 40 MHz, etc in MAC section) and “TVHT STA is a VHT STA” • Also we don’t want to change 802.11-2012 and 11ac technically Introduction Wookbong Lee, LG Electronics

  5. Define following bandwidth parameters • Channel width 1(CW1): A station (STA) dependant single channel bandwidth. In case of TV high throughput (TVHT) STA, this represents 6, 7 or 8 MHz depending on regulatory domain. Other than this STA, this represents 20 MHz. • Channel width 2(CW2): A station (STA) dependant double channel bandwidth. This is twice as large as channel width 1(CW1). • Channel width 4(CW4): A station (STA) dependant quadruple channel bandwidth. This is four times larger than channel width 1(CW1). • Channel width 8 (CW8): A station (STA) dependant eight-fold channel bandwidth. This is eight times larger than channel bandwidth 1(CW1). • Channel width 4+4 (CW4+4): A station (STA) dependant two quadruple channel bandwidth. This represents a bandwidth of two non-contiguous channel. The bandwidth of each frequency segment is channel bandwidth 4(CW4). • Channel width 1+1 (CW1+1): A station (STA) dependant two double channel bandwidth. This represents a bandwidth of two non-contiguous channel. The bandwidth of each frequency segment is channel bandwidth 1(CW1). • Channel width 2+2 (CW2+2): A station (STA) dependant two double channel bandwidth. This represents a bandwidth of two non-contiguous channel. The bandwidth of each frequency segment is channel bandwidth 2(CWw). Possible Solutions for Absolute Bandwidth (1/3) Wookbong Lee, LG Electronics

  6. Add exact bandwidth for CW1, CW2, etc, in (at least) each PHY clause, for example, • In 22.1.1 of 11ac draft, we can modify • The VHT PHY provides support for CW1, CW2, CW4 and CW8 contiguous channel widths and support for CW4+4 20 MHz, 40 MHz, 80 MHz and 160 MHz contiguous channel widths and support for 80+80 MHz non-contiguous channel width. • In this clause, CW1 represents 20 MHz. • In 23.1.1 of 11af draft, we can have • The TVHT PHY provides support for CW1, CW2, and CW4 contiguous channel widths and support for CW1+1 and CW2+2 non-contiguous channel width. • In this clause, CW1 represents 6, 7 or 8 MHz depending on the regulatory domain. • Replace 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz to CW1, CW2, CW4, CQ8 and CW4+4, respectively, from Clause 1 to 13, except for 8.4.1.27 CSI Report field, 8.4.1.28 Noncompressed Beamforming Report field, 8.4.1.29 Compressed Beamforming Report field, 8.4.1.48 VHT Compressed Beamforming Report field, for example, • In 7.3.5.11.2 of 11ac draft, • secondaryCW2 secondary40: Indicates that the secondary CW240 MHz channel is busy according to the rules specified in 22.3.19.5.4 (CCA sensitivity for signals not occupying the primary CW120 MHz channel). • In Table 8-13b of 11ac draft, • BW: … Set to 0 for CW1 20 MHz, Set 1 for CW2 40 MHz, Set 2 for CW4 80 MHz, and Set 3 for CW8 and CW4+4160 MHz and 80+80 MHz • Modifying bandwidth in PHY clauses and 8.4.1.27-29, 48 is FFS Possible Solutions for Absolute Bandwidth (2/3) Wookbong Lee, LG Electronics

  7. Feedback section needs to be PHY dependant • 8.4.1.27 CSI Report field, 8.4.1.28 Noncompressed Beamforming Report field, 8.4.1.29 Compressed Beamforming Report field, 8.4.1.48 VHT Compressed Beamforming Report field • Operation element may need to be PHY dependant due to different channelization • We need to handle secondary channel offset which is not used in TGaf. • Capability may need to be PHY dependant due to different set of mandatory support • DATARATE needs to be changed to “current value” divided by CW1/20 MHz Possible Solutions for Absolute Bandwidth (3/3) Wookbong Lee, LG Electronics

  8. Change text in 802.11-2012 and 802.11ac draft from Clause 1 to 13, except for 8.4.1.27 CSI Report field, 8.4.1.28 Noncompressed Beamforming Report field, 8.4.1.29 Compressed Beamforming Report field, 8.4.1.48 VHT Compressed Beamforming Report field • Replace CBW 20/40 to CW1/CW2 • Replace 20/40 MHz to CW1/CW2 • Replace 20/40/80/160 MHz to CW1/CW2/CW4/CW8 • Replace 20/40/80/160/80+80 MHz to CW1/CW2/CW4/CW8/CW4+4 • Replace 20/40/80 MHz to CW1/CW2/CW4 • Replace 20/40 to CW1/CW2 • Replace 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz to CW1, CW2, CW4, CQ8 and CW4+4, respectively • Replace 40-MHz to CW2 • Replace CBW20, CBW40, CBW80, CBW160 and CBW80+80 to CW1, CW2, CW4, CW8 and CW4+4 • Replace secondary40 and secondary80 to secondaryCW2 and secondaryCW4, respectively Proposed Remedy Wookbong Lee, LG Electronics

  9. Change text in 802.11af draft • Replace TVHT_W to CW1 • Replace TVHT_2W to CW2 • Replace TVHT_W+W to CW1+1 • Replace TVHT_4W to CW4 • Replace TVHT_2W+2W to CW2+2 Proposed Remedy (Continued) Wookbong Lee, LG Electronics

  10. Currently, we defined TVHT STA as follows: • TVHT STA is a VHT STA that excludes features supported as an HT STA, and supports VHT features identified in Clause 8, Clause 9, Clause 10, Clause 13 and Clause 23. • But this is very confusingas stated in many comments • Some of optional VHT features are not supported by TVHT STA • CW8 and CW4+4: TXVECTOR parameter BANDWIDTH shall not be set to CW8 or CW4+4 which is already included in current .11af draft • 5 to 8 spatial streams: TXVECTOR parameter NUM_STS shall not be set to 5-8 which is already included in current .11af draft • VHT STA supports some of HT features, but TVHT does not support HT features • Instead of saying TVHT does not support HT features, we can say a certain HT features (such as RIFS) are not permitted for STAs operating as TVHT STA • For example, TXVECTOR parameter FORMAT shall not be set to HT_MF or HT_GF which is already included in current .11af draft TVHT STA? (1/2) Wookbong Lee, LG Electronics

  11. Not all mandatory features are supported in TVHT STA • 20/40/80 MHz • VHT supports 20/40/80 as mandatory features: CW1/CW2/CW4 • TVHT supports CW1 as a mandatory feature, but CW2 and CW4 is optional • Can we make these as mandatory features? • VHT PPDU • TVHT supports TVHT PPDU • Can we change TVHT PPDU to VHT PPDU? • Currently TVHT PPDUs are different from VHT PPDU other than CW1 (40MHz VHT PPDU is same as TVHT_W TVHT PPDU except for down-clock related parameters) • Maybe we can say exact VHT PPDU format for corresponding bandwidth is different for different clause, and we just change TVHT PPDU to VHT PPDU • Actually, X MHz VHT PPDU is only present in 10.39.1 Basic VHT BSS functionality and Clause 22. And we already have 10.41.1 Basic TVHT BSS functionality TVHT STA? (2/2) Wookbong Lee, LG Electronics

  12. Change Clause 4.3.10b as follows: • The IEEE 802.11 TVHT STA operates in television white spaces (TVWS) bandsbroadcast frequency bands below 1 GHz. • A TVHT STA supports all mandatory features of a VHT STA as mandatory features except for CW2 and CW4 channel widths. A TVHT STA supports CW2 and CW4 channel widths as optional features. A TVHT STA supports all optional features of a VHT STA as optional features except for CW8 or CW4+4 channel widths and more than 5 spatial streams. CW8 or CW4+4 channel widths and more than 5 spatial streams are not permitted for STAs operating as TVHT STAs.is a VHT STA that excludes features supported as an HT STA, and supports VHT features identified in Clause 8, Clause 9, Clause 10, Clause 13 and Clause 23.References to The features and behaviors of VHT STAs featuresspecified in Clause 6, Clause 8, Clause 9, Clause 10,and Clause 13 and Clause 23 apply to those of TVHT STAs features as well, unless stated otherwise stated. The main PHY features in a TVHT STA that are not present in a VHT STA are the following: • Optional support for CW1+1 • Optional support for CW2+2 • Mandatory support for 6 MHz, 7 MHz and/or 8 MHz channel widths (single width channels) • Mandatory support for TVHT PPDUs • Optional support for two non-adjacent single width channels • Optional support for two non-adjacent double width channels Proposed Remedy Wookbong Lee, LG Electronics

  13. The main MAC features in a TVHT STA are the following: • Mandatory support for the A-MPDU padding of TVHT PPDU • Mandatory support for VHT single MPDU • Mandatory support for responding to BW indication in RTS • Optional support for MPDUs of up to 11 454 octets • Optional support for A-MPDU pre-EOF padding of up to 1 048 575 octets • These TVHT features are available to TVHT STAs associated with a TVHT AP in a BSS. A subset of the TVHT features is available for use between two TVHT STAs that are members of the same IBSS. • The support for TVHT transmit beamforming sounding and MU PPDUs in a TVHT AP and more than one TVHT STA within a TVHT BSS enables the optional use of downlink MU-MIMO. The use of 20 MHz, 40 MHz, 80 MHz or 160 MHz channel widths is not permitted for STAs operating as TVHT STAs. The use of HT features, such as RIFS, is not permitted for STAs operating as TVHT STAs. Proposed Remedy (Continued) Wookbong Lee, LG Electronics

  14. Change text in 802.11af draft • Replace “TVHT PPDU” with “VHT PPDU in TVWS bands” • Replace “FORMAT is TVHT” with “FORMAT is VHT” • Replace “FORMAT set to TVHT” with “FORMAT set to VHT” • Replace “FORMAT equals to TVHT” with “FORMAT equals to VHT” • Replace “TVHT format” with “VHT format” • In line 38-39 of page 230, change text as follows • The TXVECTOR parameter FORMAT shall be set to NON_HT or TVHT. • In Table 23-1, replace “TVHT” with “VHT” • In Table 23-31, change text as follows • Set to 4 for TVHT Proposed Remedy (Continued) Wookbong Lee, LG Electronics

More Related