This Document Updates Tgae 2.0 Clause 6.3 to Resolved Comments Received from LB 172

March 2011doc.: IEEE 802.11-11/0407r0

IEEE P802.11
Wireless LANs

LB 172 Clause 6.3 comment resolutions
Date: 2011-03-15
Author(s):
Name / Affiliation / Address / Phone / email
Michael Montemurro / Research in Motion / 4701 Tahoe Blvd, Mississauga, ON. Canada. L4W 0B4 / +1 905-629-4746 /
Stephen McCann / Research in Motion / 200 Bath Road, Slough, Berkshire, SL1 3XE, UK / +44 1753 667099 /

Overview

This document updates TGae 2.0 Clause 6.3 to resolved comments received from LB 172.

It addresses comments 1093, 1128, 1129, 1130, 1271, 1340, 1342

REV HISTORY:

R0 – initial revision

Modify the following sub-clause:

6.3 MLME SAP interface

6.3.7 Associate

6.3.7.5 MLME-ASSOCIATE.response

6.3.7.5.2 Semantics of the service primitive

Change the primitive parameter list as shown:

The primitive parameters are as follows:

MLME-ASSOCIATE.response(
PeerSTAAddress,
ResultCode,
CapabilityInformation,
AssociationID,
EDCA Parameter Set,
RCPI,
RSNI,
RMEnabledCapabilities,
Content of FT Authentication Elements,
SupportedOperatingClasses,
DSERegisteredLocation,
HTCapabilities,
Extended Capabilities,
20/40 BSS Coexistence,

TimeoutInterval,
BSSMaxIdlePeriod,
TIMBroadcastResponse,
QFM Policy,
VendorSpecificInfo

)

Insert the following new row before VendorSpecificInfo in the parameter table:

Name / Type / Valid range / Description
QFM Policy / QFM Policy element / As defined in 8.4.2.ae1 (QFM Policy element) / Indicates the QFM Policy parameters of the AP. This parameter is present when dot11QFMPolicyActivateddot11QFMActivated [1271] is true, and is not present otherwise.

6.3.8 Reassociate

6.3.8.5 MLME-REASSOCIATE.response

6.3.8.5.2 Semantics of the service primitive

Change the primitive parameter list as shown:

The primitive parameters are as follows:

MLME-REASSOCIATE.response(

PeerSTAAddress,

ResultCode,

CapabilityInformation,

AssociationID,

EDCAParameterSet,

RCPI,

RSNI,

RMEnabledCapabilities,

Content of FT Authentication Information elements,

SupportedOperatingClasses,

DSERegisteredLocation,

HT Capabilities,

Extended Capabilities,

20/40 BSS Coexistence,

TimeoutInterval,

BSSMaxIdlePeriod,

TIMBroadcastResponse,

FMSResponse,

DMSResponse,

QoSMapSet,

QFM Policy,

VendorSpecificInfo

)

Insert the following new row before VendorSpecificInfo in the parameter table:

Name / Type / Valid range / Description
QFM Policy / QFM Policy element / As defined in 8.4.2.ae1 (QFM Policy element) / Indicates the QFM Policy parameters of the AP. This parameter is present when dot11QFMPolicyActivateddot11QFMActivated [1271] is true, and is not present otherwise.

6.3.11 Start

6.3.11.2 MLME-START.request

6.3.11.2.2 Semantics of the service primitive

Change the primitive parameter list as shown:

The primitive parameters are as follows:

MLME-START.request(

SSID,

BSSType,

BeaconPeriod,

DTIMPeriod,

CF parameter set,

PHY parameter set,

IBSS parameter set,

ProbeDelay,

CapabilityInformation,

BSSBasicRateSet,

OperationalRateSet,

Country,

IBSS DFS Recovery Interval,

EDCAParameterSet,

DSERegisteredLocation,

HT Capabilities,

HT Operation,

BSSMembershipSelectorSet,

BSSBasicMCSSet,

HTOperationalMCSSet,

Extended Capabilities,

20/40 BSS Coexistence,

Overlapping BSS Scan Parameters,

MultipleBSSID,

InterworkingInfo,

AdvertisementProtocolInfo,

RoamingConsortiumInfo,

Mesh ID,

Mesh Configuration,

QFM Policy,

VendorSpecificInfo

)

