60 likes | 321 Views
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: Power Save Proposal Date Submitted: 23 January, 2002 Source: Dr. William Shvodian Company: XtremeSpectrum, Inc. Address: 8133 Leesburg Pike, Suite 700, Vienna, VA 22182
E N D
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: Power Save Proposal Date Submitted: 23 January, 2002 Source: Dr. William Shvodian Company: XtremeSpectrum, Inc. Address: 8133 Leesburg Pike, Suite 700, Vienna, VA 22182 Voice: 703-269-3047 , FAX: 703-269-3092 , E-Mail: bshvodian@xtremespectrum.com Re: [ Power save mechanism in TG3-MAC ] Abstract: This provides a comparison of the proposed power save mechanism for TG3-MAC. Purpose: To provide information for comment resolution of LB12 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 Dr. William Shvodian
Complexity of EPS in D09 • 11 power management primitive parameters • 6 power management commands • Multiple commands (and Beacons) required for entering EPS mode • Power Management Information Element – Where is this ever used? • 7 full pages of text in Clause 8. • Very difficult to understand, much less implement. • Violates the KISS principal. Dr. William Shvodian
Complexity of EPS in D09 • PNC needs to change CTAs for every DEV in each EPS set twice per sleep interval • Critical timing interaction required between Beacon contents and Beacon transmission time • Multiple areas of the standard have been modified and complicated in the name of power management (CTRB, CTA) • Requires unspecified upper layer negotiation for EPS set configuration and maintenance Dr. William Shvodian
Things that PNC must maintain for EPS • Members of EPS Set • EPS Set Value (1 octet) • EPS Set Members (1 octet per member) • EPSTime (2 octets) & associated timer(s) • EPSNext (2 octets) • ATP • Streams associated with the EPS Set • CTAs for each DEV in the EPS set • CTAs: Active, EPS, Null • 4+ EPS action types Dr. William Shvodian
Gubbi Alternative Power Save Proposal • No IP • 2 or 3 command types • 2 MLME primitive parameters • 3 total commands – single exchange to enter sleep • 1 EPS mode • 1 type of CTA • PNC only has to track ATP. • PNC does nothing but receive Sleep Continue frames if DEVs stay in EPS mode • PNC only has to change CTAs when DEV wakes • Easy to understand, easy to implement, low complexity, low power for both DEV and PNC Dr. William Shvodian
Recommendation • Adopt Gubbi proposed text as the new power save baseline. Dr. William Shvodian