July 2010 doc.: IEEE 802.11-10/0xxxr0 A proposal for enabling the use of IEEE 802.11ax-stye Spatial Reuse under EN 301 893 2 November 2017 Authors: Name.

Slides:



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

Doc.: IEEE /0063r0 Submission July 2015 Andrew Myles, CiscoSlide 1 Proposal for IEEE 802 submission to 3GPP 14 July 2015 Authors: NameCompanyPhone .
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:
Doc.: IEEE /163r0 Submission Jan 2016 Andrew Myles, CiscoSlide 1 What is the status of the ETSI BRAN work on a revised version of EN ?
A proposed response to 3GGP on fourteen coexistence issues
Summary of WG activities
A proposed response to 3GGP on fourteen coexistence issues
Proposal for ETSI BRAN to restrict blocking energy
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.
July 2010 doc.: IEEE /0xxxr0 Agenda for IEEE Coexistence SC meeting in Orlando in November November 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.
July 2010 doc.: IEEE /0xxxr0 Agenda for IEEE Coexistence SC meeting in Orlando in November October 2017 Authors: Name Company Phone.
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.
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
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6
July 2010 doc.: IEEE /0xxxr0 Agenda for IEEE Coexistence SC meeting in Orlando in November November 2017 Authors: Name Company Phone.
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
July 2010 doc.: IEEE /0xxxr0 Preliminary agenda for IEEE Coexistence SC meeting in Hawaii in August August 2017 Authors: Name Company.
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?
IEEE Coexistence SC closing report in Bangkok in Nov 2018
A discussion of ED & PD for & LAA in unlicensed spectrum
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
IEEE 802 Process for Interactions with ISO/IEC JTC 1/SC 6 & 7
3GPP RAN1 and RAN4 status on NR-Unlicensed and LAA
IEEE Coexistence SC closing report in St Louis in Jan 2019
3GPP RAN1 status on NR-Unlicensed
IEEE Coexistence SC closing report in Irvine in January 2018
IEEE Coexistence SC closing report in Vancouver in Mar 2019
PDED Ad Hoc closing report in San Antonio in November 2016
IEEE GPP 6 GHz Coexistence Workshop Preparation
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
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
IEEE Coexistence SC closing report in Atlanta in May 2019
IEEE PDED ad hoc closing report in Atlanta in Jan 2017
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.
Status of NR-U - Wi-Fi coexistence
Functional Requirements for EHT Specification Framework
Coexistence in 6 GHz License-exempt Spectrum
IEEE Coexistence SC closing report in Atlanta in May 2019
LAA / Wi-Fi Coexistence evaluations with commercial hardware
Some contributions to ETSI BRAN
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.
July 2010 doc.: IEEE /0xxxr0 Agenda for IEEE Coexistence SC meeting in Hanoi in September August 2019 Authors: Name Company Phone.
Presentation transcript:

July 2010 doc.: IEEE 802.11-10/0xxxr0 A proposal for enabling the use of IEEE 802.11ax-stye Spatial Reuse under EN 301 893 2 November 2017 Authors: Name Company Phone email Andrew Myles Cisco +61 418 656587 amyles@cisco.com Andrew Myles, Cisco Andrew Myles, Cisco

EN 301 893 can be refined to allow 802 EN 301 893 can be refined to allow 802.11ax-style SR with dual threshold Situation EN 301 893 is an ETSI BRAN standard that provides a means of conforming to the R-ED requirements Spatial reuse is a concept that well aligned with the efficient use goals of the RE-D Problem EN 301 893 will need to be revised to enable 802.11ax-style SR The challenge is to revise EN 301 893 in a way that balances 802.11ax-style SR against other goals Assumption Answer One solution is for EN 301 893 to allow the potential “victim” of SR to decide if the medium is occupied A second variation is for a device to allow simultaneous transmissions within its own MCOT The proposed SR rules enable innovation, maintain technology neutrality & minimise complexity ETSI BRAN agrees to 802.11 WG’s request to enable dual threshold for 802.11ax Andrew Myles, Cisco

