×Jan-03-2024
Apple Inc is looking for a 4G/5G system engineer on mobility control. Based in California, USA (Bay Area or San Diego). .

UE procedure for determining physical downlink control channel assignmentV15.11.0

Identify PDCCH monitoring time
ParameterValue
μ
SearchSpace.monitoringSlotPeriodicity
SearchSpace.monitoringSlotOffset
SearchSpace.duration
SearchSpace.monitoringSymbolsWithinSlot
ControlResourceSet.duration

PDCCH monitoring slots
nfnslot within a subframe
012345678910111213141516171819
0234512131415
1234512131415
2234512131415
3234512131415

PDCCH monitoring symbols
isymbol012345678910111213
Monitor PDCCH?YYYYYY

RNTI

Different DCIs are scrambled by different kinds of RNTIs. This is used to address a specific UE, a group of UEs or all UEs:

  • SI-RNTI and P-RNTI have fixed values to all UEs
  • INT-RNTI and SFI-RNTI are common to a group of UEs
  • Other RNTIs are dedicated per UE
Types of Radio Network Temporary Identifier (RNTI)
RNTIDCI formatApplicationValue
hexdecimal
SI-RNTI1_0PDSCH for System Information (SI)FFFF65535
P-RNTI1_0PDSCH for Paging messagesFFFE65534
RA-RNTI1_0PDSCH for Random Access Response (RAR, MSG2)0001 to FFEF0001 - 65519
TC-RNTI0_0, 1_0PUSCH for MSG3 re-transmissions, PDSCH for MSG4
C-RNTI0_0, 0_1, 1_0, 1_1PUSCH and PDSCH for control/data plane signaling
MCS-C-RNTI0_0, 0_1, 1_0, 1_1dynamic selection of low spectral efficiency MCS table for PDSCH and PUSCH
CS-RNTI0_0, 0_1, 1_0, 1_1configured grant scheduling for PUSCH, semi-persistent scheduling for PDSCH
TPC-PUSCH-RNTI2_2PUSCH power control command
TPC-PUCCH-RNTI2_2PUCCH power control command
TPC-SRS-RNTI2_3SRS power control command
INT-RNTI2_1Interruption signalled using pre-emption indications
SFI-RNTI2_0dynamic changes to the slot format signalled using SLot Format Indicator (SFI)
SP-CSI-RNTI0_1activate/deactivate semi-persistent CSI reporting

CORESET

Base station transmits PDCCH to UE using Resource Elements (REs) within a Control Resource Set (CORESET). For each DL BWP configured to a UE in a serving cell, a UE can be provided by higher layer signalling with P ≤ 3 CORESETs. For each CORESET, the UE is provided the following by ControlResourceSet:

Parameter structure of ControlResourceSet
ParameterValueDescriptions
controlResourceSetId0..11coreset index, unique among the BWPs of a serving cell
frequencyDomainResourcesBIT STRING (SIZE 45)a set of resource blocks, each bit corresponds a group of 6 RBs
duration1, 2, 3contiguous time duration of the CORESET in number of symbols
cce-REG-MappingTypeCHOICE
interleavednonInterleaved
reg-BundleSize2, 3, 6-number of REGs bundled together
interleaverSize2, 3, 6
shiftIndex0..274when absent, use physCellId
precoderGranularitysameAsREG-bundle, allContiguousRBsprecoder granularity in frequency domain
tci-StatesPDCCH-ToAddListSEQUENCE(SIZE 1..64) of TCI-StateIda subset of the TCI states defined in pdsch-Config
tci-StatesPDCCH-ToReleaseListSEQUENCE(SIZE 1..64) of TCI-StateId
tci-PresentInDCIenabledfield present: TCI field is present in DL-related DCI

field absent: TCI field is absent in DL-related DCI
pdcch-DMRS-ScramblingID0..65535DM-RS scrambling sequence initialization value. When absent, use physCellId

