<doc.: IEEE −doc>

Slides:



Advertisements
Similar presentations
doc.: IEEE <doc#>
Advertisements

November 2010 doc.: IEEE e Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: LB60 comment.
<month year> <doc.: IEEE doc>
Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
<month year> doc.: IEEE <# > <April 2008>
<month year> doc.: IEEE < e>
<month year> doc.: IEEE < e>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
<doc.: IEEE −doc>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Add name of submission] Date Submitted:
doc.: IEEE <doc#>
<month year> doc.: IEEE < e>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
<month year> doc.: IEEE < e>
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> doc.: IEEE < e>
doc.: IEEE <doc#>
<month year> doc.: IEEE < e>
Submission Title: [Rate one over four code for TG4a]
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Inclusion.
<month year> doc.: IEEE < e>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> March 2015
<month year> doc.: IEEE < e>
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> July 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> July 2014
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> September 2015
Submission Title: [Uniform bandplan for TG4a Modulation]
<month year> doc.: IEEE < e>
<month year> doc.: IEEE <xyz> November 2000
<author>, <company>
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> <doc.: IEEE doc> May 2015
<month year> <doc.: IEEE doc> May 2015
<month year>20 Jan 2006
doc.: IEEE <doc#>
<month year> doc.: IEEE < e>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
<month year> doc.: IEEE < e>
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> January 2016
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [SFD comparison] Date Submitted: [18−July−2006]
Submission Title: [SFD comparison] Date Submitted: [18−July−2006]
<month year> <doc.: IEEE doc> July 2015
<author>, <company>
Submission Title: [SFD comparison] Date Submitted: [18−July−2006]
<month year> doc.: IEEE <030158r0> <March 2003>
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
September 2009doc.: IEEE wng0
<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.
<month year> <doc.: IEEE doc> March 2015
July 2003 doc.: IEEE <03/242> July 2003
Submission Title: TG9ma Agenda for September Meeting
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Presentation transcript:

<doc.: IEEE 802.15−doc> <month year> <doc.: IEEE 802.15−doc> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [A MAC frame format including Information Elements] Date Submitted: [16th July 2015 ] Source: [Billy Verso] Company: [DecaWave] Address: [Adelaide Chambers, Peter Street, Dublin 8, Ireland] Voice:[1353 1 6975030] Fax: [] E−Mail:[billy.verso “at” decawave.com] Re: [A presentation of a MAC frame format including Information Elements] Abstract: [Presents a MAC frame format proposal for 802.15.8 that includes information elements] Purpose: [Material for discussion in IEEE 802.15 TG8] 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. Verso (DecaWave) <author>, <company>

Introduction This document presents a method to include Information Elements (IEs) into the 802.15.8 MAC Frame It also presents a possible encoding method for the IEs This is not the same as the IE encoding used in 802.15.4 Verso (DecaWave)

General MAC frame format with IEs The above is based generally on 802.15.4 (“2015?”) with the addressing fields sized as per TG8’s current thinking The difference between Header and Payload IEs is that Header IEs are not encrypted while Payload IEs may be encrypted Verso (DecaWave)

Frame control field (EXAMPLE) Verso (DecaWave)

Content Length (octets) Content Length (octets) IE’s defined for ranging IE ID value IE Name Acronym Content Content Length (octets) 1 Ranging Request Reply Time IE RRRT IE NONE 2 Ranging Reply Time Instantaneous IE RRTI IE RX to TX Reply Time 4 3 Ranging Reply Time Deferred IE RRTD IE Ranging Preferred Reply Time IE RPRT IE Preferred Reply Time 5 Ranging Control Double-sided TWR IE RCDT IE Control Info 6 Ranging Round Trip Measurement IE RRTM IE TX to RX round trip time 7 Ranging Time-of-Flight IE RTOF IE One more IE is needed IE ID value IE Name Acronym Content Content Length (octets) IE List terminator IE TERM IE NONE Verso (DecaWave)

Proposed Payload IE encoding The above is would allow some future flexibility The short form is a very limited resource and will be prized If no other use more important IE usage emerges we should use the shortest ones for the Ranging IEs Shorter messages are better for higher density networks and reduced power drain Verso (DecaWave)

Conclusion The scheme presented here represents some initial thoughts on how 802.15.8 could encode its IEs This probably need to be developed a little more before we write the text and so is subject to change Verso (DecaWave)