Motivation for Vendor Specific Request Element

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0060r1 Submission January 2011 Minyoung Park, Intel Corp.Slide 1 Low Power Capability Support for ah Date: Authors:
Advertisements

Submission November 2010 doc.: IEEE /1237r0 Over the Air Database Access for Mode 2 Capable Devices Slide 1 Santosh Abraham, Qualcomm Incorporated.
ESP Element ID Request Date: Authors: March 2016 Month Year
EDMG Capability and Operation Element Channel Indications
Data Function Frames Date: Authors: Jan 2009 Month Year
FCC TVWS Terminology Date: Authors: Month Year Month Year
TX Masks Date: Authors: January 2017
BRP Transmit Sector Sweep
Header Compression Date: Authors: May 2012 Month Year
Month Year Month Year doc.: IEEE yy/xxxxr0 doc.: IEEE /0135r0
Firmware Notification
Firmware Notification
BSS Max Idle Period and Sleep Interval
FCC TVWS Terminology Date: Authors: Month Year Month Year
TGaq Transaction Protocol
Wake Up Frame to Indicate Group Addressed Frames Transmission
BSS Transition Improvements
Co-existence Beacon Element
NDP Transmission Date: Authors: Month Year Month Year
Bandwidth Indication Design for 120MHz
Improvement to TWT Parameter set selection
Spec Text Motion Date: Authors: July 2018 Month Year
First Path FTM SFD Text Date: Authors: December 2017
Group Delay for Group Addressed Wake Up Frames
CID#102 - Channel Allocation
Motion to accept latest draft of TGp
TIM Offset of Page Segments
CSN & BSS Bridging Date: Authors: Jan 2013
AP Location Capability
Discussion on CR for CID 5066
Local Administrator Advertisements
AP Power Down Notification
Negotiation for HEz Ranging for Passive Location Support
IEEE Liaison Report for
CID#89-Directed Multicast Service (DMS)
Channel Allocation March 2008 Authors: Date: Month Year
Resolution to TGaj Draft 0.01 CID 146
Broadcast Service Advertisements
Mutliband-60GHz-Location-Capability-Publishing
IEEE Liaison Report for
TGaj Editor Report for CC22
Discussion concerning MC-OOK and CIDs 212 and 665
Centralized Clustering Resolution to CID 127
ESP Element ID Request Date: Authors: March 2016 Month Year
Supporting Authentication/Association for Large Number of Stations
Tge Request to ANA Srinivas Kandala Sharp Labs of America, Inc.
VHT NAV Assertion Date: Authors: Month Year
3-4, Hikarino-oka, Yokosuka, Japan
TGaj Editor Report for LB226
Timing Measurement Date: Authors: Jan 2010 November 2007
Dynamic TIM and Page Segmentation
GCR using SYNRA for GLK Date: Authors: July 2015 Month Year
TGp Motions for Tuesday
Month Year doc.: IEEE yy/xxxxr0 November 2013
MIMO phase in MU-MIMO Beamforming
Alternative Transport for Event and Diagnostic Reporting
BSS Transition with Bearing
Proposed Normative Text Changes Concerning Poll Responses
Spectrum Allocation for Wireless LAN and ITS in Japan
Results for SS6 calibration case for single BSS and OBSS
Box 5 results for Single BSS Calibration Case
Month Year doc.: IEEE yy/xxxxr0
Group Synchronized DCF
Discussion concerning MC-OOK and CIDs 212 and 665
Broadcast Service Advertisements
Proposed Resolution to CID 147 in CC12
Unsolicited Block ACK Extension
ISTA2RSTA LMR Feedback AP Policy and Negotiation
First Path FTM SFD Text Date: Authors: December 2017
Request for Legacy IE ID for RSN Extension
Presentation transcript:

Motivation for Vendor Specific Request Element Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2018 Motivation for Vendor Specific Request Element Date: 2018-01-17 Authors: C. Hansen, Peraso John Doe, Some Company

Abstract Use case example for the Vendor Specific Request Element Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2018 Abstract Use case example for the Vendor Specific Request Element C. Hansen, Peraso John Doe, Some Company

Information Request Example (1) January 2018 Information Request Example (1) PBSS containing PCP 2 and STA 3 and STA 4 STA 1 would like to determine if STA 3 in the PBSS has Vendor Specific Capabilities A and B. PCP 2 STA 3 STA 1 STA 4 C. Hansen, Peraso

Information Request Example (2) January 2018 Information Request Example (2) C. Hansen, Peraso

Information Request Example (3) January 2018 Information Request Example (3) Also Extended Request because the Element IDs are limited C. Hansen, Peraso

802.11-2016 Vendor Specific Element January 2018 802.11-2016 Vendor Specific Element The Vendor Specific Element field can be used for responses, but it is not suitable for requests. A STA may have several possible elements it could share. C. Hansen, Peraso

Solution – New Vendor Specific Request (2) January 2018 Solution – New Vendor Specific Request (2) Example: STA 1 makes a Vendor Specific Request for Vendor Specific Elements A and B from STA 3 using an Information Request to PCP 2. PCP 2 responds with the appropriate Vendor Specific Elements for STA 3. C. Hansen, Peraso

Solution – New Vendor Specific Request January 2018 Solution – New Vendor Specific Request C. Hansen, Peraso

References January 2018 doc.: IEEE 802.11-yy/xxxxr0 Month Year C. Hansen, Peraso John Doe, Some Company