1 / 18

Comment Resolutions - Taylor et.al

This contribution contains various comment resolution proposals in response to assigned LB51 comments.

ktitcomb
Download Presentation

Comment Resolutions - Taylor et.al

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. 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. Larry Taylor, DTC (UK)

  2. 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 Larry Taylor, DTC (UK)

  3. Part 1868-870MHz Band Channel Numbers Related comments Taylor 637, 638 Larry Taylor, DTC (UK)

  4. Proposed Resolution • Define 200kHz spacing for the 863-870 band • Delete last paragraph in 6.1.2.5a.3 • Channel numbers will be defined according to equation (1) • Note that GuardBand is re-introduced in Equation (1) and we need to define: • GuardBand = • 0 for the bands in Japan • 25kHz for European 863-870 band • ½ Channel Spacing elsewhere • Note also that product vendors will declare support for channel numbers compliant with local regulatory requirements via the phySUNChannelsSupported PIB attribute Larry Taylor, DTC (UK)

  5. Part 2MR-O-QPSK Channel Numbers Related comments Taylor / Schmidt / Park 470, 643, 644, 649, 661 Larry Taylor, DTC (UK)

  6. Section 6.1.2.5a.4 • Remove each occurrence of “For channel page x, ” , where x = 0,1,2,3 Larry Taylor, DTC (UK)

  7. Part 3OFDM & O-QPSK Page 7 PHY Mode Representation Related comments Taylor / Seibert 494 Larry Taylor, DTC (UK)

  8. Modify Figure 22a as follows Larry Taylor, DTC (UK)

  9. Part 4MLME Scan for SUN PHYs Related comments Taylor / Ecclesine 474 Larry Taylor, DTC (UK)

  10. 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 Larry Taylor, DTC (UK)

  11. Part 5MR-O-QPSK Channel Pages Related comments Schmidl / Taylor / Schmidt / Park 501, 584, 585, 586 Larry Taylor, DTC (UK)

  12. 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 MR-O-QPSK) Larry Taylor, DTC (UK)

  13. 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-787 is band 15 868-870 is band … presumably band 2 902-928 is band 3 … presumably the 915 band 2400-2483.5 is band 4 For each frequency band in Table 75p and Table 75qdefine 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 Define rows for the 4 PHY Modes defined in each band as per table 75p and table 75q June, 2010 Slide 13 Larry Taylor, DTC (UK) Larry Taylor, DTC (UK)

  14. 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 Larry Taylor, DTC (UK)

  15. Part 6PIB Attributes Related comments Taylor 1107, 1175 Larry Taylor, DTC (UK)

  16. Global Corrections • 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…. Larry Taylor, DTC (UK)

  17. 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 Larry Taylor, DTC (UK)

  18. 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 Larry Taylor, DTC (UK)

More Related