Ranging ID and its Lifetime Management

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0134r2 Submission July 2015 Ganesh Venkatesan (Intel Corporation)Slide 1 Functional Requirements for a.11az Range Measurement protocol.
Advertisements

Doc.: IEEE /0150r11 Submission July 2015 Ganesh Venkatesan (Intel Corporation)Slide 1 GCR using SYNRA for GLK Date: Authors:
IEEE 802.1AS REV D5.0 Review Comments
PHY Security FRD and SRD Text
IEEE 802.1AS REV D5.0 Review Comments
802.11az Negotiation Date: Authors: Jan 2017 Month Year
Security for location determination at a Public Domain
Location Measurement Protocol for Unassociated STAs
Resource Negotiation for Unassociated STAs in MU Operation
802.11az Negotiation Date: Authors: May 2017 Month Year
IEEE 802.1AS REV D5.0 Review Comments
Trigger Frame Format for az
PHY Security FRD and SRD Text
Polling for MU Measurements
SU Sounding Measurement Exchange and Feedback
Protected LTF Using PMF in SU and MU Modes
Month Year doc.: IEEE yy/xxxxr0 July 2015
Pre-association Security Negotiation for 11az SFD Follow up
Month Year doc.: IEEE yy/xxxxr0 July 2017
Random Access RU Allocation in the Trigger Frame
Random Access RU Allocation in the Trigger Frame
AID Selection Date: Authors: September 2010 Month Year
BSS Max Idle Period and Sleep Interval
Pre-association Security Negotiation for 11az SFD Follow up
Channel Access Efficiency
Wake Up Frame to Indicate Group Addressed Frames Transmission
Availability Window Advertisement
Resource Allocation for Unassociated STAs – Follow Up
Two-sided LMR Feedback between AP and STA
Two-sided LMR Feedback between AP and STA
Pre-Association Security Negotiation (PASN) for 11az
Resource Negotiation for Unassociated STAs in MU Operation
MU Ranging Sequence Date: Authors: Nov 2017 Month Year
Month Year doc.: IEEE yy/xxxxr0 July 2015
Default UORA Parameters
Random Access RU Allocation in the Trigger Frame
An unified az Protocol Date: Authors: Nov 2016
Intel Secured Location Threat Model
Availability Window Update
Random Access RU Allocation in the Trigger Frame
AP Power Down Notification
AP Power Down Notification
Negotiation for HEz Ranging for Passive Location Support
Peer Power Save Mode for TDLS
Channel Allocation March 2008 Authors: Date: Month Year
AID Reassignment Protocol
FTM Frame Exchange Authentication
Fast Session Transfer Session Setup in TVWS
Power Efficiency for Individually Addressed Frames Reception
11az related bits in the Extended Capabilities element
CR for CID 1115 Date: Authors: May 2019
Interference Signalling Enhancements
Scheduled Peer Power Save Mode for TDLS
Timing Measurement Date: Authors: Jan 2010 November 2007
GCR using SYNRA for GLK Date: Authors: July 2015 Month Year
Intel Secured Location Threat Model
Power Efficiency for Individually Addressed Frames Reception
Secure SU and MU Ranging Measurement Procedure
HEz Ranging Availability Window
Sounding-only Support During Ranging
11az Ranging and Location Privacy
Availability Window Termination
PHY Security SRD Text Update
ISTA2RSTA LMR Feedback AP Policy and Negotiation
Location Measurement Protocol for 11ax
11az Negotiation Protocol (update)
Intel Secured Location Threat Model
CR for CID 1115 Date: Authors: May 2019
Request for Legacy IE ID for RSN Extension
Availability Window Advertisement
Presentation transcript:

Ranging ID and its Lifetime Management Month Year doc.: IEEE 802.11-yy/xxxxr0 Nov 2017 Ranging ID and its Lifetime Management Date: 2017-11-06 Authors: Ganesh Venkatesan (Intel Corporation) John Doe, Some Company

Motivation/Background Nov 2017 Motivation/Background Ranging Id is assigned by an AP to unassociated STAs that initiated a MU iFTMR with the AP The assigned Ranging ID is communicated via the iFTM that the AP sends in response to iFTMR to the STA The assignment and maintenance of the Ranging ID consumes resources in the AP To conserve resources AP’s would like to release resources associated with inactive Ranging IDs as soon as possible This submission discusses Ranging ID lifetime and management Ganesh Venkatesan (Intel Corporation)

