Section4 Action frame format details
This subclause describes the Action frame formats, including the Action Details field, allowed in each of the action categories defined in Table 7-24 in 7.3.1.11.
7.4.1 Spectrum management action details
Five Action frame formats are defined for spectrum management. An Action Value field, in the octet field immediately after the Category field, differentiates the five formats. The Action Value field values associated with each frame format are defined in Table 7-44.
7.4.1.1 Measurement Request frame format
The Measurement Request frame uses the Action frame body format and is transmitted by a STA requesting another STA to measure one or more channels. The format of the Measurement Request frame body is shown in Figure 7-96.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 0 (representing a Measurement Request frame).
The Dialog Token field shall be set to a nonzero value chosen by the STA sending the measurement request to identify the request/report transaction.
The Measurement Request Elements field shall contain one or more of the Measurement Request elements described in 7.3.2.21. The number and length of the Measurement Request elements in a Measurement Request frame is limited by the maximum allowed MMPDU size.
7.4.1.2 Measurement Report frame format
The Measurement Report frame uses the Action frame body format and is transmitted by a STA in response to a Measurement Request frame or by a STA autonomously providing measurement information. The format of the Measurement Report frame body is shown in Figure 7-97.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 1 (representing a Measurement Report frame).
The Dialog Token field shall be set to the value in any corresponding Measurement Request frame. If the Measurement Report frame is not being transmitted in response to a Measurement Request frame, then the Dialog token shall be set to 0.
The Measurement Report Elements field shall contain one or more of the Measurement Report elements described in 7.3.2.22. The number and length of the Measurement Report elements in a Measurement Report frame is limited by the maximum allowed MMPDU size.
7.4.1.3 TPC Request frame format
The TPC Request frame uses the Action frame body format and is transmitted by a STA requesting another STA for transmit power and link margin information. The format of the TPC Request frame body is shown in Figure 7-98.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 2 (representing a TPC Request frame).
The Dialog Token field shall be set to a nonzero value chosen by the STA sending the request to identify the transaction. The TPC Request element shall be set as described in 7.3.2.17.
7.4.1.4 TPC Report frame format
The TPC Report frame uses the Action frame body format and is transmitted by a STA in response to a TPC Request frame. The format of the TPC Report frame body is shown in Figure 7-99.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 3 (representing a TPC Report frame).
The Dialog Token field shall be set to the Dialog Token value in the corresponding TPC Request frame. The TPC Report element shall be set as described 7.3.2.18.
7.4.1.5 Channel Switch Announcement frame format
The Channel Switch Announcement frame uses the Action frame body format and is transmitted by an AP in a BSS or a STA in an IBSS to advertise a channel switch. The format of the Channel Switch Announcement frame body is shown in Figure 7-100.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 4 (representing a Channel Switch Announcement frame).
The Channel Switch Announcement element shall be set as described 7.3.2.20.
7.4.2 QoS Action frame details
Several Action frame formats are defined for QoS purposes. The Action field values associated with each frame format within the QoS category are defined in Table 7-45.
7.4.2.1 ADDTS Request frame format
The ADDTS frames are used to carry TSPEC and optionally TCLAS elements to set up and maintain TSs using the procedures defined in 11.4.
The frame body of the ADDTS Request frame contains the information shown in Table 7-46.
The Category field is set to 1 (representing QoS).
The Action field is set to 0 (representing ADDTS request).
The Dialog Token, TCLAS, and TCLAS Processing fields of this frame are contained in an MLMEADDTS. request primitive that causes the frame to be sent. Some of the TSPEC parameters are contained in the MLME-ADDTS.request primitive while the other parameters (i.e., Surplus Bandwidth Allowance, Minimum Service Interval, Maximum Service Interval, and Minimum PHY Rate) are generated within the MAC.
The TSPEC element, defined in 7.3.2.30, and the optional TCLAS element, defined in 7.3.2.31, contain the QoS parameters that define the TS. The TS is identified by the TSID and Direction fields within the TSPEC element. The TCLAS element is optional at the discretion of the non-AP STA that sends the ADDTS Request frame, regardless of the setting of the access policy (EDCA or HCCA). There may be one or more TCLAS elements in the ADDTS frame. The TCLAS Processing element is present when there are more than one TCLAS element and is defined in 7.3.2.33.
7.4.2.2 ADDTS Response frame format
The ADDTS Response frame is transmitted in response to an ADDTS request frame. The frame body of the ADDTS Response frame contains the information shown in Table 7-47.
The Category field is set to 1(representing QoS).
The Action field is set to 1 (representing ADDTS response).
The Status Code field is defined in 7.3.1.9.
The Dialog Token, TS Delay, TSPEC, TCLAS, and TCLAS Processing fields in this frame are contained in an MLME-ADDTS.response primitive that causes the frame to be sent. The TS Delay information element is present in an ADDTS Response frame only if the status code is set to 47. The Schedule element, defined in 7.3.2.34, is present in an ADDTS Response frame only if the status code is set to 0 (i.e., when the TS is admitted).
7.4.2.3 DELTS frame format
The DELTS frame is used to delete a TS using the procedures defined in 11.4.7.
The frame body of a DELTS frame contains the information shown in Table 7-48.
The Category field is set to 1 (representing QoS).
The Action field is set to 2 (representing DELTS).
The TS Info field is defined in 7.3.2.30.
The Reason Code field is defined in 7.3.1.7.
A DELTS frame is used to delete a TS characterized by the TS Info field in the frame. A DELTS frame may be sent from the HC to the source STA of that TS, or vice versa, to indicate an imperative request, to which no response is required from the recipient STA.
7.4.2.4 Schedule frame format
The Schedule frame is transmitted by the HC to a non-AP STA to announce the schedule of delivery of data and polls. The frame body of the Schedule frame contains the information shown in Table 7-49.
The Category field is set to 1 (representing QoS).
The Action field is set to 3 (representing Schedule).
The Schedule element is defined in 7.3.2.34.
7.4.3 DLS Action frame details
Several Action frame formats are defined for DLS management purposes. An Action field, in the octet field immediately after the Category field, differentiates the formats. The Action field values associated with each frame format are defined in Table 7-50.
7.4.3.1 DLS Request frame format
The DLS Request frame is used to set up a direct link with a peer MAC. The frame body of the DLS Request frame contains the information shown in Table 7-51.
The Category field is set to 2 (representing DLS).
The Action field is set to 0 (representing DLS request).
The Destination MAC Address field value is the MAC address of the target destination.
The Source MAC Address field value is the MAC address of the initiating STA.
The Capability Information field value is the capability information of the originator of the request.
The DLS Timeout Value field is defined in 7.3.1.13.
The Supported Rates and Extended Supported Rates fields contain the supported rates information of the originator.
7.4.3.2 DLS Response frame format
The DLS Response frame is sent in response to a DLS Request frame. The frame body of a DLS Response frame contains the information shown in Table 7-52.
The Category field is set to 2 (representing DLS).
The Action field is set to 1 (representing DLS response).
The Status Code field is defined in 7.3.1.9.
The Destination MAC Address field value and the Source MAC Address field value are copied from the corresponding fields in the DLS Request frame.
The Capability Information field is the capability information of the target destination. This information is included only if the DLS result code corresponds to SUCCESS (DLS status code 0). The Supported Rates and Extended Supported Rates fields contain the supported rates information of the target destination. This information is included only if the DLS result code corresponds to SUCCESS (DLS
status code 0).
7.4.3.3 DLS Teardown frame format
The DLS Teardown frame is sent to terminate a direct link with a peer MAC. The frame body of the DLS
Teardown frame contains the information shown in Table 7-53.
The Category field is set to 2 (representing DLS).
The Action field is set to 2 (representing DLS teardown).
The Destination MAC Address field value is the MAC address of the target destination.
The Source MAC Address field value is the MAC address of the initiating STA.
The Reason Code field is defined in 7.3.1.7.
7.4.4 Block Ack Action frame details
The ADDBA frames are used to set up Block Ack for a specific TC or TS. The Action field values
associated with each frame format within the Block Ack category are defined in Table 7-54.
7.4.4.1 ADDBA Request frame format
An ADDBA Request frame is sent by an originator of Block Ack to another STA. The frame body of an
ADDBA Request frame contains the information shown in Table 7-55.
The Category field is set to 3 (representing Block Ack).
The Action field is set to 0 (representing ADDBA request).
The Dialog Token field is set to a nonzero value chosen by the STA.
The Block Ack Parameter Set field is defined in 7.3.1.14.
The Block Ack Timeout Value field is defined in 7.3.1.15.
The Block Ack Starting Sequence Control field is defined in 7.2.1.7.
7.4.4.2 ADDBA Response frame format
The ADDBA Response frame is sent in response to an ADDBA Request frame. The frame body of an
ADDBA Response frame contains the information shown in Table 7-56.
The Category field is set to 3 (representing Block Ack).
The Action field is set to 1 (representing ADDBA response).
The Dialog Token field value is copied from the corresponding received ADDBA Request frame.
The Status Code field is defined in 7.3.1.9.
The Block Ack Parameter Set field is defined in 7.3.1.14.
The Block Ack Timeout Value field is defined in 7.3.1.15.
7.4.4.3 DELBA frame format
The DELBA frame is sent by either the originator of the traffic or the recipient to terminate the Block Ack
participation. The frame body of a DELBA frame format contains the information shown in Table 7-57.
The Category field is set to 3 (representing DELBA).
The Action field is set to 2 (representing DELBA).
The DELBA Parameters field is defined in 7.3.1.16.
The Reason Code field is defined in 7.3.1.7.
7.4.5 Vendor-specific action details
The Vendor Specific Action frame is defined for vendor-specific signaling. The format of the Vendor
Specific Action frame is shown in Figure 7-101. An OUI, in the octet field immediately after the Category field, differentiates the vendors.
7.4.1 Spectrum management action details
Five Action frame formats are defined for spectrum management. An Action Value field, in the octet field immediately after the Category field, differentiates the five formats. The Action Value field values associated with each frame format are defined in Table 7-44.
7.4.1.1 Measurement Request frame format
The Measurement Request frame uses the Action frame body format and is transmitted by a STA requesting another STA to measure one or more channels. The format of the Measurement Request frame body is shown in Figure 7-96.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 0 (representing a Measurement Request frame).
The Dialog Token field shall be set to a nonzero value chosen by the STA sending the measurement request to identify the request/report transaction.
The Measurement Request Elements field shall contain one or more of the Measurement Request elements described in 7.3.2.21. The number and length of the Measurement Request elements in a Measurement Request frame is limited by the maximum allowed MMPDU size.
7.4.1.2 Measurement Report frame format
The Measurement Report frame uses the Action frame body format and is transmitted by a STA in response to a Measurement Request frame or by a STA autonomously providing measurement information. The format of the Measurement Report frame body is shown in Figure 7-97.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 1 (representing a Measurement Report frame).
The Dialog Token field shall be set to the value in any corresponding Measurement Request frame. If the Measurement Report frame is not being transmitted in response to a Measurement Request frame, then the Dialog token shall be set to 0.
The Measurement Report Elements field shall contain one or more of the Measurement Report elements described in 7.3.2.22. The number and length of the Measurement Report elements in a Measurement Report frame is limited by the maximum allowed MMPDU size.
7.4.1.3 TPC Request frame format
The TPC Request frame uses the Action frame body format and is transmitted by a STA requesting another STA for transmit power and link margin information. The format of the TPC Request frame body is shown in Figure 7-98.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 2 (representing a TPC Request frame).
The Dialog Token field shall be set to a nonzero value chosen by the STA sending the request to identify the transaction. The TPC Request element shall be set as described in 7.3.2.17.
7.4.1.4 TPC Report frame format
The TPC Report frame uses the Action frame body format and is transmitted by a STA in response to a TPC Request frame. The format of the TPC Report frame body is shown in Figure 7-99.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 3 (representing a TPC Report frame).
The Dialog Token field shall be set to the Dialog Token value in the corresponding TPC Request frame. The TPC Report element shall be set as described 7.3.2.18.
7.4.1.5 Channel Switch Announcement frame format
The Channel Switch Announcement frame uses the Action frame body format and is transmitted by an AP in a BSS or a STA in an IBSS to advertise a channel switch. The format of the Channel Switch Announcement frame body is shown in Figure 7-100.
The Category field shall be set to 0 (representing spectrum management).
The Action Value field shall be set to 4 (representing a Channel Switch Announcement frame).
The Channel Switch Announcement element shall be set as described 7.3.2.20.
7.4.2 QoS Action frame details
Several Action frame formats are defined for QoS purposes. The Action field values associated with each frame format within the QoS category are defined in Table 7-45.
7.4.2.1 ADDTS Request frame format
The ADDTS frames are used to carry TSPEC and optionally TCLAS elements to set up and maintain TSs using the procedures defined in 11.4.
The frame body of the ADDTS Request frame contains the information shown in Table 7-46.
The Category field is set to 1 (representing QoS).
The Action field is set to 0 (representing ADDTS request).
The Dialog Token, TCLAS, and TCLAS Processing fields of this frame are contained in an MLMEADDTS. request primitive that causes the frame to be sent. Some of the TSPEC parameters are contained in the MLME-ADDTS.request primitive while the other parameters (i.e., Surplus Bandwidth Allowance, Minimum Service Interval, Maximum Service Interval, and Minimum PHY Rate) are generated within the MAC.
The TSPEC element, defined in 7.3.2.30, and the optional TCLAS element, defined in 7.3.2.31, contain the QoS parameters that define the TS. The TS is identified by the TSID and Direction fields within the TSPEC element. The TCLAS element is optional at the discretion of the non-AP STA that sends the ADDTS Request frame, regardless of the setting of the access policy (EDCA or HCCA). There may be one or more TCLAS elements in the ADDTS frame. The TCLAS Processing element is present when there are more than one TCLAS element and is defined in 7.3.2.33.
7.4.2.2 ADDTS Response frame format
The ADDTS Response frame is transmitted in response to an ADDTS request frame. The frame body of the ADDTS Response frame contains the information shown in Table 7-47.
The Category field is set to 1(representing QoS).
The Action field is set to 1 (representing ADDTS response).
The Status Code field is defined in 7.3.1.9.
The Dialog Token, TS Delay, TSPEC, TCLAS, and TCLAS Processing fields in this frame are contained in an MLME-ADDTS.response primitive that causes the frame to be sent. The TS Delay information element is present in an ADDTS Response frame only if the status code is set to 47. The Schedule element, defined in 7.3.2.34, is present in an ADDTS Response frame only if the status code is set to 0 (i.e., when the TS is admitted).
7.4.2.3 DELTS frame format
The DELTS frame is used to delete a TS using the procedures defined in 11.4.7.
The frame body of a DELTS frame contains the information shown in Table 7-48.
The Category field is set to 1 (representing QoS).
The Action field is set to 2 (representing DELTS).
The TS Info field is defined in 7.3.2.30.
The Reason Code field is defined in 7.3.1.7.
A DELTS frame is used to delete a TS characterized by the TS Info field in the frame. A DELTS frame may be sent from the HC to the source STA of that TS, or vice versa, to indicate an imperative request, to which no response is required from the recipient STA.
7.4.2.4 Schedule frame format
The Schedule frame is transmitted by the HC to a non-AP STA to announce the schedule of delivery of data and polls. The frame body of the Schedule frame contains the information shown in Table 7-49.
The Category field is set to 1 (representing QoS).
The Action field is set to 3 (representing Schedule).
The Schedule element is defined in 7.3.2.34.
7.4.3 DLS Action frame details
Several Action frame formats are defined for DLS management purposes. An Action field, in the octet field immediately after the Category field, differentiates the formats. The Action field values associated with each frame format are defined in Table 7-50.
7.4.3.1 DLS Request frame format
The DLS Request frame is used to set up a direct link with a peer MAC. The frame body of the DLS Request frame contains the information shown in Table 7-51.
The Category field is set to 2 (representing DLS).
The Action field is set to 0 (representing DLS request).
The Destination MAC Address field value is the MAC address of the target destination.
The Source MAC Address field value is the MAC address of the initiating STA.
The Capability Information field value is the capability information of the originator of the request.
The DLS Timeout Value field is defined in 7.3.1.13.
The Supported Rates and Extended Supported Rates fields contain the supported rates information of the originator.
7.4.3.2 DLS Response frame format
The DLS Response frame is sent in response to a DLS Request frame. The frame body of a DLS Response frame contains the information shown in Table 7-52.
The Category field is set to 2 (representing DLS).
The Action field is set to 1 (representing DLS response).
The Status Code field is defined in 7.3.1.9.
The Destination MAC Address field value and the Source MAC Address field value are copied from the corresponding fields in the DLS Request frame.
The Capability Information field is the capability information of the target destination. This information is included only if the DLS result code corresponds to SUCCESS (DLS status code 0). The Supported Rates and Extended Supported Rates fields contain the supported rates information of the target destination. This information is included only if the DLS result code corresponds to SUCCESS (DLS
status code 0).
7.4.3.3 DLS Teardown frame format
The DLS Teardown frame is sent to terminate a direct link with a peer MAC. The frame body of the DLS
Teardown frame contains the information shown in Table 7-53.
The Category field is set to 2 (representing DLS).
The Action field is set to 2 (representing DLS teardown).
The Destination MAC Address field value is the MAC address of the target destination.
The Source MAC Address field value is the MAC address of the initiating STA.
The Reason Code field is defined in 7.3.1.7.
7.4.4 Block Ack Action frame details
The ADDBA frames are used to set up Block Ack for a specific TC or TS. The Action field values
associated with each frame format within the Block Ack category are defined in Table 7-54.
7.4.4.1 ADDBA Request frame format
An ADDBA Request frame is sent by an originator of Block Ack to another STA. The frame body of an
ADDBA Request frame contains the information shown in Table 7-55.
The Category field is set to 3 (representing Block Ack).
The Action field is set to 0 (representing ADDBA request).
The Dialog Token field is set to a nonzero value chosen by the STA.
The Block Ack Parameter Set field is defined in 7.3.1.14.
The Block Ack Timeout Value field is defined in 7.3.1.15.
The Block Ack Starting Sequence Control field is defined in 7.2.1.7.
7.4.4.2 ADDBA Response frame format
The ADDBA Response frame is sent in response to an ADDBA Request frame. The frame body of an
ADDBA Response frame contains the information shown in Table 7-56.
The Category field is set to 3 (representing Block Ack).
The Action field is set to 1 (representing ADDBA response).
The Dialog Token field value is copied from the corresponding received ADDBA Request frame.
The Status Code field is defined in 7.3.1.9.
The Block Ack Parameter Set field is defined in 7.3.1.14.
The Block Ack Timeout Value field is defined in 7.3.1.15.
7.4.4.3 DELBA frame format
The DELBA frame is sent by either the originator of the traffic or the recipient to terminate the Block Ack
participation. The frame body of a DELBA frame format contains the information shown in Table 7-57.
The Category field is set to 3 (representing DELBA).
The Action field is set to 2 (representing DELBA).
The DELBA Parameters field is defined in 7.3.1.16.
The Reason Code field is defined in 7.3.1.7.
7.4.5 Vendor-specific action details
The Vendor Specific Action frame is defined for vendor-specific signaling. The format of the Vendor
Specific Action frame is shown in Figure 7-101. An OUI, in the octet field immediately after the Category field, differentiates the vendors.
The Category field is set to the value indicating the vendor-specific category, as specified in Table 7-24.
The OUI field is a public OUI assigned by the IEEE. It is 3 octets in length. It contains the OUI of the entity that has defined the content of the particular vendor-specific action.
The Vendor Specific Content contains vendor-specific field(s). The length of the Vendor Specific Content in a Vendor Specific Action frame is limited by the maximum allowed MMPDU size.
