Issues for clarification related to “paused COT” in EN

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0063r0 Submission July 2015 Andrew Myles, CiscoSlide 1 Proposal for IEEE 802 submission to 3GPP 14 July 2015 Authors: NameCompanyPhone .
Advertisements

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 /0008r1 Submission Jan 2016 Andrew Myles, CiscoSlide 1 Proposed feedback from IEEE 802 on 3GPP LAA CRs 18 Jan 2015 Authors: NameCompanyPhone .
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
July 2010 doc.: IEEE /0xxxr0 Proposed liaison presentation to SC6 in relation to the identifier conflict issue 9 May 2011 Authors: Andrew Myles,
3GPP RAN1 #90 meeting summary on LAA Enhancements
Summary of WG activities
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
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.
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.
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
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 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
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
Possible liaison motion for IEEE as an IMT-2020 technology
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
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.
Measurement reporting in TGh
IEEE Coexistence SC closing report in Hawaii in Sept 2018
Clarification on Beacon Transmission Rules
IEEE Coexistence SC closing report in Berlin in July 2017
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
3GPP RAN1 status on NR-Unlicensed
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
3GPP LAA Liaison Approval Process
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
IEEE Coexistence SC closing report in Atlanta in May 2019
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.
EN Spectrum Mask Interpretations
Presentation transcript:

Issues for clarification related to “paused COT” in EN 301 893 July 2010 doc.: IEEE 802.11-10/0xxxr0 Issues for clarification related to “paused COT” in EN 301 893 16 October 2017 Authors: Name Company Phone email Matthew Fischer Broadcom matthew.fischer@broadcom.com Andrew Myles Cisco +61 418 656587 amyles@cisco.com Matthew Fischer (Broadcom) et al Andrew Myles, Cisco

EN 301 893 should be clarified so it is clear a device can only make a single attempt to access a “paused COT” Situation? EN 301 893 includes a “paused COT” feature that allows a UE to continue an eNB’s COT after a pause Complication? There is contention in 3GPP RAN1 on the meaning of the rules related to the “paused COT” Answer? The correct interpretation is that a device can only make a single attempt to access a “paused COT” Next steps? EN 301 893 should be clarified so it is clear a device can only make a single attempt to access a “paused COT” Matthew Fischer (Broadcom) et al

EN 301 893 includes a “paused COT” feature that allows a UE to continue an eNB’s COT after a pause EN 301 893 includes an adaptivity clause that specifies an LBT mechanism that is mostly aligned with EDCA in 802.11 One difference is that it allows a “paused COT” (COT = Channel Occupancy Time, like a TxOP) An initiating device obtains a COT in the normal way using LBT mechanism Specified in EN 301 893, clause 4.2.7.3.2.6 The initiating device may authorise a responding device to continue the COT Specified in EN 301 893, clause 4.2.7.3.2.7 & with COT lengths in 4.2.7.3.2.4 The COT continuation can occur immediately, after at most 16us This mode is often used by 802.11 The COT continuation can occur after a pause This feature was put in place to account for a problem that LAA UEs, unlike 802.11 devices, cannot respond immediately to a grant from an eNB The general idea is that the eNB will specify a grant to the UE at a particular time, but the UE must execute a 25µs LBT before taking up the grant If the medium is not free at the grant time then the grant is lost Matthew Fischer (Broadcom) et al

The key elements of the “paused COT” are specified in EN 301 893, clause 4.2.7.3.2.7 Matthew Fischer (Broadcom) et al

The length of COTs that are paused is specified in EN 301 893, clause 4.2.7.3.2.4 Note: Table 8 contains similar rules for Supervised Devices Matthew Fischer (Broadcom) et al

There is contention in 3GPP RAN1 on the meaning of the rules related to the “paused COT” There have been discussions in 3GPP RAN1 about the interpretation of the “paused COT” feature It is reported that some RAN1 participants have plans to allow a UE (in Releases 14 & 15) to make multiple attempts to extend a “paused COT” A eNB issues multiple grants to share a COT to the same UE The UE then attempts to gain access using the 25µs LBT mechanism at each grant time If the UE fails at the first grant time, then it retries at subsequent grant times It is also reported that that other RAN1 participants believe that a UE can only make a single attempt to extend a “paused COT” A eNB issues a single grant to share a COT to a particular UE The UE then attempts to gain access using the 25µs LBT mechanism If the UE fails at the grant time, it then loses the grant and must wait for the eNB to send it another grant Matthew Fischer (Broadcom) et al

The correct interpretation is that a device can only make a single attempt to access a “paused COT” Reasons Reason 1: the text as written is clear that only a responding device can only make a single attempt to access a “paused COT” Reason 2: the multiple attempt interpretation allows access at any time and any number of times, which is not the intent Reason 3: discussion in ETSI BRAN at the time highlighted that only a single grant per device was intended Matthew Fischer (Broadcom) et al

The correct interpretation is that a device can only make a single attempt to access a “paused COT” Reason 1: the text as written is clear that only a responding device can only make a single attempt to access a “paused COT” The text in 4.2.7.3.2.7 is clear in that an initiating device can only send a single grant to a responding device The first paragraph refers to a singular authorisation per responding device The first paragraph equates an authorisation to a grant The text in 4.2.7.3.2.7 is relatively clear in that a responding device can only receive a single grant from an initiating device 1) refers only to a single grant It is possible that this text refers to each example of a grant, but this is unlikely as there is no evidence elsewhere of the possibility of multiple grants to a responding device Matthew Fischer (Broadcom) et al

The correct interpretation is that a device can only make a single attempt to access a “paused COT” Reason 2: the multiple attempt interpretation allows access at any time and any number of times, which is not the intent Suppose the rules in EN 301 893 allowed initiating device to authorise a responding device to retry attempts to access a “paused COT” by sending multiple grants Now suppose those multiple grants were for access every 1ns While this is not possible for LAA for other reasons, EN 301 893 is written to be technology neutral and so what LAA can do is not relevant This would mean that the responding device could have access to the medium at any time it could find the medium free for 25µs “any time” is constrained by other rules in 4.2.7.3.2.4 related to “paused COTs” It is clearly not the intent of the text in EN 301 893 to provide access to the medium at any time Matthew Fischer (Broadcom) et al

The correct interpretation is that a device can only make a single attempt to access a “paused COT” Reason 3: discussion in ETSI BRAN at the time highlighted that only a single grant per device was intended The inclusion of the “paused COT” was agreed in ETSI BRAN in December 2015 It was suggested as a result a complaint by a LAA stakeholder that a UE could not share an eNB’s COT because LTE’s design meant the UE could not respond immediately to a grant During discussion of the “paused COT” it was made very clear that if the medium was not free at the grant time, the single grant was lost A Wi-Fi stakeholder explained multiple times that the UE would only have one opportunity at the grant time; he also asserted the LAA stakeholders were “nuts” (direct quote) for proposing a solution that did not appear to be helpful to LAA The LAA stakeholders all acknowledged the situation and stated the feature was useful and acceptable to LAA Matthew Fischer (Broadcom) et al

EN 301 893 should be clarified so it is clear a device can only make a single attempt to access a “paused COT” An interpretation of EN 301 893 to allow multiple grants per device to access a “paused COT” risks fair sharing As a starting point, ETSI BRAN should be asked to make it clear only a single grant per device is allowed Matthew Fischer (Broadcom) et al