A discussion of ED & PD for & LAA in unlicensed spectrum

Slides:



Advertisements
Similar presentations
Month Year doc.: IEEE yy/xxxxr0 November 2014
Advertisements

Doc.: IEEE /0633r0 Submission May 2008 Andrew Myles (Cisco)Slide 1 Discussion of 40Mhz coexistence with 20MHz BSS in secondary channel Date:
Doc.: IEEE /0079r0 Submission September 2015 Andrew Myles (Cisco)Slide 1 Discussion of issues related to EN revision 16 September 2015.
Doc.: IEEE /0079r1 Submission September 2015 Andrew Myles (Cisco)Slide 1 Discussion of issues related to EN revision 16 September 2015.
Doc.: IEEE /0024r0 Submission Feedback on 3GPP CRs: LAA Multi-Channel Access and Energy Detect (ED) Coexistence Slide 1 Date: Authors:
A proposed response to 3GGP on fourteen coexistence issues
Month Year doc: IEEE /xxxxr0
Agenda for PDED Ad Hoc teleconference on 27 September 2016
CCA Sensitivity Date: September 2017
Comments on LAA EVM Date: Authors: January 2015 Month Year
Agenda for PDED Ad Hoc meeting in San Antonio in September 2016
Summary of WG activities
Reporting Mechanisms Needed for DFS to Support Regulatory Compliance
July 2010 doc.: IEEE /0903r0 A resolution proposal comments related to for next generation security in built on changes in ac 14.
A proposed response to 3GGP on fourteen coexistence issues
Agenda for PDED ad hoc teleconference on 11 October 2016
Proposal for ETSI BRAN to restrict blocking energy
Discussion on detection schemes and thresholds
July 2010 doc.: IEEE /0xxxr0 A summary of draft LS from 3GPP in response to IEEE 802 LS in March May 2017 Authors: Name Company Phone.
Presentation to TGax relating to coexistence efforts in Coexistence SC
July 2010 doc.: IEEE /0xxxr0 Discussion of issues related to extending dual threshold in next revision of EN June 2017 Authors: Name.
Proposed response to 3GPP ED request
Agenda for IEEE Coexistence SC meeting in Chicago in March 2018
July 2010 doc.: IEEE /0xxxr0 Revised shorter presentation to TGax relating to coexistence efforts in Coexistence SC 12 Sept 2017 Authors: Name.
July 2010 doc.: IEEE /0xxxr0 Revised shorter presentation to TGax relating to coexistence efforts in Coexistence SC 13 Sept 2017 Authors: Name.
Should IEEE be proposed as an IMT-2020 technology?
July 2010 doc.: IEEE /0xxxr0 What is the status of the ETSI BRAN work on a revised version of EN ? 10 Nov 2015 Authors: Name Company Phone.
Agenda for PDED Ad Hoc meeting in Atlanta in January 2017
Issues for clarification related to “paused COT” in EN
Discussion on detection schemes and thresholds
July 2010 doc.: IEEE /0xxxr0 Supporting presentation for IEEE WG Liaison Statement to ETSI BRAN relating to next revision of EN
July 2010 doc.: IEEE /0xxxr0 A summary of most recent LS from 3GPP RAN/RAN1 and proposed process for review 13 Jan 2017 Authors: Name Company.
July 2010 doc.: IEEE /0xxxr0 Motion for LS to 3GPP RAN4 from IEEE PDED ad hoc meeting in Daejeon in May May 2017 Authors: Name.
3GPP RAN1 and RAN4 status on NR-Unlicensed and LAA
July 2010 doc.: IEEE /0xxxr0 A proposal for enabling the use of IEEE ax-stye Spatial Reuse under EN November 2017 Authors: Name.
July 2010 doc.: IEEE /0xxxr0 Revised shorter presentation to TGax relating to coexistence efforts in Coexistence SC 13 Sept 2017 Authors: Name.
IEEE PDED ad hoc closing report in Daejeon in May 2017
IEEE Coexistence SC closing report in San Diego in July 2018
Summary of workshop on NR unlicensed
IEEE PDED ad hoc closing report in Vancouver in Mar 2017
Agenda for PDED Ad Hoc meeting in San Antonio in September 2016
What should WG do about the ED related request from 3GPP RAN1?
TGh Monitored Signal Strength Indication (MSSI)
IEEE Coexistence SC closing report in Warsaw in May 2018
IEEE Coexistence SC closing report in Orlando in November 2017
Functional Requirements for EHT Specification Framework
July 2010 doc.: IEEE /0xxxr0 A summary of draft LS from 3GPP in response to IEEE 802 LS in March May 2017 Authors: Name Company Phone.
3GPP RAN1 status on NR-Unlicensed
CCA Sensitivity Date: September 2017
Comments on LAA EVM Date: Authors: January 2015 Month Year
3GPP RAN1 status on NR-Unlicensed
IEEE Coexistence SC closing report in Irvine in January 2018
PDED Ad Hoc closing report in San Antonio in November 2016
July 2010 doc.: IEEE /0xxxr0 A summary of proposed LS from IEEE 802 to 3GPP RAN/RAN1 on technical & process issues 26 July 2016 Authors: Name.
PDED Ad Hoc closing report in San Antonio in November 2016
NGV Backward Interoperability: Follow-up
July 2010 doc.: IEEE /0xxxr0 Recommendation from PDED Ad Hoc in San Antonio in Nov 2016 wrt ED threshold 9 Nov 2016 Authors: Name Company Phone.
IEEE Coexistence SC closing report in Hawaii in Sept 2018
IEEE Coexistence SC closing report in Berlin in July 2017
3GPP RAN1 status on NR-Unlicensed
Duration in L-SIG Date: Authors: May 2010 Month Year
Comments on LAA EVM Date: Authors: January 2015 Month Year
TGah Coexistence Assurance
July 2010 doc.: IEEE /0903r0 A resolution proposal comments related to for next generation security in built on changes in ac 14.
The use of no LBT for DRS is not justified by history
July 2010 doc.: IEEE /0xxxr0 LBT should remain the basis of fair & efficient coexistence in 6 GHz unlicensed spectrum 1 July 2019 Authors: Name.
Functional Requirements for EHT Specification Framework
Coexistence in 6 GHz License-exempt Spectrum
LAA / Wi-Fi Coexistence evaluations with commercial hardware
July 2010 doc.: IEEE /0xxxr0 NR-U’s definition of success for LBT needs to be realigned with & European rules 1 July 2019 Authors: Name.
Presentation transcript:

A discussion of ED & PD for 802.11 & LAA in unlicensed spectrum July 2010 doc.: IEEE 802.11-10/0xxxr0 A discussion of ED & PD for 802.11 & LAA in unlicensed spectrum 18 July 2016 Authors: Name Company Phone email Andrew Myles Cisco +61 2 84461010 +61 418 656587 amyles@cisco.com Andrew Myles, Cisco Andrew Myles, Cisco

IEEE 802 should explain & promote the need for 802 IEEE 802 should explain & promote the need for 802.11 PD detection … because it is important! The situation The problem The answer 3GPP RAN1 is requesting that future multi-technology coexistence be driven purely by a fixed ED threshold 3GPP RAN1’s request should challenge 802.11 WG to revaluate its assumptions & current solutions IEEE 802 must be driven by unlicensed band’s Guiding Principle that transmitters should not harm receivers Unfortunately, neither 802.11 or LAA satisfy the Guiding Principle in mixed environments very well The underlying issue is that neither 802.11 or LAA can detect the other system in some cases Lesson: both ED & PD matter for multi- technology coexistence environments The existence of billions of 802.11 systems today means that an 802.11 based PD must be used Possible next steps IEEE 802 should consider a range of “next steps” to explain and promote the need for 802.11 PD detection Andrew Myles, Cisco