EN 301 893 is an ETSI BRAN standard that provides a means of conforming to the R-ED requirements EN 301 898 is a Harmonised Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU Directive 2014/53/EU is also known as RE-D Article 3.2 of the RE-D encourages effective & efficient use of the spectrum and the avoidance of harmful interference Radio equipment shall be so constructed that it both effectively uses and supports the efficient use of radio spectrum in order to avoid harmful interference EN 301 893 has been developed & revised by ETSI BRAN over many years to allow one voluntary means of conforming to the essential requirements The current version of EN 301 893 is v2.1.1 and was ratified in May 2017 ETSI BRAN have just adopted a WI to revise EN 301 893 again, with the adaptivity clauses representing one significant focus Andrew Myles, Cisco

EN 301 893 defines two threshold methods to support the effective use goals of RE-D The adaptivity clauses in EN 301 893 v2.1.1 were mainly designed to encourage fair sharing of the 5GHz band by all technologies Fair sharing promotes effective use of spectrum The sharing mechanism specified by the adaptivity clause is based on an LBT mechanism derived from 802.11 EDCA, using two threshold methods to determine whether the medium is “busy” Energy Detection threshold of -72 dBm (the threshold actually varies depending on tx power); OR Energy Detection threshold of -62 dBm, as long as the system is conformant with IEEE 802.11-2016 (including its Preamble Detection threshold of -82 dBm) The first method was included mainly for use by LTE based technologies, while the second method was included mainly for use by 802.11a/n/ac The current version of EN 301 893 specifies the first method must be used for any systems not conformant with IEEE 802.11-2016 Therefore, 802.11ax systems must currently use the first method Andrew Myles, Cisco

It is hoped the two threshold methods will enable fair sharing between 802.11 & LTE technologies The two threshold methods driving LBT in EN 301 893 represent a compromise hammered out in ETSI BRAN during 2015-16 by stakeholders from the Wi-Fi & LAA communities The two threshold methods may enable “fair” sharing between 802.11a/n/ac & LAA in at least some environments 3GPP simulations show “fair” sharing between LAA & 802.11ac in a number of specific scenarios, although the simulations have known flaws that have been noted by IEEE 802 in multiple LS’s to 3GPP RAN1 It is likely both threshold methods, or refinements, will become the basis for some level of “fair” sharing between all technologies There are no proposals to fundamentally change EN 301 893’s LBT mechanism 802.11 WG has proposed that EN 301 893 be refined to allow any technology (incl 802.11ax) to use the second method (denoted the dual threshold method) Few 802.11ax/LTE technology coexistence simulations have been published but it is hoped the two threshold methods will enable some level of “fair” sharing Andrew Myles, Cisco

Spatial reuse is a concept that well aligned with the efficient use goals of the RE-D IEEE 802.11ax will include two spatial reuse (SR) mechanisms to enable some simultaneous transmissions by 802.11 in dense deployments OBSS_PD-based spatial reuse SRP-based spatial reuse SR, such as that proposed for 802.11ax, when designed and implemented well, should enable more efficient use of limited spectrum resources As such, SR is well aligned with R-ED Article 3.2, which encourages efficient use of spectrum Andrew Myles, Cisco

Assumption: ETSI BRAN agrees to 802 Assumption: ETSI BRAN agrees to 802.11 WG’s request to enable dual threshold for 802.11ax IEEE 802.11 WG has requested ETSI BRAN to refine EN 301 893 to allow 802.11ax to use a dual threshold option similar to that specified in IEEE 802.11-2016 This proposal to enable 802.11ax-style SR is based on an assumption that that ETSI BRAN agrees to this request If ETSI BRAN do not agree to the request (thus forcing 802.11ax to use the single threshold option of ED = -72 dBm or less) then SR is enabled for ED less than -72 dBm 802.11ax may have less access to the medium than both 802.11ac and LAA in certain circumstances Andrew Myles, Cisco

EN 301 893 will need to be revised to enable 802.11ax-style SR The current version of EN 301 893 was specified with a bias towards ensuring fairness between systems (effective use) rather than efficiency Fairness between 802.11ac & LAA was the focus over the last two years SR was not considered in developing the current version of EN 301 893 However, the dual threshold mechanism will need some refinement to enable the use of 802.11ax-style SR Essentially, an exception to the PD = -82 dBm threshold is required to enable 802.11ax-style SR The challenge is to revise EN 301 893 in a way that balances 802.11ax-style SR against other goals Andrew Myles, Cisco

