WF on Beam failure recovery

Slides:



Advertisements
Similar presentations
Way forward for LTE DL 4Rx AP SI on RF
Advertisements

WF on design of physical downlink control channel for MTC CATT, Alcatel Lucent, Alcatel Lucent Shanghai Bell, Ericsson, ETRI, InterDigital, MediaTek, NTT.
WF on PBCH Coverage Enhancement
Way forward on eIMTA signaling to support up to 32 component carriers
WF on DL LBT Scheme for DRS
3GPP TSG RAN WG1 # R1-15xxxx Fukuoka, Japan 25th – 29th May 2015
WF on MCOT and CWS for LBT priority classes
WF on LAA DL Multi-Channel LBT
Proposal for NB-IoT single-tone only UE
WF on UE capability signaling for FD-MIMO Class B LG Electronics, Intel Coorporation, NTT DOCOMO, Qualcomm 3GPP TSG RAN WG1 Meeting #84 R St Julian’s,
Clarification of the scope of the study on latency reduction techniques for LTE 3GPP TSG RAN Meeting #71RP-16xxxx Göteborg, Sweden, March , 2016.
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:
WF on Supporting different Numerologies in a NR carrier LG Electronics, [Huawei, HiSilicon, Panasonic], 3GPP TSG RAN WG1 Meeting #85R Nanjing,
Overview of open issues in
Offline discussion on remaining details on RRM measurements
WF on Bandwidth Part for DL common channel
WF on RA-RNTI design 3GPP TSG RAN WG1 Meeting NR#3 R1-171xxxx
3GPP TSG-RAN WG4 Meeting NR#3 Nagoya, Japan, 18 – 21 Sep, 2017
Summary on Beam Recovery Mechanism
Summary of SLS for RRM NTT DOCOMO
Offline Discussion on remaining details about RACH Procedure
Draft WF on single Tx switched UL
Single Tx switched UL DRAFT 3GPP RAN #77 September , 2017
R GPP TSG RAN WG1 Meeting #90 Prague, P.R. Czechia, 21st – 25th August 2017 Agenda: WF.
WF on new NR CG sequences for PUCCH
Initial workplan on NR spectrum
QCL configurations in above 6GHz and the necessary RS QCL linkeages
WF on pre-DFT PT-RS pattern for DFTsOFDM
Summary of proposals on CBG-based retransmission
Proposals on remaining issues on PDCCH structure
RACH configuration ZTE, Sanechips R1-171xxxx
Proposals on remaining issues on search space
WF on Beam Indication for Beam Management
WF on measurement capability and measurement gap for NR
Way forward on UE EIS Spherical Coverage and Beam Correspondence
3GPP TSG RAN WG1 Meeting #90bis
TSG-RAN Workshop on Radio mobility MOB
Summary on Beam Recovery Mechanism
R : SRS Enhancements for LTE-A
WF on remaining open items for allowing 1Tx transmission in LTE-NR DC
Illustration of RMSI monitoring windows (TDM)
WF on SS Block Index Reporting through RACH Procedure
Way forward on cell identification in NR
Discussion on TB-ack/CBG-Nack for initial transmissions
WF on transmit diversity for DFTsOFDM
Samsung, KT Corp., NTT DOCOMO, Verizon, [ZTE], [CATT], [Intel]
WF on beam reporting CATT, Intel R1-17xxxxx
WF on Beam-Related Indication
WF on CSI timing offset for PUSCH
LTE-A Relays and Repeaters
Shanghai, China, April 11-15, 2011 Source: Qualcomm Incorporated
WF on Radio Link Monitoring in NR
Vodafone, Agilent, Anite, Azimuth, Bluetest, [Intel], ETS-Lindgren
Motorola Mobility, Lenovo, …
WF on UE mandatory channel bandwidth for NR bands
Motivation for WI on "LTE-based V2X Services"
WF on LTE-NR DC with UL coexistence
Summary on CA Aspects Samsung 3GPP TSG RAN WG1#91
WF on 4Tx UL Codebook For CP-OFDM
Summary of Offline Discussion on RMSI CORESET Configuration (Part 2)
WF on UL Beam Management
WF on UL Beam Management
Summary on CA Aspects Samsung 3GPP TSG RAN WG1#91
WF on CB-group based retransmission
WF on Phase discontinuity issue in intra-band EN-DC with 1-PA
WF on LTE-NR Coexistence
3GPP RAN1 status on NR-Unlicensed
Status of NR-U - Wi-Fi coexistence
Jing Sun, Qualcomm Incorporated Rapporteur of Rel.16 NR-U Work Item
Presentation transcript:

WF on Beam failure recovery 3GPP TSG-RAN WG1 Meeting #89 R1-170XXXX Hangzhou, China 15 - 19 May 2017 Agenda item: 7.1.2.2.2 Document for decision WF on Beam failure recovery Huawei, HiSilicon, …

Background Agreements: UE Beam failure recovery mechanism includes the following aspects Beam failure detection New candidate beam identification Beam failure recovery request transmission UE monitors gNB response for beam failure recovery request UE monitors beam failure detection RS to assess if a beam failure trigger condition has been met Beam failure detection RS at least includes periodic CSI-RS for beam management SS-block within the serving cell can be considered, if SS-block is also used in beam management as well FFS: Trigger condition for declaring beam failure UE monitors beam identification RS to find a new candidate beam Beam identification RS includes Periodic CSI-RS for beam management, if it is configured by NW Periodic CSI-RS and SS-blocks within the serving cell, if SS-block is also used in beam management as well Information carried by beam failure recovery request includes at least one followings Explicit/implicit information about identifying UE and new gNB TX beam information Explicit/implicit information about identifying UE and whether or not new candidate beam exists FFS: Information indicating UE beam failure Additional information, e.g., new beam quality Down-selection between the following options for beam failure recovery request transmission PRACH PUCCH PRACH-like (e.g.,different parameter for preamble sequence from PRACH) Beam failure recovery request resource/signal may be additionally used for scheduling request UE monitors a control channel search space to receive gNB response for beam failure recovery request FFS: the control channel search space can be same or different from the current control channel search space associated with serving BPLs FFS: UE further reaction if gNB does not receive beam failure recovery request transmission

Proposals Beam failure recovery should include DL beam failure only and both DL and UL beam failure scenarios. Beam failure request should support both of the two types of contents Information about identifying UE ,new gNB TX beam information and its beam quality Information about identifying UE and whether or not new candidate beam exists The following UL channels for reporting beam failure report should be supported Dedicated channel with shared resource with RACH using orthogonal sequence and/or orthogonal time/frequency resource with RACH Periodic UL control channel for reporting beam failure, e.g. NR-PUCCH The spatial QCL assumption of the search space of beam failure recovery response should be associated with The recommended beam if the recommended beam carried on beam failure request. The preconfigured beam set if there is no recommended beam carried on beam failure request