111103600000aaobssmlmecleanup.docx

1、111103600000aaobssmlmecleanupIEEE P802.11Wireless LANsOBSS MLME cleanupDate: 2011-03-14Author(s):NameAffiliationAddressPhoneemailAlex AshleyNDS LtdOne London Road, Middlesex, TW18 4EX, UKaashley at nds dot comAbstractCID2090 states:The usage of MLME-QLOADREQUEST and MLME-MLME-QLOADREPORT primitives

2、is non-standard. Why not just use an MLME-QLOADREQUEST 4-way primitive (.request, .indication, .response, .confirm)?with a proposed resolution of:Delete MLME-QLOADREPORT primitives. Add MLME-QLOADREQUEST.response (somewhat similar to existing MLME-QLOADREPORT.request). Modify MLME-QLOADREQUEST.confi

3、rm that is similar to existing MLME-QLOADREPORT.indication. Same thing with TXOPADVERTISEMENT and TXOPRESPONSE.This proposal also proposes resolutions to CID 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 that all call for a “Protected” parameter to be added.This document proposes normative text cha

4、nges to accept this comment. This document is based upon P802.11aa D3.01. Changes from the draft is shown using Word change tracking.6.3.3.3 MLME-SCAN.confirm 6.3.3.3.2 Semantics of the service primitiveInsert QLoad Report at the end of the table describing the BSSDescription parameter (note that th

5、e entire table is not shown here): (#2002)NameTypeValid rangeDescriptionIBSS adoptionQLoad ReportAs defined inframe formatAs defined in 8.4.2.aa93The values from the QLoad Report element if such an element was present in the probe response frame, else null. The parameter is optionally present only i

6、f dot11QLoadReportActivated is true.Do not adopt6.3.aa79 QLoad Report managementThis set of primitives supports the process of QLoad reporting between APs as described in 10.aa24.1.6.3.aa79.1 MLME-QLOAD.request6.3.aa79.1.1 FunctionThis primitive is used by an AP to transmit a QLoad Request to a spec

7、ified AP.6.3.aa79.1.2 Semantics of the service primitive The primitive parameters are as follows:MLME-QLOAD.request( PeerMACAddress(#2197) DialogTokenProtected (#2004) )NameTypeValid rangeDescriptionPeerMACAddress(#2197)MACAddressAny valid individual MACAddressThe address of the peer MAC entity to w

8、hich the QLoadRequest shall be sent.DialogTokenInteger1255Specifies a number unique to the QLoadReport.request primitiveProtectedBooleantrue, falseIf true, the request is sent using the Protected QLoad Request Protected Dual of Public Action Frame. If false, the request is sent using the QLoad Reque

9、st Public Action frame6.3.aa79.1.3 When GeneratedThe primitive is generated by the SME at an AP to request the sending of a QLoad Request to another AP indicated by PeerMACAddress(#2197).6.3.aa79.1.4 Effect of ReceiptOn receipt of this primitive, the MLME constructs a QLoad Request Action management

10、 frame if the Protected parameter is false, or a Protected QLoad Request Protected Dual of Public Action frame if the Protected parameter is true. The AP then attempts to transmit this frame to the AP indicated by PeerMACAddress(#2197).6.3.aa79.2 MLME-QLOAD.confirm6.3.aa79.2.1 FunctionThis primitive

11、 reports the result of a request to send a QLoad Request.6.3.aa79.2.2 Semantics of the service primitive The primitive parameters are as follows:MLME-QLOAD.confirm( ResultCode(#2198),PeerMACAddress,DialogToken,Protected (#2007)QLoadReport )NameTypeValid rangeDescriptionResultCode(#2198) Enumeration

12、SUCCESS, INVALID PARAMETERS or UNSPECIFIED FAILUREReports the outcome of a request to send a QLoad RequestPeerMACAddress(#2197) MACAddressAny valid individual MACAddressThe address of the peer MAC entity to which the QLoadRequest shall be sent.DialogToken Integer0255Specifies a number unique to the

13、QLoadReport.request primitive or 0 when sending an unsolicited reportProtectedBooleantrue, falseIf true, the response was sent using the Protected QLoad Report Protected Dual of Public Action Frame. If false, the response was sent using the QLoad Report Public Action frame.QLoadReport(#2199)Set of r

14、eports, each as defined in the QLoad Report elementSet of reports, each as defined in the QLoad Report elementSet of reports, each as defined in the QLoad Report element6.3.aa79.2.3 When GeneratedThis primitive is generated by the MLME as a result of an MLME-QLOAD.request primitive indicating the re

15、sults of that request. This primitive is generated by the MLME as a result of an MLME-QLOAD.request is found to contain invalid parameters, or when the STA receives a response in the form of an QLoad Report frame in the corresponding Robust AV Streaming Action frame.6.3.aa79.2.4 Effect of ReceiptThe

16、 SME is notified of the results of the QLoad request procedure.The SME should operate according to the procedures defined in 10.aa24.1. 6.3.aa79.3 MLME-QLOAD.indication6.3.aa79.3.1 FunctionThis primitive indicates that a QLoad Request frame has been received.6.3.aa79.3.2 Semantics of the service pri

17、mitive The primitive parameters are as follows: MLME-QLOAD.indication( PeerMACAddress(#2197) DialogTokenProtected (#2005) )NameTypeValid rangeDescriptionPeerMACAddress(#2197)MACAddressAny valid individual MACAddressThe address of the peer MAC entity to which the QLoadRequest shall be sent.DialogToke

18、n Integer1255Specifies a number unique to the QLoadReport.request primitive ProtectedBooleantrue, falseIf true, the request was sent using the Protected QLoad Request Protected Dual of Public Action Frame. If false, the request was sent using the QLoad Request Public Action frame.6.3.aa79.3.3 When G

19、eneratedThis primitive is generated by the MLME when a valid QLoad Request Public Action frame or a Protected QLoad Request Public Dual of Public Action frame is received.6.3.aa79.3.4 Effect of ReceiptOn receipt of this primitive, the SME either rejects the request or commences the transaction as de

20、scribed in 10.aa24.1.6.3.aa79.4 MLME-QLOAD.response6.3.aa79.4.1 FunctionThis primitive is used by an AP to transmit a QLoad Report to a specified AP in response to a QLoad Request.6.3.aa79.4.2 Semantics of the service primitive The primitive parameters are as follows:MLME-QLOAD .response( PeerMACAdd

21、ress(#2197) DialogTokenProtected (#2006) QLoadReport(#2199) )NameTypeValid rangeDescriptionPeerMACAddress(#2197) MACAddressAny valid individual MACAddressThe address of the peer MAC entity to which the QLoadRequest shall be sent.DialogToken Integer0255Specifies a number unique to the QLoadReport.req

22、uest primitive or 0 when sending an unsolicited reportProtectedBooleantrue, falseIf true, the response is sent using the Protected QLoad Report Protected Dual of Public Action Frame. If false, the response is sent using the QLoad Report Public Action frame.QLoadReport(#2199)Set of reports, each as d

23、efined in the QLoad Report elementSet of reports, each as defined in the QLoad Report elementSet of reports, each as defined in the QLoad Report element6.3.aa79.4.3 When GeneratedThe primitive is generated by the SME at an AP in response to the reception of a QLoad Request from the AP indicated by P

24、eerMACAddress(#2197).6.3.aa79.4.4 Effect of ReceiptOn receipt of this primitive, the MLME constructs a QLoad Report Action management frame if the Protected parameter is false, or a Protected QLoad Report Protected Dual of Public Action frame if the Protected parameter is true. The AP then attempts

25、to transmit this frame to the other AP indicated by PeerMACAddress(#2197). 6.3.aa80 HCCA TXOP Advertisement managementThese set of primitives support the process of TSPEC schedule negotiation between an AP and overlapping APs as described in 10.aa24.6.3.aa80.1 MLME-TXOPADVERTISEMENT.request6.3.aa80.

26、1.1 FunctionThis primitive is used by an AP to transmit an HCCA TXOP Advertisement to a specified AP.6.3.aa80.1.2 Semantics of the service primitive The primitive parameters are as follows:MLME-TXOPADVERTISEMENT.request( PeerMACAddress(#2197) DialogTokenProtected (#2008) ActiveTXOPReservationsPendin

27、gTXOPReservations )NameTypeValid rangeDescriptionPeerMACAddress(#2197) MACAddressAny valid individual MACAddressThe address of the peer MAC entity to which the TXOPAdvertisement shall be sent.DialogToken Integer0255Specifies a number unique to the TXOPAdvertisement.request primitive ProtectedBoolean

28、true, falseIf true, the request is sent using the Protected HCCA TXOP Advertisement Protected Dual of Public Action Frame. If false, the request is sent using the HCCA TXOP Advertisement Public Action frame.ActiveTXOPReservationsTXOP ReservationAs defined in 8.4.1.aa32Specifies the HCCA TXOPs that h

29、ave been createdPendingTXOPReservationsTXOP ReservationAs defined in 8.4.1.aa32Specifies the HCCA TXOPs that are in the process of being created.6.3.aa80.1.3 When GeneratedThe primitive is generated by the SME at an AP to request the sending of an HCCA TXOP Advertisement Public Action frame or Prote

30、cted HCCA TXOP Advertisement Protected Dual of Public Action frame to the AP indicated by PeerMACAddress(#2197).6.3.aa80.1.4 Effect of ReceiptOn receipt of this primitive, the MLME constructs a TXOP Advertisement Public Action frame if the Protected parameter is false, or constructs a Protected TXOP

31、 Advertisement Protected Dual of Public Action frame if the Protected parameter is true. The AP then attempts to transmit this frame to the AP indicated by PeerMACAddress(#2197).6.3.aa80.2 MLME-TXOPADVERTISEMENT.confirm6.3.aa80.2.1 FunctionThis primitive reports the result of a request to perform HCCA TXOP negotiation.6.3.aa80.2.2 Semantics of the service pr