1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
March, 2006
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [proposed merger]
Date Submitted: [8 March, 2006]
Source: [Chun-Ting Chou] Company [Philips]
Address [345 Scarborough Rd, Briarcliff Manor, NY 10510]
Voice:[ ], FAX: [ ],
Re: [N/A]
Abstract: [Summary of agreements and proposed merger]
Purpose: [Summary of agreements and proposed merger]
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
NOTE: Update all red fields replacing with your information; they are required. This is a manual update in appropriate
fields. All Blue fields are informational and are to be deleted. Black stays. After updating delete this box/paragraph.
Chun-Ting Chou, Philips
<author>, <company>

2. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
March, 2006
A1: Beaconing
All mesh-capable devices (including PNC and DEV) shall send beacons
All beaconing devices may be considered as “PNCs” and therefore, SOP has to be solved 2 1
Master (PNC/FFD)
Slave (DEV/RFD)
Control & Data path
Mesh Control & Data path
Data path
Mesh Data path 6 A 5 C 3 7 4 8 B 9
Inter-piconet
Communications
Source: Michael Sim’s presentation 13
Chun-Ting Chou, Philips
<author>, <company>

3. A2: Distributed solutions for SOP
<month year>
doc.: IEEE <doc#>
March, 2006
A2: Distributed solutions for SOP
Parent/child/neighbor relationship not required (distributed, peer-to-peer solutions for SOP)
A’s Superframe
Source: Michael Sim’s presentation
B’s Superframe A A B B C
Alignment
C’s Superframe A B C
“beacon period”
Chun-Ting Chou, Philips
<author>, <company>

4. A3: Alignment of superframes
<month year>
doc.: IEEE <doc#>
March, 2006
A3: Alignment of superframes
“Protection” via CTA is based on superframes are aligned & synchronized
Alignment
Medium slot boundary or superframe start time
Synchronization
distributed nature of both solutions
clock drifting
Chun-Ting Chou, Philips
<author>, <company>

5. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
March, 2006
Merger
When a beaconing mesh-enabled device powers up, it scan for at least one superframe and shall attempt to join the existing beacon group, if any (better performance)
When two beacon mesh-enabled devices (or two groups) observe each other, they shall “cross protect” each other’s channel time allocations (reduced complexity)
Chun-Ting Chou, Philips
<author>, <company>

6. Backward compatibility
<month year>
doc.: IEEE <doc#>
March, 2006
Backward compatibility
A mesh capable device shall protect a legacy piconet
If a legacy PNC is operating on a channel, the mesh device may use a different channel
If there are no alternative channels available, the mesh capable device may join the existing legacy piconet and allocate a private CTA for mesh operation
There might be other options to protect the existing legacy piconet
Chun-Ting Chou, Philips
<author>, <company>