9.2 PDCCH/EPDCCH/MPDCCH/SPDCCH validation for semi-persistent scheduling
36.2133GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Physical layer proceduresRelease 17TS
A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:
– the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI or UL-SPS-V-RNTI
– the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B, 2C and 2D, the new data indicator field refers to the one for the enabled transport block.
A UE shall validate a Semi-Persistent Scheduling assignment EPDCCH only if all the following conditions are met:
– the CRC parity bits obtained for the EPDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI or UL-SPS-V-RNTI
– the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B, 2C and 2D, the new data indicator field refers to the one for the enabled transport block.
A UE shall validate a Semi-Persistent Scheduling assignment MPDCCH only if all the following conditions are met:
– the CRC parity bits obtained for the MPDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI
– the new data indicator field is set to ‘0’.
A UE shall validate a Semi-Persistent Scheduling assignment SPDCCH/PDCCH with DCI format 7-0A/7-0B /7-1A/7-1B/7-1C/7-1D/7-1E/7-1F/7-1G only if all the following conditions are met:
– the CRC parity bits obtained for the SPDCCH/PDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI
– the new data indicator field is set to ‘0’.
– the DMRS position indicator field for DCI formats 7-1F/7-1G is set to 0 in case of subslot-PDSCH.
– in case of subslot-PUSCH, the DMRS pattern field for DCI formats 7-0A/7-0B is set to,
– ‘0’ for the LSB if the higher layer parameter semiPersistSchedIntervalUL is set to 1 subslot or if the UE is configured with higher layer parameter totalNumberPUSCH-SPS-STTI-UL-Repetitions, ’00’ otherwise for semi-persistent scheduling activation PDCCH /SPDCCH validation,
– ’11’ for semi-persistent scheduling release PDCCH /SPDCCH validation,
If the UE is not configured with more than one uplink SPS configuration on a given serving cell, validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-1A, 9.2-1B, 9.2-1C; otherwise, if the UE is configured with more than one uplink SPS configurations on a given serving cell, validation is achieved if all the fields excluding the 3 least significant bits of HARQ process number field for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-1A.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent activation or release.
– If the valid DCI format 0 is scrambled with UL-SPS-V-RNTI, the UE shall consider the received DCI information as a valid semi-persistent activation or release only for the SPS configuration indicated by the UL SPS configuration index field.
– On a given serving cell, if the UE is configured with more than one uplink SPS configurations, and if the valid DCI format 0/7-0A/7-0B is scrambled with SPS C-RNTI, the UE shall consider the received DCI information as a valid semi-persistent activation or release only for the SPS configuration indicated by the 3 least significant bits of the HARQ process number field in the DCI.
If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH/EPDCCH/SPDCCH Validation
|
DCI format 0 |
DCI format 1/1A |
DCI format |
DCI format |
DCI format 7-1A/1B/1C/1D/1E/1F/1G |
|
|
TPC command for scheduled PUSCH |
set to ’00’ |
N/A |
N/A |
set to ’00’ |
N/A |
|
Cyclic shift DM RS |
set to ‘000’ if present |
N/A |
N/A |
set to ‘0’ |
N/A |
|
Modulation and coding scheme |
MSB is set to ‘0’ |
N/A |
N/A |
N/A |
N/A |
|
HARQ process number |
N/A |
FDD: set to ‘000’ TDD: set to ‘0000’ |
FDD: set to ‘000’ TDD: set to ‘0000’ |
set to ‘0000’ |
set to ‘0000’ |
|
Modulation and coding scheme |
N/A |
MSB is set to ‘0’ for 5-bit MCS field, otherwise two MSBs are set to ‘0’ |
For the enabled transport block: |
– |
– |
|
Redundancy version |
N/A |
set to ’00’ |
For the enabled transport block: |
set to ’00’ |
set to ’00’ |
|
TPC command for slot/subslot-PUCCH |
N/A |
N/A |
N/A |
N/A |
set to ’00’ |
|
Cyclic Shift Field mapping table for DMRS |
– |
N/A |
N/A |
set to ‘0’ |
N/A |
Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH/EPDCCH/SPDCCH Validation
|
DCI format 0 |
DCI format 1A |
DCI format 7-0A/7-0B |
DCI format 7-1A/1B/1C/1D/1E/1F/1G |
|
|
TPC command for scheduled PUSCH |
set to ’00’ |
N/A |
set to ’00’ |
N/A |
|
Cyclic shift DM RS |
set to ‘000’ if present |
N/A |
set to ‘0’ |
N/A |
|
Modulation and coding scheme |
set to ‘11111’ |
N/A |
N/A |
N/A |
|
Resource block assignment and |
Set to all ‘1’s |
N/A |
N/A |
N/A |
|
HARQ process number |
N/A |
FDD: set to ‘000’ TDD: set to ‘0000’ |
set to ‘0000’ |
set to ‘0000’ |
|
Modulation and coding scheme |
N/A |
set to ‘11111’ for 5-bit MCS field, otherwise set to ‘111111’ |
set to ‘11111’ |
set to ‘11111’ |
|
Redundancy version |
N/A |
set to ’00’ |
set to ’00’ |
set to ’00’ |
|
Resource block assignment |
N/A |
Set to all ‘1’s |
set to all ‘1’s |
set to all ‘1’s |
|
TPC command for slot/subslot-PUCCH |
N/A |
N/A |
N/A |
set to ’00’ |
|
Cyclic Shift Field mapping table for DMRS |
– |
N/A |
set to ‘0’ |
N/A |
Table 9.2-1B: Special fields for Semi-Persistent Scheduling Activation MPDCCH Validation
|
DCI format 6-0A |
DCI format 6-1A |
|
|
HARQ process number |
set to ‘000’ |
Set to all ‘0’s |
|
Redundancy version |
set to ’00’ |
set to ’00’ |
|
TPC command for scheduled PUSCH |
set to ’00’ |
N/A |
|
TPC command for scheduled PUCCH |
N/A |
set to ’00’ |
Table 9.2-1C: Special fields for Semi-Persistent Scheduling Release MPDCCH Validation
|
DCI format 6-0A |
DCI format 6-1A |
|
|
HARQ process number |
set to ‘000’ |
Set to all ‘0’s |
|
Redundancy version |
set to ’00’ |
set to ’00’ |
|
Repetition number |
set to ’00’ |
set to ’00’ |
|
Modulation and coding scheme |
set to ‘1111’ |
set to ‘1111’ |
|
TPC command for scheduled PUSCH |
set to ’00’ |
N/A |
|
Resource block assignment |
Set to all ‘1’s |
Set to all ‘1’s |
For the case that the DCI format indicates a semi-persistent downlink scheduling activation, the TPC command for PUCCH field shall be used as an index to one of the four PUCCH resource values configured by higher layers, with the mapping defined in Table 9.2-2
Table 9.2-2: PUCCH resource value for downlink semi-persistent scheduling
|
Value of ‘TPC command |
|
|
’00’ |
The first PUCCH resource value configured by the higher layers |
|
’01’ |
The second PUCCH resource value configured by the higher layers |
|
’10’ |
The third PUCCH resource value configured by the higher layers |
|
’11’ |
The fourth PUCCH resource value configured by the higher layers |
