Doc.: IEEE 802.11-07/2403r0



IEEE P802.11

Wireless LANs

|TGn LB97 Submission for PHY FEC Comment CID #2796: Annex G Tables |

|Date: 2007-09-12 |

|Author(s): |

|Name |Company |Address |Phone |email |

|George Vlantis |STMicroelectronics, Inc. |1060 East Brokaw Road, San Jose |+1.408.451.8109 (o) |George.Vlantis@ |

| | |CA, 95131 |+1.408.893.9357 (m) | |

| | | | | |

Introduction

Interpretation of a Motion to Adopt

A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGn Draft. This introduction is not part of the adopted material.

Editing instructions formatted like this are intended to be copied into the TGn Draft (i.e. they are instructions to the 802.11 editor on how to merge the TGn amendment with the baseline documents).

TGn Editor: Editing instructions preceded by “TGn Editor:” are instructions to the TGn editor to modify existing material in the TGn draft. As a result of adopting the changes, the TGn editor will execute the instructions rather than copy them to the TGn Draft.

Summission Note: Notes to the reader of this submission are not part of the motion to adopt. These notes are there to clarify or provide context.

Proposed Resolutions

Click on icon below “TGn Draft 2.06 review.xls” for the original text of Comment CID #2796 by Adrian Stephens..

[pic]

Click on icon below “11-07-2796-01-000n-lb97-phy-pmd-comments-resolutions.doc” for the previous motioned resolution of Comment CID #2796.

[pic]

CID 2796

Commenter’s Comment: “‘Note that the bit-ordering of the octets is most significant bit first.’

The meaning of this is unclear.” The Commenter is Adrian Stephens. The Assignee was Assaf Kasher.

Commenter’s Proposed Change: “Replace with: ‘The values shown in the Binary Value column are shown with the most significant bit on the left’. Make similar changes throughout G.”

Assaf’s Counter Resolution: From 11-07-2796r1 (click above):

|2796 |"Note that the bit-ordering of the octets is most|Replace with: "The values shown in the Binary Value column are shown with the |

| |significant bit first." |most significant bit on the left". |

| | | |

| |The meaning of this is unclear. |Make similar changes throughout G. |

Suggestion: Counter (Accept in principle)

TGn Editor: change the following text on line 6 page 403 D2.04:

The DATA bits are shown in Table G.13. Note that the bit-ordering of the octets is most significant bit first The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: change the following text on line 38 page 405 D2.04:

The scrambled DATA bits are shown in Table G.16, The values shown in the Binary Value columns are shown with the most significant bit on the left. with the bit-ordering being most significant bit first.

TGn Editor: change the following text on line 37 page 407 D2.04:

The DATA encoded bits are shown in Table G.18 The values shown in the Binary Value columns are shown with the most significant bit on the left., with the bit ordering being most significant bit first.

TGn Editor: change the following text on line 61 page 420 D2.04:

The scrambled sequence is given in Table G.34 The values shown in the Binary Value columns are shown with the most significant bit on the left., with the bit orderingbeing most significant bit first.

TGn Editor: change the following text on line 62 page 424 D2.04:

The results of applying shortening bits, as prescribed in paragraph (c) of 20.3.10.6.5 (LDPC PPDU encoding

process) is given in Table G.36 The values shown in the Binary Value columns are shown with the most significant bit on the left., with the bit-ordering being most significant bit first.

TGn Editor: change the following text on line 62 page 426 D2.04:

The results are given in Table G.37 The values shown in the Binary Value columns are shown with the most significant bit on the left, with the bit-ordering being most significant bit first

TGn Editor: change the following text on line 45 page 429 D2.04:

The results are given in Table G.38 The values shown in the Binary Value columns are shown with the most significant bit on the left., with the bit-ordering being most significant bit first.

TGn Editor: change the following text on line 35 page 433 D2.04:

The resulting 1136 bits are shown inTable G.40. The values shown in the Binary Value columns are shown with the most significant bit on the left. Bit-ordering is most significant bit first.

TGn Editor: change the following text on line 21 page 437 D2.04:

process) is given in Table G.42, with the bit-ordering being most significant bit first. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: change the following text on line 31 page 439 D2.04:

