Vendor Specific WUR Frame Follow Up

Slides:



Advertisements
Similar presentations
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Advertisements

WUR Negotiation and Acknowledgement Procedure Follow up
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Vendor Specific WUR Frame
WUR Negotiation and Acknowledgement Procedure Follow up
High Level MAC Concept for WUR
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Mature Topics for Draft 0.1
2200 Mission College Blvd., Santa Clara, CA 95054, USA
WUR Discovery Frame Format
BSSID Information in FCS
WUR frame format follow-up
Improve Scanning for Identifying Transmitted BSSID
Overview of ba Power Management in D0.4
Short WUR Frame Date: Authors: Mar 2018 Liwen Chu Marvell
Computation of TSF Update
WUR frame format follow-up
WUR frame format follow-up
Examples of Integrating WUR with Existing Power Save Protocol
Suggested Practice for SFD and Draft Spec Text Proposal
Considerations on VL WUR frames
Vendor Specific WUR Frame Follow Up
Vendor Specific WUR Frame Follow Up
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Operation after Wake-up Frame Transmission and Reception
Overview of ba Power Management in D0.4
Overview of ba Power Management in D0.4
2200 Mission College Blvd., Santa Clara, CA 95054, USA
WUR Action Frame Format Follow up
Operation after Wake-up Frame Transmission and Reception
Indication for WUR Duty Cycle
Starting Time Indication of WUR Beacon and Duty Cycle Operation
Indication for WUR Duty Cycle
BSSID Information in FCS
WUR frame format follow-up
WUR Action Frame Format Follow up
Overview of ba Power Management in D0.4
Consideration of EDCA for WUR Signal
2200 Mission College Blvd., Santa Clara, CA 95054, USA
WUR frame format follow-up
WUR Discovery Frame Format
Vendor Specific WUR Frame Follow Up
2200 Mission College Blvd., Santa Clara, CA 95054, USA
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Comment Classification for Draft 1.0
Comment Classification for Draft 1.0
Comment Classification for Draft 1.0
2200 Mission College Blvd., Santa Clara, CA 95054, USA
WUR frame format follow-up
Comment Classification for Draft 2.0
Operation after Wake-up Frame Transmission and Reception
Operation after Wake-up Frame Transmission and Reception
BSSID Information in FCS
Comment Classification for Draft 2.0
WUR Discovery Frame Format
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Comment Classification for Draft 2.0
WUR MAC and Wakeup Frame
WUR Negotiation and Acknowledgement Procedure Follow up
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Overview of ba Power Management in D0.4
Consideration of EDCA for WUR Signal
Indication for WUR Duty Cycle
Starting Time Indication of WUR Beacon
2200 Mission College Blvd., Santa Clara, CA 95054, USA
Comment Classification for Draft 3.0
WUR Negotiation and Acknowledgement Procedure Follow up
Multi-link Operation Framework
Comment Classification for Draft 3.0
Comment Classification for Draft 3.0
Presentation transcript:

Vendor Specific WUR Frame Follow Up July 2008 doc.: IEEE 802.11-08/1021r0 Vendor Specific WUR Frame Follow Up Date: 2017-09-xx Name Affiliation Address Phone Email Po-Kai Huang Intel 2200 Mission College Blvd., Santa Clara, CA 95054, USA   +1-408-765-8080   po-kai.huang@intel.com Dan Bravo Noam Ginsburg Robert Stacey Po-Kai Huang et al. (Intel) Peter Loc

Abstract We discuss in [1] about the need to have vendor specific WUR frame to carry vendor specific content Enable future invention in WFA Enable further invention for specific vendor’s needs Based on the discussion of frame format presented in [2], we provide further thought of the design to minimize the spec impact Po-Kai Huang et al. (Intel)

Support of vendor specific frame We expect that vendor specific frame to be useful in the future for WFA extension or vendor specific needs The vendor specific content may also have variable length, which may increase implementation cost if we make it mandatory to support vendor specific frame. Due to the reasons above, the support for vendor specific frame should be optional Po-Kai Huang et al. (Intel)

Consideration for frame format design Based on the structure proposed in [2], a simple design for vendor specific frame can be the following A value in the Type field of Frame control can indicate vendor specific frame Address and TD control fields can indicate vendor specific ID, ex., OUI Frame Body can carry vendor specific content Po-Kai Huang et al. (Intel)

Conclusion We follow up on the design of vendor specific frame To avoid complication of STA’s implementation, we think vendor specific frame is optional for STA to support We think the design of vendor specific frame can fit in the general concept of WUR frame format without complicating the design We propose to have a value in the type field to indicate vendor specific frame Po-Kai Huang et al. (Intel)

Straw Poll #1 Do you support that a value in the Type field of WUR frame is used to indicate vendor specific frame that can carry vendor specific content It is optional for a AP or non-AP STA to support transmission or reception of vendor specific frame. Po-Kai Huang et al. (Intel)

Reference [1] 11-17-1008-00-00ba Vendor Specific WUR Frame [2] 11-17-1004-01-00ba Considerations on WUR frame format Po-Kai Huang et al. (Intel)