Professional Documents
Culture Documents
Created By :
Shubham Pawar
What is coreset ?
Structure of CORESET
2
What is Coreset ?
CORESET is a set of physical resources(i.e, a specific area on NR Downlink Resource Grid) and
a set of parameters that is used to carry PDCCH/DCI.
It is equivalent to LTE PDCCH area (the first 1,2,3,4 OFDM symbols in a subframe).
In LTE PDCCH region, the PDCCH always spread across the whole channel Bandwidth
3
LTE Control Region vs NR CORESET
Legacy LTE control channels are always distributed across the entire system bandwidth, making it difficult to
control intercell interference .
NR PDCCHs are specifically designed to transmit in a configurable control resource set (CORESET).
A CORESET is analogous to the control region in LTE but is generalized in the sense that the set of RBs and
the set of OFDM symbols in which it is located are configurable with the corresponding PDCCH search
spaces. Such configuration flexibilities of control regions including time, frequency, numerologies, and
operating points enable NR to address a wide range of use cases.
The main difference between CORESET and LTE Control Region.
Frequency Domain Parameter : Since Control Region in LTE is always spreaded
across the whole channel band width, there is no parameters defining the
frequency domain region for LTE control region, but in NR we need a
parameter defining the frequency domain width for CORESET since the
frequency domain width can be set in any value in the multiples of 6 RBs.
Time Domain Parameter : Both NR CORESET and LTE Control Region can vary in
time domain length. So we need the parameter for time domain length both in
LTE in NR. In LTE, the time domain length of control region is defined by the
physical channel called PCFICH but in NR the time domain length of CORESET is
defined by the RRC parameter (ControlResourceSetduration).
Note: LTE has similar mapping between Aggregation Level and the Number of CCEs as described above.
The UE generally does not know the number of CCEs occupied by the current PDCCH, what DCI format
information is transmitted , and where the information it needs is located.
However, the UE knows what information it is expecting, and UE is aware of the RNTI value, For Example , In
Idle state UE would be expecting Paging or SI information, After initiating Random Access UE expects a RACH
Response, When there is uplink data in the buffer waiting to be sent UE expects UL Grant, etc…
For different expected information , The UE uses the corresponding RNTI to perform CRC check on the received
TB that has the CRC scrambled with the respective RNTI.
If the CRC check is successful, Then the UE knows that this information is what it needs and will further derive
the content of the DCI message, This is called PDCCH Blind decoding process.
• Common Search Space (CSS) PDCCH blind decoding procedure (Common RNTI's are mandated to use AL4,
AL8,AL16)
• Based on the above CSS nested CCE tree PDCCH blind decoding is performed based on following sequence, 4
CCEs (perform Blind decoding for 4 PDCCH Candidates), Then 8 CCEs(perform blind decoding for 2 PDCCH
candidates) and Then, Finally 16 CCEs(perform Blind decoding for 1 PDCCH candidate).
• Search Space are indicated by a set of contiguous CCEs the UE is supposed to monitor for scheduling
assignments/grants relating to a certain component carrier.
• Below are two types of search spaces used in NR-PDCCH to control each component carrier.
Common Search Space (CSS): DCI CRC is Scrambled with a SI-RNTI (System Information), RA-RNTI
(Random Access),TCRNTI( Temp Cell RNTI), P-RNTI (Paging ), INT-RNTI (Interruption ), SFI-RNTI (Slot Format
Indication), TPC-PUCCH-RNTI (Tx Pwr Ctrl), TPC-PUSCH-RNTI, TPC-SRS-RNTI, C-RNTI (Cell RNTI), CS-RNTI
(Configured Scheduling), For all common procedures
UE-Specific Search Space(USS): DCI CRC is Scrambled with a C-RNTI (Cell RNTI), CS-RNTI (Configured
Scheduling), these are specifically targeted to individual UE.
• A common search space (CSS) is shared across all UEs and a UE-specific search space (USS) is used per UE basis
(meaning this SS is specific for a UE).
9
Search Space Configuration
searchSpaceId : Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH
(MIB) or ServingCellConfigCommon. The searchSpaceId is unique among the BWPs of a Serving Cell
controlResourceSetId : The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET
configured in MIB and in ServingCellConfigCommon Values 1..maxNrofControlResourceSets-1 identify
CORESETs configured by dedicated signaling.
10
Search Space Configuration
monitoringSymbolsWithinSlot : Symbols for PDCCH monitoring in the slots configured for PDCCH
monitoring. The most significant (left) bit represents the first OFDM symbol in a slot. The least significant
(right) bit represents the last symbol. Corresponds to L1 parameter 'Montoringsymbols-PDCCH-within-slot'.
This indicates the starting OFDM symbols that UE should search for a SearchSpace. For example, if the value is
'1000000000000', it mean that UE should start searching from the first OFDM symbol. if the value is
'0100000000000', it mean that UE should start searching from the second OFDM symbol.
SearchSpaceType : Indicates whether this is a common search space (present) or a UE specific search
space as well as DCI formats to monitor for.
MIB carries the parameters indicating the location & resources for ControlResourceSetZero (CORSET#0) on the resource grid,
where UE needs to search for the Type0-PDCCH common search space to derive the SIB1 information.
As per 38.213 (Clause 4.1), UE determines If a control resource set zero for Type0-PDCCH common search space is present if
following criteria is met, if Kssb<=23 for FR1 and if Kssb is <= 11 for FR2 .
UE decodes the MIB message and reads the value of the IE " PDCCH Config SIB1". PDCCH Config SIB1: Value of this IE is a 8
bits length,
First 4 bits (MSB) will determine the "controlResourceSetZero" Index , this will indicate the Number of RB/symbols used to
determine the CORESET size of the type0 PDCCH Common Search Space.
Last 4 Bits (LSB) will determine the "searchSpaceZero" Index, this will indicate the PDCCH Monitoring Occasions, meaning the
System Frame Number & Slot Index that the UE need to monitor for the Type0-PDCCH common search space
12
CORESET -0 Configuration
• Now to get Number of RB/Symbol from Control Resource set 0 index,
which is 12 in this example. We need to refer 38.213 table from 13-1 to 13-10.
• To refer exact table, we need SSB Sub carrier spacing, PDCCH sub carrier
spacing and min BW.
• SSB sub carrier spacing we get from 38.104 - Table 5.4.3.3-1 for operating band. In this example band is n78 and from
38.104 SSB SCS is 30 kHz.
• PDCCH Sub carrier spacing is 30 kHz obtain from MIB SubCarrierSpacingCommon parameter. (n78 is FR1 band
).
• Min BW can be obtain from 38.101-1 - Table 5.3.5-1 Channel Bandwidths for Each NR band : FR1. For this n78 band Min
BW is 10 Mhz from the table
• To get which table to refer with this 3 conditions, I have made below table to refer.
Based on ControlResourceSetZero index 12 we got number of RB 48 and number of Symbol 1 from table 13-4
14
CORESET -0 Configuration
• For SSB index 4, O=5, M=1, i=0, SCS(u)=1, for u=1 slots/Frame=20
n0=(5x2^1+[0x1])mod20 = (10+0)mod20=10mod20=10
• CORESET 0 is scheduled at slot 10 and Slot 11 in the radio frame that meets the SFNc criteria
15
Xiaomi Technology India Private Limited 16