as prescribed by paragraph (c) of 20.3.10.6.5 (LDPC PPDU encoding process) . The results are given in Table

G.43, with the bit-ordering being most significant bit first. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: change the following text on line 6 page 442 D2.04:

The results are given in Table G.44, with the bit-ordering being most significant bit first. The values shown in the Binary Value columns are shown with the most significant bit on the left.

History: Assaf’s resolution was implemented in Drafts 2.06 and is currently implemented in Draft 2.07, unchanged from Draft 2.06.

During the Draft 2.06 review process, it was discovered by Adrian that the “bit ordering” of the tables, “seqnencing of bits” of the tables, “endianness” of the tables, etc. is addressed in Clause 7.1.1 “Conventions”. It is only necessary to specify deviations from the convention.

It was also pointed out that indicating that the “leftmost bit” of a binary value is the “most-significant” doesn’t quite convey the intended information either.

The conclusion was that the most important idea that needs to be conveyed in the Tables of Annex G of 802.11n is to convey the enumeration of the bits, similar to Annex G of 802.11 REVma. That is, what needs to specified is which bit in the Tables is bit zero, bit one, bit two, etc.

After further scrutiny of Draft 2.07, is was discovered that the three Tables that contain the ASCII messages inputs for the three examples have the “Binary Val” and “Hex Val” columns in reverse order from the other tables that represent that outputs of the various encoding processing steps that follow the REVma convention.

The three Tables that have this issue that are in ASCII order are:

“Table G.13—The DATA bits before scrambling” (for the BCC Example on pp. 427-428)

“Table G.34—The DATA bits for LDPC example 1 before scrambling” (pp. 444-445)

“Table G.40—The DATA bits for LDPC example 2 before scrambling” (pp. 455-457)

The Tables that have this issue and agree with 802.11 REVma ordering are:

“Table G.16—The DATA bits after scrambling” (for the BCC Example on pp. 429-430)

“Table G.18—The BCC encoded DATA bits” (pp. 431-432)

“Table G.35—The DATA bits for LDPC example 1 after scrambling (pp. 445-446)

“Table G.36—The DATA bits for LDPC example 1 after insertion of shortening bits” (pp. 447-448)

“Table G.37—The DATA bits for LDPC example 1 after LDPC encoding” (pp. 449-451)

“Table G.38—The DATA bits after puncturing and removal of shortening bits” (pp. 452-453)

“Table G.41—The DATA bits for LDPC example 2 after scrambling (pp. 457-458)

“Table G.42—The DATA bits for LDPC Example #2 after insertion of shortening bits” (pp. 459-461)

“Table G.43—The DATA bits for LDPC example 2 after LDPC encoding” (pp. 461-464)

“Table G.44—The DATA bits after removal of shortening bits and copying of repetition bits” (pp. 465-468)

The Tables that do not have this issue (i.e. no binary values):

BCC Example: Tables G.1, G.24, G.25, G.26, G.27, G.28, G.29, G.30, G.31, and G.32

LDPC #1 Example: Tables G.33 (page 443)

LDPC #2 Example: Table G.39 (pp. 454-455)

Proposed Resolution: Counter (Accept In Principle).

Discussion:

Therefore, the remedy that the Commenter, Adrian and myself feel makes the most sense is to: (1) explicitly put the bit ordering of each of the tables that have binary entries(listed above) by inserting the enumeration into each tables headers; (2) insert an explanatory statement in the introduction of Annex G that states that the bit positions of the binary values in each Annex G Table are specified in each Table’s header; and (3) revise the text preceding each of the Annex G Tables, deleting the clause referring to the bit positions of the binary values .

Hence, I move to authorize the editor to make the following changes to Draft 2.07:

(1) Inserting enumeration into each table’s header:

TGn Editor: In D2.07, replace the one- line header of Table G.13 (pp. 427-428), Table G.34 (pp.444-445), and Table G.40 (pp.455-457) with the following two-line header:

|Bit ## |Binary Val |Binary Val |Binary Val |Hex Val |Hex Val |Hex Val |

| |b7 b0 |b15 b8 |b23 b16 | | | |

|000-023 |00000000 |00000000 |00000100 |0x00 |0x00 |0x04 |

