3GPP RAN1 status on NR-Unlicensed

Slides:



Advertisements
Similar presentations
Doc.: g Draft ETSI ERM TG28 Liaison response on EN March 2010 Larry Taylor, DTCSlide 1 Project: IEEE P Working Group for.
Advertisements

Discussion of LAA LBT Categories
3GPP TSG RAN WG1 # R1-15xxxx Fukuoka, Japan 25th – 29th May 2015
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.
WF on MCOT and CWS for LBT priority classes
WF on Regulation and MCOT
WF on LAA DL Multi-Channel LBT
Doc.: IEEE /0024r0 Submission Feedback on 3GPP CRs: LAA Multi-Channel Access and Energy Detect (ED) Coexistence Slide 1 Date: Authors:
WF on MCOT limit Signaling and Modifying LBT type Ericsson, … 3GPP TSG RAN WG1 #85 R1-16xxxx Nanjing, China 23 rd – 27 th May 2016 Agenda item:
Overview of open issues in
Offline discussion on remaining details on RRM measurements
A proposed response to 3GGP on fourteen coexistence issues
WF on RA-RNTI design 3GPP TSG RAN WG1 Meeting NR#3 R1-171xxxx
Month Year doc: IEEE /xxxxr0
Offline Discussion on remaining details about RACH Procedure
Comments on LAA EVM Date: Authors: January 2015 Month Year
Summary of proposals on CBG-based retransmission
3GPP RAN1 #90 meeting summary on LAA Enhancements
WF on Beam Indication for Beam Management
A proposed response to 3GGP on fourteen coexistence issues
Way Forward on Alt. 2 vs. Alt
Samsung, KT Corp., NTT DOCOMO, Verizon, [ZTE], [CATT], [Intel]
WF on UE mandatory channel bandwidth for NR bands
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.
Proposed response to 3GPP ED request
3GPP RAN1 status on NR-Unlicensed
3GPP RAN1 status on LAA and NR-Unlicensed
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 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 A discussion of LS from 3GPP RAN1/RAN4 in May 2017 in response to IEEE 802 LS in March July 2017 Authors:
3GPP RAN1 status on NR-Unlicensed
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.
3GPP RAN1 and RAN4 status on NR-Unlicensed and LAA
3GPP RAN1, RAN2 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 Coexistence SC closing report in San Diego in July 2018
WF on LTE-NR Coexistence
Summary of workshop on NR unlicensed
IEEE PDED ad hoc closing report in Vancouver in Mar 2017
Random Access RU Allocation in the Trigger Frame
IEEE Coexistence SC closing report in Warsaw in May 2018
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
3GPP RAN1 and RAN4 status on NR-Unlicensed and LAA
Comments on LAA EVM Date: Authors: January 2015 Month Year
3GPP RAN1 status on NR-Unlicensed
IEEE Coexistence SC closing report in Hawaii in Sept 2018
3GPP RAN1 status on NR-Unlicensed
IEEE Coexistence SC closing report in Atlanta in May 2019
Comments on LAA EVM Date: Authors: January 2015 Month Year
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
Jing Sun, Qualcomm Incorporated Rapporteur of Rel.16 NR-U Work Item
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.
LBT for Short Control Messages
On standalone transmissions with short fixed LBT
Performance Evaluation of Channel Access Mechanisms in 6 GHz Spectrum
EN Spectrum Mask Interpretations
Presentation transcript:

3GPP RAN1 status on NR-Unlicensed Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 3GPP RAN1 status on NR-Unlicensed Date: 2019-05-16 Authors: Name Affiliations Address Phone email Sindhu Verma Broadcom sindhu.verma@broadcom.com Shubhodeep Adhikari shubhodeep.adhikari@broadcom.com John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Abstract This presentation provides updates from the latest 3GPP RAN1 meetings (RAN1#96b and RAN1#97) on the standardization of NR-Unlicensed, with a focus on fair coexistence with 802.11. John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Outline The presentation discusses status of the following topics: Reply to LS from IEEE 802.11 on the use of no/short LBT LBT for transmission of DL control messages LBT for UCI-only PUSCH transmissions LBT for DL transmissions containing only UL grants LBT for a 16us gap after a DL transmission and before a UL transmission in a gNB-acquired COT Supported sub-slot PDSCH durations CW adaptation mechanisms Multi-carrier channel access schemes Common preamble between NR-U and Wi-Fi in 5 GHz and 6 GHz. John Doe, Some Company

Reply to LS from IEEE 802.11 on the use of no/short LBT Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Reply to LS from IEEE 802.11 on the use of no/short LBT The LS from IEEE 802.11 to 3GPP RAN1 had raised concerns on NR-U employing the following: Transmission of DRS by the gNB up to 5% of the time when the total duration of such transmissions is up to 1 ms Transmissions by UEs for Random Access, HARQ-ACK, Scheduling Request, Channel State Information, etc. The response contained in R1-1905860 says the following (the original proposal supported by many companies had omitted the highlighted details which now can be used as the topic for further LS exchanges): NR-U uses short LBT to transmit DRS alone or multiplexed with non-unicast data (e.g. OSI, paging, RAR) if the DRS length is up to 1ms and the DRS is transmitted no more than 5% of the time. NR-U DRS may have different signals/channels than LAA DRS. Other proposals to use short LBT for transmissions other than the types of DRS transmissions mentioned above were not approved by RAN1, although it is expected that transmission with short LBT might be allowed for some NR-U carriers in a similar way that it is allowed for LTE-LAA with type B channel access procedure for transmissions on multiple carriers. Regarding the request for 3GPP RAN1 to consider supporting the proposal in ETSI BRAN to ban the use of no LBT and restrict the use of short LBT (to about 1%), the RAN1 view is that the clause 4.2.7.3.3 in EN 301 893 is used by LTE- LAA, even though a short LBT is additionally applied. There is no consensus on supporting the proposal to ban the use of no LBT and restrict the use of short LBT (to about 1%). John Doe, Some Company

LBT for transmission of DL control messages Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 LBT for transmission of DL control messages Agreed: DRS alone or multiplexed with non-unicast data (e.g. OSI, paging, RAR) When the DRS duty cycle ≤1/20, and the total duration is up to 1 ms: 25 µs Cat 2 LBT is used (as in LAA) The maximum DRS transmission window duration is 5 ms. The maximum number of candidate SSB positions within a DRS transmission window, Y, is selected as Y = 10 for 15 kHz SCS and Y = 20 for 30 kHz SCS. The number of starting points for DRS transmissions with the 5 ms window that can use a Cat. 2 LBT is to be discussed further as part of channel access discussions. When DRS duty cycle is > 1/20, or total duration > 1 ms: Cat4 with any channel access priority class value can be used DRS multiplexed with unicast data Channel access priority class is selected according to the multiplexed data John Doe, Some Company

LBT for UCI-only PUSCH transmissions Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 LBT for UCI-only PUSCH transmissions Agreed: For a UCI-only transmission on PUSCH in a channel occupancy initiated by the UE, Cat4 with lowest channel access priority class value can be used by the UE John Doe, Some Company

LBT for DL transmissions containing only UL grants Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 LBT for DL transmissions containing only UL grants Proposed by Ericsson (R1-1907454): When a gNB transmission includes only control signals/channels/information without any user plane data, the priority class value for accessing the channel is up to gNB. The proposal affects the channel access mechanism indirectly used by the UEs which will share the COT initiated by the gNB while sending the grants. It is based on an incorrect statement “In LAA, the choice of LBT priority class for grant-only transmissions, i.e. PDCCH only, is up to eNB” noted in the above contribution. In LAA, it has been ensured that for grant-only transmissions, the priority class is based on the data that is expected to be transmitted. The only agreement was “UL grant only transmission by eNB based on Rel-13 Cat-4 LBT priority class is supported” which is valid along with another agreement: “When the UE performs 25 microsecond LBT on an LAA SCell, There is no additional restriction at the UE (other than the multiplexing rules defined in RAN2) on the type of the traffic that can be carried in the scheduled subframes. eNB shall not schedule the UE more subframes than the minimum necessary to transmit all the traffic corresponding to the same LBT priority class or lower (i.e., with a lower number in the LBT priority class table) than the LBT priority class used by the eNB based on the DL traffic and the latest BSR and received UL traffic from the UE. The eNB is responsible for making sure that the mapping between QCI and LBT priority class is consistent with section 5.7.1 in TS 36.300. The eNB is expected to take the QCI with the lowest priority in the logical channel group into account when defining the LBT priority class for a logical channel group” Broadcom proposes the same mechanism as in LAA for grant-only transmissions. John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 LBT for a 16us gap after a DL transmission and before a UL transmission in a gNB-initiated COT Agreed: For LBT by a UE prior to transmission of a UL burst within a gNB-initiated channel occupancy as an LBE device, for gap durations shorter than 25 microseconds, Cat 2 LBT can be indicated (FFS: explicit and/or implicit) to the UE if the gap is 16 microseconds (allowing for implementation tolerances) Select one of the following alternatives for Cat2 LBT in a 16 us gap. Alt 1: The 16us measurement period is split into two slots with the first slot having a duration 7us and second slot having a duration of 9us. Energy measurement is done in the 9us slot with the measurement including averaging for at least 4 us in any portion of the slot. LBT is said to be successful if the measured energy is lower than the ED threshold. Alt 2: The 16us measurement period is split into two slots with the first slot having a duration 7us and second slot having a duration of 9us. Energy measurement is done in both the 7us and 9us slot with the measurement including averaging for at least 4 us in any portion of each slot. LBT is said to be successful if the measured energy is lower than the ED threshold in both slots. Alt 3: Energy measurement is done in any portion of the 16 us duration including averaging for at least 4 us. LBT is said to be successful if the measured energy is lower than the ED threshold. Alt 2 is Broadcom's proposal and it aligns most closely in performance to what is done in 11ax John Doe, Some Company

Supported sub-slot PDSCH durations Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Supported sub-slot PDSCH durations Agreed: Durations from 2 to 13 symbols are supported Capability signaling will be defined for UEs to indicate which specific subset of durations are supported by the UE This helps to significantly reduce transmission of reservation signals by NR-U. John Doe, Some Company

CW adaptation mechanisms Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 CW adaptation mechanisms Proposal that has been developed in an offline of the ongoing RAN1#97 meeting The following alternatives have been identified for a definition of reference slot for CWS adjustment Alt 1: reference slot for CWS update for PDSCH/PUSCH is defined as the n first slots of the most recent transmission on the LBT subband made by gNB or UE, for which at least some HARQ-ACK feedback is expected to be available FFS: value of n Alt 2: reference slot for CWS update for PDSCH/PUSCH is defined as the n first slots of the most recent transmission on the LBT subband made by gNB or UE Alt 2 is Broadcom proposal to align the behavior with the ETSI BRAN regulations John Doe, Some Company

Multi-carrier channel access schemes Month Year doc.: IEEE 802.11-yy/xxxxr0 May 2019 Multi-carrier channel access schemes Agreed: Multi-carrier channel access schemes that are applicable to multiple carriers with a single LBT sub-band per carrier that is the same as the carrier bandwidth are also applicable to multiple LBT sub-bands within a carrier when such carriers are used either as a single wideband carrier or as part of carrier aggregation of a set of carriers. John Doe, Some Company

Common preamble between NR-U and Wi-Fi May 2019 Common preamble between NR-U and Wi-Fi         Both RAN1 WG and TSG-RAN have extensively discussed coexistence aspects, but did not find consensus for adopting a preamble for NR-U. As a consequence, and in accordance with the workplan outlined in the NR-U Work Item //add link//, RAN1 WG will not address proposals any further on adopting a preamble for NR-U. -        Nevertheless, TSG-RAN is open for further discussions on a common preamble for 6GHz at its next meeting (3-6 June), and will check whether member company views have shifted towards a consensus.