Submission Title: [Channel Bands Update]

Slides:



Advertisements
Similar presentations
Doc.: IEEE xxx g Submission March 2011 Kuor Hsin Chang, Bob Mason (Elster Solutions) Project: IEEE P Working Group for Wireless.
Advertisements

Doc.: IEEE b Submission November 2004 Robert Cragie, Jennic Ltd.Slide 1 Project: IEEE P Working Group for Wireless Personal.
doc.: IEEE <doc#>
September 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: PIB Coordination in g Date Submitted:
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 1014 Proposed Partial Resolution.
Name - WirelessHD doc.: IEEE g July 2010
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Submission Title: [TG4b MAC backward compatibility]
Submission Title: [Channel Page/Number Proposal]
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [PIB Coordination in g] Date Submitted:
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
January 2014 doc.: IEEE /0084r0 January 2016
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
July Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [On unifying PPDU formats] Date Submitted:
Submission Title: [Errors in a] Date Submitted: [18 March, 2010]
doc.: IEEE <doc#>
Project: IEEE P WG for Wireless Personal Area Networks (WPANs)
Date Submitted: [March 13, 2011] Source:[Ben Rolfe] Company [BCA, SSN]
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE g-Trends-in-SUN-capacity
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
Submission Title: [IEEE WPAN Mesh Reference Model]
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
Submission Title: [Frame and packet structure in ]
Submission Title: Rogue Resolutions from kivinen
doc.: IEEE g-Trends-in-SUN-capacity
doc.: IEEE <doc#>
doc.: IEEE g-Trends-in-SUN-capacity
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment Resolutions – Taylor et al] Date.
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
f- 433 MHz PHY and MAC for TG4f - Preliminary Proposal July 2009 Project: IEEE P Working Group for Wireless Personal.
平成31年4月 doc.: IEEE /424r1 July 2008 doc.: IEEE c
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#1>
doc.: IEEE <doc#>
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 1014 Proposed Partial Resolution.
Submission Title: [Proposed Resolution for FSK/GFSK Prior Comments]
doc.: IEEE <doc#>
September 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: PIB Coordination in g Date Submitted:
July 2004 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Modified Delayed (Dly) Acknowledgement for.
Submission Title: Rogue Resolutions from kivinen
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comment Resolutions – Taylor et al] Date.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution of TG6 Draft D0 comments.
<month year> doc.: IEEE <030158r0> <March 2003>
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
<month year> doc.: IEEE < e> <March 2016>
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
doc.: IEEE <doc#>
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution of TG6 Draft D0 comments.
doc.: IEEE g-Trends-in-SUN-capacity
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
September, 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: Sept.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:
Presentation transcript:

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Channel Bands Update] Date Submitted: [10 February, 2010] Source: [Larry Taylor] Company [DTC (UK)] Address [UK] Voice:[], FAX: [], E-Mail:[larry.taylor@discretetime.com] Re: [Draft 15.4g draft FSK text] Abstract: [Update on Channel Bands – corrects a duplicate PHY PIB attribute name in 15-10-0007-02] Purpose: [This presentation supports updated Channel Bands draft text in 802.15-10-0008-1] 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.

Separate Standard Channel Page & Generic PHY Channel Page structures Channel Bands Update Separate Standard Channel Page & Generic PHY Channel Page structures Page 2

Focus of the Update The general form of the Channel Band Descriptor provides a very powerful generic PHY description mechanism However, the Standard PHYs don’t need the general form of the descriptor This update separates the standard channel page description (Channel Page 7) from the Generic PHY description (Channel Page 8) and defines a channel numbering scheme for standard 15.4g operation Page 3

Part I – Standard Operation Channel Numbering

Reminder – The Problem 15.4g defines A large number of frequency bands (~20) A large number of PHY Modes (~50) Different data rates, channel separation, modulation Any PHY Mode may operate over a frequency band Not all combinations are defined, but in general all are possible This results in a very large number of distinct channels – far more than can be represented using the 32-bit Channel Page/Channel Number structure

Existing Constraints Many MAC Management primitives and MAC Commands use Channel Page and Channel Number parameters To maintain consistency with existing 15.4 specifications the extended channel numbering model must retain Channel Page and Channel Number structure In addition, the MLME-SCAN primitive has an explicit ScanChannels parameter defined as a 27-bit field Needs re-definition for 15.4g Field size is PHY Mode & frequency band dependent

15.4g Channel Page 7 Structure Define Channel Page 7 for 15.4g Bit positions index into the table of standard frequency bands A device sets the corresponding bit to 1 for each standard frequency band supported It is a convenient way of avoiding defining a PHY PIB attribute phyFrequencyBandsSupported Page 7

Page 7 Bit Index Each bit position in Page 7 corresponds to an index in the Standard Frequency Band Table Bit 20..27 are unused and reserved for future use