|024-047 |00000010 |00000000 |00101110 |0x02 |0x00 |0x2E |

TGn Editor: In D2.07, replace the one- line header of Table G.16 (pp. 429-430), Table G.18 (pp.431-432), Table G.35 (pp.445-446), Table G.36 (pp.447-448), Table G.37 (pp.449-451), Table G.38 (pp.452-453), Table G.41 (pp.457-458), Table G.42 (pp.459-461), Table G.43 (pp.461-464) and Table G.44 (pp.465-468) with the following two-line header:

|Bit ## |Binary Val |Binary Val |Binary Val |Hex Val |Hex Val |Hex Val |

| |b0 b7 |b8 b15 |b16 b23 | | | |

|000-023 |01101100 |00011001 |10001001 |0x6C |0x19 |0x89 |

|024-047 |10001111 |01101000 |00100001 |0x8F |0x68 |0x21 |

(2) Inserting a cautionary note at the beginning of Annex G:

TGn Editor: In D2.07, page 423, line 60, insert the following editorial instructions (in italics), and insert the renumbered subclause heading G.1.1 “Introduction” with the following accompanying text:

G.1.1 Introduction

Append the following new paragraph at the end of G.1.1:

In each Annex G Table which has “Binary Val” columns, the bit positions of the binary values are specified in the header of the Table.

(3) Deleting the text above the Annex G Tables that have “Binary Val” columms:

TGn Editor: In D2.07, subclause G.1.5.1, page 426, lines 4-8, preceding Table G.13, delete the last sentence of the paragraph:

The DATA bits are shown in Table G.13. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.1.5.2, page 428, lines 38-41, preceding Table G.16, delete the last sentence of the paragraph:

The scrambled DATA bits are shown in Table G.16. The values shown in the Binary Value columns are shown with the most significant bit on the left

TGn Editor: In D2.07, subclause G.1.6.1, page 430, lines 36-39, preceding Table G.18, delete the last sentence of the paragraph:

The DATA encoded bits are shown in Table G.18. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.2.2, page 442, lines 63-65, preceding Table G.34, delete the last sentence of the paragraph:

The resulting 816 bits are shown in Table G.34. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.2.3, page 443, lines 46-49, preceding Table G.35, delete the last sentence of the paragraph:

The scrambled sequence is given in Table G.35. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.2.4, page 446, lines 61-64, preceding Table G.36, delete the last sentence of the paragraph:

The results of applying shortening bits, as prescribed in paragraph (c) of 20.3.10.6.5 (LDPC PPDU encoding process) is given in Table G.36 The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.2.5, page 448, lines 60-65, preceding Table G.37, delete the last sentence of the paragraph:

The results are given in Table G.37. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.2.6, page 451, lines 60-65, preceding Table G.38, delete the last sentence of the two-sentence paragraph, preserving the NOTE following it:

The results are given in Table G.38. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.3.2, page 455, lines 32-30, preceding Table G.40, delete the last sentence of the paragraph:

The resulting 1136 bits are shown in Table G.40. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.3.3, page 457, lines 19-23, preceding Table G.41, delete the last sentence of the paragraph:

The scrambled sequence is given in Table G.41. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.3.4, page 459, lines 19-22, preceding Table G.42, delete the last sentence of the two-sentence paragraph, preserving the NOTE following it:

The results of applying shortening bits, as prescribed in paragraph (c) of 20.3.10.6.5 (LDPC PPDU encoding process) is given in Table G.42 The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.3.5, page 461, lines 28-32, preceding Table G.43, , delete the last sentence of the two-sentence paragraph, preserving the NOTE following it:

The results are given in Table G.43. The values shown in the Binary Value columns are shown with the most significant bit on the left.

TGn Editor: In D2.07, subclause G.3.6, page 465, lines 6-8, preceding Table G.44, delete the last sentence of the two-sentence paragraph, preserving the two NOTEs following it:

The results are given in Table G.44. The values shown in the Binary Value columns are shown with the most significant bit on the left.

-----------------------

Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.

Abstract

This document contains proposed changes to the IEEE P802.11n Draft to address the following LB97 comment: #2796

The changes marked in this document are based on TGn Draft version P802 11n D2.07.pdf.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download