1. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 1 July, 2008 Chang woo Pyo, NICT Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment Resolutions related to MAC (UEP, UEP/EEP, Retransmission)] Date Submitted: [July 29, 2008] Source: [Chang woo Pyo, Zhou Lan, Fumihide Kojima, Hiroyuki Nakase, Hirosh Harada, Shuzo Kato] Company [National Institute of Information and Communications Technology (NICT)] Address 1 [3-4 Hikari-no-oka, Yokosuka-shi, Kanagawa 239-0847, Japan] Voice 1 :[+81-46-847-5074], FAX 1 : [+81-46-847-5440] E-Mail[] Re: [Comment Resolutions related to MAC (UEP, UEP/EEP, Retransmission)] Abstract: [Comment Resolutions related to MAC (UEP, UEP/EEP, Retransmission)] Purpose: [To be considered in TG3C baseline document.] Notice:This document has been prepared to assist the IEEE P802.15. 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. Release:The contributors acknowledge and accept that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 2 July, 2008 Chang woo Pyo, NICT Comment Resolutions related to MAC (UEP, UEP/EEP and Retransmission) Chang woo Pyo NICT

3. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 3 July, 2008 Chang woo Pyo, NICT High Level Summary This document provides the resolutions for the comments on UEP, UEP/EEP and Retransmission –17 received UEP comments are categorized as following 7 comments related to UEP definitions 4 comments related to UEP MCSs of SC PHY 2 comments related to editorial modification 2 comments related to UEP/FCSL 1 comment related to UEP Annex D1 1 comment related to UEP capability –2 received UEP/EEP comments 2 comments related to UEP and EEP mode indications –1 received Retransmission comment Clarification of retransmission bit in MAC sub-header of SC PHY The text (to appear in the draft document) based on the resolution can be found in “15-08-0555-01-003c-text-for-comment resolution- MAC“

4. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 4 July, 2008 Chang woo Pyo, NICT Categorization of Received Comments 17 UEP comments –7 comments related to UEP definitions 37, 59, 70, 71, 89, 386, 538 –4 comments related to UEP MCSs of SC PHY 25, 539, 540, 651 –2 comments related to editorial modification 68, 69 –2 comments related to UEP/FCSL 119, 122 –1 comment related to UEP Annex D1 118 –1 comment related to UEP capability 533 2 UEP/EEP comments –2 comments related to UEP and EEP mode indications 383, 563 1 Retransmission comment –Clarification of retransmission bit in MAC sub-header of SC PHY 532

5. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 5 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP Definitions (1/2) Comments : Clarify 3 UEP Types Resolution –Add the following sentence (Blue) in Section 5.3.16 For flexible error protection that accounts for data that has more emphasis on the msbs than the lsbs, e.g., video, UEP is provided as an option. This UEP has three different types as described in 8.17 and may be applied for three different PHY modes described in 5.5.1.

6. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 6 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP Definitions (2/2) –Line 10-15 in Section 8.17 - replaced by the following sentences “UEP Type 1 protects an aggregated frame which consists of msb subframes, lsb subframes or both msb and lsb subframes by using the different FECs. UEP Type 2 protects an aggregated frame which consists of msb subframes, lsb subframes or both msb and lsb subframes by using different MCSs. UEP Specific IE, defined in clause 7.4.24, is only used in UEP Type 2 in order for the originating DEV to inform the recipient DEV of the separating position of msbs and lsbs. If necessary, UEP Type 2 can transmit announce command frame with UEP Specific IE to dynamically change the separating position. UEP Type 3 protects msb and lsb in a subframe unequally by either applying different FEC coding rates to msbs and lsbs or mapping msbs and lsbs to a skewed constellation. Capability of supporting UEP by FEC coding and/or by the skewed constellation is defined in 7.4.7. All UEP types, UEP Type 1, UEP Type 2 and UEP Type 3, can be used in SC PHY as described in 12.2.2.4. UEP Type 3 is only used in HSI OFDM and AV OFDM as described in 12.3.2.5 and 12.4, respectively.”

7. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 7 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP MCSs of SC PHY Comments : Clarify UEP MCSs in SC PHY Resolution: Table 109 in Section 12.2.2.4 is replaced as following that includes UEP MCS for SC PHY and the supported UEP Types in each UEP MCS Table 109. UEP MCS for SC PHY mode ValueModulation FEC PHY-SAP data rate Supported UEP Type msblsb 0 BPSK RS (255,239)1518.4Mb/sUEP Type 1 and UEP Type 2 1LDPC(672,336)810Mb/sUEP Type 1 and UEP Type 2 2LDPC(672,504)1215Mb/sUEP Type 1 and UEP Type 2 3 QPSK LDPC(672,336)1620Mb/sUEP Type 1 and UEP Type 2 4LDPC(672,504)2430Mb/sUEP Type 1 and UEP Type 2 5LDPC(672,588)2835Mb/sUEP Type 1 and UEP Type 2 6 8QAM RS (255,239)4555.1Mb/sUEP Type 1 and UEP Type 2 7 16QAM RS (255,239)6073.4Mb/sUEP Type 1 and UEP Type 2 8 QPSK LDPC(672,336)LDPC(672,504)2040Mb/sUEP Type 3 9LDPC(672,504)LDPC(672,588)2652Mb/sUEP Type 3

8. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 8 July, 2008 Chang woo Pyo, NICT Comment resolution related to editorial modification (1/2) Modified description in Section 12.2.2.4 –Replace the sentence in Line 28 “The MCS types, which are used for unequal error protection, are shown in Table 109” to “The UEP MCSs for SC PHY mode are shown in Table 109.” –Add the words in Line 40, “In UEP Type 3, when the transmitter chooses one of the UEP MCSs …. to apply adopt different…” Revise Figure 196 –Change LDPC (576,228) to LDPC (672,336) –Change LDPC (576,432) to LDPC (672,504) –Change LDPC (576,504) to LDPC (672,588) –Remove "3:2 alternating" and "7:6 alternating" in the caption of the figure

9. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 9 July, 2008 Chang woo Pyo, NICT Comment resolution related to editorial modification (2/2) Comment: Clarification needed on the bit multiplexing. What do the Ai and Bi indicate? How do these bits relate to what is being shown in Figure 195? Resolution: Insert the following text in Section 12.2.2.4. “When LDPC (672, 336) is used for msb group and LDPC (672, 504) is used for lsb group, the encoded bits shall be multiplexed every 10 bits with 6 bits as the encoded msbs and 4 bits as the encoded lsbs. A1, A2, A3, A4, A5, A6 are used in an increasing order in time to label the 6 encoded msbs from encoder LDPC (672, 336), while B1, B2, B3, B4 are used in an increasing order in time to label the 4 encoded lsbs from encoder LDPC (672, 504). The bit multiplexing/interleaving shall be performed such that the output pattern is A1, B1, A2, B2, A3, A4, B3, A5, B4, A6 with A1 being the earliest bit at the input of the symbol mapper while A6 being the latest, as illustrated in the upper part of Figure 196. When LDPC (672, 504) is used for msb group and LDPC (672, 588) is used for lsb group, the encoded bits shall be multiplexed every 13 bits with 7 bits as the encoded MSBs and 6 bits as the encoded lsbs. A1, A2, A3, A4, A5, A6, A7 are used in an increasing order in time to label the 7 encoded msbs from encoder LDPC (672, 504), while B1, B2, B3, B4, B5, B6 are used in an increasing order in time to label the 6 encoded lsbs from encoder LDPC (672, 588). The bit multiplexing/interleaving shall be performed such that the output pattern is A1, B1, A2, B2, A3, B3, A4, B4, A5, B5, A6, B6, A7 with A1 being the earliest bit at the input of the symbol mapper while A7 being the latest, as illustrated in the lower part of Figure 196.”

10. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 10 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP/FCSL Comment: –Move some of the video related functionality to a video FCSL (PAL) Resolution: –Reject. 15.3c already considered separating video related processing between FCSL and MAC/PHY. The UEP related information in current 15.3c draft is to tell the necessary MAC/PHY functions to support UEP.

11. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 11 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP Annex D1 Comment : Provide the map to the UEP types in Annex D1 Resolution : Remove Annex D1 and define Table 109 for UEP MCS in Section 12.2.2.4.

12. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 12 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP capability Comment: Cannot support multiple UEP Resolution: Table 49b in Section 7.4.7 is modified to indicate a multiple UEP type capabilities as following Table 49b – UEP type field values for SC UEP support ValueSC UEP Type 0No UEP supported 1Type 1 using MCS of QPSK with different RS and LDPC codes UEP Type1 using different FECs 2Type 1 using MCS of 16-QAM with different RS and LDPC codes UEP Type1 and Type 2, up to QPSK using different MCSs 3Type 2 using MCS of QPSK with different RS and LDPC codes UEP Type1 and Type 2, up to 16-QAM using different MCSs 4Type 2 using MCS of 16-QAM with different RS and LDPC codes UEP Type 3 using different MCSs only 5Type 3 using different MCSs UEP Type 3 using skewed constellation only 6UEP Type 3 using skewed constellation UEP Type 3 using different MCSs and skewed constellation 7 All UEP Types

13. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 13 July, 2008 Chang woo Pyo, NICT Comment resolution related to UEP/EEP Comments : UEP and EEP mode indications Resolution –To indicate UEP and EEP, UEP field (1bit) is newly defined in SC PHY header in Section 12.2.4.1 –The UEP bit shall be set to one if UEP is used, it shall be set to zero otherwise. bits: 37-3935-36343331-3211-306-10540-3 ReservedPW length ID Low latency mode BF IDPreamble type Frame length MCSUEPAGGScramble seed ID Figure 201—SC PHY header format

14. doc.: IEEE 802.15-08-0556-01-003c Submission Slide 14 July, 2008 Chang woo Pyo, NICT Comment resolution related to retransmission Comment: Clarification of retransmission bit in MAC subheader shown in Figure 10a Resolution: –Retransmission bit in MAC subheader is removed because the receiver sends Blk- ACK bitmap for subframes to the transmitter regardless of the requirement of subframe retransmission. –Reserved bit is changed from 5bits to 6bits Reserved (6bits)