1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2005
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [PAR conflict in IEEE baseline document]
Date Submitted: [ 21 Septemeber, 2005]
Source: [Michael Sim] Company [Panasonic Singapore Laboratories]
Address [Blk 1022 Tai Seng Avenue # , Singapore, Singapore , Singapore]
Voice:[ ], FAX: [ ],
Re: [Response to IEEE baseline document]
Abstract: [Presentation to highlight the technical problem of IEEE baseline draft in satisfying the PAR.]
Purpose: [For discussion in the IEEE Task Group]
Notice: This document has been prepared to assist the IEEE P 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 P
Michael Sim, Panasonic Singapore Laboratories
<author>, <company>

2. September 2005
IEEE PAR
Scope: “To provide a recommended practice to provide the architectural framework enabling WPAN devices to promote interoperable, stable, and scaleable wireless mesh topologies and, if needed, to provide the amendment text to the current WPAN standards that is required to implement this recommended practice.”
Objectives: facilitates wireless mesh topologies optimized for IEEE WPANs.
Extension of network coverage without increasing the transmit power or the receiver sensitivity
Enhanced reliability via route redundancy
Easier network configuration
Better device battery life
Michael Sim, Panasonic Singapore Laboratories

3. Superframe Structures
September 2005
Superframe Structures
IEEE
Baseline MAC
Superframe n-1
Superframe n
Superframe n+1 B
CAP
Channel time allocation period …
CTA 1
CTA 2
CTA n-1
CTA n
IEEE
Superframe n-1
Superframe n
Superframe n+1
Beacon Period – Multiple beaconing slot
Procedure to determine which Beacon slot to use
CAP after Beacon Period
How long is Beacon Period?
Devices (PNC and DEV) involving in Mesh operation to broadcast beacons in beacon period
Active Superframe
Inactive B
Single Beacon slot
CAP after beacon transmission
Michael Sim, Panasonic Singapore Laboratories

4. Changes Required to IEEE 802.15.3(4) (for TG discussion)
September 2005
Changes Required to IEEE (4) (for TG discussion)
In order to use baseline method for Mesh IEEE need to be changed:
Superframe structure to change to allow Beacon Period (variable sized?) consisting of beacon slots
Can this new structure coexists with IEEE superframe?
GTS for isochronous data stream changed from CTA to DRP
All Mesh devices (PNC and DEV) to broadcast beacon in a new way (i.e. using numbered beacon slots in Beacon Period)
DEV also required to broadcast beacon?
In order for non-mesh enabled device to communicate with mesh devices, does it mean that:
15.3(4) device need to be able to communicate using the new superframe structure as well?
How much of IEEE MAC is changed?
Technically, it seems like a major re-write of 15.3/4 MAC
Will it be acceptable to the TG3 members as “recommended practice”?
Main concern: Wasted effort working on a baseline document that potentially fails at the sponsor ballet due to violation of PAR or not accepted generally by TG3 or TG4 as “recommended practice”.
Michael Sim, Panasonic Singapore Laboratories

5. End of Slide Thank You. September 2005
Michael Sim, Panasonic Singapore Laboratories