Doc.: IEEE 802.11-08/0441r1
IEEE P802.11
Wireless LANs
|Normative Text for D2.0 Location Services and Time Synchronization |
|Date: 2008-03-05 |
|Name |Company |Address |Phone |email |
|Allan Thomson |Cisco Systems |170 W. Tasman Drive, San Jose, |+1-408-853-5570 |allant@ |
| | |CA95134 | | |
|Brian Hart |Cisco Systems |170 W. Tasman Drive, San Jose, |+1-408-525-3346 |brianh@ |
| | |CA95134 | | |
[pic]
Wireless LAN Network Management
Overview
WLAN Network Management enables STAs to exchange information for the purpose of improving the overall performance of the wireless network. STAs use Wireless Network Management protocols to exchange operational data so that each STA is aware of the network conditions, allowing STAs to be more cognizant of the topology of the network. Wireless Network Management protocols provide a means for STAs to be aware of presence of co-located interference, and allow STAs to manage RF parameters based on network conditions.
In addition to providing information on network conditions, Wireless Network Management also provides a means to exchange location information, provide support for multiple BSSID's on the same wireless infrastructure, more efficient delivery of group addressed frames, and enable a sleep mode in which a STA can sleep for long periods of time without receiving buffered frames from the AP.
Wireless Network Management service includes:
* BSS Transition Management
* Co-located interference Reporting
* Diagnostic Reporting
* Event reporting
* Location Services
* Timing Measurement
* Maximum Multicast Rate processing
* Multicast Diagnostic reporting
* Multiple BSSIDs
* Proxy ARP
* Sleep Mode
* STA Diagnostics
* TIM Broadcast
* Traffic Filtering Service
* Traffic Generation
Location Services
Location Request and Response frames allow STAs to exchange location information with each other. Location Configuration Request and Response frames enable STAs to configure a collection of location related parameters for Location Track Notification frames. The AP can indicate that it can provide E-911 Civic or GEO Location data for its location, to support emergency services applications.
7. Timing Measurement
Time Measurement request/report pair returns accurate time information for a frame received at the responding STA.
Information Elements
Insert Element IDs to +18 into Table 26 and change the Reserved row accordingly:
|Element IDs |
|Information Element |Element ID |Length (in octets) |
|Event Request (see 7.3.2.62) | |4 to 256 |
|Event Report (see 7.3.2.63) |+1 |5 to 256 |
|Diagnostic Request (see 7.3.2.64) |+2 |4 to 256 |
|Diagnostic Report (see 7.3.2.65) |+3 |5 to 256 |
|Location Parameters (see 7.3.2.66) |+4 |2 to 256 |
|Multiple BSSID (see 7.3.2.67) |+5 |3 to 256 |
|SSID List (see 7.3.2.68) |+6 |2 to 256 |
|Multiple BSSID-Index (see 7.3.2.69) |+7 |3 to 5 |
|FBMS Descriptor (see 7.3.2.70) |+8 |3 to 256 |
|FBMS Request (see 7.3.2.71) |+9 |4 to 256 |
|FBMS Response (see 7.3.2.72) |+10 |3 to128 |
|Traffic Generation (see 7.3.2.73) |+11 |3-5 |
|BSS Max Idle Period (see 7.3.2.74) |+12 |3 |
|TFS Request (see 7.3.2.75) |+13 |5 to 256 |
|TFS Response (see 7.3.2.76) |+14 |2 to 256 |
|Sleep Mode (see 7.3.2.77) |+15 |5 |
|TIM Broadcast Request (see 7.3.2.78) |+16 |3 |
|TIM Broadcast Response (see 7.3.2.79) |+17 |10 |
|Reserved |+18, 220 | |
Measurement Request element
Change Table 29 in 7.3.2.21 and split the "Measurement Use" column into four separate entries as follows:
|Measurement Type definitions for measurement requests |
|Name |Measurement Type |Measurement Use |
|Basic Request |0 | |
|Clear Channel Assessment (CCA) request |1 |Spectrum Management |
|Receive power indication (RPI) histogram request |2 | |
|Channel load request |3 | |
|Noise histogram request |4 |Radio Resource Measurement |
|Beacon request |5 | |
|Frame request |6 | |
|STA statistics request |7 |Radio Resource Measurement and Wireless |
| | |Network Management |
|LCI request |8 |Radio Resource Measurement |
|Transmit stream/category measurement request |9 |Radio Resource Measurement and Wireless |
| | |Network Management |
|Multicast diagnostics request |10 |Wireless Network Management |
|Location Civic request |11 |Radio Resource Measurement |
|Location Identifier request |12 |Radio Resource Measurement |
|Reserved |13110-254 |N/A |
|Measurement Pause request |255 |Radio Resource Measurement and Wireless |
| | |Network Management |
12. Location Civic Request
The Measurement Request field corresponding to a Location Civic Request is shown in Figure vXXX. The response to a Location Civic Request is a Location Civic Report.
| | | | |
| |Location Subject |Location Service |Location Service |
| | |Interval Units |Interval |
|Octets: |1 |1 |2 |
Figure vXXX: Location Civic Request Format
The Location Subject field is a single octet and is defined in Table 7-29L. [ed note: this is a 11k reference]
The Location Service Interval Units field contains the units for the Location Service Interval field, as indicated in Table v24.
|Location Service Interval Units |
|Location Service Interval Units|Description |
|Value | |
|0 |Seconds |
|1 |Minutes |
|2 |Hours |
|3-255 |Reserved |
The Location Service Interval field is the time interval, expressed in the units indicated in the Location Service Interval Units field, at which the STA requests to receive Location Civic Reports. A Location Service Interval of 0 indicates that only a single Location Civic Report is requested.
13. Location Identifier Request
The Measurement Request field corresponding to a Location Identifier Request is shown in Figure vXXX. The response to a Location Identifier Request is a Location Identifier Report.
| | | | |
| |Location Subject |Location Service |Location Service |
| | |Interval Units |Interval |
|Octets: |1 |1 |2 |
Figure vXXX: Location Identifier Request
The Location Subject field is a single octet and is defined in Table 7-29L [ed note: this is a 11k reference]
The Location Service Interval Units field is defined in Table v24.
The Location Service Interval field is the time interval, expressed in the units indicated in the Location Service Interval Units field, at which the STA requests to receive Location Identifier Reports. A Location Service Interval of 0 indicates that only a single Location Identifier Report is requested.
Measurement Report element
Change Table 30 in 7.3.2.22 and split the "Measurement Use" column into four separate entries as follows:
|Measurement Type definitions for measurement reports |
|Name |Measurement Type |Measurement Use |
|Basic report |0 | |
|Clear Channel Assessment (CCA) report |1 |Spectrum Management |
|Receive power indication (RPI) histogram |2 | |
|report | | |
|Channel load report |3 | |
|Noise histogram report |4 |Radio Resource Measurement |
|Beacon report |5 | |
|Frame report |6 | |
|STA statistics report |7 |Radio Resource Measurement and Wireless |
| | |Network Management |
|LCI report |8 |Radio Resource Measurement |
|Transmit stream/category measurement report |9 |Radio Resource Measurement and Wireless |
| | |Network Management |
|Multicast diagnostics report |10 |Wireless Network Management |
|Location Civic report |11 |Radio Resource Measurement |
|Location Identifier report |12 |Radio Resource Measurement |
|Reserved |1310-255 |N/A |
11. Location Civic Report
The Location Civic Report includes the location information defined in CIVIC format for the location subject provided in the Location Civic measurement request.
| | | | | |
| |Location Accuracy |Location Accuracy |Location Accuracy |Civic Location |
| |X-estimate |Y-estimate |Z-estimate | |
|Octets: |2 |2 |2 |variable |
The Location Accuracy X-estimate field is an estimated accuracy in the X-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the X-dimension is unknown the field is set to 65535.
The Location Accuracy Y-estimate field is an estimated accuracy in the Y-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the Y-dimension is unknown the field is set to 65535.
The Location Accuracy Z-estimate field is an estimated accuracy in the Z-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the Z-dimension is unknown the field is set to 65535.
The Civic Location field is a variable octet field and the format of the data is defined in RFC 4776.
12. Location Identifier Report
The Location Identifier Report includes an indirect reference to where the location information for the location subject provided in the Location Identifier measurement request can be retrieved.
| | |
| |Public Identifier |
| |URILink |
|Octets: |variable |
The Public Identifier LinkURI field is a URI format string value, provided to comply with RFC 3693. The Public Identifier LinkURI confirms the validity of the location estimate to an external agent when a STA forwards a location estimate to that agent. The protocol used to query the infrastructure for a location report based on the Public Identifier Link is beyond the scope of this standard.
Extended Capabilities information element
Change the last paragraph of 7.3.2.27 as follows:
The Capabilities field is a bit field indicating the capabilities being advertised by the STA transmitting the information element. One octet of extended information has been defined. The format of that octet appears in Figure 7-76a (Capabilities fieldfirst octet). The length of the Capabilities field is a variable n. The Capabilities field is shown in Table 7-35a
Delete Figure 7-67a, and insert the following table at the end of 7.3.2.27 as follows:
|Capabilities field |
|Bit |Information |Notes |
| |Event |When dot11MgmtOptionEventsEnabled is set to 1, the Event bit is set to 1 to |
| | |indicate the STA supports Event processing as described in 11.20.3. When |
| | |dot11MgmtOptionEventsEnabled is set to 0, the Event bit is set to 0 to indicate |
| | |that the STA does not support this capability. |
|+1 |Diagnostics |When dot11MgmtOptionDiagnosticsEnabled is set to 1, the Diagnostics bit is set to |
| | |1 to indicate the STA supports Diagnostics as described in 11.20.4. When |
| | |dot11MgmtOptionDiagnosticsEnabled is set to 0, the Diagnostics bit is set to 0 to |
| | |indicate that the STA does not support this capability. |
|+2 |Multicast Diagnostics |When dot11MgmtOptionMulticastDiagnosticsEnabled is set to 1, the Multicast |
| | |Diagnostics bit is set to 1 to indicate the STA supports Multicast diagnostics as |
| | |described in 11.20.2. When dot11MgmtOptionMulticastDiagnosticsEnabled is set to 0,|
| | |the Multicast Diagnostics bit is set to 0 to indicate that the STA does not |
| | |support this capability. |
|+3 |Location |When dot11MgmtOptionLocationEnabled is set to 1, the Location bit field is set to |
| | |1 to indicate that the STA supports Location as described in 11.20.5. When |
| | |dot11MgmtOptionLocationEnabled is set to 0, the Location bit field is set to 0 to |
| | |indicate that the STA does not support this capability.The STA sets the Location |
| | |field to 1 when dot11MgmtOptionLocationEnabled is set to true and supports |
| | |Location as described in 11.20.5. Otherwise, the STA sets the Location field to 0.|
|+4 |FBMS |When dot11MgmtOptionFBMSEnabled is set to 1, the FBMS bit is set to 1 to indicate |
| | |the STA supports FBMS as described in 11.2.1.4a and 11.20.8. When |
| | |dot11MgmtOptionFBMSEnabled is set to 0, the FBMS bit is set to 0 to indicate the |
| | |STA does not support FBMS. |
|+5 |Proxy ARP Service |When dot11MgmtOptionProxyARPEnabled is set to 1, the Proxy ARP Service bit is set |
| | |to 1 to indicate the AP is providing proxy ARP service as described in 11.2.1.4b. |
| | |If Proxy ARP service is enabled, then the AP responds to broadcast ARP request on |
| | |behalf of the STA. When dot11MgmtOptionProxyARPEnabled is set to 0, the Proxy ARP |
| | |Service bit is set to 0 to indicate the AP is not providing proxy ARP service for |
| | |any associated STA. The Proxy ARP Service bit is set to zero by a non-AP STA. |
|+6 |Co-located Interference|When dot11MgmtOptionCLIReportingEnabled is set to 1, the Co-located Interference |
| |Reporting |Reporting bit is set to 1 to indicate the STA supports Co-located Interference |
| | |Reporting as described in 11.20.10. When dot11MgmtOptionCLIReportingEnabled is set|
| | |to 0, the Co-located Interference Reporting bit is set to 0 to indicate that the |
| | |STA does not support this capability. |
|+7 |E911 CIVIC Location |The STA sets the E911 CIVIC Location field is set to 1 when |
| | |dot11RRMCivicMeasurementEnabled dot11MgmtOptionE911CIVICLocationEnabled is set to |
| | |true and the STA has its own Civic location defined and can respond to a Location |
| | |Civic Request as described in 11.10.8.9. Otherwise, the STA sets the E911 CIVIC |
| | |Location field to 0 and sets it to 0 otherwise. The E911 CIVIC bit is set to 0 and|
| | |ignored when the Location bit is set to 0. When |
| | |dot11MgmtOptionE911CIVICLocationEnabled is set to 1, the E911 CIVIC Location bit |
| | |is set to 1 to indicate that the AP has its location defined in CIVIC format, as |
| | |described by the Location Descriptor sub-element in 7.3.2.66.10, and provides it |
| | |to the non-AP STA upon request. When dot11MgmtOptionE911CIVICLocationEnabled is |
| | |set to 0, the E911 CIVIC Location bit is set to 0 to indicate that the AP does not|
| | |have its location defined in CIVIC format or is not capable of providing CIVIC |
| | |format location to the non-AP STA upon request.The E911 CIVIC bit shall be set to |
| | |0 for a non-AP STA. |
|+8 |E911 Geo Location |The STA sets the E911 Geo Location field to 1 when dot11RRMLCIMeasurementEnabled |
| | |is set to true and the STA has its own Geo location defined and can respond to a |
| | |LCI Request as described in 11.10.8.6. Otherwise, the STA sets the E911 Geo |
| | |Location field to 0. |
| | |The E911 Geo Location field is set to 0 and reserved when the Location field is |
| | |set to 0. When dot11MgmtOptionE911GeoLocationEnabled is set to 1, the E911 Geo |
| | |Location field is set to 1 to indicate that the STA has its location defined in |
| | |Geo format and provides it upon request via the LCI Request described in |
| | |7.3.2.21.9. When dot11MgmtOptionE911GeoLocationEnabled is set to 0, the E911 Geo |
| | |Location field is set to 0 to indicate the STA does not have its location defined |
| | |in Geo format or is not capable of providing Geo format location upon requestThe |
| | |E911 Geo bit is set to 0 and ignored when the Location bit is set to 0. When |
| | |dot11MgmtOptionE911GeoLocationEnabled is set to 1, the E911 Geo Location bit is |
| | |set to 1 to indicate that the STA supports that the AP has its location defined in|
| | |Geo format, as described by the Location Descriptor sub-element in 7.3.2.66.10 |
| | |and provides it to the non-AP STA upon request. When |
| | |dot11MgmtOptionE911GeoLocationEnabled is set to 0, the E911 Geo Location bit is |
| | |set to 0 to indicate the AP does not have its location defined in Geo format or is|
| | |not capable of providing Geo format location to the non-AP STA upon request. The |
| | |E911 Geo bit shall be set to zero for a non-AP STA. |
|+9 |TFS |When dot11MgmtOptionTFSEnabled is set to 1, the TFS bit is set to 1 to indicate |
| | |that the STA supports TFS as described in 11.20.11. When dot11MgmtOptionTFSEnabled|
| | |is set to 0, the TFS bit is set to 0 to indicate that the STA does not support |
| | |TFS. |
|+10 |Sleep Mode |When dot11MgmtOptionSleepModeImplemented is set to 1, the Sleep Mode bit is set to|
| | |1 to indicate that the STA supports sleep mode as described in 11.20.12. When |
| | |dot11MgmtOptionSleepModeImplemented is set to 0, the Sleep Mode bit is set to 0 to|
| | |indicate that the STA does not support sleep mode. |
|+11 |TIM Broadcast |When dot11MgmtOptionTIMBroadcastEnabled is set to 1, the TIM Broadcast bit is set |
| | |to 1 to indicate that the STA supports TIM Broadcast as described in 11.2.1.11a. |
| | |When dot11MgmtOptionTIMBroadcastEnabled is set to 0, the TIM Broadcast bit is set |
| | |to 0 to indicate that the STA does not support TIM Broadcast. |
|+12 |BSS Transition |When dot11MgmtOptionBSSTransitionEnabled is set to 1, the BSS Transition bit is |
| | |set to 1 to indicate that the STA supports BSS Transition Management as described |
| | |in 11.20.8. When dot11MgmtOptionBSSTransitionEnabled is set to 0, the BSS |
| | |Transition bit is set to 0 to indicates that the STA does not support BSS |
| | |Transition Management. |
|+13 |Traffic Generation |When dot11MgmtOptionTrafficGenerationEnabled is set to 1, the Traffic Generation |
| | |bit is set to 1 to indicate the STA supports Traffic Generation as described in |
| | |11.20.11. When dot11MgmtOptionTrafficGenerationEnabled is set to 0, the Traffic |
| | |Generation bit is set to 0 to indicate that the STA does not support this |
| | |capability. |
|+14 |AC Station Count |When dot11MgmtOptionACStationCountEnabled is set to1, the AC Station Count bit is |
| | |set to 1 to indicate the STA supports AC Station Count as described in 11.20.12. |
| | |When dot11MgmtOptionACStationCountEnabled is set to 0, the AC Station Count bit is|
| | |set to 0 to indicate that the STA does not support this capability. |
|+15 |Timing e Measurement |When dot11MgmtOptionTimingMsmtEnabled is set to true, the Time Measurement field |
| | |is set to 1 to indicate the STA supports Time Measurement as described in |
| | |11.20.5.5XXXX. When dot11MgmtOptionTimingMsmtEnabled is set to 0, the Timinge |
| | |Measurement field is set to 0 to indicate that the STA does not support this |
| | |capability |
|+165-n*8 |Reserved |All other bits are reserved, and are set to 0 on transmission and ignored on |
| | |reception. |
Location Parameters element
Location Parameters definition
The Location Parameters information element is used for location services. The format of this information element is shown in Figure v42.
| | | | |
| |Element ID |Length |Location Sub-elements |
|Octets: |1 |1 |variable |
|Location Parameters Information element format |
The Element ID field is equal to the Location Parameters value in Table 7-26.
The value of the Length field is variable and depends on the length of the Location Sub-elements field.
The Location Sub-elements field contains one or more Location sub-elements described in Table v19.
|Location Sub-elements |
|Identifier |Sub-element Name |Sub-element Length (in |
| | |octets) |
|1 |Location Indication Parameters (see 7.3.2.66.2) |10 |
|2 |Location Indication Channels (see 7.3.2.66.3) |4 to 254 |
|3 |Location Request Options (see 7.3.2.66.4) |4 |
|34 |Location Status (see 7.3.2.66.5 [correct ref]) |43 |
|5 |Location Service Parameters (see 7.3.2.66.6) |5 |
|46 |Radio Information (see 7.3.2.66.7 [correct ref]) |7 |
|7 |Timing Measurements (see 7.3.2.66.8) |8 to 20 |
|58 |Motion (see 7.3.2.66.9 [correct ref]) |5 |
|9 |Location Descriptor (see 7.3.2.66.10) |5 |
|10 |Location Data (see 7.3.2.66.11) |3 to 254 |
|11 |Location Source Identifier (see 7.3.2.66.12) |9 to 254 |
|612 |Location Indication Broadcast Data Rate (see 7.3.2.66.13 |4 |
| |[correct ref]) | |
|7 |Time Of Departure (see [add ref]) |7 |
|813-220 |Reserved | |
|221 |Vendor Specific (see 7.3.2.66.14 [correct ref])) |5 to 254 |
|222-255 |Reserved | |
The Location Parameters element is included in Location Beacon frames, as described in 7.2.3.1, Probe Response frames, as described in 7.2.3.9, Association Request frames, as described in 7.2.3.4, and Reassociation Request frames, as described in 7.2.3.6, Location Request frames, as described in 7.4.11.5, Location Response frames, as described in 7.4.11.6, Location Configuration Request frames, as described in 7.4.11.7, Location Configuration Response frames, as described in 7.4.11.8, Location Track Notification frames, as described in 7.4.XX.. The use of the Location Parameters element and frames is described in 11.20.5.
Of the Location sub-elements listed in Table v19, Table v20 below lists the sub-elements that are excluded from the Location Parameters information element when the Location Parameters information element is sent as part of a Beacon or Probe Response frame.
|Sub-elements excluded in Beacon or Probe Response |
|frames |
|Identifier |Sub-Element Name |
|4 |Location Status |
|8 |Motion |
Location Indication Parameters sub-element
The Location Indication Parameters sub-element contains STA Location reporting characteristics. The format of the Location Indication Parameters sub-element is shown in Figure v43.
| | | | | | |
| |Sub-element ID |Length |Indication Multicast Address |Report Interval Units |Normal Report |
| | | | | |Interval |
|Octets: |1 |1 |6 |1 |2 |
| | | | | | | |
| |Normal Number of Frames |In-Motion Report |In-Motion Number of Frames |Burst Inter-frame |Tracking Duration |
| |per Channel |Interval |per Channel |Interval | |
|Octets: |1 |2 |1 |1 |1 |
|Location Indication Parameters sub-element | | | | | |
The Sub-element ID field contains the value for Location Indication Parameters as defined in Table v19.
The Length field is set to 17.68.
The Indication Multicast Address field specifies the destination address the Location Track Notification frames are sent to in a non-IBSS network. The value of this field is a locally administered multicast address formed from a random number generated according to the procedure defined in 11.20.5.3. The field is reserved when Location Track Notifications are transmitted in an IBSS.
The Report Interval Units field contains the units used for the Normal Report Interval field and In-Motion Report Interval field, as indicated in Table v21.
|Report Interval Units Field |
|Report Interval Units |Description |
|0 |Milliseconds |
|1 |Seconds |
|2 |Minutes |
|3 |Hours |
|4 - 255 |Reserved |
The Normal Report Interval is the time interval, expressed in the units indicated in the Report Interval Units field at which the STA reports or is expected to report its Location by sending a transmit one or more Location Request Track Notification frames. The STA will not report its locationtransmit Location Track Notifications when the Normal Report Interval is set to 0. The minimum Normal Report Interval is 500mSecs.
The Normal Number of Frames per Channel is the number of Location Request Track Notification frames per channel sent or expected to be sent by the STA at each Normal Report Interval.
The In-Motion Report Interval is the time interval, expressed in the units indicated in the Report Interval Units field at which the STA reports or is expected to reports its location by sending a Location Request Track Notification frame when the STA is in motion. If motion detection is not supported, this field is set to 0. The minimum In-Motion Report Interval is 500mSecs. The definition of motion and the means to determine motion are outside the scope of this standard.
The In-Motion Number of Frames per Channel is the number of Location Response Track Notification frames per channel sent or expected to be sent by the STA at each In-Motion Report Interval. If motion detection is not supporteddot11MgmtOptionMotionDetectionEnabled is false, this field is set to 0.
The Burst Inter-frame Interval is the target time interval, expressed in milliseconds between the transmissions of each of the Normal or In-Motion frames per on the same channel. The Burst Inter-frame interval value is set to 0 to indicate that frames will be transmitted with no fixed target inter-frame delay.
The Tracking Duration is the amount of time, in minutes, that a STA sends the Location Track Notification frames until the duration is reached. The duration starts as soon as the STA sends a Configuration Location Response frame with a Location Status value of Success. If the Tracking Duration is non-zero value the STA will send Location Track Notification Frames, based on the Normal and In-Motion Report Interval field values, until the duration ends. If the Tracking Duration is 0 the STA will continuously send Location Track Notification frames as defined by Normal and In-Motion Report Interval field values until transmission is terminated based on 11.20.5.3 procedures.
Location Indication Channels sub-element
The Location Indication Channels sub-element contains location reporting channel information. The format of the Location Indication Channels sub-element format is shown in Figure v44.
| | | | | | | |
| |Sub-element ID |Length |Regulatory |Channel 1 |…Regulatory |Channel n |
| | | |Class 1 | |Class n | |
|Octets: |1 |1 |1 |1 |1 |1 |
|Location Reporting Channels sub-element |
The Sub-element ID field contains the value for Location Indication Channels as defined in Table v19.
The Length field is set to 2 *twice the number of channels.
The Regulatory Class 1 through Regulatory Class n-n fields each indicates the frequency band for on which the measurement request appliesa STA transmits Location Track Notification frames. Valid values of the Regulatory Class field are defined in Annex J.
The Channel 1 through Channel n-n fields each includes the channel numbers on which a STA sends or an ESS expects to receive location Location Track Notification frames. Valid values of the Channel field are defined in Annex J.
Location Request Options sub-element
The Location Request Options sub-element indicates the sub-elements that are to be included in the subsequent Location Response frame. The format of the Location Request Options sub-element is shown in Figure v45.
| | | | |
| |Sub-element ID |Length |Options |
|Octets: |1 |1 |2 |
|Location Request Options sub-element |
The Sub-element ID field contains the value for Location Request Options as defined in Table v19.
The Length field is set to 2.
The options field is used to identify the desired Location Parameter sub-elements to be included in a subsequent Location Response frame. A value of 1 for a given bit indicates that the sub-element is to be included and a value of 0 indicates that the sub-element needs not be included. All reserved values are set to 0. Table v22 shows the available options.
|Location Request Option Bit description |
|Bit |Included Sub-element |
|0 |Timing Measurements |
|1 |Radio Information |
|2 |Motion |
|3 |Timing Offset Measurement |
|4-15 |Reserved |
7.3.2.66.4 Location Status sub-element
The Location Status sub-element provides the result of a Location Request or Location Configuration Request frame. The format of the Location Status sub-element is shown in Figure v46.
| | | | | |
| |Sub-element ID |Length |Config Sub-Element |Status |
| | | |ID | |
|Octets: |1 |1 |1 |1 |
|Location Status sub-element | | | |
The Sub-element ID field contains the value for Location Status as defined in Table v19.
The Length field is set to 21.
The Config Sub-Element ID field is set to a specific Location Parameters sub-element ID transmitted in a Location Configuration Request frame as defined in Table v19. If the Status field value applies to more than one sub-elements then the Config Sub-Element ID is set to 0. If the Status field value applies to one sub-element, then the Location Status sub-element may be included in the Location Configuration Response for each configuration sub-element that has a non-Success Status value.
The Status field identifies the result of the Location Request frame and is one of the values in Table v5.
Location Service Parameters sub-element
The Location Service Parameters sub-element describes the capabilities an AP STA provides to a non-AP STA. The format of the Location Service Parameters sub-element is shown in Figure v47.
| | | | | | | |
| |Sub-element ID |Length |Location Service |Location Service |Location Service |Location Service |
| | | |Token |State |Interval Units |Interval |
|Octets: |1 |1 |1 |1 |1 |2 |
|Location Service Parameters sub-element |
The Sub-element ID field contains the value for Location Service Parameters as defined in Table v19.
The Length field is set to 4.
The Location Service Token field contains a unique identifier for the Location Service associated with a unique service interval. If this is a new request then the Location Service Token value is set to 0. Otherwise, the Location Service Token value is set to the value assigned by the AP. The Location Service Token is fixed for the lifetime of the service on the AP.
The Location Service State field defines whether the STA is requesting location services to start or end. The values are defined in Table v23.
|Location Service State Field |
|State Value |Description |
|0 |Stop |
|1 |Start |
|2-255 |Reserved |
The Location Service Interval Units field contains the units for the Location Service Interval field, as indicated in Table v28.
|Location Service Interval Units |
|Location Service Interval Units|Description |
|Value | |
|0 |Seconds |
|1 |Minutes |
|2 |Hours |
|3-255 |Reserved |
7.3.2.66.5
The Location Service Interval field is the time interval, expressed in the units indicated in the Location Service Interval Units field, at which the STA requests to receive location data.
Radio Information sub-element
The Radio Information sub-element contains radio information. The format of the Radio Information sub-element is shown in Figure v48.
| |
The Sub-element ID field contains the value for Radio Information as defined in Table v19.
The Length field is set to 5.
The Transmit Power field is set to the transmit power used to transmit the current Location Request Track Notification frame containing the Location Parameters element with the Radio Information sub-element and is a signed integer, one octet in length, reported in dBm. A value of -128 indicates that the transmit power is unknown. The maximum tolerance for the transmit power value reported in the Radio Information sub-element is ± 5 dB. This tolerance is defined as the difference, in decibels, between the reported power value and the total transmitted power across all antennas of the STA which are measured when transmitting Location Request frames.
The Antenna ID field is the identifying number for the antenna used to transmit the Location Request frame. The Antenna ID is defined in 7.3.2.40.
Antenna ID is defined in 7.3.2.40 of TGk D9.0.
The Antenna Gain field is the antenna gain of the antenna (or group of antennas) over which the Location Request Track Notification frame is transmitted and is a signed integer, one octet in length reported in dBi. A value of -128 indicates that the antenna gain is unknown.
The Received RSNI field contains the RSNI value (dB) measured against the most recently received Location Request Configuration Request frame requesting that a Radio Information sub-element be included in the Location Response Track Notification frame. The RSNI value is defined in 7.3.2.41. A value of -128255 indicates that the RSNI value is unknown or is not used.
The RCPI field contains the RCPI value (dBm) measured against the most recently received d Location Configuration Request frame requesting that a Radio Information sub-element be included in the Location Response Track Notification frame. The RCPI value is defined 7.3.2.39. A value of -128 255 indicates that the RCPI value is unknown or is not used.
Timing Measurements sub-element
The Timing Measurements sub-element contains timing information. The format of the Timing Measurements sub-element is shown in Figure v49.
| | | | | | | |
| |Sub-element ID |Length |Timestamp |Timestamp |Timestamp |Ingress Timestamp|
| | | |Difference |Difference Units |Difference |(optional) |
| | | | | |Accuracy | |
|Octets: |1 |1 |4 |1 |1 |10 |
|Timing Measurements sub-element |
The Sub-element ID field contains the value for Timing Measurements as defined in Table v19.
The Length field is set to 6 or 16.
The Timestamp Difference field contains the time difference between the time that an individually addressed Location Request frame was received from a STA, defined to occur at the PHY-RXEND.indication of the received Location Request frame, and the time that the corresponding ACK frame was sent to the STA, defined to occur at the PHY-TXEND.confirm of the ACK frame transmission.
The Timestamp Difference Units field contains the units for the timestamp difference field, as indicated in Table v25.
|Timestamp Difference Units |
|Timestamp Difference Units |Description |
|0 |Microseconds |
|1 |Hundreds of Nanoseconds |
|2 |Tens of Nanoseconds |
|3 |Nanoseconds |
|4 - 255 |Reserved |
The Timestamp Difference Accuracy field contains the expected standard deviation of the timestamp difference of the timestamp in the units indicated in the Timestamp Difference Units field.
The Ingress Timestamp field contains the time at which the individually addressed Location Request frame was received by a STA, defined to occur at the PHY-RXEND.indication of the received Location Request frame. The Ingress Timestamp field is composed of the time fields defined in Table v26. The Ingress Timestamp field is present when the Options field in the Location Requst Option sub-element is set to the value of Timing Offset Measurement, as defined in 7.3.2.66.4.
|Ingress Timestamp Field |
|Octets |Type |Description |
|6 |Unsigned Integer |Seconds |
|4 |Unsigned Integer |Nanoseconds |
6. The Ingress Timestamp field is captured from a monotonically increasing free-running counter and is provided to higher layers in the STA which can compute its offset to the time of another STA.
7. Motion sub-element
The Motion sub-element contains motion information. The format of the Motion sub-element is shown in Figure v50.
| | | | | | | | |
The Sub-element ID field contains the value for Motion as defined in Table v19.
The Length field is set to 86.
The Motion Indicator field is defined in Table v30in Table v28. The mechanism that a STA uses to determine the value of the Motion Indicator field is beyond the scope of the standard.
|Table v30 – Motion Indicator Field |
|Motion Indicator Value |Description |
|0 |Stationary |
|1 |Start of motion |
|2 |In motion |
|3 |End of motion |
|4 |Unknown |
|5-255 |Reserved |
The Bearing field, defined by a 2 octet unsigned integer, specifies the direction that the STA is traveling with relation to true north, increasing clockwise, measured in degrees from 01 degree to 35960 degrees. If the Bearing value is unknown, the field is set to 655350.
The Speed Units field contains the units for both Horizontal and Vertical the Speed field, as defined in Table v27.
|Speed Units |
|Speed Units Value |Description |
|0 |centimeters per second |
|1 | meters per second |
|2-255 |Reserved |
The Horizontal Speed field contains the horizontal speed of the STA expressed in the units indicated in the Speed Units field. If the Horizontal Speed value is unknown, the field is set to 655350.
The Vertical Speed field contains the vertical speed of the STA expressed in the units indicated in the Speed Units field. If the Vertical Speed value is unknown, the field is set to 65535.
Location Descriptor sub-element
The Location Descriptor sub-element describes the content of the Location Data element either being requested or received by a STA. The format of the Location Descriptor sub-element is shown in Figure v51.
| | | | | | |
| |Sub-element ID |Length |Location |Location |Encoding |
| | | |Descriptor |Resolution |Descriptor |
| | | | |Descriptor | |
|Octets: |1 |1 |1 |1 |1 |
|Location Descriptor sub-element |
The Sub-element ID field contains the value for Location Descriptor as defined in Table v19.
The Length field is set to 3.
In a Location Request frame, the Location Descriptor field indicates whether the STA is requesting the Local Location or Remote Location, as shown in Table v28.
In a Location Response frame, the Location Descriptor field indicates whether the response includes the Location Estimate element of the sender or the receiver of the Location Response frame.
|Location Descriptor Bits 0-3 Description |
|Descriptor (Bits 0-3) |Description |
|0 |Local Location: location of itself |
|1 |Remote Location: location of the peer of the |
| |link |
|2-15 |Reserved |
Bits 4-7 of the Location Descriptor field indicate the format of the Location Data either being requested or sent in a Location response frame, as indicated in Table v29.
|Location Descriptor Bits 4-7 Description |
|Format |Description |
|0 |CIVIC |
|1 |GEO |
|2 |CIVIC Preferred |
|3 |GEO Preferred |
|4 |Not Supported |
|5 |Vendor Specific |
|6-15 |Reserved |
GEO and CIVIC formats and usage rules are defined in IETF RFC 4119. Usage rules for the receiver of the location information are defined by RFC 4119 and RFC 3693.
The Location Resolution Descriptor field has two subfields that indicate the location resolution and the accuracy being requested or sent in a response, as indicated in Table v30 and Table v31. Bits 5-7 are reserved bits.
|Location Resolution Descriptor (Bits 0-3) |
|Resolution (Bits 0 –|Description |Notes |
|3) | | |
|0 |Highest possible |Defines the most accurate level of location resolution possible |
| | |and may be one of the followings. |
|1 |Building resolution |The location resolution is capable of identifying the building. |
|2 |AP resolution |The location resolution is capable of identifying the AP |
| | |associated to. |
|3 |XY resolution |The location resolution is capable of identifying a particular XY|
| | |position within the location datum use. |
|4-15 |Reserved | |
|Accuracy Bit |
|Accuracy (Bit 4) |Description |
|0 |No accuracy estimate |
|1 |Include accuracy estimate |
The Encoding Descriptor field indicates the Location Data encoding, as indicated in Table v32.
|Location Encoding Descriptor |
|Encoding Value |Description |
|0 |LCI |
|1 |Text |
|2 |ASN.1 |
|3-255 |Reserved |
The value of 0 indicates that the location data object is defined by the binary format described in RFC 3825. The value of 1 indicates that the location data object is defined in plain-text XML as defined by the schema in RFC 4119. A value of 2 indicates that the location data object is defined in an ASN.1 encoding, per X.694.
Location Data sub-element
The Location Data sub-element provides the requested location data. The format of the Location Data sub-element is shown in Figure v52.
| | | | | | | |
| |Sub-element ID |Length |Location Accuracy|Location Accuracy|Location Accuracy|Location Value |
| | | |X-estimate |Y-estimate |Z-estimate | |
|Octets: |1 |1 |2 |2 |2 |variable |
|Location Data sub-element |
The Sub-element ID field contains the value for Location Data as defined in Table v19.
The value of the Length field is variable.
The Location Accuracy X-estimate field is an estimated accuracy in the X-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the X-dimension is unknown the field is set to 0.
The Location Accuracy Y-estimate field is an estimated accuracy in the Y-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the Y-dimension is unknown the field is set to 0.
The Location Accuracy Z-estimate field is an estimated accuracy in the Z-dimension in 0.1 meter increments, defined by a little endian 16 bit unsigned integer. For example, an accuracy estimate of +/- 5 meters is represented by the number X'32'. If the location accuracy estimate in the Z-dimension is unknown the field is set to 0.
The Location Value field contains the location data that matches the format defined by the Location Descriptor sub-element in 7.3.2.66.10.
Location Source Identifier sub-element
The Location Source Identifier sub-element provides the Location Source Identifier. The format of the sub-element is shown in Figure v53.
| | | | | | |
| |Sub-element ID |Length |Time zone Offset |Location Timestamp |Public Identifier |
| | | | | |Link |
|Octets: |1 |1 |1 |6 |variable |
|Location Source Identifier sub-element |
The Sub-element ID field contains the value for Location Source Identifier as defined in Table v19.
The value of the Length field is variable.
The Time zone Offset field is the Coordinated Universal Time (UTC) offset, specified in hours, that the location timestamp is specified with respect to. The default Time zone Offset value is 0 (UTC).
The Location timestamp field is the time that the location value was determined, as specified by the UTC fields shown in Table v33.
|Timestamp Field |
|Octet |Description |
|0 - 2 |Milliseconds (0-999) |
|3 |Seconds (0-59) |
|4 |Minutes (0-59) |
|5 |Hours (0-23) |
8. A STA that is incapable of providing time sets the Time zone and Timestamp field to 0.
9. The Public Identifier Link field is a string value, provided to comply with RFC 3693. The Public Identifier Link confirms the validity of the location estimate to an external agent when a STA forwards a location estimate to that agent. The protocol used to query the infrastructure for a location report based on the Public Identifier Link is beyond the scope of this standard.
10. Location Indication Broadcast Data Rate sub-element
The Location Indication Broadcast Data Rate sub-element contains location reporting transmission rate information. The format of the Location Indication Broadcast Data Rate sub-element format is shown in Figure v54.
| | | | |
| |Sub-element ID |Length |Broadcast Target Data Rate |
|Octets: |1 |1 |2 |
|Location Indication Broadcast Data Rate sub-element |
The Sub-element ID field contains the value for Location Indication Broadcast Data Rate as defined in Table v19.
The value of the Length field is set to 2.
The Broadcast Target Data Rate field specifies the target data rate, in 0.5Mb/s units, at which the STA will transmits broadcast Location Track Notificationlocation frames.
11. Time Of Departure sub-element
The Time Of Departure sub-element contains time of departure information for the Location Track Notification frame including the sub-element. The format of the Time Of Departure sub-element format is shown in Figure vXXXXX.
| | | | | | |
The Sub-element ID field contains the value for Time Of Departure as defined in Table v19.
The value of the Length field is set to 7.
The TOD Timestamp field specifies the value of the TOD timestamp counter at a constant interval before the frame carrying the TOD timestamp is transmitted in units specified by the TOD Units field.
The TOD Tolerance field specifies 95% tolerance of the TOD Timestamp field value.
The TOD Units field specifies the units for the TOD Timestamp field and may be one of the following values defined in Table XXX below:
|TOD Units |
|TOD Units Value |Description |
|0 |TODU 22: 1 / 1408 MHz |
|1 |TODU 20: 1 / 1280 MHz |
|2 |TODU40: 1 / 2560 MHz |
|3 |TODU16: 1 / 1000 MHz |
|43-255 |Reserved |
Vendor Specific Information sub-element
The Vendor Specific information sub-element contains vendor specific information. The format of the Vendor Specific sub-element is shown in Figure v55. The first 3 octets of the field contain the OUI of the entity that has defined the content of the sub-element. The length of the Vendor Specific information sub-element (n) is 3 < n < 255. The OUI field is a public OUI assigned by the IEEE. It is 3 octets in length. The length of the vendor-specific content is n–3 octets.
| | | | | |
| |Sub-element ID |Length |OUI |Vendor Specific |
| | | | |content |
|Octets: |1 |1 |3 |n-3 |
|Vendor Specific Information sub-element |
The Sub-element ID field contains the value for Vendor Specific information as defined in Table v19.
The value of the Length field is variable.
Multiple Vendor Specific information sub-elements may appear in a single frame. Each Vendor Specific information sub-element can have a different OUI value. The number of Vendor Specific information sub-elements that may appear in the information element is limited only by the maximum information element size.
Action frame format details
7.4.7 Public Action frame details
7.4.7.1 Public Action frames
Insert the following row to Table 7-57e:
|Table 7-57e – Public Action field values |
|Action field value |Description |
|9 |Location Track Notification |
|10 |Timing Measurement |
|11-255 |Reserved |
Insert the following section after 7.4.7.9:
10. Location Track Notification frame format
The Location Track Notification frame uses the Action frame body format and is transmitted by a STA to allow remote location determination to occur by another STA. The format of the Location Track Notification frame body is shown in Figure vXX.
| | | | |
| |Category |Action |Location Parameters Element |
|Octets: |1 |1 |variable |
| | |Figure vXX: Location Track Notification frame format | |
The Category field is set to the value for Public Action defined Table 7-24.
The Action field is set to the value indicating Location Track Notification, as specified in Table 7-57e.
The Location Parameters Element field contains the Location Parameters sub-elements, described in 7.3.2.66. Table vXX defines the allowed Location Parameters sub-elements for a Location Parameters element that is included in the frame.
|Table vXX - Location Parameters Element field for Location Track Notification frame |
|Allowed Sub-elements |Sub-element ID |Notes |
|Radio Information |6 |The Radio Information sub-element is included in the |
| | |Location Track Notification frame. |
|Motion |8 |The Motion sub-element is included in the Location Track |
| | |Notification frame if dot11MgmtOptionMotionEnabled is true.|
|Time Of Departure |7 |The Time Of Departure sub-element is included in the |
| | |Location Track Notification frame and |
| | |dot11MgmtOptionTODEnabled is true. |
|Vendor Specific |221 |The Vendor Specific sub-element may be included in the |
| | |Location Track Notification frame. |
7.4.7.11 Timing Measurement frame format
The Timing Measurement frame uses the Action frame body format and is used to exchange timing measurement related data between two STAs. The format of the frame is shown in Figure vXXX.
| |
| Bit PositionFrame Use Mode |Description |
|0 |=0: The Timing Measurement is |
| |an Initial (Follow On to Dialog Token is zero) or |
| |a Follow On frame (the frame is transmitted by the STA |
| |that transmitted the Initial frame. |
| |=1: The Timing Measurement public action frame is a follow|
| |on frame. This means that the frame is transmitted by the |
| |peer STA to which the corresponding Initial Timing |
| |Measurement public action frame was sent. |
|1-7 |The Timing Measurement public action frame is a Response |
| |frame. This means that the frame is transmitted by the |
| |peer STA to which the corresponding Initial Timing |
| |Measurement public action frame was sent.Reserved |
|Bits 1-7 Frame Use Mode/Timestamp Difference Units |
|Timestamp Difference Units |Description |
|0 |Microseconds |
|1 |Hundreds of Nanoseconds |
|2 |Tens of Nanoseconds |
|3 |Nanoseconds |
|4 – 126 |Reserved |
|127 |TimestampDifference Unit unspecified |
The Timestamp Difference Accuracy and the Timestamp Accuracy fields contain the standard deviation of the value in the Timestamp Difference and Timestamp fields respectively in the units indicated in the Timestamp Difference Units field.
The Timestamp field contains the time at which the first data symbol corresponding to an individually addressed Timing Measurement public action frame was
a) transmitted by a STA, defined to occur at the PHY-TXSTART.confirm or
b) received by the STA, defined to occur at the PHY-RXSTART.indication
of the Timing Measurement public action frame. The Timestamp field is composed of the time fields defined in Table v26..The Timestamp Difference and TimeStamp Difference Accuracy fields are ignored if the Timestamp Difference Units is set to 255.
The Timestamp field contains the time at which an individually addressed Timing Measurement public action frame was transmitted by a STA, defined to occur at the PHY-TXSTART.confirm of the Timing Measurement public action frame. The Timestamp field is composed of the time fields defined in Table v26..
|Timestamp Field |
|Octets |Type |Description |
|86 |Unsigned Integer |MicrosSeconds |
|24 |Unsigned Integer |Nanoseconds |
The value in the Timestamp field is derived from a monotonically increasing counter incremented periodically with clock ticks where the clock is driven by a free running oscillator and is provided to higher layers in the STA which can compute its offset to the time of another STAThe Timestamp field is captured from a monotonically increasing free-running counter and is provided to higher layers in the STA which can compute its offset to the time of another STA.
Insert the following after 7.4.10:
802.11-2007 ends with 7.4.5. 11k adds 6. 11r adds 7. 11y adds none 11n adds 9 (8). 11w adds none. 11p adds 8 (9). 11s adds 6 (10).
Wireless Network Management action details
Several Action frame formats are defined for Wireless Network 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 v41.
|Wireless Network Management Action field values |
|Action field value |Description |
|0 |Event Request |
|1 |Event Report |
|2 |Diagnostic Request |
|3 |Diagnostic Report |
|4 |Location Request |
|5 |Location Response |
|46 |Location Configuration Request |
|57 |Location Configuration Response |
|68 |BSS Transition Management Query |
|79 |BSS Transition Management Request |
|810 |BSS Transition Management Response |
|911 |FBMS Request |
|102 |FBMS Response |
|113 |Co-located Interference Request |
|124 |Co-located Interference Response |
|1315 |TFS Request |
|1416 |TFS Response |
|1517 |TFS Notify |
|1618 |Sleep Mode Request |
|1719 |Sleep Mode Response |
|1820 |TIM Broadcast Request |
|1921 |TIM Broadcast Response |
|2022 |TIM |
|213 |Traffic Generation Update |
|224-255 |Reserved |
Location Request frame format
The Location Request frame uses the Action frame body format and is transmitted by a STA to advertise its Location or request its own location information from another STA that supports location services. The format of the Location Request frame body is shown in Figure v79.
| | | | | |
| |Category |Action |Dialog Token |Location Parameters Element |
|Octets: |1 |1 |1 |variable |
|Location Request frame body format |
The Category field is set to the value indicating the Wireless Network Management category, as specified in Table 24 in 7.3.1.11.
The Action field is set to the value indicating Location Request, as specified in Table v41 in 7.4.11.
The Dialog Token field is set to a nonzero value that is unique among the Location Request frames sent to each destination MAC address for which a corresponding Location Response frame has not been received.
The Location Parameters Element field contains the Location Parameters sub-elements, described in 7.3.2.66. Table v42 defines the allowed Location Parameters sub-elements for a Location Parameters element that is included in the Location Request frame.
|Location Parameters Element field for Location Request frame |
|Allowed Sub-elements |Sub-element ID |Notes |
|Radio Information |6 |The Radio Information sub-element may be included in the |
| | |Location Request frame. |
|Motion |8 |The Motion sub-element may be included in the Location |
| | |Request frame. |
|Location Descriptor |9 |The Location Descriptor sub-element may be included in the |
| | |Location Request frame. |
|Location Data |10 |The Location Data sub-element may be included in the |
| | |Location Request frame. |
|Location Request Options |3 |The Location Request Options sub-element may be included in|
| | |the Location Request frame. |
|Vendor Specific Information |221 |The Vendor Specific Information sub-element may be included|
| | |in the Location Request frame. |
Location Response frame format
The Location Response frame uses the Action frame body format and is transmitted by a STA in response to the receipt of a Location Request frame. The format of the Location Response frame body is shown in Figure v80.
| | | | | |
| |Category |Action |Dialog Token |Location Parameters |
| | | | |Element |
|Octets: |1 |1 |1 |variable |
The Category field is set to the value indicating the Wireless Network Management category, as specified in Table 24 in 7.3.1.11.
The Action field is set to the value indicating Location Response, as specified in Table v41 in 7.4.11.
The Dialog Token field is set to the nonzero value received in the Location Request frame to identify the request/response transaction.
The Management Action Pending field is set to 0 if no management action is pending for the destination STA, and set to 1 if there is a management action pending for the destination STA.
The Location Parameters Element field contains the Location Parameters sub-elements, described in 7.3.2.66. Table v43 defines the allowed Location Parameters sub-elements for a Location Parameters element that is included in the Location Response frame.
|Location Parameters Element field for Location Response frame |
|Allowed Sub-element Fields |Sub-element ID |Notes |
|Radio Information |6 |The Radio Information sub-element may be included in the |
| | |Location Response frame. |
|Timing Measurements |7 |The Timing Measurements sub-element may be included in the |
| | |Location Response frame. |
|Motion |8 |The Motion sub-element may be included in the Location |
| | |Response frame. |
|Location Descriptor |9 |The Location Descriptor sub-element may be included in the |
| | |Location Response frame. |
|Location Status |4 |The Location Status sub-element is included in the Location|
| | |Response frame. |
|Location Source Identifier |11 |The Location Source Identifier sub-element may be included |
| | |in the Location Response frame. |
|Vendor Specific Information |221 |The Vendor Specific Information sub-element may be included|
| | |in the Location Response frame. |
Location Configuration Request frame format
The Location Configuration Request frame uses the Action frame body format and is transmitted by a STA to configure another STA to send a Location Track Notification frame on a set of channels establish a location service that periodically for the purposes of determining location of the STA provides a location estimate to another STA or to configure the peer STA for the periodic exchange of frames necessary to locate the STA. The format of the Location Configuration Request frame body is shown in Figure v81.
| | | | | |
| |Category |Action |Dialog Token |Location Parameters Element |
|Octets: |1 |1 |1 |variable |
|Location Configuration Request frame body format |
The Category field is set to the value indicating the Wireless Network Management category, as specified in Table 24 in 7.3.1.11.
The Action field is set to the value indicating Location Configuration Request, as specified in Table v41 in 7.4.11.
The Dialog Token field is set to a nonzero value that is unique among the Location Configuration Request frames sent to each destination MAC address for which a corresponding Location Configuration Response frame has not been received.
The Location Parameters Element field contains the location parameters sub-elements, described in 7.3.2.66. Table v44 defines the allowed Location Parameters sub-elements for a Location Parameters element that is included in the Location Configuration Request frame.
|Location Parameters Element field for Location Configuration Request frame |
|Allowed Sub-element Fields |Sub-element ID |Notes |
|Location Indication Parameters |1 |The Location Reporting Parameters sub-element may beis |
| | |included in the Location Configuration Request frame. |
|Location Indication Channels |2 |The Location Reporting Channels sub-element may beis |
| | |included in the Location Configuration Request frame. |
|Location Indication Broadcast Data |612 |The Location Indication Broadcast Data Rate sub-element may|
|Rate | |beis included in the Location Configuration Request frame. |
|Location Service Parameters |5 |The Location Service Parameters sub-element may be included|
| | |in the Location Configuration Request frame. |
|Location Descriptor |9 |The Location Descriptor sub-element may be included in the |
| | |Location Configuration Request frame. |
|Location Data |10 |The Location Data sub-element may be included in the |
| | |Location Configuration Request frame. |
|Location Request Options |3 |The Location Request Options sub-element may be included in|
| | |the Location Configuration Request frame. |
|Vendor Specific Information |221 |The Vendor Specific Information sub-element may be included|
| | |in the Location Configuration Request frame. |
Location Configuration Response frame format
The Location Configuration Response frame uses the Action frame body format and is transmitted by a STA in response to the receipt of a Location Configuration Request frame. The format of the Location Configuration Response frame body is shown in Figure v82.
| | | | | |
| |Category |Action |Dialog Token |Location Parameters |
| | | | |Element |
|Octets: |1 |1 |1 |variable |
|Location Configuration Response frame body format |
The Category field is set to the value indicating the Wireless Network Management category, as specified in Table 24 in 7.3.1.11.
The Action field is set to the value indicating Location Configuration Response, as specified in Table v41 in 7.4.11.
The Dialog Token field is set to the nonzero value received in the Location Configuration Request frame to identify the request/response transaction.
The Location Parameters Element field contains the location parameters sub-elements, described in 7.3.2.66. Table v45 defines the allowed Location Parameters sub-elements for a Location Parameters element that is included in the Location Configuration Response frame.
|Location Parameters Element field for Location Configuration Response frame |
|Allowed Sub-element Fields |Sub-element ID |Notes |
|Location Indication Parameters |1 |The Location Reporting Parameters sub-element may be |
| | |included in the Location Configuration Response frame. |
|Location Indication Channels |2 |The Location Reporting Channels sub-element may be included|
| | |in the Location Configuration Response frame. |
|Location Indication Broadcast Data |612 |The Location Indication Broadcast Data Rate sub-element may|
|Rate | |be included in the Location Configuration Response frame. |
|Location Status |3 |The Location Status sub-element is included in the Location|
| | |Configuration Response frame. If all configuration of the |
| | |sub-elements contained in a Location Configuration Request |
| | |frame was successful then a single Location Status |
| | |sub-element is included in the Location Configuration |
| | |Response frame. For each sub-element contained in the |
| | |Location Configuration Request frame that is not successful|
| | |a Location Status sub-element is included in the Location |
| | |Configuration Response frame that indicates the sub-element|
| | |ID and the unsuccessful status code for that sub-element |
| | |ID. |
|Location Status |4 |The Location Status sub-element is included in the Location|
| | |Configuration Response frame. |
|Vendor Specific Information |221 |The Vendor Specific Information sub-element may be included|
| | |in the Location Configuration Response frame. |
Location request
This set of primitives supports the exchange of location parameter information between peer SMEs. Figure v107 depicts the location request and response process. The figure illustrates the basic protocol and is only an example and therefore is not meant to be exhaustive of all possible protocol uses.[pic]
Location Request and Response Protocol Exchange
MLME-LOCATIONREQUEST.request
Function
This primitive requests the transmission of a location request action frame to a peer entity.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONREQUEST.request (
Peer MAC Address,
Dialog Token,
Location Parameters)
|Name |Type |Valid Range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address, or the |request shall be sent. |
| | |Broadcast MAC | |
| | |address | |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the SME to request that a Location Request frame be sent to a peer entity to convey location information.
Effect of receipt
On receipt of this primitive, the MLME constructs a Location Request frame containing the set of location elements specified. This frame is then scheduled for transmission.
MLME-LOCATIONREQUEST.confirm
Function
This primitive reports the result of a location request.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONREQUEST.confirm (
Dialog Token,
ResultCode,
TX Timestamp,
RX Timestamp)
|Name |Type |Valid Range |Description |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|ResultCode |Enumeration |SUCCESS, INVALID |Indicates the result of the corresponding |
| | |PARAMETERS, or |MLME-LOCATION.request. |
| | |UNSPECIFIED FAILURE | |
|TX Timestamp |10 octets as defined|10 octets as defined|The TX Timestamp field contains the time at which the |
| |in Table v26 |in Table v26 |unicast Location Request frame was transmitted by a STA,|
| | | |defined to occur at the PHY-TXEND.indication of the |
| | | |transmitting Location Request frame. The TX Timestamp |
| | | |field is composed of the time fields defined in |
| | | |Table v26. |
|RX Timestamp |10 octets as defined|10 octets as defined|The RX Timestamp field contains the time at which the |
| |in Table v26 |in Table v26 |ACK frame in response to the Location Request frame was |
| | | |received by a STA, defined to occur at the |
| | | |PHY-RXEND.indication of the received ACK frame. The RX |
| | | |Timestamp field is composed of the time fields defined |
| | | |in Table v26. |
When generated
This primitive is generated by the MLME when the request to transmit a Location Request frame completes.
Effect of receipt
On receipt of this primitive, the SME evaluates the result code.
MLME-LOCATIONREQUEST.indication
Function
This primitive indicates that a Location Request frame has been received requesting a location transaction.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONREQUEST.indication (
Peer MAC Address,
Dialog Token,
Location Parameters)
|Name |Type |Valid Range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address or the |request shall be sent. |
| | |broadcast MAC | |
| | |address | |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the MLME when a valid Location Request frame is received.
Effect of receipt
On receipt of this primitive, the SME either rejects the request or commences the location transaction.
Location response
This set of primitives supports the exchange of location parameters between peer SMEs.
MLME-LOCATIONRESPONSE.request
Function
This primitive requests the transmission of location information to a peer entity, in response to a received Location Request frame.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONRESPONSE.request (
Peer MAC Address,
Dialog Token,
Management Action Pending,
Location Parameters)
|Name |Type |Valid Range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |request shall be sent. |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Management Action |Integer |0 – 255 |The management action pending value indicates if a |
|Pending | | |management action is pending for the STA. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the SME to request that a Location Response frame be sent to a peer entity to convey location information.
Effect of receipt
On receipt of this primitive, the MLME constructs a Location Response frame containing the set of location elements specified. This frame is then scheduled for transmission.
MLME-LOCATIONRESPONSE.confirm
Function
This primitive reports the result of a request to send a location response action frame.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONRESPONSE.confirm (
Dialog Token,
ResultCode)
|Name |Type |Valid Range |Description |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|ResultCode |Enumeration |SUCCESS, INVALID |Reports the outcome of a request to send a Location |
| | |PARAMETERS, or |Response frame. |
| | |UNSPECIFIED FAILURE | |
When generated
This primitive is generated by the MLME when the request to transmit a Location Response frame completes.
Effect of receipt
On receipt of this primitive, the SME evaluates the result code.
MLME-LOCATIONRESPONSE.indication
Function
This primitive indicates that a Location Response frame has been received.
Semantics of the service primitive
The primitive parameters are as follows:
MLME- LOCATIONRESPONSE.indication (
Peer MAC Address,
Dialog Token,
Management Action Pending,
Location Parameters)
|Name |Type |Valid Range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |response shall be sent. |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Management Action |Integer |1 – 255 |The management action pending value indicates if a |
|Pending | | |management action is pending for the STA. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the MLME when a valid Location Response frame is received.
Effect of receipt
On receipt of this primitive, the SME evaluates the Location Parameters
Location Configuration request
This set of primitives supports the exchange of location configuration parameter information between peer SMEs. The information diagram shown in Figure v106 depicts the location configuration request and response process. The figure illustrates the basic protocol and is only an example, and therefore is not meant to be exhaustive of all possible protocol uses. [pic]
Location Configuration Request and Response Protocol Exchange
MLME-LOCATIONCFG.request
Function
This primitive requests the transmission of location configuration request action frame to a peer entity.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONCFG.request (
Peer MAC Address,
Dialog Token,
Location Parameters)
|Name |Type |Valid rRange |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |configuration request shall be sent. |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the SME to request that a Location Configuration Request frame be sent to a peer entity to convey location information.
Effect of receipt
On receipt of this primitive, the MLME constructs a Location Configuration Request frame containing the set of location elements specified. This frame is then scheduled for transmission.
MLME-LOCATIONCFG.confirm
Function
This primitive reports the result of a location configuration request.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONCFG.confirm (
Dialog Token,
ResultCode,
Peer MAC Address,
Location Parameters)
|Name |Type |Valid rRange |Description |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|ResultCode |Enumeration |SUCCESS, |Reports the outcome of a request to send a Location |
| | |TRANSMISSION |Configuration Request frame. |
| | |FAILURE, | |
| | |INVALID PARAMETERS, | |
| | |or UNSPECIFIED | |
| | |FAILURE | |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |configuration response shall be sent. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the MLME when transmission of the Location Configuration Request frame is acknowledged, (re) transmission of the Location Configuration Request frame fails, the Location Configuration Request frame contains invalid parameters, or for unspecified failure reasons.
This primitive is generated by the MLME as a result of the receipt of a Location Configuration Response action management frame. This primitive is also generated when the MLME-LOCATIONCFG.request contains invalid parameters and when a timeout or failure occurs.
Effect of receipt
On receipt of this primitive, the SME evaluates the result code.
MLME-LOCATIONCFG.indication
Function
This primitive indicates that a Location Configuration Request frame has been received requesting a location transaction.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONCFG.indication (
Peer MAC Address,
Dialog Token,
Location Parameters)
|Name |Type |Valid rRange |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |configuration request shall be sent. |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the MLME when a valid Location Configuration Request frame is received.
Effect of receipt
On receipt of this primitive, the SME either rejects the request or commences the location transaction.
MLME-LOCATIONCFG.response
Function
This primitive requests the transmission of location information to a peer entity, in response to a received Location Configuration Request frame.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONCFG.response (
Peer MAC Address,
Dialog Token,
Location Parameters)
|Name |Type |Valid rRange |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |MAC Address |request shall be sent. |
|Dialog Token |Integer |1 – 255 |The dialog token to identify the location transaction. |
|Location Parameters |Location element |Location element |A location element containing one or more sub-elements |
| | | |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the SME to request that a Location Configuration Response frame be sent to a peer entity to convey location information.
Effect of receipt
On receipt of this primitive, the MLME constructs a Location Configuration Response frame containing the set of location elements specified. This frame is then scheduled for transmission.
53. Location Track Notification
This set of primitives supports the location track notification from one SME to one or more receiving SMEs. The informative diagram in Figure v106 depicts the location track notification process, is not meant to be exhaustive of all possible protocol uses.
[pic]
Location Track Notification Protocol Exchange
MLME-LOCATIONTRACKNOTIF.request
Function
This primitive requests the transmission of location configuration request action frame to a peer entity.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONTRACKNOTIF.request (
Peer MAC Address,
Location Parameters)
|Name |Type |Valid range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |or group addressed |track notification shall be sent. |
| | |MAC Address | |
|Location Parameters |Location Parameters |Location Parameters |A location parameters element containing one or more |
| |element |element |sub-elements describing the STA location information. |
| | | |See 7.3.2.66. |
When generated
This primitive is generated by the SME to request that a Location Track Notification frame be sent to a peer entity to help convey location information.
Effect of receipt
On receipt of this primitive, the MLME constructs a Location Track Notification frame containing the set of location elements specified. This frame is then scheduled for transmission.
MLME-LOCATIONTRACKNOTIF.indication
Function
This primitive indicates that a Location Track Notification frame has been received.
Semantics of the service primitive
The primitive parameters are as follows:
MLME-LOCATIONTRACKNOTIF.indication (
Peer MAC Address,
Location Parameters)
|Name |Type |Valid range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the location|
| | |or group addressed |track notification shall be sent. |
| | |MAC Address | |
|Location Parameters |Location Parameters |Location Parameters |A location element containing one or more sub-elements |
| |element |element |describing the STA location information. See 7.3.2.66. |
When generated
This primitive is generated by the MLME when a valid Location Track Notification frame is received.
Effect of receipt
On receipt of this primitive, the SME uses the information contained within the notification.
54. Timing Measurement
The following set of primitives supports exchange of timing measurement information from one SME to another. The informative diagram in Figure v107 depicts the time sync information exchange. Multiple exchange of time sync information may be required in order for a STA to synchronize itself with respect to another STA.
[pic]
Figure v107 – Timing Measurement Information Exchange
10.3.54.1 MLME-TIMINGMSMT.request
10.3.54.1.1 Function
This primitive requests the transmission of Timing Measurement public action frame to a peer entity.
10.3.54.1.2 Semantics of the service primitive
The primitive parameters are as follows:
MLME-TIMINGMSMT.request (
Peer MAC Address,
Dialog Token,
Follow On to Dialog Token,
Timestamp Difference,
Timestamp Difference Units,
Timestamp Difference Accuracy,
Timestamp,
Timestamp Accuracy)
|Name |Type |Valid range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the Timimg |
| | |or group addressed |Measurement public action frame shall be sent. |
| | |MAC Address | |
|Dialog Token |Integer |1-255 |The dialog token to identify the Timing Measurement |
| | | |transaction. |
|Follow On to Dialog |Interger |0-255 |The dialog token of a Timing Measurement public action |
|Token | | |frame to which the current frame is a follow on. See |
| | | |11.20.5.5. |
|Timestamp Difference |Location Parameters |Location Parameters |See 7.4.7.11. |
| |element |element | |
|Timestamp Difference |As defined in Timing|As defined in Timing|See 7.4.7.11. |
|Units |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp Difference |As defined in Timing|As defined in Timing|See 7.4.7.11. |
|Accuracy |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp |As defined in Timing|As defined in Timing|See 7.4.7.11. |
| |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp Accuracy |As defined in Timing|As defined in Timing|See 7.4.7.11 |
| |Measurement public |Measurement public | |
| |action frame |action frame | |
10.3.54.1.2 When generated
This primitive is generated by the SME to request that a Timing Measurement public action frame be sent to a peer entity.
10.3.54.1.3 Effect of receipt
On receipt of this primitive, the MLME constructs a Timing Measurement public action frame containing the time measurement parameters specified. This frame is then scheduled for transmission.
10.3.54.2 MLME-TIMINGMSMT.confirm
10.3.54.2.1 Function
This primitive indicates that a Timing Measurement public action frame has been successfully received by the peer STA to which it was sent.
10.3.54.3.2 Semantics of the service primitive
The primitive parameters are as follows:
MLME-TIMINGMSMT.confirm (
Peer MAC Address,
Dialog Token,
Timestamp,
Ingress Timestamp)
|Name |Type |Valid range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which acknowledges|
| | |or group addressed |the receipt of the Timing Measurement public action |
| | |MAC Address |frame |
|Dialog Token |Integer |1-255 |The dialog token to identify the Timing Measurement |
| | | |transaction. |
|Timestamp |As defined in Timing|As defined in Timing|See 7.3.2.21.14 for format of Timestamp. The time at |
| |Measurement public |Measurement public |which the Timing Measurement public action frame was |
| |action frame |action frame |sent. This corresponds to PHY-TXSTART.confirm. |
|Ingress TimeStamp |As defined in Timing|As defined in Timing|See 7.3.2.21.14 for format of Timestamp. |
| |Measurement public |Measurement public |The Ingress Timestamp contains the time at which the ACK|
| |action frame |action frame |for Timing Measurement public action frame was received |
| | | |by the STA, defined to occur at the |
| | | |PHY-RXSTART.Indication of the received frame. (t4 in |
| | | |Figure v107) |
10.3.54.2.3 When generated
This primitive is generated by the MLME when an ACK corresponding to the Timing Measurement public action frame is received from the peer STA.
10.3.54.2.4 Effect of receipt
On receipt of this primitive, the SME uses the information contained within the notification.
10.3.54.3 MLME-TIMINGMSMT.indication
10.3.54.3.1 Function
This primitive indicates that a Timing Measurement public action frame has been received.
10.3.54.3.2 Semantics of the service primitive
The primitive parameters are as follows:
MLME-TIMINGMSMT.indication (
Peer MAC Address,
Dialog Token,
Follow On to Dialog Token,
Timestamp Difference,
Timestamp Difference Units,
Timestamp Difference Accuracy,
Timestamp,
Ingress Timestamp)
|Name |Type |Valid range |Description |
|Peer MAC Address |MACAddress |Any valid individual|The address of the peer MAC entity to which the Timing |
| | |or group addressed |Measurement public action frame shall be sent. |
| | |MAC Address | |
|Dialog Token |Integer |1-255 |The dialog token to identify the Timing Measurement |
| | | |transaction. |
|Follow On to Dialog |Interger |0-255 |The dialog token of a Timing Measurement public action |
|Token | | |frame to which the current frame is a follow on. See |
| | | |11.20.5.5. |
|Timestamp Difference |Location Parameters |Location Parameters |See 7.3.2.21.14. |
| |element |element | |
|Timestamp Difference |As defined in Timing|As defined in Timing|See 7.3.2.21.14. |
|Units |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp Difference |As defined in Timing|As defined in Timing|See 7.3.2.21.14. |
|Accuracy |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp |As defined in Timing|As defined in Timing|See 7.3.2.21.14. |
| |Measurement public |Measurement public | |
| |action frame |action frame | |
|Timestamp Accuracy |As defined in Timing|As defined in Timing|See 7.3.2.21.14. |
| |Measurement public |Measurement public | |
| |action frame |action frame | |
|Ingress TimeStamp |As defined in Timing|As defined in Timing|See 7.3.2.21.14 for format of TimeStamp. |
| |Measurement public |Measurement public |The Ingress Timestamp contains the time at which the |
| |action frame |action frame |Timing Measurement public action frame was received by |
| | | |the STA, defined to occur at the PHY-RXSTART.Indication |
| | | |of the received frame. (t2 in Figure-v107) |
10.3.54.3.3 When generated
This primitive is generated by the MLME when a valid Timing Measurement public action frame is received.
10.3.54.3.4 Effect of receipt
On receipt of this primitive, the SME uses the information contained within the notification.
Insert the following sentence at the end of 11.10.8.6
11.10.8.6 Location Configuration Information Report
If dot11RRMLCIMeasurementEnabled is true and a STA has its own location configured in LCI format it shall set the E911 Geo Location field to 1 in the Extended Capabilities element.
Insert the following paragraphs
11.10.8.9 Location Civic Report
If dot11RRMCivicMeasurementEnabled is true, a STA shall reject any Location Civic Request for location information which is not available and shall respond with a Measurement Report frame including a Measurement Report element with the incapable bit set to 1. If dot11RRMCivicMeasurementEnabled is true and a STA accepts a Location Civic Request it shall respond with a Measurement Report frame including one Location Civic Report element.
A Location Civic Request shall indicate a location request for the requesting STA or the reporting STA by setting the Location Civic request Location Subject field to indicate Local or Remote request respectively. Local Location Civic Measurement Request is used by requesting STA to obtain its own location by asking “Where am I?”. Remote Location Civic Measurement Request is used by requesting STA to obtain location of the reporting STA by asking “Where are you?”.
If dot11RRMCivicMeasurementEnabled is false, a STA shall reject the received Location Civic Measurement Request and shall respond with a Location Civic Report where the Incapable bit is set in the Measurement Report Mode field.
If dot11RRMCivicMeasurementEnabled is true and a STA has its own location configured in Civic format it shall set the E911 CIVIC Location field to 1 in the Extended Capabilities element.
11.10.8.10 Location Identifier Report
The Location Identifier Report provides the ability for a STA to receive an indirect URI reference and forward that reference to an external agent for the purposes of that agent gathering the STA’s location value. The protocol used to query the infrastructure for a location report based on the Public Identifier URI provided in the Location Identifier Report is beyond the scope of this standard.
If dot11RRMIdentifierMeasurementEnabled is true, a STA shall reject any Location Identifier Request for location information which is not available and shall respond with a Measurement Report frame including a Measurement Report element with the incapable bit set to 1. If dot11RRMIdentifierMeasurementEnabled is true and a STA accepts a Location Identifier Request it shall respond with a Measurement Report frame including one Location Identifier Report element.
A Location Identifier Request shall indicate a location request for the requesting STA or the reporting STA by setting the Location Identifier request Location Subject field to indicate Local or Remote request respectively. Local Location Identifier Measurement Request is used by requesting STA to obtain its own location by asking “Where am I?”. Remote Location Civic Measurement Request is used by requesting STA to obtain location of the reporting STA by asking “Where are you?”.
If dot11RRMIdentifierMeasurementEnabled is false, a STA shall reject the received Location Identifier Measurement Request and shall respond with a Location Identifier Report where the Incapable bit is set in the Measurement Report Mode field.
Location procedures
Location Request procedures
The Location Request/Location Report and Location Configuration Request/Location Configuration Report protocol provides the means to enable location services. A STA that has a value of true for the MIB attribute dot11MgmtOptionLocationEnabled is defined as a STA that supports Location Services and indicates this support by setting the dot11MgmtOptionLocationEnabled bit of the Extended Capabilities element to 1 in transmitted Beacon, Association Request, Association Response, Reassociation Request, Reassociation Response, and Probe Response frames.
A STA may periodically provide location related information by sending Location Request frames. The Location Request frame may be a broadcast or individually addressed frame. A Location Request frame may be sent by a STA as an individually addressed frame or as a broadcast frame to all STAs capable of receiving the frame.
A non-AP STA may send Location Request frames containing parameters defined by the Location Parameters information element in the Location Configuration Request and Response frames. When a non-AP STA has been configured by the Location Configuration Request frame to transmit broadcast Location Request frames, it shall transmit the Location Request frame preferably at the Broadcast Target Rate as defined in the Location Indication Broadcast Data Rate sub-element. When a non-AP STA moves from one ESS to another ESS, the non-AP STA may send Location Request frames containing parameters defined by the Location Parameters information element in the Location Configuration Request and Response frames of the new ESS.
Transmitting Location Request frames on non-operating channels may require the STA to interrupt its data services on the operating channel, switch channels and transmit the Location Request frames. Transmitting Location Request frames on the operating channel may not require the STA to interrupt its data services. All stations are responsible for maintaining data services and association or membership with the BSS or IBSS respectively, on the operating channel while transmitting the Location Request frame on non-operating channels. A STA shall be configured by the Location Configuration Request frame the time between the successive Location Request frame transmissions for both operating and non-operating channels.
A STA may request its own location information from another STA that supports location services and is capable of providing location of other STAs. To request the location, the STA shall send a Location Request frame with a Location Parameters information element that includes a Location Descriptor sub-element. The Location Descriptor sub-element in the request shall specify “Local”. The STA shall specify the Location Descriptor, Location Resolution Descriptor, and Encoding Descriptor fields of the Location Descriptor sub-element and encoding descriptor received in the Location Response frame. The STA may define the Vendor Specific Information.
A STA may request the Remote location information from another STA that supports location services and is capable of providing its location. To request the location, the STA shall send a Location Request frame with a Location Parameters information element that includes a Location Descriptor sub-element in the request frame. The Location Descriptor sub-element in the request shall specify “Remote”. The STA shall specify the values of Format Descriptor, Resolution Descriptor and Encoding Descriptor fields of the Location Descriptor sub-element. The STA may define the Vendor Descriptor.
A STA that supports the location capability may send a Location Request frame to provide data for the purpose of locating the STA. The STA shall send a Location Request frame on the requested channels and at the requested interval as defined by the requesting Location Parameters information element in the Location Configuration Request frame. The STA shall include a Radio Information and Motion sub-element as requested by the Location Request Options sub-element in the corresponding requesting Location Parameters information element. The STA sending the Location Request frame may also include a Location Request Options sub-element to indicate whether a Radio Information sub-element, Timing Measurements or Motion sub-element is requested in the corresponding Location Response frame. If no Location Request Options sub-element is included then no Location Response frame shall be sent.
A STA that supports the location capability may send a Location Request frame to provide its location capability. The STA shall include a Location Descriptor sub-element in the Location Parameters information element in a Location Request frame to provide its location capability. The location description value of 2 “CIVIC Preferred” or 3 “GEO Preferred” indicates that the STA is capable of supporting both CIVIC and GEO formats, but prefers the indicated format. If the STA is capable of calculating its own location and wishes to provide its location to the AP, then the STA may include a Location Data sub-element in the Location Parameters information element.
A STA may include the Radio Information field values in the Location Request frame, to provide radio related information to the receiving STA. The Radio Information can be used to support location services.
A STA may include the Motion field values in the Location Request frame, to provide motion related information to the receiving STA. The Motion Information can be used to support location services.
Location Response procedures
The Location Response frame shall be sent by a STA in response to a received Location Request frame in which the Response Requested bit is set to 1, and provides location reporting parameters to the STA.
A non-AP STA shall only respond to a Location Request frame sent by an AP if that non-AP STA is associated with the AP.
A Location Response frame may be sent for several purposes, including providing location parameters to another STA or exchanging frames for location calculation purposes.
A STA that supports the location capability and receives a Location Request frame that includes a Location Request Options sub-element shall respond with Location Response frame that includes the requested sub-elements in the Location Request Options sub-element and a Location Status sub-element indicating the result of the request.
A STA that supports location services and receives a Location Parameters information element that includes a Location Service Parameters sub-element or a Location Request frame that includes a Location Description sub-element shall respond with Location Response frames that include a Location Descriptor and a Location Data sub-element. Depending on the options defined in the Location Descriptor of the request, the STA may also include the Location Source Identifier sub-element in the response. The STA shall set the Location Descriptor, Bits 0 to 3, to specify whether the STA requests local or remote location information. The STA shall set the Format Descriptor, Resolution Descriptor and Encoding Descriptor bits in the Location Descriptor sub-element to match the Location Data sub-element content. If the responding STA is not able to respond with values that match the request as defined in the Location Description sub-element, the STA shall send a response with a Location Status element that indicates Fail.
If a STA received a Location Response frame with the Management Action Pending field value set to “1”, the STA, if not already associated to a BSS, shall attempt to associate to the AP from which it received the Location Response frame, or to another AP of its choosing to determine the management action that is pending. The Management Action Pending field is used to indicate that an application requests a non-AP STA associates to enable an application function.
A STA that supports location services and receives a Location Request frame which includes a Location Request Options sub-element with the Radio Information bit set to “1” shall respond with a Location Response frame that includes a Radio Information sub-element containing available radio information field values. The Radio Information can be used to support location services.
A STA that supports location services and receives a Location Request frame which includes a Location Request Options sub-element with the Motion bit set to “1” shall respond with a Location Response frame that includes a Motion sub-element containing the applicable Motion Indicator field value. Motion Information can be used to support location services.
A STA that supports location services and ingress timestamping and receives a Location Request frame which includes a Location Request Options sub-element with the Timing Measurements bit set to “1” shall respond with a Location Response frame that includes a Timing Measurements sub-element containing the time difference between the time that the Location Request frame was received from the STA and the time that the corresponding ACK frame was sent to the requesting STA. The STA shall respond to the Timing Measurement request with the highest level of accuracy it supports as defined in the Timing Measurement sub-element. A STA that supports location services but does not support ingress timestamping and receives a Location Request frame which includes a Location Request Options sub-element with the Timing Measurements bit set to “1” shall respond with a Location Response frame with a Location Status sub-element that indicates Incapable.
Location Track Configuration procedures
11.20.5.3.1 Location Track Configuration Procedures
A STA that has a value of true for the MIB attribute dot11MgmtOptionLocationEnabled is defined as a STA that supports Location. A STA for which the MIB attribute dot11MgmtOptionLocationEnabled is true shall set the Location field of the Extended Capabilities element to 1.
If dot11MgmtOptionLocationEnabled is true a STA shall set the Location bit to 1 in the Extended Capabilities element.
If dot11MgmtOptionLocationEnabled is true and a STA receives a Location Configuration Request frame, it shall respond with a Location Configuration Response frame.
To support location service there are several parameters that may be configured on a STA. A STA may be configured to send frames periodically to enable another STA to collect the necessary data for location determination. In addition, if a STA has advertised its ability to provide location service to other STAs, a STA may request periodic location updates from the STA providing the location service by sending a configuration request frame. In an infrastructure BSS, a non-AP STA shall not transmit Location Configuration Request frames.
A STA may configure another STA to transmit Location Track Notification frames for the purpose of tracking that the receiving STA’s location by sending Location Indication Channels, Location Indication Interval and Location Indication Broadcast Data Rate sub-elements in a Location Parameters information element in a Location Configuration Request frame.
A Location Configuration Request frame may be a broadcast or individually addressed frame. A STA receiving a broadcast Location Configuration Request frame shall only send a Location Configuration Response frame if the STA does not accept the parameters included in the Location Configuration Request.
A STA that receives an individually addressed Location Configuration Request shall respond with a Location Configuration Response frame. If all Location Parameter sub-elements included in the Location Configuration Request are successfully configured on the receiving STA, then the STA shall include in the Location Configuration Response frame a single Location Status sub-element indicating success. If one or more Location Parameter sub-elements are unsuccessfully configured, then the STA shall include in the Location Configuration Response frame a Location Status sub-element for each failed sub-element indicating the sub-element ID and status value and if applicable the Location Parameters sub-elements. .
The Location Status sub-element has four possible status values: Success, Fail, Refused and Incapable. When the requesting STA that sent a Location Configuration Request frame receives a Location Configuration Response frame with Location Status indicating anything other than Success, the requesting STA shall assume the original request was not processed and no configuration took affect on the receiving STA and the requesting STA should take appropriate action based on the status value returned.
• For Location Status Fail
o If the STA has been configured successfully prior to the current Location Configuration Request and continues to transmit Location Track Notification frames based on those parameters, the STA shall respond with its current Location Parameters sub-elements values.
o If the STA has no previously configured value, tThe STA shall responding to the configuration request may includewith its minimum Location Parameters sub-elements that it is capable of supporting. the current set of Location Parameters sub-elements this configured on the STA.
o The STA may either retry the original request or send an alternate request.
• For Location Status Incapable
o The STA responding to the configuration request may include the minimum Location Parameters sub-elements that it is capable of supporting.
o The configuring STA shall not send another configuration request matching the previous configuration request while the reporting STA is associated to the same BSS.
o The configuring STA may send an alternate request.
• For Location Status Refuse
o The STA responding to the configuration request may include the minimum Location Parameters sub-elements that it is capable of supporting.
o The configuring STA may send an alternate request.
A STA may configure the location service by including a Location Parameters information element in a Location Configuration Request frame.
A Location Configuration Request frame may be a broadcast or individually addressed frame. A STA receiving an individually addressed Location Configuration Request frame shall respond with a Location Configuration Response frame that includes a Location Parameters information element indicating the result of the request in the Location Status sub-element. A STA receiving a broadcast Location Configuration Request frame shall not send a Location Configuration Response frame.
The location configuration methods, from highest to lowest precedence, are as follows: 1) an individually addressed Location Configuration Request frame, 2) broadcast Location Configuration Request frame. When a STA receives a new Location Configuration frame at the same or a higher precedence than the previous it shall cancel the previous configuration and begin using the newest configuration.
A STA may configure another STA to periodically transmit Location Request frames for the purpose of providing location data by sending a Location Parameters information element with the appropriate interval to the other STA in a Location Configuration Request frame.
The Location Configuration Request frame may include the Location Indication Broadcast Data Rate sub-element included in Location Configuration Request frames to indicates the target data rate at which the STA should shall transmit broadcast Location Request Track Notification frames. The Location Indication Broadcast Data Rate included in the Location Configuration Request frame shall be a data rate defined in the operational data rate set. Whenever possible, a STA should transmit Location Request frames using the received Location Indication Broadcast Data Rate. If it is not possible to transmit at the data rate provided in the Location Indication Broadcast Data Rate sub-element, the STA should transmit Location Request frames at a data rate that is acceptable to the STA while maintaining other services.
The Location Indication Multicast Address field configured in the Location Indication Interval sub-element shall be a multicast locally administered IEEE MAC address as defined in IEEE Std 802-1990 that is shared across all APs in the same ESS. The remaining 46 bits of that MAC address shall be a number selected in a manner that minimizes the probability of STAs generating the same number, even when those STAs are subjected to the same initial conditions.
The A STA shall may terminate the periodic transmission of Location Request Track Notification frames on another STA by sending a Location Configuration Request frame including a Location Parameters information element with the Location Indication Interval sub-element specifying anwith an interval of zero. If a STA configured to transmit Location Track Notification frames leaves or can no longer detect the ESS that configured it, the STA shall terminate the transmission of Location Track Notification frames.
Note: All public action frames, including the Location Track Notification frames, are Class 1 frames and how public action frames are treated upon reception by STAs is defined in 11.3..The Location Parameters information element shall contain a Location Service Parameters sub-element describing the desired behavior. If the frame used to initiate service is an individually addressed Location Configuration Request frame then the STA shall respond with a Location Configuration Response frame that includes the STA's Location Parameters element indicating the STA's values for the sub-elements specified in the Location Parameters element and a Location Status sub-element indicating whether the request is successful or not. The Location Status sub-element has four possible status values: Success, Fail, Refused and Incapable. When the STA that sent a Location Configuration Request frame receives a Configuration Response frame with Location Status indicating anything other than Success, the STA shall assume the original request was not processed and the STA should take appropriate action based on the status value returned. For Location Status Fail, the STA may either retry the original request or send an alternate request. For Location Status Incapable, the STA shall not send another configuration request matching the previous configuration request while associated to the same BSS. The requesting STA may use the Location Service State field in the Location Service Parameters sub-element to start or stop the service. For Location Status Refuse, the STA may send an alternate request.
2. Location Track Notification procedures
A STA configured by another STA as described in the previous section shall transmit Location Track Notification frames as shown in the informative diagram in Figure vXXX below. The diagram shows the STA was configured to transmit on 3 channels, 3 frames per channel.
[pic]
Figure vXXX: STA transmission on 3 channels, 3 frames per channel.
The STA transmits Location Track Notification frames based on the following parameters:
• Location Indication Channels
o This sub-element indicates the channels the STA shall transmit on during normal or motion intervals.
• Indication Multicast Address
o For non-IBSS networks, the STA shall transmit the Location Track Notification frames to the Indication Multicast Address field in the Location Indication Parameters sub-element configured by the Location Configuration Request frame.
o An AP shall discard any Location Track Notification frame received from a STA that does not match the Location Indication Multicast Address field value for the AP’s ESS.
o For IBSS networks, the STA shall transmit the Location Track Notification frames to the destination address of the STA that configured the STA using Location Configuration Request frames.
• Location Indication Interval
o When the STA is stationary or dot11MgmtOptionMotionDetectionEnabled is false, the following procedures are to be followed:
▪ For each normal interval, the STA shall transmit on each channel, the number Location Track Notification frames specified by the Normal number of frames per channel field.
o If dot11MgmtOptionMotionDetectionEnabled is true and the STA is in motion
▪ For each motion interval the STA shall transmit on each channel, the number Location Track Notification frames specified by the Motion number of frames per channel field.
• Tracking Duration
o The STA shall transmit Location Track Notification frames until the Tracking Duration duration is reached.
o The duration starts as soon as the STA sends a Configuration Location Response frame with a Location Status value of Success.
o If the Tracking Duration is non-zero value the STA shall transmit Location Track Notification Frames, based on the Normal and In-Motion Report Interval field values, until the duration ends.
o If the Tracking Duration is 0 the STA shall continuously transmit Location Track Notification frames as defined by Normal and In-Motion Report Interval field values until configured to stop sending the frames.
• Location Indication Broadcast Data Rate
o The STA shall transmit Location Track Notification frames at the data rate specified in this sub-element.
• Time Of Departure
o If dot11MgmtTODEnabled is true, the STA shall transmit this sub-element in the Location Track Notification frame.
o Note: The values of the fields in the Time of Departure sub-element are measured by the PHY in real-time, then passed without real-time requirements to the MAC via the TXSTATUS parameter of the PHY-TXSTATUS.confirm primitive.
• If there are multiple antennas and/or TXBF capability then the STA shall transmit using the most omni-directional mode possible.
If the STA being configured responds with a non-zero Location Status value (i.e Fail, Refused and Incapable), the STA that issued the original Location Configuration Request frame may accept the values returned by the Location Configuration Response frame. In that case, the configuring STA may issue an alternate Location Configuration Request frame that specifies the values in the Location Parameters element matching the ones returned by the STA in the Location Configuration Response frame.
11.20.5.5 Timing Measurement Procedure
If dot11MgmtOptionTimingMsmtEnabled is true, the Timing Measurement field in the Extended Capabilities element shall be set to 1 and the STA supports the Timing Measurement procedurethe STA supports the Timing Measurement procedure. A STA provides timing measurement values to a peer STA using the Timing Measurement public action frame. A receiving STA uses the timing values in the Timing Measurement public action frame to:
• estimate the location of the STA transmitting the action frame and
• estimate the offset of the locationlocal clock with respect to the clock of the STA transmitting the action frame.
Two Timing Measurement public action frames are required to be received by a STA from a peer STA in order for the receiving STA to determine the location and the clock-offset relative to the sender. The Follow On to Dialog Token field in the action frame is used in the second action frame to identify the first action frame and shall be set to the value of the Dialog Token from the first action frame.
If dot11MgmtOptionTimingMsmtEnabled is false the STA shall set the Timing Measurement field in the Extended Capabilities element to 0. As a result the STA does not support the Timing Measurement procedure. When a STA that does not support the Timing Measurement procedure receives a Timing Measurement public action frame it shall ignore the frame.
If dot11MgmtOptionTimingMsmtEnabled is false the STA does not support the Timing Measurement procedure or support for the Timing Measurement procedure is disabled. If dot11RRMTimingMsmtEnabled is false the STA receiving a Timing Measurement public action frame shall ignore the frame.
A STA that supports the location capability may send a Location Configuration Request frame to provide its own location information and location capability. The STA shall include a Location Descriptor sub-element in a Location Configuration Request frame to provide its location capability. The Location Descriptor value (Bit 4 to Bit 7) of 2 “CIVIC Preferred” or 3 “GEO Preferred” indicates that the STA is capable of supporting both CIVIC and GEO formats, but prefers the indicated format. The STA shall indicate the location resolution it can support with the Location Resolution Descriptor field in the Location Descriptor sub-element.
Location advertising procedures
An AP that advertises location capabilities shall set the Location bit to 1 in the Extended Capabilities element. If the Location bit is set to 0 then no location services are provided by the AP. If the location bit is set to 1 an AP may also follow these procedures:
* If the AP has its location configured in CIVIC format, as described by the Location Descriptor sub-element in 7.3.2.66.10 then the AP shall set the E911 CIVIC bit to 1.
* If the AP has its location configured in Geo format, as described by the Location Descriptor sub-element in 7.3.2.66.10 then the AP shall set the E911 Geo bit to 1.
A STA may advertise its location information to another STA. Advertisement is accomplished by including a Location Parameters information element in a Location Request, Location Configuration Request, Probe Response or Location Response frame. For the case of a Location Response frame the STA shall set the dialog token field to zero to indicate this frame is not in response to a corresponding Location Request frame. To advertise, the STA shall include both the Location Descriptor and Location Data sub-elements in the Location Parameters information element. The STA shall define the fields of the Location Descriptor sub-element as follows. The Location Descriptor shall indicate Local. The Location Descriptor subfields: Location Descriptor, Resolution Descriptor and Encoding Descriptor fields shall all be set to match the data contained in the Location Data sub-element. Depending on the options defined in the Location Descriptor, the STA may also include the Location Source Identifier sub-element.
Timing Offset Measurement Procedure
The Timing Offset Measurement procedure is used to synchronize the time and/or the frequency of clocks as needed by time difference of arrival for location and audio/video applications.
A STA may request a Timing Offset Measurement from another STA that supports Timing Offset Measurement. To request a Timing Offset Measurement, the STA shall send a Location Request frame with a Location Parameters information element that includes the Location Request Option sub-element to indicate that a Timing Offset Measurement is requested.
A STA that supports Timing Offset Measurement and receives Timing Offset Measurement request shall respond with Location Response frames that include a Timing Measurement sub-element and a Location Status sub-element indicating the result of the request. If the responding STA is not able to provide Timing Offset Measurement, the STA shall send a response with a Location Status sub-element that indicates Incapable.
12.3.4.3 PHY-SAP service primitives parameters
TGV editor: Insert the following entries into Table 12-3:
|TXSTATUS |PHY-TXSTART.confirm |A set of parameters |
12.3.5.5 PHY-TXSTART.confirm
12.3.5.5.1 Function
TGV editor: Change
This primitive is issued by the PHY to the local MAC entity to confirm the start of a transmission and to indicate parameters related to the start. The PHY will issue this primitive in response to every PHY-TXSTART.request primitive issued by the MAC sublayer.
12.3.5.5.2 Semantics of the service primitive
TGV editor: Change
The semantics of the primitive are as follows:
PHY-TXSTART.confirm(TXSTATUS)
The TXSTATUS represents a list of parameters that the local PHY entity provides to the MAC sublayer related to the transmission an MPDU. This vector contains both PLCP and PHY management parameters. The required PHY parameters are listed in 12.3.4.4 (presently none).
This primitive has no parameters.
12.3.5.5.3 When generated
TGV editor: Change
This primitive will be issued by the PHY to the MAC entity when the PHY has received a PHYTXSTART.
request from the MAC entity, frame transmission has begun, and the PHY is ready to begin accepting outgoing data octets from the MAC.
12.3.5.5.4 Effect of receipt
TGV editor: Change
The receipt of this primitive by the MAC entity will cause the MAC to start the transfer of data octets. Parameters in the TXSTATUS vector may be used locally or remotely after being incorporated into a transmitted frame in order to determine time-of-flight and hence range and/or location.
15.2.6 Transmit PLCP
TGV editor: Change, noting changes in diagrams
The transmit PLCP is shown in Figure 15-6.
[pic]
Figure 15-6—Transmit PLCP
In order to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity shall be in the
transmit state. Further, the PHY shall be set to operate at the appropriate channel through STA management
via the PLME. Other transmit parameters such as DATARATE, TX antenna, and TX power are set via the
PHY-SAP with the PHY-TXSTART.request(TXVECTOR) as described in 15.4.4.2.
Based on the status of CCA indicated by PHY-CCA.indicate, the MAC will assess that the channel is clear. A clear channel shall be indicated by PHY-CCA.indicate(IDLE). If the channel is clear, transmission of the
PPDU shall be initiated by issuing the PHY-TXSTART.request(TXVECTOR) primitive. The TXVECTOR
elements for the PHY-TXSTART.request are the PLCP header parameters SIGNAL (DATARATE),
SERVICE, and LENGTH, and the PMD parameters of TX_ANTENNA, and TXPWR_LEVEL and TIME_OF_DEPARTURE_REQUESTED. The PLCP header parameter LENGTH is calculated from the TXVECTOR element by multiplying by 8 for 1 Mb/s and by 4 for 2 Mb/s.
The PLCP shall issue PMD_ANTSEL, PMD_RATE, and PMD_TXPWRLVL primitives to configure the PHY. The PLCP shall then issue a PMD_TXSTART.request and the PHY entity shall immediately initiate data scrambling and transmission of the PLCP preamble based on the parameters passed in the PHYTXSTART.request primitive. The time required for transmit power-on ramp described in 15.4.7.7 shall be included in the PLCP SYNC field. If the MIB variables dot11MgmtOptionLocationTODImplemented and dot11MgmtOptionLocationTODEnabled exist and are set to TRUE and the TXVECTOR parameter TIME_OF_DEPARTURE_REQUESTED is TRUE then the PLCP shall issue a PHY_TXSTART.confirm(TXSTATUS) primitive to the MAC, forwarding the TIME_OF_DEPARTURE, TIME_OF_DEPARTURE _TOLERANCE and TIME_OF_DEPARTURE_UNITS parameters for the PMD_TXSTART.request within the TXSTATUS vector.
Once the PLCP preamble transmission is complete, data shall be exchanged between the MAC and the PHY by a series of PHY-DATA.request(DATA) primitives issued by the MAC and PHY-DATA.confirm primitives issued by the PHY. The modulation rate change, if any, shall be initiated with the first data symbol of the MPDU as described in 15.2.5. The PHY proceeds with MPDU transmission through a series of data octet transfers from the MAC. At the PMD layer, the data octets are sent in LSB-to-MSB order and presented to the PHY through PMD_DATA.request primitives. Transmission can be prematurely terminated by the MAC through the primitive PHY-TXEND.request. PHY-TXSTART shall be disabled by the issuance of the PHY-TXEND.request. Normal termination occurs after the transmission of the final bit of the last MPDU octet according to the number supplied in the TXVECTOR LENGTH field. The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHY-TXSTART
shall be disabled). It is recommended that chipping continue during power-down. Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive from the PHY.
A typical state machine implementation of the transmit PLCP is provided in Figure 15-7.
[pic]
Figure 15-7—PLCP transmit state machine
15.4.4.2 PMD_SAP peer-to-peer service primitive parameters
TGv Editor: Insert the following new rows at the end of Table 15-4—DSSS PMD_SAP peer-to-peer service primitives
|TIME_OF_DEPARTURE_REQUESTED |TXVECTOR |FALSE, TRUE. When TRUE, the MAC entity |
| | |requests that the PHY PLCP entity measure and|
| | |report time of departure parameters; when |
| | |FALSE, the MAC entity requests that the PHY |
| | |PLCP entity neither measure nor report time |
| | |of departure parameters |
|TIME_OF_DEPARTURE |TXSTATUS |0 to 232-1. The locally-measured time of the |
| | |PMD_TXSTART.request, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_TOLERANCE |TXSTATUS |1 to 216-1. The 95% tolerance of |
| | |TIME_OF_DEPARTURE, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_UNITS |TXSTATUS |Enumerated type: |
| | |TODU22: 1 / 1408 MHz |
| | |TODU20: 1 / 1280 MHz |
| | |TODU40: 1 / 2560 MHz |
| | |TODU16: 1 / 1000 MHz |
15.4.7 PMD transmit specifications
TGv Editor: Insert a new section after 15.4.7.9
15.4.7.10 Time of Departure accuracy test
The Time of Departure accuracy shall be better than TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH ns. The Time of Departure accuracy test is defined Annex VV with the following test parameters:
- MULTICHANNEL_BANDWIDTH is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x.
- FIRST_TRANSITION_FIELD is the SYNC field.
- SECOND_TRANSITION_FIELD is the SFD field.
- TRAINING_FIELD is the concatenation of the SYNC and SFD fields, using as its chip pulse a rectangular pulse of duration 1/ 11 MHz convolved with a brick-wall low pass filter of bandwidth 11 MHz
- TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH is 100 ns.
The Time of Departure accuracy test shall be performed by instrumentation capable of converting signals transmitted on one or more channels into a stream of complex samples at fs sample/s or more, with sufficient accuracy in terms of I/Q arm amplitude and phase balance, dc offsets, phase noise, etc. The minimum sampling rate fs is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x. A possible embodiment of such a setup is converting the signal to a low IF frequency with a microwave synthesizer, sampling the signal with a digital oscilloscope and decomposing it digitally into quadrature components. The sampled signal shall be processed in a manner similar to an actual time of arrival processor, according to the following steps, or an equivalent procedure:
a) Start of frame shall be detected.
b) Channel number, coarse and fine frequency offsets shall be estimated.
c) The packet shall be derotated according to estimated frequency offsets.
d) Transition from the SYNC field to the SFD field shall be detected, and fine timing
(with one sample resolution) shall be established.
e) The SYNC and SFD portions of the derotated signal shall be up-sampled to above 1 GHz.
f) The up-sampled signal shall be cross-correlated with a reference waveform of the SYNC and SFD fields. The reference waveform shall use as its chip pulse a rectangular pulse of duration 1/ 11 MHz convolved with a brick-wall low pass filter of bandwidth 11 MHz
g) The measured time of departure shall equal the time of the peak of the magnitude of the cross-correlation.
h) The reported and measured times of departure shall be recorded, and the reported time of departure tolerance.
i) Steps a) to h) shall be repeated for at least 4 packets within 1 second. Time of departure errors shall be calculated as the RMS deviation of the reported values from estimated values. The estimated values shall be determined using the weighted least squares line of best fit, where the X, Y and weight parameters shall be the measured times of departure, the reported times of departure and half the reported tolerances respectively.
j) Step i) shall be repeated 500 times.
k) The Time of Departure accuracy test is passed if 95% or more of the time of departure errors are less than their reported time of departure tolerances, and 95% of the reported time of departure tolerances are less than 2 ns.
Note: One implementation of a time of departure measurement system is a free-running oscillator clocking (a) the digital-to-analog converter(s) used to transmit the packet, (b) a 32-bit continuously-counting counter and (c) a hardware finite state machine such that PMD_TXSTART.request causes a transition within the FSM which in turn causes frame transmission at the DACs a fixed number of cycles later; where the time of departure is recorded as the value of the counter at that transition. In this implementation, the principal source of time of departure error is only short term oscillator imperfection (e.g. phase noise).
17.2.2 TXVECTOR parameters
TGV editor: Insert one new row at the end of Table 17-1—TXVECTOR parameters
|TIME_OF_DEPARTURE_REQUESTED |PHY-TXSTART.request(TXVECTOR) |FALSE, TRUE. When TRUE, the MAC entity |
| | |requests that the PHY PLCP entity measure |
| | |and report time of departure parameters; |
| | |when FALSE, the MAC entity requests that |
| | |the PHY PLCP entity neither measure nor |
| | |report time of departure parameters |
TGV editor: Insert new section after 17.2.2.4
17.2.2.5 TIME_OF_DEPARTURE_REQUESTED
The allowed values are FALSE or TRUE. A parameter value of TRUE indicates that the MAC sublayer is requesting that the PLCP entity provide time of departure measurement and reporting in the PHY-TXSTART.confirm(TXSTATUS) primitive. A parameter value of FALSE indicates that the MAC sublayer is requesting that the PLCP entity not provide time of departure measurement nor reporting in the PHY-TXSTART.confirm(TXSTATUS) primitive.
TGV editor: Insert new section after 17.2.3
17.2.4 TXSTATUS parameters
The parameters listed in Table 17-2a are defined as part of the TXSTATUS parameter list in the
PHY-TXSTART.confirm service primitive.
Table 17-2a—TXSTATUS parameters
|Parameter |Associate Primitive |Value |
|TIME_OF_DEPARTURE |TXSTART.confirm(TXSTATUS) |0 to 232-1. The locally-measured time of the |
| | |PMD_TXSTART.request, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_TOLERANCE |TXSTART.confirm(TXSTATUS) |1 to 216-1. The 95% tolerance of |
| | |TIME_OF_DEPARTURE, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_UNITS |TXSTART.confirm(TXSTATUS) |Enumerated type: |
| | |TODU22: 1 / 1408 MHz |
| | |TODU20: 1 / 1280 MHz |
| | |TODU40: 1 / 2560 MHz |
17.2.4.1 TXSTATUS TIME_OF_DEPARTURE
The allowed values for the TIME_OF_DEPARTURE parameter are integers in the range of 0 to 232-1 This parameter is used to indicate the time of departure of the last transmitted frame initiated by the most recent PHY-TXSTART.request in units given by TIME_OF_DEPARTURE_UNITS. TIME_OF_DEPARTURE may be used locally or remotely after being incorporated into a transmitted frame in order to determine time-of-flight and hence range and/or location.
The allowed values for the TIME_OF_DEPARTURE parameter are integers in the range of 0 to 232-1 This parameter is used to indicate the time of departure of the last transmitted frame in units given by TIME_OF_DEPARTURE_UNITS. TIME_OF_DEPARTURE may be used locally or remotely after being incorporated into a transmitted frame in order to determine time-of-flight and hence range and/or location.
17.2.4.2 TXSTATUS TIME_OF_DEPARTURE_TOLERANCE
The allowed values for the TIME_OF_DEPARTURE_TOLERANCE parameter are integers in the range of 1 to 216-1 This parameter is used to indicate the 95% tolerance of the TIME_OF_DEPARTURE in units given by TIME_OF_DEPARTURE_UNITS. TIME_OF_DEPARTURE_TOLERANCE may be used locally or remotely after being incorporated into a transmitted frame in order to determine time-of-flight and hence range and/or location.
17.2.4.3 TXSTATUS TIME_OF_DEPARTURE_UNITS
TIME_OF_DEPARTURE_UNITS indicates the units used for TIME_OF_DEPARTURE and TIME_OF_TOLERANCE. The allowed values for TIME_OF_DEPARTURE_UNITS are TODU22 (1 / 1408 MHz), TODU20 (1 / 1280 MHz) and , TODU40 (1 / 2560 MHz) and TODU16 (1 / 1000 MHz)..
17.3.9 PMD transmit specifications
TGv Editor: Insert a new section after 17.3.9.7
17.3.9.8 Time of Departure accuracy test
The Time of Departure accuracy shall be better than TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH ns. The Time of Departure accuracy test is defined Annex VV with the following test parameters:
- MULTICHANNEL_BANDWIDTH is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x.
- FIRST_TRANSITION_FIELD is the Short symbols.
- SECOND_TRANSITION_FIELD is the Long symbols.
- TRAINING_FIELD is the Long symbols windowed by the windowing described in 17.3.2.4 with TTR = 100 ns for 20 MHz channel spacing, TTR = 200 ns for 10 MHz channel spacing and TTR = 400 ns for 5 MHz channel spacing.
- TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH is 100 ns.
The Time of Departure accuracy test shall be performed by instrumentation capable of converting signals transmitted on one or more channels into a stream of complex samples at fs sample/s or more, with sufficient accuracy in terms of I/Q arm amplitude and phase balance, dc offsets, phase noise, etc. For 20 MHz channel spacing, the minimum sampling rate fs is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x. A possible embodiment of such a setup is converting the signal to a low IF frequency with a microwave synthesizer, sampling the signal with a digital oscilloscope and decomposing it digitally into quadrature components. The sampled signal shall be processed in a manner similar to an actual time of arrival processor, according to the following steps, or an equivalent procedure:
a) Start of frame shall be detected.
b) Channel number, coarse and fine frequency offsets shall be estimated.
c) The packet shall be derotated according to estimated frequency offsets.
d) Transition from the short symbols to the long symbols shall be detected, and fine timing (with one sample resolution) shall be established.
e) The long symbols of the derotated signal shall be up-sampled to above 1 GHz.
f) The up-sampled signal shall be cross-correlated with a reference waveform of the long symbols. The reference waveform shall use as its windowing the windowing described in 17.3.2.4 with TTR = 100 ns for 20 MHz channel spacing, TTR = 200 ns for 10 MHz channel spacing and TTR = 400 ns for 5 MHz channel spacing.
g) The measured time of departure shall equal the time of the peak of the magnitude of the cross-correlation.
h) The reported and measured times of departure shall be recorded, and the reported time of departure tolerance.
i) Steps a) to h) shall be repeated for at least 4 packets within 1 second. Time of departure errors shall be calculated as the RMS deviation of the reported values from estimated values. The estimated values shall be determined using the weighted least squares line of best fit, where the X, Y and weight parameters shall be the measured times of departure, the reported times of departure and half the reported tolerances respectively.
j) Step i) shall be repeated 500 times.
k) The Time of Departure accuracy test is passed if 95% or more of the time of departure errors are less than their reported time of departure tolerances, and 95% of the reported time of departure tolerances are less than 2 ns.
Note: One implementation of a time of departure measurement system is a free-running oscillator clocking (a) the digital-to-analog converter(s) used to transmit the packet, (b) a 32-bit continuously-counting counter and (c) a hardware finite state machine such that PMD_TXSTART.request causes a transition within the FSM which in turn causes frame transmission at the DACs a fixed number of cycles later; where the time of departure is recorded as the value of the counter at that transition. In this implementation, the principal source of time of departure error is only short term oscillator imperfection (e.g. phase noise).
17.3.11 Transmit PLCP
TGV editor: Change, noting changes in diagrams
The transmit PLCP is shown in Figure 17-14. In order to transmit data, PHY-TXSTART.request shall be
enabled so that the PHY entity shall be in the transmit state. Further, the PHY shall be set to operate at the
appropriate frequency through STA management via the PLME. Other transmit parameters, such as
DATARATE and TX power, are set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as
described in 17.2.2.
A clear channel shall be indicated by PHY-CCA.indicate(IDLE). The MAC considers this indication before
issuing the PHY-TXSTART.request. Transmission of the PPDU shall be initiated after receiving the PHYTXSTART.
request(TXVECTOR) primitive. The TXVECTOR elements for the PHY-TXSTART.request
are the PLCP header parameters DATARATE, SERVICE, and LENGTH, and the PMD parameters
TXPWR_LEVEL and TIME_OF_DEPARTURE_REQUESTED.
The PLCP shall issue PMD_TXPWRLVL and PMD_RATE primitives to configure the PHY. The PLCP
shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble and PLCP header,
based on the parameters passed in the PHY-TXSTART.request primitive, shall be immediately initiated. If the MIB variables dot11MgmtOptionLocationTODImplemented and dot11MgmtOptionLocationTODEnabled exist and are set to TRUE and the TXVECTOR parameter TIME_OF_DEPARTURE_REQUESTED is TRUE then the PLCP shall issue a PHY_TXSTART.confirm(TXSTATUS) primitive to the MAC, forwarding the TIME_OF_DEPARTURE, TIME_OF_DEPARTURE _TOLERANCE and TIME_OF_DEPARTURE_UNITS parameters for the PMD_TXSTART.request within the TXSTATUS vector.
Once PLCP preamble
transmission is started, the PHY entity shall immediately initiate data scrambling and data encoding.
The
scrambled and encoded data shall then be exchanged between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the MAC, and PHY-DATA.confirm primitives issued by
the PHY. The modulation rate change, if any, shall be initiated from the SERVICE field data of the PLCP
header, as described in 17.3.2.
The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The
PLCP header parameter, SERVICE, and PSDU are encoded by the convolutional encoder with the
bit-stealing function described in 17.3.5.5. At the PMD layer, the data octets are sent in bit 0–7 order and
presented to the PHY through PMD_DATA.request primitives. Transmission can be prematurely terminated
by the MAC through the primitive PHY-TXEND.request. PHY-TXSTART shall be disabled by the issuance
of the PHY-TXEND.request. Normal termination occurs after the transmission of the final bit of the last
PSDU octet, according to the number supplied in the OFDM PHY preamble LENGTH field.
[pic]
Figure 17-14—Transmit PLCP
The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART
shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm
primitive from the PHY. If the coded PSDU (C-PSDU) is not multiples of the OFDM symbol, bits shall be
stuffed to make the C-PSDU length multiples of the OFDM symbol.
In the PMD, the GI shall be inserted in every OFDM symbol as a countermeasure against severe delay
spread.
A typical state machine implementation of the transmit PLCP is provided in Figure 17-15. Requests (.req)
and confirmations(.confirm) are issued once with designated states.
[pic]
Figure 17-15—PLCP transmit state machine
18.2.5 Transmit PLCP
TGV editor: Change, noting changes in diagrams
The transmit procedures for a High Rate PHY using the long PLCP preamble and header are the same as the
transmit procedures described in 15.2.6 and 15.2.7 and do not change apart from the ability to transmit
5.5 Mb/s and 11 Mb/s.
The procedures for a transmitter employing HR/DSSS/short and HR/DSSS/PBCC/short are the same except
for length and rate changes. The decision to use a long or short PLCP is beyond the scope of this standard.
The transmit PLCP is shown in Figure 18-7.
A PHY-TXSTART.request(TXVECTOR) primitive will be issued by the MAC to start the transmission
of a PPDU. In addition to parameters DATARATE and LENGTH, other transmit parameters
such as PREAMBLE_TYPE and MODULATION are set via the PHY-SAP with the
PHY-TXSTART.request(TXVECTOR), as described in 18.3.5. The SIGNAL, SERVICE, and LENGTH
fields of the PLCP header are calculated as described in 18.2.3.
The PLCP shall issue PMD_ANTSEL, PMD_RATE, and PMD_TXPWRLVL primitives to configure the
PHY. The PLCP shall then issue a PMD_TXSTART.request, and the PHY entity shall immediately initiate
data scrambling and transmission of the PLCP preamble based on the parameters passed in the
PHY-TXSTART.request primitive. The time required for transmit power-on ramp, described in 18.4.7.6,
shall be included in the PLCP SYNC field. If the MIB variables dot11MgmtOptionLocationTODImplemented and dot11MgmtOptionLocationTODEnabled exist and are set to TRUE and the TXVECTOR parameter TIME_OF_DEPARTURE_REQUESTED is TRUE then the PLCP shall issue a PHY_TXSTART.confirm(TXSTATUS) primitive to the MAC, forwarding the TIME_OF_DEPARTURE, TIME_OF_DEPARTURE _TOLERANCE and TIME_OF_DEPARTURE_UNITS parameters for the PMD_TXSTART.request within the TXSTATUS vector.
Once the PLCP preamble transmission is complete, data shall be
exchanged between the MAC and the PHY by a series of PHY-DATA.request(DATA) primitives issued by
the MAC and PHY-DATA.confirm primitives issued by the PHY. The modulation and rate change, if any,
shall be initiated with the first data symbol of the PSDU, as described in 18.2.3.7 and 18.2.3.14. The PHY
proceeds with PSDU transmission through a series of data octet transfers from the MAC. At the PMD layer,
the data octets are sent in LSB-to-MSB order and presented to the PHY through PMD_DATA.request
primitives. Transmission can be prematurely terminated by the MAC through the primitive
PHY-TXEND.request. PHY-TXSTART shall be disabled by the issuance of the PHY-TXEND.request.
Normal termination occurs after the transmission of the final bit of the last PSDU octet, calculated from the
number supplied in the PHY preamble LENGTH and SERVICE fields using the equations specified in
18.2.3.5. The PPDU transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHY-TXSTART shall be disabled). It is recommended that modulation continue during power-down to
prevent radiating a continuous wave carrier. Each PHY-TXEND.request is acknowledged with a
PHY-TXEND.confirm primitive from the PHY.
[pic]
Figure 18-7—Transmit PLCP
A typical state machine implementation of the transmit PLCP is provided in Figure 18-8.
[pic]
Figure 18-8—PLCP transmit state machine
18.3.5 Vector descriptions
TGv Editor: Insert the following new rows at the end of Table 18-6—Parameter vectors
|TIME_OF_DEPARTURE_REQUESTED |TXVECTOR |FALSE, TRUE. When TRUE, the MAC entity |
| | |requests that the PHY PLCP entity measure and|
| | |report time of departure parameters; when |
| | |FALSE, the MAC entity requests that the PHY |
| | |PLCP entity neither measure nor report time |
| | |of departure parameters |
|TIME_OF_DEPARTURE |TXSTATUS |0 to 232-1. The locally-measured time of the |
| | |PMD_TXSTART.request, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_TOLERANCE |TXSTATUS |1 to 216-1. The 95% tolerance of |
| | |TIME_OF_DEPARTURE, in units of |
| | |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_UNITS |TXSTATUS |Enumerated type: |
| | |TODU22: 1 / 1408 MHz |
| | |TODU20: 1 / 1280 MHz |
| | |TODU40: 1 / 2560 MHz |
| | |TODU16: 1 / 1000 MHz |
18.4.7 PMD transmit specifications
TGv Editor: Insert a new section after 18.4.7.8
18.4.7.9 Time of Departure accuracy
The Time of Departure accuracy shall be better than TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH ns. The Time of Departure accuracy test is defined Annex VV with the following test parameters:
- MULTICHANNEL_BANDWIDTH is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x.
- FIRST_TRANSITION_FIELD is the SYNC field.
- SECOND_TRANSITION_FIELD is the SFD field.
- TRAINING_FIELD is the concatenation of the appropriate short or long SYNC and SFD fields, using as its chip pulse a rectangular pulse of duration 1/ 11 MHz convolved with a brick-wall low pass filter of bandwidth 11 MHz
- TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH is 100 ns.
18.4.7.9 Time of Departure accuracy test
The Time of Departure accuracy test shall be performed by instrumentation capable of converting signals transmitted on one or more channels into a stream of complex samples at fs sample/s or more, with sufficient accuracy in terms of I/Q arm amplitude and phase balance, dc offsets, phase noise, etc. The minimum sampling rate fs is [pic] sample/s where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x. A possible embodiment of such a setup is converting the signal to a low IF frequency with a microwave synthesizer, sampling the signal with a digital oscilloscope and decomposing it digitally into quadrature components. The sampled signal shall be processed in a manner similar to an actual time of arrival processor, according to the following steps, or an equivalent procedure:
a) Start of frame shall be detected.
b) Channel number, coarse and fine frequency offsets shall be estimated.
c) The packet shall be derotated according to estimated frequency offsets.
d) Transition from the SYNC field to the SFD field shall be detected, and fine timing
(with one sample resolution) shall be established.
e) The type (short or long) of preamble shall be determined
f) The SYNC and SFD portions of the derotated signal shall be up-sampled to above 1 GHz.
g) The up-sampled signal shall be cross-correlated with a reference waveform of the appropriate short or long SYNC and SFD fields. The reference waveform shall use as its chip pulse a rectangular pulse of duration 1/ 11 MHz convolved with a brick-wall low pass filter of bandwidth 11 MHz
h) The measured time of departure shall equal the time of the peak of the magnitude of the cross-correlation.
i) The reported and measured times of departure shall be recorded, and the reported time of departure tolerance.
j) Steps a) to i) shall be repeated for at least 4 packets within 1 second. Time of departure errors shall be calculated as the RMS deviation of the reported values from estimated values. The estimated values shall be determined using the weighted least squares line of best fit, where the X, Y and weight parameters shall be the measured times of departure, the reported times of departure and half the reported tolerances respectively.
k) Step j) shall be repeated 500 times.
l) The Time of Departure accuracy test is passed if 95% or more of the time of departure errors are less than their reported time of departure tolerances, and 95% of the reported time of departure tolerances are less than 2 ns.
Note: One implementation of a time of departure measurement system is a free-running oscillator clocking (a) the digital-to-analog converter(s) used to transmit the packet, (b) a 32-bit continuously-counting counter and (c) a hardware finite state machine such that PMD_TXSTART.request causes a transition within the FSM which in turn causes frame transmission at the DACs a fixed number of cycles later; where the time of departure is recorded as the value of the counter at that transition. In this implementation, the principal source of time of departure error is only short term oscillator imperfection (e.g. phase noise).
19.2 PHY-specific service parameter list
TGV editor: Insert one new row at the end of Table 17-1—TXVECTOR parameters
|TIME_OF_DEPARTURE_REQUESTED |FALSE, TRUE. When TRUE, the |
| |MAC entity requests that the |
| |PHY PLCP entity measure and |
| |report time of departure |
| |parameters; when FALSE, the |
| |MAC entity requests that the |
| |PHY PLCP entity neither |
| |measure nor report time of |
| |departure parameters |
19.2 PHY-specific service parameter list
TGv editor: change
The architecture of the IEEE 802.11 MAC is intended to be PHY independent. Some PHY implementations
require PHY-dependent MAC state machines running in the MAC sublayer in order to meet certain PMD
requirements. The PHY-dependent MAC state machine resides in a sublayer defined as the MLME. In
certain PMD implementations, the MLME may need to interact with the PLME as part of the normal PHY
SAP primitives. These interactions are defined by the PLME parameter list currently defined in the PHY
service primitives as TXVECTOR, TXSTATUS and RXVECTOR. The list of these parameters and the values they may
represent are defined in the specific PHY specifications for each PMD. This subclause addresses the
TXVECTOR, TXSTATUS and RXVECTOR for the ERP. The service parameters for RTXVECTOR, TXSTATUS and TRXVECTOR
shall follow 17.2.2, 17.2.4 and 17.2.3, respectively.
Several service primitives include a parameter vector. DATARATE and LENGTH are described in 12.3.4.4.
The remaining parameters are considered to be management parameters and are specific to this PHY.
The parameters in Table 19-1 are defined as part of the TXVECTOR parameter list in the PHYTXSTART.
request service and PLME_TXTIME.request primitives.
The parameters in Table 19-1a are defined as part of the TXSTATUS parameter list in the PHYTXSTART.
confirm service primitive.
TGv Editor: Insert the following new table after table 19-1
Table 19-1a: TXSTATUS parameters
|Parameter |Value |
|TIME_OF_DEPARTURE |0 to 232-1. The locally-measured time of the |
| |PMD_TXSTART.request, in units of |
| |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_TOLERANCE |1 to 216-1. The 95% tolerance of |
| |TIME_OF_DEPARTURE, in units of |
| |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_UNITS |Enumerated type: |
| |TODU22: 1 / 1408 MHz |
| |TODU20: 1 / 1280 MHz |
| |TODU40: 1 / 2560 MHz |
| |TODU16: 1 / 1000 MHz |
19.4.7 PMD transmit specifications
TGV editor: Change:
The PMD transmit specifications shall follow 17.3.9 with the exception of the transmit power level
(17.3.9.1), the transmit center frequency tolerance (17.3.9.4), and the symbol clock frequency tolerance
(17.3.9.5), and the time of departure accuracy test (17.3.9.8). Regulatory requirements may have an effect on the combination of maximum transmit power and spectral mask if the resulting signals violate restricted band emission limits.
TGv Editor: Insert a new section after 19.4.7.3
19.4.7.4 Time of Departure accuracy test
The time of departure specifications shall follow 17.3.9.8 for PPDUs transmitted using ERP-OFDM format and 18.4.7.9 for PPDUs transmitted using ERP-DSSS/CCK, ERP-PBCC and DSSS-OFDM formats.
20.2.1 Introduction
TGv Editor: Change
The PHY interfaces to the MAC through the TX_VECTOR, TXSTATUS, RX_VECTOR, and the
PHYCONFIG_VECTOR. The TX_VECTOR supplies the PHY with per packet transmit parameters. Status of the transmission is reported from PHY to MAC by parameters within TXSTATUS. Using
the RX_VECTOR, the PHY informs the MAC of the received packet parameters. Using the
PHYCONFIG_VECTOR, the MAC configures the PHY for operation, independent of frame transmission or
reception.
20.2.2 TXVECTOR parameters
TGV editor: Insert one new row at the end of Table 20-1—TXVECTOR and RXVECTOR parameters
|TIME_OF_DEPARTURE_REQUESTED | |Enumerated type: |O |N |
| | |TRUE indicates that the | | |
| | |MAC entity requests that | | |
| | |the PHY PLCP entity | | |
| | |measure and report time of| | |
| | |departure parameters. | | |
| | |FALSE indicates that the | | |
| | |MAC entity requests that | | |
| | |the PHY PLCP entity | | |
| | |neither measure nor report| | |
| | |time of departure | | |
| | |parameters | | |
20.2.4 Support for NON_HT formats
TGV editor: Insert new row immediately before the last row (i.e. Note row) of Table 20-3—Mapping of the HT PHY parameters for NON_HT operation
|TIME_OF_DEPARTURE_REQUESTED |TIME_OF_DEPARTURE_REQUESTED |TIME_OF_DEPARTURE_REQUESTED |TIME_OF_DEPARTURE_REQUESTED |TIME_OF_DEPARTURE_REQUESTED |
TGV editor: Insert new section after 20.2.4
20.2.5 TXSTATUS parameters
The parameters listed in Table 20-3a are defined as part of the TXSTATUS parameter list in the
PHY-TXSTART.confirm(TXSTATUS) service primitive.
Table 20-3a—TXSTATUS parameters
|Parameter |Value |
|TIME_OF_DEPARTURE |0 to 232-1. The locally-measured time of the |
| |PMD_TXSTART.request, in units of |
| |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_TOLERANCE |1 to 216-1. The 95% tolerance of |
| |TIME_OF_DEPARTURE, in units of |
| |TIME_OF_DEPARTURE_UNITS. |
|TIME_OF_DEPARTURE_UNITS |Enumerated type: |
| |TODU22: 1 / 1408 MHz |
| |TODU20: 1 / 1280 MHz |
| |TODU40: 1 / 2560 MHz |
| |TODU16: 1 / 1000 MHz |
20.3.21 PMD transmit specification
TGv Editor: Insert a new section after 20.3.21.7
20.3.21.8 Time of Departure accuracy test
The Time of Departure accuracy shall be better than an TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH ns. The Time of Departure accuracy test is defined Annex VV with the following test parameters:
- MULTICHANNEL_BANDWIDTH is [pic] sample/s (for a CH_BANDWIDTH parameter equal to HT_CBW20) or [pic] sample/s (for a CH_BANDWIDTH parameter equal to HT_CBW40) where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x.
- FIRST_TRANSITION_FIELD is L-STF (for HT-mixed format) or HT-GF-STF (for HT-greenfield format)
- SECOND_TRANSITION_FIELD is L-LTF (for HT-mixed format) or HT-GF-LTF1 (for HT-greenfield format)
- TRAINING_FIELD is L-LTF (for HT-mixed format) or HT-LTF1 (for HT-greenfield format) windowed by the windowing described in 17.3.2.4 with TTR = 100 ns.
- TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH is 100 ns (for a CH_BANDWIDTH parameter equal to HT_CBW20) or 100 ns (for a CH_BANDWIDTH parameter equal to HT_CBW40).
The Time of Departure accuracy test shall be performed by instrumentation capable of converting signals transmitted on one or more channels into a stream of complex samples at fs sample/s or more, with sufficient accuracy in terms of I/Q arm amplitude and phase balance, dc offsets, phase noise, etc. For a CH_BANDWIDTH parameter equal to HT_CBW20 or HT_CBW40, the minimum sampling rate fs is [pic] or [pic] sample/s respectively, where fH is the nominal center frequency in Hz of the highest channel, fL is the nominal center frequency in Hz of the lowest channel, and [pic] equals the smallest integer equal to or larger than x. A possible embodiment of such a setup is converting the signal to a low IF frequency with a microwave synthesizer, sampling the signal with a digital oscilloscope and decomposing it digitally into quadrature components. The sampled signal shall be processed in a manner similar to an actual time of arrival processor, according to the following steps, or an equivalent procedure:
a) Start of frame shall be detected.
b) Channel number, coarse and fine frequency offsets shall be estimated.
c) The packet shall be derotated according to estimated frequency offsets.
d) For HT-mixed format, the transition from the L-STF to the L-LTF shall be detected; for HT-greenfield format, the transition from the HT-GF-STF to the HT-GF-LTF1 shall be detected; and in either case fine timing (with one sample resolution) shall be established.
e) The L-LTF or HT-LTF1 of the derotated signal shall be up-sampled to above 1 GHz.
f) The up-sampled signal shall be cross-correlated with a reference waveform of the L-LTF (for HT-mixed format) or HT-LTF1 (for HT-greenfield format). The reference waveform shall use as its windowing the windowing described in 17.3.2.4 with TTR = 100 ns.
g) The measured time of departure shall equal the time of the peak of the magnitude of the cross-correlation.
h) The reported and measured times of departure shall be recorded, and the reported time of departure tolerance.
i) Steps a) to h) shall be repeated for at least 4 packets with the same CH_BANDWIDTH parameter within 1 second. Time of departure errors shall be calculated as the RMS deviation of the reported values from estimated values. The estimated values shall be determined using the weighted least squares line of best fit, where the X, Y and weight parameters shall be the measured times of departure, the reported times of departure and half the reported tolerances respectively.
j) Step i) shall be repeated 500 times with the same CH_BANDWIDTH parameter.
k) The Time of Departure accuracy test for the tested CH_BANDWIDTH parameter is passed if 95% or more of the time of departure errors are less than their reported time of departure tolerances, and 95% of the reported time of departure tolerances are less than i) 2 ns if the CH_BANDWIDTH parameter equals HT_CBW20, or ii) 1 ns if the CH_BANDWIDTH parameter equals HT_CBW40.
Note: One implementation of a time of departure measurement system is a free-running oscillator clocking (a) the digital-to-analog converter(s) used to transmit the packet, (b) a 32-bit continuously-counting counter and (c) a hardware finite state machine such that PMD_TXSTART.request causes a transition within the FSM which in turn causes frame transmission at the DACs a fixed number of cycles later; where the time of departure is recorded as the value of the counter at that transition. In this implementation, the principal source of time of departure error is only short term oscillator imperfection (e.g. phase noise).
20.3.23 Transmit PLCP
TGV editor: Change, noting changes in diagrams
There are three options for transmit PLCP procedure. The first two options, for which typical transmit procedures
are shown in Figure 20-20 and Figure 20-21, are selected if the FORMAT field of PHY-TXSTART.request(
TXVECTOR) is set to HT_MF or HT_GF, respectively. These transmit procedures do not describe the
operation of optional features, such as LDPC or STBC. The third option is to follow the transmit procedure
as in Clause 17 or Clause 19 if the FORMAT field is set to NON_HT. Additionally, if the FORMAT field is
set to NON_HT, CH_BANDWIDTH indicates NON_HT_CBW20, and NON_HT_MODULATION indicates
OFDM, follow the transmit procedure as in Clause 17. If the FORMAT field is set to NON_HT,
CH_BANDWIDTH indicates NON_HT_CBW20, and NON_HT_MODULATION indicates other than
OFDM, follow the transmit procedure as in Clause 19. And furthermore, if the FORMAT field is set to
NON_HT and CH_BANDWIDTH indicates NON_HT_CBW40, follow the transmit procedure as in Clause
17, except that the signal in Clause 17 is generated simultaneously on each of the upper and lower 20 MHz
channels that comprise the 40 MHz channel as defined in 20.3.8 and 20.3.11.11. In all these options, in order
to transmit data, PHY-TXSTART.request shall be enabled so that the PHY entity shall be in the transmit state.
Further, the PHY shall be set to operate at the appropriate frequency through station management via the
PLME, as specified in 20.4. Other transmit parameters, such as MCS Coding types and transmit power, are
set via the PHY-SAP with the PHY-TXSTART.request(TXVECTOR), as described in 20.2.2.
A clear channel shall be indicated by PHY-CCA.indication(IDLE). Note - under some circumstances, the
MAC uses the latest value of PHY-CCA.indication before issuing the PHY-TXSTART.request. Transmission
of the PPDU shall be initiated after receiving the PHYTXSTART.request(TXVECTOR) primitive. The
TXVECTOR elements for the PHY-TXSTART.request are specified in Table 20-1.
The PLCP shall issue the parameters in the following PMD primitives to configure the PHY:
— PMD_TXPWRLVL
— PMD_TX_PARAMETERS
The PLCP shall then issue a PMD_TXSTART.request, and transmission of the PLCP preamble may start if TIME_OF_DEPARTURE_REQUESTED is FALSE, and shall start immediately if TIME_OF_DEPARTURE_REQUESTED is FALSETRUE,
based on the parameters passed in the PHY-TXSTART.request primitive. If the MIB variables dot11MgmtOptionLocationTODImplemented and dot11MgmtOptionLocationTODEnabled exist and are set to TRUE and the TXVECTOR parameter TIME_OF_DEPARTURE_REQUESTED is TRUE then the PLCP shall issue a PHY_TXSTART.confirm(TXSTATUS) primitive to the MAC, forwarding the TIME_OF_DEPARTURE, TIME_OF_DEPARTURE _TOLERANCE and TIME_OF_DEPARTURE_UNITS parameters for the PMD_TXSTART.request within the TXSTATUS vector.
The data shall then be exchanged
between the MAC and the PHY through a series of PHY-DATA.request(DATA) primitives issued by the
MAC, and PHY-DATA.confirm primitives issued by the PHY. Once PLCP preamble transmission is started,
the PHY entity shall immediately initiate data scrambling and data encoding. The encoding method shall be
based on the FEC_CODING, CH_BANDWIDTH, and MCS parameter of the TXVECTOR. A modulation
rate change, if any, shall be initiated starting with the SERVICE field data, as described in 20.3.2.
The PHY proceeds with PSDU transmission through a series of data octet transfers from the MAC. The SERVICE
field and PSDU are encoded by the encoder selected by the FEC_CODING, CH_BANDWIDTH, and
MCS parameters of the TXVECTOR as described in 20.3.3. At the PMD layer, the data octets are sent in bit
0–7 order and presented to the PHY through PMD_DATA.request primitives. Transmission can be prematurely
terminated by the MAC through the primitive PHY-TXEND.request. PHY-TXSTART shall be disabled
by receiving a PHY-TXEND.request. Normal termination occurs after the transmission of the final bit
of the last PSDU octet, according to the number supplied in the LENGTH field.
The packet transmission shall be completed and the PHY entity shall enter the receive state (i.e., PHYTXSTART
shall be disabled). Each PHY-TXEND.request is acknowledged with a PHY-TXEND.confirm primitive
from the PHY. If the length of the coded PSDU (C-PSDU) is not an integer multiple of the OFDM
symbol length, bits shall be stuffed to make the C-PSDU length an integer multiple of the OFDM symbol
length.
In the PMD, the GI or short GI shall be inserted in every OFDM symbol as a countermeasure against delay
spread.
A typical state machine implementation of the transmit PLCP is provided in Figure 20-22. Requests (.req)
and confirmations(.confirm) are issued once per state as shown. This state machine does not describe the operation
of optional features, such as LDPC or STBC.
[pic]
Figure 20-20—PLCP transmit procedure (HT-mixed format PPDU)
[pic]
Figure 20-21—PLCP transmit procedure (HT-greenfield format PPDU)
[pic]
Figure 20-22—PLCP transmit state machine
Wireless Network Management extensions
|Item |Protocol Capability |References |Status |Support |
|WNM1 |Extended Capabilities element |7.3.2.62 |CFv:M |Yes, No, N/A |
|WNM2 |Management Diagnostic Alerts |11.20.2 |CFv:M |Yes, No, N/A |
| WNM2.1 | Measurement Request frame |7.4.5.1 |CFv:M |Yes, No, N/A |
| WNM2.2 | Measurement Report frame |7.4.5.2 |CFv:M |Yes, No, N/A |
| WNM2.3 | Protocol for Triggered Measurements |11.10.7 |CFv:M |Yes, No, N/A |
| WNM2.4 | Triggered STA Statistics Reporting |7.3.2.21.8, |CFv:M |Yes, No, N/A |
| | |7.3.2.22.8, | | |
| | |11.10.8.5 | | |
| WNM2.5 | Triggered QoS Metrics Reporting |7.3.2.21.10, | (CFv AND CF12):O |Yes, No, N/A |
| | |7.3.2.22.10, | | |
| | |11.11.9.8 | | |
| WNM2.6 | Multicast Diagnostics Reporting |7.3.2.21.10a, |CFv:M |Yes, No, N/A |
| | |7.3.2.22.10a, | | |
| | |11.20.2 | | |
|WNM3 |Event |11.20.3 |CFv:M |Yes, No, N/A |
| WNM3.1 | Event Request |7.3.2.62, |(CFv AND CF1):M |Yes, No, N/A |
| | |7.4.11.1 | | |
| WNM3.2 | Event Report |7.3.2.63, |(CFv AND CF12):M |Yes, No, N/A |
| | |7.4.11.2 | | |
|WNM4 |Diagnostic |11.20.4 |CFv:M |Yes, No, N/A |
| WNM4.1 | Diagnostic Request |7.3.2.64, |(CFv AND CF1):M |Yes, No, N/A |
| | |7.4.11.3 | | |
| WNM4.2 | Diagnostic Report |7.3.2.65, | (CFv AND CF12):M |Yes, No, N/A |
| | |7.4.11.4 | | |
|WNM4.3 |Manufacturer Information STA Report |7.3.2.65.2, |CFv:M |Yes, No, N/A |
| |Diagnostic Type |11.20.4.3 | | |
|WNM4.4 |Configuration Profile Diagnostic Type |7.3.2.65.3, |CFv:M |Yes, No, N/A |
| | |11.20.4.2 | | |
|WNM4.5 |Association Diagnostic Type |7.3.2.64.2, |CFv:M |Yes, No, N/A |
| | |7.3.2.65.4, | | |
| | |11.20.4.4 | | |
|WNM4.6 |802.1X Authentication Diagnostic Type |7.3.2.64.3, |(CFv AND PC34):O |Yes, No, N/A |
| | |7.3.2.65.4, | | |
| | |11.20.4.4 | | |
|WNM5 |Location |11.20.5, 7.3.2.66 |CFv:M |Yes, No, N/A |
|WNM5.1 |Location Request |7.4.11.5 |CFv:M |Yes, No, N/A |
|WNM5.2 |Location Response |7.4.11.6 |CFv:M |Yes, No, N/A |
|WNM5.1 |Location Civic Request/Report |11.10.8.9 |CFv:M | |
|WNM5.2 |Location Civic Report | |CFv:M | |
|WNM5.23 |Location Identifier Request/Report |11.10.8.10 |CFv:M | |
|WNM5.4 |Location Identifier Report | |CFv:M | |
|WNM5.35 |Location Track Notification |11.20.5.3 |CFv:OM | |
| | | | | |
|WNM5.35.1 |Time Of Departure Notifications | |CFv:O | |
| | | | | |
|WNM5.3.2 |Motion Detection Notifications | |CFv:O | |
|WNM5.463 |Location Configuration Request |7.4.11.7 |CFv:M |Yes, No, N/A |
|WNM5.56.1 | Normal Indication | |CFv:OM | |
|WNM5.56.2 | Motion Indication | |CFv:O | |
|WNM5.674 |Location Configuration Response |7.4.11.8 |CFv:M |Yes, No, N/A |
| WNM17 [ed note put |Timing Measurement |11.20.5.5 |CFv:O | |
|at end] | | | | |
|WNM6 |Multiple BSSID Support |11.20.6, 11.20.7 |CFv:O |Yes, No, N/A |
|WNM7 |BSS Transition Management |11.20.8 |CFv:M |Yes, No, N/A |
| WNM7.1 | Neighbor Report Element |7.3.2.37 |(CFv AND CF1):M |Yes, No, N/A |
| WNM7.2 | BSS Transition Management Query |7.4.11.9 |(CFv AND CF1):M |Yes, No, N/A |
| WNM7.3 | BSS Transition Management Request |7.4.11.10 | (CFv AND CF12):M |Yes, No, N/A |
| WNM7.4 | BSS Transition Management Response |7.4.11.11 | (CFv AND CF12):M |Yes, No, N/A |
|*WNM8 |FBMS |9.2.7;11.20.9 |CFv:O |Yes, No, N/A |
|WNM8.1 |FBMS Request |7.4.11.12 |(CF2&WNM8):M |Yes, No, N/A |
|WNM8.2 |FBMS Response |7.4.11.13 |(CF1&WNM8):M |Yes, No, N/A |
|WNM9 |Proxy ARP |11.2.1.4b |CFv:O |Yes, No, N/A |
|WNM10 |Co-located Interference Reporting |7.4.11.14, |CFv:O |Yes, No, N/A |
| | |7.4.11.15, 11.20.10 | | |
|WNM11 |BSS Max Idle Period |7.3.2.74, 11.2.1.4c |CFv:O |Yes, No, N/A |
|*WNM12 |TFS |11.20.13 |CFv:O |Yes, No, N/A |
|WNM12.1 |TFS Request frame |7.3.2.75, 7.4.11.16 |WNM12:M |Yes, No, N/A |
|WNM12.2 |TFS Response frame |7.3.2.76, 7.4.11.17 |WNM12:M |Yes, No, N/A |
|WNM12.3 |TFS Notify frame |7.4.11.18 |(CF1&WNM12):M, |Yes, No, N/A |
| | | |(CF2&WNM12):O | |
|*WNM13 |Sleep Mode |11.20.14 |CFv:O |Yes, No, N/A |
|WNM13.1 |Sleep Mode Request frame |7.3.2.77, 7.4.11.19 |WNM13:M |Yes, No, N/A |
|WNM13.2 |Sleep Mode Response frame |7.3.2.77, 7.4.11.20 |WNM13:M |Yes, No, N/A |
|WNM14 |TIM broadcast |7.3.2.78, 7.3.2.79, |CFv:O |Yes, No. N/A |
| | |7.4.11.21, | | |
| | |7.4.11.22, | | |
| | |7.4.11.23, | | |
| | |11.2.1.11a | | |
|WNM15 |Traffic Generation |7.4.11.24, 11.20.11 |(CFv AND CF12):O |Yes, No, N/A |
|WNM16 |AC Station Count |11.20.12 |(CFv AND CF12):O |Yes, No, N/A |
11k uses 14. 11r uses 15, 11n uses 16.
Change the “Dot11StationConfigEntry” of the “dotStationConfig TABLE” as follows:
-- *********************************************************************
-- * dotStationConfig TABLE
-- *********************************************************************
Dot11StationConfigEntry ::=
SEQUENCE {
dot11StationID MacAddress,
dot11MediumOccupancyLimit INTEGER,
dot11CFPollable TruthValue,
dot11CFPeriod INTEGER,
dot11CFPMaxDuration INTEGER,
dot11AuthenticationResponseTimeOut Unsigned32,
dot11PrivacyOptionImplemented TruthValue,
dot11PowerManagementMode INTEGER,
dot11DesiredSSID OCTET STRING,
dot11DesiredBSSType INTEGER,
dot11OperationalRateSet OCTET STRING,
dot11BeaconPeriod INTEGER,
dot11DTIMPeriod INTEGER,
dot11AssociationResponseTimeOut Unsigned32,
dot11DisassociateReason INTEGER,
dot11DisassociateStation MacAddress,
dot11DeauthenticateReason INTEGER,
dot11DeauthenticateStation MacAddress,
dot11AuthenticateFailStatus INTEGER,
dot11AuthenticateFailStation MacAddress,
dot11MultiDomainCapabilityImplemented TruthValue,
dot11MultiDomainCapabilityEnabled TruthValue,
dot11CountryString OCTET STRING,
dot11SpectrumManagementImplemented TruthValue,
dot11SpectrumManagementRequired TruthValue,
dot11RSNAOptionImplemented TruthValue,
dot11RSNAPreauthenticationImplemented TruthValue,
dot11RegulatoryClassesImplemented TruthValue,
dot11RegulatoryClassesRequired TruthValue,
dot11QosOptionImplemented TruthValue,
dot11ImmediateBlockAckOptionImplemented TruthValue,
dot11DelayedBlockAckOptionImplemented TruthValue,
dot11DirectOptionImplemented TruthValue,
dot11APSDOptionImplemented TruthValue,
dot11QAckOptionImplemented TruthValue,
dot11QBSSLoadOptionImplemented TruthValue,
dot11QueueRequestOptionImplemented TruthValue,
dot11TXOPRequestOptionImplemented TruthValue,
dot11MoreDataAckOptionImplemented TruthValue,
dot11AssociatedinNQBSS TruthValue,
dot11DLSAllowdInQBSS TruthValue,
dot11DLSAllowed TruthValue,
dot11AssociateStation MacAddress,
dot11AssociateID INTEGER,
dot11AssociateFailStation MacAddress,
dot11AssociateFailStatus INTEGER,
dot11ReassociateStation MacAddress,
dot11ReassociateID INTEGER,
dot11ReassociateFailStation MacAddress,
dot11ReassociateFailStatus INTEGER,
dot11RadioMeasurementCapable TruthValue,
dot11RadioMeasurementEnabled TruthValue,
dot11RadioMeasurementProbeDelay INTEGER,
dot11MeasurementPilotReceptionEnabled TruthValue,
dot11MeasurementPilotTransmissionEnabled TruthValue,
dot11MeasurementPilotTransmissionVirtualApSetEnabled TruthValue,
dot11MeasurementPilotPeriod INTEGER,
dot11LinkMeasurementEnabled TruthValue,
dot11NeighborReportEnabled TruthValue,
dot11ParallelMeasurementsEnabled TruthValue,
dot11TriggeredMeasurementsEnabled TruthValue,
dot11RepeatedMeasurementsEnabled TruthValue,
dot11MeasurementPauseEnabled TruthValue,
dot11QuietIntervalEnabled TruthValue,
dot11PassiveBeaconMeasurementEnabled TruthValue,
dot11ActiveBeaconMeasurementEnabled TruthValue,
dot11TableBeaconMeasurementEnabled TruthValue,
dot11ReportingConditionsEnabled TruthValue,
dot11FrameMeasurementEnabled TruthValue,
dot11ChannelLoadEnabled TruthValue,
dot11NoiseHistogramEnabled TruthValue,
dot11StatisticsReportEnabled TruthValue,
dot11LCIReportEnabled TruthValue,
dot11TransmitStreamMeasurementEnabled TruthValue,
dot11APChannelReportEnabled TruthValue,
dot11AnnexQMIBSupportEnabled TruthValue,
dot11NonOperatingChannelMeasurementsEnabled TruthValue,
dot11MaximumMeasurementDuration Unsigned32,
dot11MeasurementPilotSupport Unsigned32,
dot11FastBSSTransitionImplemented TruthValue,
dot11RRMCivicMeasurementEnabled TruthValue,
dot11RRMIdentifierMeasurementEnabled TruthValue,
dot11WirelessManagementImplemented TruthValue,
dot11MaxIdlePeriod INTEGER,
dot11TIMBroadcastInterval INTEGER,
dot11TIMBroadcastOffset INTEGER}
Insert the following elements at the end of the dot11StationConfigTable element definitions:
last entry in 802.11-2007 has order 42. 11k adds 42-56. 11r adds 57. 11y adds none. 11n adds 1 entry (58). 11s adds none.
dot11RRMCivicMeasurementEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that dot11RadioMeasurementEnabled is
TRUE and that the station capability for Location Civic Measurement is enabled. FALSE
indicates the station has no Location Civic Measurement capability or that the capability
is present but is disabled. The default value of this attribute is
FALSE."
::= { dot11StationConfigEntry XX }
dot11RRMIdentifierMeasurementEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that dot11RadioMeasurementEnabled is
TRUE and that the station capability for Location Identifier Measurement is enabled. FALSE
indicates the station has no Location Identifier Measurement capability or that the capability
is present but is disabled. The default value of this attribute is
FALSE."
::= { dot11StationConfigEntry XX }
dot11WirelessManagementImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“This attribute, when TRUE, indicates that the station
implementation is capable of supporting one or more Wireless Network
Management services.
The default value of this attribute is FALSE.”
::= { dot11StationConfigEntry 59}
dot11MaxIdlePeriod OBJECT-TYPE
SYNTAX INTEGER (1...65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
“This attribute indicates that the number of 1000 TUs that pass before an AP
disassociates an inactive non-AP STA. This value is transmitted in the Association Response and Reassociation frames.”
::= { dot11StationConfigEntry 60}
dot11TIMBroadcastInterval OBJECT-TYPE
SYNTAX INTEGER (0...255)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
“This attribute indicates the smallest active number of Beacon periods between TIM frame transmissions.The default value of this attribute is 0.”
::= { dot11StationConfigEntry 61}
dot11TIMBroadcastOffset OBJECT-TYPE
SYNTAX SIGNED INTEGER (-2,147,483,648 to 2,147,483,647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
“This attribute indicates the offset in microseconds relative to the TBTT for which a TIM frame is scheduled for transmission. The default value of this attribute is 0.”
::= { dot11StationConfigEntry 62}
Insert the following element at the end of the list of child objects for dot11smt object identifier:
--***********************************************************
--*Wireless Network Management
--************************************************************
-- dot11WirelessMgmtOptionsTable ::= { dot11smt 17}
Insert the following text at the end of the Station management MIB:
-- **********************************************************************
-- * dot11WirelessMgmtOptions TABLE
-- **********************************************************************
dot11WirelessMgmtOptionsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot11WirelessMgmtmOptionsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
“Wireless Management attributes. In tabular form to
allow for multiple instances on an agent. This table
only applies to the interface if dot11WirelessManagementImplemented
is set to TRUE in the dot11StationConfigTable. Otherwise
this table should be ignored.”
::= { dot11smt 17 }
dot11WirelessMgmtOptionsEntry OBJECT-TYPE
SYNTAX Dot11WirelessMgmtOptionsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot11WirelessMgmtOptionsTable. It is
possible for there to be multiple IEEE 802.11 interfaces
on one agent, each with its unique MAC address. The
relationship between an IEEE 802.11 interface and an
interface in the context of the Internet-standard MIB is
one-to-one. As such, the value of an ifIndex object
instance can be directly used to identify corresponding
instances of the objects defined herein.
ifIndex - Each IEEE 802.11 interface is represented by an
ifEntry. Interface tables in this MIB module are indexed
by ifIndex."
INDEX { ifIndex }
::= { dot11WirelessMgmtOptionsTable 1 }
Dot11WirelessMgmtOptionsEntry ::=
SEQUENCE {
dot11MgmtOptionLocationEnabled TruthValue,
dot11MgmtOptionFBMSImplemented TruthValue,
dot11MgmtOptionFBMSEnabled TruthValue,
dot11MgmtOptionEventsEnabled TruthValue,
dot11MgmtOptionDiagnosticsEnabled TruthValue,
dot11MgmtOptionMultiBSSIDImplemented TruthValue,
dot11MgmtOptionMultiBSSIDEnabled TruthValue,
dot11MgmtOptionTFSImplemented TruthValue,
dot11MgmtOptionTFSEnabled TruthValue,
dot11MgmtOptionSleepModeImplemented TruthValue, dot11MgmtOptionSleepModeEnabled TruthValue,
dot11MgmtOptionTIMBroadcastImplemented TruthValue,
dot11MgmtOptionTIMBroadcastEnabled TruthValue,
dot11MgmtOptionProxyARPEnabled TruthValue,
dot11MgmtOptionBSSTransitionEnabled TruthValue,
dot11MgmtOptionTrafficGenerationImplemented TruthValue,
dot11MgmtOptionTrafficGenerationEnabled TruthValue,
dot11MgmtOptionACStationCountImplemented TruthValue,
dot11MgmtOptionACStationCountEnabled TruthValue,
dot11MgmtOptionMulticastDiagnosticsEnabled TruthValue,
dot11MgmtOptionCLIReportingEnabled TruthValue,
dot11MgmtOptionMotionDetectionImplemented TruthValue,
dot11MgmtOptionMotionDetectionEnabled TruthValue,
dot11MgmtOptionTODImplemented TruthValue,
dot11MgmtOptionTODEnabled TruthValue,}
dot11MgmtOptionTimingMsmtImplemented TruthValue,
dot11MgmtOptionTimingMsmtEnabled TruthValue}
dot11MgmtOptionLocationEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the
capability of the station to provide location is
enabled. The capability is disabled, otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 1 }
dot11MgmtOptionFBMSImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station
implementation is capable of supporting FBMS when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 2 }
dot11MgmtOptionFBMSEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the
capability of the station to provide FBMS is
enabled. The capability is disabled, otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 3 }
dot11MgmtOptionEventsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the
capability of the station to provide Event Reporting is
enabled. The capability is disabled, otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 4 }
dot11MgmtOptionDiagnosticsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the
capability of the station to provide Diagnostic Reporting is
enabled. The capability is disabled, otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 5 }
dot11MgmtOptionMultiBSSIDImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station
implementation is capable of supporting Multiple BSSID when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 6 }
dot11MgmtOptionMultiBSSIDEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the
capability of the station to provide Multi BSSID is
enabled. The capability is disabled, otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 7 }
dot11MgmtOptionTFSImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station implementation is capable of supporting TFS when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 8 }
dot11MgmtOptionTFSEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that TFS is enabled. TFS is disabled otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 9 }
dot11MgmtOptionSleepModeImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station implementation is capable of supporting Sleep Mode when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 10 }
dot11MgmtOptionSleepModeEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that Sleep Mode is enabled. Sleep Mode is disabled otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 11 }
dot11MgmtOptionTIMBroadcastImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station implementation is capable of supporting TIM Broadcast when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 12}
dot11MgmtOptionTIMBroadcastEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that TIM broadcast is enabled. TIM broadcast is disabled otherwise.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 13}
dot11MgmtOptionProxyARPEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability of the AP to provide the Proxy ARP service is enabled. The capability is disabled, otherwise. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 14 }
dot11MgmtOptionBSSTransitionEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability of the station to provide BSS Transition is enabled. The capability is disabled, otherwise. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 15 }
dot11MgmtOptionTrafficGenerationImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station implementation is capable of supporting Traffic Generation when the dot11WirelessManagementImplemented is TRUE. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 16 }
dot11MgmtOptionTrafficGenerationEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability of the station to provide Traffic Generation is enabled. Traffic Generation is disabled otherwise. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 17 }
dot11MgmtOptionACStationCountImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station implementation is capable of supporting AC Station Count when the dot11WirelessManagementImplemented is TRUE. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 18 }
dot11MgmtOptionACStationCountEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability of the station to provide AC Station Count is enabled. AC Station Count is disabled otherwise. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 19 }
dot11MgmtOptionMotionDetectionImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station
implementation is capable of supporting motion detection when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 20 }
dot11MgmtOptionMotionDetectionEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability to support motion detection is enabled. The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 21 }
dot11MgmtOptionTODImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station
implementation is capable of supporting Time Of Departure for transmitted Clause 15, 17, 18, 19 and 20 frames when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 22 }
dot11MgmtOptionTODEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the capability to support Time Of Departure frames for transmitted Clause 15, 17, 18, 19 and 20 frames is enabled.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 23 }
dot11MgmtOptionTimeMsmtImplemented OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station
implementation is capable of supporting Timing Measurement capability when the dot11WirelessManagementImplemented is TRUE.
The default value of this attribute is FALSE."
::= { dot11WirelessMgmtOptionsEntry 24 }
dot11MgmtOptionTimeMsmtEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute, when TRUE, indicates that the station capability for Timing Measurement is enabled. FALSE indicates the station has no Timing Measurement capability or that the capability is present but is disabled. The default value of this attribute is FALSE"
::= { dot11WirelessMgmtOptionsEntry 25 }
-- ********************************************************************
-- * dot11LocationServicesdot11LOCATIONCONFIG TABLE
-- ********************************************************************
dot11LocationServices dot11LocationConfiguration OBJECT-TYPE
SYNTAX SEQUENCE OF Dot11LocationServicesDot11LocationConfiguration
MAX-ACCESS READ-WRITE
STATUS current
DESCRIPTION
"Group contains conceptual table of attributes for
Wireless Network Management Location ConfigurationServices."
::= { dot11smt xx }
dot11LocationServicesEntry dot11LocationConfigurationEntry OBJECT-TYPE
SYNTAX Dot11LOCATIONSERVICESEntryDot11LOCATIONCONFIGEntry
MAX-ACCESS READ-WRITE
STATUS current
DESCRIPTION
"An entry in the dot11LOCATIONSERVICESTabledot11LOCATIONCONFIGTable
Indexed by dot11LOCATIONSERVICESIndexdot11LOCATIONCONFIGIndex."
INDEX { dot11LOCATIONSERVICESdot11LOCATIONCONFIGIndex }
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGTable 1 }
Dot11LOCATIONSERVICESDot11LOCATIONCONFIGEntry ::=
SEQUENCE {
dot11LOCATIONSERVICESdot11LOCATIONCONFIGIndex Unsigned32,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGMACAddress MacAddress,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersReportIntervalUnits INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersNormalReportInterval INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersNormalFramesperChannel INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersInMotionReportInterval INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersInMotionFramesperChannel INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersBurstInterframeInterval INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationChannelsChannel OCTET STRING,
dot11LOCATIONSERVICESLocationRequestOptions INTEGER,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationStatus INTEGER,
dot11LOCATIONSERVICESServiceParametersLocationServiceState INTEGER,
dot11LOCATIONSERVICESServiceParametersLocationServiceInterval INTEGER,
dot11LOCATIONSERVICESRadioInformationTransmitPower INTEGER,
dot11LOCATIONSERVICESRadioInformationAntennaID INTEGER,
dot11LOCATIONSERVICESRadioInformationAntennaGain INTEGER,
dot11LOCATIONSERVICESRadioInformationReceivedRSNI INTEGER,
dot11LOCATIONSERVICESRadioInformationRCPI INTEGER,
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifference OCTET STRING,
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifferenceUnits INTEGER,
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifferenceAccuracy INTEGER,
dot11LOCATIONSERVICESTimingMeasurementsIngressTimestamp OCTET STRING,
dot11LOCATIONSERVICESMotionIndicator INTEGER,
dot11LOCATIONSERVICESMotionSpeed INTEGER
dot11LOCATIONSERVICESLocationDescriptor INTEGER,
dot11LOCATIONSERVICESLocationDescriptorResolution INTEGER,
dot11LOCATIONSERVICESLocationDescriptorEncoding INTEGER,
dot11LOCATIONSERVICESLocationDataAccuracyEstimate INTEGER,
dot11LOCATIONSERVICESLocationDataLocationValue DisplayString,
dot11LOCATIONSERVICESLocationSourceIdentifierTimeZoneOffset INTEGER,
dot11LOCATIONSERVICESLocationSourceIdentifierLocationTimestamp OCTET STRING,
dot11LOCATIONSERVICESLocationSourceIdentifierPublicIdentifierLink DisplayString,
dot11LOCATIONSERVICESdot11LOCATIONCONFIGIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute is the Index for LOCATIONSERVICES LOCATIONCONFIG Report elements in dot11LOCATIONSERVICESdot11LOCATIONCONFIGTable,
greater than 0."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 1 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGMACAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute is the MAC address of the STA reporting location information."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 2 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersReportIntervalUnits OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters Report Interval Units value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 3 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersNormalReportInterval OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters Normal Report Interval value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 4 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersNormalFramesperChannel OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters Normal Frames per Channel value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 5 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersInMotionReportInterval OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters in-motion Report Interval value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 6 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersInMotionFramesperChannel OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters in-motion Frames per Channel value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 7 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationParametersBurstInterframeInterval OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Parameters inter-frame Interval value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 8 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationIndicationChannels OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..254))
MAX-ACCESS read-onlywrite
STATUS current
DESCRIPTION
"This attribute contains the Location Indication Channels Channel and Regulatory Class octet fields."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 9 }
dot11LOCATIONSERVICESLocationRequestOptions OBJECT-TYPE
SYNTAX INTEGER (0...65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains a bit field indicating the Location Request Options value."
::= { dot11LOCATIONSERVICESEntry 10 }
dot11LOCATIONSERVICESdot11LOCATIONCONFIGLocationStatus OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Status value."
::= { dot11LOCATIONSERVICESdot11LOCATIONCONFIGEntry 11 }
dot11LOCATIONSERVICESServiceParametersLocationServiceState OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Services Parameters Location Service State value."
::= { dot11LOCATIONSERVICESEntry 12 }
dot11LOCATIONSERVICESServiceParametersLocationServiceInterval OBJECT-TYPE
SYNTAX INTEGER (0...65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Services Parameters Location Service Interval value."
::= { dot11LOCATIONSERVICESEntry 13 }
TGv Editor: Insert a new Annex after the last Annexand renumber appropriately.
Annex VV Time of departure accuracy test (Informative)
The Time of Departure accuracy test is parameterized by the following test parameters:
- MULTICHANNEL_BANDWIDTH
- FIRST_TRANSITION_FIELD
- SECOND_TRANSITION_FIELD
- TRAINING_FIELD
- TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH
The Time of Departure accuracy test is performed as follows or in an equivalent or more accurate manner.
The Time of Departure accuracy test is performed by instrumentation capable of converting signals transmitted on one or more channels into a stream of complex samples at fs sample/s or more, with sufficient accuracy in terms of I/Q arm amplitude and phase balance, dc offsets, phase noise, etc. The minimum sampling rate is MULTICHANNEL_BANDWIDTH sample/s respectively. A possible embodiment of such a setup is converting the signal to a low IF frequency with a microwave synthesizer, sampling the signal with a digital oscilloscope and decomposing it digitally into quadrature components. The sampled signal is processed in a manner similar to an actual time of arrival processor, according to the following steps:
a) Start of frame is detected.
b) Channel number, coarse and fine frequency offsets are estimated.
c) The packet is derotated according to estimated frequency offsets.
d) The transition from FIRST_TRANSITION_FIELD to SECOND_TRANSITION_FIELD is detected; and fine timing (with one sample resolution) is established.
e) The TRAINING_FIELD of the derotated signal is up-sampled to above 1 GHz.
f) The up-sampled signal is cross-correlated with a reference waveform of the TRAINING_FIELD
g) The measured time of departure equals the time of the peak of the magnitude of the cross-correlation.
h) The reported and measured times of departure are recorded, and the reported time of departure tolerance.
i) Steps a) to h) are repeated for at least 4 packets within 1 second. Time of departure errors are calculated as the RMS deviation of the reported values from estimated values. The estimated values are determined using the weighted least squares line of best fit, where the X, Y and weight parameters shall be the measured times of departure, the reported times of departure and half the reported tolerances respectively.
j) Step i) are repeated 500 times
k) The Time of Departure accuracy test is passed if 95% or more of the time of departure errors are less than their reported time of departure tolerances, and 95% of the reported time of departure tolerances are less than the TIME_OF_DEPARTURE_ACCURACY_TEST_THRESH ns.
Note 1: One implementation of a time of departure measurement system is a free-running oscillator clocking (a) the digital-to-analog converter(s) used to transmit the packet, (b) a 32-bit continuously-counting counter and (c) a hardware finite state machine such that PMD_TXSTART.request causes a transition within the FSM which in turn causes frame transmission at the DACs a fixed number of cycles later; where the time of departure is recorded as the value of the counter at that transition. In this implementation, the principal source of time of departure error is only short term oscillator imperfection (e.g. phase noise) and RF group delay variation with channel.
Note 2: 1 ns of time of departure error corresponds to approximately 0.3 m of distance error, so high location accuracy depends upon a tight time of departure tolerance.
dot11LOCATIONSERVICESRadioInformationTransmitPower OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Radio Information Transmit Power value."
::= { dot11LOCATIONSERVICESEntry 14 }
dot11LOCATIONSERVICESRadioInformationAntennaID OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Radio Information Antenna ID value."
::= { dot11LOCATIONSERVICESEntry 15 }
dot11LOCATIONSERVICESRadioInformationAntennaGain OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Radio Information Antenna Gain value."
::= { dot11LOCATIONSERVICESEntry 16 }
dot11 LOCATIONSERVICESRadioInformationReceivedRSNI OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Radio Information Received RSNI value.
::= { dot11LOCATIONSERVICESEntry 17 }
dot11LOCATIONSERVICESRadioInformationRCPI OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute conains the Radio Information RCPI value."
::= { dot11LOCATIONSERVICESEntry 18 }
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifference OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Timing Measurements Timestamp Difference value."
::= { dot11LOCATIONSERVICESEntry 19 }
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifferenceUnits OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Timing Measurements Timestamp Difference Units value."
::= { dot11LOCATIONSERVICESEntry 20 }
dot11LOCATIONSERVICESTimingMeasurementsTimestampDifferenceAccuracy OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Timing Measurements Timestamp Difference Accuracy value."
::= { dot11LOCATIONSERVICESEntry 21 }
dot11LOCATIONSERVICESTimingMeasurementsIngressTimestamp OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (12))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Timing Measurements Ingress Timestamp value."
::= { dot11LOCATIONSERVICESEntry 22 }
dot11LOCATIONSERVICESMotionIndicator OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Motion Indicator value."
::= { dot11LOCATIONSERVICESEntry 23 }
dot11LOCATIONSERVICESMotionSpeed OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Motion Speed value."
::= { dot11LOCATIONSERVICESEntry 24 }
dot11LOCATIONSERVICESLocationDescriptor OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Descriptor value."
::= { dot11LOCATIONSERVICESEntry 25 }
dot11 LOCATIONSERVICESLocationDescriptorResolution OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Descriptor sub element Location Resolution Descriptor field value."
::= { dot11LOCATIONSERVICESEntry 26 }
dot11LOCATIONSERVICESLocationDescriptorEncoding OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute conains the Location Descriptor sub-element Encoding Descriptor value value."
::= { dot11LOCATIONSERVICESEntry 27 }
dot11LOCATIONSERVICESLocationDataAccuracyEstimate OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Data Accuracy Estimate value."
::= { dot11LOCATIONSERVICESEntry 28 }
dot11LOCATIONSERVICESLocationDataLocationValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (3..254))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location data value."
::= { dot11LOCATIONSERVICESEntry 29 }
dot11LOCATIONSERVICESLocationSourceIdentifierTimeZoneOffset OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Source Identifier Time Zone Offset value."
::= { dot11LOCATIONSERVICESEntry 30 }
dot11LOCATIONSERVICESLocationSourceIdentifierLocationTimestamp OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (6))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Location Source Identifier Location Timestamp value."
::= { dot11LOCATIONSERVICESEntry 31 }
dot11LOCATIONSERVICESLocationSourceIdentifierPublicIdentifierLink OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute contains the Public Identifier Link value."
::= { dot11LOCATIONSERVICESEntry 32 }
-----------------------
Abstract
This submission contains the normative text for changes to D2.0 Location Services that addresses ALL accepted and countered comments in spreadsheet 08/0440r0.
.
This proposal text is aligned with P802.11v-D2.01.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.