Considerations on post wake-up sequences

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /0881r1 July 2015 Woojin Ahn, Yonsei Univ.Slide 1 Regarding buffer status of UL-STAs in UL- OFDMA Date: Authors:
Advertisements

Multiple Data Rates for WUR
Multiple Data Rates for WUR
Supporting Low Power Operation
Overall MAC Procedure for WUR
AP Power Saving Date: Authors: May 2017 Month Year
WUR Reconnection Usage Model
WUR Negotiation and Acknowledgement Procedure Follow up
On AP Power Saving Usage Model
Discussion of Duty-Cycled Wake-Up Receivers
Purpose Indication of WUR Packets
WUR Negotiation and Acknowledgement Procedure Follow up
High Level MAC Concept for WUR
Demand on Roaming for WUR
WUR coexistence with existing power save mode
Considerations on WUR Design
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
WUR MAC issues follow-up
Considerations for WUR Response
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Demand of Being Woken Up While Moving Follow-up
Wake Up Frame to Indicate Group Addressed Frames Transmission
Channel Access for WUR FDMA
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Assign and Update Wake-Up Signals in WLAN with Wake-Up Radio Receivers
2840 Junction Ave, San Jose, CA 95134, USA
Wake up packet contents
WUR Use Cases and Requirements
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
WUR MAC issues follow-up
Regarding UL MU protection
SFD Proposal on Retransmission
2840 Junction Ave, San Jose, CA 95134, USA
Group Delay for Group Addressed Wake Up Frames
Power saving operation for WUR STAs in duty cycle mode
Regarding HE fragmentation
WUR Use Cases and Requirements
WUR MAC and Wakeup Frame
Month Year doc.: IEEE yy/xxxxr0
AP re-discovery by WUR STA
Further Consideration for WUR Acknowledgement Indication
CW value after UL MU procedure
Multiple Data Rates for WUR
Power saving operation for WUR STAs in duty cycle mode
Packet Design for Wake-up Receiver (WUR)
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Regarding buffer status of UL-STAs in UL-OFDMA
Considerations for WUR Response
BSS parameters update notification
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
WUR Security Proposal Date: Authors: September 2017
WUR Security Proposal Date: Authors: September 2017
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
WUR Negotiation and Acknowledgement Procedure Follow up
Regarding HE fragmentation
Power saving operation for WUR STAs in duty cycle mode
WUR MAC and Wakeup Frame
Power Efficient WUR AP Discovery
Purpose Indication of WUR Packets
On AP Power Saving Usage Model
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
CW value after UL MU procedure
Channel Access for WUR FDMA
Month Year doc.: IEEE yy/xxxxr0
WUR Negotiation and Acknowledgement Procedure Follow up
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Power Efficient WUR AP Discovery - A Follow Up
19, Yangjae-daero 11gil, Seocho-gu, Seoul , Korea
Further Consideration for WUR Acknowledgement Indication
Purpose Indication of WUR Packets
Presentation transcript:

Considerations on post wake-up sequences Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2017 Considerations on post wake-up sequences Date: 2017-01-16 Authors: Woojin Ahn et al., WILUS John Doe, Some Company

Abstract Discussing post wake-up sequences of WUR STAs January 2017 Abstract Discussing post wake-up sequences of WUR STAs Regarding transmission failure and recovery Proposing to apply Wake-Up (WU) report exchange Avoiding excessive recovery delay Drawing a boundary between the Primary Connectivity Radio (PCR) and WUR MAC procedure Detecting false wake-up attack Considerations on WU report on group addressed (multiple) wake-up scenario Woojin Ahn et al., WILUS

General post wake-up sequence January 2017 General post wake-up sequence If a transmitted Wake-Up Packet (WUP) is delivered successfully to a WUR STA, the PCR of the STA starts to wake After the STA wakes up, AP may initiate PCR transmission sequence AP must wait until the STA’s PCR is ready (Wake-Up Delay) If the AP didn’t get any response, the reason could be one of: PCR Data or Ack transmission failure WUP transmission failure Woojin Ahn et al., WILUS

