June, 2010

Larry Taylor, DTC (UK)Slide 1

doc.: IEEE 802.15-10-0538-04-004g

Submission

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Submission Title: [Comment Resolutions – Taylor et al]Date Submitted: [ 11 July, 2010]Source: [J.L.Taylor], Company [DTC (UK)], Address [UK], E-Mail:[larry.taylor@discretetime.com]

Re: [LB51 Comment Resolution]

Abstract: [This contribution contains various comment resolution proposals]

Purpose: [Response to assigned LB51 comments]

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 contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

June, 2010

Larry Taylor, DTC (UK)Slide 2

doc.: IEEE 802.15-10-0538-04-004g

Submission

Contents

• Part 1 - 868-870MHz Band Channel Numbers• Part 2 - MR-O-QPSK Channel Numbers• Part 3 - OFDM & MR-O-QPSK Page 7 definition• Part 4 - MLME Scan for SUN PHYs• Part 5 - MR-O-QPSK Channel Pages• Part 6 - PIB Attributes

June, 2010

Larry Taylor, DTC (UK)Slide 3

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 1868-870MHz Band Channel Numbers

Related comments

Taylor

637, 638

June, 2010

Larry Taylor, DTC (UK)Slide 4

doc.: IEEE 802.15-10-0538-04-004g

Submission

Proposed Resolution

• Define 200kHz spacing for the 863-870 band– Make the Table 1a † note also apply to Channel Spacing entries for

optional data rate columns for 863-870MHz band • Delete last paragraph in 6.1.2.5a.3

– Channel numbers will be defined according to equation (1)

• Insert in a suitable place in 6.1.2.5a.3 (taking into account other comment resolutions on GuardBand):– GuardBand =

• 25kHz for European 863-870 band

• Note also that product vendors will declare support for channel numbers compliant with local regulatory requirements via the phySUNChannelsSupported PIB attribute

June, 2010

Larry Taylor, DTC (UK)Slide 5

doc.: IEEE 802.15-10-0538-04-004g

Submission

Daniel Popa (Itron), Larry Taylor (DTC(UK))Slide 5

Resolutions

# Comment Proposed Resolution637 "Exceptions may apply to the upper part of

the European 868 MHz band, where channel carrier assignment

may be individually tailored to suit regulatory requirements." What will be the channel carrier assignment?

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 1

638 The statement that exceptions to channel numbering for the upper part of the European 868MHz band is unqualified and therefore with little meaning. How are the channel numbers tailored?

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 1

June, 2010

Larry Taylor, DTC (UK)Slide 6

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 2MR-O-QPSK Channel Numbers

Related comments

Taylor / Schmidt / Park

470, 643, 644, 649, 661

June, 2010

Larry Taylor, DTC (UK)Slide 7

doc.: IEEE 802.15-10-0538-04-004g

Submission

Section 6.1.2.5a.4

• Remove each occurrence of “For channel page x, ” , where x = 0,1,2,3

June, 2010

Larry Taylor, DTC (UK)Slide 8

doc.: IEEE 802.15-10-0538-04-004g

Submission

Slide 8

Resolutions

# Comment Proposed Resolution470 This chapter is quite confusing. There is no

placeholder for the channel number. For both, the MR-O-QPSK PHY and the OFDM PHY, the "PHY Mode" field is not useful, since all information on the PHY mode is transmitted within PPDU.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 2

643 Overloads channel page 0,4 which are already used in the base standard, so this is not allowed in an amendment.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 2

644 This is inconsistent with 6.1.2.5a.1 which says this PHY is specified as channel page 7.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 2

649 Overloads channel page 1 and 3 which are used in the base standard, which is not allowed.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 2

661 Channel page 2 and 3 are already used. Accept in principle - resolution as in Document 15-10-0538-04-004g Part 2

June, 2010

Larry Taylor, DTC (UK)Slide 9

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 3OFDM & O-QPSK Page 7 PHY Mode

Representation

Related comments

Taylor / Seibert

494

June, 2010

Larry Taylor, DTC (UK)Slide 10

doc.: IEEE 802.15-10-0538-04-004g

Submission

Modify Figure 22a as follows

Bits 31..27 Bits:26..22 Bits:21..20 Bits:19..16 Bits: 15..0

… … … … …

Page 7 Frequency Band

Modulation Scheme = MR-FSK

Reserved Bit map, where each bit corresponds to a particular PHY mode

Modulation Scheme = OFDM

