Working Assumption. For multi-DCI based inter-cell Multi-TRP operation with two TA enhancement, one additional PRACH configuration is supported for each configured additional PCI the additional PRACH configuration is used in a RACH procedure triggered by a PDCCH order for the corresponding configured additional PCI [111] Agreement For multi-DCI based Multi-TRP operation with two TA enhancement, support CFRA triggered by PDCCH order for both intra-cell and inter-cell cases. [111] Agreement For multi-DCI based Multi-TRP operation with two TA enhancement, support the case where a PDCCH order sent by one TRP triggers RACH procedure towards either the same TRP or a different TRP at least for inter-cell Multi-DCI. FFS: for intra-cell Multi-DCI FFS: whether there are any restrictions needed FFS: if cross TRP RACH triggering is an optional feature [111] Conclusion For multi-DCI based Multi-TRP operation with two TA enhancement, there is no consensus to support enhancements for CBRA triggered by PDCCH order.
Working Assumption. For intra-cell multi-DCI based Multi-TRP operation with two TA enhancement, support the case where a PDCCH order sent by TRPX triggers RACH procedure towards either TRPX or TRPY. FFS: details of PRACH power control
Working Assumption. All QCL source RS resource types as defined in TCI state for Rel-16 multi-TRP are supported for scheme 1 Agreement Support semi-static (RRC-based) switching of scheme 1 (PDSCH) with Rel-16 scheme 1a FFS: Whether dynamic switching is additionally supported For future meeting: Companies to consider Proposal #3-8a in FL summary (R1-2104020) for future meetings. Companies to consider Proposal #3-10 in FL summary (R1-2104020) for future meetings. Agreement Scheme 1 for PDSCH is identified by New RRC parameter and the number of TCI states indicated by DCI FFS RRC configuration details, e.g., per BWP or per CC FFS whether or not restriction to a single CDM group for XX-XX is also supported Agreement Confirm the following working assumption from RAN1#104b-e: All QCL source RS resource types as defined in TCI state for Rel-16 multi-TRP are supported for scheme 1.
Working Assumption. At least for rank 1, FD bases used for Wf quantization are limited within a single window with size N configured to the UE whereas FD bases in the window must be consecutive from an orthogonal DFT matrix, i.e. Alt 1 FFS: Further dependence/restriction, e.g. conditioned on N3 or the number of CSI-RS ports, can be applied to above design. If does, how to support a non-consecutive FD bases used for Wf quantization FFS: Whether to introduce thresholds for N3 and/or P Agreement Following working assumption is confirmed (with revision in RED): At least for rank 1 and 2, FD bases used for Wf quantization are limited within a single window with size N configured to the UE whereas FD bases in the window must be consecutive from an orthogonal DFT matrix, i.e. Alt 1. FFS other restrictions, e.g. value(s) of N, if the value of N3 is small FFS other restrictions, e.g. when the number of CSI-RS ports is small Agreement At least for rank 1 and for Mv>1, Minit for the single window with size N is fixed to be 0 Agreement At least for rank 1 and 2 and Mv > 1, for relationship between N and Mv, study and down-select one alternative from following in RAN1#106-e Alt 1: N= Mv always, no UE reporting of Wf Alt 2-1: N >= Mv, Wf is layer-common and reported by UE for N>Mv. Alt 2-2: N >= Mv, Wf is layer-specific and reported by UE for N>Mv. Note: Wf is layer-common for N=Mv Note: For all alternatives, a layer-common window/set of size N is configured. Agreement At least for rank 1/2 and Mv > 1, for relationship between N and Mv, support following alternative Alt 2-1: N >= Mv, Wf is layer-common and reported by UE for N>Mv. For Mv=2, N=2 and one value from {3, 4, 5} RAN1 to select one value from {3, 4, 5} in RAN1#106bis-e FFS: how to report Wf in terms of reporting mechanism and associated bits when Mv=2 and N=one value from {3, 4, 5} Note: Wf is layer-common for N=Mv Note: For all alternatives, a layer-common window/set of size N is configured. Agreement For Rel-17 PS codebook for rank 3/4 and M> 1, Support M=2, which is rank-common When N >= M, Wf is layer-common and reported by UE for N>M Note: Wf is layer-common for N=M Agreement In addition to N=2, N=4 is supported when M=2 for rank 1/2 For rank 3/4, when M=2, N = 2 or 4 is supported and same with the value of N configured for rank 1/2 FFS how to handle N3=3 case Agreement If M=2 and N>M, the non-zero offset between the lower and higher FD indices of Wf is reported by using ceiling(log2(N-1)) bits, assuming that the lower FD in...
Working Assumption. All HARQ-ACK codebook types (Type-1/2/3) are applicable when multi-carrier PDSCH scheduling is configured. Agreement One value for the maximum number of co-scheduled cells by a DCI format 0_X in Rel-18 is selected from {3, 4, 8}. For a UE, the maximum number of co-scheduled cells by a DCI format 0_X can be smaller than or equal to the maximum number supported in Rel-18. Agreement One value for the maximum number of co-scheduled cells by a DCI format 1_X in Rel-18 is selected from {3, 4, 8}. For a UE, the maximum number of co-scheduled cells by a DCI format 1_X can be smaller than or equal to the maximum number supported in Rel-18.
Working Assumption. For a set of cells which is configured for multi-cell scheduling, Existing DCI size budget is maintained on each cell of the set of cells. DCI size of DCI format 0_X/1_X is counted on one cell among the set of cells. FFS which cell DCI size of the DCI format 0_X/1_X is counted on. BD/CCE of DCI format 0_X/1_X is counted on one cell among the set of cells. FFS which cell BD/CCE of the DCI format 0_X/1_X is counted on. Search space of DCI format 0_X/1_X is configured on one cell of the set of cells and associated with the search space of the scheduling cell with the same search space ID. FFS which cell the SS of the DCI format 0_X/1_X is configured on. FFS: How to address Rel-17 BD/CCE limit for any given cell (operating the feature under Rel-17 BD/CCE limit) Note: This does not mean a UE is required to support number of BDs/CCEs beyond the Rel-17 limits (i.e., and ) for PDCCH candidates for each scheduled cell. Agreement UE does not expect to be configured both multi-PDSCH scheduling and multi-cell PDSCH scheduling on the same or different cells within a same PUCCH group.
