3 GPP TSG RAN WG 1 88 b

3 GPP TSG RAN WG 1 #88 b R 1 -170 xxxx Spokane, USA, 3 rd – 7 th April 2017 Agenda Item: 8. 1. 2. 2. 1 WF on Beam Indication for Beam Management Huawei, Hi. Silicon, […]

Background • Agreements in RAN 1#88 on beam reporting – NR supports the following beam reporting considering L groups where L>=1 and each group refers to a Rx beam set (Alt 1) or a UE antenna group (Alt 2) depending on which alternative is adopted. • For each group l, UE reports at least the following information: – Information indicating group at least for some cases » FFS: condition(s) to omit this parameter e. g. when L=1 or Nl=1 • Measurement quantities for Nl beam (s) – Support L 1 RSRP and CSI report (when CSI-RS is for CSI acquisition) » FFS: the details of RSRP/CSI derivation and content » FFS: Other reporting contents, e. g. , RSRQ » FFS: Configurability between L 1 RSRP and CSI report » FFS: whether or not to support differential L 1 RSRP feedback » FFS: How to select Nl beam(s) e. g max Nl beams in terms of received power being above a certain threshold or in terms of correlation less than a certain threshold • Information indicating Nl DL Tx beam(s) when applicable – FFS: the details on this information, e. g. , CSI-RS resource IDs, antenna port index, a combination of antenna port index and a time index, sequence index, beam selection rules for assisting rank selection for MIMO tx, etc. • This group based beam reporting is configurable per UE basis. – This group based beam reporting can be turned off per UE basis e. g. when L=1 or Nl=1 » NOTE: No group identifier is reported when it is turned off – FFS: how L is determined. e. g. by network configuration or UE selection or UE capability e. g. how many beams can be received simultaneously – FFS: how is configured using the CSI framework to support multi-panel or multi-TRP transmission 2

Background • Agreements in RAN 1#88 on beam indication – For reception of unicast DL data channel, support indication of spatial QCL assumption between DL RS antenna port(s) and DMRS antenna port(s) of DL data channel: Information indicating the RS antenna port(s) is indicated via DCI (downlink grants) • The information indicates the RS antenna port(s) which is QCL-ed with DMRS antenna port(s) – FFS: Indication details » E. g. explicit indication of RS port/resource ID, or implicitly derived • FFS when the indication is applied (e. g. , the indication is assumed only for the scheduled PDSCH or until next indication; when the above information is included, if there should be a scheduling/beam switch offset, etc. ) • FFS: Beam indication for receiving fall back unicast PDSCH (if supported) • Note: related signalling is UE-specific – FFS: Beam indication (if needed) for receiving (UE-group) common PDSCH for RRC connected UE – Candidate signalling methods for beam indication for a NR-PDCCH (i. e. configuration method to monitor NRPDCCH) • MAC CE signalling • RRC signalling • DCI signalling • Spec-transparent and/or implicit method • Combination of the above 3

Observation • • • There is a gap to be filled between beam reporting and subsequent beam indication – Likely only a subset of measured beams will be reported and be used for subsequent indication – Directly using reported information for indication would lead to large overhead, especially in DCI – Unclear whether information on UE Rx beam group/set (if reported) should be used for indication Spatial QCL can be used to facilitate control/data channel reception, but may not be appropriate between – Coarse and fine beams – Adjacent fine beams pointing at different directions More discussions can be found in – R 1 -1704229, R 1 -1704724, R 1 -1704877, R 1 -1705505, R 1 -1705891 4

Proposal • NR defines beam pair link (BPL) to represent a beamformed communication link between g. NB and UE – For below 6 GHz, this BPL may not reflect UE-side beamforming – For above 6 GHz, this BPL may include UE-side beamforming – This BPL refers to either g. NB Tx beam (represented by CRI and/or port ID) or UE Rx beam group/set (if reported and depending on which alternative is adopted) – Note: DL and UL BPLs can be different • NR supports using BPL indicator for beam indication for DL beam refinement/tracking – After receiving BPL indicator at the UE • If UE Rx beam groups/sets were reported before, UE knows which UE Rx beam group/set should be used for e. g. , P-2 procedure • If UE Rx beam groups/sets were not reported before, UE knows which g. NB Tx beam will be used, and UE can perform beam refinement around corresponding Rx beam for e. g. , P-3 procedure 5

Appendix • Example mapping between the reported information and bits for beam indication (R 11704229) – Where {100, 101, 110, 111} refers to {BPL#0, BPL#1, BPL#2, BPL#3}, respectively – Only one table is valid depending on whether information on UE Rx beam group/set was reported or not Information on g. NB Tx beams Bits for beam indication Info. on UE Rx beam sets Bits for beam indication CRI and/or port ID [100] Set#0 [100] CRI and/or port ID [101] Set#1 [101] CRI and/or port ID [110] … [110] CRI and/or port ID [111] … [111] 6