Bits: 19..13

Reserved

Bit: 12..9

(Integer)

OFDM Option

(Range 1..5)

Bit: 8..0

(Bit Map)

MCS Values Supported

(for Option)

Modulation Scheme = MR-O-QPSK

Bits: 19..5 Reserved

Bit: 4

Spreading Mode

Bit: 3..0

(Bit Map)

Rate Modes Supported

June, 2010

Larry Taylor, DTC (UK)Slide 11

doc.: IEEE 802.15-10-0538-04-004g

Submission

Daniel Popa (Itron), Larry Taylor (DTC(UK))Slide 11

Resolutions

# Comment Proposed Resolution494 The number of bits to specify the mode

implemented by an OFDM device is greater than what is available with this proposed channel numbering technique. There are 32 valid combinations of modulation and coding schemes in OFDM.

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 3

June, 2010

Larry Taylor, DTC (UK)Slide 12

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 4MLME Scan for SUN PHYs

Related comments

Taylor / Ecclesine

474

June, 2010

Larry Taylor, DTC (UK)Slide 13

doc.: IEEE 802.15-10-0538-04-004g

Submission

Section 7.1.11.1.1, Table 67, row 2 ScanChannels

• Change the Valid Range column to:– 27-bit field. If phyCurrentPage = 7 or 8,

(phyMaxSUNChannelSupported+1)-bit field

• Change the Description column to:– The bits (b0, b1.. bn-1 where n=27 or

(phyMaxSUNChannelSupported-1) ) indicate which channels are to be scanned (1=scan, 0=do not scan) for each of the channels supported by phyCurrentPage

June, 2010

Larry Taylor, DTC (UK)Slide 14

doc.: IEEE 802.15-10-0538-04-004g

Submission

Daniel Popa (Itron), Larry Taylor (DTC(UK))Slide 14

Resolutions

# Comment Proposed Resolution474 The new bitmap defined in page 7 and page

8 is not compatible with the legacy bitmaps and is causing some issues for the MLME-SCAN.request primitive (clause 7.1.11.1.1 in 802.15.4-2006)

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 4

June, 2010

Larry Taylor, DTC (UK)Slide 15

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 5MR-O-QPSK Channel Pages

Related comments

Schmidl / Taylor / Schmidt / Park

501, 521, 584, 585, 586

June, 2010

Larry Taylor, DTC (UK)Slide 16

doc.: IEEE 802.15-10-0538-04-004g

Submission

General Comment on Figures 22x

• All the information contained in the PHY Mode figures is already contained elsewhere in the specification

• There is a comment suggesting to move the figures to an informative annex

• Alternative is to delete them as they are redundant• This would also obviate the need to add new figures for MR-O-

QPSK and OFDM PHY Modes• In order to make the MR-FSK PHY Mode mapping to the

standard PHY Mode bit map unambiguous:– add PHY Mode 0, PHY Mode 1 and PHY Mode 2 to the Column

headings for the 3 Mandatory and Optional columns in Table 1a– Add a PHY Mode column to Table 1 and include the PHY Mode

number for the different entries for each frequency band (as is done in Table 75p for RateMode in MR-O-QPSK)

June, 2010

Larry Taylor, DTC (UK)Slide 17

doc.: IEEE 802.15-10-0538-04-004g

Submission

June, 2010

Larry Taylor, DTC (UK)Slide 17

Note to Editors - add Figures 22m…

• Create figures in the PHY modes list for MR-O-QPSK– In each figure set the Page number to 7– In each figure set bits 20-21 to (1,0) and define it as O-QPSK

• Frequency band values are:– 779-787MHz is band 15– 868-870MHz is band 2– 902-928MHz is band 3– 2400-2483.5MHz is band 4

• For each frequency band in Table 75p and Table 75q define the figure with:

– Bits 26-22 corresponding to the Frequency Band index in Table 3a– Bits 19-5 Reserved– Bit 4 set to the Spreading Mode– Bits 3-0 set to 1 except for 868-870MHz band– Define rows for the 4 (3 for band 2) PHY Modes defined in each band as

per table 75p and table 75q

June, 2010

Larry Taylor, DTC (UK)Slide 18

doc.: IEEE 802.15-10-0538-04-004g

Submission

Note to Editors - add OFDM Figures 22x..

• For each frequency band in Table 1 with OFDM in the Modulation column– In each figure set the Page number to 7– In each figure set bits 20-21 to (0,1) and define it as OFDM

