Sept 2008doc.: IEEE 802.11-08/0894r2
IEEE P802.11
Wireless LANs
Date: 2008-09-08
Author(s):
Name / Affiliation / Address / Phone / email
Dave Stephenson / Cisco Systems, Inc. / 170 W. Tasman Dr.
San Jose, CA95134 / +1 408 527 7991 /
7.2.3Management frames
7.2.3.5Association Response frame format
Add the following contents to Table7-11 as shown below:
Table 7-11—Association Response frame body
Order / Information / NotesANA / QoS Map / QoSMap is present if dot11InterworkingServiceEnabledis true and the QoS Map bit in the Extended Capabilities element of the corresponding Association Request frame is set to 1.
7.2.3.7Reassociation Response frame format
Add the following contents to Table7-12 as shown below:
Table 7-13—Reassociation Response frame body
Order / Information / Notes<ANA> / QoS Map / QoS Map is present if dot11InterworkingServiceEnabled is true and the QoS Map bit in the Extended Capabilities element of the corresponding Reassociation Request frame is set to 1.
7.4Action frame format details
7.4.2QoS Action frame details
Change table 7-45 with table by inserting new rows as shown below.
Table 7-45—QoS action field values
Action field value / Meaning0 / ADDTS request
1 / ADDTS response
2 / DELTS
3 / Schedule
4 / QoS Map Request
54 / QoS Map Configure
65-255 / Reserved
7.4.2.5QoS Map Request frame format
The QoS Map Request frame is used by a non-AP STA to request the QoS Map Set element using the procedures defined in 11.19.1.
The frame body of the QoS Map Request frame contains the information shown in Table
Table 7-46a—QoS Map request frame body
Order / Information0 / Category
1 / Action
2 / Dialog Token
Renumber the following clause as appropriate (given that 7.4.2.5 is deleted).
The Category field is set to the value in Table 7-24 (representing QoS).
The Action field is set to the value in Table 7-45 (representing QoS Map Configure).
The Dialog Token field is set to a non-zero value chosen by the non-AP STA sending the QoS Map request to identify the request/report transaction.
7.4.2.6QoS Map Configure frame format
The QoS Map Configure is used by an AP to provide the QoS Map Set to a non-AP STA using the procedures defined in 11.19.111.19.
Table 7-57z—QoS Map configure frame body
Order / Information0 / Category
1 / Action
2 / Dialog Token
3 / QoS Map Set
The Category field is set to the value in Table 7-24 (representing QoS).The Category field is set to 1 (representing QoS).
The Action field is set to the value in Table 7-45 (representing QoS Map Configure).The Action field is set to 5 (representing QoS Map Configure).
The Dialog Token field is set to the value in the corresponding QoS Map request frame. If the QoS map configure frame is not being transmitted in response to a QoS Map request frame, then the Dialog Token is set to 0.
The QoS Map Set element is defined in 7.3.2.64.
10.Layer management
10.3MLME SAP interface
Amend the text as shown below, renumbering clauses as necessary:
10.3.40QoS Map Set element management
The QoS Map Set element is provided to non-AP STAs in (Re)-association response frames. However, if the SME of an AP detects a change of the QoS Map information while one or more non-AP STAs are associated to the BSS, then the AP’s SME may transmit an un-solicited QoS Map Set element to associated STAs. The AP’s SME invokes the MLME-QoSMap.reponse primitive to transmit individually-addressed frames containing a QoS Map Set element to associated STAs. When a non-AP STA receives such unsolicited QoS Map information, its MLME generates a MLME-QoSMap.confirm to the STA’s SME. In turn, the SME should take appropriate action, e.g., initiate an ADDTS or DELTS if admission control changes are necessary.
Four primitives enable a non-AP STA to retrieve the QoS Map Set element from an AP and make it available to the SME. Once the SME has the QoS Map Set, a higher layer protocol or application accessing the QoS Map Set in the SME, will be able to set the correct priority in a MA-UNITDATA.request primitive.
The primitives defined are: MLME-QoSMap.request, MLME-QoSMap.confirm, MLME-QoSMap.indication, MLME-QoSMap.response.
Among them, the MLME-QoSMap.response may be generated by the AP unsolicited, e.g., when the SME of the AP detects a change of the QoS Map information. When a non-AP STA receives such unsolicited QoS Map information, its SME needs to decide appropriate action, e.g., initiate an ADDTS or DELTS if admission control changes are necessary.
10.3.40.1MLME-QoSMap.request
10.3.40.1.1Function
This primitive requests the information of the QoS Map from the network. It is valid at the non-AP STA and requests the AP to provide QoS Map Set information.
10.3.40.1.2Semantics of the service primitive
The primitive parameters are as follows:
MLME-QoSMap.request (
DialogToken
Timeout
)
Dialog Token / Integer / 1 – 255 / The dialog token to identify the QoS Map Set message transaction.
Timeout / Integer / Greater than or equal to 1 / Specifies a time limit (in TU) after which the QoS Map request procedure will be terminated.
10.3.40.1.3When generated
This primitive is generated by the SME at a non-AP QoS STA to request the QoS Mapset in use within the BSS.
10.3.40.1.4Effect of receipt
The non-AP STA operates according to the procedures defined in 11.19.1.
10.3.40.2MLME-QoSMap.confirm
10.3.40.2.1Function
This primitive reports the QoS Mapping information sent from the AP to the non-AP STA. It is valid at non-AP STA.
10.3.40.2.2Semantics of the service primitive
The primitive parameters are as follows:
MLME-QoSMap.confirm(
ResultCode
DialogToken
QoS Map Set
)
ResultCode / Enumeration / SUCCESS,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE / Indicates the results of the corresponding MLMEQoSMap.request primitive.
Dialog Token / Integer / 0 - 255 / The dialog token to identify the QoS Map Set message transaction.
QoS Map Set / As defined in frame format / As defined in 7.3.2.64 / Specifies the QoS Map Set the non-AP STA should use.
10.3.40.2.3When generated
This primitive is generated by the SME as a result of an MLME-QoSMap.request primitive indicating the result of that request.
The primitive is generated when the non-AP STA receives a response in the form of a QoS Map Configure frame in the corresponding Action frame from the AP. This requires no prior MLME-QoSMap.request primitive from the non-AP STA.
The SME of the non-AP STA should use the information to decide proper actions. For example, an ADDTS or DELTS procedure should be activated if the QoS Map information indicates a change in the admission control.
10.3.40.2.4Effect of receipt
The non-AP STA operates according to the procedures defined in 11.19.1.
10.3.40.3MLME-QoSMap.indication
10.3.40.3.1Function
This primitive reports to the AP SME the request for QoS Map Set.
10.3.40.3.2Semantics of the service primitive
The primitive parameters are as follows:
MLME-QoSMap.indication (
DialogToken
Non-APSTAAddress
)
Dialog Token / Integer / 1 – 255 / The dialog token to identify the QoS Map Set message transaction.
Non-APSTAAddress / MACAddress / Any valide individual MAC address / Specifies the address of the peer MAC entity from which query message is received.
10.3.40.3.3When generated
This primitive is generated by the SME as a result of receipt of a request for the QoS Map Set from a non-AP STA in the form of a QoS Map Request in the corresponding QoS Map Action frame.
10.3.40.3.4Effect of receipt
The AP is notified of the request from the non-AP STA.
This primitive solicits an MLME-QoSMap.response primitive from the SME that contains the corresponding QoS Map information associated with the non-AP QoS STA requesting the information
The SME operates according to the procedures defined in 11.19.1.
The SME generates an MLME-QoSMap.response primitive within a dot11QoSMapResponseTimeout.
10.3.40.4MLME-QoSMap.response
10.3.40.4.1Function
This primitive is used to transmitresponds to the request for a QoS Map Setby to a specified non-AP STA MAC entity. The specified non-AP STA MAC address is an individual MAC address.
The specified non-AP STA MAC address could be a broadcast address. A QoS Map can also be sent in an unsolicited Action Frame, either to a unicast or a broadcast address,
10.3.40.4.2Semantics of the service primitive
The primitive parameters are as follows:
MLME-QoSMap.response(
ResultCode,
Non-APSTAAddress,
DialogToken,
QoS Map Set
)
ResultCode / Enumeration / SUCCESS,
INVALID_PARAMETERS,
TIMEOUT,
TRANSMISSION_FAILURE / Indicates the results of the corresponding MLMEQoSMap.request primitive.
Non-APSTAAddress / MACAddress / Any valide individual MAC address / Specifies the address of the peer MAC entity from which query message is received.
Dialog Token / Integer / 0 - 255 / The dialog token to identify the QoS Map Set message transaction.
QoS Map Set / As defined in frame format / As defined in 7.3.2.64 / Specifies the QoS Map Set the non-AP STA should use.
10.3.40.4.3When generated
This primitive is generated by the MLME at the AP as a result of an MLME-QoSMap.indication primitive, or as a result of any change in the AP QoS Map configurations.
10.3.40.4.4Effect of receipt
The primitive causes the MAC entity at the AP to send a QoS Map Configure frame in the corresponding QoS Map action management frame to the non-AP STA.
11.MLME
11.19Support for QoS Mapping from External Networks
11.19.1Interworking Procedures: Support for QoS Mapping from External Networks
Maintaining proper end-to-end QoS is an important factor when providing interworking services. This is because the external networks may employ different network-layer (Layer 3) QoS practices. For example, the use of a particular differentiated services code point (DSCP) for a given service may be different between different networks. To ensure the proper QoS over-the-air in the IEEE 802.11 infrastructure, the mapping from DSCP to UP for the corresponding network needs to be identified and made known to the non-AP STAs. If an inconsistent mapping is used then:
—Admission control at the AP may incorrectly reject a service request, because the non-AP STA used the incorrect UP.
—Non-AP STAs may use the incorrect value for User Priority in TSPEC and TCLAS elements.
—The user may be given a different QoS over the IEEE 802.11 AN network than expected, e.g., a lower QoS may be provided by the IEEE 802.11 AN than the STA expected.
Therefore, APs with dot11QosmapEnabled set to TRUE, shall set the QoSMap bit in the Extended capabilities element to 1 . The AP’s SME shall cause the QoS Map Set to be available to higher layer protocols or applications so they will be able to set the correct priority in an MA-UNITDATA.request primitive.
For frames transmitted by an AP belonging to an admitted TS, the UP obtained from the TS’s TCLAS element shall be used instead of the UP derived from the QoS Map Set. For frames transmitted by an AP belonging to an admitted TS not having a TCLAS element, the UP shall be derived from the QoS Map Set.
Therefore, a Nnon-AP STAs with dot11InterworkingServiceEnabled dot11QosmapEnabled set to TRUE, shall set the QoSMap bit in the Extended capabilities element to 1 . An AP receiving an Association request frame or Re-association request frame having this bit set to 1 shall include the QoS Map Set element in the corresponding Association response frame or Re-association response frame per 7.3.2.5 or 7.3.2.7 respectively. request the QoS Map from an AP prior to transmitting frames at other than best-effort user priority (UP = 0). The non-AP STA requests the QoS Map by transmitting a QoS Map Request Action frame to the AP to which it’s associated. In response, the AP transmits the QoS Map Set element in a QoS Map Configure Action frame. Upon receiving the QoS Map Set element, the non-AP STA’sSME shall cause the QoS Map Set to be available to higher layer protocols or applications so they will be able to set the correct priority in an MA-UNITDATA.request primitive.is then capable of deciding the proper user priority and in turn the AC to use over-the-air for a particular service. The AP shall ensure the correctness of the QoS mapping information at the non-AP STA associated to itself.
Whenever the AP detects a change in the QoS mapping information, it shall update the non-AP STA with the new QoS Map Set element. It accomplishes this update by having its SME send to the MLME an MLME-QoSMap.response primitive.
11.19.2QoS Map Distribution Operation
The QoS Map Distribution operation described below provides a method for synchronizing the QoS mapping at the STA and AP.
After the non-AP STA finishes the RSNA security procedures, its SME shall generate a MLME-QoSMap.request primitive to the MLME. The MLME of the non-AP STA shall send a QoS Map Request Action frame to the AP.
When the MAC entity at the AP receives a QoS Map Request Action frame from a non-AP STA, the MLME shall generate a MLME-QoSMap.indication primitive to its SME.
When SME of the AP receives a MLME-QoSMap.indication, it shall generate an MLME-QoSMap.response primitive. The SME of the AP can also decide to generate an unsolicited MLME-QoSMap.response primitive to the MLME based on its configuration status.
When the MLME of the AP receives a MLME-QoSMap.response, it shall send a QoS Map Configure Action frame to the corresponding non-AP STA MAC entity. QoS Map Configurate Action frames shall be transmitted to non-AP STAs using individual MAC addresses.
When the MAC entity at the non-AP STA receives a QoS Map Configure action frame from the AP, the MLME shall generate a MLME-QoSMap.confirm primitive to its SME. When the QoS Map Configure action frame is unsolicited, the non-AP STA SME can choose to generate another MLME-QoSMap.request primitive.
When the non-AP STA's SME receives the QoS Map response, it shall make the QoS Map available to higher layers so that in turn, they can invoke the MA-UNITDATA.request with the correct priority.
11.19.3Transport of QoS Map Set
Typically, the QoS Map Set is configured on an AP for each external network to which the BSS is interworked. Most of the time, the QoS Map Set remains static. In this case, the QoS Map Set shall be transmitted to the requesting non-AP STA using an individually addressed QoS Map Configure action frame.
However, it is possible that the QoS Map Set may need to be changed during operation of the BSS. If the QoS map set corresponding to a particular SSID is changed, the AP shall unicast the new QoS map set using an unsolicited QoS Map Configure Action frame to each non-AP STA associated to that SSID.
Annex T
(Informative)
Interworking with External Networks
T.1Interworking with External Networks and Emergency Call Support
T.2QoS Mapping Guidelines for Interworking with External Networks
Amend the text as shown below:
The QoS parameters mapping may be used for both uplink and downlink data transmission:.
—For uplink: At at the non-AP STA, external QoS parameters are mapped to IEEE 802.11 QoS parameters, e.g., DSCP to IEEE 802.11 User Priority (and in turn to EDCA ACs), or bandwidth QoS parameters to HCCA parameters. These This mappings helps the non-AP STA to construct correct QoS requests to the APAP, e.g., ADDTS Request and to transmit frames at the correct priority. At the AP, external QoS parameters are mapped to IEEE 802.11 QoS parameters such as EDCA ACs or UP, possibly using the QoS Map from the user's SSPN.
—For downlink: At at the AP, either 802.1p User Priority values or DSCP values are mapped to EDCA ACsUPs. Optionally, the non-AP STA can use TSPEC and TCLAS elements in an ADDTS Request frame to setup a traffic stream in the BSS. In this method, the User Priority is specified in the TCLAS element. The policy used by the AP which chooses a specific method to map frames to user priorities is outside the scope of 802.11.
As listed above, some of these mapping could be static, e.g., the 802.1p User Priority to EDCA ACs. Optionally, the non-AP STA can use TSPEC and TCLAS elements in an ADDTS mappings. And some mapping could be more flexible, e.g., the DSCP to EDCA AC mapping. Different external network may use different DSCP sets for the same services as described in T.2.2. For example, a 3GPP network may use different code points from that of a corporate network. The QoS Map distribution mechanism defined in 11.19.1 provides means to synchronize communicate to the STA’s mapping information with that available from the network.
T.2.1Determination of the mapping for a STA
Amend the text as shown below:
The QoS mapping to be applied depends upon the network the non-AP STA is accessing. In an interworking IEEE 802.11 infrastructure setting, the same physical AP may serve non-AP STAs from different SSPNs on different BSSIDs. AndAs such, these STAs may not be separated into different virtual BSSsAPs. Figure T-2 presents an example of the scenario:
Editor: this figure and its caption should be deleted.
Figure T-3—non-AP STA QoS Map determination sequence
Amend the text as shown below:
In this scenario, each BSS maps to a different VLAN on the DS. Thus, when a STA associates to a particular SSID, essentially it is connecting to a different VLAN and therefore to a different destination network or SSPN. As shown in the Figure T-3, wWhen the non-AP STA (Re)associates to an AP with a given SSID, the AP includes the QoS Map in the (Re)association request frame. Note: it is assumed that the AP is pre-configured with the information about the network information behind it, e.g., which QoS MapVLAN corresponds to which VLANDSCP Map.