Presentation is loading. Please wait.

Presentation is loading. Please wait.

March, 2006 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [proposed merger] Date Submitted: [8 March,

Similar presentations


Presentation on theme: "March, 2006 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [proposed merger] Date Submitted: [8 March,"— Presentation transcript:

1 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

2 March, 2006 A1: Beaconing All mesh-capable devices (including PNC and DEV) should 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

3 A2: Distributed solutions for SOP
March, 2006 A2: Distributed solutions for SOP No parent/child/neighbor relationship (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

4 A3: Alignment of superframes
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

5 Issues being addressed
March, 2006 Issues being addressed Alignment Where to align? (both solutions have pros and cons) What to consider? (complexity, power consumption, efficiency) Synchronization Support of CAP Mandatory or optional? How? Chun-Ting Chou, Philips

6 March, 2006 Proposed Merger When a beaconing 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 devices (or two groups) observe each other, they shall “cross protect” each other’s beacon transmission (reduced complexity) Chun-Ting Chou, Philips

7 Power Consumption Beacon Beacon March, 2006 N=3, improvement =194%
Wake-up time (~5 ms) Tx/Rx turnaround time (~10 us) Tx/Rx turnaround time +Guard time (~20 us) Beacon Beacon A B C A B C (Tx/RX) 300 mA Power = 70*300* *60*3 = = (Standby) 60 mA (idle) <1 mA Make it conservative: Wake up time = 2 ms N=3, improvement =194% (Tx/RX) 300 mA Power = 80*300* *60 = = (idle) <1 mA When N increases, improvement increases ( 327% for N=6, 587% for N=infinity) Chun-Ting Chou, Philips

8 QoS Support for delay-sensitive Apps.
March, 2006 QoS Support for delay-sensitive Apps. Less fragmented superframes Fragmented superframes With less fragmented superframes, PNCs are able to accommodate more time- sensitive applications/streams via CTA re-configuration Delay Requirement A B C A CAP/MCTA or BP With fragmented superframes, the number of sensitive applications/streams can be admitted via CTA re-configuration is limited, even sufficient amount of CTA exists A B C Chun-Ting Chou, Philips

9 Backward Compatibility
March, 2006 Do we need a CAP? Why not How to provide a CAP and its functions Association CAT (slotted Aloha or CSMA/CA) Open MCTA (slotted Aloha or CSMA/CA) Open CTA (slotted Aloha or CSMA/CA) How does a PNC do? For mesh-capable PNC (use content access CTAs listed above) For “legacy” PNC (they do whatever they like) Chun-Ting Chou, Philips


Download ppt "March, 2006 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [proposed merger] Date Submitted: [8 March,"

Similar presentations


Ads by Google