3GPP RAN1 is requesting that future multi-technology coexistence be driven purely by a fixed ED threshold The IEEE 802 review of LAA Rel. 13 resulted in IEEE 802 requesting 3GPP RAN1 to make LAA more sensitive to 802.11 transmissions: This request was based on the observations that the proposed LAA mechanism (based on ED of -72dBm only) does not ensure fair coexistence See Comment 3 in 19-16-0037-09 for details RAN1 rejected IEEE 802’s request on the basis that RAN1 has had considerable debate and has agreed there is not a problem, but without responding to the particular issues raised by IEEE 802 See Response 3 in R1-166040 RAN1 further suggested that 802.11 also use ED of -72dBm in the future RAN1 respectfully requests future IEEE 802.11 technologies to align the energy detection threshold used with other technologies operating in the same unlicensed band, e.g., -72 dBm. An energy detection threshold of -72 dBm has been chosen by 3GPP for Rel-13 LAA also with an interest in aligning with other technologies in the future. Andrew Myles, Cisco

3GPP RAN1’s request should challenge 802 3GPP RAN1’s request should challenge 802.11 WG to revaluate its assumptions & current solutions 802.11 has been successfully operating and enabling coexistence for many years using both an ED (energy detection) of -62dBm and a PD (preamble detection) of -82dBm Success in this case has been the property of 802.11 that allows anyone, anytime, anyplace to operate a network that works well enough! However, the success has been made easier because most of the time 802.11 systems only have to share with other 802.11 systems That may no longer be the case, with the potential introduction of new technologies like LAA, LTE-U and MulteFire In the future, 802.11 systems may want to coexist with each other differently, with an increased focus on frequency reuse in 802.11ax 3GPP RAN1’s suggestion to drive coexistence based only on ED of -72dBM should challenge the 802.11 WG to revaluate our assumptions & solutions Andrew Myles, Cisco

IEEE 802 must be driven by unlicensed band’s Guiding Principle that transmitters should not harm receivers The rules for unlicensed spectrum in various regulatory domains are usually some variant of: Recognised services have absolute priority over unlicensed devices Unlicensed devices should avoid interfering with other unlicensed devices … and accept interference from other unlicensed devices! This leads to a Guiding Principle that has been an underlying driving assumption in almost all 802.11 WG activities over 25 years An 802.11 device (or any unlicensed device) should not transmit in an unlicensed channel if it is reasonably likely to cause harm to an ongoing reception by another unlicensed device in the channel This Guiding Principle should be something for which there should be no disagreement Note: it is not claimed that the Guiding Principle is a specific law or regulation anywhere, just that it represents best practice everywhere Andrew Myles, Cisco

Harm in the Guiding Principle must refer to damage to any ongoing reception … not a long term average The Guiding Principle refers to harm to an ongoing reception by another unlicensed device Harm has been interpreted by various stakeholders in two main ways In 802.11 WG, harm is generally focused on the potential damage caused to any ongoing current reception In 3GPP RAN1, harm is often evaluated by simulation of average performance in various environments, rather than harm to the ongoing current reception Unfortunately, averaging over time and environments hides too many sins and cannot be used to protect receptions by individual devices 3GPP RAN1’s simulation do not evaluate many important environments Even for the environments simulated, averages (or even 90% percentiles) will not reveal cases where some devices are unfairly “locked out” Every device has a right to operate, and so any evaluation of harm must be focused on any ongoing current reception … not a long term average Andrew Myles, Cisco

Unfortunately, neither 802 Unfortunately, neither 802.11 or LAA satisfy the Guiding Principle in mixed environments very well Transmitting device Does transmitting device satisfy the Guiding Principle in a … … 802.11 or LAA only environment? … mixed 802.11/LAA environment? 802.11   LAA A issue for 3GPP RAN , not 802.11 WG Andrew Myles, Cisco

This presentation is based on common definitions of Energy Detection (ED) & Preamble Detection (PD) Refers to the ability of the receiver to detect energy level in the channel based on the noise floor, ambient energy, interference sources, and any unidentifiable 802.11 transmissions that can’t be decoded Preamble detection (PD) Refers to the ability of the receiver to detect and decode an 802.11 preamble In addition, Clear Channel Assessment (CCA) must be reported as BUSY when an 802.11 preamble is detected, and must be held as BUSY for the length of the received frame as indicated in the frame's PLCP Length field Andrew Myles, Cisco