Current Frequency Band Add a PHY PIB attribute phyCurrentFrequencyBand Value is an index into the standard frequency band table Must correspond to a bit set to 1 in Channel Page 7 bits 0..26 Identifies which of the supported standard frequency bands is currently being used

PHY Mode Add a PHY PIB attribute phyPHYModesSupported A bit mask of supported PHY Modes (bit set to 1) with each bit corresponding to an index into the table of standard PHY Modes Size is determined by the number of standard PHY Modes Add PHY PIB attribute phyCurrentPHYMode Its value is an index into the table of standard PHY Modes and must correspond to a bit set to 1 in phyPHYModesSupported

Channels Supported The current 15.4 channel bit mask in bits 0..26 of the Channel Page indicate which channels are supported Allows a subset of possible channels to be supported Also used for channel scanning Add a PHY PIB attribute phyCurrentChannelsSupported to hold the channel bit mask for the current frequency band Size is frequency band and PHY Mode dependent

Number of Channels Add a PHY PIB attribute phyNumberChannels Identifies the number of channels for phyCurrentPHYMode in phyCurrentFrequencyBand Also identifies the number of significant bits in phyChannelsSupported

Current Channel The current channel is therefore determined by: phyCurrentChannel A number in the range 0..phyNumberChannels-1 Corresponding bit position in phyCurrentChannelsSupported must be set to 1 phyCurrentFrequencyBand A bit position in Page 7 set to 1 Indexes table of standard frequency bands phyCurrentPHYMode An index into the table of standard PHY Modes

Standard Canonical Name To support negotiation of mode of operation by higher layers Index values of standard frequency bands and PHY Modes Channel number is qualified by standard frequency band phyCurrentFrequencyBand PHY Mode phyCurrentPHYMode Channels supported phyChannelsSupported

PHY PIB Attributes New PHY PIB Attributes Modified PHY PIB Attributes phyCurrentFrequencyBand Value is an index into the table of standard frequency bands and must correspond to a bit position in Channel Page 7 set to 1 phyPHYModesSupported Bit mask of PHY Modes supported. Each bit corresponds to an index into the standard table of PHY Modes phyCurrentPHYMode Value is an index into the table of standard PHY Modes and must correspond to a bit set to 1 in phyPHYModesSupported phyNumberChannels Value is the number of channels in phyCurrentFrequencyBand for phyCurrentPHYMode phyCurrentChannelsSupported Channel bit mask of size phyNumberChannels identifying which channels may be used in the current freqency band Modified PHY PIB Attributes phyCurrentChannel Requires amended definition since range will be >27 for some SUN frequency bands and is frequency band and PHY Mode dependent phyCurrentChannel must correspond to a bit position in phyCurrentChannelsSupported set to 1 Page 15

The Channel Band Descriptor Part II – Generic PHY The Channel Band Descriptor

The Problem To allow 15.4g compliant systems to declare vendor specific modes of operation in a standard way Permit exchange and negotiation of operating parameters (frequency band and PHY Mode) Provide efficient short canonical name suitable for use in commands

15.4g Channel Page 8 Structure Define Channel Page 8 for 15.4g Each bit 0..26 (set to 1) identifies a Generic PHY descriptor

Generic PHY Descriptor Generic PHY Descriptors are only in Channel Page 8 Page 8 + ID forms a canonical name Frequency descriptor part based on band agnostic representation Parametric PHY part is PHY Type dependent Parameters for FSK PHY are suggested

PHY PIB Attributes Add PHY PIB attribute phyNumberGenericPHYDescriptors Add PHY PIB attribute phyGenericPHYDescriptors Array of phyNumberGenericPHYDescriptors elements each one containing a Generic PHY Descriptor Elements are uniquely identified by ID in the local system Add PHY PIB attribute phyCurrentGenericPHYDescriptor Value is the ID of a Generic PHY Descriptor and must correspond to a bit set to 1 in bits 0..26 of Channel Page 8

Part III – Mode Switch Support

Mode Switch PPDU Flag in the PHY Header identifies a frame PPDU variant for Mode Switching The Frame needs a parameter to identify the operating mode of the subsequent PPDU The canonical name serves as this parameter

Canonical Name (1) The canonical name is made up of two parts Frequency Band part PHY Mode part Channel Page 7 Frequency Band part is the bit index in channel page 7 and is the value of phyCurrentFrequencyBand PHY Mode is the value of phyCurrentPHYMode and is an index into the PHY Mode table Channel Page 8 phyCurrrentGenericPHYDescriptor holds the ID of a generic PHY descriptor Both Frequency Band & PHY Mode are identified in the generic PHY descriptor

Canonical Name (2) The canonical name is therefore Channel Page (7) : Frequency Band Index : PHY Mode index Channel Page (8) : Generic PHY Descriptor ID An encoding in 16 bits (or less) is possible The Mode Switch also needs a target Channel Number field

Questions Page 25