Insert the following new row before VendorSpecificInfo in the parameter table:

Name / Type / Valid range / Description
QFM Policy / QFM Policy element / As defined in 8.4.2.ae1 (QFM Policy element) / This element is present when dot11QFMPolicyActivateddot11QFMActivated [1271] is true, and is not present otherwise, and is provided by the SME to signal to the MLME the QFM Policy to be used for this BSS.

Modify this sub-clause as follows:

6.3.ae1 MFQQMF Policy

6.3.ae1.1 Introduction

The following MLME primitives support the signaling of MFQQMF Policy.

6.3.ae1.2 MLME-MFQPOLICYCONFIG.request

6.3.ae1.2.1 Function

This primitive supports the signaling of MFQ Policy Configuration between peer SMEs. An SME configures the MFQ Policy within a peer SME.

6.3.ae1.2.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQPOLICYCONFIG.request (

Peer MAC Address,

Dialog Token,

MFQ Policy parameters

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the MFQ Policy Config request is sent.
Dialog Token / Integer / 1-255 / The dialog token to identify the MFQ Policy Config transaction.
MFQ Policy parameters / MFQ Policy element / As defined in 8.4.2.ae1 (MFQ Policy element) / These parameters indicate the MFQ Policy the peer is requested to use.

6.3.ae1.2.3 When generated

This primitive is generated by the SME when a STA wishes to request a change of the MFQ Policy within another STA.

6.3.ae1.2.4 Effect of receipt

On receipt of this primitive, the MLME constructs an MFQ Policy Config Request frame containing the set of MFQ Policy parameters. This frame is then scheduled for transmission.

6.3.ae1.3 MLME-MFQQMFPOLICYCONFIG.confirm

6.3.ae1.3.1 Function

This primitive reports the result of an MFQQMF Policy Configreceipt of an MFQQMF Policy frame. .

6.3.ae1.3.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQQMFPOLICYCONFIG.confirm (

Peer MAC Address,

Dialog Token,

MFQQMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the MFQQMF Policy Config request is sent.is received.
Dialog Token / Integer / 1-255 / The dialog token to identify the MFQQMF Policy Config transaction.
MFQQMF Policy parameters / MFQQMF Policy element / As defined in 8.4.2.ae1 (MFQQMF Policy element) / These parameters indicate the MFQQMF Policy the peer is requested to use.
Result Code / Enumeration / SUCCESS,
REJECTREJECT,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE,
UNSPECIFIED_FAILURE / Reports the outcome of a request to sendreceipt of anMFQQMF Policy Config Responsequest frame.

6.3.ae1.3.3 When generated

This primitive is generated when a QMF Policy Change response frame has been received from a peer entity.

generated by the MLME when the request to MFQ Policy Config transmission completes has been received..

6.3.ae1.3.4 Effect of receipt

On receipt of this primitive, the SME evaluates the result code. configures the MFQ Policy in the MAC..

6.3.ae1.4 MLME-MFQQMFPOLICYCONFIG.indication

6.3.ae1.4.1 Function

This primitive indicates that anMFQQMF Policy Config Responsequest frame has been received from a peer entity.

6.3.ae1.4.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQQMFPOLICYCONFIG.indication (

Peer MAC Address,

Dialog Token,

MFQQMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC from which the MFQQMF Policy Config responsequest was received
Dialog Token / Integer / 1-255 / The dialog token to identify the MFQQMF Policy Config transaction.
MFQQMF Policy parameters / MFQQMF Policy element / As defined in 8.4.2.ae1 (MFQQMF Policy element) / This element is optionally present.
Result Code / Enumeration / SUCCESS,
REJECT,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE,
UNSPECIFIED_FAILURE / Reports the receipt of a QMF Policy response frame.

6.3.ae1.4.3 When generated

This primitive is generated by the MLME when a valid MFQQMF Policy Change Config rResponseequest frame is received from a peer entity.

6.3.ae1.4.4 Effect of receipt

On receipt of this primitive, the MFQQMF Policy Change Config rResponsequest frame elements are provided to the SME to be processed.

6.3.ae1.5 MLME-MFQQMFPOLICYCONFIG.response

6.3.ae1.5.1 Function

This primitive requests the transmission of a MFQQMF Policy Config Response frame to a peer entity., in response to a received MFQ Policy Config Request frame. A MFQQMF Policy frame may be sent unsolicited to a peer entity, or in response to an MFQ Policy Request frame.

6.3.ae1.5.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQQMFPOLICYCONFIG.response (

Peer MAC Address,

Dialog Token,

MFQQMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the MFQQMF Policy Changeonfig responseequest is sent.
Dialog Token / Integer / 1-255 / The dialog token to identify the MFQQMF Policy Changeonfig transaction.
MFQQMF Policy parameters / MFQQMF Policy element / As defined in 8.4.2.ae1 (MFQQMF Policy element) / These parameters indicate the MFQQMF Policy the peer is requested to use.
Result Code / Enumeration / SUCCESS,
REJECT,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE,
UNSPECIFIED_FAILURE / Reports the outcome of the an MFQtransaction Policy Config Request.

6.3.ae1.5.3 When generated

This primitive is generated by the SME to request that an MFQQMF Policy Config Response frame be sent to a

peer entity to convey MFQQMF Policy information., following the configuration request from that peer entity. It may be sent unsolicited to a peer entity or in response to a MFQ Policy Request frame.

6.3.ae1.5.4 Effect of receipt

On receipt of this primitive, the MLME constructs an MFQQMF Policy Config Response frame containing the

set of MFQQMF Policy elements specified. This frame is then scheduled for transmission.

6.3.ae1.2 MLME-QMFPOLICYCHANGE.request

6.3.ae1.2.1 Function

This primitive supports the signaling of QMF Policy between peer SMEs. An SME changes the QMF Policy within a peer SME.

6.3.ae1.2.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-QMFPOLICYCHANGE.request (

Peer MAC Address,

Dialog Token,

QMF Policy parameters

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the QMF Policy Change request is sent.
Dialog Token / Integer / 1-255 / The dialog token to identify the QMF Policy Change transaction.
QMF Policy parameters / QMF Policy element / As defined in 8.4.2.ae1 (QMF Policy element) / These parameters indicate the QMF Policy the peer is requested to use.

6.3.ae1.2.3 When generated

This primitive is generated by the SME when a STA wishes to request a change of the QMF Policy within a peer entity.

6.3.ae1.2.4 Effect of receipt

On receipt of this primitive, the MLME constructs a QMF Policy Change request frame containing the set of QMF Policy parameters. This frame is then scheduled for transmission.

6.3.ae1.3 MLME-QMFPOLICYCHANGE.confirm

6.3.ae1.3.1 Function

This primitive reports the QMFreceipt of a QMF Policy frame.

6.3.ae1.3.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-QMFPOLICYCHANGE.confirm (

Peer MAC Address,

Dialog Token,

QMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the QMF Policy Change is received.
Dialog Token / Integer / 1-255 / The dialog token to identify the QMF Policy transaction.
QMF Policy parameters / QMF Policy element / As defined in 8.4.2.ae1 (QMF Policy element) / These parameters indicate the QMF Policy the peer is requested to use.
Result Code / Enumeration / SUCCESS,
REJECT,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE,
UNSPECIFIED_FAILURE / Reports the receipt of a QMF Policy Change response frame.

6.3.ae1.3.3 When generated

This primitive is generated when the QMF Policy Change has been received by the MAC.

6.3.ae1.3.4 Effect of receipt

On receipt of this primitive, the SME evaluates the result code.

6.3.ae1.4 MLME-QMFPOLICYCHANGE.indication

6.3.ae1.4.1 Function

This primitive indicates that a QMF Policy Change request frame has been received from a peer entity.

6.3.ae1.4.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-QMFPOLICYCHANGE.indication (

Peer MAC Address,

Dialog Token,

QMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC from which the QMF Policy Change request was received
Dialog Token / Integer / 1-255 / The dialog token to identify the QMF Policy Change transaction.
QMF Policy parameters / QMF Policy element / As defined in 8.4.2.ae1 (QMF Policy element) / This element is optionally present.
Result Code / Enumeration / SUCCESS,
REJECT,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE,
UNSPECIFIED_FAILURE / Reports the receipt of a QMF Policy change request frame.

6.3.ae1.4.3 When generated

This primitive is generated by the MLME when a valid QMF Policy Change Request frame is received from a peer entity.

6.3.ae1.4.4 Effect of receipt

On receipt of this primitive, the QMF Policy Change Request frame elements are provided to the SME to be processed.

6.3.ae1.5 MLME-QMFPOLICYCHANGE.response

6.3.ae1.5.1 Function

This primitive requests the transmission of a QMF Policy Change frame to a peer entity.

6.3.ae1.5.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-QMFPOLICYCHANGE.response (

Peer MAC Address,

Dialog Token,

QMF Policy parameters,

Result Code

)

Name / Type / Valid Range / Description
Peer MAC Address / MAC Address / Any valid individual MAC Address / The address of the peer MAC entity to which the QMF Policy Change response is sent.
Dialog Token / Integer / 1-255 / The dialog token to identify the QMF Policy Change transaction.
QMF Policy parameters / QMF Policy element / As defined in 8.4.2.ae1 (QMF Policy element) / These parameters indicate the QMF Policy the peer is requested to use.
Result Code / Enumeration / SUCCESS,
REJECT / Reports the outcome of the transaction.

6.3.ae1.5.3 When generated

This primitive is generated by the SME to request that a QMF Policy Change frame be sent to a peer entity to convey QMF Policy information.

6.3.ae1.5.4 Effect of receipt

On receipt of this primitive, the MLME constructs a QMF Policy frame containing the set of QMF Policy elements specified. This frame is then scheduled for transmission.

6.3.ae1.6 MLME-MFQQMFPOLICYSET.request

6.3.ae1.6.1 Function

This primitive supports the signaling of MFQQMF Policy from the SME to the MLME.

6.3.ae1.6.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQQMFPOLICYSET.request (

Peer MAC address,

MFQQMF Policy parameters

)

Name / Type / Valid Range / Description
Peer MAC Address / MACAddress / Any valid individual MAC address / The address of the STA to which the MFQQMF Policy is used for transmissions.
MFQQMF Policy parameters / MFQQMF Policy element / As defined in 8.4.2.ae1 (MFQQMF Policy element) / This element is optionally present when dot11MFQQMFPolicyActivated is true, and is not present otherwise.

6.3.ae1.6.3 When generated

This primitive is generated by the SME to request the MLME to set MFQQMF Policy information..

6.3.ae1.6.4 Effect of receipt

On receipt of this primitive, the MLME uses the supplied set of MFQQMF Policy parameters when transmitting to the peer.

6.3.ae1.7 MLME-MFQQMFPOLICYSET.confirm

6.3.ae1.7.1 Function

This primitive reports the result of an MFQQMF Policy Set request operation.

6.3.ae1.7.2 Semantics of the service primitive

The primitive parameters are as follows:

MLME-MFQQMFPOLICYSET.confirm (

Result Code,

MFQQMF Policy parameters

)

Name / Type / Valid Range / Description
Result Code / Enumeration / SUCCESS,
REJECT,
INVALID_PARAMETERS,
UNSPECIFIED_FAILURE / Reports the outcome of a request to set MFQQMF Policy.
MFQQMF Policy parameters / MFQQMF Policy element / As defined in 8.4.2.ae1 (MFQQMF Policy element) / This element is optionally present when dot11MFQQMFPolicyActivated is true, and is not present otherwise.

6.3.ae1.7.3 When generated

This primitive is generated by the MLME when the request to set MFQQMF Policy completes.

6.3.ae1.7.4 Effect of receipt

On receipt of this primitive, the SME evaluates the result code.

Modify the changes to this sub-clause as follows:

8.4.2.ae1 Management Frame QoS Policy element

(11n)

The Management Frame QoS Policy element defines access categories of management frames and is used to advertise and exchange management frame QoS policy between STAs. The use of the Mangament Frame QoS Policy element is given in clause 10.ae1. See Figure 8-4ae1 (Management Frame QoS Policy element format).

Element ID / Length / MFQQMF Policy Information / Access Category Assignment Count / List of Access Category Assignment fields (optional)
Octets: / 1 / 1 / 1 / 1 / 0-254

Figure 8-4ae1—Management Frame QoS Policy element format

The Element ID field is equal to the Management Frame QoS Policy value in Table 8-50.

The value of the length field is between 1 and 255.

The MFQQMF Policy Information field indicates properties of the MFQQMF policy. See Figure 8-4ae1a

B0 / B1 B7
MFQQMF Policy Type / Reserved

Figure 8-4ae1a — MFQQMF Policy Information Field format

The MFQQMF Policy Identifier field identifies the policy advertised by the AP. The MFQQMF Policy Type field identifies whether the MFQQMF Policy is partial or complete.

The Access Category Assignment Count field indicates the number of Access Category Assignment field(s) included in this information element.

The List of Access Category Assignment fields contains zero or more Access Category Assignment fields.(11n)

The Access Category Assignment field specifies a group of management frames and their associated access categories. See Figure 8-4ae2 (Access Category Assignment Field format).

AC Assignment Header / Category Value (optional) / Action Value Bitmap (optional)
Octets: / 2 / 1 / Variable

Figure 8-4ae2—Access Category Assignment Field format

The format of the AC Assignment Header subfield of the Access Category Assignment field is defined in Figure 8-4ae3 (AC Assignment Header subfield).

B0 B1 / B2 B7 / B8 / B9 / B10 B11 / B12 B15
Access Category Assignment Field Type / Access Category Assignment Field Length / I / G / ACI / Management Frame Subtype

Figure 8-4ae3 – AC Assignment Header subfield

The Access Category Assignment Field Type subfield is 2 bits in length and defines the structure of the Access Category Assignment field. It is set to 0. Values 1, 2, and 3 are reserved.

The Access Category Assignment Field Length subfield is 6 bits in length and defines the length in octets of the Access Category Assignment field excluding the AC Assignment Header subfield.

Modify these sub-clauses as follows:

10.ae1.2 Management frame QoS policy advertisement and configuration procedures

Management frame QoS policies are exchanged and implemented between two MFQQMF STAs. The ACI classification by transmitting STA for every MFQQMF frame is governed by the MFQQMF policy obtained from the receiving STA. The MFQQMF policy is either advertised by the receiving STA or obtained through the exchange of Policy Config Request/Response frames.

A STA shall not transmit an MFQQMF Policy element that sets I=0 and G=0 in any of the included QACM subfields.

The MFQQMF Policy that the MLME uses following an MLME-START.request or MLME-JOIN.request shall be the default MFQQMF policy, until overridden by an explicit MLME-MFQQMFPOLICYSET.request.[m1]The MLME of an MFQQMF STA shall be initially configured with the default MFQQMF policy. The SME of an MFQQMF STA may use the MLME-MFQQMFPOLICYSET primitive to configure the MLME with a non-default MFQQMF QoS policy (See 6.3.ae1.6).

The ACI classification for any management frame can be reconfigured, for example, vendor-specific and vendor-specific protected management frames may be reconfigured to suit the vendor application requirements. [m2]

There are two types of transmitted MFQQMF policy: the complete MFQQMF policy or the partial MFQQMF policy. Complete MFQQMF policy includes a transmission access category for each management frame that is not transmitted using the default MFQQMF policy access category defined in Table 10-ae1. Partial MFQQMF policy includes a transmission access category for State 1 and State 2 management frames that are not transmitted using the default MFQQMF access categories defined in Table 10-ae1.