Further discussion for WLAN Radar

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /0098r0 January 2016 Assaf Kasher, IntelSlide 1 Channel bonding proposals Date: Authors:
Advertisements

Channel Access in A-BFT over Multiple Channels
Channel Width Selection Within TXOP
Bandwidth signaling for EDMG
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
EDMG Capability and Operation Element Channel Indications
Resource Negotiation for Unassociated STAs in MU Operation
Month Year doc.: IEEE yy/xxxxr0 November, 2015
Relay Flow Control Date: Authors: May 2013 Month Year
Power Save Delivery for 11ay
EDMG capabilities for Open Loop Spatial Multiplexing in SU-MIMO
Beamforming for mmWave Distribution Networks
Short SSW Frame for A-BFT
Advanced MU-MIMO acknowledgement and PS flow
Random Access RU Allocation in the Trigger Frame
SU-MIMO Type for Group Addressed Frames
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
Hybrid Beamforming Protocol Design Details
“Near-far” self-classification capabilities of EDMG STAs
Analog and Baseband Beam Tracking in ay
Analog and Baseband Beam Tracking in ay
March 2018 Additions to Group Beamforming in support of Beam Measurement for mmWave Distribution Networks Name Affiliation Address Phone Tony Xiao.
Asymmetric beamforming training procedure enhancements
MU Beamforming for mmWave Distributed Network
MU-MIMO channel access flow for 11ay
120MHz channelization solution
“Near-far” self-classification capabilities of EDMG STAs
TDD-SP Coexistence Date: September 2016
SU-MIMO Type for Group Addressed Frames
Multi-BF Procedure for 11ay
WUR MAC and Wakeup Frame
Random Access RU Allocation in the Trigger Frame
Short SSW Format for 11ay Date: 2016-March-14 Authors: March 2016 Name
WLAN Radar Date: 2018-December-5 Authors: December 2018 Name Company
AP Coordination in EHT Date: Authors: Name Affiliations
Hybrid Beamforming Protocol Design Details
Random Access RU Allocation in the Trigger Frame
Adding control trailer to control mode PPDUs
WUR MAC and Wakeup Frame
Further considerations on WUR frame format
TDD-SP Coexistence Date: September 2016
EDMG PHY Header-A for DCM SQPSK Over Two Channel Aggregation in 11ay
PHY-CCA Indication doc.: IEEE yy/xxxxr0 Date:
Multi-BF Procedure for 11ay
Unsolicited RSS for SLS in DTI
“Near-far” self-classification capabilities of EDMG STAs
Header-A Definition for EDMG Control Mode
BTI and A-BFT for EDMG AP with Multiple Antennas
Considerations on MU-MIMO Protection in 11ac
EDMG PHY Header-A for DCM SQPSK Over Two Channel Aggregation in 11ay
EDMG capabilities for Open Loop Spatial Multiplexing in SU-MIMO
Header-A Definition for EDMG Control Mode
Duration in L-SIG Date: Authors: May 2010 Month Year
SU-MIMO and MU-MIMO link access
Channel Width Selection Within TXOP
WUR MAC and Wakeup Frame
Channelization for China’s Spectrum
Month Year doc.: IEEE yy/xxxxr0 November 2013
Reserving STA Date: Authors: January 2011 January 2011
Discussion on Rank Adaptation
EDMG PHY Header-A for DCM SQPSK Over Two Channel Aggregation in 11ay
EDMG PHY Header-A for DCM SQPSK Over Two Channel Aggregation in 11ay
1MHz mode PHY based power savings
Mechanism for Inter-system Coexistence
EDMG PHY Header-A for DCM SQPSK Over Two Channel Aggregation in 11ay
Reducing Overhead in Active Scanning
Reducing Overhead in Active Scanning
SM Power Save for 11ay Date: Authors: August 2017
DMG STA Directional Transmit Activity Report Frame
Utilizing Unused Resources by Allowing Simultaneous Transmissions
Presentation transcript:

Further discussion for WLAN Radar September 2016 doc.: IEEE 802.11-16/XXXXr0 January 2019 Further discussion for WLAN Radar Date: 2019-01-03 Name Affiliation Address Phone Email Tony Xiao Han Huawei Technologies Tony.hanxiao@huawei.com Rui Du Wei Lin Ross Jian Yu Yan Xin Intel Corporation

Outline Background and motivation Opt 1. No change for the Spec January 2019 Outline Background and motivation Opt 1. No change for the Spec Opt 2. Scheme in [2] Opt 3. Modified scheme based on [2] Opt 4. Dedicated explicit indication scheme based on [2] Summary and comparison Conclusion

Background and motivation 2/23/2019 January 2019 Background and motivation As described in [1], radar use-case in unlicensed mmWave starts to gain interest in the industry for many applications. Hence, in [1, 2], radar is proposed as part of the WLAN framework, in order to achieve better Coexistence and sharing between radar function and WLAN function. In this proposal, we want to summarize and analyze all possible solutions considered so far to include radar function in WLAN, and ask for the feedback from the group. Oren Kedem, Intel et al

Background and motivation 2/23/2019 January 2019 Background and motivation Monostatic radar is a type of radar in which the transmitter and receiver are collocated. Bistatic radar is the name given to a radar system comprising a transmitter and receiver that are separated by a distance comparable to the expected target distance. A system containing multiple spatially diverse Monostatic radar or Bistatic radar components with a shared area of coverage is called Multistatic radar. The Multistatic radar could be used to do, e.g., target detection, with the following advantages comparing to Monostatic radar: Multistatic radar is able to localize the target with only a single time radar signal transmission Multistatic radar system, which include multiple receivers at different locations, is more robust than Monostatic radar on target detection. Bistatic Radar Multistatic Radar Oren Kedem, Intel et al

Opt 1. No change for the Spec 2/23/2019 January 2019 Opt 1. No change for the Spec A possible scheme without changing the Spec The radar STA (i.e., STA with radar function) could send DMG CTS-to-Self to set the NAV, Then radar STA could transmit any radar signal during the TXOP. Pros No change for the Spec (especially in the late phase of the 11ay project) Could work for Monostatic radar Cons May not robust enough, since the WLAN device may miss the DMG CTS-to-Self and fail to set the NAV, and then only energy detection could be used for the following radar signal. Does not support Bistatic/Multistatic radar. Since the transmitter and receiver are in different devices for Bistatic/Multistatic radar, so without explicit indication, the receivers do not know the PPDU is for radar, then do not know when to turn on/switch to radar functionality, and do not know when and where to receive the radar signal. Oren Kedem, Intel et al

Opt 2. Scheme in [2] January 2019 2/23/2019 January 2019 Opt 2. Scheme in [2] Scheme in [2] including some modification for the Spec, e.g., The DMG PHY and EDMG PHY is used to implement radar functionality Setting RA=TA for some types of frame (e.g., SSW), and this “may” indicate for radar functionality Adding TRN for some types of frame (e.g., SSW), which is not allowed in the Spec for now Pros More robust than Opt 1, since radar signal is included in a DMG/EDMG PPDU. Could work for Monostatic radar Cons EDMG PHY is not a good choice, since 11ad STA cannot understand 11ay preamble and so on (e.g., MAC header including RA, TA, and Duration fields), and cannot set NAV. Hence, 11ad STA may potentially transmit, which could create interference to radar signal. Receiving a DMG PPDU with RA=TA, the unintended STAs do not explicitly know it’s radar PPDU/TXOP, then the STAs only keep quiet during the TXOP, but cannot go to sleep (or go to sleep with concern/risk), since the TXOP holder (e.g., PCP/AP) may transmit to them. But keeping awake and receiving each following PPDU is wasting the energy of the unintended STAs. Does not support Bistatic/Multistatic radar. Since the transmitter and receiver are in different devices for Bistatic/Multistatic radar, so without explicit indication, the receivers do not know the PPDU is for radar, then do not know when to turn on/switch to radar functionality, and do not know when and where to receive the radar signal. Oren Kedem, Intel et al

