nlink BWP. Note that the 466 Chapter 4 scheduling flexibility may not be impacted by limiting the maximum number of CORESETs since different monitoring occasions can be configured flexibly even in associa- tion with the same CORESET. It is important to further note that the concept of PDCCH monitoring periodicity is defined per search space set and is not configured at the CORESET-level. Every configured search space with a certain monitoring periodicity (in terms of slots and starting symbols within the monitored slots) is associated with a CORESET. In LTE, the DCI format was closely coupled with the DCI size and monitoring for a certain DCI format in most cases implied monitoring for a new DCI size. In NR, the DCI formats and DCI sizes are decoupled. Different formats can have different DCI sizes, but several formats can share the same DCI size. This allows adding more formats in the future without increasing the number of blind decoding attempts. An NR device needs to monitor up to four different DCI sizes: one size used for the fallback DCI formats, one for downlink scheduling assignments, and unless the uplink downlink non-fallback formats are size-aligned, one for uplink scheduling grant. In addition, a device may need to monitor SFI and/or preemption indication DCIs using a fourth size, depending on the configuration. An NR UE needs to monitor the PDCCH candidates at multiple aggregation levels for the detection and reception of PDCCH. Inside a configured CORESET, NR SS defines the PDCCH candidates of each AL [8]. In NR, PDCCH employs DM-RS-based transmission. Unlike LTE PDCCH where cell-specific reference signals were used for coherent demodu- lation, the NR channel estimation complexity scales with the number of CCEs being monitored. Thus it is important to balance the scheduling flexibility against UE imple- mentation burden to facilitate cost-efficient UE implementation. For PDCCH DM-RS in a CORESET, the antenna port QCL configuration relating to the SS/PBCH block antenna port(s) or configured CSI-RS a