Suggested comment resolution on Power save clause

Slides:



Advertisements
Similar presentations
Beacon Measurement on Pilot Frames
Advertisements

Coexistence Motions for LB84 Comment Resolution
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Motions Date: Authors: January 2006
Suggested comment resolution on Power save clause
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
Power Save Mechanism for Unsync MPs
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Quick Beacon Impacts on LB 92
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
July 2012 Opening Report Date: Authors: July 2012
Protection Assurance Method
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
Suggested comment resolution on ATIM window parameter
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGr Proposed Draft Revision Notice
Suggested comment resolution on Power save clause
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
May 2005 CAPWAP AHC Closing Report
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
TGv Redline D0.13 Insert and Deletion
Suggested comment resolution on Mesh DTIM element
Overview Suggested Comment Resolution for Mesh Synchronization
January Opening Report
Clarification on CID3778 and Mesh TIM element
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
Location Capability Negotiation
Suggested comment resolution on ATIM window parameter
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Summary of Unresolved MAC Comments for 2/28 TGs Telecon
Greenfield protection mechanism
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

Suggested comment resolution on Power save clause April 2007 Suggested comment resolution on Power save clause Authors: Date: 2007-04-12 Notice: This document has been prepared to assist IEEE 802.11. 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Kazuyuki Sakoda et.al.

Abstract Reviewed Comments labeled as “Power Save” April 2007 Abstract Reviewed Comments labeled as “Power Save” There are 102 open comments regarding “Power Save”. It is better to break them down to more detailed sub-categories. Following slides present : Suggested detailed issue identifier for “power save” related comments. Suggested draft text refinement policy on power save clause. Kazuyuki Sakoda et.al.

Suggested sub-categories for power save issues April 2007 Suggested sub-categories for power save issues “Power save - editorial” [37] While not as an editorial comment, comments suggest the better explanation. Comments suggesting to restructure the document regarding power save clause. “Power save - clarification” [10] Comments invoking some clarification. “Power save - ATIM parameter” [02] Comments on how to advertise ATIM window size parameter. “Power save - ATIM window” [03] Comments on the particular issue on ATIM window. “Power save - APSD” [15] Comments regarding APSD type of power saving. “Power save - sync parameter” [06] Comments on how to deal with sync MP’s parameters. “Power save - MIB” [05] Comments on the lack of MIB attribute. “Power save - general” [21] Comments which seems to need some discussion to resolve. “Power save - other” [03] Comments seem to be belonging to other category. Kazuyuki Sakoda et.al.

Suggested sub-categories for power save issues April 2007 Suggested sub-categories for power save issues “Power save - editorial” [37] While not as an editorial comment, comments suggest the better explanation. Comments suggesting to restructure the document regarding power save clause. “Power save - clarification” [10] Comments invoking some clarification. “Power save - ATIM parameter” [02] Comments on how to advertise ATIM window size parameter. “Power save - ATIM window” [03] Comments on the particular issue on ATIM window. “Power save - APSD” [15] Comments regarding APSD type of power saving. “Power save - sync parameter” [06] Comments on how to deal with sync MP’s parameters. “Power save - MIB” [05] Comments on the lack of MIB attribute. “Power save - general” [21] Comments which seems to need some discussion to resolve. “Power save - other” [03] Comments seem to be belonging to other category. Focused comments in this proposal comments which could be resolved by 07/319, 07/320. Kazuyuki Sakoda et.al.

Summary of comments focused in this proposal April 2007 Summary of comments focused in this proposal Many of the comments identified as “Power save - editorial” or “Power save - clarification” request to clean up the text. What the Power Save capability bits in Mesh capability indicate? What is meant by “power save support”? What happens if MP changes its power management mode? How the ATIM window will be used? Suggest to change the document structure. MAP behavior and MP behavior is mixed up. Power save mode and power save support is mixed up. Text refers to inappropriate information elements. Informative text should not be present in the main body of the standard. Does LWMP process “association” ? Some editorial suggestions... Kazuyuki Sakoda et.al.

Suggested refinement policy April 2007 Suggested refinement policy Explicitly define two roles: Power save supporting MP: MP which is communicating with MP in power save mode. Power save supporting MP may or may not be in power save mode. Power saving MP: MP which is in power save mode. Power saving MP can establish/maintain peerlink only with power save supporting MPs. Power saving MP needs to be “power save supporting MP”, unlike STA in BSS. Reorganize the power save clause Explain the behavior of unsync MP and sync MP independently. Explain the behavior of “power save supporting MP” and “power saving MP” independently. Kazuyuki Sakoda et.al.

Suggested changes to the draft spec April 2007 Suggested changes to the draft spec Before: 11A.11 Power Management in a Mesh (Optional) 11A.11.1 Overview 11A.11.2 Basic approach 11A.11.3 Initialization of power management within a mesh 11A.11.4 MP power state transitions 11A.11.5 Frame transmission 11A.11.6 Power management operation with APSD 11A.11.7 TS Reinstatement 11A.11.8 Beacon broadcaster power save mode Kazuyuki Sakoda et.al.

Suggested changes to the draft spec April 2007 Suggested changes to the draft spec  After: 11A.11 Power Management in a Mesh (Optional) 11A.11.1 Overview 11A.11.2 Basic approach 11A.11.3 MP power management modes 11A.11.4 Initialization of power management in mesh 11A.11.4.1 Initialization of power management of unsync MP 11A.11.4.2 Initialization of power management of sync MP 11A.11.5 Receive operation for MPs in PS mode 11A.11.5.1 Receiving frames from unsync MP 11A.11.5.2 Receiving frames from sync MP 11A.11.6 Frame transmission 11A.11.6.1 Operation of power save supporting unsync MP 11A.11.6.2 Operation of power save supporting sync MP 11A.11.7 Power management operation with APSD Kazuyuki Sakoda et.al.

Suggested changes to the draft spec (Cont’d) April 2007 Suggested changes to the draft spec (Cont’d) 11A.11.1 Overview Motivation of power save mode in mesh. Utilization of the power save capability bits. 11A.11.2 Basic approach Brief overview of the entire power save mechanism. 11A.11.3 MP power management modes State transition between active mode and power save mode. 11A.11.4 Initialization of power management in mesh Procedure which needs to be done to initialize power management. 11A.11.4.1 Initialization of power management of unsync MP Procedure necessary for unsync MP 11A.11.4.2 Initialization of power management of sync MP Procedure necessary for syncMP Kazuyuki Sakoda et.al.

Suggested changes to the draft spec April 2007 Suggested changes to the draft spec 11A.11.5 Receive operation for MPs in PS mode Power state transmition of power saving MP 11A.11.5.1 Receiving frames from unsync MP How to receive frames from unsync MP 11A.11.5.2 Receiving frames from sync MP How to receive frames from sync MP 11A.11.6 Frame transmission Frame transmission rules for power save supporting MP 11A.11.6.1 Operation of power save supporting unsync MP Frame transmission rules for unsync MP 11A.11.6.2 Operation of power save supporting sync MP Frame transmission rules for sync MP 11A.11.7 Power management operation with APSD Additional rules for APSD type of operation. Kazuyuki Sakoda et.al.