mmWave & 5G

DCI Format 1_1

/D-C-I one-one/
One of the 5G NR downlink control information formats carried on the PDCCH, DCI format 1_1 schedules a PDSCH transmission for a single UE and is monitored only in the UE-specific search space. Unlike the compact fallback format 1_0, its payload is configurable: fields for frequency-domain resource assignment, antenna ports, bandwidth-part selection, transmission-configuration indication, and code-block-group control are sized by RRC, letting the gNB unlock spatial multiplexing up to 8 layers, dynamic BWP switching, and beam management. Typical sizes run from about 45 to more than 70 bits, scrambled by a 16-bit C-RNTI CRC for addressing and error detection.
Category: mmWave & 5G
Search space: UE-specific only
Schedules: PDSCH (DL data)

The Flexible Downlink Scheduling Grant in 5G NR

3GPP TS 38.212 defines a small set of DCI formats, each tailored to a scheduling job. Formats 0_0 and 0_1 grant uplink PUSCH; formats 1_0 and 1_1 grant downlink PDSCH. Within the downlink pair, 1_0 is the fallback grant: a fixed, compact field layout that the UE can decode before it has a full RRC configuration, and which appears in both the common and UE-specific search spaces. Format 1_1 is the workhorse scheduling grant once the connection is established. It lives only in the UE-specific search space, and its field set expands or contracts according to how the network has configured that UE.

That flexibility is the entire point. Format 1_1 carries fields that 1_0 simply does not have: a bandwidth-part indicator so the scheduler can move a UE between configured BWPs slot by slot, an antenna-ports field that selects DMRS ports and the number of MIMO layers, a transmission-configuration-indication (TCI) field that points to a beam for FR2 millimeter-wave operation, an SRS request, and optional code-block-group transmission information for fine-grained HARQ retransmission. Because these fields are present or sized only when the corresponding feature is configured, two UEs on the same cell can be monitoring 1_1 payloads of different lengths in the same slot.

Variable length creates a decoding problem. The UE does not know in advance which PDCCH candidate carries its grant, so it performs blind decoding across an aggregation of control-channel elements. To keep that search tractable, 3GPP caps the number of distinct DCI sizes a UE budgets per slot at four total, of which at most three may be C-RNTI scrambled. When the natural size of 1_1 collides with this budget, a defined padding and alignment procedure either zero-pads the smaller format up to a common size or truncates fields, so the UE never has to test more sizes than the limit allows.

Payload Sizing and Resource Assignment

Type 1 frequency-domain resource assignment (bits):
Nbits = ⌈ log2( NRBBWP × (NRBBWP + 1) / 2 ) ⌉

Bandwidth-part indicator (bits):
NBWP = ⌈ log2(nBWP) ⌉,  where nBWP = number of configured DL BWPs (max 4)

Time-domain resource assignment: 0 to 4 bits (indexes the PDSCH-TimeDomainResourceAllocationList)

CRC and addressing: LCRC = 16 bits, scrambled by the 16-bit C-RNTI

Example: for a 100 MHz FR1 carrier at 30 kHz SCS, NRBBWP ≈ 273, so the type 1 field is ⌈ log2(273 × 274 / 2) ⌉ = ⌈ log2(37401) ⌉ = 16 bits. With antenna-ports, TCI, and CBG fields enabled the total 1_1 payload reaches roughly 60 to 70 bits before CRC.

DCI 1_1 vs 1_0 Field Comparison

AttributeDCI Format 1_0DCI Format 1_1
RoleFallback PDSCH grantFull-feature PDSCH grant
Search spaceCommon & UE-specificUE-specific only
Payload size~40 to 45 bits (fixed)~45 to 70+ bits (RRC-configured)
Resource alloc typeType 1 onlyType 0, type 1, or dynamic switch
MIMO layers1 layer (fixed DMRS port)Up to 8 via antenna-ports field
BWP indicatorNot present0, 1, or 2 bits
Beam (TCI) fieldNot present0 or 3 bits
CBG retransmissionNot supportedOptional (0, 2, 4, 6, or 8 bits)
Common Questions

Frequently Asked Questions

How does DCI format 1_1 differ from DCI format 1_0?

Format 1_0 is a compact fallback grant with a fixed field set, monitored in both the common and UE-specific search spaces and typically 40 to 45 bits. Format 1_1 is UE-specific only, with an RRC-configured payload of roughly 45 to 70+ bits. It adds a bandwidth-part indicator, an antenna-ports field, a TCI field for beam selection, and an SRS request, unlocking spatial multiplexing, dynamic BWP switching, and beam management that 1_0 cannot signal.

Why is the payload size of DCI 1_1 variable?

Several fields are sized by the gNB through RRC rather than fixed in the spec. The type 1 frequency-assignment field is ⌈log2(N(N+1)/2)⌉ bits and grows with carrier bandwidth; the BWP indicator is 0 to 2 bits; antenna-ports depends on DMRS configuration; and rate-matching, ZP-CSI-RS, and CBG fields appear only when enabled. The UE computes the exact size, then applies a size-alignment procedure so it blind-decodes no more than four DCI sizes (three C-RNTI scrambled) per slot.

What does the antenna-ports field in DCI 1_1 control?

It selects the DMRS ports for the PDSCH, which sets the number of spatial layers and the reference-signal pattern. The field indexes a row in the antenna-port tables of TS 38.212 and signals how many DMRS CDM groups carry no data, so the UE knows which resource elements hold data versus reference signals. With the TCI field it enables single-user MIMO up to 8 layers or coordinated multi-user MIMO, whereas 1_0 is locked to one layer on a fixed port.

5G NR Front-Ends

Build the RF Path Behind the Grant

From FR2 beamforming arrays to millimeter-wave up/down converters, RF Essentials supplies the hardware that turns a DCI 1_1 schedule into a real downlink. Talk to our engineers about your 5G system.

Get in Touch