5G-NR K0, K1 & K2 For Time Domain DL & UL Resource Allocation

5G-NR K0,K1 & K2 for Time Domain DL
& UL Resource allocation.
As per TS 38.214 (Physical layer procedures for Data) I have put together below PHY layer
Time Domain (Slot & Symbol level) resource allocation procedures.
Below are three 'k' values that govern time domain slot & symbol level resource allocation in
5G NR, based on the specifications in 38.214 (Physical layer procedures for Data) I have put
together below details on how UE interprets each of these 'k' vlues when gNB allocates Time
Domain resources per User.
Physical meanings of the 'k' are relatively simple as indicated below
K0: It is the offset between the DL slot where the PDCCH(DCI) for downlink scheduling is
received and the DL Slot where PDSCH data is scheduled.
K1: It is the offset between the DL slot where the data is scheduled on PDSCH and the UL
slot where the ACK/NACK Feedback for the scheduled PDSCH data need to be sent.
K2: Is the offset between the DL slot where the PDCCH(DCI) for Uplink scheduling is
received and the UL Slot where the UL data need to sent on PUSCH.
Based on the specifications in 38.214 & 38.213 I have put together below details on how
TimeDomain DL & UL resource allocation happens based on k0,k1 & k2 values.
5G NR TDD Slot Pattern
 When operating in TDD mode, UE need to be aware when to expect

the transmission(UL) and when to expect the reception(DL) in terms
of slots.
 Unlike LTE there are no predefined patterns, In NR the pattern can
be defined in more flexible way based on below parameters and
communicated to the UE via RRC Reconfig message for NSA.
 TS 38.133 (Radio Resource Management) has details on TDD
Pattern configurations for FR1 & FR2 for all the SCS.
I put together below details of TDD slot periodicity for RF2 with SCS of 120Khz, TS
38.101, 1.2 has all slot pattern configuration details for all SCS.
K0: Time Domain PDSCH Slot & Symbols Allocation
 In NR, DCI formats 1_0 and 1_1 are used to dynamically allocate
time-domain resources for PDSCH.
 In the case of dynamic scheduling, PDCCH carrying DCI 1_0 and
1_1 are in general addressed to either C-RNTI or SPS-C-RNTI.
 DCI formats 1_0 and 1_1 carries 4-bit field named ‘time domain
resource assignment’.
 There can be up to 16 rows in the look-up table or 'pdsch-
TimeDomainAllocationList' and hence maximum 4-bits are used for
the field ‘time domain resource assignment’ in a DCI message.
 When scheduling in a common search space for a SI-RNTI,RA-
RNTI,P-RNTI The ‘time domain resource assignment’ value points
to one of the rows of a default look-up table (A,B or C) or 'pdsch-
TimeDomainAllocationList' if provided in the Pdsch-
ConfingCommon setup.
 When scheduling for C-RNTI in a UE Specific Search Space The
‘time domain resource assignment' value points to one of the rows in
the 'pdsch-TimeDomainAllocationList' provided in the RRC
Reconfig message under 'pdsch-Config setup' . Below table from
38.14 5.1.2.1.1-1 has the details.
 Below I have illustrated examples on how the UE determines which
look-up table to be used.
 Each row in the look-up table provides the following parameters.
Determining DL Slot & symbols for PDSCH data scheduling:
 Not Always PDCCH & PDSCH numerology (SCS) are same,

therefore determining slot offset for PDSCH allocation only based
on k0 is not sufficient.
 There fore Below equation is used to determine the Slot Offset for
PDSCH allocation.
 PDCCH & PDSCH may have difference numerology then as shown

above scaling factor need to be added to k0 value, meaning if
PDCCH DCI is scheduled in Slot1 and PDCCH SCS is 30Khz( µ
=2) and PDSCH is 120Khz ( µ=3) then the scaling factor is
[1*2^3/2^2] = 8/2=4 need to add this scaling factor to k0.
I put together below examples to show how Time Domain resources are allocated for
scheduling Common & UE Specific RNTI's
Example1: PDSCH Time Domain Resource allocation for scheduling common RNTI (RA-
RNTI)
Based on above common configuration
 PDCCH (µ)= 3 (120kHZ)

 PDSCH(µ) = 3 (120Khz)
 PDCCH Monitoring slot = sl1 (PDCCH is available in every slot)
 PDCCH Monitoring Symbol in a Slot = Symbol 0 (1st symbol of a
slot).
 K0 for slot determination and Start Symbol & Allocation length