• Frequency band values are:– 470 is band 7– 780 is band 15– 868-870 is band 2– 915 is band 3– 922 is band 16– 950 is band 0– 2400-2483.5 is band 4

• For each frequency band define the figure using Option and MCS values from Table 75f:

– Bits 26-22 corresponding to the Frequency Band index in Table 3a– Bits 19-13 Reserved– Bits 12-9 set to the Option value– Bits 8-0 set to the MCS values supported

June, 2010

Larry Taylor, DTC (UK)Slide 19

doc.: IEEE 802.15-10-0538-04-004g

Submission

Slide 19

Resolutions

# Comment Proposed Resolution501 Figures 22b,c,…seem to repeat information

already given in 6.1.1 and at the very beginning of this subclause. Are they necessary? If so, should they be moved into an annex?

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 5

521 The columns "Page, Freq Band, Modulation Scheme" are redundant, they are specified elsewhere. Repeating them here will just lead to mistakes. All the reader needs to know is the standard defined PHY mode mapping.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 5

584 Fig 22b through 22l do not include any OFDM bands.

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 5

585 This clause does not completely describe all the PHY mode combinations called out 6.12a/b/c. This needs to be a complete and consistent specification for al SUN PHYs

Accept in principle - resolution as in Document 15-10-0538-04-004g Part 5

June, 2010

Larry Taylor, DTC (UK)Slide 20

doc.: IEEE 802.15-10-0538-04-004g

Submission

Daniel Popa (Itron), Larry Taylor (DTC(UK))Slide 20

Resolutions

# Comment Proposed Resolution586 Complete the specification to describe how

each field in the channel page structure should be set. Consider moving the examples to informative annexes. Consider including examples of channel paging structures with OFDM usage.

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 5

June, 2010

Larry Taylor, DTC (UK)Slide 21

doc.: IEEE 802.15-10-0538-04-004g

Submission

Part 6PIB Attributes

Related comments

Taylor

1107, 1175

June, 2010

Larry Taylor, DTC (UK)Slide 22

doc.: IEEE 802.15-10-0538-04-004g

Submission

Global Corrections

• At the Editors’ discretion– In all tables defining PIB Attributes, rename

“Range” to “Valid Range”– Change all Valid Range definitions of the

type “x/8 octets or x bits” to “x bits”• x/8 is not the number of octets required to

contain x bits – it is Ceiling(x/8). We do not need to tell the reader there are 8 bits in an octet….

June, 2010

Larry Taylor, DTC (UK)Slide 23

doc.: IEEE 802.15-10-0538-04-004g

Submission

6.4.2, Table 31

• Rename “Range” to “Valid Range”• Row 1 phyMaxSUNChannelSupported

– Change the Valid Range column to a range in agreement with changes to channel number range

– Change Description column to:• phyMaxSUNChannelSupported defines the highest

channel number supported and therefore defines the number of bits in phySUNChannelsSupported

June, 2010

Larry Taylor, DTC (UK)Slide 24

doc.: IEEE 802.15-10-0538-04-004g

Submission

Section 6.4.2, Table 31a

• Rename “Range” to “Valid Range”• Row 3 NumChannels

– Change the Valid Range column to a range in agreement with changes to channel number range

• Row 4 Channel Spacing– Change the Valid Range column to:

• 1,, 1,200– Change the Description column to:

• The distance between adjacent channel center frequencies in kHz

• Row 5 Data Rate– Change Type column to:

• Float– Change Valid Range column to:

• 1-1,000– Change the Description column to:

• The data rate in kbps.

• Row 6 Modulation Scheme– Delete row – duplicate information to table 3b

June, 2010

Larry Taylor, DTC (UK)Slide 25

doc.: IEEE 802.15-10-0538-04-004g

Submission

Daniel Popa (Itron), Larry Taylor (DTC(UK))Slide 25

Resolutions

# Comment Proposed Resolution1107 Further evidence that the channel numbering

proposal for MRFSK PHYs requires clarification and verification. The description of phyMaxSUNChannelsSupported is incorrect. It states that 'The page 7 or page 8 entry specified by phyCurrentSUNPageEntry describes the total number of defined channel for the PHY mode….' This is not correct

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 6

1175 The parameter values in 6.42 require further clarification. For example, the parameters in table in 31a are not consistent with the tolerances specified in 6.12.a4

Accept in Principle. Resolution as in Document 15-10-0538-04-0004g Part 6