802. 11 generally satisfies the Guiding Principle in an 802 802.11 generally satisfies the Guiding Principle in an 802.11-only environment Assumption: 802.11 in 802.11 only environment < -82dBm 802.11 tx’s … … low risk of adversely affecting other 802.11 systems given they are so far away  PD > -82dBm 802.11 doesn’t tx … … avoids significant risk of damaging ongoing tx’s by other 802.11 systems 1st  802.11 < -62dBm Probably collision (otherwise would PD trigger), 802.11 tx’s … … low risk of tx causing adverse effect to ongoing tx’s by other 802.11 systems given they probably in a collision already, and there is some possibility of successful tx 2nd  ED > -62dBm Probably collision (otherwise PD would trigger), but 802.11 doesn’t tx … … there is not much pointtx’ing given the energy is so loud  Andrew Myles, Cisco

802.11 doesn’t satisfy the Guiding Principle very well in all cases in a mixed LAA/802.11 environment Assumption: 802.11 in mixed LAA/802.11 environment < -82dBm 802.11 tx’s … … low risk of adversely affecting other 802.11 systems given they are so far away (note: PD not relevant to LAA)  PD > -82dBm 802.11 doesn’t tx … … avoids significant risk of damaging ongoing tx’s by other 802.11 systems (note: PD not relevant to LAA) 1st  802.11 < -62dBm 802.11 tx’s … … but will tx over top of LAA tx’s down to -82dBm & below (but typically will not adversely affect other 802.11 tx’s) … but mitigated noting LAA claims to handle interference well 2nd  ED > -62dBm 802.11 doesn’t tx … … there is not much point tx’ing given the energy is so loud  Andrew Myles, Cisco

LAA doesn’t satisfy the Guiding Principle in a mixed LAA/802 LAA doesn’t satisfy the Guiding Principle in a mixed LAA/802.11 environment very well – and it matters! < -72dBm LAA tx’s … … but will tx over top of ongoing 802.11 tx’s down to -82dBm, where 802.11 would not in the same circumstances Assumption: LAA in mixed LAA/802.11 environment  ED > -72dBm LAA doesn’t tx … … which means that LAA respects ongoing 802.11 tx’s from -72dBm to -62dBm better than 802.11 protects LAA tx’s Only  LAA 3GPP RAN’s own studies indicate that LAA not satisfying the Guiding Principle actually matters The issue above is not just a “thought experiment” with no practical effect As noted in the IEEE 802 LS to 3GPP RAN1, 3GPP RAN1’s own simulation studies (despite their flaws) have shown that if LAA only uses an ED of -72dBm, fair coexistence with IEEE 802.11 cannot always be achieved Also as noted in the LS, unfair coexistence with 802.11 is particularly acute in scenarios where the full coverage of each 802.11 AP is utilized (which are under-represented in 3GPP RAN1 studies), since devices with weaker link strengths are especially sensitive to interference. Not done PD Andrew Myles, Cisco

The underlying issue is that neither 802 The underlying issue is that neither 802.11 or LAA can detect the other system in some cases A review of what causes 802.11 & LAA to not satisfy the Guiding Principle very well in all cases reveals a common factor… 802.11 does not do as well when it can’t distinguish between a collision and an LAA transmission between -82dBm and -62dBm LAA does not do as well when it can’t distinguish between a collision and an 802.11 transmission between -82dBm and -72dBm The underlying issue is that both systems can’t decode the transmissions of the other technology in any circumstances, and thus can’t differentiate between a collision and a transmission The problem is not currently equal between the technologies because 802.11 has a 20dBm “gap”, whereas LAA only has a 10dBm “gap” Adoption of a common ED = -72dBm (as suggested by 3GPP RAN1) makes the problem equally bad … but does not solve it! Andrew Myles, Cisco

Lesson: both Energy & Preamble Detection matter for multi-technology coexistence environments The underlying issue described on the previous page has a lesson as a corollary Both ED and PD are important because: ED can be used to detect collisions PD can be used to differentiate transmissions from collisions This is a lesson that was known as far back as 1998/99 In 1998/99 the IEEE 802.11 WG and ETSI BRAN recognised the important of a common PD mechanism when they agreed on a common PHY for 802.11 and HIPERLAN II Of course, this agreement was ultimately irrelevant because HIPERLAN II failed in the market place, meaning coexistence with 802.11 was moot Lesson Both Energy Detection (ED) and Preamble Detection (PD) matter for multi-technology coexistence! Andrew Myles, Cisco