Month Year doc.: IEEE 802.11-yy/xxxxr0 Nov 2017 Ranging ID Lifetime AP has an implementation dependent Ranging ID lifetime Lifetime of all Ranging IDs assigned by the AP If the STA to which a Ranging ID is assigned by the AP does not initiate a Range Measurement Request to the AP within the Ranging ID lifetime, the Ranging ID assignment is retired The STA must obtain a new Ranging ID in order to initiate a Range Measurement with the AP – this requires the STA to send an iFTMR and receive an iFTM with the status set to SUCCESS does initiate a Range Measurement within the Ranging ID lifetime(at time = t), the subsequent Range Measurement request from rhe STA to the AP must be received by the AP before time = t + lifetime Ganesh Venkatesan (Intel Corporation) John Doe, Some Company

How does this work (an example)? Nov 2017 How does this work (an example)? Ganesh Venkatesan (Intel Corporation)

Straw Poll We support: Nov 2017 Ranging IDs are of the same size and range as AIDs and following same rules and limitations. Ranging IDs and AIDs are from same space and non-conflicting. the assignment of Ranging IDs by a RSTA to unassociated ISTA resulting in the execution MU HEz Ranging protocol with the RSTA: the assigned Ranging ID is included in the HEz Specific subelement contained in iFTM. the RSTA may advertise a Ranging ID lifetime which defines the duration for which the Ranging ID remains valid the mechanism to advertise Ranging ID lifetime is TBD the best choice for Ranging ID lifetime value is implementation dependent the Ranging ID is retired at both ISTA and RSTA when the corresponding Ranging ID Lifetime expires which also terminates the FTM session. Ranging ID lifetime may be equal to MAX BSS IDLE PERIOD. When an FTM session terminates or aborts the Ranging ID expires. Termination may be explicit (i.e. using FTM or FTM Req) or implicit due to Ranging ID Lifetime expiration. Support of the Ranging ID Lifetime is optional. Ganesh Venkatesan (Intel Corporation)

Nov 2017 Motion Move to add the following text to the 802.11az SFD (Cl. 3.2 Protocol Description), granting the SFD Editor editorial license: Ranging IDs are of the same size and range as AIDs and following same rules and limitations. Ranging IDs and AIDs are from same space and non-conflicting. the assignment of Ranging IDs by a RSTA to unassociated ISTA resulting in the execution MU HEz Ranging protocol with the RSTA: the assigned Ranging ID is included in the HEz Specific subelement contained in iFTM. the RSTA may advertise a Ranging ID lifetime which defines the duration for which the Ranging ID remains valid the mechanism to advertise Ranging ID lifetime is TBD the best choice for Ranging ID lifetime value is implementation dependent the Ranging ID is retired at both ISTA and RSTA when the corresponding Ranging ID Lifetime expires which also terminates the FTM session. Ranging ID lifetime may be equal to MAX BSS IDLE PERIOD. When an FTM session terminates or aborts the Ranging ID expires. Termination may be explicit (i.e. using FTM or FTM Req) or implicit due to Ranging ID Lifetime expiration. Support of the Ranging ID Lifetime is optional. Moved: Ganesh Venkatesan; Seconded: Ganesh Venkatesan (Intel Corporation)

Nov 2017 Backup Ganesh Venkatesan (Intel Corporation)

How is the Ranging ID Advertised? Nov 2017 How is the Ranging ID Advertised? In iFTM (HEz-specific sub-element) Probably the best way to communicate this value Delivered along with the Ranging ID The lifetime alone does not make sense As a capability Ganesh Venkatesan (Intel Corporation)

Nov 2017 What would be the best choice for the value of the Ranging ID Lifetime? Should allow for reuse of Ranging IDs as fast as possible Could be as large as BSS Max Idle Period? Would match associated STA behavior – is this needed? Would tie-up Ranging IDs for too long Security implications of having an unused Ranging ID live longer than needed Best to set the Ranging ID Lifetime in such a way that the Ranging ID is retired as soon as one of the following happens: FTM session is torn down explicitly The initiator does not initiate a new Ranging Measurement before the (last LMR delivery + Ranging ID lifetime) Ganesh Venkatesan (Intel Corporation)

Other Issues to consider Nov 2017 Other Issues to consider What happens if the STA with Ranging ID is never Polled? Ranging ID lifetime determination should consider the worst case scenario for a STA to be polled. What happens of the RSTA switches between SU and MU modes of ranging with a STA that is assigned a Ranging ID? Ranging ID lifetime be renewed when a ranging happens (irrespective of the ranging being SU or MU) Ganesh Venkatesan (Intel Corporation)