Detailed descriptions of the CORESET configurations:

  • controlResourceSetId of 0 is used for the CORESET configured by the controlResourceSetZero IE within MIB and within the ServingCellConfigCommon IE.
  • the CORESET duration is semi-statically configured. This differs from LTE where a UE needs to decode PCFICH before knowing how many symbols are used for PDCCH. Removing PCFICH in NR helps to speed up the decoding process.
    • Note: CORESET configuration does not specify the start symbol of the PDCCH (which is defined within SearchSpace configuration.
  • PDCCH and its DMRS are transmitted using a single antenna port 2000. Base station can apply precoding to this antenna port to generate a beam in the direction of the UE. precoderGranularity provides UE with information regarding the frequency selectivity of the precoding applied by the base station.
    • When precoderGranularity = sameAsREG-bundle: UE assumes that base station applies the same precoding weights to RBs within a REG bundle.
    • When precoderGranularity = allContiguousRBs: UE assumes that base station applies the same precoding weights to all RBs belonging to contiguous REG bundles. a UE does not expect:
      • to be configured a set of resource blocks of a CORESET that includes more than four sub-sets of resource blocks that are not contiguous in frequency
      • any RE of a CORESET to overlap with any RE determined from lte-CRS-ToMatchAround or with any RE of a SS/PBCH block
  • For each CORESET in a DL BWP of a serving cell, a respective frequencyDomainResources provides a bitmap. The bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, in ascending order of the PRB index in the DL BWP bandwidth of BWP PRBs with starting common RB position where the first common RB of the first group of 6 PRBs has common RB index .
  • A UE is also provided with Quasi Co-Location (QCL) information to support PDCCH decoding. QCL means that transmissions from different antenna ports share same common characteristics. To determine the quasi co-location relation of CORESET and the reference signals:
    • For a CORESET other than a CORESET with index 0:
      • if a UE has not been provided a configuration of TCI state(s) for the CORESET, or has been provided initial configuration of more than one TCI states for the CORESET but has not received a MAC CE activation command for one of the TCI states: UE assumes that the DM-RS antenna port associated with PDCCH receptions is quasi co-located with the SS/PBCH block the UE identified during the initial access procedure
      • if a UE has been provided a configuration of more than one TCI states for the CORESET as part of Reconfiguration with sync procedure but has not received a MAC CE activation command for one of the TCI states: UE assumes that the DM-RS antenna port associated with PDCCH receptions is quasi colocated with the SS/PBCH block or the CSI-RS resource the UE identified during the random access procedure initiated by the Reconfiguration with sync procedure.
      • if a UE is provided a single TCI state for a CORESET, or if the UE receives a MAC CE activation command for one of the provided TCI states for a CORESET, the UE assumes that the DM-RS antenna port associated with PDCCH receptions in the CORESET is quasi co-located with the one or more DL RS configured by the TCI state.
    • For a CORESET with index 0, the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with:
      • the one or more DL RS configured by a TCI state, where the TCI state is indicated by a MAC CE activation command for the CORESET, if any, or
      • a SS/PBCH block the UE identified during a most recent random access procedure not initiated by a PDCCH order that triggers a contention-free random access procedure, if no MAC CE activation command indicating a TCI state for the CORESET is received after the most recent random access procedure
      • the UE expects that QCL-TypeD of a CSI-RS in a TCI state indicated by a MAC CE activation command for the CORESET is provided by a SS/PBCH block:
        • if the UE receives a MAC CE activation command for one of the TCI states, the UE applies the activation command in the first slot that is after slot where k is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command and μ is the SCS configuration for the PUCCH. The active BWP is defined as the active BWP in the slot when the activation command is applied.

Search space

A set of PDCCH candidates for a UE to monitor is defined in terms of PDCCH search space sets. A search space set can be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. A UE monitors PDCCH candidates in one or more of the following search spaces sets:

Search space set types
TypeScrambling RNTIDCI formatUsed forConfigured bycell
CSSType0SI-RNTI1_0SIBMIB or SIB1PCell of MCG
Type0ASI-RNTI1_0other SIBssearchSpaceOtherSystemInformationPCell of MCG
Type1RA-RNTI, TC-RNTI, C-RNTI0_0, 1_0MSG2, MSG4ra-SearchSpacePCell
Type2P-RNTI1_0pagingpagingSearchSpacePCell of MCG
Type3INT-RNTI, SFI-RNTI, TPC-XXX-RNTI0_0, 1_0, 2_0, 2_1, 2_2, 2_3MISCSearchSpace with searchSpaceType = commonany
C-RNTI, MCS-C-RNTI, CS-RNTIPCell
USSC-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI0_0, 0_1, 1_0, 1_1UE specific signalingSearchSpace with searchSpaceType = ue-Specificany

While the full list of possible CCE aggregation levels is already defined in TS 38.211 Table 7.3.2.1-1: Supported PDCCH aggregation levels, for Type0, Type0A and Type2 PDCCH CSS, the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level are given in Table 10.1-1:

Table 10.1-1: CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level for CSS sets configured by searchSpaceSIB1
CCE Aggregation LevelNumber of CandidatesResource Element Groups (REG)Resource Elements (RE)
4424288
8248576
161961152

Each search space is mapped to a specific Control Resource Set (CORESET). The CORESET defines the set of Resource Blocks and the number of symbols available to the search space set. For each DL BWP configured to a UE in a serving cell, the UE is provided by higher layers with S ≤ 10 search space sets where, for each search space set from the S search space sets, the UE is provided the following by SearchSpace:

Parameter structure of SearchSpace
ParameterDetails
searchSpaceId0..39
controlResourceSetId0..11
monitoringSlotPeriodicityAndOffsetCHOICE
1 slot10 slots0..9160 slots0..159
2 slots0..116 slots0..15320 slots0..319
4 slots0..320 slots0..19640 slots0..639
5 slots0..440 slots0..391280 slots0..1279
8 slots0..780 slots0..792560 slots0..2559
duration2..2559
monitoringSymbolsWithinSlotBIT STRING (SIZE 14)
nrofCandidatesaggregationLevel1{0, 1, 2, 3, 4, 5, 6, 8}
aggregationLevel2
aggregationLevel4
aggregationLevel8
aggregationLevel16
searchSpaceTypeCHOICE
commonue-Specific
dci-Format0-0-AndFormat1-0dci-Formats{formats0-0-And-1-0, formats0-1-And-1-1}
dci-Format2-0nrofCandidates-SFIaggregationLevel1{1, 2}
aggregationLevel2
aggregationLevel4
aggregationLevel8
aggregationLevel16
dci-Format2-1
dci-Format2-2
dci-Format2-3dummy1sl{1, 2, 4, 5, 8, 10, 16, 20}
dummy2{1, 2}

Detailed descriptions of the SearchSpace configuration:

  • searchSpaceId: s, an identify for the Search Space Set being configured
  • controlResourceSetId: an association between the search space set s and a CORESET p
  • monitoringSlotPeriodicityAndOffset: a PDCCH monitoring periodicity of ks slots and a PDCCH monitoring offset of os slots
  • duration: Ts < ks slots indicating a number of slots that the search space set s exists
  • monitoringSymbolsWithinSlot: a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH monitoring. It is a bit string with each bit representing one symbol within a slot. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot.
  • nrofCandidates: , a number of PDCCH candidates per CCE aggregation level L. Base station uses this IE to focus the UE blinddecoding attempts to the most appropirate aggregation levels. E.g. if UE signal quality is low, base station may set 0 candidate for low aggregation levels.
  • searchSpaceType: an indication that search space set s is a CSS set or a USS set
    • if search space set s is a CSS set:
      • dci-Format0-0-AndFormat1-0: an indication to monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0
      • dci-Format2-0: an indication to monitor one or two PDCCH candidates for DCI format 2_0 and a corresponding CCE aggregation level
      • dci-Format2-1: an indication to monitor PDCCH candidates for DCI format 2_1
      • dci-Format2-2: an indication to monitor PDCCH candidates for DCI format 2_2
      • dci-Format2-3: an indication to monitor PDCCH candidates for DCI format 2_3
    • if search space set s is a USS set:
      • dci-Formats: an indication to monitor PDCCH candidates either for DCI format 0_0 and DCI format 1_0, or for DCI format 0_1 and DCI format 1_1

Restrictions of SearchSpace configuration:

  • If the monitoringSymbolsWithinSlot indicates to a UE to monitor PDCCH in a subset of up to three consecutive symbols that are same in every slot where the UE monitors PDCCH for all search space sets, the UE does not expect to be configured with a PDCCH SCS other than 15 kHz if the subset includes at least one symbol after the third symbol.
  • A UE does not expect to be provided a first symbol and a number of consecutive symbols for a CORESET that results to a PDCCH candidate mapping to symbols of different slots.
  • A UE does not expect any two PDCCH monitoring occasions on an active DL BWP, for a same search space set or for different search space sets, in a same CORESET to be separated by a non-zero number of symbols that is smaller than the CORESET duration.

A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot:

  • For search space set s, the UE determines that a PDCCH monitoring occasion(s) exists in a slot with number in a frame with number nf if
  • The UE monitors PDCCH candidates for search space set s for Ts consecutive slots, starting from slot , and does not monitor PDCCH candidates for search space set s for the next ks - Ts consecutive slots.
PDCCH monitoring

Within the search space, a UE performs blind decoding because it does not know the aggregation level, the position of the PDCCH within the set of CCEs, or the format, size of the DCI. To help limit the processing requirement of the UE, 3GPP provides in

  • Table 10.1-2: the maximum number of monitored PDCCH candidates, , for a DL BWP with SCS configuration μ for a UE per slot for operation with a single serving cell.
  • Table 10.1-3: the maximum number of non-overlapped CCEs, , for a DL BWP with SCS configuration μ that a UE is expected to monitor corresponding PDCCH candidates per slot for operation with a single serving cell. CCEs for PDCCH candidates are non-overlapped if they correspond to:
    • different CORESET indexes, or
    • different first symbols for the reception of the respective PDCCH candidates.
Table 10.1-2Table 10.1-3
μMaximum number of monitored PDCCH candidates

per slot and per serving cell
Maximum number of non-overlapped CCEs

per slot and per serving cell
04456
13656
22248
32032