PUCCH-Config
PUCCH-Config is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.
Definition
The IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP).
PUCCH-Config ::= SEQUENCE {
resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N
resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N
resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N
resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N
format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig
OPTIONAL, -- Need N
schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId
OPTIONAL, -- Need N
multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M
dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M
spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo
OPTIONAL, -- Need N
spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId
OPTIONAL, -- Need N
pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M
...,
[[
resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N
dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, -- Need M
ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16 } OPTIONAL, -- Need M
subslotLengthForPUCCH-r16 CHOICE {
normalCP-r16 ENUMERATED {n2,n7},
extendedCP-r16 ENUMERATED {n2,n6}
} OPTIONAL, -- Need R
dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need M
numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R
dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK
spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo
OPTIONAL, -- Need N
spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId
OPTIONAL, -- Need N
spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16
OPTIONAL, -- Need N
spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF
PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N
resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16
OPTIONAL, -- Need N
resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16
OPTIONAL, -- Need N
sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M
schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610
OPTIONAL -- Need N
]],
[[
format0-r17 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M
format2Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M
format3Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M
format4Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M
ul-AccessConfigListDCI-1-2-r17 SetupRelease { UL-AccessConfigListDCI-1-2-r17 } OPTIONAL, -- Need M
mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Need R
powerControlSetInfoToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfo-r17
OPTIONAL, -- Need N
powerControlSetInfoToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfoId-r17
OPTIONAL, -- Need N
secondTPCFieldDCI-1-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
secondTPCFieldDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
dl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } OPTIONAL, -- Need M
dl-DataToUL-ACK-DCI-1-2-r17 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r17} OPTIONAL, -- Need M
ul-AccessConfigListDCI-1-1-r17 SetupRelease { UL-AccessConfigListDCI-1-1-r17 } OPTIONAL, -- Need M
schedulingRequestResourceToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1700
OPTIONAL, -- Need N
dmrs-BundlingPUCCH-Config-r17 SetupRelease { DMRS-BundlingPUCCH-Config-r17 } OPTIONAL, -- Need M
dl-DataToUL-ACK-v1700 SetupRelease { DL-DataToUL-ACK-v1700 } OPTIONAL, -- Need M
dl-DataToUL-ACK-MulticastDCI-Format4-1-r17 SetupRelease { DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 } OPTIONAL, -- Need M
sps-PUCCH-AN-ListMulticast-r17 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL -- Need M
]],
[[
schedulingRequestResourceToAddModListExt-v1900 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1900
OPTIONAL, -- Need N
resourceToAddModListExt-v1900 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1900
OPTIONAL -- Need N
]]
}Fields (52)
| Field | Description |
|---|---|
| resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet · OPTIONAL Need N since v15.1.0 | Lists for adding and releasing PUCCH resource sets (see TS 38.213 [13], clause 9.2). |
| resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId · OPTIONAL Need N since v15.1.0 | Lists for adding and releasing PUCCH resource sets (see TS 38.213 [13], clause 9.2). |
| resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource · OPTIONAL Need N since v15.1.0 | Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt , it includes the same number of entries, and listed in the same order, as in resourceToAddModList . |
| resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId · OPTIONAL Need N since v15.1.0 | Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt , it includes the same number of entries, and listed in the same order, as in resourceToAddModList . |
| format1 SetupRelease { PUCCH-FormatConfig } · OPTIONAL Need M | Parameters that are common for all PUCCH resources of format 1. |
| format2 SetupRelease { PUCCH-FormatConfig } · OPTIONAL Need M | Parameters that are common for all PUCCH resources of format 2. |
| format3 SetupRelease { PUCCH-FormatConfig } · OPTIONAL Need M | Parameters that are common for all PUCCH resources of format 3. |
| format4 SetupRelease { PUCCH-FormatConfig } · OPTIONAL Need M | Parameters that are common for all PUCCH resources of format 4. |
| schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig · OPTIONAL Need N since v15.1.0 | |
| schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId · OPTIONAL Need N since v15.1.0 | |
| multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId · OPTIONAL Need M since v15.1.0 | |
| dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) · OPTIONAL Need M since v15.1.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo · OPTIONAL Need N since v15.1.0 | Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see TS 38.321 [3], clause 5.18.8 and TS 38.213 [13], clause 9.2.2). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt ) and vice-versa. If the network includes spatialRelationInfoToAddModListExt , it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt . If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. |
| spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId · OPTIONAL Need N since v15.1.0 | Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE. |
| pucch-PowerControl PUCCH-PowerControl · OPTIONAL Need M since v15.1.0 | Configures power control parameters PUCCH transmission. |
| resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 · OPTIONAL Need N since v16.7.0 | Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt , it includes the same number of entries, and listed in the same order, as in resourceToAddModList . |
| dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } · OPTIONAL Need M since v16.0.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16 } · OPTIONAL Need M since v16.2.0 | List of the combinations of cyclic prefix extension and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable, respectively, to DCI format 1_1 and DCI format 1_2. The fields ul-AccessConfigListDCI-1-1-r16 and ul-AccessConfigListDCI-1-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.2.2-6). The field ul-AccessConfigListDCI-1-1-r17 indicates a list which only contains UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.2.2-6A). |
| subslotLengthForPUCCH-r16 CHOICE { · OPTIONAL Need R since v16.0.0 | Indicates the sub-slot length for sub-slot based PUCCH feedback in number of symbols (see TS 38.213 [13], clause 9). Value n2 corresponds to 2 symbols, value n6 corresponds to 6 symbols, value n7 corresponds to 7 symbols. For normal CP, the value is either n2 or n7 . For extended CP, the value is either n2 or n6 . |
| normalCP-r16 ENUMERATED {n2,n7} since v16.1.0 | |
| extendedCP-r16 ENUMERATED {n2,n6} since v16.1.0 | |
| dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} · OPTIONAL Need M since v16.2.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) · OPTIONAL Need R since v16.2.0 | Configuration of the number of bits for "PUCCH resource indicator" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} · OPTIONAL Cond PI2-BPSK since v16.0.0 | This field is used for PUCCH formats 3 and 4 according to TS 38.211, Clause 6.4.1.3.3.1. |
| spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo · OPTIONAL Need N since v16.4.0 | Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see TS 38.321 [3], clause 5.18.8 and TS 38.213 [13], clause 9.2.2). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt ) and vice-versa. If the network includes spatialRelationInfoToAddModListExt , it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt . If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. |
| spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId · OPTIONAL Need N since v16.4.0 | Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE. |
| spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16 · OPTIONAL Need N since v16.4.0 | Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see TS 38.321 [3], clause 5.18.8 and TS 38.213 [13], clause 9.2.2). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt ) and vice-versa. If the network includes spatialRelationInfoToAddModListExt , it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt . If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. |
| spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoId-r16 · OPTIONAL Need N since v16.4.0 | Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE. |
| resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16 · OPTIONAL Need N since v16.0.0 | Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE. |
| resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16 · OPTIONAL Need N since v16.0.0 | Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE. |
| sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 } · OPTIONAL Need M since v16.1.0 | Indicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config. |
| schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610 · OPTIONAL Need N since v16.4.0 | |
| format0-r17 SetupRelease { PUCCH-FormatConfig } · OPTIONAL Need M since v17.0.0 | Parameters that are common for all PUCCH resources of format 0. |
| format2Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } · OPTIONAL Need M since v17.0.0 | |
| format3Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } · OPTIONAL Need M since v17.0.0 | |
| format4Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } · OPTIONAL Need M since v17.0.0 | |
| ul-AccessConfigListDCI-1-2-r17 SetupRelease { UL-AccessConfigListDCI-1-2-r17 } · OPTIONAL Need M since v17.0.0 | List of the combinations of cyclic prefix extension and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable, respectively, to DCI format 1_1 and DCI format 1_2. The fields ul-AccessConfigListDCI-1-1-r16 and ul-AccessConfigListDCI-1-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.2.2-6). The field ul-AccessConfigListDCI-1-1-r17 indicates a list which only contains UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.2.2-6A). |
| mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} · OPTIONAL Need R since v17.0.0 | Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when a PUCCH resource used for repetitions of a PUCCH transmission includes first and second spatial settings for FR2, or first and second sets of power control parameters for FR1 (see TS 38.213 [13], clause 9.2.6). |
| powerControlSetInfoToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfo-r17 · OPTIONAL Need N since v17.0.0 | Configures power control sets for repetition of a PUCCH transmission in FR1. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included. |
| powerControlSetInfoToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfoId-r17 · OPTIONAL Need N since v17.0.0 | |
| secondTPCFieldDCI-1-1-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | A second TPC field can be configured via RRC for DCI-1-1 and DCI-1-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1. |
| secondTPCFieldDCI-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | A second TPC field can be configured via RRC for DCI-1-1 and DCI-1-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1. |
| dl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } · OPTIONAL Need M since v17.0.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| dl-DataToUL-ACK-DCI-1-2-r17 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r17} · OPTIONAL Need M since v17.0.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| ul-AccessConfigListDCI-1-1-r17 SetupRelease { UL-AccessConfigListDCI-1-1-r17 } · OPTIONAL Need M since v17.0.0 | List of the combinations of cyclic prefix extension and UL channel access type (see TS 38.212 [17], clause 7.3.1) applicable, respectively, to DCI format 1_1 and DCI format 1_2. The fields ul-AccessConfigListDCI-1-1-r16 and ul-AccessConfigListDCI-1-2-r17 are only applicable for FR1 (see TS 38.212 [17], Table 7.3.1.2.2-6). The field ul-AccessConfigListDCI-1-1-r17 indicates a list which only contains UL channel access types and is only applicable for FR2-2 (see TS 38.212 [17], Table 7.3.1.2.2-6A). |
| schedulingRequestResourceToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1700 · OPTIONAL Need N since v17.0.0 | |
| dmrs-BundlingPUCCH-Config-r17 SetupRelease { DMRS-BundlingPUCCH-Config-r17 } · OPTIONAL Need M since v17.0.0 | Configuration of the parameters for DMRS bundling for PUCCH (see TS 38.214 [19], clause 6.1.7). DMRS bundling for PUCCH is not supported for PUCCH format 0/2. In this release, this is not applicable to FR2-2. |
| dl-DataToUL-ACK-v1700 SetupRelease { DL-DataToUL-ACK-v1700 } · OPTIONAL Need M since v17.0.0 | List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| dl-DataToUL-ACK-MulticastDCI-Format4-1-r17 SetupRelease { DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 } · OPTIONAL Need M since v17.0.0 | List of timing for given group-common PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACK-MulticastDciFormat4-1 applies to DCI format 4_1 for MBS multicast (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
| sps-PUCCH-AN-ListMulticast-r17 SetupRelease { SPS-PUCCH-AN-List-r16 } · OPTIONAL Need M since v17.0.0 | The field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast. |
| schedulingRequestResourceToAddModListExt-v1900 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1900 · OPTIONAL Need N since v19.0.0 | |
| resourceToAddModListExt-v1900 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1900 · OPTIONAL Need N since v19.0.0 | Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt , it includes the same number of entries, and listed in the same order, as in resourceToAddModList . |
Used by (2)
Uses (42)
- DL-DataToUL-ACK-DCI-1-2-r16
- DL-DataToUL-ACK-DCI-1-2-r17
- DL-DataToUL-ACK-MulticastDCI-Format4-1-r17
- DL-DataToUL-ACK-r16
- DL-DataToUL-ACK-r17
- DL-DataToUL-ACK-v1700
- DMRS-BundlingPUCCH-Config-r17
- PUCCH-FormatConfig
- PUCCH-FormatConfigExt-r17
- PUCCH-PowerControl
- PUCCH-PowerControlSetInfo-r17
- PUCCH-PowerControlSetInfoId-r17
- PUCCH-Resource
- PUCCH-ResourceExt-v1610
- PUCCH-ResourceExt-v1900
- PUCCH-ResourceGroup-r16
- PUCCH-ResourceGroupId-r16
- PUCCH-ResourceId
- PUCCH-ResourceSet
- PUCCH-ResourceSetId
- PUCCH-SpatialRelationInfo
- PUCCH-SpatialRelationInfoExt-r16
- PUCCH-SpatialRelationInfoId
- PUCCH-SpatialRelationInfoId-r16
- SPS-PUCCH-AN-List-r16
- SchedulingRequestResourceConfig
- SchedulingRequestResourceConfigExt-v1610
- SchedulingRequestResourceConfigExt-v1700
- SchedulingRequestResourceConfigExt-v1900
- SchedulingRequestResourceId
- SetupRelease
- UL-AccessConfigListDCI-1-1-r16
- UL-AccessConfigListDCI-1-1-r17
- UL-AccessConfigListDCI-1-2-r17
- maxNrofPUCCH-ResourceGroups-r16
- maxNrofPUCCH-ResourceSets
- maxNrofPUCCH-Resources
- maxNrofPowerControlSetInfos-r17
- maxNrofSR-Resources
- maxNrofSpatialRelationInfos
- maxNrofSpatialRelationInfos-r16
- maxNrofSpatialRelationInfosDiff-r16