Functional requirements for scalability operation

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0341r2 Submission March 2011 MediaTek, Inc Slide 1 Usage Cases for ah Date: Authors:
Advertisements

Doc.: IEEE /0134r2 Submission July 2015 Ganesh Venkatesan (Intel Corporation)Slide 1 Functional Requirements for a.11az Range Measurement protocol.
Submission doc.: IEEE /r1 60 GHz Focus Area Date: Slide 1Alecsander Eitan, Qualcomm Jan Authors:
Amendment Proposal for TV White Spaces Operation
Proposed Functional Requirements for 11az
AP Power Saving Date: Authors: May 2017 Month Year
Resource Negotiation for Unassociated STAs in MU Operation
Network Based Use Case Date: Authors: February 2016
Relay Threat Model for TGaz
Relay Threat Model for TGaz
Locationing Protocol for 11az
Examining ba Usage Models for Mainstream Devices
BSS Load Information Element for 11ax
Demand on Roaming for WUR
Follow-Up on WUR Discovery Frame and Discovery Channel
WUR Discovery Frame and Discovery Channel
Month Year doc.: IEEE yy/xxxxr0 July 2015
Month Year doc.: IEEE yy/xxxxr0 July 2017
Relay Threat Model for TGaz
WUR Discovery Frame Content
Differentiated Initial Link Setup (Follow Up)
WUR Discovery Frame Content
Examining ba Usage Models for Mainstream Devices
Follow-Up on WUR Discovery Frame and Discovery Channel
Motivation and Requirements on 60 GHz Beamforming
Follow-Up on WUR Discovery Frame and Discovery Channel
WUR Discovery Frame Content
Consideration on WUR frame for Fast Scanning
Discussions on Multi-AP Coordination
Amendment text submissions formatting conventions
Peer Power Save Mode for TDLS
WUR Discovery Frame Content
Follow-Up on WUR Discovery Frame and Discovery Channel
Resource Negotiation for Unassociated STAs in MU Operation
Month Year doc.: IEEE yy/xxxxr0 July 2015
WUR Discovery Frame Content
WUR Discovery Frame Content
Examining ba Usage Models for Mainstream Devices
CID#102 - Channel Allocation
Examining ba Usage Models for Mainstream Devices
WUR Discovery Frame Content
Proposed Functional Requirements for 11az
Follow-Up on WUR Discovery Frame and Discovery Channel
Proposed SFD Text for ai Prioritized Active Scanning
Functional Requirements for EHT Specification Framework
Saishankar Nandagopalan
Follow-Up on WUR Discovery Frame and Discovery Channel
Use Case Document Definitions
WUR Discovery Frame Content
Access distribution in ai
Channel Allocation March 2008 Authors: Date: Month Year
MU with Frequency Domain Multiplexing
EHT Feature Discussion
Usage Cases for ah Date: Authors: March 2011
Use Case Characteristics Discussion
Locationing Protocol for 11az
Scheduled Peer Power Save Mode for TDLS
Saishankar Nandagopalan
60GHz Functional Requirements
Traffic Information Dissemination Use Case
Differentiated Initial Link Setup (Follow Up)
Saishankar Nandagopalan
Proposed SFD Text for ai Prioritized Active Scanning
AoD in Passive Ranging Date: Authors: Name Affiliations
Functional Requirements for EHT Specification Framework
GAS procedure in TGai Date: Authors: May 2012 Month Year
Network Based Use Case Date: Authors: February 2016
Functional Requirements for a .11az Scalability Requirements
Month Year doc.: IEEE yy/xxxxr0 August 2019
EHT Multi-AP Feature Discussion
Presentation transcript:

Functional requirements for scalability operation Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2016 Functional requirements for scalability operation Date: 2016-05-17 Authors: Name Affiliation Address Phone Email Chao-Chun Wang MediaTek Inc Chao-chun.wang@mediatek.com James Yee James.yee@mediatek.com Thomas Handte SONY Corp. thomas.handte@ eu.sony.com Kåre Agardh SONY mobile kare.agardh@ sonymobile.com Chao-Chun Wang (MediaTek Inc) John Doe, Some Company

May 2016 Background This document proposes a set of functional requirements for a scalable .11az protocol to support a large number of STAs (> 200) in performing locationing operation concurrently. Chao-Chun Wang (MediaTek Inc)

Definition of Scalability May 2016 Definition of Scalability 11-16-0134-03-00az-accuracy-and-coverage-functional-requirements details the functional requirement for accuracy and coverage The objectives of the accuracy and coverage are also applicable to scalability, except the consideration of the performance threshold needs to be updated for > 200 STAs rather than for a single STA Chao-Chun Wang (MediaTek Inc)

May 2016 Objectives Optimize the time it takes to get a first location fix with the required accuracy Determine the Refresh rate of the location information vs. accuracy Minimize Power (i.e., minimize Idle Rx, Active Rx and Active Tx) Minimize Medium Usage Optimize the duration a device has to operate off-channel Chao-Chun Wang (MediaTek Inc)

Functional Requirements - 1(Scalability) May 2016 Functional Requirements - 1(Scalability) The scalable mode of the 802.11az range measurement protocol shall: Support at least one mode which allows for scalable positioning, meeting the following scalability mode requirements Support at least 200 unassociated and associated STAs, per AP performing locationing operation concurrently Achieve improved accuracy of 1st fixed time of a STA with greater number of APs involved Utilize less than 10% of the channel capacity of an AP Operate with a maximum refresh rate of .5Hz Maintain stability with up to 5% STAs joining and leaving the coverage of the AP Chao-Chun Wang (MediaTek Inc)

Functional Requirements – 2 (Scalability) May 2016 Functional Requirements – 2 (Scalability) The scalable mode of the 802.11az positioning measurement protocol should: Minimize the STA‘s power consumption. Minimize the off-channel time of an associated STA Off-channel time is the time an associated STA is required to spend on channel(s) other than the one used by the AP it’s associated to for the purpose of location measurement exchange. Chao-Chun Wang (MediaTek Inc)

Motion - 1 Move to adopt the set of functional requirements listed in slide #5 and include them in the TGaz Functional Requirements Document under the sub-section focused on Scalability for the .11az protocol Moved: Seconded: Result:

Motion - 2 Move to adopt the set of functional requirements listed in slide #6 and include them in the TGaz Functional Requirements Document under the sub-section focused on Scalability for the .11az protocol Moved: Seconded: Result:

Back UP

Functional Requirements for scalable positioning protocol Parameter Value Assumptions comments Number of locating STAs STAs STA may be unassociated STA. Number is per AP. Number of APs used to accomplish the task dependent? Yes. e.g. If to support the technique more than 1 AP is required multiply the number of loc. STAs by number of APs required to accomplish the task. Medium usage 10% Dedicated to location determination purposes for the scalable operational mode. Refresh rate 0.5Hz Rate of location fixes required by the Application layer. e.g. might be that multiple measurements are required for a single fix to be generated. Mobility factor? 5% Percentage of STAs joining the service and leaving the service out of the STAs under coverage of 1 AP. Out of refresh rate. STA stays for 20 cycles @ 0.5Hz giving 5% of total locating STAs. e.g. ability to account for variability in STA’s mobility Support for unassociated STAs required.