Opt 3. Modified scheme based on [2] 2/23/2019 January 2019 Opt 3. Modified scheme based on [2] Enhanced scheme based on [2] Only the DMG PHY is used to implement radar functionality Using RA=TA for few types of frame (e.g., SSW) as explicit indication for radar PPDU/TXOP Adding TRN for some frames (e.g., SSW) Pros More robust than Opt 1&2, since radar signal is included in a DMG PPDU and explicitly indicated. The unintended EDMG STAs explicitly know it’s radar PPDU/TXOP, then the STAs could go to sleep without any concern/risk, since the TXOP holder (e.g., PCP/AP) will not transmit to them during the TXOP. Cons It is a misusing of “RA=TA” and will cause problem in the future. E.g., if we want other function/indication, and together with setting RA=TA at the same time, then it will cause problem for radar functionality (e.g., will cause false alarm for Bistatic/Multistatic radar) and for EDMG STA (will treat it as radar PPDU/TXOP, which is not, and will improperly go to sleep). Still does not work for Bistatic/Multistatic radar. Since the RA=TA, i.e., RA does not indicate the actual receiver, hence the receiver could not receive this radar PPDU. Oren Kedem, Intel et al

Opt 4. Enhanced scheme based on [2] 2/23/2019 January 2019 Opt 4. Enhanced scheme based on [2] Enhanced scheme based on [2] Only the DMG PHY is used to implement radar functionality Adding dedicated explicit indication for radar PPDU/TXOP E.g., 1 reserved value in Scrambler Initialization field (in Table 46 in [3]) in control mode PPDU Adding TRN for some frames (e.g., SSW) Pros More robust than Opt 1&2&3, since radar signal is included in a DMG PPDU and dedicated explicitly indicated. The unintended EDMG STAs explicitly know it’s radar PPDU/TXOP, then the STAs could go to sleep without any concern/risk, since the TXOP holder (e.g., PCP/AP) will not transmit to them during the TXOP. Could work for Monostatic radar and Bistatic/Multistatic radar Will not cause any further problem in the future Cons Need explicit indication (if we call this is Cons/drawback) Oren Kedem, Intel et al

Summary and comparison 2/23/2019 January 2019 Summary and comparison Robustness/Coexistence Monostatic radar Bistatic/Multistatic radar Power saving Spec change Opt 1. No change for the Spec E.g., DMG CTS-to-Self, then any radar signal Low. since the WLAN device may miss the DMG CTS-to-Self and fail to set the NAV Yes (could work) No Opt 2. Scheme in [2] E.g., DMG PHY and EDMG PHY, RA=TA (non explicit indication ), adding TRN Medium. Better than Opt 1. But EDMG PHY is not a good choice Opt 3. Modified scheme based on [2] E.g., DMG PHY, explicit indication by setting RA=TA for few types of frame , adding TRN Better than Opt 1&2. But it is a misusing of “RA=TA” and will cause problem in the future. The unintended EDMG STAs explicitly know it’s radar PPDU/TXOP, then the STAs could go to sleep without any concern/risk, Opt 4. Dedicated explicit indication scheme based on [2] E.g., DMG PHY, dedicated explicit indication, adding TRN High. Better than Opt 1&2&3 Oren Kedem, Intel et al

January 2019 Conclusions This contribution summarizes and analyzes all possible solutions considered so far to include radar functionality in WLAN After comparison, it seems that the Opt 1 could work without changing the Spec. If the group agrees to change the Spec, then the Opt 4 is a better solution.

January 2019 Straw Poll/Motion 1 Which option do you prefer for adding radar functionality? (The corresponding draft text will be provided if Opt 4 is preferred) Opt 1. No change for the Spec E.g., DMG CTS-to-Self, then any radar signal Opt 2. Scheme in [2] E.g., DMG PHY and EDMG PHY, RA=TA, adding TRN Opt 3. Modified scheme based on [2] E.g., DMG PHY, explicit indication by misusing RA=TA, adding TRN Opt 4. Dedicated explicit indication scheme based on [2] E.g., DMG PHY, dedicated explicit indication, adding TRN Abstain

January 2019 References [1] 11-18-2094-00-00ay-wlan-radar.pptx [2] 11-18-2095-00-00ay-wlan-radar-annex.docx [3] Draft P802.11ay_D2.1.pdf