The challenge is to revise EN 301 893 in a way that balances 802 The challenge is to revise EN 301 893 in a way that balances 802.11ax-style SR against other goals Maintain fairness Enable innovation Develop rules for SR in EN 301 893 that maintains fair access for all technologies, similar to current version of EN 301 893 Minimise restrictive rules for SR in EN 301 893, thus enabling future innovation without needing to revise EN 301 893 again Goals for revising EN 301 893 to allow 802.11ax-style SR Limit complexity Support technology neutrality Refine EN 301 893 to allow SR in a way that focuses on general principles rather than relying on detailed & complex rules Rather than specifying technology-specific rules in EN 301 893, specify rules than can apply to any technology Andrew Myles, Cisco

One solution is for EN 301 893 to allow the potential “victim” of SR to decide if the medium is occupied One possible concept to enable SR in the context of EN 301 893 (and achieve the other goals on the previous page) is: A device may consider the medium to be not occupied if it has a reasonable basis to believe the current transmitter would consent to the device transmitting simultaneously One obvious reasonable basis would be if the device followed rules for SR that had been adopted by the transmitting device For example, if the device determined that the transmitting device was an 802.11 device (possibly by decoding the preamble and/or MAC header) then one could reasonably argue that simultaneous transmission was allowed in circumstances defined by the SR rules in 802.11ax There is no reason an LTE based systems could also not use this mechanism too Using this mechanism would probably require decoding preambles & possibly MAC headers Andrew Myles, Cisco

The proposed new rule in EN 301 893 increases the possibility of simultaneous transmissions The proposed new rule for enabling SR allows the medium to be considered not occupied if the transmitting device consents to simultaneous transmissions A device assuming the medium to be not occupied will allow the LBT mechanism to continue counting down and the device to transmit earlier than normal While this rule will enable simultaneous transmissions in many cases, it will not necessarily do so, depending on the state of the LBT countdown However, it is important to allow the LBT mechanism to continue operating as normal to avoid collisions between multiple other independent devices (a common situation in unlicensed spectrum) Andrew Myles, Cisco

A second variation is for a device to allow simultaneous transmissions within its own MCOT Discussions related to 3GPP NR-Unlicensed at a recent workshop suggest that these systems will often be coordinated & synchronised Therefore, these NR systems will not always need LBT to coordinate access and avoid collisions This observation suggests a second option should be introduced in EN 301 893 that allows immediate simultaneous transmission in some circumstances A device may transmit during an MCOT of the current transmitter if it has a reasonable basis to believe the current transmitter would consent to simultaneous transmissions While this proposed option was inspired by NR discussions, there is no reason future versions of 802.11 could not take advantage of this option too Andrew Myles, Cisco

The proposed SR rules enable innovation, maintain technology neutrality & minimise complexity The proposal is that EN 301 893 be modified to incorporate two rules to enable spatial reuse A device may consider the medium to be not occupied if it has a reasonable basis to believe the current transmitter would consent to simultaneous transmissions A device may transmit during an MCOT of the current transmitter if it has a reasonable basis to believe the current transmitter would consent to simultaneous transmissions These rules are conceptual; the actual text in EN 301 893 will depend on other refinements to EN 301 893 However, the proposed rules are sufficiently high level that they enable behaviour that supports the efficiency goals of EN 301 893 … … while also enabling future innovation in various standards, maintaining technology neutrality and minimising EN 301 893 complexity Andrew Myles, Cisco

The IEEE 802.11 Coexistence SC will discuss this proposed solution Questions Does 802.11 WG still want to promote the use of dual thresholds for 802.11ax? At least some would be happy for 802.11ax to use ED = -72 dBm at all times with no PD restrictions; this would resolve the SR issue but potentially cause fairness issues with 802.11ac and/or LAA Do we want to allow 802.11ax-style SR in a system that uses dual thresholds? Maybe it is sufficient to enable SR only in an environment that relies on ED = -72 dBm Assuming we want SR with traditional dual thresholds: Are these proposed rules good enough to enable 802.11ax-style SR? Do these proposed rules have any unintended consequences? … Andrew Myles, Cisco