indicator value (SLIV) is derived based on the "time domain
resource assignment index" value in the DL DCI (1_0) which is
referenced to some 3gpp table's (38.214 5.1.2.1.1-1) or pdsch-
TimeDomainAllocationList provided in pdsch-ConfigCommon
setup via RRC Reconfigure message.
 In below example for RA-RTI I have considered referencing to a
3GPP Table(38.215,5.1.2.1), meaning pdsch-
TimeDomainAllocationList for pdsch-ConfigCommon setup is not
provided in RRC Reconfig message.
Example2:PDSCH Time Domain Resource allocation for Scheduling UE Specific C- RNTI

(Scheduling Data)
Based on above UE Specific configuration
 PDCCH (µ)= 3 (120kHZ)

 PDSCH(µ) = 3 (120Khz)
 PDCCH Monitoring slot = sl1 (PDCCH is available in every slot)
 PDCCH Monitoring Symbol in a Slot = Symbol 0 (1st symbol of a
slot).
 K0 for slot determination and Start Symbol & Allocation length
indicator value (SLIV) is derived based on the "time domain
resource assignment index" value in the DL DCI (1_1) which is
referenced to some 3gpp table's (38.214 5.1.2.1.1-1) or pdsch-
TimeDomainAllocationList provided in pdsch-Config setup via
RRC Reconfigure message.
 In below example for scheduling DL Data (C-RNTI) I have
considered referencing pdsch-TimeDomainAllocationList provided
in pdsch-Config setup in RRC Reconfigure message.
 TS 38.214,Clause 5.1.2.1 has complete details on SLIV calculations.
K1: PDSCH-to-HARQ_feedback timing indicator
 The "PDSCH-to-HARQ-timing-indicator" field values provided in

the DCI message map to values for a set of number of slots provided
by higher layer parameter dl-DataToUL-ACK under PUCCH-Config
in RRC Reconfig message (K1 Value).
 PDSCH-to-HARQ-timing-indicator is a three bits value sent in DCI
message, TS 38.214 Table 9.2.3-1 provides a mapping between
PDSCH-to-HARQ-timing-indicator value and the number of slots to
send feedback "dl-DataToUL-ACK" in PUCCH-Config in RRC
Reconfiguration message.
Below is an example to get K1 value for sending feedback for PDSCH data scheduled in DL
Slots 70,71,72 & 73.
Stay tuned will post a separate article on K2 value for UL PUSCH resource allocation..

5G-NR K0, K1 & K2 For Time Domain DL & UL Resource Allocation

Uploaded by

Copyright:

Available Formats

5G-NR K0, K1 & K2 For Time Domain DL & UL Resource Allocation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G-NR K0, K1 & K2 For Time Domain DL & UL Resource Allocation

Uploaded by

Copyright:

Available Formats

5G-NR K0,K1 & K2 for Time Domain DL

& UL Resource allocation.

Physical meanings of the 'k' are relatively simple as indicated below

5G NR TDD Slot Pattern

 When operating in TDD mode, UE need to be aware when to expect

K0: Time Domain PDSCH Slot & Symbols Allocation

 Not Always PDCCH & PDSCH numerology (SCS) are same,

 PDCCH & PDSCH may have difference numerology then as shown

Based on above common configuration

 PDCCH (µ)= 3 (120kHZ)

Example2:PDSCH Time Domain Resource allocation for Scheduling UE Specific C- RNTI

Based on above UE Specific configuration

 PDCCH (µ)= 3 (120kHZ)

K1: PDSCH-to-HARQ_feedback timing indicator

 The "PDSCH-to-HARQ-timing-indicator" field values provided in

You might also like