Recovery procedure of WUR AP January 2017 Recovery procedure of WUR AP Since AP cannot find out what causes the lack of response, it should retry the whole procedure starting from WUP retransmission An excessive delay might occur including WUP, PCR transmission, WUD, and additional channel access delays The failure of PCR MAC procedure requires WUR MAC to invoke a retransmission of WUP WUR is expected to cooperate with many other different 802.11 MAC standards We need to minimize a requirement for changes between two different MAC specifications It is necessary to finalize WUR wake-up procedure before the PCR data exchange In order to avoid such an excessive delay of WUP retransmission To separate wake-up sequence from PCR MAC procedure Woojin Ahn et al., WILUS

Wake-Up report exchange (1) January 2017 Wake-Up report exchange (1) A 2-way handshake protocol using PCR can be considered A WUR STA reports its wake-up status WU report/response, if initiated by WUR STA WU report poll/report, if initiated by WUR AP Some useful information can also be included in the frame exchange Status information, following MAC sequence Woojin Ahn et al., WILUS

Wake-Up report exchange (2) January 2017 Wake-Up report exchange (2) By applying WU report exchange, If there’s no WU report from the intended STA, AP retransmits WUP instead of initiating PCR transmission sequence which causes waste of resource In case of PCR transmission failure, AP doesn’t have to reinvoke WUR procedure The PCR MAC procedure starts with the end of the WU report exchange (WUR MAC) Woojin Ahn et al., WILUS

January 2017 WU report and security WU report procedure can be exploited to detect false wake-up Simply copying and repeating of any captured WUP might cause a STA’s power leakage If a WUR STA, not solicited by the WUR AP, sends a WU report, AP might be aware of an attack from the outside In which case, WU report initiated by the non-AP STA could be more appropriate The AP wouldn’t send WU report poll to which it haven’t sent a WUP After the detecting of false wake-up, WUR (re)association procedure might be invoked Woojin Ahn et al., WILUS

Wake-up report in group addressed WUP January 2017 Wake-up report in group addressed WUP AP might wake-up multiple STA simultaneously with a single WUP To reduce overhead caused by the listing of WUR addresses e.g., modulated by OOK A group management procedure may exist using PCR Group assignment, group address for WUP In Group Addressed (GA) WUR scenario, WU report exchange might incur overhead problem as well WU report might be sent both either contention or scheduling basis The more number of STAs assigned in a same group, the longer the delay caused by the WU reports exchange procedure Woojin Ahn et al., WILUS

January 2017 Considerations on WU report exchange scheme in group wake-up scenario (1) One of the easiest ways is simply not to allow group wake-up STAs to send WU reports To avoid the latency caused by the WU report exchange However, WU report is still important especially for group wake-up STAs The long duration of recovery, including both WUR and PCR MAC procedure, causes power consumption and latency of multiple STAs False wake-up attack with group addressed WUP could be fatal It is necessary to find out a proper way to apply the WU report exchange in group wake-up situation Woojin Ahn et al., WILUS

January 2017 Considerations on WU report exchange scheme in group wake-up scenario (2) One of the main usage scenarios of 11ba standard is IoT networks The variance of number of associated STAs could be much larger than the existing WLAN usage scenario 10s to 100s E.g., Home automation vs. cargo scenario Priority differences A WUR group may be consist of heterogeneous devices E.g., an anchor node (data sink) with a lot of normal sensor nodes STAs may have different WUDs and latency requirements More flexible WU reporting scheme might be necessary instead of a fixed reporting policy For example, letting AP to choose which STAs to send WU reports adaptively Need further discussions Woojin Ahn et al., WILUS

January 2017 Conclusion In this contribution, we have discussed the necessity of WU report and corresponding issues WU report exchange could be beneficial in terms of: Reducing the delay of recovery procedure Boundary between WUR and PCR MAC Detecting false wake-up attack WU report exchange could also be applied to group wake-up scenario Further discussions are required for better application Considering the variety of usage model of 11ba Woojin Ahn et al., WILUS

January 2017 Strawpoll 1 Do you agree that the WU report procedure is necessary for WUR networks? Y/N/A Woojin Ahn et al., WILUS

January 2017 Strawpoll 2 Do you agree that the WU report procedure is necessary for group wake-up STAs? Y/N/A Woojin Ahn et al., WILUS