tion) first allocation) REG 1 REG 1 REG 2 REG 1 REG 1 REG 2 DM-RS REG 2 REG 3 REG 4 REG 2 REG 3 REG 4 REG 3 REG 5 REG 6 REG 3 DM-RS REG 4 REG 4 REG 5 REG 6 REG 5 REG 5 REG 6 DM-RS REG 6 REG composition and DM-RS locations Figure 4.18 REG-to-CCE mapping options and REG composition 6] 448 Chapter 4 frequency domain, but transmitted only in the resource blocks used for PDCCH (with one exception as discussed below). However, during initial access, the location of the common resource blocks is not known to UE as this information is signaled as part of the minimum SI. Therefore, for CORESET 0 configured by PBCH, the sequence is generated starting from the first resource block in the CORESET. The RRC parameters that define a CORESET are as follows [13]: ControlResourceSet:: = SEQUENCE controlResourceSetId ControlResourceSetId, frequencyDomainResources BIT STRING (SIZE (45)), duration INTEGER ...maxCoReSetDuration) , , //maxCoReSetDuration = 3 ice-REG-MappingTyp CHOICE { interleaved SEQUENCE { reg-BundleSize ENUMERATED {n2, n3, n6}, interleaverSize ENUMERATED {n2, n3, n6}, shiftIndex INTEGER(0. maxNrofPhysicalResourceBlocks-1 nonInterleaved precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs} tci-StatesPDCCH SEQUENCE (SIZE (1. .maxNrofTCI-StatesPDCCH) OF TCI-StateId tci-PresentInDCI ENUMERATED {enabled} OPTIONAL pdcch-DMRS-ScramblingID BIT STRING (SIZE (16)) OPTIONAL In the preceding definition [6,9], controlResourceSetId corresponds to L1 parameter CORESET-ID whose value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon and values 1, 2, ,maxNrofControlResourceSets-1 identify the CORESETs configured by dedicated signaling. The controlResourceSetId is unique among the BWPs of a serving cell. frequencyDomainResources corresponds to the L1 parameter CORESET-freg-dom. Each bit corresponds a group of six RBs, with the grouping start from PRB 0, which is fully New Radio Access Physical Layer Aspects (Part 2) 449 contained in the bandwidth part within which the CORESET is configured