3 GPP TSG RAN WG 1 NR AdHoc

  • Slides: 4
Download presentation
3 GPP TSG RAN WG 1 NR Ad-Hoc Meeting Qingdao, China, June 27 -30,

3 GPP TSG RAN WG 1 NR Ad-Hoc Meeting Qingdao, China, June 27 -30, 2017 R 1 -1711846 Agenda item: 5. 1. 3. 4. 1. 1 Way Forward on NR Carrier Aggregation Huawei, Hi. Silicon, KT, CATR, Media. Tek, [Intel], [Ericsson], [Samsung], [CATT], [Sony]…

Background Agreements on Carrier Aggregation during RAN 1 #89: • Support cross-carrier scheduling for

Background Agreements on Carrier Aggregation during RAN 1 #89: • Support cross-carrier scheduling for aggregated carriers with the same and different numerology. – FFS: the timing relationship between DCI and the corresponding PDSCH/PUSCH – FFS: impact on the maximum number of HARQ processes – FFS: potential restrictions (e. g. , on combination of different numerology) • Support joint UCI feedback for aggregated carriers with the same or different numerology. – FFS: the timing relationship between PDSCH and the corresponding HARQ-ACK – FFS: impact on maximum number of HARQ process – FFS: potential restrictions (e. g. , on combination of different numerology) • Support one PUCCH in one cell group for NR DC/CA – FFS: The carrier for PUCCH transmission can be configured within one cell group – FFS: potential restrictions (e. g. , on combination of different numerology, on combination of different frequency bands)

Proposal (1/2) • • A component carrier is defined as being either DL or

Proposal (1/2) • • A component carrier is defined as being either DL or UL NR support Primary Component Carrier (PCC) and Secondary Component Carrier (SCC) – A UE monitors PDCCH candidates in the common search space and UE specific search space(s) on PCC – A UE at least monitor UE specific search space(s) on SCC Support cross carrier scheduling with CIF – A carrier is scheduled by one and only one carrier – FFS: the number of CIF bits For scheduling with different and same numerologies – For self-scheduling • PDCCH and the scheduled PDSCH have the same numerologies • PDCCH and the scheduled PUSCH can have the same or different numerologies – The time granularity indicated in the DCI for the timing relationship between DCI and the corresponding PUSCH follows the numerology of the PUSCH transmission – For cross-carrier scheduling • PDCCH and the scheduled PDSCH/PUSCH can have different or the same numerologies – The time granularity indicated in the DCI for the timing relationship between DCI and the corresponding PDSCH/PUSCH follows the numerology of the PDSCH/PUSCH transmission – The UE processing time for cross-numerology scheduling should not be more stringent than that for the same numerology scheduling

Proposal (2/2) • • • NR Support multiple PUCCH groups – The carrier for

Proposal (2/2) • • • NR Support multiple PUCCH groups – The carrier for PUCCH transmission can be configured within one PUCCH group For joint UCI feedback with the same and different numerology – The time granularity indicated in the DCI for PDSCH and the corresponding HARQ-ACK follows the numerology for HARQ-ACK transmission – The UE processing time for cross-numerology scheduling should not be more stringent than that for the same numerology feedback NR support multiple timing advance groups including Primary Timing Advance Group and Secondary Timing Advance Group(s) – Support PRACH transmission for timing advance acquisition on SCC