July, 2003 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Changes to 802.15.4] Date Submitted:

Slides:



Advertisements
Similar presentations
Submission Title: [Add name of submission]
Advertisements

<month year> <doc.: IEEE doc> May 2015
<month year> doc.: IEEE < e> <Mar 2016>
<month year> doc.: IEEE <030158r0> July, 2004
March, 2003 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [WG-TG4 Opening Report Mar03] Date Submitted:
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Add name of submission] Date Submitted:
doc.: IEEE <doc#>
Submission Title: [SG5 Closing Report Mar04]
doc.: IEEE <doc#>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [PIB Coordination in g] Date Submitted:
doc.: IEEE <doc#>
NOV 01 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Application Specific Information Element] Date.
doc.: IEEE <doc#>
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<month year> <Sept 2018>
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#>
January 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Technical Requirement sub-group report]
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4h Closing Report for Orlando Mar 2010.
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
doc.: IEEE <doc#>
July 2005 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c rate-range requirements: looking forward]
Submission Title: [One-to-many and many-to-many peering procedures]
Source: [Pat Kinney] Company [Kinney Consulting LLC]
Sept 2004 doc.: IEEE b Sept 2004 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE <xyz> November 2000
Submission Title: [IEEE WPAN Mesh Reference Model]
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Extensions to IEEE in support of.
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
Submission Title: [Frame and packet structure in ]
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Simplified geometry for the usage model.
<month year>20 Jan 2006
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Extensions to IEEE in support of.
<month year> <Nov 2018>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
doc.: IEEE <doc#>
doc.: IEEE <doc#>
April 19 July 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: WNG Closing Report for San Diego.
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
March 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [DF6 Radio-burst length over PSDU size] Date.
doc.: IEEE <doc#>
10 May 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Open Issues with the TG3 Criteria Document]
July 2010 <month year> doc.: IEEE g Doc.: IEEE g
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution of TG6 Draft D0 comments.
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
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.
July 2009 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Flexible DSSS Merging Effort] Date Submitted:
<month year> <doc.: IEEE doc> September 2015
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Improve the latency between GTS request.
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Summary.
<month year> <doc.: IEEE doc> March 2015
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4h Closing Report for Orlando Mar 2010.
July 2003 doc.: IEEE <03/242> July 2003
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: CID 422 Proposal Date Submitted: 14 August,
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

July, 2003 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Changes to 802.15.4] Date Submitted: [19 July 2003] Source: [Patrick Kinney] Company [Kinney Consulting LLC] Address [4097 Manor Oaks Ct, Export, PA, USA] Voice:[+1.724.733.8650], FAX: [Add FAX number], E-Mail:[pat.kinney@ieee.org] Re: [In response to call for amendments or corrigendum to IEEE 802.15.4.] Abstract: [Changes to 802.15.4 standard including MAC and PHY changes.] Purpose: [This submission contains changes to enhance 802.15.4.] 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. Patrick Kinney, Kinney Consulting LLC

Alignment with 802.2 Highly Accurate Distributed Clock July, 2003 Proposed Changes to 802.15.4 Alignment with 802.2 Highly Accurate Distributed Clock Patrick Kinney, Kinney Consulting LLC

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> July, 2003 Alignment with 802.2 Type 1 LLC states that although MACs will set maximum packet size it also requires that the minimum packet size is 128 octets. 6.8.1 Maximum number of octets in a UI PDU Refer to the appropriate MAC protocol specification for any limitation on the maximum number of octets in a UI PDU. No restrictions are imposed by the LLC sublayer. However, in the interest of having a value that all users of Type 1 LLC may depend upon, all MACs must at least be capable of accommodating UI PDUs with information fields up to and including 128 octets in length. Patrick Kinney, Kinney Consulting LLC <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> July, 2003 Alignment with 802.2 Type 2 LLC states that although MACs will set maximum packet size it also requires that the minimum packet size is 128 octets. 7.8.3 Maximum number of octets in an I PDU, N1 N1 is a data link connection parameter that denotes the maximum number of octets in an I PDU. Refer to the various MAC descriptions to determine the precise value of N1 for a given medium access method. LLC itself places no restrictions on the value of N1. However, in the interest of having a value of N1 that all users of Type 2 LLC may depend upon, all MACs must at least be capable of accommodating I PDUs with information fields up to an including 128 octets in length. Patrick Kinney, Kinney Consulting LLC <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> July, 2003 Alignment with 802.2 Type 3 LLC states that MACs will set maximum packet size. 8.6.2 Maximum number of octets in an ACn command PDU, N3 N3 is a logical link parameter that denotes the maximum number of octets in an ACn command PDU. Refer to the various MAC descriptions to determine the precise value of N3 for a given medium access method. LLC places no restrictions on the value of N3. Patrick Kinney, Kinney Consulting LLC <author>, <company>

Alignment with 802.2 LLC Propose change to the PHY July, 2003 Alignment with 802.2 LLC Propose change to the PHY Change of the PHY from 127 to 153 bytes, and Propose change to the MAC Change aMaxMACFrameSize to 128 bytes. Patrick Kinney, Kinney Consulting LLC

Highly Accurate Distributed Clock July, 2003 Highly Accurate Distributed Clock Multiple sensor arrays typically need an accurate shared clock. Disturbances Flow rates Temperature v.s. time gradients Pressure v.s. time gradients Etc. Patrick Kinney, Kinney Consulting LLC

Highly Accurate Distributed Clock July, 2003 Highly Accurate Distributed Clock An accurate distributed clock must be done at the MAC level CSMA backoffs are not known at higher layers PHY and MAC timing is not known at higher layers Higher SAPs are not intended to be time bound nor used at very short intervals Patrick Kinney, Kinney Consulting LLC

Highly Accurate Distributed Clock July, 2003 Highly Accurate Distributed Clock Propose adding primitives into the MAC to allow the coordinator to send out highly accurate clock signals to attached devices Patrick Kinney, Kinney Consulting LLC