NR - Downlink Control

Table of Contents

Introduction

In NR system, the downlink control information (DCI) is carried by physical downlink control channel (PDCCH), which physically occupied a region in the 2-dimension resource grid, which is essentially comprised of a certain number of resource elements (RE's), a.k.a., control resource set (CORESET). Different from the counterpart in LTE, i.e., PDCCH region which always covers the whole frequency range, CORESET does not span the whole bandwidth, since the bandwidth in NR system is remarkably large while not all the NR UE's are able to perform reception over the whole bandwidth.

Due to the static feature of CORESET, the indication of its size is not necessary. Therefore, there is no PCFICH in NR system. Additionally, irrespective of downlink or uplink, asynchronous HARQ is utilized in NR. Hence, PHICH is not needed either.

In NR, the channel coding scheme for PDCCH is based on polar codes. It can support 512 coded bits (prior to rate matching1) and up to 140 information bits. Targetting an enhanced coverage, a beamformed single layer transmission is adopted for PDCCH. In this sense, it is similar to ePDCCH in LTE system.

Resource hierarchy

Just as its name indicates, the basic element for PDCCH is control channel element (CCE), which is comprised of 6 resource element groups (REG's), and a REG is defined as one resource block (RB) in one OFDM symbol2. An aggregation level number of CCE's forms one PDCCH. The value of aggregation level can be 1, 2, 4, 8, 163.

CORESET

A CORESET is essentially a time-frequency resource in which the UE tries to decode candidate control channels using one or more search spaces. For the sake of reuse between bandwidth parts (BWP's), a CORESET is per-cell other than per-BWP configured.

A CORESET can occur at any position within a slot and any frequency range of the carrier. In the time domain, it can be up to 3 OFDM symbols. While in the frequency domain, it is defined as a multiple of 6 RB's up to the whole bandwidth of a carrier.

For better spectral efficiency, the resources in a CORESET can be dynamically used for PDSCH transmission. To this end, whether the reserved resources are available for PDSCH is dynamically indicated in the DCI.

Particularly, the first CORESET, i.e., CORESET 0, is configured by master information block (MIB) in PBCH. After connection setup, a UE can be configured with a multiplicity of potentially overlapped CORESET's.

Each CORESET can be configured with a transmission configuration indication (TCI), which indicates the quasi-colocation (QCL) relationship of the PDCCH.

CCE-to-REG mapping

CCE-to-REG mapping is per-CORESET configured. Generally, there are a couple of CCE-to-REG mapping schemes, interleaved and non-interleaved. The former targets frequency diversity, while the latter aims to facilitate interference coordination and opportunistic scheduling.

A set of REG's which share the same precoding are termed one REG bundle. Namely, a REG bundle is the basic unit on which channel estimation is performed. All the possible cases can be listed in the table below.

CORESET duration (OFDM symbol) REG bundle size (REG number) REG bundle number
1 6 1
  2 3
2 6 1
  2 3
3 6 1
  3 2

Search space

As in LTE system, a NR UE also needs to blindly detect the DCI format4. A UE needs to monitor up to 4 different DCI sizes with 3 using C-RNTI and 1 using other RNTI's:

  • One size for fallback DCI formats,
  • One size for downlink scheduling assignments,
  • One size for uplink scheduling grants,
  • One size for slot-format indication and preemption indication.

A UE attempts to blindly decode a DCI based on search space, which is defined as a set of control channel candidates formed by a given aggregation level number of CCE's. To limit the complexity of blind DCI decoding, several constraints depending on the subcarrier bandwidth have been specified, e.g.,

  • For 15/30/60/120 kHz subcarrier bandwidth, up to 44/36/22/20 blind decoding attempts can be supported across all DCI payload sizes in one slot.
  • For 15/30/60/120 kHz subcarrier bandwidth, up to 56/56/48/32 CCE's on which channel estimation is performed can be supportd across all CORESET's in a slot.

DCI formats

Downlink scheduling assignments (DCI formats 1-0 and 1-1)

In NR, there are a couple of DCI formats for downlink scheduling assignments, the non-fallback format, i.e., DCI format 1-1, and the fallback format, i.e., DCI format 1-0. The former supports all NR features, whose size is variable since some information fields may be absent, which depends on whether the corresponding features are configured or not. The latter supports a limited set of NR functionalities with a fixed size.

Class Field Format 1-0 (bits) Format 1-1 (bits)
Format identifier   1 1
Resource related CFI 0 0, 35
  BWP indicator 0 0-26
  Frequency domain allocation7 Only type 1 resource allocation is supported.  
  Time domain allocation 1-4 1-4
  VRB-to-PRB mapping8 0, 1 0, 1
  PRB bundling size indicator 0, 1 0, 1
  Reserved resources9 0-2 0-2
  ZP CSI-RS trigger 0 0-2
Transport block (TB) related MCS 5 5, 1010
  New data indicator (NDI) 1 1, 2
  Redundancy version (RV) 2 2, 4
HARQ related Process number 4 4
  Downlink assignment index (DAI) 2 0, 2, 4
  HARQ feedback timing11 3 3
  Codeblock group transmission indicator (CBGTI) 0 0, 2, 4, 6, 812
  Codeblock group flush information (CBGFI) 0 0-112
Multi-antenna related Antenna ports 0 4-6
  Transmission configuration indication (TCI) 0 0, 313
  SRS request 0 214
  DMRS sequence initialization 0 0, 115
PUCCH-related PUCCH power control16 2 2
  PUCCH resource indicator (PRI)17 3 3

Uplink scheduling grants (DCI formats 0-0 and 0-1)

Similar to downlink scheduling assignments, uplink scheduling grants also use one of DCI formats, the non-fallback format, i.e., DCI format 0-1, and the fallback format, i.e., DCI format 0-0. Aiming to reduce the number of blind decoding, the non-fallback DCI formats for downlink scheduling assignments (format 1-1) and uplink scheduling grants (format 0-1) are aligned by padding to the smaller one.

Class Field Format 0-0 (bits) Format 0-1 (bits)
Format identifier   1 1
Resource related CFI 0 0, 35
  UL/SUL18 0, 1 0, 1
  BWP indicator 0 0-26
  Frequency domain allocation7 Only type 1 resource allocation is supported.  
  Time domain allocation 1-4 1-4
  Frequency hopping19 0, 1 0, 1
TB related MCS 5 5
  NDI 1 1
  RV 2 2
HARQ related Process number 4 4
  DAI20 0  
  CBGTI 0 0, 2, 4, 612
Multi-antenna related DMRS sequence initialization 0 115
  Antenna ports 0 2-5
  SRS resource indicator (SRI)21 0 Depend on the number of SRS groups configured,
      and codebook-based/non-codebook-based precoding.
  Precoding information22 0 0-623
  PTRS-DMRS association 0 0, 224
  SRS request 0 214
  CSI request 0 0-625
Power control PUSCH power control   2
  Beta offset 0 0, 226

Slot format indication (DCI format 2-0)

DCI format 2-0 is used to signal the SFI which is scrambled by SFI-RNTI and common to a severality of UE's.

Preemption indication (DCI format 2-1)

DCI format 2-1 is used to signal the preemption indicator to a UE, which is scrambled by INT-RNTI and common to multiple UE's.

Uplink power control commands (DCI format 2-2)

As a complement to the power control commands, DCI format 2-2 aims to support power control for semipersistent scheduling. For the purpose of reducing the number of blind decoding attempts, its size is aligned with the size of the fallback DCI formats, i.e., DCI formats 0-0 and 1-0.

SRS control commands (DCI format 2-3)

DCI format 2-3 is proposed for power control of SRS, which is decoupled with the power control for PUSCH.

Signalling of frequency domain resources

The frequency-domain resource allocation fields indicate the resource blocks in the active BWP. Regarding the indication, there are a couple of methods, termed type-0 and type-1 respectively. The former is based on a bitmap, and will bring about large signaling overhead. While the latter covers the a starting position in the frequency domain and an amount of resources.

The resource allocation scheme can be configured as type-0, type-1, and dynamic selection between the both27. Note that the allocation is indicated in the term of VRB. For type-0, each VRB is directly mapped to a PRB without interleaving. For type-1, there are two alternatives for the VRB-to-PRB mapping, interleaved and non-interleaved.

Generally, many transmission parameters are per-BWP configured. The information obtained are based on the current BWP, which should be transformed and translated before applied to the target BWP by padding/truncating for each DCI field.

Signalling of time domain resources

The time domain allocation field in DCI is essentially an entry index of the corresponding table. Totally two tables are configured by RRC signalling, for downlink scheduling assignment and uplink scheduling grant respectively. A table has up to 16 entries, with each entry consisting of

  • A slot offset relative to the DCI belonging slot
  • The starting OFDM symbol for data transmission
  • The number of OFDM symbols in the slot
  • For downlink, the PDSCH mapping type.

Slot aggregation is a tool for coverage enhancement, in which a TB is repeated across up to 8 slots. The related configuration is separately signalled by RRC signalling.

Signalling of TB size

Regarding TB size determination, NR adopts a hybrid method. For smaller TB, NR defines a table to lookup. While for larger TB, the TB size can be computed based on a formula.

Considering the 5-bit MCS field, there are 32 combinations. Depending on whether 256QAM is supported or not, there are 28 or 29 MCS levels and the other 428 or 329 are reserved for retransmission.

According to the indication of the scheduled resources, the number of RE's available can be obtained. By subtracting the RE's for DMRS, and CSI-RS/SRS, the number of RE's available for data transmission can be further acquired. According to the spectral efficiency indicated by MCS, an intermediate number of information bits can be got whereby table lookup or formula-based computation can be carried out. After that, the TB size can be determined.

For retransmission, the TB size is equal to that for initial transmission. Based on the modulation order indicated by the reserved MCS level, the code rate can be implicitly derived.

Footnotes:

1

Rate matching is used to match the number of coded bits to the resources available for PDCCH transmission, e.g., shortening, puncturing or repetition.

2

Within a REG, on every 4th subcarrier there is a DMRS RE.

3

In LTE, the aggregation level can only be 1, 2, 4, 8.

4

In NR, in order to reduce the complexity of blind DCI decoding at UE's, some DCI formats are aligned with identical size.

5

Present only when cross carrier scheduling is configured.

6

Used to activate one of up to 4 BWP's configured by higher layer signalling.

7

Depend on bandwidth and resource allocation type of the current active BWP, not the target BWP.

8

Present only when resource allocation type 1 is used.

9

Indicate whether the reserved resources can be used for PDSCH or not.

10

Depend on a second TB's presence.

11

Indicate when HARQ acknowledgement should be transmitted relative to the reception of the PDSCH.

12

Only if CBG retransmission is configured.

13

Indicate the QCL relationship for downlink transmission.

14

Request a SRS transmission.

15

Select between two preconfigured initialization values for the DMRS sequence.

16

Adjust PUCCH transmission power.

17

Select the PUCCH resource from a set of configured resources.

18

Present only when a supplementary uplink is configured.

19

Handle frequency hopping for type 1 resource allocation.

20

Handling of HARQ codebooks in case of UCI transmitted on PUSCH.

21

Determine the antenna ports and uplink transmission beam to PUSCH.

22

Select the precoding matrix and the number of layers for codebook-based precoding.

23

Depend on the number of antenna ports and the maximum rank supported.

24

Indicate the association between DMRS and PTRS ports.

25

Request transmission of a CSI report.

26

Control the amount of resources for UCI on PUSCH in case dynamic beta offset signalling is configured.

27

Using 1 bit in DCI.

28

Corresponding to QPSK, 16QAM, 64QAM, and 256QAM.

29

Corresponding to QPSK, 16QAM, and 64QAM.