3GPP TSG RAN WG1 Meeting #100bis-e	R1-20xxxxx

E-meeting, April 20-30, 2020

Agenda Item:	7.2.5.1

Source:	Moderator (Huawei)

Title:	Text proposal on PDCCH overbooking/dropping for TS 38.213 Section 10.1

Document for:	Discussion and decision

1	Introduction

In RAN1#100b-e meeting, under email discussion [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03], the following proposals were agreed:

Agreements:

Option 2 (revised): PDCCH overbooking/dropping is only performed in at most 1 span within a slot.

If the number of spans within a slot is larger than 1, then PDCCH overbooking/dropping is performed in the first span

Agreements:

If the number of non-overlapping CCE for channel estimation of the configured PDCCH candidates to monitor in some monitoring span j exceeds the CCE limit per monitoring span of the span j, UE can skip monitoring all PDCCH candidates in the search space sets with highest search space set indices in span j until the number of non-overlapping CCE of remaining PDCCH candidates to monitor in the monitoring span j does not exceed the CCE limit per monitoring span for span j, i.e. no partial dropping in any search space set.

The document provides the corresponding Text proposal to reflect the above agreements for TS 38.213 v16.1.0 section 10.1. It was concluded to endorse the TP in section 2 in this contribution as the outcome of email discussion [100e-NR-L1enh_URLLC_PDCCH-03].

2	Text Proposal

---------------------------------Start of Text Proposal on TS 38.213 v16.1.0----------------------------------------

10.1	UE procedure for determining physical downlink control channel assignment

<Unchanged parts are omitted>

A UE does not expect to be configured CSS sets that result to corresponding total, or per scheduled cell, numbers of monitored PDCCH candidates and non-overlapped CCEs per slot or per span that exceed the corresponding maximum numbers per slot.

For same cell scheduling or for cross-carrier scheduling where a scheduling cell and scheduled cell(s) have DL BWPs with same SCS configuration , a UE does not expect a number of PDCCH candidates, and a number of corresponding non-overlapped CCEs per slot or per span on a secondary cell to be larger than the corresponding numbers that the UE is capable of monitoring on the secondary cell per slot or per span, respectively. If a UE is provided PDCCHMonitoringCapabilityConfig = R16 PDCCH monitoring capability for the primary cell, except the first span of each slot, the UE does not expect a number of PDCCH candidates, and a number of corresponding non-overlapped CCEs per span on the primary cell to be larger than the corresponding numbers that the UE is capable of monitoring on the primary cell per span.

For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapped CCEs per slot are separately counted for each scheduled cell.

For all search space sets within a slot or within a span in slot , denote by a set of CSS sets with cardinality of and by a set of USS sets with cardinality of . The location of USS sets , , in is according to an ascending order of the search space set index.

Denote by , , the number of counted PDCCH candidates for monitoring for CSS set and by , , the number of counted PDCCH candidates for monitoring for USS set .

For the CSS sets, a UE monitors PDCCH candidates requiring a total of non-overlapping CCEs in a slot or in a span.

The UE allocates PDCCH candidates for monitoring to USS sets for the primary cell having an active DL BWP with SCS configuration in a slot if the UE is not provided PDCCHMonitoringCapabilityConfig for the primary cell or if the UE is provided PDCCHMonitoringCapabilityConfig = R15 PDCCH monitoring capability for all serving cells, or in the first span of each slot if the UE is provided PDCCHMonitoringCapabilityConfig = R16 PDCCH monitoring capability for the primary cell, according to the following pseudocode. If for the USS sets for scheduling on the primary cell the UE is not provided CORESETPoolIndex for first CORESETs, or is provided CORESETPoolIndex with value 0 for first CORESETs, and is provided CORESETPoolIndex with value 1 for second CORESETs, and if or , the following pseudocode applies only to USS sets associated with the first CORESETs. A UE does not expect to monitor PDCCH in a USS set without allocated PDCCH candidates for monitoring. If the UE is provided PDCCHMonitoringCapabilityConfig = R16 PDCCH monitoring capability for the primary cell, in the following pseudocode,and are replaced by and respectively, and and are replaced by and respectively

Denote by the set of non-overlapping CCEs for search space set and by the cardinality of where the non-overlapping CCEs for search space set are determined considering the allocated PDCCH candidates for monitoring for the CSS sets and the allocated PDCCH candidates for monitoring for all search space sets , .

Set

Set

Set

while AND

allocate PDCCH candidates for monitoring to USS set

;

;

;

end while

<Unchanged parts are omitted>

--------------------------------------End of Text Proposal on TS 38.212----------------------------------------------