1. Submission for CID 12 and 231 Date: 2006-06-22 Authors: 6/22/2006
doc.: IEEE yy/xxxxr0
6/22/2006
Submission for CID 12 and 231
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Zhang junping,Huawei
Zhang junping,Huawei

2. 6/22/2006
Abstract
Submission for CID 12 and 231
Zhang junping,Huawei

3. Outline The overview of CID 12 and 231 Proposed resolution 6/22/2006
doc.: IEEE yy/xxxxr0
6/22/2006
Outline
The overview of CID 12 and 231
Proposed resolution
Zhang junping,Huawei
Zhang junping,Huawei

4. The overview of CID 231 and 12 CID: 231
6/22/2006
The overview of CID 231 and 12
CID: 231
Comment: Congestion Level should be defined.
Proposed Change: A submission will be provided.
Resolution: Defer-RPS
CID: 12
Comment:
It is not clear what the use of the expiration timer is. If an MP is at a certain congestion level (say congested), it cannot predict beforhand how long this condition would last. Congestion levels don't usually time out.
Proposed Change: Delete expiration timer
Resolution: Defer-NS
Zhang junping,Huawei

5. The definition of level and timer
6/22/2006
The definition of level and timer
Neighborhood Congestion Element
Octets: 1 1 2 ID
Length
Congestion Level
Expiration Timer
The congestion level indicates the congestion level of MP which detects congestion
The expiration timer indicates the lifetime of current congestion level
The neighborhood should adjust their transmit rate according to the congestion level and expiration timer
Zhang junping,Huawei

6. The definition of level and timer(con’t)
6/22/2006
The definition of level and timer(con’t)
Congestion level will increase by degrees at the end of each period if congestion announcement needs to be sent
The congestion level initials or resets to zero, which indicates no need to send announcement frame.
The expiration timer equals one period
Zhang junping,Huawei

7. 6/22/2006
The usage of level
Mp5 sends a congestion announcement to its neighbors(mp1,mp2,mp3 and mp4)
The neighbors adjust their local rate by adjusting the AIFSN according to the congestion level included in congestion announcement sent by mp5
The specific adjust method is the local implementation matter.
Zhang junping,Huawei

8. The usage of expiration timer
6/22/2006
The usage of expiration timer
The process of rate adjusting for neighborhood
The neighbors reset the transmit rate to the default value if there is no announcement received when time is out.
Zhang junping,Huawei

9. 6/22/2006
motion
Motion: move to insert the submission text( s-congestion-control-announcement.doc) into the P802.11s / D0.03
Move :
Second :
Result:
Zhang junping,Huawei

10. 6/22/2006
The problem
If congestion mp received more than one congestion announcement , which announcement it will adjust its rate according to
This is the implementation matter
The neighboring mp
The congestion mp
Zhang junping,Huawei

11. 6/22/2006
Why does the expiration timer have the same value all the time for a mp 1 3 2
period
level
The congestion duration is too difficult to estimate
Each level will last one period, so the value of the expiration timer need not be estimated any more
If announcement need to be sent ,the level will increase by one
Zhang junping,Huawei

12. Backup : an example of rate adjusting
6/22/2006
Backup : an example of rate adjusting
Method of rate adjusting
is a constant, and has different value depend on scenario
n denotes congestion level indicated by neighborhood congestion announcement
Zhang junping,Huawei