Preamble Detection is likely to become increasingly important to enable wide deployment of frequency reuse Improved frequency reuse is asserted to be a feature of LAA … and of 802.11ax! Wide deployment of frequency reuse requires transmitters attempting improved frequency reuse to understand the likelihood of interfering with other systems Note: this assertion assumes a desire to satisfy the Guiding Principle, eg LAA can never attempt improved frequency reuse when just using just ED because the other systems might be a legacy 802.11 system that will suffer interference ED is not sufficient to make this evaluation; a common PD mechanism is required! Andrew Myles, Cisco

The existence of billions of 802. 11 systems today means that an 802 The existence of billions of 802.11 systems today means that an 802.11 based PD must be used The lesson of simulation, analysis and history is that both ED and PD are required of effective multi-technology coexistence Requiring ED is easy because energy is generic Requiring PD is harder because the different technologies need to agree on the form of a PHY level communication mechanism The existence of billions of 802.11 in 5Ghz band means PD based on 802.11a must be used Back in 1998/99 when there was no legacy base, there was a choice – the form of PD could be negotiated by IEEE 802.11 WG and ETSI BRAN – and it was! In 2016 with billions of 802.11 based devices operating in 5GHz band the only answer is to use a backwards compatible mechanism – based on 802.11a! Discarding PD (as suggested by 3GPP RAN1) not only does not solve the LAA/802.11 problem, it also creates an new 802.11/legacy 802.11 problem The only possible discussion on the form of PD in 2016 might be one on how users of the 5GHz band might transition to a new PD in the future Andrew Myles, Cisco

IEEE 802 should consider a range of “next steps” to explain and promote the need for 802.11 PD detection Options for … Reject the 3GPP RAN1 request to rely on PD at -72bBm With reasons of course Request (again) 3GPP RAN1 to adopt 802.11 based PD detection Again with detailed explanations Suggest to 3GPP RAN1 that LAA at least have options for 802.11 based PD transmission Note that this will help 802.11 detect LAA for improved coexistence … next steps Consider notifying other stakeholders of the IEEE 802 requests and suggestions Regulators: FCC, OFCOM, etc Other SDOs: Wi-Fi Alliance, ETSI BRAN, GSMA, WBA, etc Press: technical press, mass media Consider sponsoring lab tests to demonstrate issues Perhaps working with the Wi-Fi Alliance Andrew Myles, Cisco

IEEE 802 should continue to request that 3GPP RAN1 defines LAA to use 802.11 PD detection The IEEE 802 proposed resolution of comment 3 in 19-16-0037-09 was for LAA to detect 802.11 with similar sensitivity that 802.11 detects 802.11, either by defining the use by LAA of: 802.11 based PD at -82dBm (preferable!) ED at -77dBm or lower An even better solution that maximise communications between the two technologies would be for LAA to also respect 802.11 NAVs These proposals would solve the coexistence problem (consistent with the Guiding Principle) from an 802.11 perspective in that 802.11 would not be adversely affected by LAA Assuming other details of LAA, including LBT, are reasonable It is interesting to note that it is rumoured that at least one implementation of LTE-U does implement 802.11 based PD detection If true, this is a demonstration that such a requirement is not an undue burden Andrew Myles, Cisco

IEEE 802 should suggest that 3GPP RAN1 defines LAA to use 802 IEEE 802 should suggest that 3GPP RAN1 defines LAA to use 802.11 PD transmission too It is equally important to solve the coexistence problem (consistent with the Guiding Principle) from an LAA perspective so that LAA is not adversely affected by 802.11 An easy solution to this problem is for LAA to define the use of 802.11 based protection mechanisms, so that 802.11 devices can help protect LAA devices from 802.11 interference Transmission of 802.11 based PD; and/or Transmission of 802.11 based CTS-to-self Of course, it is the choice of 3GPP RAN1 as to whether they want protection from 802.11 systems … Andrew Myles, Cisco